find and replace on atym

gonzolively · gonzolively · commit 253abd8a8dda · 2024-10-23T15:16:00.000-06:00
diff --git a/docs/architecture/containers/components/binary_objects/index.md b/docs/architecture/containers/components/binary_objects/index.md
@@ -5,7 +5,7 @@ parent: Components
 nav_order: 2 
 ---
 
-Atym containers can optionally include binary objects as part of the container image. These are additional resources that can be referenced by the WebAssembly module during execution.
+Ocre containers can optionally include binary objects as part of the container image. These are additional resources that can be referenced by the WebAssembly module during execution.
 
 Common use cases for binary objects include:
 
diff --git a/docs/architecture/containers/components/index.md b/docs/architecture/containers/components/index.md
@@ -8,11 +8,11 @@ nav_order: 0
 
 # Container Components
 
-Atym containers are designed to bring cloud-native principles to embedded devices, combining efficiency with flexibility. Each container is a self-contained unit that encapsulates an application and its dependencies, structured to optimize performance and resource usage on constrained hardware.
+Ocre containers are designed to bring cloud-native principles to embedded devices, combining efficiency with flexibility. Each container is a self-contained unit that encapsulates an application and its dependencies, structured to optimize performance and resource usage on constrained hardware.
 
-![](atym_container.png)
+![](ocre_container.png)
 
-An Atym container consists of **three** main elements, which are defined and organized within a **[Container Image Manifest](../container_image_manifest/)**:
+An Ocre container consists of **three** main elements, which are defined and organized within a **[Container Image Manifest](../container_image_manifest/)**:
 
 - **[WebAssembly Module:](../components/webassembly_module/)** The core executable portion of the container, compiled from the developer's chosen language.
 - **[Container Configuration:](../components/container_configuration/)** Metadata including the application name, execution properties, variables, and permissions.
diff --git a/docs/architecture/containers/components/ocre_container.png b/docs/architecture/containers/components/ocre_container.png
diff --git a/docs/architecture/containers/components/webassembly_module/index.md b/docs/architecture/containers/components/webassembly_module/index.md
@@ -7,8 +7,8 @@ nav_order: 0
 
 # WebAssembly Modules
 
-Atym containers use [WebAssembly (WASM)](https://webassembly.org/) modules as the format for executable code. These modules are stateless binaries compiled to run on the WASM virtual machine.
+Ocre containers use [WebAssembly (WASM)](https://webassembly.org/) modules as the format for executable code. These modules are stateless binaries compiled to run on the WASM virtual machine.
 
-Modules can either be pure WebAssembly or Ahead-of-Time (AOT) compiled binaries optimized for a specific platform target. In general, the Atym 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.
+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.
diff --git a/docs/architecture/containers/container_image_manifest/index.md b/docs/architecture/containers/container_image_manifest/index.md
@@ -6,33 +6,33 @@ nav_order: 1
 ---
 
 
-The Container Image Manifest is a crucial component of Atym containers, providing a comprehensive description of the container's structure and contents. It serves as the blueprint that defines and references the three main elements of an Atym container described in the [Components](../components/index.md) section. The manifest ensures that all components can be correctly deployed and executed by the [Atym Runtime](../../runtime). 
+The Container Image Manifest is a crucial component of Ocre containers, providing a comprehensive description of the container's structure and contents. It serves as the blueprint that defines and references the three main elements of an Ocre container described in the [Components](../components/index.md) section. The manifest ensures that all components can be correctly deployed and executed by the [Ocre Runtime](../../runtime). 
 
-Atym container images follow the [Open Container Initiative (OCI)](https://opencontainers.org/) format where possible, with some modifications to support the needs of constrained, embedded devices. The manifest format is modeled after the [OCI Image Manifest](https://github.com/opencontainers/image-spec/blob/main/manifest.md) format and conforms to the [Wasm OCI Artifact](https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/) layout specifications. This structure ensures that all components of the container are properly defined, versioned, and can be efficiently managed in resource-constrained environments.
+Ocre container images follow the [Open Container Initiative (OCI)](https://opencontainers.org/) format where possible, with some modifications to support the needs of constrained, embedded devices. The manifest format is modeled after the [OCI Image Manifest](https://github.com/opencontainers/image-spec/blob/main/manifest.md) format and conforms to the [Wasm OCI Artifact](https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/) layout specifications. This structure ensures that all components of the container are properly defined, versioned, and can be efficiently managed in resource-constrained environments.
 
 ---
 
 ### Example
 
-Here's an example of an Atym Container Image Manifest:
+Here's an example of an Ocre Container Image Manifest:
 
 ```json
 {
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.manifest.v1+json",
   "config": {
-    "mediaType": "application/vnd.atym.image.config.v1+json",
+    "mediaType": "application/vnd.ocre.image.config.v1+json",
     "digest": "sha256:32b81b11f15ea9c198d59e143b2a5f15446b50b8954ce2e6cfab959988271c78",
     "size": 341
   },
   "layers": [
     {
-      "mediaType": "application/vnd.atym.image.v1.wasm",
+      "mediaType": "application/vnd.ocre.image.v1.wasm",
       "digest": "sha256:6d61671e8d62f5e77ed054c2d3df4dc9b31e3c74fee7d478f3f2bbdc99a6f256",
       "size": 330
     },
     {
-      "mediaType": "application/vnd.atym.image.v1.blob",
+      "mediaType": "application/vnd.ocre.image.v1.blob",
       "digest": "sha256:201ef6570d2967b299cf5ab8f946f061d5db523c106bc90f72729693b798f431",
       "size": 709
     }
@@ -47,7 +47,7 @@ The elements within the container configuration are defined as follows:
 #### Required:
 - `schemaVersion` (*int*): Image manifest schema version; per the OCI Image Spec this
 MUST be **2**.
-- `mediaType` (*string*): Required type of this manifest file. For Atym containers, this MUST be
+- `mediaType` (*string*): Required type of this manifest file. For Ocre containers, this MUST be
 **application/vnd.nubixio.image.manifest.v1+json**.
 - `config` (*object*): References the configuration object for this container image. Schema follows the [OCI Content Descriptor schema](https://github.com/opencontainers/image-spec/blob/main/descriptor.md). It has the
 following restrictions:
diff --git a/docs/architecture/containers/index.md b/docs/architecture/containers/index.md
@@ -6,9 +6,9 @@ parent: Architecture
 nav_order: 1
 ---
 
-Atym containers are lightweight, portable environments that allow software to run consistently across different platforms. In the embedded world, Atym/Ocre containers bring the benefits of containerization to resource-constrained devices, revolutionizing embedded development. Atym 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/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.
 
 
 ![](containers.png)
 
-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, Atym containers offer these benefits while maintaining near-native performance, making them suitable for a wide range of embedded applications.
+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.
diff --git a/docs/architecture/index.md b/docs/architecture/index.md
@@ -7,9 +7,9 @@ nav_order: 2
 
 # Architecture
 
-![](atym_solution.png)
-Atym's core architecture consists of two **primary** components.
+![](ocre_solution.png)
+Ocre's core architecture consists of two **primary** components.
 
-- **[Atym 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 Atym Hub. It allows developers to focus on building solutions rather than dealing with low-level device details.
+- **[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.
 
-- **[Containers](../architecture/containers/):** Lightweight, portable environments for running applications on embedded devices. Atym containers consist of a WebAssembly module, configuration metadata, and optional binary objects. 
+- **[Containers](../architecture/containers/):** Lightweight, portable environments for running applications on embedded devices. Ocre containers consist of a WebAssembly module, configuration metadata, and optional binary objects. 
diff --git a/docs/architecture/ocre_solution.png b/docs/architecture/ocre_solution.png
diff --git a/docs/architecture/runtime/index.md b/docs/architecture/runtime/index.md
@@ -1,22 +1,22 @@
 ---
 layout: default
-title: Atym Runtime
+title: Ocre Runtime
 parent: Architecture
 nav_order: 0 
 ---
 
-# Atym Runtime
+# Ocre Runtime
 
 
-The Atym 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. 
+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. 
 
 ---
 
-![](atym_runtime_detailed.png)
+![](ocre_runtime_detailed.png)
 
 ## Components
 
-As illustrated in the diagram above, the runtime is composed of two main layers: the open-source Ocre components (in orange) and Atym's proprietary additions (in green).
+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).
 
 ### 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.
@@ -26,6 +26,6 @@ As illustrated in the diagram above, the runtime is composed of two main layers:
 - **[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.
 
-### Atym Components (Proprietary) 
-- **Device Manager**: Manages the secure boot process, establishes connection with the Atym 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 Atym container runtime. 
+### 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. 
diff --git a/docs/architecture/runtime/ocre_runtime_detailed.png b/docs/architecture/runtime/ocre_runtime_detailed.png
diff --git a/docs/overview/index.md b/docs/overview/index.md
@@ -4,8 +4,8 @@ title: Overview
 has_children: false
 nav_order: 1 
 ---
-Atym is a SaaS-based infrastructure solution that extends containerization to billions of resource-constrained edge devices, breaking past the "Linux barrier" to enable containerized applications on devices with as little as 1MB of memory. It brings cloud-native principles and OCI-like containerization to embedded devices, allowing developers to build, deploy, and manage modular applications across a wide range of connected products.
+Ocre is a SaaS-based infrastructure solution that extends containerization to billions of resource-constrained edge devices, breaking past the "Linux barrier" to enable containerized applications on devices with as little as 1MB of memory. It brings cloud-native principles and OCI-like containerization to embedded devices, allowing developers to build, deploy, and manage modular applications across a wide range of connected products.
 
-![Atym High-level Architecture](atym_architecture.png)
+![Ocre High-level Architecture](ocre_architecture.png)
 
-Traditionally, updates on embedded devices have been risky and complex, requiring specialized tools like cross-compilers and unit test tools. Atym simplifies this process by leveraging [Zephyr RTOS](https://zephyrproject.org/), [WebAssembly](https://webassembly.org/), and its custom runtime. With Atym, developers can create containers using their preferred language, allowing for flexibility and accelerating the deployment of modular applications in secure, platform-independent containers. This approach reduces risk and enables safer, more frequent updates to edge devices.
+Traditionally, updates on embedded devices have been risky and complex, requiring specialized tools like cross-compilers and unit test tools. Ocre simplifies this process by leveraging [Zephyr RTOS](https://zephyrproject.org/), [WebAssembly](https://webassembly.org/), and its custom runtime. With Ocre, developers can create containers using their preferred language, allowing for flexibility and accelerating the deployment of modular applications in secure, platform-independent containers. This approach reduces risk and enables safer, more frequent updates to edge devices.
diff --git a/docs/overview/ocre_architecture.png b/docs/overview/ocre_architecture.png
diff --git a/docs/reference/board-support/index.md b/docs/reference/board-support/index.md
@@ -7,4 +7,4 @@ has_children: true
 
 # Board Support
 
-This is the list of currently supported boards by the Atym platform. Click on the manufacturer below:
+This is the list of currently supported boards by the Ocre platform. Click on the manufacturer below:
diff --git a/docs/reference/container-api/index.md b/docs/reference/container-api/index.md
@@ -7,4 +7,4 @@ parent: Reference
 
 # Container APIs
 
-This section documents the Atym Container APIs.
+This section documents the Ocre Container APIs.
diff --git a/docs/reference/terms-and-definitions/index.md b/docs/reference/terms-and-definitions/index.md
@@ -60,4 +60,4 @@ A grouping that provides a unit of isolation. Each tenant operates within a segr
 ## V
 ---
 ### Variables
-Key/value pairs that are defined by the Atym system. These are generally values for key system attributes such as the current date/time.
+Key/value pairs that are defined by the Ocre system. These are generally values for key system attributes such as the current date/time.
diff --git a/docs/samples/index.md b/docs/samples/index.md
@@ -7,7 +7,7 @@ has_children: true
 
 # Sample Applications
 
-This page provides an overview of the sample applications available for Atym-enabled devices. These samples demonstrate how to build and deploy applications using the Atym platform, helping you get started with development quickly and efficiently.
+This page provides an overview of the sample applications available for Ocre-enabled devices. These samples demonstrate how to build and deploy applications using the Ocre platform, helping you get started with development quickly and efficiently.
 
 ---
 ## Sample Structure
@@ -24,11 +24,11 @@ These files work together to create a complete Ocre container application.
 ---
 
 ## Available Samples
-We offer *two* sample applications to help you understand and explore the capabilities of the Atym platform:
+We offer *two* sample applications to help you understand and explore the capabilities of the Ocre platform:
 
-1. **[Hello World](./hello-world/index.md):** A basic application that demonstrates the fundamental structure of an Atym application and familiarizes you with the development environment.
+1. **[Hello World](./hello-world/index.md):** A basic application that demonstrates the fundamental structure of an Ocre application and familiarizes you with the development environment.
 
-2. **[Blinky](./blinky/index.md)**: An application that shows how to interact with device hardware by controlling an LED, introducing basic I/O operations on Atym-enabled devices.
+2. **[Blinky](./blinky/index.md)**: An application that shows how to interact with device hardware by controlling an LED, introducing basic I/O operations on Ocre-enabled devices.
 
 ---
 
