@powerhousedao/academy 3.2.0-dev.2 → 3.2.0-dev.4

package/docs/academy/01-GetStarted/home.mdx

@@ -1,5 +1,5 @@
 ---
-title: Get Started
+title: Get started
 slug: /
 sidebar_class_name: category-index-page
 ---
@@ -11,11 +11,11 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
 <div className={styles.learningPath}>
   {/* Get Started Card - Full Width */}
   <div className={`${styles.pathCard} ${styles.fullWidth}`}>
-    <div className={styles.cardHeader} style={{ justifyContent: 'center' }}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Flash.svg" alt="" />
-      </div>
-      <h3 className="card-title">Get started</h3>
+    <div className={styles.cardHeader}>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Flash.svg" alt="" className={styles.titleIcon} />
+        Get started
+      </h3>
     </div>
     <div className={styles.cardContent}>
       <div style={{ maxWidth: '960px', margin: '0 auto', textAlign: 'center' }}>
@@ -49,13 +49,13 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
 
   <div className={styles.pathCard} style={{ border: '1px solid #4FC86F' }}>
     <div className={styles.cardHeader}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/BuilderEnvironment.svg" alt="" />
-      </div>
-      <h3 className="card-title">Get Started</h3>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Flash.svg" alt="" className={styles.titleIcon} />
+        Get started
+      </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/GetStarted/CreateNewPowerhouseProject" className="path-button">Build a Todo-list Document Model</a>
+      <a href="/academy/GetStarted/CreateNewPowerhouseProject" className="path-button">Build a todo-list document model</a>
     </div>
   </div>
 
@@ -64,16 +64,16 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
   {/* Row 2: Build User Experiences, Builder Track Image, Work with Data */}
   <div className={styles.pathCard} style={{ border: '1px solid #4FC86F' }}>
     <div className={styles.cardHeader}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Editor.svg" alt="" />
-      </div>
-      <h3 className="card-title">Build User Experiences</h3>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Editor.svg" alt="" className={styles.titleIcon} />
+        Build user experiences
+      </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/GetStarted/BuildToDoListEditor" className="path-button">Building a Todo-list Editor</a>
-      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingDocumentEditors" className="path-button">Building Document Editors</a>
-      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer" className="path-button">Building Custom Drive Explorers</a>
-      <a href="/academy/ComponentLibrary/DocumentEngineering" className="path-button">Component Library</a>
+      <a href="/academy/GetStarted/BuildToDoListEditor" className="path-button">Build a todo-list editor</a>
+      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingDocumentEditors" className="path-button">Build document editors</a>
+      <a href="/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer" className="path-button">Build custom drive explorers</a>
+      <a href="/academy/ComponentLibrary/DocumentEngineering" className="path-button">Component library</a>
     </div>
   </div>
 
@@ -86,38 +86,37 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
   }}>
     <img src="/img/Union.svg" alt="Powerhouse Union" width="250" />
     <div className={styles.masteryTrackTitle}>
-      <h3 className="card-title" style={{ margin: 0 }}>Mastery Track</h3>
+      <h3 className="card-title" style={{ margin: 0 }}>Mastery track</h3>
     </div>
   </div>
 
   <div className={styles.pathCard} style={{ border: '1px solid #4FC86F' }}>
     <div className={styles.cardHeader}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Data.svg" alt="" />
-      </div>
-      <h3 className="card-title">Work with Data</h3>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Data.svg" alt="" className={styles.titleIcon} />
+        Work with data
+      </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI" className="path-button">Reading & Writing through the API</a>
-      <a href="/academy/MasteryTrack/WorkWithData/WorkingWithSubgraphs" className="path-button">Create your own Subgraph</a>
-      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Using the Analytics Engine</a>
-      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Using the Analytics Engine</a>
+      <a href="/academy/MasteryTrack/WorkWithData/ReadingAndWritingThroughTheAPI" className="path-button">Read & write through the API</a>
+      <a href="/academy/MasteryTrack/WorkWithData/WorkingWithSubgraphs" className="path-button">Create your own subgraph</a>
+      <a href="/academy/MasteryTrack/WorkWithData/Analytics-Engine/intro" className="path-button">Use the analytics engine</a>
     </div>
   </div>
 
   {/* Launch Card - Full Width with 3 column buttons - RE-INSERTED */}
   <div className={`${styles.pathCard} ${styles.fullWidth}`}>
-    <div className={styles.cardHeader} style={{ justifyContent: 'center' }}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Launch.svg" alt="" />
-      </div>
-      <h3 className="card-title">Launch</h3>
+    <div className={styles.cardHeader}>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Launch.svg" alt="" className={styles.titleIcon} />
+        Launch
+      </h3>
     </div>
     <div className={styles.cardContent}>
       <div className={styles.buttonContainer}>
-        <a href="/academy/MasteryTrack/Launch/IntroductionToPackages" className="path-button">Intro To Packages</a>
-        <a href="/academy/MasteryTrack/Launch/PublishYourProject" className="path-button">Publish Your Project</a>
-        <a href="/academy/MasteryTrack/Launch/SetupEnvironment" className="path-button">Setup a Cloud Environment</a>
+        <a href="/academy/MasteryTrack/Launch/IntroductionToPackages" className="path-button">Intro to packages</a>
+        <a href="/academy/MasteryTrack/Launch/PublishYourProject" className="path-button">Publish your project</a>
+        <a href="/academy/MasteryTrack/Launch/SetupEnvironment" className="path-button">Set-up a cloud environment</a>
       </div>
     </div>
   </div>
@@ -125,38 +124,38 @@ import BrowserOnly from '@docusaurus/BrowserOnly';
   {/* Row 3: Cookbook, Use-cases, Advanced Topics */}
   <div className={styles.pathCard}>
     <div className={styles.cardHeader}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Cookbook.svg" alt="" />
-      </div>
-      <h3 className="card-title">Cookbook</h3>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Cookbook.svg" alt="" className={styles.titleIcon} />
+        Cookbook
+      </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/Cookbook" className="path-button">Powerhouse Recipes</a>
+      <a href="/academy/Cookbook" className="path-button">Powerhouse recipes</a>
     </div>
   </div>
 
   {/* Ensure this Use-cases Card block is clean */}
   <div className={styles.pathCard}> {/* New Use-cases Card */}
     <div className={styles.cardHeader}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Cookbook.svg" alt="Use-cases Icon" />
-      </div>
-      <h3 className="card-title">Use-cases</h3>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Cookbook.svg" alt="Use-cases Icon" className={styles.titleIcon} />
+        Use-cases
+      </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/ExampleUsecases/Chatroom/SetupBuilderEnvironment" className="path-button">Explore Use-cases</a>
+      <a href="/academy/ExampleUsecases/Chatroom/SetupBuilderEnvironment" className="path-button">Explore use-cases</a>
     </div>
   </div>
 
   <div className={styles.pathCard}>
     <div className={styles.cardHeader}>
-      <div className={styles.cardIconWrapper}>
-        <img src="/img/academy/icons/Advanced.svg" alt="" />
-      </div>
-      <h3 className="card-title">Architecture</h3>
+      <h3 className="card-title">
+        <img src="/img/academy/icons/Advanced.svg" alt="" className={styles.titleIcon} />
+        Architecture
+      </h3>
     </div>
     <div className={styles.cardContent}>
-      <a href="/academy/Architecture/PowerhouseArchitecture" className="path-button">Learn More</a>
+      <a href="/academy/Architecture/PowerhouseArchitecture" className="path-button">Learn more</a>
     </div>
   </div>
 </div>

package/docs/academy/01-GetStarted/styles.module.css

@@ -12,9 +12,9 @@
   display: grid;
   grid-template-columns: repeat(3, 1fr);
   gap: 2rem;
-  max-width: 1200px;
-  margin: 0 auto;
-  padding: 2rem;
+  /* max-width: 1200px; */
+  /* margin: 0 auto; */
+  /* padding: 2rem; */
   width: 100%;
   box-sizing: border-box;
 }
@@ -53,30 +53,23 @@
   display: flex;
   align-items: center;
   margin-bottom: 1rem;
-}
-
-.cardIconWrapper {
-  display: flex;
-  align-items: center;
   justify-content: center;
-  width: 20px;
-  height: 20px;
-  margin-right: 0.75rem;
 }
 
 :global(.card-title) {
   display: flex;
-  align-items: center;
+  align-items: flex-start;
   justify-content: flex-start;
   margin: 0;
   padding: 0;
   font-size: 1.25rem;
   font-weight: 600;
   line-height: 1.2;
+  gap: 0rem;
 }
 
 :global(.card-title img) {
-  display: inline-flex;
+  margin-top: 2px;
 }
 
 :global(.path-button) {
@@ -127,4 +120,4 @@
 :global([data-theme='dark']) :global(.path-button:hover) {
   background: var(--ifm-color-emphasis-200);
   border-color: var(--ifm-color-emphasis-300);
-} 
+}

package/docs/academy/02-MasteryTrack/01-BuilderEnvironment/02-StandardDocumentModelWorkflow.md

@@ -1,13 +1,14 @@
 # Create Powerhouse packages
 
 :::warning
-**This tutorial is a summary for builders that are familiar with building document models**.    
-It guides you through creating a Powerhouse Document Model, from initial setup to publishing a distributable package. 
+**This tutorial is a summary for builders that are already familiar with building document models**.    
+It provides a summary from initial setup up to publishing a distributable package.    
+
 Please start with the '**Get Started**' Chapter or '**Document Model Creation**' section if you are unfamiliar with building a document model.
 :::
 
 <details>
-<summary>Key Commands that you'll use in this flow</summary>
+<summary>Key commands that you'll use in this flow</summary>
 
 -   `pnpm install -g ph-cmd`: Installs the Powerhouse CLI globally.
 -   `ph init`: Initializes a new Powerhouse project or sets up the local environment.
@@ -22,7 +23,7 @@ Please start with the '**Get Started**' Chapter or '**Document Model Creation**'
 
 </details>
 
-## Phase 1: Setup and Initialization
+## Phase 1: Setup and initialization
 
 ### 1.1. Install Powerhouse CLI
 Ensure you have the Powerhouse Command Line Interface (`ph-cmd`) installed. This tool is crucial for managing your Powerhouse projects.
@@ -33,7 +34,7 @@ pnpm install -g ph-cmd
 The [Prerequisites](/academy/MasteryTrack/BuilderEnvironment/Prerequisites) guide for detailed installation instructions for Node.js, pnpm, and Git if you haven't set them up yet.
 :::
 
-### 1.2. Initialize Your Project Environment
+### 1.2. Initialize your project environment
 Before creating a specific project, or if you're setting up your environment for the first time to use Connect Studio Mode, initialize the Powerhouse environment. This command prepares your local setup, including a local Reactor configuration.
 ```bash
 ph init
@@ -60,7 +61,7 @@ When installing or using the Powerhouse CLI commands you are able to make use of
 Please be aware that these versions can contain bugs and experimental features that aren't fully tested.
 </details>
 
-### 1.3. Launch Connect in Studio Mode
+### 1.3. Launch Connect in studio mode
 Connect is your local development hub. Running it in Studio Mode spins up a local instance with a local Reactor, allowing you to define, build, and test document models.
 ```bash
 ph connect
@@ -71,14 +72,14 @@ This command typically opens Connect in your browser at `http://localhost:3000/`
 **Powerhouse Reactors** are essential nodes in the Powerhouse network. They store documents, manage versions, resolve conflicts, and verify document operation histories by rerunning them. Reactors can be configured for local storage (as in Studio Mode), centralized cloud storage, or decentralized storage networks.
 :::
 
-## Phase 2: Document Model Specification
+## Phase 2: Document model specification
 
-### 2.1. Define the Document Model Schema
+### 2.1. Define the document model schema
 Within Connect Studio Mode, navigate to the Document Model Editor. Here, you'll specify the structure of your document model using GraphQL Schema Definition Language (SDL).
 -   **State Schema:** Describes the data fields and types within your document (e.g., `ToDoItem` with `id`, `text`, `checked` fields).
 -   This schema is the blueprint for your document model's data.
 
-### 2.2. Define Document Model Operations
+### 2.2. Define document model operations
 In the same editor, specify the operations (state transitions) for your document model. These are also defined using GraphQL, specifically input types.
 -   **Operations Schema:** Specifies the actions that can be performed on the document (e.g., `AddTodoItemInput`, `UpdateTodoItemInput`, `DeleteTodoItemInput`).
 -   Each input type details the parameters required for an operation.
@@ -87,12 +88,12 @@ In the same editor, specify the operations (state transitions) for your document
     *   Use GraphQL input types for operation parameters.
     *   Ensure operations reflect user intent for a clean API.
 
-### 2.3. Export Document Model Specification
+### 2.3. Export document model specification
 Once your schema and operations are defined in Connect, export the specification. This will download a `.phdm.zip` file (e.g., `YourModelName.phdm.zip`). Save this file in the root of your Powerhouse project directory.
 
-## Phase 3: Implementation and Testing
+## Phase 3: Implementation and testing
 
-### 3.1. Generate Scaffolding Code
+### 3.1. Generate scaffolding code
 Use the Powerhouse CLI to process the exported `.phdm.zip` file and generate the necessary boilerplate code for your document model.
 ```bash
 ph generate YourModelName.phdm.zip
@@ -103,13 +104,13 @@ This command creates a new directory under `document-models/YourModelName/` cont
 -   A `gen/` folder with autogenerated TypeScript types, action creators, and utility functions based on your schema.
 -   A `src/` folder where you'll implement your custom logic (reducers, utils).
 
-### 3.2. Implement Reducer Logic
+### 3.2. Implement reducer logic
 Reducers are pure functions that implement the state transition logic for each operation defined in your schema. Navigate to `document-models/YourModelName/src/reducers/to-do-list.ts` (or similar, based on your model name).
 -   Implement the functions for each operation (e.g., `addTodoItemOperation`, `updateTodoItemOperation`).
 -   These functions take the current state and an action (containing input data) and return the new state.
 -   Powerhouse handles immutability behind the scenes.
 
-### 3.3. Write Unit Tests for Reducers
+### 3.3. Write unit tests for reducers
 It's crucial to test your reducer logic. Write unit tests in the `document-models/YourModelName/src/reducers/tests/` directory.
 -   Verify that each operation correctly transforms the document state.
 -   Use the auto-generated action creators from the `gen/` folder to create operation actions for your tests.
@@ -118,7 +119,7 @@ Run tests using:
 pnpm run test
 ```
 
-### 3.4. Implement the Document Editor
+### 3.4. Implement the document editor
 A document editor provides the user interface for interacting with your document model in Connect. Generate an editor template:
 ```bash
 ph generate --editor YourModelName --document-types powerhouse/YourModelName
@@ -132,25 +133,25 @@ This creates a template file, typically at `editors/your-model-name/editor.tsx`.
 -   Utilize components from `@powerhousedao/document-engineering` for consistency and rapid development. Learn more at [Document-Engineering](/academy/ComponentLibrary/DocumentEngineering)
 
 
-### 3.5. Test the Editor
+### 3.5. Test the editor
 Run Connect locally to see your editor in action:
 ```bash
 ph connect
 ```
 Create a new document of your defined type. Interact with your editor, test all functionalities, and ensure it correctly dispatches actions to the reducers and reflects state changes.
 
-## Phase 4: Packaging and Publishing
+## Phase 4: Packaging and publishing
 
 Once your document model and editor are implemented and tested, you can package them for distribution. A Powerhouse Package is a modular unit that can group document models, editors, scripts, and processors.
 
-### 4.1. Prepare Project for Packaging
+### 4.1. Prepare project for packaging
 If you didn't initialize your project with `ph init` intending it as a package, ensure your project structure is set up correctly. The `ph init` command is designed to create this structure.
 -   `document-models/`: Contains your document models.
 -   `editors/`: Contains your editor components.
 -   `src/`: Often used for shared utilities or can be part of the model/editor structure.
 -   (Optional) `processors/`, `scripts/` for advanced functionalities.
 
-### 4.2. Specify Package Details in `package.json`
+### 4.2. Specify package details in `package.json`
 Navigate to the `package.json` file in your project root. This file is crucial for NPM publishing.
 -   **`name`**: Follow a scoped naming convention, e.g., `@your-org-ph/your-package-name`. The `-ph` suffix helps identify Powerhouse ecosystem packages.
 -   **`version`**: Use semantic versioning (e.g., `1.0.0`).
@@ -184,7 +185,7 @@ Example `package.json` snippet:
 }
 ```
 
-### 4.3. Add a Manifest File (`manifest.json`)
+### 4.3. Add a manifest file (`manifest.json`)
 Create a `manifest.json` file in your project root. This file describes your package's contents (document models, editors) and helps host applications like Connect understand and integrate your package.
 
 Example `manifest.json`:
@@ -214,14 +215,14 @@ Example `manifest.json`:
 ```
 Update your project's main `index.js` or entry point to export your document models and editors so they can be discovered by Powerhouse applications.
 
-### 4.4. Build Your Project
+### 4.4. Build your project
 Compile and optimize your project for production:
 ```bash
 pnpm build
 ```
 This command typically creates a `dist/` or `build/` directory with the compiled assets. Ensure your `package.json`'s `files` array includes this directory and other necessary assets like `manifest.json`, `document-models`, and `editors` if they are not part of the build output but need to be in the package.
 
-### 4.5. Version Control
+### 4.5. Version control
 Store your project in a Git repository for versioning and collaboration.
 ```bash
 git init
@@ -241,13 +242,13 @@ To share your package with others or deploy it to different environments, publis
     ```
     Follow the prompts in your terminal or browser.
 
-2.  **Publish the Package:**
+2.  **Publish the package:**
     ```bash
     npm publish
     ```
     If your package is scoped and public, NPM will use the `publishConfig` from your `package.json`. If not set there, you might need `npm publish --access public`.
 
-### 4.7. Using Your Published Package
+### 4.7. Using your published package
 Once published, your package can be installed and used in any Powerhouse environment (like another local Connect instance or a deployed Reactor setup).
 ```bash
 ph install @your-org-ph/your-package-name

package/docs/academy/02-MasteryTrack/01-BuilderEnvironment/03-BuilderTools.md

@@ -1,9 +1,9 @@
-# Powerhouse Builder Tooling
+# Powerhouse builder tooling
 
 This page provides an overview of all the builder tooling offered by the Powerhouse ecosystem.   
 This list will be maintained and updated as our toolkit grows.
 
-## Powerhouse Command Line Interface
+## Powerhouse command line interface
 ___
 
 ### Installing the Powerhouse CLI 
@@ -49,7 +49,7 @@ Please be aware that these versions can contain bugs and experimental features t
 
 <summary> How to clean your system of the Powerhouse CLI?</summary>
 
-### Cleaning and Updating ph-cmd
+### Cleaning and updating ph-cmd
 
 If you need to perform a clean reinstallation of the Powerhouse CLI (`ph-cmd`), follow these steps:
 
@@ -83,7 +83,7 @@ This process ensures a clean slate by removing both the CLI tool and its configu
 
 </details>
 
-### The Use Command
+### The use command
 The use command allows you to switch between different environments for your Powerhouse project dependencies.
 
 ```bash
@@ -117,7 +117,7 @@ ph use local /path/to/local/packages
 ph use latest --package-manager pnpm
 ``` 
 
-### The Update Command
+### The update command
 The update command allows you to update your Powerhouse dependencies to their latest versions based on the version ranges specified in your package.json.
 
 ```bash
@@ -145,7 +145,7 @@ ph update --force prod
 ph update --package-manager pnpm
 ```
 
-## **Key Differences**
+## **Key differences**
 
 ### **Use command**
 - For switching between different **environments**.
@@ -172,7 +172,7 @@ The boilerplate includes essential commands with NPM/PNPM scripts for:
 - Building
 - Testing
 
-## Design System
+## Design system
 ___
 The Powerhouse Design System is a collection of reusable front-end components based on GraphQL scalars, including custom scalars specific to the web3 ecosystem. It provides:
 - Consistent UI components across Powerhouse applications
@@ -181,7 +181,7 @@ The Powerhouse Design System is a collection of reusable front-end components ba
 
 We cover some of these topics in our design system documentation. Read more about the [design system here](/academy/ComponentLibrary/DocumentEngineering)
 
-## Reactor Libraries
+## Reactor libraries
 ___
 Reactors are the nodes in the Powerhouse network that handle document storage, conflict resolution, and operation verification. 
 The Reactor Libraries include:
@@ -196,32 +196,32 @@ Handles client-side interactions
 ### Local
 Manages local storage and offline functionality
 
-### Drive App
+### Drive app
 Handles document organization and storage management, but can also be customized to offer specific functionality, categorization, or tailored interfaces for your documents. 
 
-## Code Generators
+## Code generators
 ___
 Powerhouse provides several code generation tools to streamline development:
 
-    ### Document Model Scaffolding
+    ### Document model scaffolding
     Generates the basic structure for new Document Models with the command `ph init` based on the boilerplate. 
 
-    ### Editor Generator
+    ### Editor generator
     Creates template code for Document Model editors with the command `ph generate --editor <name> --document-types <documenttype>`
 
-    ### Drive Editor Generator
+    ### Drive editor generator
     Builds scaffolding for custom Drive interfaces with the command `ph generate --drive-editor <name>`
 
-    ### Subgraph Generator
+    ### Subgraph generator
     Creates GraphQL subgraph templates for data access automatically upon `ph reactor`
 
-    ### Processor Generator
+    ### Processor generator
     Generates processor templates for event handling automatically upon `ph reactor`
 
-    ### Analytics Processor Generator
+    ### Analytics processor generator
     Creates specialized processors for analytics tracking
 
-## Analytics Engine
+## Analytics engine
 ___
 The Analytics Engine is a system that allows tracking and analyzing operations and state changes on Document Models. Features include:
 - Custom dashboard and report generation

package/docs/academy/02-MasteryTrack/01-BuilderEnvironment/_category_.json

@@ -1,5 +1,5 @@
 {
-    "label": "Builder Environment",
+    "label": "Builder environment",
     "link": {
       "type": "doc",
       "id": "academy/MasteryTrack/BuilderEnvironment/Prerequisites"

package/docs/academy/02-MasteryTrack/02-DocumentModelCreation/01-WhatIsADocumentModel.md

@@ -1,7 +1,7 @@
-# What is a Document Model?
+# What is a document model?
 
 :::tip
-This chapter on **Document Model Creation** will help you with an in depth practicial understanding while building an **advanced ToDoList** document model. 
+This chapter on **Document Model Creation** will help you with an in depth practicial understanding while building an **advanced to-do list** document model. 
 Although not required, if you have completed the 'Get Started' tutorial you will revisit familiar topics and can update your existing document model.
 :::
 
@@ -19,7 +19,7 @@ A Document Model can be understood as:
 
 ### **How does a document model function?**
 
-#### **Structure and Composition**
+#### **Structure and composition**
 
 Each document model consists of three key components:
 
@@ -31,11 +31,11 @@ Document models leverage **event sourcing, CQRS (Command Query Responsibility Se
 
 ---
 
-## **1. Structure of a Document Model**
+## **1. Structure of a document model**
 
 A document model consists of the following key components:
 
-### **1.1 State Schema**
+### **1.1 State schema**
 
 The **state schema** defines the structure of the document, including its fields and data types. It serves as a blueprint for how data is stored and validated.
 
@@ -60,7 +60,7 @@ type LineItem {
 }
 ```
 
-### **State Schema Features:**
+### **State schema features:**
 
 - Uses **GraphQL-like definitions** for a **clear, structured schema**.
 - Supports **custom scalar types** like `OID`, `Currency`, and `DateTime`. Or other Web3 specific scalars
@@ -70,7 +70,7 @@ The state schema acts as a **template** for document instances. Every new invoic
 
 ---
 
-### **1.2 Document Operations**
+### **1.2 Document operations**
 
 Document models are **append-only**, meaning changes are not made directly to the document state. Instead, **document operations** define valid state transitions.
 
@@ -99,7 +99,7 @@ Instead, a new event is appended to the document history.
 
 ---
 
-### **1.3 Event History (Append-Only Log)**
+### **1.3 Event history (append-only log)**
 
 Every operation applied to a document is **stored as an event** in an append-only log.
 
@@ -112,7 +112,7 @@ Every operation applied to a document is **stored as an event** in an append-onl
   { "timestamp": 1700000200, "operation": "MARK_AS_PAID", "data": {} 
 ```
 
-### **Event History Benefits:**
+### **Event history benefits:**
 
 - Provides a **transparent audit trail** of changes.
 - Enables **time travel debugging** by reconstructing past states.
@@ -120,11 +120,11 @@ Every operation applied to a document is **stored as an event** in an append-onl
 
 ---
 
-## **2. How Document Models Work Technically**
+## **2. How document models work technically**
 
 Document models in Powerhouse rely on **event-driven architecture, event sourcing, and CQRS principles**. Here's a step-by-step breakdown:
 
-### **2.1 Document Creation**
+### **2.1 Document creation**
 
 1. A user (or system) **submits an operation** to create a new document.
 2. The document model **validates** the input data against the state schema.
@@ -142,7 +142,7 @@ Document models in Powerhouse rely on **event-driven architecture, event sourcin
 
 ---
 
-### **2.2 Document Modification**
+### **2.2 Document modification**
 
 1. A user submits an **operation** (e.g., `ADD_LINE_ITEM`).
 2. The **event is appended** to the document history.
@@ -163,7 +163,7 @@ Since changes are **not applied directly**, this model is **highly scalable and
 
 ---
 
-### **2.3 Querying Document Models**
+### **2.3 Querying document models**
 
 Powerhouse uses **GraphQL queries** to fetch document states efficiently. Because documents store structured data, developers can instantly query:
 
@@ -200,6 +200,6 @@ Document Models offer a range of features that can be leveraged to create sophis
 
 Document Models are a powerful primitive within the Powerhouse vision, offering a flexible, structured, and efficient way to manage business logic and data. 
 
-### Up Next: How to build a Document Model
+### Up next: How to build a document model
 
-In the next chapters, we'll teach you how to build a ToDoList document model while explaining all of the theory that is involved.
+In the next chapters, we'll teach you how to build a To-do List document model while explaining all of the theory that is involved.