fixes prettier and cspell errors

Author: ZPain8464

content/docs/courses.mdx

@@ -14,4 +14,3 @@ In the span of 10 guides, we'll cover routing, policies, TLS certificates, ident
 To get started, complete the [**Quickstart guide**](/docs/quickstart) first.
 
 When you're finished, learn how to [**Build Routes**](/docs/courses/zero-fundamentals/build-routes.mdx) in Pomerium Zero.
-

content/docs/courses/zero-fundamentals/advanced-policies.mdx

@@ -42,10 +42,10 @@ If you're following these guides sequentially, your current policy only includes
 <TabItem value="ppl-editor" label="PPL Editor">
 
 ```yaml showLineNumbers
-  allow:
-    and:
-      - domain:
-          is: example.com
+allow:
+  and:
+    - domain:
+        is: example.com
 ```
 
 </TabItem>
@@ -55,7 +55,6 @@ This policy is a great first step to protecting your services. If you're using a
 
 With Pomerium Policy Language (PPL), you can build richer policies that apply to real-world use cases. Let's cover a few example "real-world" policies below that would fall into the "advanced" category.
 
-
 ### Grant access based on the email criterion
 
 You can build an allowlist so that access is only granted to users with a matching email address:
@@ -132,7 +131,6 @@ Taking the policy you just created, you could create an identical policy that so
     </TabItem>
     </Tabs>
 
-
 ### Deny based on day of week, time of day
 
 Lastly, we'll create a new policy that denies access to any user on Saturday, Sunday, or weekdays after 5PM.
@@ -199,4 +197,3 @@ In this way, you can chain together multiple policies to add richer access contr
 Now that you've seen some advanced policies, you should learn about advanced routes.
 
 Go to [**Advanced Routes**](/docs/courses/zero-fundamentals/advanced-routes).
-

content/docs/courses/zero-fundamentals/advanced-routes.mdx

@@ -1,4 +1,6 @@
 ---
+# cSpell:ignore WORKDIR, workdir, nodeserver
+
 id: advanced-routes
 title: Advanced Routes
 sidebar_label: 05. Advanced Routes
@@ -102,16 +104,15 @@ To add JWT claim headers in the Zero Console:
 1. In **Editing Cluster Settings**, select **Headers**
 1. In the **JWT Claim Headers** field, enter the values below:
 
-    | **KEY** | **VALUE** |
-    | :--- | :--- |
-    | `x-pomerium-claim-email` | `email` |
-    | `x-pomerium-claim-user` | `user` |
-    | `x-pomerium-claim-name` | `name` |
-
-    For example:
+   | **KEY**                  | **VALUE** |
+   | :----------------------- | :-------- |
+   | `x-pomerium-claim-email` | `email`   |
+   | `x-pomerium-claim-user`  | `user`    |
+   | `x-pomerium-claim-name`  | `name`    |
 
-    ![Entering custom JWT claim headers in the Zero Console](./img/advanced-routes/jwt-claim-headers.png)
+   For example:
 
+   ![Entering custom JWT claim headers in the Zero Console](./img/advanced-routes/jwt-claim-headers.png)
 
 After you save your changes, apply your changeset, and access your HTTPBin route, inspect the request. You'll see these additional, unsigned HTTP headers added to the response body:
 
@@ -125,11 +126,11 @@ Now, configure [**Set Request Headers**](/docs/reference/routes/headers#set-requ
 1. In **Property Name**, enter `X-SET-REQUEST-HEADERS`
 1. In **Property Value**, enter `X-TEST-VALUE`
 
-    Next, configure [**Remove Request Headers**](/docs/reference/routes/headers#remove-request-headers) to remove two of the JWT claim headers you set in the previous section.
+   Next, configure [**Remove Request Headers**](/docs/reference/routes/headers#remove-request-headers) to remove two of the JWT claim headers you set in the previous section.
 
 1. In the **Remove Request Headers** field, enter `X-POMERIUM-CLAIM-NAME` and `X-POMERIUM-CLAIM-USER`.
 
-    ![Setting and removing HTTP request headers in the Zero Console](./img/advanced-routes/set-and-remove-request-headers.png)
+   ![Setting and removing HTTP request headers in the Zero Console](./img/advanced-routes/set-and-remove-request-headers.png)
 
 Apply your changeset and test the request again. You'll notice that the request header was added to the request, and the specified JWT claim headers were removed:
 
@@ -159,8 +160,7 @@ TODO
 
 ### Direct Response
 
-TODO
-You can configure Pomerium to send a small, static HTTP response to the downstream client for a managed route.
+TODO You can configure Pomerium to send a small, static HTTP response to the downstream client for a managed route.
 
 ## Test prefix and path settings
 
@@ -326,14 +326,14 @@ services:
     networks:
       main:
         aliases:
-        - verify.<CLUSTER_SUBDOMAIN>.pomerium.app
-        - authenticate.<CLUSTER_SUBDOMAIN>.pomerium.app
+          - verify.<CLUSTER_SUBDOMAIN>.pomerium.app
+          - authenticate.<CLUSTER_SUBDOMAIN>.pomerium.app
   verify:
     image: cr.pomerium.com/pomerium/verify:latest
     networks:
       main:
         aliases:
-        - verify
+          - verify
   grafana:
     image: grafana/grafana:latest
     ports:

content/docs/courses/zero-fundamentals/build-policies.mdx

@@ -13,7 +13,8 @@ This guide shows you how to build **Authorization Policies** in Pomerium Zero. W
   height="500"
   src="https://www.youtube.com/embed/lRpkd20psbk?si=IZj3kIV-t7gbVui5"
   title="YouTube video player"
-  frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+  frameborder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
   referrerpolicy="strict-origin-when-cross-origin"
   allowfullscreen></iframe>
 
@@ -82,7 +83,6 @@ You can view a policy formatted in YAML using the **PPL Editor** tab:
 
 :::
 
-
 **Example 2**: Allow access based on the domain criterion
 
 Requiring an exact email address is one way to secure an app, but it won't let anyone else in without that specific email address. This obviously won't scale for an organization where multiple members may require access to the same service.
@@ -130,5 +130,3 @@ If you built your policy correctly, Pomerium should only grant you access if you
 Next, you'll learn how to secure your upstream service by verifying the user's identity with a JWT. This adds another layer of security to your application.
 
 Go to [**Single Sign-on**](/docs/courses/zero-fundamentals/single-sign-on).
-
-

content/docs/courses/zero-fundamentals/build-routes.mdx

@@ -32,7 +32,7 @@ In Pomerium, **Routing** makes it possible for the Proxy service to manage reque
 
 To route requests and responses to the correct locations, the Proxy service requires two sets of routing instructions:
 
-- The **From** URL. This URL defines the external, publically accessible URL of a proxied request. It tells the Proxy service to listen for requests from this location.
+- The **From** URL. This URL defines the external, publicly accessible URL of a proxied request. It tells the Proxy service to listen for requests from this location.
 - The **To** URL. This URL defines the destination of the proxied request, or where the Proxy service should direct the origin server's response. It can be an internal or external resource.
 
 ## How to build routes in Pomerium Zero
@@ -48,14 +48,14 @@ To learn how to build routes, you'll follow these steps:
 The service you'll secure is [Grafana](https://grafana.com/), an open-source observability platform. In the same `docker-compose.yaml` file where you're running Pomerium Zero, add the Grafana configuration below:
 
 ```yaml
-  grafana:
-    image: grafana/grafana:latest
-    ports:
-      - 3000:3000
-    networks:
-      main: {}
-    volumes:
-      - ./grafana-storage:/var/lib/grafana
+grafana:
+  image: grafana/grafana:latest
+  ports:
+    - 3000:3000
+  networks:
+    main: {}
+  volumes:
+    - ./grafana-storage:/var/lib/grafana
 ```
 
 ### Build a route
@@ -66,12 +66,13 @@ In the Zero Console:
 
 1. In the **From** field, select **https://** from the protocol dropdown. In the next field, enter the external URL. It should follow this format:
 
-    `grafana.<CLUSTER_STARTER_DOMAIN>.pomerium.app`
+   `grafana.<CLUSTER_STARTER_DOMAIN>.pomerium.app`
+
 1. In the **To** field, enter the destination URL: `http://grafana:3000`
 
 1. In the **Policies** field, select **Any Authenticated User**.
 
-    ![Building your first route in the Zero Console](./img/routes/pz-courses-first-route.png)
+   ![Building your first route in the Zero Console](./img/routes/pz-courses-first-route.png)
 
 Save your route and **apply the changeset**.
 
@@ -89,7 +90,6 @@ Great job! You successfully built a route in Pomerium Zero. Next, you'll learn h
 
 Go to [Build Policies](/docs/courses/zero-fundamentals/build-policies).
 
-
 #### Configuration file state
 
 At this point, your Docker Compose file should look like this:
@@ -109,13 +109,13 @@ services:
     networks:
       main:
         aliases:
-        - verify.<YOUR_CLUSTER_SUBDOMAIN>.pomerium.app
+          - verify.<YOUR_CLUSTER_SUBDOMAIN>.pomerium.app
   verify:
     image: cr.pomerium.com/pomerium/verify:latest
     networks:
       main:
         aliases:
-        - verify
+          - verify
   grafana:
     image: grafana/grafana:latest
     ports:
@@ -131,4 +131,3 @@ networks:
 volumes:
   pomerium-cache:
 ```
-

content/docs/courses/zero-fundamentals/certificates.mdx

@@ -4,4 +4,3 @@ title: Certificates
 sidebar_label: 07. Certificates
 sidebar_position: 7
 ---
-

content/docs/courses/zero-fundamentals/single-sign-on.mdx

@@ -1,4 +1,6 @@
 ---
+# cSpell:ignore webkitallowfullscreen, mozallowfullscreen
+
 id: single-sign-on
 title: Single Sign On
 sidebar_label: 03. Single Sign-on with JWTs
@@ -18,8 +20,7 @@ Watch the video for a quick walkthrough or read the guide below for step-by-step
   height="500"
   webkitallowfullscreen
   mozallowfullscreen
-  allowfullscreen>
-</iframe>
+  allowfullscreen></iframe>
 
 :::note **Before you start**
 
@@ -93,7 +94,7 @@ In the Zero Console:
 1. Select the **Headers** tab
 1. Apply the **Pass Identity Headers** setting
 
-    ![Apply the route-level pass identity headers setting in the Zero Console](./img/sso/pz-courses-apply-pass-id-headers.gif)
+   ![Apply the route-level pass identity headers setting in the Zero Console](./img/sso/pz-courses-apply-pass-id-headers.gif)
 
 :::info
 
@@ -106,24 +107,25 @@ The [**Pass Identity Headers**](/docs/reference/routes/pass-identity-headers-per
 In your Docker Compose file, add the following environment variables to your Grafana service:
 
 ```yaml title="docker-compose.yaml" {8-15} showLineNumbers
-  grafana:
-    image: grafana/grafana:latest
-    ports:
-      - 3000:3000
-    networks:
-      main: {}
-    environment:
-      - GF_AUTH_SIGNOUT_REDIRECT_URL=https://grafana.<CLUSTER_SUBDOMAIN>.pomerium.app/.pomerium/sign_out
-      - GF_AUTH_JWT_ENABLED=true
-      - GF_AUTH_JWT_HEADER_NAME=X-Pomerium-Jwt-Assertion
-      - GF_AUTH_JWT_EMAIL_CLAIM=email
-      - GF_AUTH_JWT_USERNAME_CLAIM=sub
-      - GF_AUTH_JWT_JWK_SET_URL=https://authenticate.<CLUSTER_SUBDOMAIN>.pomerium.app/.well-known/pomerium/jwks.json
-      - GF_AUTH_JWT_CACHE_TTL=60m
-      - GF_AUTH_JWT_AUTO_SIGN_UP=true
-    volumes:
-      - ./grafana-storage:/var/lib/grafana
+grafana:
+  image: grafana/grafana:latest
+  ports:
+    - 3000:3000
+  networks:
+    main: {}
+  environment:
+    - GF_AUTH_SIGNOUT_REDIRECT_URL=https://grafana.<CLUSTER_SUBDOMAIN>.pomerium.app/.pomerium/sign_out
+    - GF_AUTH_JWT_ENABLED=true
+    - GF_AUTH_JWT_HEADER_NAME=X-Pomerium-Jwt-Assertion
+    - GF_AUTH_JWT_EMAIL_CLAIM=email
+    - GF_AUTH_JWT_USERNAME_CLAIM=sub
+    - GF_AUTH_JWT_JWK_SET_URL=https://authenticate.<CLUSTER_SUBDOMAIN>.pomerium.app/.well-known/pomerium/jwks.json
+    - GF_AUTH_JWT_CACHE_TTL=60m
+    - GF_AUTH_JWT_AUTO_SIGN_UP=true
+  volumes:
+    - ./grafana-storage:/var/lib/grafana
 ```
+
 > See Grafana's [Configure JWT authentication](https://grafana.com/docs/grafana/latest/setup-grafana/configure-security/configure-authentication/jwt/) docs for more information about these settings.
 
 :::note
@@ -191,7 +193,6 @@ Great job! You successfully configured SSO in Pomerium. Next, you'll learn how t
 
 Go to [**Build Advanced Policies**](/docs/courses/zero-fundamentals/advanced-policies).
 
-
 #### Configuration file state
 
 At this point, your Docker Compose file should look like this:
@@ -211,14 +212,14 @@ services:
     networks:
       main:
         aliases:
-        - verify.<CLUSTER_SUBDOMAIN>.pomerium.app
-        - authenticate.<CLUSTER_SUBDOMAIN>.pomerium.app
+          - verify.<CLUSTER_SUBDOMAIN>.pomerium.app
+          - authenticate.<CLUSTER_SUBDOMAIN>.pomerium.app
   verify:
     image: cr.pomerium.com/pomerium/verify:latest
     networks:
       main:
         aliases:
-        - verify
+          - verify
   grafana:
     image: grafana/grafana:latest
     ports:

content/docs/courses/zero-fundamentals/tcp-routes.mdx

@@ -1,4 +1,6 @@
 ---
+# cSpell:ignore myssh, linuxkit, aarch, epoll, atomicvar,
+
 id: tcp-routes
 title: TCP Routes
 sidebar_label: 06. TCP Routes
@@ -72,23 +74,23 @@ Use "pomerium-cli [command] --help" for more information about a command.
 Add the Redis and OpenSSH server configurations to your Docker Compose file:
 
 ```yaml
-  redis:
-    image: redis:latest
-    networks:
-      main: {}
-    expose:
-      - 6379
-
-  myssh:
-    image: linuxserver/openssh-server:latest
-    networks:
-      main: {}
-    expose:
-      - 2222
-    environment:
-      PASSWORD_ACCESS: "true"
-      USER_PASSWORD: supersecret
-      USER_NAME: user
+redis:
+  image: redis:latest
+  networks:
+    main: {}
+  expose:
+    - 6379
+
+myssh:
+  image: linuxserver/openssh-server:latest
+  networks:
+    main: {}
+  expose:
+    - 2222
+  environment:
+    PASSWORD_ACCESS: 'true'
+    USER_PASSWORD: supersecret
+    USER_NAME: user
 ```
 
 ## Add routes in Pomerium Zero
@@ -98,21 +100,21 @@ Create a Redis route:
 1. Create a new route for your Redis database
 1. In **From**, select **tcp+https://** in the protocol dropdown menu
 1. Enter your external route and append `:6379` to it
-    1. For example, `redis.super-hero-7645.pomerium.app:6379`
+   1. For example, `redis.super-hero-7645.pomerium.app:6379`
 1. In **To**, enter `tcp://redis:6379`
 1. In **Policies**, select `Any Authenticated User`
 
-    ![Building the Redis route in the Zero Console](./img/tcp/redis-service.png)
+   ![Building the Redis route in the Zero Console](./img/tcp/redis-service.png)
 
 Create an OpenSSH route:
 
 1. Create a new route for the OpenSSH server
 1. In **From**, select **tcp+https://** in the protocol dropdown menu
 1. Enter your external route and append `:22` to it
-    1. For example, `myssh.super-hero-7645.pomerium.app:22`
+   1. For example, `myssh.super-hero-7645.pomerium.app:22`
 1. In **To**, enter `tcp://myssh:2222`
 
-    ![Building the OpenSSH route in the Zero Console](./img/tcp/ssh-server.png)
+   ![Building the OpenSSH route in the Zero Console](./img/tcp/ssh-server.png)
 
 Save your changes and apply them.