style: fix minor spelling errors (#203)

Fixing minor spelling things across the repo.

cli/src/help.rs

@@ -47,7 +47,7 @@ subdirectories won't be traversed. By default <MAX_DEPTH> is infinite."#;
 pub const DUMP_LONG_HELP: &str = r#"Show the data produced by YARA modules for a file
 
 YARA modules analyze files and extract information from them. This command shows all
-the data produced by one ore more YARA module for the given file. If no module is
+the data produced by one or more YARA module for the given file. If no module is
 explicitly specified with the `--module` option, any module for which YARA produced
 some information will be shown.
 

docs/Module Developer's Guide.md

@@ -418,7 +418,7 @@ After creating the files `yara-x/src/modules/protos/text.proto` and
 `yara-x/src/modules/text.rs` we are almost ready for building the module into
 YARA. But there are few more pending steps.
 
-Ths first thing that you must know is that your module is behind a `cargo`
+The first thing that you must know is that your module is behind a `cargo`
 feature
 flag. The module won't be built into YARA unless you tell `cargo` to do so. The
 name of the feature controlling your module is `text-module`, and this feature
@@ -1014,7 +1014,7 @@ You'll notice that each module in `/yara-x/src/modules/` has a `tests/`
 directory with a nested `testdata/` directory. The testing framework is
 expecting a particular format and input structure to use them:
 
-1. File conveted
+1. File converted
    to [Intel Hex](https://developer.arm.com/documentation/ka003292/latest/)
    format format
 2. Intel Hex format output zipped

lib/Cargo.toml

@@ -83,7 +83,7 @@ console-module = []
 # https://cuckoosandbox.org/
 #
 # The use of this module is currently discouraged. It is here for backward
-# compatiblity with YARA, but it won't be actively mantained or improved as
+# compatibility with YARA, but it won't be actively maintained or improved as
 # the Cuckoo Sandbox seems to be abandoned since 2017.
 cuckoo-module = []
 

lib/src/compiler/emit.rs

@@ -2144,7 +2144,7 @@ fn emit_for<I, B, C, A>(
 /// Each pair is stored in the `identifiers` and `expressions` fields of the
 /// `with` statement.
 /// For each pair, the code emitted by this function sets the variable
-/// corresponding to the identifier to the value of the emmited expression.
+/// corresponding to the identifier to the value of the emitted expression.
 /// Those variables are later used in the condition of the `with` statement.
 fn emit_with(
     ctx: &mut EmitContext,

lib/src/compiler/mod.rs

@@ -2391,7 +2391,7 @@ bitmask! {
 
 /// A sub-pattern in the compiled rules.
 ///
-/// Each pattern in a rule has one ore more associated sub-patterns. For
+/// Each pattern in a rule has one or more associated sub-patterns. For
 /// example, the pattern `$a = "foo" ascii wide` has a sub-pattern for the
 /// ASCII variant of "foo", and another one for the wide variant.
 ///

lib/src/modules/macho/parser.rs

@@ -44,7 +44,7 @@ const EXPORT_SYMBOL_FLAGS_WEAK_DEFINITION: u64 = 0x00000004;
 const EXPORT_SYMBOL_FLAGS_REEXPORT: u64 = 0x00000008;
 const EXPORT_SYMBOL_FLAGS_STUB_AND_RESOLVER: u64 = 0x00000010;
 
-/// Mach-O import opcode consants
+/// Mach-O import opcode constants
 const BIND_OPCODE_MASK: u8 = 0xF0;
 const BIND_IMMEDIATE_MASK: u8 = 0x0F;
 const _BIND_OPCODE_DONE: u8 = 0x00;

parser/src/parser/mod.rs

@@ -172,7 +172,7 @@ pub(crate) struct ParserImpl<'src> {
 
     /// A cache for storing partial parser results. Each item in the set is a
     /// (position, SyntaxKind) tuple, where position is the absolute index
-    /// of a token withing the source code. The presence of a tuple in the
+    /// of a token within the source code. The presence of a tuple in the
     /// cache indicates that the non-terminal indicated by SyntaxKind failed
     /// to match that position. Notice that only parser failures are cached,
     /// but successes are not cached. [packrat][1] parsers usually cache both

site/content/docs/intro/yara_vs_yara-x.md

@@ -109,7 +109,7 @@ YARA in all cases.
 ### Parser re-usability
 
 One of the problems with YARA was its monolithic design. The parser was so
-integrated with the rule compilation logic that it was impossible to re-use
+integrated with the rule compilation logic that it was impossible to reuse
 it for other purposes, like code formatting tools, linters, etc.
 
 Consequently, numerous alternative YARA parsers have emerged over time, such as
@@ -118,7 +118,7 @@ But maintaining those parser in-sync with the official one is hard, and very
 often they lag behind.
 
 YARA-X, in contrast, has a more modular design, where the parser is decoupled
-from the rule compilation logic, allowing the re-use of the parser for other
+from the rule compilation logic, allowing the reuse of the parser for other
 purposes.
 
 ## The bad things