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

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/pg.md

@@ -2,7 +2,7 @@
 sidebar_position: 3
 ---
 
-# Postgres Store
+# Postgres store
 
 The `PostgresAnalyticsStore` is an `IAnalyticsStore` implementation that leverages a Postgres database. It requires some APIs that do not run in a browser, and is intended for server-side applications.
 
@@ -54,7 +54,7 @@ const store = new PostgresAnalyticsStore({
 
 For more details on these optional constructor parameters, see the [Utilities](#utilities) section.
 
-## Raw Queries
+## Raw queries
 
 Though there is no method on `IAnalyticsStore` for running arbitrary queries, the `PostgresAnalyticsStore` implementation provides a `raw(sql: string)` method. This is used only in development, testing, and [benchmarking](https://github.com/powerhouse-inc/analytics-engine/blob/main/benchmarks/src/wasm.ts) situations and is not intended for production use cases.
 

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/schema.md

@@ -1,4 +1,4 @@
-# Database Schema
+# Database schema
 
 ![untitled](../images/dbs.png)
 *Database table structures for the analytics engine.*

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/typescript/utilities.md

@@ -78,7 +78,7 @@ const result = profiler.recordSync("computeSync", () => {
 });
 ```
 
-### Name Stack
+### Name stack
 
 Often, it is useful to group metrics together. This is accomplished through a metric naming stack, which takes the form: `[Namespace].[... Stack Values].[Metric Name]`. This allows systems to pass down a profiler instance, and compose results.
 

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/use-cases/index.md

@@ -2,6 +2,6 @@
 sidebar_position: 4
 ---
 
-# Use Cases
+# Use cases
 
 This section covers various real-world use cases.

package/docs/academy/02-MasteryTrack/04-WorkWithData/06-Analytics Engine/use-cases/maker.md

@@ -1,4 +1,4 @@
-# Sky Dashboard
+# Sky dashboard
 
 All consumable data for the Sky ecosystem is available through GraphQL API, which allows you to only fetch the data you require.
 
@@ -6,7 +6,7 @@ The API is available in two environments, a developer environment (DEV) and a pr
 
 Both environments are available through Apollo Studio Explorer where the user can find the analytics query and start fetching information from the analytics engine.
 
-### Available Metrics
+### Available metrics
 
 To see which metrics are available to fetch analytics data, use the below query:
 
@@ -87,7 +87,7 @@ The above query will output the following list, which is described in the dropdo
 
 </details>
 
-### Available Dimensions
+### Available dimensions
 
 To see the available dimensions use the query below:
 
@@ -292,7 +292,7 @@ This query will return budget data in MKR for the specified time frame and dimen
 
 By appropriately specifying the currency in your queries, you can tailor the financial analysis to suit the specific needs of your investigation, whether it be transactional stability with DAI or governance dynamics with MKR.
 
-### Examples of Filter Configurations
+### Examples of filter configurations
 
 1. Analyzing MKR Budgets for a Specific Period:
 
@@ -341,7 +341,7 @@ This filter setup is designed to provide an annual overview of actuals and forec
 
 These examples demonstrate how to construct a complete filter object for different types of financial analysis. By properly defining each parameter, users can ensure accurate and relevant data retrieval from the analytics engine.
 
-### Multicurrency Series
+### Multicurrency series
 
 #### Overview
 
@@ -394,7 +394,7 @@ In the future, there could become more metrics available for different purposes,
 
 4. Data Retrieval: The converted data is then retrieved as part of the analytics query, allowing users to analyze financials directly in the currency of their choice.
 
-#### Query Structure
+#### Query structure
 
 The query structure for fetching multicurrency data is similar to the standard analytics query, with the addition of the `multicurrencySeries` field and relevant subfields for specifying the conversion criteria.
 
@@ -447,13 +447,13 @@ query MultiCurrencySeries($filter: MultiCurrencyConversions) {
 
 ```
 
-**Example Use Case**
+#### Example use case
 
 - **Budget Analysis in Different Currencies**: A user can analyze the MakerDAO budget in both MKR and DAI, viewing how the budget figures translate between the governance token and the stablecoin. This can be particularly useful for reports that need to present financial data in a currency that is more widely used or understood by the audience.
 
-#### Writing Queries
+#### Writing queries
 
-Writing queries in the analytics engine involves constructing structured requests to retrieve specific data. Here’s a step-by-step guide to help you write a basic query.
+Writing queries in the analytics engine involves constructing structured requests to retrieve specific data. Here's a step-by-step guide to help you write a basic query.
 
 **Step 1: Understand Your Data Requirements**
 
@@ -465,7 +465,7 @@ Access the analytics engine through a GraphQL interface, like Apollo Studio or a
 
 **Step 3: Start with the Query Structure**
 
-Every query begins with the keyword query, followed by an optional name, and the main query field. In our case, it’s `Analytics`:
+Every query begins with the keyword query, followed by an optional name, and the main query field. In our case, it's `Analytics`:
 
 ```graphql
 query MyAnalyticsQuery {
@@ -535,7 +535,7 @@ query MyAnalyticsQuery($filter: AnalyticsFilter) {
 
 **Step 6: Execute the Query**
 
-Once you have constructed the query, execute it in your GraphQL interface. Ensure that the filter object is passed correctly as a variable. In most interfaces, there’s a separate section or panel where you can define these variables.
+Once you have constructed the query, execute it in your GraphQL interface. Ensure that the filter object is passed correctly as a variable. In most interfaces, there's a separate section or panel where you can define these variables.
 
 **Step 7: Review the Results**
 
@@ -547,7 +547,7 @@ Query writing is often an iterative process. Based on the initial results, you m
 
 By following these steps, you can effectively write and execute queries in the analytics engine, tailoring the data retrieval to your specific analytical needs.
 
-### Query Examples
+### Query examples
 
 Example 1: Fetching Total MakerDAO Actual Expenses and Budget for 2023
 

package/docs/academy/02-MasteryTrack/05-Launch/01-IntroductionToPackages.md

@@ -1,10 +1,10 @@
-# Intro to Packages
+# Introduction to packages
 
 Packages of document models are a core structuring mechanism in the Powerhouse framework, allowing developers to group and manage related document models efficiently. These packages serve as modular collections of document definitions, ensuring consistency, scalability, and reusability across different applications.
 
 By packaging document models together, developers can create well-organized, interoperable sets of data structures that capture the specific needs of various operational processes. Whether used for financial operations, governance, or contributor management, these packages streamline development and integration within Powerhouse's decentralized framework.
 
-### Key Features of Packages
+### Key features of packages
 
 - **Modular Structure** – Packages encapsulate related document models, making it easier to manage and deploy them as a cohesive unit.
 - **Standardized Definitions** – Each document model within a package follows Powerhouse's structured schema approach, ensuring consistency in data representation.
@@ -12,7 +12,7 @@ By packaging document models together, developers can create well-organized, int
 - **Dependency Management** – Developers can define dependencies between document models, ensuring proper relationships and data flows between interconnected components.
 - **Automated Schema Evolution** – Versioning mechanisms allow document models within a package to evolve over time without breaking existing functionality.
 
-### Example Use Cases of Packages
+### Example use cases of packages
 
 - **Finance Package** – A set of document models handling invoices, payments, budgets, and financial reporting. link
 - **Contributor Billing Package** – Defines document models for tracking work, invoicing, and facilitating payments (in both fiat and crypto) for contributors in decentralized organizations. link
@@ -33,9 +33,9 @@ Within a package, you'll find **several key modules**, each serving a distinct r
 
 ---
 
-## **Modules of a Powerhouse Package**
+## Modules of a Powerhouse package
 
-### **1. Document Model**
+### 1. Document model
 
 The **core component** of any package, defining how data is structured and manipulated.
 
@@ -43,14 +43,14 @@ The **core component** of any package, defining how data is structured and manip
 - Serves as the foundation for decentralized workflows.
 - **Example:** An **Invoice** document model might define fields like `issuer`, `recipient`, `amount`, and operations like `ADD_LINE_ITEM` or `MARK_AS_PAID`.
 
-### **2. Document Model Editor**
+### 2. Document model editor
 
 A **UI component** that allows users to **interact with document models visually**.
 
 - Enables users to **create, modify, and manage** documents without coding.
 - Supports multiple editors for a single document model, offering different **UI experiences** tailored to specific roles.
 
-### **3. Scripts**
+### 3. Scripts
 
 **Automated actions** that run on demand or on a schedule.
 
@@ -58,7 +58,7 @@ A **UI component** that allows users to **interact with document models visually
 - Not continuously running—activated manually or at predefined intervals.
 - **Example:** A script that **generates a weekly financial report** from invoice data.
 
-### **4. Processors**
+### 4. Processors
 
 **Event-driven background tasks** that react to document changes.
 
@@ -66,7 +66,7 @@ A **UI component** that allows users to **interact with document models visually
 - Supports real-time **data updates, analytics, and workflow automation**.
 - **Example:** A processor that **monitors new invoices** and updates an **analytics dashboard** in real-time.
 
-### **5. Drive-Apps**
+### 5. Drive-apps
 
 **Custom interfaces** that provide enhanced ways to interact with a package's document models.
 

package/docs/academy/02-MasteryTrack/05-Launch/02-PublishYourProject.md

@@ -1,4 +1,4 @@
-# Publish Your Package
+# Publish your package
 
 This tutorial is a step by step guide tackling the following topics: 
 1. the process of **building a powerhouse project** 
@@ -116,7 +116,7 @@ These include:
 - `scripts`: A folder containing the scripts you might use.
 - `tests`: A folder containing your unit tests.
 
-### 1.2. Adding Document Models, editors and unit tests
+### 1.2. Adding document models, editors and unit tests
 
 Now that you've set up your directory. 
 Go ahead and add the document models you'd like to add by going through the standard document model building flow:
@@ -203,11 +203,11 @@ If you're publishing a package under a scope (like @your-org/my-package), you mi
 }
 ```
 
-### 2.1 Versioning, Tagging, and Publishing Your Package
+### 2.1 Versioning, tagging, and publishing your package
 
 Before publishing, it's crucial to version your package correctly and tag the release in your Git repository. This helps track changes and allows users to depend on specific versions.
 
-**1. Versioning with PNPM**
+#### 1. Versioning with pnpm
 
 Use the `pnpm version` command to update your package version according to semantic versioning rules (`patch` for bugfixes, `minor` for new features, `major` for breaking changes). This command will:
 - Update the `version` in your `package.json`.
@@ -226,7 +226,7 @@ pnpm version major
 ```
 Take note of the new version tag created (e.g., `v1.0.1`), as you'll need it in the next step.
 
-**2. Pushing Changes to Git**
+#### 2. Pushing changes to Git
 
 Next, push your commits and the new version tag to your remote Git repository:
 
@@ -246,7 +246,7 @@ Alternatively, to push all new local tags (use with caution):
 # git push --tags
 ```
 
-**3. Understanding Git Tags vs. NPM Distributor Tags**
+#### 3. Understanding Git tags vs. npm distributor tags
 
 It's important to distinguish between Git tags and NPM distributor tags (dist-tags):
 
@@ -256,7 +256,7 @@ It's important to distinguish between Git tags and NPM distributor tags (dist-ta
     -   `beta`, `next`, `alpha`: Often used for pre-release versions.
     When you publish a package without specifying an NPM tag, it usually gets the `latest` tag by default.
 
-**4. Publishing to NPM**
+#### 4. Publishing to npm
 
 Now you are ready to publish your package to the NPM registry. Ensure you are logged into NPM (the `npm login` command shown in previous steps should be used, or `pnpm login` which is an alias).
 
@@ -279,7 +279,7 @@ This is useful for testing releases before making them `latest`.
 
 Now let's verify that the package(s) get published in the package repository, next to pre-existing packages that you might have been publishing before.
 
-## 3. Deploying the host apps & project.
+## 3. Deploying the host apps and project
 Now that we've installed all the necessary services on our server instance, we can start deploying the host apps & our packaged project from npm.
 
 Install your project package we've published earlier on your local connect (`ph connect`) instance by running the following command:

package/docs/academy/02-MasteryTrack/05-Launch/03-SetupEnvironment.md

@@ -1,4 +1,4 @@
-# Environment Setup Guide
+# Environment setup guide
 
 ## Introduction
 Powerhouse is a powerful platform that helps you manage and deploy your applications efficiently.   
@@ -19,16 +19,16 @@ This tutorial will guide you through the process of creating a new virtual priva
 
 **Current Date:** May 15, 2024
 
-## Part 1: Setting Up Your DigitalOcean Droplet
+## Part 1: Setting up your DigitalOcean droplet
 
 A Droplet is a scalable virtual machine that you can configure to host your websites, applications, or other services.
 
-### Step 1: Sign Up or Log In to DigitalOcean
+### Step 1: Sign up or log in to DigitalOcean
 
 - If you don't have an account, go to [digitalocean.com](https://digitalocean.com) and sign up. You'll likely need to provide payment information.
 - If you already have an account, log in.
 
-### Step 2: Create a New Droplet
+### Step 2: Create a new droplet
 
 1. From your DigitalOcean dashboard, click the green "Create" button in the top right corner and select "Droplets".
 
@@ -62,7 +62,7 @@ A Droplet is a scalable virtual machine that you can configure to host your webs
    - Select Project: Assign the Droplet to a project.
    - Review your selections and click the "Create Droplet" button at the bottom.
 
-### Step 3: Access Your Droplet
+### Step 3: Access your droplet
 
 It will take a minute or two for your Droplet to be provisioned. Once it's ready, its IP address will be displayed in your Droplets list.
 
@@ -86,9 +86,9 @@ To log in via SSH:
 
 Now your Droplet is running! Now you can continue with the Powerhouse tutorial or any next steps.
 
-### DNS Configuration
+### DNS configuration
 
-#### Option A: Using DigitalOcean's Nameservers (Recommended)
+#### Option A: Using DigitalOcean's nameservers (recommended)
 
 1. **Add Your Domain to DigitalOcean:**
    - Go to "Networking" → "Domains"
@@ -129,7 +129,7 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
      - **WILL DIRECT TO:** Your Droplet's IP
      - **TTL:** 3600
 
-#### Option B: Using Your Existing Nameservers (NS locked)
+#### Option B: Using your existing nameservers (NS locked)
 
 1. **Just Create DNS Records at Your Registrar:**
    - **Root Domain (A Record):**
@@ -158,7 +158,7 @@ Now your Droplet is running! Now you can continue with the Powerhouse tutorial o
 
 **Note:** DNS changes may take up to 48 hours to propagate globally.
 
-### Verify Configuration
+### Verify configuration
 
 1. Use DNS lookup tools to verify your records:
    ```bash
@@ -202,9 +202,9 @@ This tutorial will guide you through the process of assigning a static IP (Elast
    :::
 
 
-## Part 1: Assigning a Static IP to EC2 Instance
+## Part 1: Assigning a static IP to EC2 instance
 
-### Step 1: Allocate Elastic IP
+### Step 1: Allocate elastic IP
 
 1. Navigate to the EC2 service in the AWS console
 2. Choose "Elastic IPs" from the navigation pane
@@ -212,7 +212,7 @@ This tutorial will guide you through the process of assigning a static IP (Elast
 4. Select the VPC where your EC2 instance is located
 5. Click "Allocate"
 
-### Step 2: Associate Elastic IP
+### Step 2: Associate elastic IP
 
 1. Go back to the EC2 console and select your instance
 2. From the "Networking" tab, expand "Network interfaces"
@@ -221,9 +221,9 @@ This tutorial will guide you through the process of assigning a static IP (Elast
 5. Choose "Actions", then "Manage IP Addresses"
 6. Find the Elastic IP you allocated and click "Associate"
 
-## Part 2: DNS Configuration
+## Part 2: DNS configuration
 
-### Option A: Using AWS Route 53 (Recommended)
+### Option A: Using AWS Route 53 (recommended)
 
 1. **Add Your Domain to Route 53:**
    - Go to Route 53 → "Hosted zones"
@@ -267,7 +267,7 @@ This tutorial will guide you through the process of assigning a static IP (Elast
      - **VALUE:** Your Elastic IP
      - **TTL:** 3600
 
-### Option B: Using Your Existing Nameservers
+### Option B: Using your existing nameservers
 
 1. **Create DNS Records at Your Registrar:**
    - **Root Domain (A Record):**
@@ -299,7 +299,7 @@ This tutorial will guide you through the process of assigning a static IP (Elast
    - Point them to your EC2 instance's public IP address
    - Wait for DNS propagation before requesting SSL certificates
 
-### Verify Configuration
+### Verify configuration
 
 1. Use DNS lookup tools to verify your records:
    ```bash
@@ -343,7 +343,7 @@ The `install` script provides a streamlined way to install the Powerhouse CLI to
 
 Up next is the configurations of your services. 
 
-### Service Configuration
+### Service configuration
 
 Next, run 
 ```bash
@@ -362,26 +362,26 @@ PM2 is configured to automatically restart services if they crash and to start t
 
 The setup command will prompt you for the following information:
 
-#### Package Installation
+#### Package installation
 During this phase, you can enter package names that you want to install. For example, you might want to `ph install @powerhousedao/todo-demo-package` or other Powerhouse packages. This step is crucial for adding the specific functionality you need. You can also press Enter to skip this step and install packages later using the `ph install` command.
 
-#### Database Configuration
+#### Database configuration
 The script offers two options for database configuration:
 *   **Option 1: Local Database** Sets up a local PostgreSQL database, which is ideal for development or small deployments. It automatically creates a database user with a secure random password and configures the database to accept local connections. This option is perfect for getting started quickly.
 *   **Option 2: Remote Database** Allows you to connect to a remote PostgreSQL database by providing a connection URL in the format `postgres://user:password@host:port/db`. This is recommended for production environments.
 
-#### SSL Configuration
+#### SSL configuration
 For SSL configuration, you have two choices:
 *   **Option 1: Let's Encrypt (Recommended for Production)** This option requires you to provide a base domain (e.g., `powerhouse.xyz`) and subdomains for your services. The script will automatically obtain and configure SSL certificates for your domains.
 *   **Option 2: Self-signed Certificate** This is suitable for development or testing. It uses your machine's hostname and generates a self-signed certificate. Browsers will show security warnings with this option.
 
-#### Domain Setup
+#### Domain setup
 You will be asked to enter your `connect` and `switchboard` subdomains to complete the setup. If you need more information, revisit the cloud provider setup sections at the beginning of this guide.
 
-#### Security Features
+#### Security features
 Security is a top priority. The script implements automatic SSL certificate management, generates secure database passwords, and configures security headers in Nginx, and sets up proper proxy settings to support WebSocket connections securely.
 
-## 2. Verifying the Setup
+## 2. Verifying the setup
 
 After the installation is complete, it's important to verify that everything is working correctly. You can check the status of your services using PM2, verify the Nginx configuration, and ensure your SSL certificates are properly installed. This step is crucial for identifying any potential issues before they affect your users.
 
@@ -406,16 +406,16 @@ sudo nginx -t
 sudo certbot certificates  # if using Let's Encrypt
 ```
 
-## 3. Accessing the Services
+## 3. Accessing the services
 
 Once everything is set up, you can access your services through the configured domains.   
 If you chose Let's Encrypt, your services will be available at their respective subdomains. With a self-signed certificate, you'll access the services through your machine's hostname with the appropriate base paths. The services are configured to use HTTPS by default, ensuring secure communication.
 
-### With Let's Encrypt:
+### With Let's Encrypt
 - Connect: `https://connect.yourdomain.com`
 - Switchboard: `https://switchboard.yourdomain.com`
 
-### With Self-signed Certificate:
+### With self-signed certificate
 - Connect: `https://your-hostname/connect`
 - Switchboard: `https://your-hostname/switchboard`
 
@@ -426,7 +426,7 @@ When issues arise, there are several common problems you might encounter.
 - Nginx configuration errors can be investigated through the error logs, and service issues can be diagnosed using PM2 logs. 
 - SSL certificate problems often relate to DNS settings or certificate paths. Understanding these common issues and their solutions will help you maintain a stable Powerhouse installation.
 
-### Common Issues:
+### Common issues
 1. **"`ph`: command not found"**
    - Run `source ~/.bashrc` or restart your terminal
    - Verify that the `PNPM_HOME` environment variable is set correctly
@@ -451,22 +451,22 @@ When issues arise, there are several common problems you might encounter.
 
 Regular maintenance is crucial for keeping your Powerhouse installation running smoothly. You can update services using the Powerhouse CLI, restart services through PM2, and monitor logs to ensure everything is functioning correctly. Regular maintenance helps prevent issues and ensures that your services are running with the latest security patches and features.
 
-### Updating Services:
+### Updating services
 ```bash
 ph update <package-name>
 ```
 
-### Restarting Services:
+### Restarting services
 ```bash
 ph service restart
 ```
 
-### Checking Service Status and Logs:
+### Checking service status and logs
 ```bash
 ph service status
 ```
 
-## 6. Security Notes
+## 6. Security notes
 
 Maintaining security is an ongoing process. It's essential to keep your database credentials secure and regularly update your SSL certificates. Regular monitoring of system logs helps identify potential security issues, and keeping your system and packages updated ensures you have the latest security patches. Consider implementing additional security measures such as firewall rules, intrusion detection systems, and regular security audits.
 
@@ -474,17 +474,17 @@ Maintaining security is an ongoing process. It's essential to keep your database
 
 Regular backups are crucial for data safety. The database can be backed up using pg_dump, and your configuration files can be archived using tar. These backups should be stored securely and tested regularly to ensure they can be restored if needed. Consider implementing an automated backup schedule and storing backups in multiple locations for redundancy.
 
-### Database Backup:
+### Database backup
 ```bash
 pg_dump -U powerhouse -d powerhouse > backup.sql
 ```
 
-### Configuration Backup:
+### Configuration backup
 ```bash
 sudo tar -czf powerhouse-config.tar.gz /etc/powerhouse/
 ```
 
-## 8. Best Practices
+## 8. Best practices
 
 To get the most out of your Powerhouse installation, follow these best practices:
 
@@ -494,7 +494,7 @@ To get the most out of your Powerhouse installation, follow these best practices
 4. **Testing**: Test your backup and restore procedures regularly.
 5. **Security**: Regularly review and update your security measures.
 
-## 9. Getting Help
+## 9. Getting help
 
 If you encounter issues or need assistance, there are several resources available:
 

package/docs/academy/02-MasteryTrack/05-Launch/04-ConfigureEnvironment.md

@@ -1,4 +1,4 @@
-# Configure Your Environment
+# Configure your environment
 
 After successfully setting up your server and installing the Powerhouse services using the `ph service setup` command as described in the [Setup Environment](./03-SetupEnvironment.md) guide, the next crucial step is to configure your environment. Proper configuration ensures that your Powerhouse Connect and Switchboard instances behave exactly as you need them to for your specific application.
 
@@ -13,11 +13,11 @@ A key principle to remember is that **environment variables will always override
 
 This guide will walk you through both methods and provide details on common configuration options, including setting up authorization.
 
-## Using Environment Variables
+## Using environment variables
 
 The most common way to configure Powerhouse services is through environment variables. You can place these variables in a `.env` file at the root of your project directory. When you run `ph service start` or `ph service restart`, these variables are loaded into the environment of your running services.
 
-### How to Create and Edit Your `.env` File
+### How to create and edit your .env file
 
 If you're on your cloud server, you can create and edit the `.env` file directly:
 
@@ -38,7 +38,7 @@ If you're on your cloud server, you can create and edit the `.env` file directly
     ph service restart
     ```
 
-### Common Environment Variables for Connect
+### Common environment variables for Connect
 
 The Powerhouse Connect application has a wide range of available environment variables to toggle features and change its behavior. Below is a list of some variables you can configure.
 
@@ -102,17 +102,17 @@ SENTRY_RELEASE=""
 ```
 You can find the most up-to-date list of variables in the source repository: [https://github.com/powerhouse-inc/powerhouse/blob/main/apps/connect/.env](https://github.com/powerhouse-inc/powerhouse/blob/main/apps/connect/.env)
 
-## Using a Configuration File
+## Using a configuration file
 
 For services like the Switchboard, you can also use a `powerhouse.config.json` file for more structured configuration, especially for features like authorization.
 
-### Configuring Authorization
+### Configuring authorization
 
 A critical aspect of your environment configuration is setting up authorization to control who can access your services and what they can do. As detailed in our dedicated [Switchboard Authorization](/academy/MasteryTrack/BuildingUserExperiences/Authorization/Authorization) guide, you can manage access using a role-based system.
 
 Here's a quick overview of how you can configure authorization:
 
-#### Via Environment Variables
+#### Via environment variables
 
 You can set the roles directly in your `.env` file. This is quick and easy for simple allowlists.
 
@@ -151,7 +151,7 @@ Remember, if you define `AUTH_ENABLED=false` as an environment variable, it will
 
 For a complete understanding of how roles (Guest, User, Admin) work and the permissions they have, please refer to the full [Authorization guide](/academy/MasteryTrack/BuildingUserExperiences/Authorization/Authorization).
 
-## Applying Your Changes
+## Applying your changes
 
 Regardless of which method you use to update your configuration, the changes will not be applied until you restart your services.
 

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

@@ -1,5 +1,5 @@
 {
-    "label": "Mastery Track",
+    "label": "Mastery track",
     "link": {
       "type": "generated-index",
       "description": "A set of tutorials that support the creation of more complex Powerhouse documents, drive apps and packages."

package/docs/academy/03-ExampleUsecases/Chatroom/03-DefineChatroomDocumentModel.md

@@ -1,11 +1,11 @@
-# Define the Chatroom Document Model
+# Define the chatroom document model
 
 In this tutorial, you will learn how to design your document model and export it to be later used in your Powerhouse project.
 If you don't have a document model created yet, have a look at the previous steps of this tutorial to create a new document model.
 
 Before you start, make sure you have the Connect application running.
 
-## Chatroom Document Model Schema
+## Chatroom document model schema
 
 We use GraphQL Schema Definition Language (SDL) to define the document model schema. Below, you can see the SDL for the `ChatRoom` document model.
 
@@ -13,7 +13,7 @@ We use GraphQL Schema Definition Language (SDL) to define the document model sch
 This schema contains the data structure of the document model and the basic operations that can be performed on the document model. For more in depth information please visit [State Schema](/academy/MasteryTrack/DocumentModelCreation/SpecifyTheStateSchema)
 :::
 
-## State Schema (See next steps)
+## State schema (See next steps)
 
 ```graphql
 # Defines a GraphQL type for the state of the chatroom document
@@ -58,7 +58,7 @@ enum ReactionType {
 }
 ```
 
-## Operations Schema (See next steps)
+## Operations schema (See next steps)
 
 ```graphql
 # add_message
@@ -91,7 +91,7 @@ input EditChatDescriptionInput {
 }
 ```
 
-## Define the Document Model
+## Define the document model
 
 To be able to define the document model, you need to open the Chatroom document model editor in Connect.