Merge pull request #2687 from jasonrandrews/review

spelling fixes

Author: jasonrandrews

.wordlist.txt

@@ -5383,4 +5383,60 @@ ultraedge
 unclound
 wNdi
 whatsapp
-workdir
+workdir
+Alexandre
+CRI
+ClickHouse's
+EDuJ
+EOL
+ERNIE's
+Expb
+FEXPA
+Grasset
+Idxb
+LOQ
+MEC
+MECID
+MECIDs
+MIMEType
+Martino
+NvLxg
+Nydus
+PASes
+PolicyDeny
+Remb
+Romana
+SLdG
+TCB
+aMWqFmwBgwT
+actix
+ae
+aot
+cdd
+columnalt
+cri
+decrypt
+eade
+empt
+expBits
+exponentials
+jsozZm
+jyco
+keyprovider
+Linux's
+minimax
+modelcontextprotocol
+nter
+nydus
+oMdFIQ
+outputNAME
+poweroff
+qJs
+rBD
+rMDhjcaEM
+remBits
+snapshotter
+unmounting
+vnd
+xqcqqYHrjZ
+ztPjILBCbFEqnVlbvjUpM

content/learning-paths/automotive/tinkerblox_ultraedge/debian_installation.md

@@ -164,7 +164,7 @@ Place a `MicroPacFile` in your project directory.
 -   **limits**: Resource limits (memory, cpu)
 -   **mount**: Volume mount points
 -   **network**: Network configuration
--   **createdBy**: maintanier of the application
+-   **createdBy**: maintainer of the application
 -   **description**: description of the application
 
 ### Building the MicroPac

content/learning-paths/automotive/tinkerblox_ultraedge/main.md

@@ -97,21 +97,21 @@ execution fabric for high-performance compute infrastructure
 
 ### 5.2 High-Level Architecture
 
-**UltraEdge ‘Core’ Layer
**  
+**UltraEdge ‘Core’ Layer**  
 Handles compute infrastructure management including service
 orchestration, lifecycle management, rule engine orchestration, and
 data-flow management .
 
-**UltraEdge ‘Boost’ Layer
**  
+**UltraEdge ‘Boost’ Layer**  
 Implements performance-critical routines and FFI (Foreign Function
 Interface) calls; Contains dynamic connectors, and southbound protocol
 adapters
 
-**UltraEdge ‘Prime’ Layer
**  
+**UltraEdge ‘Prime’ Layer**  
 Contains business logic, trigger & activation sequences, and AI & mixed
 workload orchestration .
 
-**UltraEdge Edge-Cloud ‘Connect’ Layer
**  
+**UltraEdge Edge-Cloud ‘Connect’ Layer**  
 Supports data streaming to databases (InfluxDB, SQLite) and provides
 diagnostic/logging outputs .
 
@@ -322,7 +322,7 @@ Place a `MicroPacFile` in your project directory.
 -   **limits**: Resource limits (memory, cpu)
 -   **mount**: Volume mount points
 -   **network**: Network configuration
--   **createdBy**: maintanier of the application
+-   **createdBy**: maintainer of the application
 -   **description**: description of the application
 
 ### 7.4 Building the MicroPac

content/learning-paths/cross-platform/gitlab-managed-runners/pipeline.md

@@ -8,7 +8,7 @@ layout: learningpathall
 
 ## How to Create a CI/CD Pipeline with Gitlab-hosted Runners?
 
-To create the pipeline we only need to create a new **`.gitlab-ci.yml`** file in our Project and define it's stages. Nothing else is needed since Gtilab-hosted runners are readily avilable to any Project and doesn't need to be created or instantiated by the Gitlab users.
+To create the pipeline we only need to create a new **`.gitlab-ci.yml`** file in our Project and define it's stages. Nothing else is needed since Gtilab-hosted runners are readily available to any Project and doesn't need to be created or instantiated by the Gitlab users.
 
 Once we run our pipeline with the correct **`tags`** Gitlab will create everything that we need and yep it is as simple as that.
 
@@ -19,7 +19,7 @@ Once we run our pipeline with the correct **`tags`** Gitlab will create everythi
 2. We can choose to create **`.gitlab-ci.yml`** file by using one of the 2 options circled in red in the image below. 
 ![CI-CD-New #center](_images/ci-cd-new.webp)
 
-Option1: We can Click on **`Set up CI/CD`** button/link and follow the wizad to create an empty **`.gitlab-ci.yml`** file.
+Option1: We can Click on **`Set up CI/CD`** button/link and follow the wizard to create an empty **`.gitlab-ci.yml`** file.
 
 Option2: Click on the "+" button. From the popup menu click on **`New File`** option and name the file **`.gitlab-ci.yml`** and then click on **`Commit Changes`** button on the top right hand side like in the image below (Add any message as your commit message).
 ![New-YML #center](_images/new-yml.png)

content/learning-paths/cross-platform/gitlab-managed-runners/results.md

@@ -12,7 +12,7 @@ The Pipeline script has multiple sections where each section instructs the pipel
 
 ### First Section: Stages
 
-In this section we are describing how many squentional stages will our pipeline have and what are their names (ex. **`Build, Test and Deploy`**). If we would like all the stages or jobs to run simultinously then we simply don't define this section.
+In this section we are describing how many sequential stages will our pipeline have and what are their names (ex. **`Build, Test and Deploy`**). If we would like all the stages or jobs to run simultaneously then we simply don't define this section.
 
 ### Second Section: Build-Job part of the Build stage
 
@@ -25,17 +25,17 @@ Gitlab offers 3 Arm64 based Instances that use Linux as their OS.
 - saas-linux-medium-arm64
 - saas-linux-large-arm64
 
-For more information about all Arm and other avilable Gitlab-hosted runners check [Gitlab-Hosted Runners](https://docs.gitlab.com/ci/runners/hosted_runners/linux/) page.
+For more information about all Arm and other available Gitlab-hosted runners check [Gitlab-Hosted Runners](https://docs.gitlab.com/ci/runners/hosted_runners/linux/) page.
 
 {{%/notice%}}
 
 ### Other Sections: 
 
-The rest of the other sections follow the same patthern. You will notice that the **`Test`** stage for example has 2 Jobs in it (unit-test-job and lint-test-job). The **`Deploy`** stage here has only 1 Job called **`deploy-job`**.
+The rest of the other sections follow the same pattern. You will notice that the **`Test`** stage for example has 2 Jobs in it (unit-test-job and lint-test-job). The **`Deploy`** stage here has only 1 Job called **`deploy-job`**.
 As you get to learn more YML scripting you will be able to add a lot more complex functionality to your pipelines.
 
 {{%notice Note%}}
-Gitlab offers a lot of documentions on how to create pipeline that fits different needs and also offer common templates for them as well. You can access then from [Use CI/CD to build your application](https://docs.gitlab.com/topics/build_your_application/) page.
+Gitlab offers a lot of documentation on how to create pipeline that fits different needs and also offer common templates for them as well. You can access then from [Use CI/CD to build your application](https://docs.gitlab.com/topics/build_your_application/) page.
 {{%/notice%}}
 
 ## How to run your pipeline for testing and to check the results:
@@ -52,5 +52,5 @@ If you navigate to your pipeline editor from before you will notice that there a
 
 ### The other Tabs are:
 
-1. Visualize: which can visulaize your pipeline for you as you edit it's componenets which can be very helpful especially for complex pipelines.
-2. Validate: which can validate your pipeline script as you are editting them and saving from time to time so that you can catch any issues with you code early on.
+1. Visualize: which can visualize your pipeline for you as you edit it's components which can be very helpful especially for complex pipelines.
+2. Validate: which can validate your pipeline script as you are editing them and saving from time to time so that you can catch any issues with you code early on.

content/learning-paths/embedded-and-microcontrollers/asm/intro.md

@@ -22,6 +22,6 @@ The assembly level functions will conform to the [Arm Procedure Call Standard](h
 
 [Keil MDK](https://www.keil.arm.com/) can support a number of different environments.
 
-Keil Studio is a collection of `Visual Studio Code` Extensions to provide a complete development IDE. For installation instructions, refer to the [Arm Keil Studio for VS Code](/install-guides/keilstudio_vs/) install guide. Windows, Linux, and MacOS are supported hosts.
+Keil Studio is a collection of `Visual Studio Code` Extensions to provide a complete development IDE. For installation instructions, refer to the [Arm Keil Studio for VS Code](/install-guides/keilstudio_vs/) install guide. Windows, Linux, and macOS are supported hosts.
 
 You can also use the legacy μVision IDE. For installation instructions, refer to the [Keil μVision](/install-guides/mdk/) install guide. Note that only Windows is a supported host.

content/learning-paths/embedded-and-microcontrollers/customer-support-chatbot-with-llama-and-executorch-on-arm-based-mobile-devices/how-to-2.md

@@ -8,7 +8,7 @@ layout: learningpathall
 
 ## Android NDK and Android Studio -  Environment Setup
 
-#### Plartform Required 
+#### Platform Required  
 - An AWS Graviton4 r8g.16xlarge instance to test Arm performance optimizations, or any [Arm based instance](/learning-paths/servers-and-cloud-computing/csp/) from a cloud service provider or an on-premise Arm server or Arm based laptop.
 - An Arm-powered smartphone with the i8mm feature running Android, with 16GB of RAM.
 - A USB cable to connect your smartphone to your development machine.

content/learning-paths/embedded-and-microcontrollers/yolo-on-himax/flash-and-run.md

@@ -53,7 +53,7 @@ The COM identifier is prefixed with **tty**, so you can use this to help you ide
   {{< tab header="Linux" language="shell">}}
 sudo grep -i 'tty' /var/log/dmesg
   {{< /tab >}}
-  {{< tab header="MacOS" language="shell">}}
+  {{< tab header="macOS" language="shell">}}
 ls /dev/tty.*
   {{< /tab >}}
 {{< /tabpane >}}

content/learning-paths/embedded-and-microcontrollers/yolo-on-himax/web-toolkit.md

@@ -54,7 +54,7 @@ Run the script corresponding to the OS of your host machine.
   {{< tab header="Linux" language="shell">}}
 ./we2_local_image_gen project_case1_blp_wlcsp.json
   {{< /tab >}}
-  {{< tab header="MacOS" language="shell">}}
+  {{< tab header="macOS" language="shell">}}
 ./we2_local_image_gen_macOS_arm64 project_case1_blp_wlcsp.json
   {{< /tab >}}
 {{< /tabpane >}}

content/learning-paths/mobile-graphics-and-gaming/build-llama3-chat-android-app-using-executorch-and-xnnpack/1-dev-env-setup.md

@@ -36,7 +36,7 @@ Start by downloading and installing the latest version of Android Studio by navi
 https://developer.android.com/studio/
 ```
 
-### For MacOS: Using UI
+### For macOS: Using UI
 
 Follow these steps to configure Android Studio: