Fix some typos.

Author: SvenGroot

docs/Scripts.md

@@ -50,7 +50,7 @@ If there are any lines of comments after the annotations, these specify the desc
 item. They will be concatenated into a single line, though if you have a blank line this will be
 preserved in the output.
 
-For example, the following creates an argument named "ArgumentName" whole value will be stored in
+For example, the following creates an argument named "ArgumentName" whose value will be stored in
 the `arg` field. The argument is required, positional, and has a description:
 
 ```c++
@@ -199,7 +199,7 @@ Value          | Description
 ---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------
 **None**       | Field names are used as-is, without changing them. This is the default.                                                                                                                                                                                      |
 **PascalCase** | Field names are transformed to PascalCase. This removes all underscores, and the first character and every character after an underscore is changed to uppercase. The case of other characters is not changed.                                               | `some_name`, `_some_name`, `_someName` => SomeName
-**CamelCase**  | Field names are transformed to camcelCase. Similar to PascalCase, but the first character will not be uppercase.                                                                                                                                             | `some_name`, `_some_name`, `_SomeName`=> someName
+**CamelCase**  | Field names are transformed to camelCase. Similar to PascalCase, but the first character will not be uppercase.                                                                                                                                             | `some_name`, `_some_name`, `_SomeName`=> someName
 **SnakeCase**  | Field names are transformed to snake_case. This removes leading and trailing underscores, changes all characters to lower-case, and reduces consecutive underscores to a single underscore. An underscore is inserted before previously capitalized letters. | `some_name`, `_some__name`, `_someName` => some_name
 **DashCase**   | Field names are transformed to dash-case. Similar to SnakeCase, but uses a dash instead of an underscore.                                                                                                                                                    | `some_name`, `_some__name`, `_someName` => some-name
 **Trim**       | Removes leading and trailing underscores, but leaves the rest of the name alone.                                                                                                                                                                             | `some_name`, `_some_name` => some_name; `_someName` => someName

docs/ShellCommands.md

@@ -124,8 +124,8 @@ There are three ways the name of a command is determined when you call `add_comm
     manager.add_command<my_command>("name");
     ```
 
-2. If the name argument is omitted or an empty string, the compiler looks static method called
-   `name()` on the shell command class, and if so, calls it to get the name.
+2. If the name argument is omitted or an empty string, the compiler looks for a static method called
+   `name()` on the shell command class, and if found, calls it to get the name.
 3. If no such method exists, the type name (without the namespace prefix) is used as the name.
 
 The description is determined in a similar way:
@@ -137,8 +137,8 @@ The description is determined in a similar way:
     manager.add_command<my_command>("name", "The description of the command.");
     ```
 
-2. If the description argument is omitted or an empty string, the compiler looks static method
-   called `description()` on the shell command class, and if so, calls it to get the description.
+2. If the description argument is omitted or an empty string, the compiler looks for a static method
+   called `description()` on the shell command class, and if found, calls it to get the description.
 3. If no such method exists, the description will be empty.
 
 Here is an example of a class that uses the static methods to set its name and description: