corrected minor typo's

docs/create_app.md

@@ -39,7 +39,7 @@ Further settings include:
 ## Examples
 
 1. Click the **Target Board (Optional)** drop-down list.
-2. Enter a search term tp filter the list and then select your board. The details of the selected board are displayed.
+2. Enter a search term to filter the list and then select your board. The details of the selected board are displayed.
 3. Click **Select**.
 
 Next, select the example project. There are two types of example projects (available either from **Local** packs and/or
@@ -58,7 +58,7 @@ Specify a **Solution Base Folder** and click **Create**.
     activate the workspace and download the tools specified in the `vcpkg-configuration.json` file included in a
     project.
 
-A typical Blinky example includes a `REAMDE.md` file that contains valuable information about the hardware setup and
+A typical Blinky example includes a `README.md` file that contains valuable information about the hardware setup and
 specific tasks that need to be done before working with the target board:
 
 ![Alif E7 Blinky-HP example](./images/blinky-hp.png)
@@ -272,7 +272,7 @@ If there are validation issues:
 
 1. Either click on ![Issue icon](./images/issue-icon.png) and select the issue in the pop-up box (a) or
 2. Click the "Resolve" button for access to the pop-up box (a).
-3. Once a components with validation issues is opened, you can use the "eye" icon to see which component is
+3. Once a component with validation issues is opened, you can use the "eye" icon to see which component is
    missing/affected (b).
 4. Use the "Apply" button to select the missing components (only available if there is no choice between different
    components available).

docs/installation.md

@@ -44,7 +44,7 @@ folder.
 Required tools (such as a compiler toolchain or the CMSIS-Toolbox) are installed via the
 **Arm Tools Environment Manager**, controlled by the `vcpkg-configuration.json` file.
 
-Open the **Arm Tools Environment Manager** via the command pallette (Ctrl/Cmd + Shift + p) and select
+Open the **Arm Tools Environment Manager** via the command palette (Ctrl/Cmd + Shift + p) and select
 **Arm Tools: Configure Arm Tools Environment**. The "Arm Registry" opens:
 
 ![Arm Registry](./images/arm-registry.png)
@@ -127,5 +127,5 @@ settings. The available settings are:
 | Experimental Features | Use the checkbox to enable experimental features. |
 | Generate Clang Setup | Use the checkbox to automatically generate the required setup (`.clangd` file and `.vscode/settings.json`) for the active solution context. For Arm Compiler 6, include pre-defined macros in the `.clangd` file. |
 | Output Directory | Enter an output directory prefix for 'outdir' and 'tmpdir' and relocated build information files (experimental). |
-| Probe-ID | Specufy the unique identifier of a probe to be used for debugging. |
+| Probe-ID | Specify the unique identifier of a probe to be used for debugging. |
 | Use Web Services | Use the checkbox to enable web services to obtain information about devices, boards, and examples. If enabled, information from the internet and locally installed packs is used. If disabled, only information from installed packs is used. |

docs/userinterface.md

@@ -72,7 +72,7 @@ For files containing configuration wizard annotations, open the graphical view b
 The view will be opened next to the original source file. You can switch back pressing the **Show Source** button
 ![Open source file view](./images/open-source-file-view-icon.png).
 
-![RTE_Device.h file in configuration wizard view](./images/rte-devce-config-wiz-view.png)
+![RTE_Device.h file in configuration wizard view](./images/rte-device-config-wiz-view.png)
 
 ## Status bar