fixed more atym speak, added first board to board support, and a few other minor changes

Author: gonzolively

docs/architecture/containers/index.md

@@ -6,9 +6,8 @@ parent: Architecture
 nav_order: 1
 ---
 
-Ocre containers are lightweight, portable environments that allow software to run consistently across different platforms. In the embedded world, Ocre/Ocre containers bring the benefits of containerization to resource-constrained devices, revolutionizing embedded development. Ocre containers (which are identical to [Ocre](https://lfedge.org/projects/ocre/) containers in function) enable developers to write applications in any language that can compile to WebAssembly, including C, C++, Rust, and more. This flexibility allows organizations to easily repackage existing C code into containerized apps, significantly simplifying management compared to monolithic firmware.
+Ocre containers are lightweight, portable environments that allow software to run consistently across different platforms. In the embedded world, Ocre containers bring the benefits of containerization to resource-constrained devices, revolutionizing embedded development. Ocre containers enable developers to write applications in any language that can compile to WebAssembly, including C, C++, Rust, and more. This flexibility allows organizations to easily repackage existing C code into containerized apps, significantly simplifying management compared to monolithic firmware.
 
-
-![](containers.png)
+![](ocre_containers.webp)
 
 The containerized approach facilitates easier collaboration in embedded projects, allowing vendors to contribute modules without deep integration challenges. Moreover, containers provide enhanced security through virtualization, which is particularly crucial for tiny devices lacking hardware memory management units. Importantly, Ocre containers offer these benefits while maintaining near-native performance, making them suitable for a wide range of embedded applications.

docs/architecture/containers/ocre_containers.webp

@@ -7,7 +7,6 @@ nav_order: 2
 
 # Architecture
 
-![](ocre_solution.png)
 Ocre's core architecture consists of two **primary** components.
 
 - **[Ocre Runtime:](../architecture/runtime/)** Installed on embedded devices, it serves as a stable base for container deployments. This commercially-supported version of the open-source [Ocre](https://lfedge.org/projects/ocre/) runtime provides a hardware abstraction layer and container runtime, working seamlessly with the Ocre Hub. It allows developers to focus on building solutions rather than dealing with low-level device details.

docs/architecture/index.md

@@ -4,28 +4,20 @@ title: Ocre Runtime
 parent: Architecture
 nav_order: 0 
 ---
-
 # Ocre Runtime
 
+The Ocre Runtime enables containerization on resource-constrained devices through a combination of proven open-source technologies:
 
-The Ocre Runtime is built upon the foundation of the [Ocre Runtime](https://lfedge.org/projects/ocre/), an entirely open-source initiative that provides the core functionality for running containerized applications on embedded devices. 
+![](ocre_runtime.webp)
 
----
+## Components
 
-![](ocre_runtime_detailed.png)
+- **[Zephyr](https://zephyrproject.org)**: A mature RTOS providing comprehensive library support, modularity, and support for hundreds of platforms out-of-the-box with easy adaptation to new hardware.
 
-## Components
+- **[WebAssembly Micro Runtime](https://github.com/bytecodealliance/wasm-micro-runtime)**: Provides lightweight, sandboxed execution of containers through efficient virtualization.
 
-As illustrated in the diagram above, the runtime is composed of two main layers: the open-source Ocre components (in orange) and Ocre's proprietary additions (in green).
+- **[WASI Components](https://component-model.bytecodealliance.org/introduction.html)**: Implements the WebAssembly System Interface for embedded systems, enabling standardized system access.
 
-### Ocre Components (Open-source)
-- **[Zephyr](https://zephyrproject.org)**: Ocre is built on the Zephyr RTOS for its comprehensive library support, modularity, and active developer community. This choice enables support for hundreds of platforms out-of-the-box and easy adaptation to new or custom hardware.
-- **[WebAssembly Micro Runtime](https://github.com/bytecodealliance/wasm-micro-runtime)**: Used as the virtualization layer, it allows for lightweight, sandboxed execution of containers on resource-constrained devices.
-- **Runtime Manager**: Oversees the execution of WebAssembly containers on target devices.
-- **Application Framework**: Supports multi-container embedded applications.
-- **[WASI Components](https://component-model.bytecodealliance.org/introduction.html)**: Tailored implementations of the WebAssembly System Interface for embedded systems.
-- **Hardware Abstraction Layer (HAL)**: Facilitates the "develop once, deploy anywhere" approach.
+- **Application Framework**: Manages container lifecycle, resource allocation, and inter-container communication for multi-container applications.
 
-### Ocre Components (Proprietary) 
-- **Device Manager**: Manages the secure boot process, establishes connection with the Ocre Hub, handles configuration updates, and maintains runtime integrity according to the manifest file. 
-- **Container Supervisor**: Manages container lifecycles using a state machine approach. It oversees container creation, execution, and termination, interfacing with the Ocre container runtime. 
+- **Runtime Manager**: Controls container deployment, updates, and monitoring across target devices.

docs/architecture/runtime/index.md

@@ -0,0 +1,62 @@
+---
+title: "B-U585I-IOT02A"
+layout: default
+parent: ST
+grandparent: Board Support
+---
+
+# B-U585I-IOT02A Discovery Board Overview
+
+---
+
+## Overview
+
+The **STM32 B-U585I-IOT02A Discovery Board** is a versatile IoT development platform built around ST Micro's STM32U585AI microcontroller. This board combines ultra-low-power operation with advanced security features, making it ideal for developing IoT, wearable, and sensor applications.
+
+Key features include:
+* Arm® Cortex®-M33 processor with TrustZone® security
+* 2 MB Flash memory and 786 KB SRAM
+* Wi-Fi® (802.11 b/g/n) and Bluetooth® Low Energy connectivity
+* Rich sensor array:
+ * 3D accelerometer and gyroscope
+ * Temperature and humidity sensor
+ * Digital barometer
+ * Time-of-flight and gesture detection
+* Multiple expansion options via ARDUINO® Uno V3, STMod+, and Pmod™ connectors
+* Integrated STLINK-V3E debugger with USB connectivity
+
+In the diagram below, you can see many of the board's physical components:
+
+![Board Layout](B-U585I-IOT02A.png)
+
+---
+
+## Powering the Device
+
+There are two micro-USB ports on the board. The *top right* usb port labeled **USB STLINK** is the usb port we'll be using in this guide. Plug in the device and you should see some LEDs light up.
+
+---
+
+## Connecting to the Device
+
+---
+
+## Rebooting the Device
+
+You may reboot the device by pressing the black button once.
+
+---
+
+## Resetting the Device to Factory Defaults
+
+Some information may be stored to flash memory and persist across reboots, such as any WiFi credentials you may have entered or applications that have been installed from the Atym hub. You can erase the flash memory to reset the board to a "Factory Default" state by pressing and holding the blue button for five seconds.
+
+---
+
+## Important Links
+
+For additional details about the board and development tools, please refer to the following resources:
+
+* **Product Page**: [https://www.st.com/en/evaluation-tools/b-u585i-iot02a.html](https://www.st.com/en/evaluation-tools/b-u585i-iot02a.html)
+* **User Manual**: [https://www.st.com/resource/en/user_manual/um2839-discovery-kit-for-iot-node-with-stm32u5-series-stmicroelectronics.pdf](https://www.st.com/resource/en/user_manual/um2839-discovery-kit-for-iot-node-with-stm32u5-series-stmicroelectronics.pdf)
+* **STM32CubeIDE**: [https://www.st.com/content/st_com/en/stm32cubeide.html](https://www.st.com/content/st_com/en/stm32cubeide.html)

docs/architecture/runtime/ocre_runtime.webp

@@ -1,8 +1,8 @@
 ---
-title: Placeholder
+title: ST
 layout: default
 parent: Board Support
-nav_order: 0
+has_children: true
 ---
 
-# Placeholder 
+# ST Boards

docs/architecture/runtime/ocre_runtime_detailed.png

@@ -1,8 +1,8 @@
 ---
 title: Board Support
 layout: default
-parent: Reference
-has_children: true 
+has_children: true
+nav_order: 6 
 ---
 
 # Board Support