minor tweak to note sections

Author: gonzolively

docs/architecture/containers/components/webassembly_module/index.md

@@ -11,4 +11,5 @@ Ocre containers use [WebAssembly (WASM)](https://webassembly.org/) modules as th
 
 Modules can either be pure WebAssembly or Ahead-of-Time (AOT) compiled binaries optimized for a specific platform target. In general, the Ocre Orchestration Hub will automatically AOT compile modules on-demand based on the architecture of the deployment target. However, there are instances where a pure WASM binary may be preferred.
 
-**Note:** Currently, only a single WASM module is supported per container image. However, we are exploring extending this to support multiple modules and/or components via the WebAssembly Component Model.
+{: .note}
+Currently, only a single WASM module is supported per container image. However, we are exploring extending this to support multiple modules and/or components via the WebAssembly Component Model.

docs/quickstart/firmware/hardware.md

@@ -63,8 +63,6 @@ In order to build the Ocre runtime properly, you'll need to install a few remain
 pip install -r zephyr/scripts/requirements.txt
 ```
 
-**Note:** This step is only possible after updating the repo with `west update`.
-
 ### **5. Install the Zephyr SDK**
 For the last Zephyr requirement, we must install the SDK. 
 

docs/quickstart/prerequisites/dev-environment/index.md

@@ -3,6 +3,7 @@ title: Setting Up Your Development Environment
 layout: default
 parent: Prerequisites 
 nav_order: 1
+has_toc: true
 ---
 
 # Setting Up Your Development Environment
@@ -28,7 +29,8 @@ Before you begin, ensure that you have the following tools installed on your dev
 2. [Visual Studio Code](https://code.visualstudio.com/): A lightweight but powerful source code editor.
 3. [Dev Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers): This extension allows you to use Docker containers as development environments within VS Code.
 
-**Note:** The dev container can also be run directly in GitHub via [CodeSpaces](https://docs.github.com/en/codespaces), though you will only be able to build Ocre containers, not load them on your device as the dev container will not have access to your local devices.
+{: .note}
+The dev container can also be run directly in GitHub via [CodeSpaces](https://docs.github.com/en/codespaces), though you will only be able to build Ocre containers, not load them on your device as the dev container will not have access to your local devices.
 
 ### Steps
 
@@ -44,7 +46,8 @@ Before you begin, ensure that you have the following tools installed on your dev
 
 Once you select the folder, VS Code will reload. If the container does not exist yet, it will automatically create one and clone the sample repository into an isolated container volume. This process may take a few moments, and progress will be displayed in the lower right corner of the VS Code window. After the container is ready, you can open a terminal within VS Code to access the container environment.
 
-**Note**: Additional documentation and a step-by-step guide for working with dev containers can be found [here](https://code.visualstudio.com/docs/remote/containers-tutorial).
+{: .note}
+Additional documentation and a step-by-step guide for working with dev containers can be found [here](https://code.visualstudio.com/docs/remote/containers-tutorial).
 
 ---
 
@@ -60,4 +63,10 @@ The toolchain container can also be launched and used interactively as follows:
 ```sh
 cd samples
 docker run --rm -it -v $(pwd):/home/ocre ocre/ocre-c-toolchain:latest
-```
+```
+---
+
+## Troubleshooting
+This section covers common issues you might encounter when setting up your development environment, along with their solutions.
+
+- If you encounter errors opening the dev container, you likely need to authenticate with the GitHub Container Registry. Follow the authentication steps in the [GitHub documentation](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic).

docs/samples/blinky/index.md

@@ -28,7 +28,7 @@ cmake -DWASI_SDK_DIR=/opt/wasi-sdk -DCMAKE_TOOLCHAIN_FILE=/opt/wamr-sdk/app-sdk/
 make
 ```
 
-**Note:** This will create a container image called `blinky.nbx` that we can then deploy to our device.  
+This will create a container image called `blinky.nbx` that we can then deploy to our device.  
 
 ![](BuildBlinky.jpg)
 

docs/samples/hello-world/index.md

@@ -28,7 +28,7 @@ cmake -DWASI_SDK_DIR=/opt/wasi-sdk -DCMAKE_TOOLCHAIN_FILE=/opt/wamr-sdk/app-sdk/
 make
 ```
 
-**Note:** This will create a container image called `hello-world.nbx` that we can then deploy to our device.  
+This will create a container image called `hello-world.nbx` that we can then deploy to our device.  
 
 ![](BuildHelloWorld.jpg)