chore: publish documentation after merge

We should not need to publish the documentation on the PR, but rather, after it is merged.

I also changed a few little things in the documentation so that I could test the publish.

.github/workflows/docs.yml

@@ -2,17 +2,15 @@ name: Deploy Documentation
 on:
   push:
     branches:
-      - main
-      - data_further_refactor
-  pull_request:
-    branches:
-      - main
+      - chore-publish_docs
 
 permissions:
   contents: write
 
 jobs:
   deploy:
+    env:
+      GH_TOKEN: ${{ secrets.AUTONOMI_PAT }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -33,4 +31,4 @@ jobs:
         run: |
           git config --global user.name "github-actions"
           git config --global user.email "github-actions@github.com"
-          mkdocs gh-deploy --force 
+          mkdocs gh-deploy --force 

docs/online-documentation/index.md

@@ -1,6 +1,6 @@
 # Autonomi Documentation
 
-Welcome to the Autonomi documentation! This guide will help you get started with using the Autonomi network client.
+Welcome to the Autonomi documentation! This guide will help you get started using the Autonomi network client.
 
 ## What is Autonomi?
 
@@ -13,7 +13,7 @@ Autonomi is a decentralised data and communications platform designed to provide
   - [Data Types](guides/data_types.md) - Understanding the fundamental data structures
   - [Client Modes](guides/client_modes.md) - Different operational modes of the client
   - [Data Storage](guides/data_storage.md) - How data is stored and retrieved
-  - [Local Network Setup](guides/local_network.md) - Setting up a local development environmentv
+  - [Local Network Setup](guides/local_network.md) - Setting up a local development environment
 
 ### API References