diff --git a/.cspell.json b/.cspell.json
index 1e5015f..c438807 100644
--- a/.cspell.json
+++ b/.cspell.json
@@ -97,7 +97,9 @@
     "minimis",
     "Mommy",
     "NAMI",
+    "NCMEC",
     "Nederlands",
+    "Neurodivergence",
     "Nomena",
     "Nymira",
     "OFAC",
diff --git a/package.json b/package.json
index 28c982d..4a432b8 100644
--- a/package.json
+++ b/package.json
@@ -12,16 +12,16 @@
     "test": "vitest --run"
   },
   "dependencies": {
-    "@astrojs/check": "0.9.5",
-    "@astrojs/starlight": "0.36.1",
-    "astro": "5.15.2",
-    "astro-mermaid": "1.1.0",
-    "mermaid": "11.12.1",
+    "@astrojs/check": "0.9.6",
+    "@astrojs/starlight": "0.37.1",
+    "astro": "5.16.5",
+    "astro-mermaid": "1.2.0",
+    "mermaid": "11.12.2",
     "typescript": "5.9.3"
   },
   "devDependencies": {
-    "cspell": "9.2.2",
+    "cspell": "9.4.0",
     "gray-matter": "4.0.3",
-    "vitest": "4.0.5"
+    "vitest": "4.0.15"
   }
 }
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 5c32071..af0ccc4 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -9,33 +9,33 @@ importers:
   .:
     dependencies:
       '@astrojs/check':
-        specifier: 0.9.5
-        version: 0.9.5(typescript@5.9.3)
+        specifier: 0.9.6
+        version: 0.9.6(prettier@3.7.4)(typescript@5.9.3)
       '@astrojs/starlight':
-        specifier: 0.36.1
-        version: 0.36.1(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))
+        specifier: 0.37.1
+        version: 0.37.1(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))
       astro:
-        specifier: 5.15.2
-        version: 5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1)
+        specifier: 5.16.5
+        version: 5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2)
       astro-mermaid:
-        specifier: 1.1.0
-        version: 1.1.0(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))(mermaid@11.12.1)
+        specifier: 1.2.0
+        version: 1.2.0(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))(mermaid@11.12.2)
       mermaid:
-        specifier: 11.12.1
-        version: 11.12.1
+        specifier: 11.12.2
+        version: 11.12.2
       typescript:
         specifier: 5.9.3
         version: 5.9.3
     devDependencies:
       cspell:
-        specifier: 9.2.2
-        version: 9.2.2
+        specifier: 9.4.0
+        version: 9.4.0
       gray-matter:
         specifier: 4.0.3
         version: 4.0.3
       vitest:
-        specifier: 4.0.5
-        version: 4.0.5(@types/debug@4.1.12)(yaml@2.8.1)
+        specifier: 4.0.15
+        version: 4.0.15(yaml@2.8.2)
 
 packages:
 
@@ -45,23 +45,28 @@ packages:
   '@antfu/utils@9.2.0':
     resolution: {integrity: sha512-Oq1d9BGZakE/FyoEtcNeSwM7MpDO2vUBi11RWBZXf75zPsbUVWmUs03EqkRFrcgbXyKTas0BdZWC1wcuSoqSAw==}
 
-  '@astrojs/check@0.9.5':
-    resolution: {integrity: sha512-88vc8n2eJ1Oua74yXSGo/8ABMeypfQPGEzuoAx2awL9Ju8cE6tZ2Rz9jVx5hIExHK5gKVhpxfZj4WXm7e32g1w==}
+  '@anthropic-ai/claude-code@1.0.128':
+    resolution: {integrity: sha512-uUg5cFMJfeQetQzFw76Vpbro6DAXst2Lpu8aoZWRFSoQVYu5ZSAnbBoxaWmW/IgnHSqIIvtMwzCoqmcA9j9rNQ==}
+    engines: {node: '>=18.0.0'}
+    hasBin: true
+
+  '@astrojs/check@0.9.6':
+    resolution: {integrity: sha512-jlaEu5SxvSgmfGIFfNgcn5/f+29H61NJzEMfAZ82Xopr4XBchXB1GVlcJsE+elUlsYSbXlptZLX+JMG3b/wZEA==}
     hasBin: true
     peerDependencies:
       typescript: ^5.0.0
 
-  '@astrojs/compiler@2.10.3':
-    resolution: {integrity: sha512-bL/O7YBxsFt55YHU021oL+xz+B/9HvGNId3F9xURN16aeqDK9juHGktdkCSXz+U4nqFACq6ZFvWomOzhV+zfPw==}
-
   '@astrojs/compiler@2.13.0':
     resolution: {integrity: sha512-mqVORhUJViA28fwHYaWmsXSzLO9osbdZ5ImUfxBarqsYdMlPbqAqGJCxsNzvppp1BEzc1mJNjOVvQqeDN8Vspw==}
 
   '@astrojs/internal-helpers@0.7.4':
     resolution: {integrity: sha512-lDA9MqE8WGi7T/t2BMi+EAXhs4Vcvr94Gqx3q15cFEz8oFZMO4/SFBqYr/UcmNlvW+35alowkVj+w9VhLvs5Cw==}
 
-  '@astrojs/language-server@2.15.4':
-    resolution: {integrity: sha512-JivzASqTPR2bao9BWsSc/woPHH7OGSGc9aMxXL4U6egVTqBycB3ZHdBJPuOCVtcGLrzdWTosAqVPz1BVoxE0+A==}
+  '@astrojs/internal-helpers@0.7.5':
+    resolution: {integrity: sha512-vreGnYSSKhAjFJCWAwe/CNhONvoc5lokxtRoZims+0wa3KbHBdPHSSthJsKxPd8d/aic6lWKpRTYGY/hsgK6EA==}
+
+  '@astrojs/language-server@2.16.2':
+    resolution: {integrity: sha512-J3hVx/mFi3FwEzKf8ExYXQNERogD6RXswtbU+TyrxoXRBiQoBO5ooo7/lRWJ+rlUKUd7+rziMPI9jYB7TRlh0w==}
     hasBin: true
     peerDependencies:
       prettier: ^3.0.0
@@ -72,6 +77,9 @@ packages:
       prettier-plugin-astro:
         optional: true
 
+  '@astrojs/markdown-remark@6.3.10':
+    resolution: {integrity: sha512-kk4HeYR6AcnzC4QV8iSlOfh+N8TZ3MEStxPyenyCtemqn8IpEATBFMTJcfrNW32dgpt6MY3oCkMM/Tv3/I4G3A==}
+
   '@astrojs/markdown-remark@6.3.8':
     resolution: {integrity: sha512-uFNyFWadnULWK2cOw4n0hLKeu+xaVWeuECdP10cQ3K2fkybtTlhb7J7TcScdjmS8Yps7oje9S/ehYMfZrhrgCg==}
 
@@ -88,8 +96,8 @@ packages:
   '@astrojs/sitemap@3.6.0':
     resolution: {integrity: sha512-4aHkvcOZBWJigRmMIAJwRQXBS+ayoP5z40OklTXYXhUDhwusz+DyDl+nSshY6y9DvkVEavwNcFO8FD81iGhXjg==}
 
-  '@astrojs/starlight@0.36.1':
-    resolution: {integrity: sha512-Fmt8mIsAIZN18Y4YQDI6p521GsYGe4hYxh9jWmz0pHBXnS5J7Na3TSXNya4eyIymCcKkuiKFbs7b/knsdGVYPg==}
+  '@astrojs/starlight@0.37.1':
+    resolution: {integrity: sha512-STNsR5PaDoiW4IgcX17Fp42FfyqwuweWPts/EWEMcFPAeg9Nvpu3UvVCorasYrgfJgaJTeydsOV++0ACA1KYDA==}
     peerDependencies:
       astro: ^5.5.0
 
@@ -100,16 +108,16 @@ packages:
   '@astrojs/yaml2ts@0.2.2':
     resolution: {integrity: sha512-GOfvSr5Nqy2z5XiwqTouBBpy5FyI6DEe+/g/Mk5am9SjILN1S5fOEvYK0GuWHg98yS/dobP4m8qyqw/URW35fQ==}
 
-  '@babel/helper-string-parser@7.24.8':
-    resolution: {integrity: sha512-pO9KhhRcuUyGnJWwyEgnRJTSIZHiT+vMD0kPeD+so0l7mxkMT19g3pjY9GTnHySck/hDzq+dtW/4VgnMkippsQ==}
+  '@babel/helper-string-parser@7.27.1':
+    resolution: {integrity: sha512-qMlSxKbpRlAridDExk92nSobyDdpPijUq2DW6oDnUqd0iOGxmQjyqhMIihI9+zv4LPyZdRje2cavWPbCbWm3eA==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/helper-validator-identifier@7.24.7':
-    resolution: {integrity: sha512-rR+PBcQ1SMQDDyF6X0wxtG8QyLCgUB0eRAGguqRLfkCA87l7yAP7ehq8SNj96OOGTO8OBV70KhuFYcIkHXOg0w==}
+  '@babel/helper-validator-identifier@7.28.5':
+    resolution: {integrity: sha512-qSs4ifwzKJSV39ucNjsvc6WVHs6b7S03sOh2OcHF9UHfVPqWWALUsNUVzhSBiItjRZoLHx7nIarVjqKVusUZ1Q==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/parser@7.25.4':
-    resolution: {integrity: sha512-nq+eWrOgdtu3jG5Os4TQP3x3cLA8hR8TvJNjD8vnPa20WGycimcparWnLK4jJhElTK6SDyuJo1weMKO/5LpmLA==}
+  '@babel/parser@7.28.5':
+    resolution: {integrity: sha512-KKBU1VGYR7ORr3At5HAtUQ+TV3SzRCXmA/8OdDZiLDBIZxVyzXuztPjfLd3BV1PRAQGCMWWSHYhL0F8d5uHBDQ==}
     engines: {node: '>=6.0.0'}
     hasBin: true
 
@@ -117,15 +125,15 @@ packages:
     resolution: {integrity: sha512-aA63XwOkcl4xxQa3HjPMqOP6LiK0ZDv3mUPYEFXkpHbaFjtGggE1A61FjFzJnB+p7/oy2gA8E+rcBNl/zC1tMg==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/types@7.25.4':
-    resolution: {integrity: sha512-zQ1ijeeCXVEh+aNL0RlmkPkG8HUiDcU2pzQQFjtbntgAczRASFzj4H+6+bV+dy1ntKR14I/DypeuRG1uma98iQ==}
+  '@babel/types@7.28.5':
+    resolution: {integrity: sha512-qQ5m48eI/MFLQ5PxQj4PFaprjyCTLI37ElWMmNs0K8Lk3dVeOdNpB3ks8jc7yM5CDmVC73eMVk/trk3fgmrUpA==}
     engines: {node: '>=6.9.0'}
 
   '@braintree/sanitize-url@7.1.1':
     resolution: {integrity: sha512-i1L7noDNxtFyL5DmZafWy1wRVhGehQmzZaz1HiN5e7iylJMSZR7ekOV7NsIqa5qBldlLrsKv4HbgFUVlQrz8Mw==}
 
-  '@capsizecss/unpack@3.0.0':
-    resolution: {integrity: sha512-+ntATQe1AlL7nTOYjwjj6w3299CgRot48wL761TUGYpYgAou3AaONZazp0PKZyCyWhudWsjhq1nvRHOvbMzhTA==}
+  '@capsizecss/unpack@3.0.1':
+    resolution: {integrity: sha512-8XqW8xGn++Eqqbz3e9wKuK7mxryeRjs4LOHLxbh2lwKeSbuNR4NFifDZT4KzvjU6HMOPbiNTsWpniK5EJfTWkg==}
     engines: {node: '>=18'}
 
   '@chevrotain/cst-dts-gen@11.0.3':
@@ -143,28 +151,28 @@ packages:
   '@chevrotain/utils@11.0.3':
     resolution: {integrity: sha512-YslZMgtJUyuMbZ+aKvfF3x1f5liK4mWNxghFRv7jqRR9C3R3fAOGTTKvxXDa2Y1s9zSbcpuO0cAxDYsc9SrXoQ==}
 
-  '@cspell/cspell-bundled-dicts@9.2.2':
-    resolution: {integrity: sha512-W3FKgb89DwMuQEVWz0dPH9uZqC8w+ylpbtmXuevflw3SLtGPyllMvf/1T6tcqIkg3KEWoRYFxjpJWyoOjJkZGw==}
+  '@cspell/cspell-bundled-dicts@9.4.0':
+    resolution: {integrity: sha512-Hm2gpMg/lRv4fKtiO2NfBiaJdFZVVb1V1a+IVhlD9qCuObLhCt60Oze2kD1dQzhbaIX756cs/eyxa5bQ5jihhQ==}
     engines: {node: '>=20'}
 
-  '@cspell/cspell-json-reporter@9.2.2':
-    resolution: {integrity: sha512-7nTqnnRCyQB+bTmIuBR4aRwV5JHymckmz1snCF+ItjDSvlc3qzjxldG8ao5zm34h+b/8YCvdMU9B92eHBt803w==}
+  '@cspell/cspell-json-reporter@9.4.0':
+    resolution: {integrity: sha512-TpHY7t13xNhcZF9bwOfgVIhcyPDamMnxU/TBYhf4mPtXPLrZ5gBTg3UZh0/9Zn3naMjmJtngdsLvB2wai9xBlQ==}
     engines: {node: '>=20'}
 
-  '@cspell/cspell-pipe@9.2.2':
-    resolution: {integrity: sha512-YOdbp1uoKMkYy92qxMjoOxcqcR6LEVDus+72C4X9L8eJ2b+CBO3VaVqU16Y7OQGjYMnukYgB6eyTh8YFo9uBRw==}
+  '@cspell/cspell-pipe@9.4.0':
+    resolution: {integrity: sha512-cI0sUe7SB99hJB1T6PhH/MpSrnml1kOekTCE+VH3Eb7zkVP5/mwJXs8BlufdvwBona+Cgkx6jeWlhFpxLc39Yg==}
     engines: {node: '>=20'}
 
-  '@cspell/cspell-resolver@9.2.2':
-    resolution: {integrity: sha512-5tST2xoU8xbXihr1bdQ6pfcScQ3PkFpKKhFGClVfqS0yf/CKYURqzJlRDVjrFZsl+PT6tw/Jdt0E9Wwp1X1Qgw==}
+  '@cspell/cspell-resolver@9.4.0':
+    resolution: {integrity: sha512-o9gbbdXlhxG2rqtGqQ7xZ8MGDDsPLbskBnTeuA++ix4Ch/HdjrBNmKReIGAEqJPfP+JGgoEKqFISHUDKAJ/ygQ==}
     engines: {node: '>=20'}
 
-  '@cspell/cspell-service-bus@9.2.2':
-    resolution: {integrity: sha512-AxJuw/YPJkz1Ali5mA+OW9y4JiJzb2U7H4pGYq0nRB/mWwI/xtFjuWVkI+BhwrA2P6hHdifu0JdxSLqW4IYpPQ==}
+  '@cspell/cspell-service-bus@9.4.0':
+    resolution: {integrity: sha512-UottRlFPN6FGUfojx5HtUPZTeYXg2rf2HvO/HLh0KicirVYO16vFxTevg9MyOvw1EXSsDRz8ECANjiE7fnzBCQ==}
     engines: {node: '>=20'}
 
-  '@cspell/cspell-types@9.2.2':
-    resolution: {integrity: sha512-/1dRFQ3sEY9Yo+f3w0A8MFJ0BOapQc1uFjlMF19c3uoD/e4PpNLpL1qXY4FeLWKDk1D9VT8SL93J+lIwEi5bvg==}
+  '@cspell/cspell-types@9.4.0':
+    resolution: {integrity: sha512-vSpd50OfmthBH0aRFRLA2zJFtwli3ntHA0WAOJ8tIMLUCJgF3udooRXFeX3wR8ri69C9mc3864LC4inyRC/E9w==}
     engines: {node: '>=20'}
 
   '@cspell/dict-ada@4.1.1':
@@ -173,8 +181,8 @@ packages:
   '@cspell/dict-al@1.1.1':
     resolution: {integrity: sha512-sD8GCaZetgQL4+MaJLXqbzWcRjfKVp8x+px3HuCaaiATAAtvjwUQ5/Iubiqwfd1boIh2Y1/3EgM3TLQ7Q8e0wQ==}
 
-  '@cspell/dict-aws@4.0.15':
-    resolution: {integrity: sha512-aPY7VVR5Os4rz36EaqXBAEy14wR4Rqv+leCJ2Ug/Gd0IglJpM30LalF3e2eJChnjje3vWoEC0Rz3+e5gpZG+Kg==}
+  '@cspell/dict-aws@4.0.17':
+    resolution: {integrity: sha512-ORcblTWcdlGjIbWrgKF+8CNEBQiLVKdUOFoTn0KPNkAYnFcdPP0muT4892h7H4Xafh3j72wqB4/loQ6Nti9E/w==}
 
   '@cspell/dict-bash@4.2.2':
     resolution: {integrity: sha512-kyWbwtX3TsCf5l49gGQIZkRLaB/P8g73GDRm41Zu8Mv51kjl2H7Au0TsEvHv7jzcsRLS6aUYaZv6Zsvk1fOz+Q==}
@@ -182,8 +190,8 @@ packages:
   '@cspell/dict-companies@3.2.7':
     resolution: {integrity: sha512-fEyr3LmpFKTaD0LcRhB4lfW1AmULYBqzg4gWAV0dQCv06l+TsA+JQ+3pZJbUcoaZirtgsgT3dL3RUjmGPhUH0A==}
 
-  '@cspell/dict-cpp@6.0.13':
-    resolution: {integrity: sha512-EFrhN/91tPwadI9m8Rxe65//9gqv+lpZoKtrngzF4DTnw4YAfMLTpykendHps0bz46NZW84/zoY1cxeW2TEPQQ==}
+  '@cspell/dict-cpp@6.0.15':
+    resolution: {integrity: sha512-N7MKK3llRNoBncygvrnLaGvmjo4xzVr5FbtAc9+MFGHK6/LeSySBupr1FM72XDaVSIsmBEe7sDYCHHwlI9Jb2w==}
 
   '@cspell/dict-cryptocurrencies@5.0.5':
     resolution: {integrity: sha512-R68hYYF/rtlE6T/dsObStzN5QZw+0aQBinAXuWCVqwdS7YZo0X33vGMfChkHaiCo3Z2+bkegqHlqxZF4TD3rUA==}
@@ -197,8 +205,8 @@ packages:
   '@cspell/dict-dart@2.3.1':
     resolution: {integrity: sha512-xoiGnULEcWdodXI6EwVyqpZmpOoh8RA2Xk9BNdR7DLamV/QMvEYn8KJ7NlRiTSauJKPNkHHQ5EVHRM6sTS7jdg==}
 
-  '@cspell/dict-data-science@2.0.11':
-    resolution: {integrity: sha512-Dt+83nVCcF+dQyvFSaZjCKt1H5KbsVJFtH2X7VUfmIzQu8xCnV1fUmkhBzGJ+NiFs99Oy9JA6I9EjeqExzXk7g==}
+  '@cspell/dict-data-science@2.0.13':
+    resolution: {integrity: sha512-l1HMEhBJkPmw4I2YGVu2eBSKM89K9pVF+N6qIr5Uo5H3O979jVodtuwP8I7LyPrJnC6nz28oxeGRCLh9xC5CVA==}
 
   '@cspell/dict-django@4.1.5':
     resolution: {integrity: sha512-AvTWu99doU3T8ifoMYOMLW2CXKvyKLukPh1auOPwFGHzueWYvBBN+OxF8wF7XwjTBMMeRleVdLh3aWCDEX/ZWg==}
@@ -212,14 +220,14 @@ packages:
   '@cspell/dict-elixir@4.0.8':
     resolution: {integrity: sha512-CyfphrbMyl4Ms55Vzuj+mNmd693HjBFr9hvU+B2YbFEZprE5AG+EXLYTMRWrXbpds4AuZcvN3deM2XVB80BN/Q==}
 
-  '@cspell/dict-en-common-misspellings@2.1.7':
-    resolution: {integrity: sha512-HAWSOoQ+lxdzLaTALhPofKNJdxZ7HAcTZWQNwb7cvGBiKEy182cb96U35602yBPrBsKY/vLxVs6f0E1JTeQjRQ==}
+  '@cspell/dict-en-common-misspellings@2.1.9':
+    resolution: {integrity: sha512-3pvtsn5UiW0TftC/fa3kKczD+rKFerTjxl0E/ZApz109ZkyjqolgoRPEVrERFdhGngnQ0s+634WkWRxN8nT4GA==}
 
-  '@cspell/dict-en-gb-mit@3.1.12':
-    resolution: {integrity: sha512-KJaJPsTRMXN4sgKHQRMNqqxc7WWZaR5h7+WarIoLUfbEWIQM1FCJiGn2pZX9OLQVBtSnLYo1JVXK1K/Tz3HWEQ==}
+  '@cspell/dict-en-gb-mit@3.1.15':
+    resolution: {integrity: sha512-iF1KPSULjpAbtmPFTzyykytQPliBw5Qc7EVt5a/cdpJ/WBnosjBKHj0/svESc+enQoxq7bMcmhL9qJeGHQAWyQ==}
 
-  '@cspell/dict-en_us@4.4.22':
-    resolution: {integrity: sha512-i9AJ6z5kyZU5L/b+UOOp/7dfa7RxhibLXWaexSJclf7V7R+TzwCTLoOZd1wf/5PBnNGkP8xOSaflkpUbtVijFA==}
+  '@cspell/dict-en_us@4.4.25':
+    resolution: {integrity: sha512-cEdLVSjwfFHK+QmsGYzh8a4QUqXP6B5UPiFlbkIV+eolD5hWuhBaFtaXM6+/kD47/hV2UDYj4yUdD9xsMnlBBQ==}
 
   '@cspell/dict-filetypes@3.0.14':
     resolution: {integrity: sha512-KSXaSMYYNMLLdHEnju1DyRRH3eQWPRYRnOXpuHUdOh2jC44VgQoxyMU7oB3NAhDhZKBPCihabzECsAGFbdKfEA==}
@@ -254,8 +262,8 @@ packages:
   '@cspell/dict-html-symbol-entities@4.0.4':
     resolution: {integrity: sha512-afea+0rGPDeOV9gdO06UW183Qg6wRhWVkgCFwiO3bDupAoyXRuvupbb5nUyqSTsLXIKL8u8uXQlJ9pkz07oVXw==}
 
-  '@cspell/dict-html@4.0.12':
-    resolution: {integrity: sha512-JFffQ1dDVEyJq6tCDWv0r/RqkdSnV43P2F/3jJ9rwLgdsOIXwQbXrz6QDlvQLVvNSnORH9KjDtenFTGDyzfCaA==}
+  '@cspell/dict-html@4.0.13':
+    resolution: {integrity: sha512-vHzk2xfqQYPvoXtQtywa6ekIonPrUEwe2uftjry3UNRNl89TtzLJVSkiymKJ3WMb+W/DwKXKIb1tKzcIS8ccIg==}
 
   '@cspell/dict-java@5.0.12':
     resolution: {integrity: sha512-qPSNhTcl7LGJ5Qp6VN71H8zqvRQK04S08T67knMq9hTA8U7G1sTKzLmBaDOFhq17vNX/+rT+rbRYp+B5Nwza1A==}
@@ -281,11 +289,11 @@ packages:
   '@cspell/dict-makefile@1.0.5':
     resolution: {integrity: sha512-4vrVt7bGiK8Rx98tfRbYo42Xo2IstJkAF4tLLDMNQLkQ86msDlYSKG1ZCk8Abg+EdNcFAjNhXIiNO+w4KflGAQ==}
 
-  '@cspell/dict-markdown@2.0.12':
-    resolution: {integrity: sha512-ufwoliPijAgWkD/ivAMC+A9QD895xKiJRF/fwwknQb7kt7NozTLKFAOBtXGPJAB4UjhGBpYEJVo2elQ0FCAH9A==}
+  '@cspell/dict-markdown@2.0.13':
+    resolution: {integrity: sha512-rFeGikf+lVlywEp7giATUfi8myFeee6jqgbUgtdIdl/OBmRBPe5m7mKNk7yMItMZe8ICrwMxFwJy5OeTnrr6QA==}
     peerDependencies:
       '@cspell/dict-css': ^4.0.18
-      '@cspell/dict-html': ^4.0.12
+      '@cspell/dict-html': ^4.0.13
       '@cspell/dict-html-symbol-entities': ^4.0.4
       '@cspell/dict-typescript': ^3.2.3
 
@@ -295,8 +303,8 @@ packages:
   '@cspell/dict-node@5.0.8':
     resolution: {integrity: sha512-AirZcN2i84ynev3p2/1NCPEhnNsHKMz9zciTngGoqpdItUb2bDt1nJBjwlsrFI78GZRph/VaqTVFwYikmncpXg==}
 
-  '@cspell/dict-npm@5.2.19':
-    resolution: {integrity: sha512-fg23oFvKTsGjGB6DkwCUzZrLZPwp+ItSV0UXS+n6JbcH5dj3CP6MDmdwNX6s6oaAovIFKmwFBP73GUqnjMmnpQ==}
+  '@cspell/dict-npm@5.2.26':
+    resolution: {integrity: sha512-jtjp/wE/4KRTWjtiosAakDwdvrU4lTF3djOaI0tPDPytxou6QTHSm5A7FzU+MzLqvNfdYHUsCcdvx1FE1T/6pg==}
 
   '@cspell/dict-php@4.1.0':
     resolution: {integrity: sha512-dTDeabyOj7eFvn2Q4Za3uVXM2+SzeFMqX8ly2P0XTo4AzbCmI2hulFD/QIADwWmwiRrInbbf8cxwFHNIYrXl4w==}
@@ -307,8 +315,8 @@ packages:
   '@cspell/dict-public-licenses@2.0.15':
     resolution: {integrity: sha512-cJEOs901H13Pfy0fl4dCD1U+xpWIMaEPq8MeYU83FfDZvellAuSo4GqWCripfIqlhns/L6+UZEIJSOZnjgy7Wg==}
 
-  '@cspell/dict-python@4.2.21':
-    resolution: {integrity: sha512-M9OgwXWhpZqEZqKU2psB2DFsT8q5SwEahkQeIpNIRWIErjwG7I9yYhhfvPz6s5gMCMhhb3hqcPJTnmdgqGrQyg==}
+  '@cspell/dict-python@4.2.24':
+    resolution: {integrity: sha512-B1oXYTa0+3sKOvx/svwxFaT3MrkHJ7ZLWpA1N7ZyHoET7IJhLCwcfAu7DCTq1f24Wnd4t+ARJvPEmFbMx65VBw==}
 
   '@cspell/dict-r@2.1.1':
     resolution: {integrity: sha512-71Ka+yKfG4ZHEMEmDxc6+blFkeTTvgKbKAbwiwQAuKl3zpqs1Y0vUtwW2N4b3LgmSPhV3ODVY0y4m5ofqDuKMw==}
@@ -325,8 +333,8 @@ packages:
   '@cspell/dict-shell@1.1.2':
     resolution: {integrity: sha512-WqOUvnwcHK1X61wAfwyXq04cn7KYyskg90j4lLg3sGGKMW9Sq13hs91pqrjC44Q+lQLgCobrTkMDw9Wyl9nRFA==}
 
-  '@cspell/dict-software-terms@5.1.10':
-    resolution: {integrity: sha512-ffnsKiDL5acUerJ/lDiIT0y/tfO9Jk1yp8RpAl0diOUj5iQuT4hXVfgQSx7ppseXWAGN+UgTRYWiKDb1zM3lqg==}
+  '@cspell/dict-software-terms@5.1.16':
+    resolution: {integrity: sha512-AJQ8KZyU9vi2XhEehh2ECkq/jyib0aHOjWYFeHx/2AIrn9LsYJwXI1aD7FFyQ3qixevp+ceAPJ0MVeWLL6LTTw==}
 
   '@cspell/dict-sql@2.2.1':
     resolution: {integrity: sha512-qDHF8MpAYCf4pWU8NKbnVGzkoxMNrFqBHyG/dgrlic5EQiKANCLELYtGlX5auIMDLmTf1inA0eNtv74tyRJ/vg==}
@@ -346,20 +354,23 @@ packages:
   '@cspell/dict-vue@3.0.5':
     resolution: {integrity: sha512-Mqutb8jbM+kIcywuPQCCaK5qQHTdaByoEO2J9LKFy3sqAdiBogNkrplqUK0HyyRFgCfbJUgjz3N85iCMcWH0JA==}
 
-  '@cspell/dynamic-import@9.2.2':
-    resolution: {integrity: sha512-RHQLp0iYcWuK0MGiUBA6dgEOCdI29kZTiBRVcJM/Pzvhvs8j9pzBTkMesZAJ7XOSFz2kU+skRMBsFd774dmYTA==}
+  '@cspell/dict-zig@1.0.0':
+    resolution: {integrity: sha512-XibBIxBlVosU06+M6uHWkFeT0/pW5WajDRYdXG2CgHnq85b0TI/Ks0FuBJykmsgi2CAD3Qtx8UHFEtl/DSFnAQ==}
+
+  '@cspell/dynamic-import@9.4.0':
+    resolution: {integrity: sha512-d2fjLjzrKGUIn5hWK8gMuyAh2pqXSxBqOHpU1jR3jxbrO3MilunKNijaSstv7CZn067Jpc36VfaKQodaXNZzUA==}
     engines: {node: '>=20'}
 
-  '@cspell/filetypes@9.2.2':
-    resolution: {integrity: sha512-oM+cqipbZ4PNxQcKP9sKOeRKBG+oM3NKO3To1FyxYxvnUG7DukW2yH6BS0/GUY7qK+oSftuq5d6DXEAl9wzbEQ==}
+  '@cspell/filetypes@9.4.0':
+    resolution: {integrity: sha512-RMrYHkvPF0tHVFM+T4voEhX9sfYQrd/mnNbf6+O4CWUyLCz4NQ5H9yOgEIJwEcLu4y3NESGXFef/Jn5xo0CUfg==}
     engines: {node: '>=20'}
 
-  '@cspell/strong-weak-map@9.2.2':
-    resolution: {integrity: sha512-Z7rd7NwHaoH/d/Ds97Rv042WS9PgpVdqgO2X0ehYZmgj2E0LIq2MTkIJMheUrSn37D0PW/suroKh6hN15pJtpQ==}
+  '@cspell/strong-weak-map@9.4.0':
+    resolution: {integrity: sha512-ui7mlXYmqElS/SmRubPBNWdkQVWgWbB6rjCurc+0owYXlnweItAMHTxC8mCWM/Au22SF1dB/JR8QBELFXLkTjQ==}
     engines: {node: '>=20'}
 
-  '@cspell/url@9.2.2':
-    resolution: {integrity: sha512-gvLprhrArvLP/rnC8b766dA80EXwBbzXqb9tNDRk1esQV7d3uS1Ftk1970MRlAfLg1pG6V+3C4UrB6WOB/rMCQ==}
+  '@cspell/url@9.4.0':
+    resolution: {integrity: sha512-nt88P6m20AaVbqMxsyPf8KqyWPaFEW2UANi0ijBxc2xTkD2KiUovxfZUYW6NMU9XBYZlovT5LztkEhst2yBcSA==}
     engines: {node: '>=20'}
 
   '@ctrl/tinycolor@4.1.0':
@@ -372,8 +383,8 @@ packages:
   '@emmetio/css-abbreviation@2.1.8':
     resolution: {integrity: sha512-s9yjhJ6saOO/uk1V74eifykk2CBYi01STTK3WlXWGOepyKa23ymJ053+DNQjpFcy1ingpaO7AxCcwLvHFY9tuw==}
 
-  '@emmetio/css-parser@0.4.0':
-    resolution: {integrity: sha512-z7wkxRSZgrQHXVzObGkXG+Vmj3uRlpM11oCZ9pbaz0nFejvCDmAiNDpY75+wgXOcffKpj4rzGtwGaZxfJKsJxw==}
+  '@emmetio/css-parser@0.4.1':
+    resolution: {integrity: sha512-2bC6m0MV/voF4CTZiAbG5MWKbq5EBmDPKu9Sb7s7nVcEzNQlrZP6mFFFlIaISM8X6514H9shWMme1fCm8cWAfQ==}
 
   '@emmetio/html-matcher@1.3.0':
     resolution: {integrity: sha512-NTbsvppE5eVyBMuyGfVu2CRrLvo7J4YHb6t9sBFLyY03WYhXET37qA4zOYUjBWFCRHO7pS1B9khERtY0f5JXPQ==}
@@ -390,252 +401,126 @@ packages:
   '@emnapi/runtime@1.6.0':
     resolution: {integrity: sha512-obtUmAHTMjll499P+D9A3axeJFlhdjOWdKUNs/U6QIGT7V5RjcUW1xToAzjvmgTSQhDbYn/NwfTRoJcQ2rNBxA==}
 
-  '@esbuild/aix-ppc64@0.24.2':
-    resolution: {integrity: sha512-thpVCb/rhxE/BnMLQ7GReQLLN8q9qbHmI55F4489/ByVg2aQaQ6kbcLb6FHkocZzQhxc4gx0sCk0tJkKBFzDhA==}
-    engines: {node: '>=18'}
-    cpu: [ppc64]
-    os: [aix]
-
   '@esbuild/aix-ppc64@0.25.11':
     resolution: {integrity: sha512-Xt1dOL13m8u0WE8iplx9Ibbm+hFAO0GsU2P34UNoDGvZYkY8ifSiy6Zuc1lYxfG7svWE2fzqCUmFp5HCn51gJg==}
     engines: {node: '>=18'}
     cpu: [ppc64]
     os: [aix]
 
-  '@esbuild/android-arm64@0.24.2':
-    resolution: {integrity: sha512-cNLgeqCqV8WxfcTIOeL4OAtSmL8JjcN6m09XIgro1Wi7cF4t/THaWEa7eL5CMoMBdjoHOTh/vwTO/o2TRXIyzg==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [android]
-
   '@esbuild/android-arm64@0.25.11':
     resolution: {integrity: sha512-9slpyFBc4FPPz48+f6jyiXOx/Y4v34TUeDDXJpZqAWQn/08lKGeD8aDp9TMn9jDz2CiEuHwfhRmGBvpnd/PWIQ==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [android]
 
-  '@esbuild/android-arm@0.24.2':
-    resolution: {integrity: sha512-tmwl4hJkCfNHwFB3nBa8z1Uy3ypZpxqxfTQOcHX+xRByyYgunVbZ9MzUUfb0RxaHIMnbHagwAxuTL+tnNM+1/Q==}
-    engines: {node: '>=18'}
-    cpu: [arm]
-    os: [android]
-
   '@esbuild/android-arm@0.25.11':
     resolution: {integrity: sha512-uoa7dU+Dt3HYsethkJ1k6Z9YdcHjTrSb5NUy66ZfZaSV8hEYGD5ZHbEMXnqLFlbBflLsl89Zke7CAdDJ4JI+Gg==}
     engines: {node: '>=18'}
     cpu: [arm]
     os: [android]
 
-  '@esbuild/android-x64@0.24.2':
-    resolution: {integrity: sha512-B6Q0YQDqMx9D7rvIcsXfmJfvUYLoP722bgfBlO5cGvNVb5V/+Y7nhBE3mHV9OpxBf4eAS2S68KZztiPaWq4XYw==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [android]
-
   '@esbuild/android-x64@0.25.11':
     resolution: {integrity: sha512-Sgiab4xBjPU1QoPEIqS3Xx+R2lezu0LKIEcYe6pftr56PqPygbB7+szVnzoShbx64MUupqoE0KyRlN7gezbl8g==}
     engines: {node: '>=18'}
     cpu: [x64]
     os: [android]
 
-  '@esbuild/darwin-arm64@0.24.2':
-    resolution: {integrity: sha512-kj3AnYWc+CekmZnS5IPu9D+HWtUI49hbnyqk0FLEJDbzCIQt7hg7ucF1SQAilhtYpIujfaHr6O0UHlzzSPdOeA==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [darwin]
-
   '@esbuild/darwin-arm64@0.25.11':
     resolution: {integrity: sha512-VekY0PBCukppoQrycFxUqkCojnTQhdec0vevUL/EDOCnXd9LKWqD/bHwMPzigIJXPhC59Vd1WFIL57SKs2mg4w==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [darwin]
 
-  '@esbuild/darwin-x64@0.24.2':
-    resolution: {integrity: sha512-WeSrmwwHaPkNR5H3yYfowhZcbriGqooyu3zI/3GGpF8AyUdsrrP0X6KumITGA9WOyiJavnGZUwPGvxvwfWPHIA==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [darwin]
-
   '@esbuild/darwin-x64@0.25.11':
     resolution: {integrity: sha512-+hfp3yfBalNEpTGp9loYgbknjR695HkqtY3d3/JjSRUyPg/xd6q+mQqIb5qdywnDxRZykIHs3axEqU6l1+oWEQ==}
     engines: {node: '>=18'}
     cpu: [x64]
     os: [darwin]
 
-  '@esbuild/freebsd-arm64@0.24.2':
-    resolution: {integrity: sha512-UN8HXjtJ0k/Mj6a9+5u6+2eZ2ERD7Edt1Q9IZiB5UZAIdPnVKDoG7mdTVGhHJIeEml60JteamR3qhsr1r8gXvg==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [freebsd]
-
   '@esbuild/freebsd-arm64@0.25.11':
     resolution: {integrity: sha512-CmKjrnayyTJF2eVuO//uSjl/K3KsMIeYeyN7FyDBjsR3lnSJHaXlVoAK8DZa7lXWChbuOk7NjAc7ygAwrnPBhA==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [freebsd]
 
-  '@esbuild/freebsd-x64@0.24.2':
-    resolution: {integrity: sha512-TvW7wE/89PYW+IevEJXZ5sF6gJRDY/14hyIGFXdIucxCsbRmLUcjseQu1SyTko+2idmCw94TgyaEZi9HUSOe3Q==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [freebsd]
-
   '@esbuild/freebsd-x64@0.25.11':
     resolution: {integrity: sha512-Dyq+5oscTJvMaYPvW3x3FLpi2+gSZTCE/1ffdwuM6G1ARang/mb3jvjxs0mw6n3Lsw84ocfo9CrNMqc5lTfGOw==}
     engines: {node: '>=18'}
     cpu: [x64]
     os: [freebsd]
 
-  '@esbuild/linux-arm64@0.24.2':
-    resolution: {integrity: sha512-7HnAD6074BW43YvvUmE/35Id9/NB7BeX5EoNkK9obndmZBUk8xmJJeU7DwmUeN7tkysslb2eSl6CTrYz6oEMQg==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [linux]
-
   '@esbuild/linux-arm64@0.25.11':
     resolution: {integrity: sha512-Qr8AzcplUhGvdyUF08A1kHU3Vr2O88xxP0Tm8GcdVOUm25XYcMPp2YqSVHbLuXzYQMf9Bh/iKx7YPqECs6ffLA==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [linux]
 
-  '@esbuild/linux-arm@0.24.2':
-    resolution: {integrity: sha512-n0WRM/gWIdU29J57hJyUdIsk0WarGd6To0s+Y+LwvlC55wt+GT/OgkwoXCXvIue1i1sSNWblHEig00GBWiJgfA==}
-    engines: {node: '>=18'}
-    cpu: [arm]
-    os: [linux]
-
   '@esbuild/linux-arm@0.25.11':
     resolution: {integrity: sha512-TBMv6B4kCfrGJ8cUPo7vd6NECZH/8hPpBHHlYI3qzoYFvWu2AdTvZNuU/7hsbKWqu/COU7NIK12dHAAqBLLXgw==}
     engines: {node: '>=18'}
     cpu: [arm]
     os: [linux]
 
-  '@esbuild/linux-ia32@0.24.2':
-    resolution: {integrity: sha512-sfv0tGPQhcZOgTKO3oBE9xpHuUqguHvSo4jl+wjnKwFpapx+vUDcawbwPNuBIAYdRAvIDBfZVvXprIj3HA+Ugw==}
-    engines: {node: '>=18'}
-    cpu: [ia32]
-    os: [linux]
-
   '@esbuild/linux-ia32@0.25.11':
     resolution: {integrity: sha512-TmnJg8BMGPehs5JKrCLqyWTVAvielc615jbkOirATQvWWB1NMXY77oLMzsUjRLa0+ngecEmDGqt5jiDC6bfvOw==}
     engines: {node: '>=18'}
     cpu: [ia32]
     os: [linux]
 
-  '@esbuild/linux-loong64@0.24.2':
-    resolution: {integrity: sha512-CN9AZr8kEndGooS35ntToZLTQLHEjtVB5n7dl8ZcTZMonJ7CCfStrYhrzF97eAecqVbVJ7APOEe18RPI4KLhwQ==}
-    engines: {node: '>=18'}
-    cpu: [loong64]
-    os: [linux]
-
   '@esbuild/linux-loong64@0.25.11':
     resolution: {integrity: sha512-DIGXL2+gvDaXlaq8xruNXUJdT5tF+SBbJQKbWy/0J7OhU8gOHOzKmGIlfTTl6nHaCOoipxQbuJi7O++ldrxgMw==}
     engines: {node: '>=18'}
     cpu: [loong64]
     os: [linux]
 
-  '@esbuild/linux-mips64el@0.24.2':
-    resolution: {integrity: sha512-iMkk7qr/wl3exJATwkISxI7kTcmHKE+BlymIAbHO8xanq/TjHaaVThFF6ipWzPHryoFsesNQJPE/3wFJw4+huw==}
-    engines: {node: '>=18'}
-    cpu: [mips64el]
-    os: [linux]
-
   '@esbuild/linux-mips64el@0.25.11':
     resolution: {integrity: sha512-Osx1nALUJu4pU43o9OyjSCXokFkFbyzjXb6VhGIJZQ5JZi8ylCQ9/LFagolPsHtgw6himDSyb5ETSfmp4rpiKQ==}
     engines: {node: '>=18'}
     cpu: [mips64el]
     os: [linux]
 
-  '@esbuild/linux-ppc64@0.24.2':
-    resolution: {integrity: sha512-shsVrgCZ57Vr2L8mm39kO5PPIb+843FStGt7sGGoqiiWYconSxwTiuswC1VJZLCjNiMLAMh34jg4VSEQb+iEbw==}
-    engines: {node: '>=18'}
-    cpu: [ppc64]
-    os: [linux]
-
   '@esbuild/linux-ppc64@0.25.11':
     resolution: {integrity: sha512-nbLFgsQQEsBa8XSgSTSlrnBSrpoWh7ioFDUmwo158gIm5NNP+17IYmNWzaIzWmgCxq56vfr34xGkOcZ7jX6CPw==}
     engines: {node: '>=18'}
     cpu: [ppc64]
     os: [linux]
 
-  '@esbuild/linux-riscv64@0.24.2':
-    resolution: {integrity: sha512-4eSFWnU9Hhd68fW16GD0TINewo1L6dRrB+oLNNbYyMUAeOD2yCK5KXGK1GH4qD/kT+bTEXjsyTCiJGHPZ3eM9Q==}
-    engines: {node: '>=18'}
-    cpu: [riscv64]
-    os: [linux]
-
   '@esbuild/linux-riscv64@0.25.11':
     resolution: {integrity: sha512-HfyAmqZi9uBAbgKYP1yGuI7tSREXwIb438q0nqvlpxAOs3XnZ8RsisRfmVsgV486NdjD7Mw2UrFSw51lzUk1ww==}
     engines: {node: '>=18'}
     cpu: [riscv64]
     os: [linux]
 
-  '@esbuild/linux-s390x@0.24.2':
-    resolution: {integrity: sha512-S0Bh0A53b0YHL2XEXC20bHLuGMOhFDO6GN4b3YjRLK//Ep3ql3erpNcPlEFed93hsQAjAQDNsvcK+hV90FubSw==}
-    engines: {node: '>=18'}
-    cpu: [s390x]
-    os: [linux]
-
   '@esbuild/linux-s390x@0.25.11':
     resolution: {integrity: sha512-HjLqVgSSYnVXRisyfmzsH6mXqyvj0SA7pG5g+9W7ESgwA70AXYNpfKBqh1KbTxmQVaYxpzA/SvlB9oclGPbApw==}
     engines: {node: '>=18'}
     cpu: [s390x]
     os: [linux]
 
-  '@esbuild/linux-x64@0.24.2':
-    resolution: {integrity: sha512-8Qi4nQcCTbLnK9WoMjdC9NiTG6/E38RNICU6sUNqK0QFxCYgoARqVqxdFmWkdonVsvGqWhmm7MO0jyTqLqwj0Q==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [linux]
-
   '@esbuild/linux-x64@0.25.11':
     resolution: {integrity: sha512-HSFAT4+WYjIhrHxKBwGmOOSpphjYkcswF449j6EjsjbinTZbp8PJtjsVK1XFJStdzXdy/jaddAep2FGY+wyFAQ==}
     engines: {node: '>=18'}
     cpu: [x64]
     os: [linux]
 
-  '@esbuild/netbsd-arm64@0.24.2':
-    resolution: {integrity: sha512-wuLK/VztRRpMt9zyHSazyCVdCXlpHkKm34WUyinD2lzK07FAHTq0KQvZZlXikNWkDGoT6x3TD51jKQ7gMVpopw==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [netbsd]
-
   '@esbuild/netbsd-arm64@0.25.11':
     resolution: {integrity: sha512-hr9Oxj1Fa4r04dNpWr3P8QKVVsjQhqrMSUzZzf+LZcYjZNqhA3IAfPQdEh1FLVUJSiu6sgAwp3OmwBfbFgG2Xg==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [netbsd]
 
-  '@esbuild/netbsd-x64@0.24.2':
-    resolution: {integrity: sha512-VefFaQUc4FMmJuAxmIHgUmfNiLXY438XrL4GDNV1Y1H/RW3qow68xTwjZKfj/+Plp9NANmzbH5R40Meudu8mmw==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [netbsd]
-
   '@esbuild/netbsd-x64@0.25.11':
     resolution: {integrity: sha512-u7tKA+qbzBydyj0vgpu+5h5AeudxOAGncb8N6C9Kh1N4n7wU1Xw1JDApsRjpShRpXRQlJLb9wY28ELpwdPcZ7A==}
     engines: {node: '>=18'}
     cpu: [x64]
     os: [netbsd]
 
-  '@esbuild/openbsd-arm64@0.24.2':
-    resolution: {integrity: sha512-YQbi46SBct6iKnszhSvdluqDmxCJA+Pu280Av9WICNwQmMxV7nLRHZfjQzwbPs3jeWnuAhE9Jy0NrnJ12Oz+0A==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [openbsd]
-
   '@esbuild/openbsd-arm64@0.25.11':
     resolution: {integrity: sha512-Qq6YHhayieor3DxFOoYM1q0q1uMFYb7cSpLD2qzDSvK1NAvqFi8Xgivv0cFC6J+hWVw2teCYltyy9/m/14ryHg==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [openbsd]
 
-  '@esbuild/openbsd-x64@0.24.2':
-    resolution: {integrity: sha512-+iDS6zpNM6EnJyWv0bMGLWSWeXGN/HTaF/LXHXHwejGsVi+ooqDfMCCTerNFxEkM3wYVcExkeGXNqshc9iMaOA==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [openbsd]
-
   '@esbuild/openbsd-x64@0.25.11':
     resolution: {integrity: sha512-CN+7c++kkbrckTOz5hrehxWN7uIhFFlmS/hqziSFVWpAzpWrQoAG4chH+nN3Be+Kzv/uuo7zhX716x3Sn2Jduw==}
     engines: {node: '>=18'}
@@ -648,48 +533,24 @@ packages:
     cpu: [arm64]
     os: [openharmony]
 
-  '@esbuild/sunos-x64@0.24.2':
-    resolution: {integrity: sha512-hTdsW27jcktEvpwNHJU4ZwWFGkz2zRJUz8pvddmXPtXDzVKTTINmlmga3ZzwcuMpUvLw7JkLy9QLKyGpD2Yxig==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [sunos]
-
   '@esbuild/sunos-x64@0.25.11':
     resolution: {integrity: sha512-nq2xdYaWxyg9DcIyXkZhcYulC6pQ2FuCgem3LI92IwMgIZ69KHeY8T4Y88pcwoLIjbed8n36CyKoYRDygNSGhA==}
     engines: {node: '>=18'}
     cpu: [x64]
     os: [sunos]
 
-  '@esbuild/win32-arm64@0.24.2':
-    resolution: {integrity: sha512-LihEQ2BBKVFLOC9ZItT9iFprsE9tqjDjnbulhHoFxYQtQfai7qfluVODIYxt1PgdoyQkz23+01rzwNwYfutxUQ==}
-    engines: {node: '>=18'}
-    cpu: [arm64]
-    os: [win32]
-
   '@esbuild/win32-arm64@0.25.11':
     resolution: {integrity: sha512-3XxECOWJq1qMZ3MN8srCJ/QfoLpL+VaxD/WfNRm1O3B4+AZ/BnLVgFbUV3eiRYDMXetciH16dwPbbHqwe1uU0Q==}
     engines: {node: '>=18'}
     cpu: [arm64]
     os: [win32]
 
-  '@esbuild/win32-ia32@0.24.2':
-    resolution: {integrity: sha512-q+iGUwfs8tncmFC9pcnD5IvRHAzmbwQ3GPS5/ceCyHdjXubwQWI12MKWSNSMYLJMq23/IUCvJMS76PDqXe1fxA==}
-    engines: {node: '>=18'}
-    cpu: [ia32]
-    os: [win32]
-
   '@esbuild/win32-ia32@0.25.11':
     resolution: {integrity: sha512-3ukss6gb9XZ8TlRyJlgLn17ecsK4NSQTmdIXRASVsiS2sQ6zPPZklNJT5GR5tE/MUarymmy8kCEf5xPCNCqVOA==}
     engines: {node: '>=18'}
     cpu: [ia32]
     os: [win32]
 
-  '@esbuild/win32-x64@0.24.2':
-    resolution: {integrity: sha512-7VTgWzgMGvup6aSqDPLiW5zHaxYJGTO4OokMjIlrCtf+VpEL+cXKtCvg723iguPYI5oaUNdS+/V7OU2gvXVWEg==}
-    engines: {node: '>=18'}
-    cpu: [x64]
-    os: [win32]
-
   '@esbuild/win32-x64@0.25.11':
     resolution: {integrity: sha512-D7Hpz6A2L4hzsRpPaCYkQnGOotdUpDzSGRIv9I+1ITdHROSFUWW95ZPZWQmGka1Fg7W3zFJowyn9WGwMJ0+KPA==}
     engines: {node: '>=18'}
@@ -718,33 +579,65 @@ packages:
     resolution: {integrity: sha512-A5P/LfWGFSl6nsckYtjw9da+19jB8hkJ6ACTGcDfEJ0aE+l2n2El7dsVM7UVHZQ9s2lmYMWlrS21YLy2IR1LUw==}
     engines: {node: '>=18'}
 
+  '@img/sharp-darwin-arm64@0.33.5':
+    resolution: {integrity: sha512-UT4p+iz/2H4twwAoLCqfA9UH5pI6DggwKEGuaPy7nCVQ8ZsiY5PIcrRvD1DzuY3qYL07NtIQcWnBSY/heikIFQ==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm64]
+    os: [darwin]
+
   '@img/sharp-darwin-arm64@0.34.4':
     resolution: {integrity: sha512-sitdlPzDVyvmINUdJle3TNHl+AG9QcwiAMsXmccqsCOMZNIdW2/7S26w0LyU8euiLVzFBL3dXPwVCq/ODnf2vA==}
     engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
     cpu: [arm64]
     os: [darwin]
 
+  '@img/sharp-darwin-x64@0.33.5':
+    resolution: {integrity: sha512-fyHac4jIc1ANYGRDxtiqelIbdWkIuQaI84Mv45KvGRRxSAa7o7d1ZKAOBaYbnepLC1WqxfpimdeWfvqqSGwR2Q==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [darwin]
+
   '@img/sharp-darwin-x64@0.34.4':
     resolution: {integrity: sha512-rZheupWIoa3+SOdF/IcUe1ah4ZDpKBGWcsPX6MT0lYniH9micvIU7HQkYTfrx5Xi8u+YqwLtxC/3vl8TQN6rMg==}
     engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
     cpu: [x64]
     os: [darwin]
 
+  '@img/sharp-libvips-darwin-arm64@1.0.4':
+    resolution: {integrity: sha512-XblONe153h0O2zuFfTAbQYAX2JhYmDHeWikp1LM9Hul9gVPjFY427k6dFEcOL72O01QxQsWi761svJ/ev9xEDg==}
+    cpu: [arm64]
+    os: [darwin]
+
   '@img/sharp-libvips-darwin-arm64@1.2.3':
     resolution: {integrity: sha512-QzWAKo7kpHxbuHqUC28DZ9pIKpSi2ts2OJnoIGI26+HMgq92ZZ4vk8iJd4XsxN+tYfNJxzH6W62X5eTcsBymHw==}
     cpu: [arm64]
     os: [darwin]
 
+  '@img/sharp-libvips-darwin-x64@1.0.4':
+    resolution: {integrity: sha512-xnGR8YuZYfJGmWPvmlunFaWJsb9T/AO2ykoP3Fz/0X5XV2aoYBPkX6xqCQvUTKKiLddarLaxpzNe+b1hjeWHAQ==}
+    cpu: [x64]
+    os: [darwin]
+
   '@img/sharp-libvips-darwin-x64@1.2.3':
     resolution: {integrity: sha512-Ju+g2xn1E2AKO6YBhxjj+ACcsPQRHT0bhpglxcEf+3uyPY+/gL8veniKoo96335ZaPo03bdDXMv0t+BBFAbmRA==}
     cpu: [x64]
     os: [darwin]
 
+  '@img/sharp-libvips-linux-arm64@1.0.4':
+    resolution: {integrity: sha512-9B+taZ8DlyyqzZQnoeIvDVR/2F4EbMepXMc/NdVbkzsJbzkUjhXv/70GQJ7tdLA4YJgNP25zukcxpX2/SueNrA==}
+    cpu: [arm64]
+    os: [linux]
+
   '@img/sharp-libvips-linux-arm64@1.2.3':
     resolution: {integrity: sha512-I4RxkXU90cpufazhGPyVujYwfIm9Nk1QDEmiIsaPwdnm013F7RIceaCc87kAH+oUB1ezqEvC6ga4m7MSlqsJvQ==}
     cpu: [arm64]
     os: [linux]
 
+  '@img/sharp-libvips-linux-arm@1.0.5':
+    resolution: {integrity: sha512-gvcC4ACAOPRNATg/ov8/MnbxFDJqf/pDePbBnuBDcjsI8PssmjoKMAz4LtLaVi+OnSb5FK/yIOamqDwGmXW32g==}
+    cpu: [arm]
+    os: [linux]
+
   '@img/sharp-libvips-linux-arm@1.2.3':
     resolution: {integrity: sha512-x1uE93lyP6wEwGvgAIV0gP6zmaL/a0tGzJs/BIDDG0zeBhMnuUPm7ptxGhUbcGs4okDJrk4nxgrmxpib9g6HpA==}
     cpu: [arm]
@@ -760,6 +653,11 @@ packages:
     cpu: [s390x]
     os: [linux]
 
+  '@img/sharp-libvips-linux-x64@1.0.4':
+    resolution: {integrity: sha512-MmWmQ3iPFZr0Iev+BAgVMb3ZyC4KeFc3jFxnNbEPas60e1cIfevbtuyf9nDGIzOaW9PdnDciJm+wFFaTlj5xYw==}
+    cpu: [x64]
+    os: [linux]
+
   '@img/sharp-libvips-linux-x64@1.2.3':
     resolution: {integrity: sha512-3JU7LmR85K6bBiRzSUc/Ff9JBVIFVvq6bomKE0e63UXGeRw2HPVEjoJke1Yx+iU4rL7/7kUjES4dZ/81Qjhyxg==}
     cpu: [x64]
@@ -775,12 +673,24 @@ packages:
     cpu: [x64]
     os: [linux]
 
+  '@img/sharp-linux-arm64@0.33.5':
+    resolution: {integrity: sha512-JMVv+AMRyGOHtO1RFBiJy/MBsgz0x4AWrT6QoEVVTyh1E39TrCUpTRI7mx9VksGX4awWASxqCYLCV4wBZHAYxA==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm64]
+    os: [linux]
+
   '@img/sharp-linux-arm64@0.34.4':
     resolution: {integrity: sha512-YXU1F/mN/Wu786tl72CyJjP/Ngl8mGHN1hST4BGl+hiW5jhCnV2uRVTNOcaYPs73NeT/H8Upm3y9582JVuZHrQ==}
     engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
     cpu: [arm64]
     os: [linux]
 
+  '@img/sharp-linux-arm@0.33.5':
+    resolution: {integrity: sha512-JTS1eldqZbJxjvKaAkxhZmBqPRGmxgu+qFKSInv8moZ2AmT5Yib3EQ1c6gp493HvrvV8QgdOXdyaIBrhvFhBMQ==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [arm]
+    os: [linux]
+
   '@img/sharp-linux-arm@0.34.4':
     resolution: {integrity: sha512-Xyam4mlqM0KkTHYVSuc6wXRmM7LGN0P12li03jAnZ3EJWZqj83+hi8Y9UxZUbxsgsK1qOEwg7O0Bc0LjqQVtxA==}
     engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
@@ -799,6 +709,12 @@ packages:
     cpu: [s390x]
     os: [linux]
 
+  '@img/sharp-linux-x64@0.33.5':
+    resolution: {integrity: sha512-opC+Ok5pRNAzuvq1AG0ar+1owsu842/Ab+4qvU879ippJBHvyY5n2mxF1izXqkPYlGuP/M556uh53jRLJmzTWA==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [linux]
+
   '@img/sharp-linux-x64@0.34.4':
     resolution: {integrity: sha512-ZfGtcp2xS51iG79c6Vhw9CWqQC8l2Ot8dygxoDoIQPTat/Ov3qAa8qpxSrtAEAJW+UjTXc4yxCjNfxm4h6Xm2A==}
     engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
@@ -834,6 +750,12 @@ packages:
     cpu: [ia32]
     os: [win32]
 
+  '@img/sharp-win32-x64@0.33.5':
+    resolution: {integrity: sha512-MpY/o8/8kj+EcnxwvrP4aTJSWw/aZ7JIGR4aBeZkZw5B7/Jn+tY9/VNwtcoGmdT7GfggGIU4kygOMSbYnOrAbg==}
+    engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
+    cpu: [x64]
+    os: [win32]
+
   '@img/sharp-win32-x64@0.34.4':
     resolution: {integrity: sha512-xIyj4wpYs8J18sVN3mSQjwrw7fKUqRw+Z5rnHNCy5fYTxigBz81u5mOMPmFumwjcn8+ld1ppptMBCLic1nz6ig==}
     engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
@@ -901,101 +823,51 @@ packages:
       rollup:
         optional: true
 
-  '@rollup/rollup-android-arm-eabi@4.34.7':
-    resolution: {integrity: sha512-l6CtzHYo8D2TQ3J7qJNpp3Q1Iye56ssIAtqbM2H8axxCEEwvN7o8Ze9PuIapbxFL3OHrJU2JBX6FIIVnP/rYyw==}
-    cpu: [arm]
-    os: [android]
-
   '@rollup/rollup-android-arm-eabi@4.52.5':
     resolution: {integrity: sha512-8c1vW4ocv3UOMp9K+gToY5zL2XiiVw3k7f1ksf4yO1FlDFQ1C2u72iACFnSOceJFsWskc2WZNqeRhFRPzv+wtQ==}
     cpu: [arm]
     os: [android]
 
-  '@rollup/rollup-android-arm64@4.34.7':
-    resolution: {integrity: sha512-KvyJpFUueUnSp53zhAa293QBYqwm94TgYTIfXyOTtidhm5V0LbLCJQRGkQClYiX3FXDQGSvPxOTD/6rPStMMDg==}
-    cpu: [arm64]
-    os: [android]
-
   '@rollup/rollup-android-arm64@4.52.5':
     resolution: {integrity: sha512-mQGfsIEFcu21mvqkEKKu2dYmtuSZOBMmAl5CFlPGLY94Vlcm+zWApK7F/eocsNzp8tKmbeBP8yXyAbx0XHsFNA==}
     cpu: [arm64]
     os: [android]
 
-  '@rollup/rollup-darwin-arm64@4.34.7':
-    resolution: {integrity: sha512-jq87CjmgL9YIKvs8ybtIC98s/M3HdbqXhllcy9EdLV0yMg1DpxES2gr65nNy7ObNo/vZ/MrOTxt0bE5LinL6mA==}
-    cpu: [arm64]
-    os: [darwin]
-
   '@rollup/rollup-darwin-arm64@4.52.5':
     resolution: {integrity: sha512-takF3CR71mCAGA+v794QUZ0b6ZSrgJkArC+gUiG6LB6TQty9T0Mqh3m2ImRBOxS2IeYBo4lKWIieSvnEk2OQWA==}
     cpu: [arm64]
     os: [darwin]
 
-  '@rollup/rollup-darwin-x64@4.34.7':
-    resolution: {integrity: sha512-rSI/m8OxBjsdnMMg0WEetu/w+LhLAcCDEiL66lmMX4R3oaml3eXz3Dxfvrxs1FbzPbJMaItQiksyMfv1hoIxnA==}
-    cpu: [x64]
-    os: [darwin]
-
   '@rollup/rollup-darwin-x64@4.52.5':
     resolution: {integrity: sha512-W901Pla8Ya95WpxDn//VF9K9u2JbocwV/v75TE0YIHNTbhqUTv9w4VuQ9MaWlNOkkEfFwkdNhXgcLqPSmHy0fA==}
     cpu: [x64]
     os: [darwin]
 
-  '@rollup/rollup-freebsd-arm64@4.34.7':
-    resolution: {integrity: sha512-oIoJRy3ZrdsXpFuWDtzsOOa/E/RbRWXVokpVrNnkS7npz8GEG++E1gYbzhYxhxHbO2om1T26BZjVmdIoyN2WtA==}
-    cpu: [arm64]
-    os: [freebsd]
-
   '@rollup/rollup-freebsd-arm64@4.52.5':
     resolution: {integrity: sha512-QofO7i7JycsYOWxe0GFqhLmF6l1TqBswJMvICnRUjqCx8b47MTo46W8AoeQwiokAx3zVryVnxtBMcGcnX12LvA==}
     cpu: [arm64]
     os: [freebsd]
 
-  '@rollup/rollup-freebsd-x64@4.34.7':
-    resolution: {integrity: sha512-X++QSLm4NZfZ3VXGVwyHdRf58IBbCu9ammgJxuWZYLX0du6kZvdNqPwrjvDfwmi6wFdvfZ/s6K7ia0E5kI7m8Q==}
-    cpu: [x64]
-    os: [freebsd]
-
   '@rollup/rollup-freebsd-x64@4.52.5':
     resolution: {integrity: sha512-jr21b/99ew8ujZubPo9skbrItHEIE50WdV86cdSoRkKtmWa+DDr6fu2c/xyRT0F/WazZpam6kk7IHBerSL7LDQ==}
     cpu: [x64]
     os: [freebsd]
 
-  '@rollup/rollup-linux-arm-gnueabihf@4.34.7':
-    resolution: {integrity: sha512-Z0TzhrsNqukTz3ISzrvyshQpFnFRfLunYiXxlCRvcrb3nvC5rVKI+ZXPFG/Aa4jhQa1gHgH3A0exHaRRN4VmdQ==}
-    cpu: [arm]
-    os: [linux]
-
   '@rollup/rollup-linux-arm-gnueabihf@4.52.5':
     resolution: {integrity: sha512-PsNAbcyv9CcecAUagQefwX8fQn9LQ4nZkpDboBOttmyffnInRy8R8dSg6hxxl2Re5QhHBf6FYIDhIj5v982ATQ==}
     cpu: [arm]
     os: [linux]
 
-  '@rollup/rollup-linux-arm-musleabihf@4.34.7':
-    resolution: {integrity: sha512-nkznpyXekFAbvFBKBy4nNppSgneB1wwG1yx/hujN3wRnhnkrYVugMTCBXED4+Ni6thoWfQuHNYbFjgGH0MBXtw==}
-    cpu: [arm]
-    os: [linux]
-
   '@rollup/rollup-linux-arm-musleabihf@4.52.5':
     resolution: {integrity: sha512-Fw4tysRutyQc/wwkmcyoqFtJhh0u31K+Q6jYjeicsGJJ7bbEq8LwPWV/w0cnzOqR2m694/Af6hpFayLJZkG2VQ==}
     cpu: [arm]
     os: [linux]
 
-  '@rollup/rollup-linux-arm64-gnu@4.34.7':
-    resolution: {integrity: sha512-KCjlUkcKs6PjOcxolqrXglBDcfCuUCTVlX5BgzgoJHw+1rWH1MCkETLkLe5iLLS9dP5gKC7mp3y6x8c1oGBUtA==}
-    cpu: [arm64]
-    os: [linux]
-
   '@rollup/rollup-linux-arm64-gnu@4.52.5':
     resolution: {integrity: sha512-a+3wVnAYdQClOTlyapKmyI6BLPAFYs0JM8HRpgYZQO02rMR09ZcV9LbQB+NL6sljzG38869YqThrRnfPMCDtZg==}
     cpu: [arm64]
     os: [linux]
 
-  '@rollup/rollup-linux-arm64-musl@4.34.7':
-    resolution: {integrity: sha512-uFLJFz6+utmpbR313TTx+NpPuAXbPz4BhTQzgaP0tozlLnGnQ6rCo6tLwaSa6b7l6gRErjLicXQ1iPiXzYotjw==}
-    cpu: [arm64]
-    os: [linux]
-
   '@rollup/rollup-linux-arm64-musl@4.52.5':
     resolution: {integrity: sha512-AvttBOMwO9Pcuuf7m9PkC1PUIKsfaAJ4AYhy944qeTJgQOqJYJ9oVl2nYgY7Rk0mkbsuOpCAYSs6wLYB2Xiw0Q==}
     cpu: [arm64]
@@ -1006,26 +878,11 @@ packages:
     cpu: [loong64]
     os: [linux]
 
-  '@rollup/rollup-linux-loongarch64-gnu@4.34.7':
-    resolution: {integrity: sha512-ws8pc68UcJJqCpneDFepnwlsMUFoWvPbWXT/XUrJ7rWUL9vLoIN3GAasgG+nCvq8xrE3pIrd+qLX/jotcLy0Qw==}
-    cpu: [loong64]
-    os: [linux]
-
-  '@rollup/rollup-linux-powerpc64le-gnu@4.34.7':
-    resolution: {integrity: sha512-vrDk9JDa/BFkxcS2PbWpr0C/LiiSLxFbNOBgfbW6P8TBe9PPHx9Wqbvx2xgNi1TOAyQHQJ7RZFqBiEohm79r0w==}
-    cpu: [ppc64]
-    os: [linux]
-
   '@rollup/rollup-linux-ppc64-gnu@4.52.5':
     resolution: {integrity: sha512-W/b9ZN/U9+hPQVvlGwjzi+Wy4xdoH2I8EjaCkMvzpI7wJUs8sWJ03Rq96jRnHkSrcHTpQe8h5Tg3ZzUPGauvAw==}
     cpu: [ppc64]
     os: [linux]
 
-  '@rollup/rollup-linux-riscv64-gnu@4.34.7':
-    resolution: {integrity: sha512-rB+ejFyjtmSo+g/a4eovDD1lHWHVqizN8P0Hm0RElkINpS0XOdpaXloqM4FBkF9ZWEzg6bezymbpLmeMldfLTw==}
-    cpu: [riscv64]
-    os: [linux]
-
   '@rollup/rollup-linux-riscv64-gnu@4.52.5':
     resolution: {integrity: sha512-sjQLr9BW7R/ZiXnQiWPkErNfLMkkWIoCz7YMn27HldKsADEKa5WYdobaa1hmN6slu9oWQbB6/jFpJ+P2IkVrmw==}
     cpu: [riscv64]
@@ -1036,31 +893,16 @@ packages:
     cpu: [riscv64]
     os: [linux]
 
-  '@rollup/rollup-linux-s390x-gnu@4.34.7':
-    resolution: {integrity: sha512-nNXNjo4As6dNqRn7OrsnHzwTgtypfRA3u3AKr0B3sOOo+HkedIbn8ZtFnB+4XyKJojIfqDKmbIzO1QydQ8c+Pw==}
-    cpu: [s390x]
-    os: [linux]
-
   '@rollup/rollup-linux-s390x-gnu@4.52.5':
     resolution: {integrity: sha512-gn8kHOrku8D4NGHMK1Y7NA7INQTRdVOntt1OCYypZPRt6skGbddska44K8iocdpxHTMMNui5oH4elPH4QOLrFQ==}
     cpu: [s390x]
     os: [linux]
 
-  '@rollup/rollup-linux-x64-gnu@4.34.7':
-    resolution: {integrity: sha512-9kPVf9ahnpOMSGlCxXGv980wXD0zRR3wyk8+33/MXQIpQEOpaNe7dEHm5LMfyRZRNt9lMEQuH0jUKj15MkM7QA==}
-    cpu: [x64]
-    os: [linux]
-
   '@rollup/rollup-linux-x64-gnu@4.52.5':
     resolution: {integrity: sha512-hXGLYpdhiNElzN770+H2nlx+jRog8TyynpTVzdlc6bndktjKWyZyiCsuDAlpd+j+W+WNqfcyAWz9HxxIGfZm1Q==}
     cpu: [x64]
     os: [linux]
 
-  '@rollup/rollup-linux-x64-musl@4.34.7':
-    resolution: {integrity: sha512-7wJPXRWTTPtTFDFezA8sle/1sdgxDjuMoRXEKtx97ViRxGGkVQYovem+Q8Pr/2HxiHp74SSRG+o6R0Yq0shPwQ==}
-    cpu: [x64]
-    os: [linux]
-
   '@rollup/rollup-linux-x64-musl@4.52.5':
     resolution: {integrity: sha512-arCGIcuNKjBoKAXD+y7XomR9gY6Mw7HnFBv5Rw7wQRvwYLR7gBAgV7Mb2QTyjXfTveBNFAtPt46/36vV9STLNg==}
     cpu: [x64]
@@ -1071,21 +913,11 @@ packages:
     cpu: [arm64]
     os: [openharmony]
 
-  '@rollup/rollup-win32-arm64-msvc@4.34.7':
-    resolution: {integrity: sha512-MN7aaBC7mAjsiMEZcsJvwNsQVNZShgES/9SzWp1HC9Yjqb5OpexYnRjF7RmE4itbeesHMYYQiAtUAQaSKs2Rfw==}
-    cpu: [arm64]
-    os: [win32]
-
   '@rollup/rollup-win32-arm64-msvc@4.52.5':
     resolution: {integrity: sha512-w0cDWVR6MlTstla1cIfOGyl8+qb93FlAVutcor14Gf5Md5ap5ySfQ7R9S/NjNaMLSFdUnKGEasmVnu3lCMqB7w==}
     cpu: [arm64]
     os: [win32]
 
-  '@rollup/rollup-win32-ia32-msvc@4.34.7':
-    resolution: {integrity: sha512-aeawEKYswsFu1LhDM9RIgToobquzdtSc4jSVqHV8uApz4FVvhFl/mKh92wc8WpFc6aYCothV/03UjY6y7yLgbg==}
-    cpu: [ia32]
-    os: [win32]
-
   '@rollup/rollup-win32-ia32-msvc@4.52.5':
     resolution: {integrity: sha512-Aufdpzp7DpOTULJCuvzqcItSGDH73pF3ko/f+ckJhxQyHtp67rHw3HMNxoIdDMUITJESNE6a8uh4Lo4SLouOUg==}
     cpu: [ia32]
@@ -1096,11 +928,6 @@ packages:
     cpu: [x64]
     os: [win32]
 
-  '@rollup/rollup-win32-x64-msvc@4.34.7':
-    resolution: {integrity: sha512-4ZedScpxxIrVO7otcZ8kCX1mZArtH2Wfj3uFCxRJ9NO80gg1XV0U/b2f/MKaGwj2X3QopHfoWiDQ917FRpwY3w==}
-    cpu: [x64]
-    os: [win32]
-
   '@rollup/rollup-win32-x64-msvc@4.52.5':
     resolution: {integrity: sha512-TAcgQh2sSkykPRWLrdyy2AiceMckNf5loITqXxFI5VuQjS5tSuw3WlwdN8qv8vzjLAUTvYaH/mVjSFpbkFbpTg==}
     cpu: [x64]
@@ -1109,21 +936,39 @@ packages:
   '@shikijs/core@3.14.0':
     resolution: {integrity: sha512-qRSeuP5vlYHCNUIrpEBQFO7vSkR7jn7Kv+5X3FO/zBKVDGQbcnlScD3XhkrHi/R8Ltz0kEjvFR9Szp/XMRbFMw==}
 
+  '@shikijs/core@3.20.0':
+    resolution: {integrity: sha512-f2ED7HYV4JEk827mtMDwe/yQ25pRiXZmtHjWF8uzZKuKiEsJR7Ce1nuQ+HhV9FzDcbIo4ObBCD9GPTzNuy9S1g==}
+
   '@shikijs/engine-javascript@3.14.0':
     resolution: {integrity: sha512-3v1kAXI2TsWQuwv86cREH/+FK9Pjw3dorVEykzQDhwrZj0lwsHYlfyARaKmn6vr5Gasf8aeVpb8JkzeWspxOLQ==}
 
+  '@shikijs/engine-javascript@3.20.0':
+    resolution: {integrity: sha512-OFx8fHAZuk7I42Z9YAdZ95To6jDePQ9Rnfbw9uSRTSbBhYBp1kEOKv/3jOimcj3VRUKusDYM6DswLauwfhboLg==}
+
   '@shikijs/engine-oniguruma@3.14.0':
     resolution: {integrity: sha512-TNcYTYMbJyy+ZjzWtt0bG5y4YyMIWC2nyePz+CFMWqm+HnZZyy9SWMgo8Z6KBJVIZnx8XUXS8U2afO6Y0g1Oug==}
 
+  '@shikijs/engine-oniguruma@3.20.0':
+    resolution: {integrity: sha512-Yx3gy7xLzM0ZOjqoxciHjA7dAt5tyzJE3L4uQoM83agahy+PlW244XJSrmJRSBvGYELDhYXPacD4R/cauV5bzQ==}
+
   '@shikijs/langs@3.14.0':
     resolution: {integrity: sha512-DIB2EQY7yPX1/ZH7lMcwrK5pl+ZkP/xoSpUzg9YC8R+evRCCiSQ7yyrvEyBsMnfZq4eBzLzBlugMyTAf13+pzg==}
 
+  '@shikijs/langs@3.20.0':
+    resolution: {integrity: sha512-le+bssCxcSHrygCWuOrYJHvjus6zhQ2K7q/0mgjiffRbkhM4o1EWu2m+29l0yEsHDbWaWPNnDUTRVVBvBBeKaA==}
+
   '@shikijs/themes@3.14.0':
     resolution: {integrity: sha512-fAo/OnfWckNmv4uBoUu6dSlkcBc+SA1xzj5oUSaz5z3KqHtEbUypg/9xxgJARtM6+7RVm0Q6Xnty41xA1ma1IA==}
 
+  '@shikijs/themes@3.20.0':
+    resolution: {integrity: sha512-U1NSU7Sl26Q7ErRvJUouArxfM2euWqq1xaSrbqMu2iqa+tSp0D1Yah8216sDYbdDHw4C8b75UpE65eWorm2erQ==}
+
   '@shikijs/types@3.14.0':
     resolution: {integrity: sha512-bQGgC6vrY8U/9ObG1Z/vTro+uclbjjD/uG58RvfxKZVD5p9Yc1ka3tVyEFy7BNJLzxuWyHH5NWynP9zZZS59eQ==}
 
+  '@shikijs/types@3.20.0':
+    resolution: {integrity: sha512-lhYAATn10nkZcBQ0BlzSbJA3wcmL5MXUUF8d2Zzon6saZDlToKaiRX60n2+ZaHJCmXEcZRWNzn+k9vplr8Jhsw==}
+
   '@shikijs/vscode-textmate@10.0.2':
     resolution: {integrity: sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==}
 
@@ -1241,12 +1086,6 @@ packages:
   '@types/estree-jsx@1.0.5':
     resolution: {integrity: sha512-52CcUVNFyfb1A2ALocQw/Dd1BQFNmSdkuC3BkZ6iqhdMfQz7JWOFRuJFloOzjk+6WijU56m9oKXFAXc7o3Towg==}
 
-  '@types/estree@1.0.5':
-    resolution: {integrity: sha512-/kYRxGDLWzHOB7q+wtSUQlFrtcdUccpfy+X+9iMBpHK8QLLhx2wIPYuS5DYtR9Wa/YlZAbIovy7qVdB1Aq6Lyw==}
-
-  '@types/estree@1.0.6':
-    resolution: {integrity: sha512-AYnb1nQyY49te+VRAVgmzfcgjYS91mY5P0TKUDCLEM+gNnA+3T6rWITXRLYCpahpqSQbN5cE+gHpnPyXjHWxcw==}
-
   '@types/estree@1.0.8':
     resolution: {integrity: sha512-dWHzHa2WqEXI/O1E9OjrocMTKJl2mSrEolh1Iomrv6U+JuNwaHXsXx9bLu5gG7BUWFIN0skIQJQ/L1rIex4X6w==}
 
@@ -1292,11 +1131,11 @@ packages:
   '@ungap/structured-clone@1.2.0':
     resolution: {integrity: sha512-zuVdFrMJiuCDQUMCzQaD6KL28MjnqqN8XnAqiEq9PNm/hCPTSGfrXCOfwj1ow4LFb/tNymJPwsNbVePc1xFqrQ==}
 
-  '@vitest/expect@4.0.5':
-    resolution: {integrity: sha512-DJctLVlKoddvP/G389oGmKWNG6GD9frm2FPXARziU80Rjo7SIYxQzb2YFzmQ4fVD3Q5utUYY8nUmWrqsuIlIXQ==}
+  '@vitest/expect@4.0.15':
+    resolution: {integrity: sha512-Gfyva9/GxPAWXIWjyGDli9O+waHDC0Q0jaLdFP1qPAUUfo1FEXPXUfUkp3eZA0sSq340vPycSyOlYUeM15Ft1w==}
 
-  '@vitest/mocker@4.0.5':
-    resolution: {integrity: sha512-iYHIy72LfbK+mL5W8zXROp6oOcJKXWeKcNjcPPsqoa18qIEDrhB6/Z08o0wRajTd6SSSDNw8NCSIHVNOMpz0mw==}
+  '@vitest/mocker@4.0.15':
+    resolution: {integrity: sha512-CZ28GLfOEIFkvCFngN8Sfx5h+Se0zN+h4B7yOsPVCcgtiO7t5jt9xQh2E1UkFep+eb9fjyMfuC5gBypwb07fvQ==}
     peerDependencies:
       msw: ^2.4.9
       vite: ^6.0.0 || ^7.0.0-0
@@ -1306,40 +1145,40 @@ packages:
       vite:
         optional: true
 
-  '@vitest/pretty-format@4.0.5':
-    resolution: {integrity: sha512-t1T/sSdsYyNc5AZl0EMeD0jW9cpJe2cODP0R++ZQe1kTkpgrwEfxGFR/yCG4w8ZybizbXRTHU7lE8sTDD/QsGw==}
+  '@vitest/pretty-format@4.0.15':
+    resolution: {integrity: sha512-SWdqR8vEv83WtZcrfLNqlqeQXlQLh2iilO1Wk1gv4eiHKjEzvgHb2OVc3mIPyhZE6F+CtfYjNlDJwP5MN6Km7A==}
 
-  '@vitest/runner@4.0.5':
-    resolution: {integrity: sha512-CQVVe+YEeKSiFBD5gBAmRDQglm4PnMBYzeTmt06t5iWtsUN9StQeeKhYCea/oaqBYilf8sARG6fSctUcEL/UmQ==}
+  '@vitest/runner@4.0.15':
+    resolution: {integrity: sha512-+A+yMY8dGixUhHmNdPUxOh0la6uVzun86vAbuMT3hIDxMrAOmn5ILBHm8ajrqHE0t8R9T1dGnde1A5DTnmi3qw==}
 
-  '@vitest/snapshot@4.0.5':
-    resolution: {integrity: sha512-jfmSAeR6xYNEvcD+/RxFGA1bzpqHtkVhgxo2cxXia+Q3xX7m6GpZij07rz+WyQcA/xEGn4eIS1OItkMyWsGBmQ==}
+  '@vitest/snapshot@4.0.15':
+    resolution: {integrity: sha512-A7Ob8EdFZJIBjLjeO0DZF4lqR6U7Ydi5/5LIZ0xcI+23lYlsYJAfGn8PrIWTYdZQRNnSRlzhg0zyGu37mVdy5g==}
 
-  '@vitest/spy@4.0.5':
-    resolution: {integrity: sha512-TUmVQpAQign7r8+EnZsgTF3vY9BdGofTUge1rGNbnHn2IN3FChiQoT9lrPz7A7AVUZJU2LAZXl4v66HhsNMhoA==}
+  '@vitest/spy@4.0.15':
+    resolution: {integrity: sha512-+EIjOJmnY6mIfdXtE/bnozKEvTC4Uczg19yeZ2vtCz5Yyb0QQ31QWVQ8hswJ3Ysx/K2EqaNsVanjr//2+P3FHw==}
 
-  '@vitest/utils@4.0.5':
-    resolution: {integrity: sha512-V5RndUgCB5/AfNvK9zxGCrRs99IrPYtMTIdUzJMMFs9nrmE5JXExIEfjVtUteyTRiLfCm+dCRMHf/Uu7Mm8/dg==}
+  '@vitest/utils@4.0.15':
+    resolution: {integrity: sha512-HXjPW2w5dxhTD0dLwtYHDnelK3j8sR8cWIaLxr22evTyY6q8pRCjZSmhRWVjBaOVXChQd6AwMzi9pucorXCPZA==}
 
-  '@volar/kit@2.4.11':
-    resolution: {integrity: sha512-ups5RKbMzMCr6RKafcCqDRnJhJDNWqo2vfekwOAj6psZ15v5TlcQFQAyokQJ3wZxVkzxrQM+TqTRDENfQEXpmA==}
+  '@volar/kit@2.4.27':
+    resolution: {integrity: sha512-ilZoQDMLzqmSsImJRWx4YiZ4FcvvPrPnFVmL6hSsIWB6Bn3qc7k88J9yP32dagrs5Y8EXIlvvD/mAFaiuEOACQ==}
     peerDependencies:
       typescript: '*'
 
-  '@volar/language-core@2.4.11':
-    resolution: {integrity: sha512-lN2C1+ByfW9/JRPpqScuZt/4OrUUse57GLI6TbLgTIqBVemdl1wNcZ1qYGEo2+Gw8coYLgCy7SuKqn6IrQcQgg==}
+  '@volar/language-core@2.4.27':
+    resolution: {integrity: sha512-DjmjBWZ4tJKxfNC1F6HyYERNHPYS7L7OPFyCrestykNdUZMFYzI9WTyvwPcaNaHlrEUwESHYsfEw3isInncZxQ==}
 
-  '@volar/language-server@2.4.11':
-    resolution: {integrity: sha512-W9P8glH1M8LGREJ7yHRCANI5vOvTrRO15EMLdmh5WNF9sZYSEbQxiHKckZhvGIkbeR1WAlTl3ORTrJXUghjk7g==}
+  '@volar/language-server@2.4.27':
+    resolution: {integrity: sha512-SymGNkErcHg8GjiG65iQN8sLkhqu1pwKhFySmxeBuYq5xFYagKBW36eiNITXQTdvT0tutI1GXcXdq/FdE/IyjA==}
 
-  '@volar/language-service@2.4.11':
-    resolution: {integrity: sha512-KIb6g8gjUkS2LzAJ9bJCLIjfsJjeRtmXlu7b2pDFGD3fNqdbC53cCAKzgWDs64xtQVKYBU13DLWbtSNFtGuMLQ==}
+  '@volar/language-service@2.4.27':
+    resolution: {integrity: sha512-SxKZ8yLhpWa7Y5e/RDxtNfm7j7xsXp/uf2urijXEffRNpPSmVdfzQrFFy5d7l8PNpZy+bHg+yakmqBPjQN+MOw==}
 
-  '@volar/source-map@2.4.11':
-    resolution: {integrity: sha512-ZQpmafIGvaZMn/8iuvCFGrW3smeqkq/IIh9F1SdSx9aUl0J4Iurzd6/FhmjNO5g2ejF3rT45dKskgXWiofqlZQ==}
+  '@volar/source-map@2.4.27':
+    resolution: {integrity: sha512-ynlcBReMgOZj2i6po+qVswtDUeeBRCTgDurjMGShbm8WYZgJ0PA4RmtebBJ0BCYol1qPv3GQF6jK7C9qoVc7lg==}
 
-  '@volar/typescript@2.4.11':
-    resolution: {integrity: sha512-2DT+Tdh88Spp5PyPbqhyoYavYCPDsqbHLFwcUI9K1NlY1YgUJvujGdrqUp0zWxnW7KWNTr3xSpMuv2WnaTKDAw==}
+  '@volar/typescript@2.4.27':
+    resolution: {integrity: sha512-eWaYCcl/uAPInSK2Lze6IqVWaBu/itVqR5InXcHXFyles4zO++Mglt3oxdgj75BDcv1Knr9Y93nowS8U3wqhxg==}
 
   '@vscode/emmet-helper@2.9.3':
     resolution: {integrity: sha512-rB39LHWWPQYYlYfpv9qCoZOVioPCftKXXqrsyqN1mTWZM6dTnONT63Db+03vgrBbHzJN45IrgS/AGxw9iiqfEw==}
@@ -1357,6 +1196,14 @@ packages:
     engines: {node: '>=0.4.0'}
     hasBin: true
 
+  ajv-draft-04@1.0.0:
+    resolution: {integrity: sha512-mv00Te6nmYbRp5DCwclxtt7yV/joXJPGS7nM+97GdxvuttCOfgI3K4U25zboyeX0O+myI8ERluxQe5wljMmVIw==}
+    peerDependencies:
+      ajv: ^8.5.0
+    peerDependenciesMeta:
+      ajv:
+        optional: true
+
   ajv@8.17.1:
     resolution: {integrity: sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==}
 
@@ -1371,6 +1218,10 @@ packages:
     resolution: {integrity: sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==}
     engines: {node: '>=12'}
 
+  ansi-regex@6.2.2:
+    resolution: {integrity: sha512-Bq3SmSpyFHaWjPk8If9yc6svM8c56dB5BAtW4Qbw5jHTwwXXcTLoRMkpDJp6VL0XzlWaCHTXrkFURMYmD0sLqg==}
+    engines: {node: '>=12'}
+
   ansi-styles@4.3.0:
     resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
     engines: {node: '>=8'}
@@ -1415,8 +1266,8 @@ packages:
     peerDependencies:
       astro: ^4.0.0-beta || ^5.0.0-beta || ^3.3.0
 
-  astro-mermaid@1.1.0:
-    resolution: {integrity: sha512-eW5aqOISq2Uf8goCedSl12d0qy8y77A+jRwKxwYc7LvrEN9HiCQuwTGu3zQvi0mB4+ydwaueaYbFUFSCIs2jrA==}
+  astro-mermaid@1.2.0:
+    resolution: {integrity: sha512-zELK0l0QUJaHBul9uijTr7SP+MN4LherN4sAC4xE7nx8I/TQoEtB36pnyEDMROZY3T3s4Eojw5CC/ezEBKi9RQ==}
     peerDependencies:
       '@mermaid-js/layout-elk': ^0.2.0
       astro: ^4.0.0 || ^5.0.0
@@ -1425,8 +1276,8 @@ packages:
       '@mermaid-js/layout-elk':
         optional: true
 
-  astro@5.15.2:
-    resolution: {integrity: sha512-xQQ+PiYJ7WpUJrHJpAb52TQAUCFmSR8lAtQr3tFfSIZoTQiEMFx3HITJ01t3eDUpHjja8J6JcYqgAhr9xygKQg==}
+  astro@5.16.5:
+    resolution: {integrity: sha512-QeuM4xzTR0QuXFDNlGVW0BW7rcquKFIkylaPeM4ufii0/RRiPTYtwxDYVZ3KfiMRuuc+nbLD0214kMKTvz/yvQ==}
     engines: {node: 18.20.8 || ^20.3.0 || >=22.0.0, npm: '>=9.6.5', pnpm: '>=7.1.0'}
     hasBin: true
 
@@ -1474,18 +1325,14 @@ packages:
   ccount@2.0.1:
     resolution: {integrity: sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==}
 
-  chai@6.2.0:
-    resolution: {integrity: sha512-aUTnJc/JipRzJrNADXVvpVqi6CO0dn3nx4EVPxijri+fj3LUUDyZQOgVeW54Ob3Y1Xh9Iz8f+CgaCl8v0mn9bA==}
+  chai@6.2.1:
+    resolution: {integrity: sha512-p4Z49OGG5W/WBCPSS/dH3jQ73kD6tiMmUM+bckNK6Jr5JHMG3k9bg/BvKR8lKmtVBKmOiuVaV2ws8s9oSbwysg==}
     engines: {node: '>=18'}
 
   chalk-template@1.1.2:
     resolution: {integrity: sha512-2bxTP2yUH7AJj/VAXfcA+4IcWGdQ87HwBANLt5XxGTeomo8yG0y95N1um9i5StvhT/Bl0/2cARA5v1PpPXUxUA==}
     engines: {node: '>=14.16'}
 
-  chalk@5.4.1:
-    resolution: {integrity: sha512-zgVZuo2WcZgfUEmsn6eO3kINexW8RAE4maiQ8QNs8CtpPCSyMiYsULR3HQYkm3w8FIA3SberyMJMSldGsW+U3w==}
-    engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
-
   chalk@5.6.2:
     resolution: {integrity: sha512-7NzBL0rN6fMUW+f7A6Io4h40qQlG+xGmtMxfbnH/K7TAtt8JQWVQK+6g0UXKMeVJoyV5EkkNsErQ8pVD3bLHbA==}
     engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
@@ -1551,6 +1398,10 @@ packages:
   comma-separated-tokens@2.0.3:
     resolution: {integrity: sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==}
 
+  commander@11.1.0:
+    resolution: {integrity: sha512-yPVavfyCcRhmorC7rWlkHn15b4wDVgVmBA7kV4QVBsF7kv/9TKJAbAXVTxvTnwP8HHKjRCJDClKbciiYS7p0DQ==}
+    engines: {node: '>=16'}
+
   commander@14.0.2:
     resolution: {integrity: sha512-TywoWNNRbhoD0BXs1P3ZEScW8W5iKrnbithIl0YH+uCmBd0QpPOA8yc82DS3BIE5Ma6FnBVUsJ7wVUDz4dvOWQ==}
     engines: {node: '>=20'}
@@ -1595,57 +1446,72 @@ packages:
   crossws@0.3.5:
     resolution: {integrity: sha512-ojKiDvcmByhwa8YYqbQI/hg7MEU0NC03+pSdEq4ZUnZR9xXpwk7E43SMNGkn+JxJGPFtNvQ48+vV2p+P1ml5PA==}
 
-  cspell-config-lib@9.2.2:
-    resolution: {integrity: sha512-Fp3jdFxb5gxcQP146TfNVmDqXKfm3xmcEUr1K829DmAFwhc7s+/pCRjhBPoGfQt6U7ugpxjkSx2gGKSbLhp7Mg==}
+  cspell-config-lib@9.4.0:
+    resolution: {integrity: sha512-CvQKSmK/DRIf3LpNx2sZth65pHW2AHngZqLkH3DTwnAPbiCAsE0XvCrVhvDfCNu/6uJIaa+NVHSs8GOf//DHBQ==}
     engines: {node: '>=20'}
 
-  cspell-dictionary@9.2.2:
-    resolution: {integrity: sha512-lnoCFoCAaiFJi+Hz22t+tdTj76jyTA76EYFKhmf/dbj5UO6kVy8by08uFfUbbMaC9Oi09YHnI62P/e+LBx1v8Q==}
+  cspell-dictionary@9.4.0:
+    resolution: {integrity: sha512-c2qscanRZChoHZFYI7KpvBMdy8i6wNwl2EflcNRrFiFOq67t9CgxLe54PafaqhrHGpBc8nElaZKciLvjj6Uscw==}
     engines: {node: '>=20'}
 
-  cspell-gitignore@9.2.2:
-    resolution: {integrity: sha512-Idx3IVKTpnGoyRlkj8F/lSWtWiJpqLhXmZglTzfGWxzbik8E0aQmSyT3blbNWhZL/K1JqlTjbSiAICVMoWTkhA==}
+  cspell-gitignore@9.4.0:
+    resolution: {integrity: sha512-HMrzLmJBUMSpaMMkltlTAz/aVOrHxixyhKfg5WbFCJ5JYZO6Qu3/JU3wRoOFoud9449wRjLkvrGmbbL2+vO6Lw==}
     engines: {node: '>=20'}
     hasBin: true
 
-  cspell-glob@9.2.2:
-    resolution: {integrity: sha512-6mhUk4iLu5YzY9PE86ZyAjNFjM7TD8Oh4btJ7ZV+edzJjdVjFugXWyefPXCGNfuvpaJqpuoLDwMvNHJxUmLwbg==}
+  cspell-glob@9.4.0:
+    resolution: {integrity: sha512-Q87Suj9oXrhoKck15qWorCizBjMNxG/k3NjnhKIAMrF+PdUa1Mpl0MOD+hqV1Wvwh1UHcIMYCP3bR3XpBbNx+Q==}
     engines: {node: '>=20'}
 
-  cspell-grammar@9.2.2:
-    resolution: {integrity: sha512-m0aozo5gjZYL5Vm3/9D0/yLZJTsVJAP8VeRVljN4u5T7w+WY+LsnvKSZhnkOvsT3kCJDhcKEkMVkCo8d/7EcAQ==}
+  cspell-grammar@9.4.0:
+    resolution: {integrity: sha512-ie7OQ4Neflo+61bMzoLR7GtlZfMBAm2KL1U4iNqh15wUE5fDbvXeN15H5lu+gcO8BwYvC5wxZknw1x62/J8+3Q==}
     engines: {node: '>=20'}
     hasBin: true
 
-  cspell-io@9.2.2:
-    resolution: {integrity: sha512-Rpky4woeB6/1VUCk7DtRm94A6c5XRbhcj5dUZh851EpZ0ItEz3S9+MhkX8g1sTVkDg6Hln1pu+Nbm9dFIpGkGA==}
+  cspell-io@9.4.0:
+    resolution: {integrity: sha512-8w30dqlO54H9w6WGlvZhHI5kytVbF3bYPqKJAZLWKEO36L2mdpf6/abx/FA4yVLJ56wmH1x0N0ZK32wNRl5C6A==}
     engines: {node: '>=20'}
 
-  cspell-lib@9.2.2:
-    resolution: {integrity: sha512-ksy+5vCSZz7ECUDlLA8ZGNEcWmnzl5bMe4IEPHAMaPFY3iWNsG7dXBrae1dj/b/3HqVqOdXPdwjnGAyZciissg==}
+  cspell-lib@9.4.0:
+    resolution: {integrity: sha512-ajjioE59IEDNUPawfaBpiMfGC32iKPkuYd4T9ftguuef8VvyKRifniiUi1nxwGgAhzSfxHvWs7qdT+29Pp5TMQ==}
     engines: {node: '>=20'}
 
-  cspell-trie-lib@9.2.2:
-    resolution: {integrity: sha512-84L0Or6xkfnDMmxx2BtuaqsM4LOVCgnG4ZzMMgwQJU+9nSOAHs0ULNWQTHLbsCF+FFG/siILpUkIc3z+UxjGFw==}
+  cspell-trie-lib@9.4.0:
+    resolution: {integrity: sha512-bySJTm8XDiJAoC1MDo4lE/KpSNxydo13ZETC8TF7Hb3rbWI1c6o5eZ4+i/tkG3M94OvKV91+MeAvoMCe7GGgAw==}
     engines: {node: '>=20'}
 
-  cspell@9.2.2:
-    resolution: {integrity: sha512-D9jxXlYWIxUw4IjicxrmK83n5BzuQVZaIhsDsfRiH7iP4F71gDtKR9b+UgmXevvseN7OH4LkdyaPKzjNliGAbg==}
+  cspell@9.4.0:
+    resolution: {integrity: sha512-ZvXO+EY/G0/msu7jwRiVk0sXL/zB7DMJLBvjSUrK82uVbDoDxHwXxUuOz2UVnk2+J61//ldIZrjxVK8KMvaJlg==}
     engines: {node: '>=20'}
     hasBin: true
 
+  css-select@5.2.2:
+    resolution: {integrity: sha512-TizTzUddG/xYLA3NXodFM0fSbNizXjOKhqiQQwvhlspadZokn1KDy0NZFS0wuEubIYAV5/c1/lAr0TaaFXEXzw==}
+
   css-selector-parser@3.0.5:
     resolution: {integrity: sha512-3itoDFbKUNx1eKmVpYMFyqKX04Ww9osZ+dLgrk6GEv6KMVeXUhUnp4I5X+evw+u3ZxVU6RFXSSRxlTeMh8bA+g==}
 
+  css-tree@2.2.1:
+    resolution: {integrity: sha512-OA0mILzGc1kCOCSJerOeqDxDQ4HOh+G8NbOJFOTgOCzpw7fCBubk0fEyxp8AgOL/jvLgYA/uV0cMbe43ElF1JA==}
+    engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'}
+
   css-tree@3.1.0:
     resolution: {integrity: sha512-0eW44TGN5SQXU1mWSkKwFstI/22X2bG1nYzZTYMAWjylYURhse752YgbE4Cx46AC+bAvI+/dYTPRk1LqSUnu6w==}
     engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0}
 
+  css-what@6.2.2:
+    resolution: {integrity: sha512-u/O3vwbptzhMs3L1fQE82ZSLHQQfto5gyZzwteVIEyeaY5Fc7R4dapF/BvRoSYFeqfBk4m0V1Vafq5Pjv25wvA==}
+    engines: {node: '>= 6'}
+
   cssesc@3.0.0:
     resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==}
     engines: {node: '>=4'}
     hasBin: true
 
+  csso@5.0.5:
+    resolution: {integrity: sha512-0LrrStPOdJj+SPCCrGhzryycLjwcgUSHBtxNA8aIDxf0GLsRh1cKYhB00Gd1lDOS4yGH69+SNn13+TWbVHETFQ==}
+    engines: {node: ^10 || ^12.20.0 || ^14.13.0 || >=15.0.0, npm: '>=7.0.0'}
+
   cytoscape-cose-bilkent@4.1.0:
     resolution: {integrity: sha512-wgQlVIUJF13Quxiv5e1gstZ08rnZj2XaLHGoFMYXz7SkNfCDOOteKBE6SYRfA9WxxI/iBc3ajfDoc6hb/MRAHQ==}
     peerDependencies:
@@ -1827,9 +1693,6 @@ packages:
     resolution: {integrity: sha512-0je+qPKHEMohvfRTCEo3CrPG6cAzAYgmzKyxRiYSSDkS6eGJdyVJm7WaYA5ECaAD9wLB2T4EEeymA5aFVcYXCA==}
     engines: {node: '>=6'}
 
-  destr@2.0.3:
-    resolution: {integrity: sha512-2N3BOUU4gYMpTP24s5rF5iP7BDr7uNTCs4ozw3kf/eKfvWSIu93GEBi5m427YoyJoeOzQ5smuu4nNAPGb8idSQ==}
-
   destr@2.0.5:
     resolution: {integrity: sha512-ugFTXCtDZunbzasqBxrK93Ik/DRYsO6S/fedkWEMKqt04xZ4csmnmwGDBAb07QWNaGMAmnTIemsYZCksjATwsA==}
 
@@ -1841,8 +1704,8 @@ packages:
     resolution: {integrity: sha512-KxektNH63SrbfUyDiwXqRb1rLwKt33AmMv+5Nhsw1kqZ13SJBRTgZHtGbE+hH3a1mVW1cz+4pqSWVPAtLVXTzQ==}
     engines: {node: '>=18'}
 
-  devalue@5.4.2:
-    resolution: {integrity: sha512-MwPZTKEPK2k8Qgfmqrd48ZKVvzSQjgW0lXLxiIBA8dQjtf/6mw6pggHNLcyDKyf+fI6eXxlQwPsfaCMTU5U+Bw==}
+  devalue@5.6.1:
+    resolution: {integrity: sha512-jDwizj+IlEZBunHcOuuFVBnIMPAEHvTsJj0BcIp94xYguLRVBcXO853px/MyIJvbVzWdsGvrRweIUWJw8hBP7A==}
 
   devlop@1.1.0:
     resolution: {integrity: sha512-RWmIqhcFf1lRYBvNmr7qTNuyCt/7/ns2jbpp1+PalgE/rDQcBT0fioSMUpJ93irlUhC5hrg4cYqe6U+0ImW0rA==}
@@ -1861,9 +1724,22 @@ packages:
   dlv@1.1.3:
     resolution: {integrity: sha512-+HlytyjlPKnIG8XuRG8WvmBP8xs8P71y+SKKS6ZXWoEgLuePxtDoUEiH7WkdePWrQ5JBpE6aoVqfZfJUQkjXwA==}
 
+  dom-serializer@2.0.0:
+    resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==}
+
+  domelementtype@2.3.0:
+    resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==}
+
+  domhandler@5.0.3:
+    resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==}
+    engines: {node: '>= 4'}
+
   dompurify@3.2.6:
     resolution: {integrity: sha512-/2GogDQlohXPZe6D6NOgQvXLPSYBqIWMnZ8zzOhn09REE4eyAzb+Hed3jhoM9OkuaJ8P6ZGTTVWQKAi8ieIzfQ==}
 
+  domutils@3.2.2:
+    resolution: {integrity: sha512-6kZKyUajlDuqlHKVX1w7gyslj9MPIXzIFiz/rGu35uC1wMi+kMhQwGhl4lt9unC9Vb9INnY9Z3/ZA3+FhASLaw==}
+
   dset@3.1.4:
     resolution: {integrity: sha512-2QF/g9/zTaPDc3BjNcVTGoBbXBgYfMTTceLaYcFJ/W9kggFUkhxD/hMEeuLKbugyef9SqAx8cpgwlIP/jinUTA==}
     engines: {node: '>=4'}
@@ -1894,11 +1770,6 @@ packages:
   esast-util-from-js@2.0.1:
     resolution: {integrity: sha512-8Ja+rNJ0Lt56Pcf3TAmpBZjmx8ZcK5Ts4cAzIOjsjevg9oSXJnl6SUQ2EevU8tv3h6ZLWmoKL5H4fgWvdvfETw==}
 
-  esbuild@0.24.2:
-    resolution: {integrity: sha512-+9egpBW8I3CD5XPe0n6BfT5fxLzxrlDzqydF3aviG+9ni1lDC/OvMHcxqEFV0+LANZG5R1bFMWfUrjVsdwxJvA==}
-    engines: {node: '>=18'}
-    hasBin: true
-
   esbuild@0.25.11:
     resolution: {integrity: sha512-KohQwyzrKTQmhXDW1PjCv3Tyspn9n5GcY2RTDqeORIdIJY8yKIF7sTSopFmn/wpMPW4rdPXI0UE5LJLuq3bx0Q==}
     engines: {node: '>=18'}
@@ -1964,8 +1835,8 @@ packages:
   fast-deep-equal@3.1.3:
     resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==}
 
-  fast-equals@5.3.2:
-    resolution: {integrity: sha512-6rxyATwPCkaFIL3JLqw8qXqMpIZ942pTX/tbQFkRsDGblS8tNGtlUauA/+mt6RUfqn/4MoEr+WDkYoIQbibWuQ==}
+  fast-equals@5.4.0:
+    resolution: {integrity: sha512-jt2DW/aNFNwke7AUd+Z+e6pz39KO5rzdbbFCg2sGafS4mk13MI7Z8O5z9cADNn5lhGODIgLwug6TZO2ctf7kcw==}
     engines: {node: '>=6.0.0'}
 
   fast-glob@3.3.3:
@@ -2012,9 +1883,9 @@ packages:
     engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
     os: [darwin]
 
-  gensequence@7.0.0:
-    resolution: {integrity: sha512-47Frx13aZh01afHJTB3zTtKIlFI6vWY+MYCN9Qpew6i52rfKjnhCF/l1YlC8UmEMvvntZZ6z4PiCcmyuedR2aQ==}
-    engines: {node: '>=18'}
+  gensequence@8.0.8:
+    resolution: {integrity: sha512-omMVniXEXpdx/vKxGnPRoO2394Otlze28TyxECbFVyoSpZ9H3EO7lemjcB12OpQJzRW4e5tt/dL1rOxry6aMHg==}
+    engines: {node: '>=20'}
 
   get-caller-file@2.0.5:
     resolution: {integrity: sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==}
@@ -2082,9 +1953,6 @@ packages:
   hast-util-to-estree@3.1.0:
     resolution: {integrity: sha512-lfX5g6hqVh9kjS/B9E2gSkvHH4SZNiQFiqWS0x9fENzEl+8W12RqdRxX6d/Cwxi30tPQs3bIO+aolQJNp1bIyw==}
 
-  hast-util-to-html@9.0.4:
-    resolution: {integrity: sha512-wxQzXtdbhiwGAUKrnQJXlOPmHnEehzphwkK7aluUPQ+lEc1xefC8pblMgpp2w5ldBTEfveRIrADcrhGIWrlTDA==}
-
   hast-util-to-html@9.0.5:
     resolution: {integrity: sha512-OguPdidb+fbHQSU4Q4ZiLKnzWo8Wwsf5bZfbvu7//a9oTYoqD/fWpe96NuHkoS9h0ccGOTe0C4NGXdtS0iObOw==}
 
@@ -2213,6 +2081,10 @@ packages:
     resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==}
     hasBin: true
 
+  js-yaml@4.1.1:
+    resolution: {integrity: sha512-qQKT4zQxXl8lLwBtHMWwaTcGfFOZviOJet3Oy/xmGk2gZH677CJM9EvtfdSkgWcATZhj/55JZ0rmy3myCT5lsA==}
+    hasBin: true
+
   json-schema-traverse@1.0.0:
     resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==}
 
@@ -2277,8 +2149,8 @@ packages:
   magic-string@0.30.21:
     resolution: {integrity: sha512-vd2F4YUyEXKGcLHoq+TEyCjxueSeHnFxyyjNp80yg0XV4vUhnDer/lvvlqM/arB5bXQN5K2/3oinyCRyx8T2CQ==}
 
-  magicast@0.3.5:
-    resolution: {integrity: sha512-L0WhttDl+2BOsybvEOLK7fW3UA0OQ0IQ2d6Zl2x/a6vVRs3bAY0ECOSHHeL5jD+SbOpOCUEi0y1DgHEn9Qn1AQ==}
+  magicast@0.5.1:
+    resolution: {integrity: sha512-xrHS24IxaLrvuo613F719wvOIv9xPHFWQHuvGUBmPnCA/3MQxKI3b+r7n1jAoDHmsbC5bRhTZYR77invLAxVnw==}
 
   markdown-extensions@2.0.0:
     resolution: {integrity: sha512-o5vL7aDWatOTX8LzaS1WMoaoxIiLRQJuIKKe2wAw6IeULDHaqbiqiggmx+pKvZDb1Sj+pE46Sn1T7lCqfFtg1Q==}
@@ -2346,6 +2218,9 @@ packages:
   mdast-util-to-string@4.0.0:
     resolution: {integrity: sha512-0H44vDimn51F0YwvxSJSm0eCDOJTRlmN0R1yBh4HLj9wiV1Dn0QoXGbvFAWj2hSItVTlCmBF1hqKlIyUBVFLPg==}
 
+  mdn-data@2.0.28:
+    resolution: {integrity: sha512-aylIc7Z9y4yzHYAJNuESG3hfhC+0Ibp/MAMiaOZgNv4pmEdFyfZhhhny4MNiAfWdBQ1RQ2mfDWmM1x8SvGyp8g==}
+
   mdn-data@2.12.2:
     resolution: {integrity: sha512-IEn+pegP1aManZuckezWCO+XZQDplx1366JoVhTpMpBB1sPey/SbveZQUosKiKiGYjg1wH4pMlNgXbCiYgihQA==}
 
@@ -2353,8 +2228,8 @@ packages:
     resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==}
     engines: {node: '>= 8'}
 
-  mermaid@11.12.1:
-    resolution: {integrity: sha512-UlIZrRariB11TY1RtTgUWp65tphtBv4CSq7vyS2ZZ2TgoMjs2nloq+wFqxiwcxlhHUvs7DPGgMjs2aeQxz5h9g==}
+  mermaid@11.12.2:
+    resolution: {integrity: sha512-n34QPDPEKmaeCG4WDMGy0OT6PSyxKCfy2pJgShP+Qow2KLrvWjclwbc3yXfSIf4BanqWEhQEpngWwNp/XhZt6w==}
 
   micromark-core-commonmark@2.0.1:
     resolution: {integrity: sha512-CUQyKr1e///ZODyD1U3xit6zXwy1a8q2a1S1HKtIlmgvurrEpaw/Y9y6KSIbF8P59cn/NjzHyO+Q2fAyYLQrAA==}
@@ -2486,11 +2361,6 @@ packages:
     engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
     hasBin: true
 
-  nanoid@3.3.8:
-    resolution: {integrity: sha512-WNLf5Sd8oZxOm+TzppcYk8gVOgP+l58xNy58D0nbUnOxOWRWvlcCV4kUF7ltmI6PsrLl/BgKEyS4mqsGChFN0w==}
-    engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
-    hasBin: true
-
   neotraverse@0.6.18:
     resolution: {integrity: sha512-Z4SmBUweYa09+o6pG+eASabEpP6QkQ70yHj351pQoEXIs8uHbaU2DWVmzBANKgflPa47A50PtB2+NgRpQvr7vA==}
     engines: {node: '>= 10'}
@@ -2498,9 +2368,6 @@ packages:
   nlcst-to-string@4.0.0:
     resolution: {integrity: sha512-YKLBCcUYKAg0FNlOBT6aI91qFmSiFKiluk655WzPF+DDMA02qIyy8uiRqI8QXtcFpEvll12LpL5MXqEmAZ+dcA==}
 
-  node-fetch-native@1.6.6:
-    resolution: {integrity: sha512-8Mc2HhqPdlIfedsuZoc3yioPuzp6b+L5jRCRY1QzuWZh2EGJVQrGppC6V6cF0bLdbW0+O2YpqCA25aF/1lvipQ==}
-
   node-fetch-native@1.6.7:
     resolution: {integrity: sha512-g9yhqoedzIUm0nTnTqAQvueMPVOuIY16bqgAJJC8XOOubYFNwz6IER9qs0Gq2Xd0+CecCKFjtdDTMA4u4xG06Q==}
 
@@ -2517,9 +2384,15 @@ packages:
   nth-check@2.1.1:
     resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==}
 
+  obug@2.1.1:
+    resolution: {integrity: sha512-uTqF9MuPraAQ+IsnPf366RG4cP9RtUi7MLO1N3KEc+wb0a6yKpeL0lmk2IB1jY5KHPAlTc6T/JRdC/YqxHNwkQ==}
+
   ofetch@1.4.1:
     resolution: {integrity: sha512-QZj2DfGplQAr2oj9KzceK9Hwz6Whxazmn85yYeVuS3u9XTMOGMRx0kO95MQ+vLsj/S/NwBDMMLU5hpxvI6Tklw==}
 
+  ofetch@1.5.1:
+    resolution: {integrity: sha512-2W4oUZlVaqAPAil6FUg/difl6YhqhUR7x2eZY4bQCko22UXg3hptq9KLQdqFClV+Wu85UX7hNtdGTngi/1BxcA==}
+
   ohash@2.0.11:
     resolution: {integrity: sha512-RdR9FQrFwNBNXAr4GixM8YaRZRJ5PUWbKYbE5eOsrwAjJW0q2REGcf79oYPsLyskQCZG1PLN+S/K1V00joZAoQ==}
 
@@ -2529,12 +2402,15 @@ packages:
   oniguruma-to-es@4.3.3:
     resolution: {integrity: sha512-rPiZhzC3wXwE59YQMRDodUwwT9FZ9nNBwQQfsd1wfdtlKEyCdRV0avrTcSZ5xlIvGRVPd/cx6ZN45ECmS39xvg==}
 
+  oniguruma-to-es@4.3.4:
+    resolution: {integrity: sha512-3VhUGN3w2eYxnTzHn+ikMI+fp/96KoRSVK9/kMTcFqj1NRDh2IhQCKvYxDnWePKRXY/AqH+Fuiyb7VHSzBjHfA==}
+
   p-limit@6.2.0:
     resolution: {integrity: sha512-kuUqqHNUqoIWp/c467RI4X6mmyuojY5jGutNU0wVTmEOOfcuwLqyMVoAi9MKi2Ak+5i9+nhmrK4ufZE8069kHA==}
     engines: {node: '>=18'}
 
-  p-queue@8.1.0:
-    resolution: {integrity: sha512-mxLDbbGIBEXTJL0zEx8JIylaj3xQ7Z/7eEVjcF9fJX4DBiH9oqe+oahYnlKKxm0Ci9TlWTyhSHgygxMxjIB2jw==}
+  p-queue@8.1.1:
+    resolution: {integrity: sha512-aNZ+VfjobsWryoiPnEApGGmf5WmNsCo9xu8dfaYamG5qaLP7ClhLN6NgsFe6SwJ2UbLEBK5dv9x8Mn5+RVhMWQ==}
     engines: {node: '>=18'}
 
   p-timeout@6.1.2:
@@ -2544,6 +2420,9 @@ packages:
   package-manager-detector@1.3.0:
     resolution: {integrity: sha512-ZsEbbZORsyHuO00lY1kV3/t72yp6Ysay6Pd17ZAlNGuGwmWDLCJxFpRs0IzfXfj1o4icJOkUEioexFHzyPurSQ==}
 
+  package-manager-detector@1.6.0:
+    resolution: {integrity: sha512-61A5ThoTiDG/C8s8UMZwSorAGwMJ0ERVGj2OjoW5pAalsNOg15+iQiPzrLJ4jhZ1HJzmC2PIHT2oEiH3R5fzNA==}
+
   pagefind@1.3.0:
     resolution: {integrity: sha512-8KPLGT5g9s+olKMRTU9LFekLizkVIu9tes90O1/aigJ0T5LmyPqTzGJrETnSw3meSYg58YH7JTzhTTW/3z6VAw==}
     hasBin: true
@@ -2577,6 +2456,9 @@ packages:
   pathe@2.0.3:
     resolution: {integrity: sha512-WUjGcAqP1gQacoQe+OBJsFA7Ld4DyXuUIjZ5cc75cLHvJ7dtNsTugphxIADwspS+AraAUePCKrSVtPLFj/F88w==}
 
+  piccolore@0.1.3:
+    resolution: {integrity: sha512-o8bTeDWjE086iwKrROaDf31K0qC/BENdm15/uH9usSC/uZjJOKb2YGiVHfLY4GhwsERiPI1jmwI2XrA7ACOxVw==}
+
   picocolors@1.1.1:
     resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
 
@@ -2610,17 +2492,13 @@ packages:
     resolution: {integrity: sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==}
     engines: {node: '>=4'}
 
-  postcss@8.5.2:
-    resolution: {integrity: sha512-MjOadfU3Ys9KYoX0AdkBlFEF1Vx37uCCeN4ZHnmwm9FfpbsGWMZeBLMmmpY+6Ocqod7mkdZ0DT31OlbsFrLlkA==}
-    engines: {node: ^10 || ^12 || >=14}
-
   postcss@8.5.6:
     resolution: {integrity: sha512-3Ybi1tAuwAP9s0r1UQ2J4n5Y0G05bJkpUIO0/bI9MhwmD70S5aTWbXGBwxHrelT+XM1k6dM0pk+SwNkpTRN7Pg==}
     engines: {node: ^10 || ^12 || >=14}
 
-  prettier@2.8.7:
-    resolution: {integrity: sha512-yPngTo3aXUUmyuTjeTUT75txrf+aMh9FiD7q9ZE/i6r0bPb22g4FsE6Y338PQX1bmfy08i9QQCB7/rcUAVntfw==}
-    engines: {node: '>=10.13.0'}
+  prettier@3.7.4:
+    resolution: {integrity: sha512-v6UNi1+3hSlVvv8fSaoUbggEM5VErKmmpGA7Pl3HF8V6uKY7rvClBOJlH6yNwQtfTueNkGVpOv/mtWL9L4bgRA==}
+    engines: {node: '>=14'}
     hasBin: true
 
   prismjs@1.30.0:
@@ -2710,9 +2588,6 @@ packages:
   remark-parse@11.0.0:
     resolution: {integrity: sha512-FCxlKLNGknS5ba/1lmpYijMUzX2esxW5xQqjWxw2eHFfS2MSdaHVINFmhjo+qN1WhZhNimq0dZATN9pH0IDrpA==}
 
-  remark-rehype@11.1.1:
-    resolution: {integrity: sha512-g/osARvjkBXb6Wo0XvAeXQohVta8i84ACbenPpoSsxTOQH/Ae0/RGP4WZgnMH5pMLpsj4FG7OHmcIcXxpza8eQ==}
-
   remark-rehype@11.1.2:
     resolution: {integrity: sha512-Dh7l57ianaEoIpzbp0PC9UKAdCSVklD8E5Rpw7ETfbTl3FqcOOgq5q2LVDhgGCkaBv7p24JXikPdvhhmHvKMsw==}
 
@@ -2767,11 +2642,6 @@ packages:
   robust-predicates@3.0.2:
     resolution: {integrity: sha512-IXgzBWvWQwE6PrDI05OvmXUIruQTcoMDzRsOd5CDvHCVLcLHMTSYvOK5Cm46kWqlV3yAbuSpBZdJ5oP5OUoStg==}
 
-  rollup@4.34.7:
-    resolution: {integrity: sha512-8qhyN0oZ4x0H6wmBgfKxJtxM7qS98YJ0k0kNh5ECVtuchIJ7z9IVVvzpmtQyT10PXKMtBxYr1wQ5Apg8RS8kXQ==}
-    engines: {node: '>=18.0.0', npm: '>=8.0.0'}
-    hasBin: true
-
   rollup@4.52.5:
     resolution: {integrity: sha512-3GuObel8h7Kqdjt0gxkEzaifHTqLVW56Y/bjN7PSQtkKr0w3V/QYSdt6QWYtd7A1xUtYQigtdUfgj1RvWVtorw==}
     engines: {node: '>=18.0.0', npm: '>=8.0.0'}
@@ -2796,11 +2666,6 @@ packages:
     resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==}
     engines: {node: '>=4'}
 
-  semver@7.7.1:
-    resolution: {integrity: sha512-hlq8tAfn0m/61p4BVRcPzIGr6LKiMwo4VM6dGi6pt4qcRkmNzTcWq6eCEjEh+qXjkMDvPlOFFSGwQjoEa6gyMA==}
-    engines: {node: '>=10'}
-    hasBin: true
-
   semver@7.7.3:
     resolution: {integrity: sha512-SdsKMrI9TdgjdweUSR9MweHA4EJ8YxHn8DFaDisvhVlUOe4BF1tLD7GAj0lIqWVl+dPb/rExr0Btby5loQm20Q==}
     engines: {node: '>=10'}
@@ -2813,6 +2678,9 @@ packages:
   shiki@3.14.0:
     resolution: {integrity: sha512-J0yvpLI7LSig3Z3acIuDLouV5UCKQqu8qOArwMx+/yPVC3WRMgrP67beaG8F+j4xfEWE0eVC4GeBCIXeOPra1g==}
 
+  shiki@3.20.0:
+    resolution: {integrity: sha512-kgCOlsnyWb+p0WU+01RjkCH+eBVsjL1jOwUYWv0YDWkM2/A46+LDKVs5yZCUXjJG6bj4ndFoAg5iLIIue6dulg==}
+
   siginfo@2.0.0:
     resolution: {integrity: sha512-ybx0WO1/8bSBLEWXZvEd7gMW3Sn3JFlW3TvX1nREbDLRNQNaeNN8WK0meBwPdAaOI7TtRRRJn/Es1zhrrCHu7g==}
 
@@ -2829,6 +2697,10 @@ packages:
     resolution: {integrity: sha512-rInDH6lCNiEyn3+hH8KVGFdbjc099j47+OSgbMrfDYX1CmXLfdKd7qi6IfcWj2wFxvSVkuI46M+wPGYfEOEj6g==}
     engines: {node: '>= 18'}
 
+  smol-toml@1.5.2:
+    resolution: {integrity: sha512-QlaZEqcAH3/RtNyet1IPIYPsEWAaYyXXv1Krsi+1L/QHppjX4Ifm8MQsBISz9vE8cHicIq3clogsheili5vhaQ==}
+    engines: {node: '>= 18'}
+
   source-map-js@1.2.1:
     resolution: {integrity: sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==}
     engines: {node: '>=0.10.0'}
@@ -2884,18 +2756,24 @@ packages:
   stylis@4.3.6:
     resolution: {integrity: sha512-yQ3rwFWRfwNUY7H5vpU0wfdkNSnvnJinhF9830Swlaxl03zsOjCfmX0ugac+3LtK0lYSgwL/KXc8oYL3mG4YFQ==}
 
+  svgo@4.0.0:
+    resolution: {integrity: sha512-VvrHQ+9uniE+Mvx3+C9IEe/lWasXCU0nXMY2kZeLrHNICuRiC8uMPyM14UEaMOFA5mhyQqEkB02VoQ16n3DLaw==}
+    engines: {node: '>=16'}
+    hasBin: true
+
   tiny-inflate@1.0.3:
     resolution: {integrity: sha512-pkY1fj1cKHb2seWDy0B16HeWyczlJA9/WW3u3c4z/NiWDsO3DOU5D7nhTLE9CF0yXv/QZFY7sEJmj24dK+Rrqw==}
 
   tinybench@2.9.0:
     resolution: {integrity: sha512-0+DUvqWMValLmha6lr4kD8iAMK1HzV0/aKnCtWb9v9641TnP/MFb7Pc2bxoxQjTXAErryXVgUOfv2YqNllqGeg==}
 
-  tinyexec@0.3.2:
-    resolution: {integrity: sha512-KQQR9yN7R5+OSwaK0XQoj22pwHoTlgYqmUscPYoknOoWCWfj/5/ABTMRi69FrKU5ffPVh5QcFikpWJI/P1ocHA==}
-
   tinyexec@1.0.1:
     resolution: {integrity: sha512-5uC6DDlmeqiOwCPmK9jMSdOuZTh8bU39Ys6yidB+UTt5hfZUPGAypSgFRiEp+jbi9qH40BLDvy85jIU88wKSqw==}
 
+  tinyexec@1.0.2:
+    resolution: {integrity: sha512-W/KYk+NFhkmsYpuHq5JykngiOCnxeVL8v8dFnqxSD8qEEdRfXk1SDM6JzNqcERbcGYj9tMrDQBYV9cjgnunFIg==}
+    engines: {node: '>=18'}
+
   tinyglobby@0.2.15:
     resolution: {integrity: sha512-j2Zq4NyQYG5XMST4cbs02Ak8iJUdxRM0XI5QyxXuZOzKOINmWurp3smXu3y5wDcJrptwpSjgXHzIQxR0omXljQ==}
     engines: {node: '>=12.0.0'}
@@ -2904,10 +2782,6 @@ packages:
     resolution: {integrity: sha512-PSkbLUoxOFRzJYjjxHJt9xro7D+iilgMX/C9lawzVuYiIdcihh9DXmVibBe8lmcFrRi/VzlPjBxbN7rH24q8/Q==}
     engines: {node: '>=14.0.0'}
 
-  to-fast-properties@2.0.0:
-    resolution: {integrity: sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==}
-    engines: {node: '>=4'}
-
   to-regex-range@5.0.1:
     resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==}
     engines: {node: '>=8.0'}
@@ -2932,9 +2806,6 @@ packages:
       typescript:
         optional: true
 
-  tslib@2.7.0:
-    resolution: {integrity: sha512-gLXCKdN1/j47AiHiOkJN69hJmcbGTHI0ImLmbYLHykhgeN0jVGola9yVjFgzCUklsZQMW55o+dW7IXv3RCXDzA==}
-
   tslib@2.8.1:
     resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==}
 
@@ -2945,8 +2816,8 @@ packages:
   typesafe-path@0.2.2:
     resolution: {integrity: sha512-OJabfkAg1WLZSqJAJ0Z6Sdt3utnbzr/jh+NAHoyWHJe8CMSy79Gm085094M9nvTPy22KzTVn5Zq5mbapCI/hPA==}
 
-  typescript-auto-import-cache@0.3.3:
-    resolution: {integrity: sha512-ojEC7+Ci1ij9eE6hp8Jl9VUNnsEKzztktP5gtYNRMrTmfXVwA1PITYYAkpxCvvupdSYa/Re51B6KMcv1CTZEUA==}
+  typescript-auto-import-cache@0.3.6:
+    resolution: {integrity: sha512-RpuHXrknHdVdK7wv/8ug3Fr0WNsNi5l5aB8MYYuXhq2UH5lnEB1htJ1smhtD5VeCsGr2p8mUDtd83LCQDFVgjQ==}
 
   typescript@5.9.3:
     resolution: {integrity: sha512-jl1vZzPDinLr9eUt3J/t7V6FgNEw9QjvBPdysz9KfQDD41fQrC2Y4vKQdiaUpFT4bXlb1RHhLpp8wtm6M5TgSw==}
@@ -3001,11 +2872,14 @@ packages:
   unist-util-visit-parents@6.0.1:
     resolution: {integrity: sha512-L/PqWzfTP9lzzEa6CKs0k2nARxTdZduw3zyh8d2NVBnsyvHjSX4TWse388YrrQKbvI8w20fGjGlhgT96WwKykw==}
 
+  unist-util-visit-parents@6.0.2:
+    resolution: {integrity: sha512-goh1s1TBrqSqukSc8wrjwWhL0hiJxgA8m4kFxGlQ+8FYQ3C/m11FcTs4YYem7V664AhHVvgoQLk890Ssdsr2IQ==}
+
   unist-util-visit@5.0.0:
     resolution: {integrity: sha512-MR04uvD+07cwl/yhVuVWAtw+3GOR/knlL55Nd/wAdblk27GCVt3lqpTivy/tkJcZoNPzTwS1Y+KMojlLDhoTzg==}
 
-  unstorage@1.17.1:
-    resolution: {integrity: sha512-KKGwRTT0iVBCErKemkJCLs7JdxNVfqTPc/85ae1XES0+bsHbc/sFBfVi5kJp156cc51BHinIH2l3k0EZ24vOBQ==}
+  unstorage@1.17.3:
+    resolution: {integrity: sha512-i+JYyy0DoKmQ3FximTHbGadmIYb8JEpq7lxUjnjeB702bCPum0vzo6oy5Mfu0lpqISw7hCyMW2yj4nWC8bqJ3Q==}
     peerDependencies:
       '@azure/app-configuration': ^1.8.0
       '@azure/cosmos': ^4.2.0
@@ -3082,46 +2956,6 @@ packages:
   vfile@6.0.3:
     resolution: {integrity: sha512-KzIbH/9tXat2u30jf+smMwFCsno4wHVdNmzFyL+T/L3UGqqk6JKfVqOFOZEpZSHADH1k40ab6NUIXZq422ov3Q==}
 
-  vite@6.1.0:
-    resolution: {integrity: sha512-RjjMipCKVoR4hVfPY6GQTgveinjNuyLw+qruksLDvA5ktI1150VmcMBKmQaEWJhg/j6Uaf6dNCNA0AfdzUb/hQ==}
-    engines: {node: ^18.0.0 || ^20.0.0 || >=22.0.0}
-    hasBin: true
-    peerDependencies:
-      '@types/node': ^18.0.0 || ^20.0.0 || >=22.0.0
-      jiti: '>=1.21.0'
-      less: '*'
-      lightningcss: ^1.21.0
-      sass: '*'
-      sass-embedded: '*'
-      stylus: '*'
-      sugarss: '*'
-      terser: ^5.16.0
-      tsx: ^4.8.1
-      yaml: ^2.4.2
-    peerDependenciesMeta:
-      '@types/node':
-        optional: true
-      jiti:
-        optional: true
-      less:
-        optional: true
-      lightningcss:
-        optional: true
-      sass:
-        optional: true
-      sass-embedded:
-        optional: true
-      stylus:
-        optional: true
-      sugarss:
-        optional: true
-      terser:
-        optional: true
-      tsx:
-        optional: true
-      yaml:
-        optional: true
-
   vite@6.4.1:
     resolution: {integrity: sha512-+Oxm7q9hDoLMyJOYfUYBuHQo+dkAloi33apOPP56pzj+vsdJDzr+j1NISE5pyaAuKL4A3UD34qd0lx5+kfKp2g==}
     engines: {node: ^18.0.0 || ^20.0.0 || >=22.0.0}
@@ -3170,24 +3004,24 @@ packages:
       vite:
         optional: true
 
-  vitest@4.0.5:
-    resolution: {integrity: sha512-4H+J28MI5oeYgGg3h5BFSkQ1g/2GKK1IR8oorH3a6EQQbb7CwjbnyBjH4PGxw9/6vpwAPNzaeUMp4Js4WJmdXQ==}
+  vitest@4.0.15:
+    resolution: {integrity: sha512-n1RxDp8UJm6N0IbJLQo+yzLZ2sQCDyl1o0LeugbPWf8+8Fttp29GghsQBjYJVmWq3gBFfe9Hs1spR44vovn2wA==}
     engines: {node: ^20.0.0 || ^22.0.0 || >=24.0.0}
     hasBin: true
     peerDependencies:
       '@edge-runtime/vm': '*'
-      '@types/debug': ^4.1.12
+      '@opentelemetry/api': ^1.9.0
       '@types/node': ^20.0.0 || ^22.0.0 || >=24.0.0
-      '@vitest/browser-playwright': 4.0.5
-      '@vitest/browser-preview': 4.0.5
-      '@vitest/browser-webdriverio': 4.0.5
-      '@vitest/ui': 4.0.5
+      '@vitest/browser-playwright': 4.0.15
+      '@vitest/browser-preview': 4.0.15
+      '@vitest/browser-webdriverio': 4.0.15
+      '@vitest/ui': 4.0.15
       happy-dom: '*'
       jsdom: '*'
     peerDependenciesMeta:
       '@edge-runtime/vm':
         optional: true
-      '@types/debug':
+      '@opentelemetry/api':
         optional: true
       '@types/node':
         optional: true
@@ -3204,32 +3038,32 @@ packages:
       jsdom:
         optional: true
 
-  volar-service-css@0.0.62:
-    resolution: {integrity: sha512-JwNyKsH3F8PuzZYuqPf+2e+4CTU8YoyUHEHVnoXNlrLe7wy9U3biomZ56llN69Ris7TTy/+DEX41yVxQpM4qvg==}
+  volar-service-css@0.0.67:
+    resolution: {integrity: sha512-zV7C6enn9T9tuvQ6iSUyYEs34iPXR69Pf9YYWpbFYPWzVs22w96BtE8p04XYXbmjU6unt5oFt+iLL77bMB5fhA==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
     peerDependenciesMeta:
       '@volar/language-service':
         optional: true
 
-  volar-service-emmet@0.0.62:
-    resolution: {integrity: sha512-U4dxWDBWz7Pi4plpbXf4J4Z/ss6kBO3TYrACxWNsE29abu75QzVS0paxDDhI6bhqpbDFXlpsDhZ9aXVFpnfGRQ==}
+  volar-service-emmet@0.0.67:
+    resolution: {integrity: sha512-UDBL5x7KptmuJZNCCXMlCndMhFult/tj+9jXq3FH1ZGS1E4M/1U5hC06pg1c6e4kn+vnR6bqmvX0vIhL4f98+A==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
     peerDependenciesMeta:
       '@volar/language-service':
         optional: true
 
-  volar-service-html@0.0.62:
-    resolution: {integrity: sha512-Zw01aJsZRh4GTGUjveyfEzEqpULQUdQH79KNEiKVYHZyuGtdBRYCHlrus1sueSNMxwwkuF5WnOHfvBzafs8yyQ==}
+  volar-service-html@0.0.67:
+    resolution: {integrity: sha512-ljREMF79JbcjNvObiv69HK2HCl5UT7WTD10zi6CRFUHMbPfiF2UZ42HGLsEGSzaHGZz6H4IFjSS/qfENRLUviQ==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
     peerDependenciesMeta:
       '@volar/language-service':
         optional: true
 
-  volar-service-prettier@0.0.62:
-    resolution: {integrity: sha512-h2yk1RqRTE+vkYZaI9KYuwpDfOQRrTEMvoHol0yW4GFKc75wWQRrb5n/5abDrzMPrkQbSip8JH2AXbvrRtYh4w==}
+  volar-service-prettier@0.0.67:
+    resolution: {integrity: sha512-B4KnPJPNWFTkEDa6Fn08i5PpO6T1CecmLLTFZoXz2eI4Fxwba/3nDaaVSsEP7e/vEe+U5YqV9fBzayJT71G5xg==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
       prettier: ^2.2 || ^3.0
@@ -3239,24 +3073,24 @@ packages:
       prettier:
         optional: true
 
-  volar-service-typescript-twoslash-queries@0.0.62:
-    resolution: {integrity: sha512-KxFt4zydyJYYI0kFAcWPTh4u0Ha36TASPZkAnNY784GtgajerUqM80nX/W1d0wVhmcOFfAxkVsf/Ed+tiYU7ng==}
+  volar-service-typescript-twoslash-queries@0.0.67:
+    resolution: {integrity: sha512-LD2R7WivDYp1SPgZrxx/0222xVTitDjm36oKo5+bfYG5kEgnw+BOPVHdwmvpJKg/RfssfxDI1ouwD4XkEDEfbA==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
     peerDependenciesMeta:
       '@volar/language-service':
         optional: true
 
-  volar-service-typescript@0.0.62:
-    resolution: {integrity: sha512-p7MPi71q7KOsH0eAbZwPBiKPp9B2+qrdHAd6VY5oTo9BUXatsOAdakTm9Yf0DUj6uWBAaOT01BSeVOPwucMV1g==}
+  volar-service-typescript@0.0.67:
+    resolution: {integrity: sha512-rfQBy36Rm1PU9vLWHk8BYJ4r2j/CI024vocJcH4Nb6K2RTc2Irmw6UOVY5DdGiPRV5r+e10wLMK5njj/EcL8sA==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
     peerDependenciesMeta:
       '@volar/language-service':
         optional: true
 
-  volar-service-yaml@0.0.62:
-    resolution: {integrity: sha512-k7gvv7sk3wa+nGll3MaSKyjwQsJjIGCHFjVkl3wjaSP2nouKyn9aokGmqjrl39mi88Oy49giog2GkZH526wjig==}
+  volar-service-yaml@0.0.67:
+    resolution: {integrity: sha512-jkdP/RF6wPIXEE3Ktnd81oJPn7aAvnVSiaqQHThC2Hrvo6xd9pEcqtbBUI+YfqVgvcMtXAkbtNO61K2GPhAiuA==}
     peerDependencies:
       '@volar/language-service': ~2.4.0
     peerDependenciesMeta:
@@ -3266,40 +3100,26 @@ packages:
   vscode-css-languageservice@6.3.0:
     resolution: {integrity: sha512-nU92imtkgzpCL0xikrIb8WvedV553F2BENzgz23wFuok/HLN5BeQmroMy26pUwFxV2eV8oNRmYCUv8iO7kSMhw==}
 
-  vscode-html-languageservice@5.3.0:
-    resolution: {integrity: sha512-C4Z3KsP5Ih+fjHpiBc5jxmvCl+4iEwvXegIrzu2F5pktbWvQaBT3YkVPk8N+QlSSMk8oCG6PKtZ/Sq2YHb5e8g==}
+  vscode-html-languageservice@5.6.1:
+    resolution: {integrity: sha512-5Mrqy5CLfFZUgkyhNZLA1Ye5g12Cb/v6VM7SxUzZUaRKWMDz4md+y26PrfRTSU0/eQAl3XpO9m2og+GGtDMuaA==}
 
   vscode-json-languageservice@4.1.8:
     resolution: {integrity: sha512-0vSpg6Xd9hfV+eZAaYN63xVVMOTmJ4GgHxXnkLCh+9RsQBkWKIghzLhW2B9ebfG+LQQg8uLtsQ2aUKjTgE+QOg==}
     engines: {npm: '>=7.0.0'}
 
-  vscode-jsonrpc@6.0.0:
-    resolution: {integrity: sha512-wnJA4BnEjOSyFMvjZdpiOwhSq9uDoK8e/kpRJDTaMYzwlkrhG1fwDIZI94CLsLzlCK5cIbMMtFlJlfR57Lavmg==}
-    engines: {node: '>=8.0.0 || >=10.0.0'}
-
   vscode-jsonrpc@8.2.0:
     resolution: {integrity: sha512-C+r0eKJUIfiDIfwJhria30+TYWPtuHJXHtI7J0YlOmKAo7ogxP20T0zxB7HZQIFhIyvoBPwWskjxrvAtfjyZfA==}
     engines: {node: '>=14.0.0'}
 
-  vscode-languageserver-protocol@3.16.0:
-    resolution: {integrity: sha512-sdeUoAawceQdgIfTI+sdcwkiK2KU+2cbEYA0agzM2uqaUy2UpnnGHtWTHVEtS0ES4zHU0eMFRGN+oQgDxlD66A==}
-
   vscode-languageserver-protocol@3.17.5:
     resolution: {integrity: sha512-mb1bvRJN8SVznADSGWM9u/b07H7Ecg0I3OgXDuLdn307rl/J3A9YD6/eYOssqhecL27hK1IPZAsaqh00i/Jljg==}
 
   vscode-languageserver-textdocument@1.0.12:
     resolution: {integrity: sha512-cxWNPesCnQCcMPeenjKKsOCKQZ/L6Tv19DTRIGuLWe32lyzWhihGVJ/rcckZXJxfdKCFvRLS3fpBIsV/ZGX4zA==}
 
-  vscode-languageserver-types@3.16.0:
-    resolution: {integrity: sha512-k8luDIWJWyenLc5ToFQQMaSrqCHiLwyKPHKPQZ5zz21vM+vIVUSvsRpcbiECH4WR88K2XZqc4ScRcZ7nk/jbeA==}
-
   vscode-languageserver-types@3.17.5:
     resolution: {integrity: sha512-Ld1VelNuX9pdF39h2Hgaeb5hEZM2Z3jUrrMgWQAu82jMtZp7p3vJT3BzToKtZI7NgQssZje5o0zryOrhQvzQAg==}
 
-  vscode-languageserver@7.0.0:
-    resolution: {integrity: sha512-60HTx5ID+fLRcgdHfmz0LDZAXYEV68fzwG0JWwEPBode9NuMYTIxuYXPg4ngO8i8+Ou0lM7y6GzaYWbiDL0drw==}
-    hasBin: true
-
   vscode-languageserver@9.0.1:
     resolution: {integrity: sha512-woByF3PDpkHFUreUa7Hos7+pUWdeWMXRd26+ZX2A8cFx6v/JPTtd4/uN0/jB6XQHYaOlHbio03NTHCqrgG5n7g==}
     hasBin: true
@@ -3351,16 +3171,12 @@ packages:
     resolution: {integrity: sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==}
     engines: {node: '>=10'}
 
-  yaml-language-server@1.15.0:
-    resolution: {integrity: sha512-N47AqBDCMQmh6mBLmI6oqxryHRzi33aPFPsJhYy3VTUGCdLHYjGh4FZzpUjRlphaADBBkDmnkM/++KNIOHi5Rw==}
+  yaml-language-server@1.19.2:
+    resolution: {integrity: sha512-9F3myNmJzUN/679jycdMxqtydPSDRAarSj3wPiF7pchEPnO9Dg07Oc+gIYLqXR4L+g+FSEVXXv2+mr54StLFOg==}
     hasBin: true
 
-  yaml@2.2.2:
-    resolution: {integrity: sha512-CBKFWExMn46Foo4cldiChEzn7S7SRV+wqiluAb6xmueD/fGyRHIhX8m14vVGgeFWjN540nKCNVj6P21eQjgTuA==}
-    engines: {node: '>= 14'}
-
-  yaml@2.7.0:
-    resolution: {integrity: sha512-+hSoy/QHluxmC9kCIJyL/uyFmLmc+e5CFR5Wa+bpIhIj85LVb9ZH2nVnqrHoSvKogwODv0ClqZkmiSSaIH5LTA==}
+  yaml@2.7.1:
+    resolution: {integrity: sha512-10ULxpnOCQXxJvBgxsn9ptjq6uviG/htZKk9veJGhlqn3w/DxQ631zFF+nlQXLwmImeS5amR2dl2U8sg6U9jsQ==}
     engines: {node: '>= 14'}
     hasBin: true
 
@@ -3369,6 +3185,11 @@ packages:
     engines: {node: '>= 14.6'}
     hasBin: true
 
+  yaml@2.8.2:
+    resolution: {integrity: sha512-mplynKqc1C2hTVYxd0PU2xQAc22TI1vShAYGksCCfxbn/dFwnHTNi1bvYsBTkhdUNtGIf5xNOg938rrSSYvS9A==}
+    engines: {node: '>= 14.6'}
+    hasBin: true
+
   yargs-parser@21.1.1:
     resolution: {integrity: sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==}
     engines: {node: '>=12'}
@@ -3389,10 +3210,10 @@ packages:
     resolution: {integrity: sha512-GQHQqAopRhwU8Kt1DDM8NjibDXHC8eoh1erhGAJPEyveY9qqVeXvVikNKrDz69sHowPMorbPUrH/mx8c50eiBQ==}
     engines: {node: '>=18'}
 
-  zod-to-json-schema@3.24.6:
-    resolution: {integrity: sha512-h/z3PKvcTcTetyjl1fkj79MHNEjm+HpD6NXheWjzOekY7kV+lwDYnHw+ivHkijnCSMz1yJaWBD9vu/Fcmk+vEg==}
+  zod-to-json-schema@3.25.0:
+    resolution: {integrity: sha512-HvWtU2UG41LALjajJrML6uQejQhNJx+JBO9IflpSja4R03iNWfKXrj6W2h7ljuLyc1nKS+9yDyL/9tD1U/yBnQ==}
     peerDependencies:
-      zod: ^3.24.1
+      zod: ^3.25 || ^4
 
   zod-to-ts@1.2.0:
     resolution: {integrity: sha512-x30XE43V+InwGpvTySRNz9kB7qFU8DlyEy7BsSTCHPH1R0QasMmHWZDCzYm6bVXtj/9NNJAZF3jW8rzFvH5OFA==}
@@ -3415,9 +3236,18 @@ snapshots:
 
   '@antfu/utils@9.2.0': {}
 
-  '@astrojs/check@0.9.5(typescript@5.9.3)':
+  '@anthropic-ai/claude-code@1.0.128':
+    optionalDependencies:
+      '@img/sharp-darwin-arm64': 0.33.5
+      '@img/sharp-darwin-x64': 0.33.5
+      '@img/sharp-linux-arm': 0.33.5
+      '@img/sharp-linux-arm64': 0.33.5
+      '@img/sharp-linux-x64': 0.33.5
+      '@img/sharp-win32-x64': 0.33.5
+
+  '@astrojs/check@0.9.6(prettier@3.7.4)(typescript@5.9.3)':
     dependencies:
-      '@astrojs/language-server': 2.15.4(typescript@5.9.3)
+      '@astrojs/language-server': 2.16.2(prettier@3.7.4)(typescript@5.9.3)
       chokidar: 4.0.3
       kleur: 4.1.5
       typescript: 5.9.3
@@ -3426,35 +3256,63 @@ snapshots:
       - prettier
       - prettier-plugin-astro
 
-  '@astrojs/compiler@2.10.3': {}
-
   '@astrojs/compiler@2.13.0': {}
 
   '@astrojs/internal-helpers@0.7.4': {}
 
-  '@astrojs/language-server@2.15.4(typescript@5.9.3)':
+  '@astrojs/internal-helpers@0.7.5': {}
+
+  '@astrojs/language-server@2.16.2(prettier@3.7.4)(typescript@5.9.3)':
     dependencies:
-      '@astrojs/compiler': 2.10.3
+      '@astrojs/compiler': 2.13.0
       '@astrojs/yaml2ts': 0.2.2
       '@jridgewell/sourcemap-codec': 1.5.5
-      '@volar/kit': 2.4.11(typescript@5.9.3)
-      '@volar/language-core': 2.4.11
-      '@volar/language-server': 2.4.11
-      '@volar/language-service': 2.4.11
+      '@volar/kit': 2.4.27(typescript@5.9.3)
+      '@volar/language-core': 2.4.27
+      '@volar/language-server': 2.4.27
+      '@volar/language-service': 2.4.27
       fast-glob: 3.3.3
       muggle-string: 0.4.1
-      volar-service-css: 0.0.62(@volar/language-service@2.4.11)
-      volar-service-emmet: 0.0.62(@volar/language-service@2.4.11)
-      volar-service-html: 0.0.62(@volar/language-service@2.4.11)
-      volar-service-prettier: 0.0.62(@volar/language-service@2.4.11)
-      volar-service-typescript: 0.0.62(@volar/language-service@2.4.11)
-      volar-service-typescript-twoslash-queries: 0.0.62(@volar/language-service@2.4.11)
-      volar-service-yaml: 0.0.62(@volar/language-service@2.4.11)
-      vscode-html-languageservice: 5.3.0
-      vscode-uri: 3.0.8
+      volar-service-css: 0.0.67(@volar/language-service@2.4.27)
+      volar-service-emmet: 0.0.67(@volar/language-service@2.4.27)
+      volar-service-html: 0.0.67(@volar/language-service@2.4.27)
+      volar-service-prettier: 0.0.67(@volar/language-service@2.4.27)(prettier@3.7.4)
+      volar-service-typescript: 0.0.67(@volar/language-service@2.4.27)
+      volar-service-typescript-twoslash-queries: 0.0.67(@volar/language-service@2.4.27)
+      volar-service-yaml: 0.0.67(@volar/language-service@2.4.27)
+      vscode-html-languageservice: 5.6.1
+      vscode-uri: 3.1.0
+    optionalDependencies:
+      prettier: 3.7.4
     transitivePeerDependencies:
       - typescript
 
+  '@astrojs/markdown-remark@6.3.10':
+    dependencies:
+      '@astrojs/internal-helpers': 0.7.5
+      '@astrojs/prism': 3.3.0
+      github-slugger: 2.0.0
+      hast-util-from-html: 2.0.3
+      hast-util-to-text: 4.0.2
+      import-meta-resolve: 4.2.0
+      js-yaml: 4.1.1
+      mdast-util-definitions: 6.0.0
+      rehype-raw: 7.0.0
+      rehype-stringify: 10.0.1
+      remark-gfm: 4.0.1
+      remark-parse: 11.0.0
+      remark-rehype: 11.1.2
+      remark-smartypants: 3.0.2
+      shiki: 3.20.0
+      smol-toml: 1.5.2
+      unified: 11.0.5
+      unist-util-remove-position: 5.0.0
+      unist-util-visit: 5.0.0
+      unist-util-visit-parents: 6.0.2
+      vfile: 6.0.3
+    transitivePeerDependencies:
+      - supports-color
+
   '@astrojs/markdown-remark@6.3.8':
     dependencies:
       '@astrojs/internal-helpers': 0.7.4
@@ -3481,12 +3339,12 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@astrojs/mdx@4.3.9(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))':
+  '@astrojs/mdx@4.3.9(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))':
     dependencies:
       '@astrojs/markdown-remark': 6.3.8
       '@mdx-js/mdx': 3.1.1
       acorn: 8.15.0
-      astro: 5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1)
+      astro: 5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2)
       es-module-lexer: 1.7.0
       estree-util-visit: 2.0.0
       hast-util-to-html: 9.0.5
@@ -3510,17 +3368,17 @@ snapshots:
       stream-replace-string: 2.0.0
       zod: 3.25.76
 
-  '@astrojs/starlight@0.36.1(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))':
+  '@astrojs/starlight@0.37.1(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))':
     dependencies:
       '@astrojs/markdown-remark': 6.3.8
-      '@astrojs/mdx': 4.3.9(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))
+      '@astrojs/mdx': 4.3.9(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))
       '@astrojs/sitemap': 3.6.0
       '@pagefind/default-ui': 1.3.0
       '@types/hast': 3.0.4
       '@types/js-yaml': 4.0.9
       '@types/mdast': 4.0.4
-      astro: 5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1)
-      astro-expressive-code: 0.41.3(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))
+      astro: 5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2)
+      astro-expressive-code: 0.41.3(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))
       bcp-47: 2.1.0
       hast-util-from-html: 2.0.3
       hast-util-select: 6.0.2
@@ -3529,6 +3387,7 @@ snapshots:
       i18next: 23.16.8
       js-yaml: 4.1.0
       klona: 2.0.6
+      magic-string: 0.30.21
       mdast-util-directive: 3.0.0
       mdast-util-to-markdown: 2.1.0
       mdast-util-to-string: 4.0.0
@@ -3557,29 +3416,28 @@ snapshots:
 
   '@astrojs/yaml2ts@0.2.2':
     dependencies:
-      yaml: 2.7.0
+      yaml: 2.8.1
 
-  '@babel/helper-string-parser@7.24.8': {}
+  '@babel/helper-string-parser@7.27.1': {}
 
-  '@babel/helper-validator-identifier@7.24.7': {}
+  '@babel/helper-validator-identifier@7.28.5': {}
 
-  '@babel/parser@7.25.4':
+  '@babel/parser@7.28.5':
     dependencies:
-      '@babel/types': 7.25.4
+      '@babel/types': 7.28.5
 
   '@babel/runtime@7.26.9':
     dependencies:
       regenerator-runtime: 0.14.1
 
-  '@babel/types@7.25.4':
+  '@babel/types@7.28.5':
     dependencies:
-      '@babel/helper-string-parser': 7.24.8
-      '@babel/helper-validator-identifier': 7.24.7
-      to-fast-properties: 2.0.0
+      '@babel/helper-string-parser': 7.27.1
+      '@babel/helper-validator-identifier': 7.28.5
 
   '@braintree/sanitize-url@7.1.1': {}
 
-  '@capsizecss/unpack@3.0.0':
+  '@capsizecss/unpack@3.0.1':
     dependencies:
       fontkit: 2.0.4
 
@@ -3600,26 +3458,26 @@ snapshots:
 
   '@chevrotain/utils@11.0.3': {}
 
-  '@cspell/cspell-bundled-dicts@9.2.2':
+  '@cspell/cspell-bundled-dicts@9.4.0':
     dependencies:
       '@cspell/dict-ada': 4.1.1
       '@cspell/dict-al': 1.1.1
-      '@cspell/dict-aws': 4.0.15
+      '@cspell/dict-aws': 4.0.17
       '@cspell/dict-bash': 4.2.2
       '@cspell/dict-companies': 3.2.7
-      '@cspell/dict-cpp': 6.0.13
+      '@cspell/dict-cpp': 6.0.15
       '@cspell/dict-cryptocurrencies': 5.0.5
       '@cspell/dict-csharp': 4.0.7
       '@cspell/dict-css': 4.0.18
       '@cspell/dict-dart': 2.3.1
-      '@cspell/dict-data-science': 2.0.11
+      '@cspell/dict-data-science': 2.0.13
       '@cspell/dict-django': 4.1.5
       '@cspell/dict-docker': 1.1.16
       '@cspell/dict-dotnet': 5.0.10
       '@cspell/dict-elixir': 4.0.8
-      '@cspell/dict-en-common-misspellings': 2.1.7
-      '@cspell/dict-en-gb-mit': 3.1.12
-      '@cspell/dict-en_us': 4.4.22
+      '@cspell/dict-en-common-misspellings': 2.1.9
+      '@cspell/dict-en-gb-mit': 3.1.15
+      '@cspell/dict-en_us': 4.4.25
       '@cspell/dict-filetypes': 3.0.14
       '@cspell/dict-flutter': 1.1.1
       '@cspell/dict-fonts': 4.0.5
@@ -3630,7 +3488,7 @@ snapshots:
       '@cspell/dict-golang': 6.0.24
       '@cspell/dict-google': 1.0.9
       '@cspell/dict-haskell': 4.0.6
-      '@cspell/dict-html': 4.0.12
+      '@cspell/dict-html': 4.0.13
       '@cspell/dict-html-symbol-entities': 4.0.4
       '@cspell/dict-java': 5.0.12
       '@cspell/dict-julia': 1.1.1
@@ -3640,46 +3498,47 @@ snapshots:
       '@cspell/dict-lorem-ipsum': 4.0.5
       '@cspell/dict-lua': 4.0.8
       '@cspell/dict-makefile': 1.0.5
-      '@cspell/dict-markdown': 2.0.12(@cspell/dict-css@4.0.18)(@cspell/dict-html-symbol-entities@4.0.4)(@cspell/dict-html@4.0.12)(@cspell/dict-typescript@3.2.3)
+      '@cspell/dict-markdown': 2.0.13(@cspell/dict-css@4.0.18)(@cspell/dict-html-symbol-entities@4.0.4)(@cspell/dict-html@4.0.13)(@cspell/dict-typescript@3.2.3)
       '@cspell/dict-monkeyc': 1.0.11
       '@cspell/dict-node': 5.0.8
-      '@cspell/dict-npm': 5.2.19
+      '@cspell/dict-npm': 5.2.26
       '@cspell/dict-php': 4.1.0
       '@cspell/dict-powershell': 5.0.15
       '@cspell/dict-public-licenses': 2.0.15
-      '@cspell/dict-python': 4.2.21
+      '@cspell/dict-python': 4.2.24
       '@cspell/dict-r': 2.1.1
       '@cspell/dict-ruby': 5.0.9
       '@cspell/dict-rust': 4.0.12
       '@cspell/dict-scala': 5.0.8
       '@cspell/dict-shell': 1.1.2
-      '@cspell/dict-software-terms': 5.1.10
+      '@cspell/dict-software-terms': 5.1.16
       '@cspell/dict-sql': 2.2.1
       '@cspell/dict-svelte': 1.0.7
       '@cspell/dict-swift': 2.0.6
       '@cspell/dict-terraform': 1.1.3
       '@cspell/dict-typescript': 3.2.3
       '@cspell/dict-vue': 3.0.5
+      '@cspell/dict-zig': 1.0.0
 
-  '@cspell/cspell-json-reporter@9.2.2':
+  '@cspell/cspell-json-reporter@9.4.0':
     dependencies:
-      '@cspell/cspell-types': 9.2.2
+      '@cspell/cspell-types': 9.4.0
 
-  '@cspell/cspell-pipe@9.2.2': {}
+  '@cspell/cspell-pipe@9.4.0': {}
 
-  '@cspell/cspell-resolver@9.2.2':
+  '@cspell/cspell-resolver@9.4.0':
     dependencies:
       global-directory: 4.0.1
 
-  '@cspell/cspell-service-bus@9.2.2': {}
+  '@cspell/cspell-service-bus@9.4.0': {}
 
-  '@cspell/cspell-types@9.2.2': {}
+  '@cspell/cspell-types@9.4.0': {}
 
   '@cspell/dict-ada@4.1.1': {}
 
   '@cspell/dict-al@1.1.1': {}
 
-  '@cspell/dict-aws@4.0.15': {}
+  '@cspell/dict-aws@4.0.17': {}
 
   '@cspell/dict-bash@4.2.2':
     dependencies:
@@ -3687,7 +3546,7 @@ snapshots:
 
   '@cspell/dict-companies@3.2.7': {}
 
-  '@cspell/dict-cpp@6.0.13': {}
+  '@cspell/dict-cpp@6.0.15': {}
 
   '@cspell/dict-cryptocurrencies@5.0.5': {}
 
@@ -3697,7 +3556,7 @@ snapshots:
 
   '@cspell/dict-dart@2.3.1': {}
 
-  '@cspell/dict-data-science@2.0.11': {}
+  '@cspell/dict-data-science@2.0.13': {}
 
   '@cspell/dict-django@4.1.5': {}
 
@@ -3707,11 +3566,11 @@ snapshots:
 
   '@cspell/dict-elixir@4.0.8': {}
 
-  '@cspell/dict-en-common-misspellings@2.1.7': {}
+  '@cspell/dict-en-common-misspellings@2.1.9': {}
 
-  '@cspell/dict-en-gb-mit@3.1.12': {}
+  '@cspell/dict-en-gb-mit@3.1.15': {}
 
-  '@cspell/dict-en_us@4.4.22': {}
+  '@cspell/dict-en_us@4.4.25': {}
 
   '@cspell/dict-filetypes@3.0.14': {}
 
@@ -3735,7 +3594,7 @@ snapshots:
 
   '@cspell/dict-html-symbol-entities@4.0.4': {}
 
-  '@cspell/dict-html@4.0.12': {}
+  '@cspell/dict-html@4.0.13': {}
 
   '@cspell/dict-java@5.0.12': {}
 
@@ -3753,10 +3612,10 @@ snapshots:
 
   '@cspell/dict-makefile@1.0.5': {}
 
-  '@cspell/dict-markdown@2.0.12(@cspell/dict-css@4.0.18)(@cspell/dict-html-symbol-entities@4.0.4)(@cspell/dict-html@4.0.12)(@cspell/dict-typescript@3.2.3)':
+  '@cspell/dict-markdown@2.0.13(@cspell/dict-css@4.0.18)(@cspell/dict-html-symbol-entities@4.0.4)(@cspell/dict-html@4.0.13)(@cspell/dict-typescript@3.2.3)':
     dependencies:
       '@cspell/dict-css': 4.0.18
-      '@cspell/dict-html': 4.0.12
+      '@cspell/dict-html': 4.0.13
       '@cspell/dict-html-symbol-entities': 4.0.4
       '@cspell/dict-typescript': 3.2.3
 
@@ -3764,7 +3623,7 @@ snapshots:
 
   '@cspell/dict-node@5.0.8': {}
 
-  '@cspell/dict-npm@5.2.19': {}
+  '@cspell/dict-npm@5.2.26': {}
 
   '@cspell/dict-php@4.1.0': {}
 
@@ -3772,9 +3631,9 @@ snapshots:
 
   '@cspell/dict-public-licenses@2.0.15': {}
 
-  '@cspell/dict-python@4.2.21':
+  '@cspell/dict-python@4.2.24':
     dependencies:
-      '@cspell/dict-data-science': 2.0.11
+      '@cspell/dict-data-science': 2.0.13
 
   '@cspell/dict-r@2.1.1': {}
 
@@ -3786,7 +3645,7 @@ snapshots:
 
   '@cspell/dict-shell@1.1.2': {}
 
-  '@cspell/dict-software-terms@5.1.10': {}
+  '@cspell/dict-software-terms@5.1.16': {}
 
   '@cspell/dict-sql@2.2.1': {}
 
@@ -3800,16 +3659,18 @@ snapshots:
 
   '@cspell/dict-vue@3.0.5': {}
 
-  '@cspell/dynamic-import@9.2.2':
+  '@cspell/dict-zig@1.0.0': {}
+
+  '@cspell/dynamic-import@9.4.0':
     dependencies:
-      '@cspell/url': 9.2.2
+      '@cspell/url': 9.4.0
       import-meta-resolve: 4.2.0
 
-  '@cspell/filetypes@9.2.2': {}
+  '@cspell/filetypes@9.4.0': {}
 
-  '@cspell/strong-weak-map@9.2.2': {}
+  '@cspell/strong-weak-map@9.4.0': {}
 
-  '@cspell/url@9.2.2': {}
+  '@cspell/url@9.4.0': {}
 
   '@ctrl/tinycolor@4.1.0': {}
 
@@ -3821,7 +3682,7 @@ snapshots:
     dependencies:
       '@emmetio/scanner': 1.0.4
 
-  '@emmetio/css-parser@0.4.0':
+  '@emmetio/css-parser@0.4.1':
     dependencies:
       '@emmetio/stream-reader': 2.2.0
       '@emmetio/stream-reader-utils': 0.1.0
@@ -3838,159 +3699,84 @@ snapshots:
 
   '@emnapi/runtime@1.6.0':
     dependencies:
-      tslib: 2.7.0
-    optional: true
-
-  '@esbuild/aix-ppc64@0.24.2':
+      tslib: 2.8.1
     optional: true
 
   '@esbuild/aix-ppc64@0.25.11':
     optional: true
 
-  '@esbuild/android-arm64@0.24.2':
-    optional: true
-
   '@esbuild/android-arm64@0.25.11':
     optional: true
 
-  '@esbuild/android-arm@0.24.2':
-    optional: true
-
   '@esbuild/android-arm@0.25.11':
     optional: true
 
-  '@esbuild/android-x64@0.24.2':
-    optional: true
-
   '@esbuild/android-x64@0.25.11':
     optional: true
 
-  '@esbuild/darwin-arm64@0.24.2':
-    optional: true
-
   '@esbuild/darwin-arm64@0.25.11':
     optional: true
 
-  '@esbuild/darwin-x64@0.24.2':
-    optional: true
-
   '@esbuild/darwin-x64@0.25.11':
     optional: true
 
-  '@esbuild/freebsd-arm64@0.24.2':
-    optional: true
-
   '@esbuild/freebsd-arm64@0.25.11':
     optional: true
 
-  '@esbuild/freebsd-x64@0.24.2':
-    optional: true
-
   '@esbuild/freebsd-x64@0.25.11':
     optional: true
 
-  '@esbuild/linux-arm64@0.24.2':
-    optional: true
-
   '@esbuild/linux-arm64@0.25.11':
     optional: true
 
-  '@esbuild/linux-arm@0.24.2':
-    optional: true
-
   '@esbuild/linux-arm@0.25.11':
     optional: true
 
-  '@esbuild/linux-ia32@0.24.2':
-    optional: true
-
   '@esbuild/linux-ia32@0.25.11':
     optional: true
 
-  '@esbuild/linux-loong64@0.24.2':
-    optional: true
-
   '@esbuild/linux-loong64@0.25.11':
     optional: true
 
-  '@esbuild/linux-mips64el@0.24.2':
-    optional: true
-
   '@esbuild/linux-mips64el@0.25.11':
     optional: true
 
-  '@esbuild/linux-ppc64@0.24.2':
-    optional: true
-
   '@esbuild/linux-ppc64@0.25.11':
     optional: true
 
-  '@esbuild/linux-riscv64@0.24.2':
-    optional: true
-
   '@esbuild/linux-riscv64@0.25.11':
     optional: true
 
-  '@esbuild/linux-s390x@0.24.2':
-    optional: true
-
   '@esbuild/linux-s390x@0.25.11':
     optional: true
 
-  '@esbuild/linux-x64@0.24.2':
-    optional: true
-
   '@esbuild/linux-x64@0.25.11':
     optional: true
 
-  '@esbuild/netbsd-arm64@0.24.2':
-    optional: true
-
   '@esbuild/netbsd-arm64@0.25.11':
     optional: true
 
-  '@esbuild/netbsd-x64@0.24.2':
-    optional: true
-
   '@esbuild/netbsd-x64@0.25.11':
     optional: true
 
-  '@esbuild/openbsd-arm64@0.24.2':
-    optional: true
-
   '@esbuild/openbsd-arm64@0.25.11':
     optional: true
 
-  '@esbuild/openbsd-x64@0.24.2':
-    optional: true
-
   '@esbuild/openbsd-x64@0.25.11':
     optional: true
 
   '@esbuild/openharmony-arm64@0.25.11':
     optional: true
 
-  '@esbuild/sunos-x64@0.24.2':
-    optional: true
-
   '@esbuild/sunos-x64@0.25.11':
     optional: true
 
-  '@esbuild/win32-arm64@0.24.2':
-    optional: true
-
   '@esbuild/win32-arm64@0.25.11':
     optional: true
 
-  '@esbuild/win32-ia32@0.24.2':
-    optional: true
-
   '@esbuild/win32-ia32@0.25.11':
     optional: true
 
-  '@esbuild/win32-x64@0.24.2':
-    optional: true
-
   '@esbuild/win32-x64@0.25.11':
     optional: true
 
@@ -3998,11 +3784,11 @@ snapshots:
     dependencies:
       '@ctrl/tinycolor': 4.1.0
       hast-util-select: 6.0.2
-      hast-util-to-html: 9.0.4
+      hast-util-to-html: 9.0.5
       hast-util-to-text: 4.0.2
       hastscript: 9.0.0
-      postcss: 8.5.2
-      postcss-nested: 6.2.0(postcss@8.5.2)
+      postcss: 8.5.6
+      postcss-nested: 6.2.0(postcss@8.5.6)
       unist-util-visit: 5.0.0
       unist-util-visit-parents: 6.0.1
 
@@ -4037,25 +3823,47 @@ snapshots:
   '@img/colour@1.0.0':
     optional: true
 
+  '@img/sharp-darwin-arm64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-darwin-arm64': 1.0.4
+    optional: true
+
   '@img/sharp-darwin-arm64@0.34.4':
     optionalDependencies:
       '@img/sharp-libvips-darwin-arm64': 1.2.3
     optional: true
 
+  '@img/sharp-darwin-x64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-darwin-x64': 1.0.4
+    optional: true
+
   '@img/sharp-darwin-x64@0.34.4':
     optionalDependencies:
       '@img/sharp-libvips-darwin-x64': 1.2.3
     optional: true
 
+  '@img/sharp-libvips-darwin-arm64@1.0.4':
+    optional: true
+
   '@img/sharp-libvips-darwin-arm64@1.2.3':
     optional: true
 
+  '@img/sharp-libvips-darwin-x64@1.0.4':
+    optional: true
+
   '@img/sharp-libvips-darwin-x64@1.2.3':
     optional: true
 
+  '@img/sharp-libvips-linux-arm64@1.0.4':
+    optional: true
+
   '@img/sharp-libvips-linux-arm64@1.2.3':
     optional: true
 
+  '@img/sharp-libvips-linux-arm@1.0.5':
+    optional: true
+
   '@img/sharp-libvips-linux-arm@1.2.3':
     optional: true
 
@@ -4065,6 +3873,9 @@ snapshots:
   '@img/sharp-libvips-linux-s390x@1.2.3':
     optional: true
 
+  '@img/sharp-libvips-linux-x64@1.0.4':
+    optional: true
+
   '@img/sharp-libvips-linux-x64@1.2.3':
     optional: true
 
@@ -4074,11 +3885,21 @@ snapshots:
   '@img/sharp-libvips-linuxmusl-x64@1.2.3':
     optional: true
 
+  '@img/sharp-linux-arm64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-arm64': 1.0.4
+    optional: true
+
   '@img/sharp-linux-arm64@0.34.4':
     optionalDependencies:
       '@img/sharp-libvips-linux-arm64': 1.2.3
     optional: true
 
+  '@img/sharp-linux-arm@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-arm': 1.0.5
+    optional: true
+
   '@img/sharp-linux-arm@0.34.4':
     optionalDependencies:
       '@img/sharp-libvips-linux-arm': 1.2.3
@@ -4094,6 +3915,11 @@ snapshots:
       '@img/sharp-libvips-linux-s390x': 1.2.3
     optional: true
 
+  '@img/sharp-linux-x64@0.33.5':
+    optionalDependencies:
+      '@img/sharp-libvips-linux-x64': 1.0.4
+    optional: true
+
   '@img/sharp-linux-x64@0.34.4':
     optionalDependencies:
       '@img/sharp-libvips-linux-x64': 1.2.3
@@ -4120,6 +3946,9 @@ snapshots:
   '@img/sharp-win32-ia32@0.34.4':
     optional: true
 
+  '@img/sharp-win32-x64@0.33.5':
+    optional: true
+
   '@img/sharp-win32-x64@0.34.4':
     optional: true
 
@@ -4127,7 +3956,7 @@ snapshots:
 
   '@mdx-js/mdx@3.1.1':
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       '@types/estree-jsx': 1.0.5
       '@types/hast': 3.0.4
       '@types/mdx': 2.0.13
@@ -4145,7 +3974,7 @@ snapshots:
       rehype-recma: 1.0.0
       remark-mdx: 3.0.1
       remark-parse: 11.0.0
-      remark-rehype: 11.1.1
+      remark-rehype: 11.1.2
       source-map: 0.7.6
       unified: 11.0.5
       unist-util-position-from-estree: 2.0.0
@@ -4192,132 +4021,75 @@ snapshots:
 
   '@rollup/pluginutils@5.3.0(rollup@4.52.5)':
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       estree-walker: 2.0.2
       picomatch: 4.0.3
     optionalDependencies:
       rollup: 4.52.5
 
-  '@rollup/rollup-android-arm-eabi@4.34.7':
-    optional: true
-
   '@rollup/rollup-android-arm-eabi@4.52.5':
     optional: true
 
-  '@rollup/rollup-android-arm64@4.34.7':
-    optional: true
-
   '@rollup/rollup-android-arm64@4.52.5':
     optional: true
 
-  '@rollup/rollup-darwin-arm64@4.34.7':
-    optional: true
-
   '@rollup/rollup-darwin-arm64@4.52.5':
     optional: true
 
-  '@rollup/rollup-darwin-x64@4.34.7':
-    optional: true
-
   '@rollup/rollup-darwin-x64@4.52.5':
     optional: true
 
-  '@rollup/rollup-freebsd-arm64@4.34.7':
-    optional: true
-
   '@rollup/rollup-freebsd-arm64@4.52.5':
     optional: true
 
-  '@rollup/rollup-freebsd-x64@4.34.7':
-    optional: true
-
   '@rollup/rollup-freebsd-x64@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-arm-gnueabihf@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-arm-gnueabihf@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-arm-musleabihf@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-arm-musleabihf@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-arm64-gnu@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-arm64-gnu@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-arm64-musl@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-arm64-musl@4.52.5':
     optional: true
 
   '@rollup/rollup-linux-loong64-gnu@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-loongarch64-gnu@4.34.7':
-    optional: true
-
-  '@rollup/rollup-linux-powerpc64le-gnu@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-ppc64-gnu@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-riscv64-gnu@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-riscv64-gnu@4.52.5':
     optional: true
 
   '@rollup/rollup-linux-riscv64-musl@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-s390x-gnu@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-s390x-gnu@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-x64-gnu@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-x64-gnu@4.52.5':
     optional: true
 
-  '@rollup/rollup-linux-x64-musl@4.34.7':
-    optional: true
-
   '@rollup/rollup-linux-x64-musl@4.52.5':
     optional: true
 
   '@rollup/rollup-openharmony-arm64@4.52.5':
     optional: true
 
-  '@rollup/rollup-win32-arm64-msvc@4.34.7':
-    optional: true
-
   '@rollup/rollup-win32-arm64-msvc@4.52.5':
     optional: true
 
-  '@rollup/rollup-win32-ia32-msvc@4.34.7':
-    optional: true
-
   '@rollup/rollup-win32-ia32-msvc@4.52.5':
     optional: true
 
   '@rollup/rollup-win32-x64-gnu@4.52.5':
     optional: true
 
-  '@rollup/rollup-win32-x64-msvc@4.34.7':
-    optional: true
-
   '@rollup/rollup-win32-x64-msvc@4.52.5':
     optional: true
 
@@ -4328,30 +4100,61 @@ snapshots:
       '@types/hast': 3.0.4
       hast-util-to-html: 9.0.5
 
+  '@shikijs/core@3.20.0':
+    dependencies:
+      '@shikijs/types': 3.20.0
+      '@shikijs/vscode-textmate': 10.0.2
+      '@types/hast': 3.0.4
+      hast-util-to-html: 9.0.5
+
   '@shikijs/engine-javascript@3.14.0':
     dependencies:
       '@shikijs/types': 3.14.0
       '@shikijs/vscode-textmate': 10.0.2
       oniguruma-to-es: 4.3.3
 
+  '@shikijs/engine-javascript@3.20.0':
+    dependencies:
+      '@shikijs/types': 3.20.0
+      '@shikijs/vscode-textmate': 10.0.2
+      oniguruma-to-es: 4.3.4
+
   '@shikijs/engine-oniguruma@3.14.0':
     dependencies:
       '@shikijs/types': 3.14.0
       '@shikijs/vscode-textmate': 10.0.2
 
+  '@shikijs/engine-oniguruma@3.20.0':
+    dependencies:
+      '@shikijs/types': 3.20.0
+      '@shikijs/vscode-textmate': 10.0.2
+
   '@shikijs/langs@3.14.0':
     dependencies:
       '@shikijs/types': 3.14.0
 
+  '@shikijs/langs@3.20.0':
+    dependencies:
+      '@shikijs/types': 3.20.0
+
   '@shikijs/themes@3.14.0':
     dependencies:
       '@shikijs/types': 3.14.0
 
+  '@shikijs/themes@3.20.0':
+    dependencies:
+      '@shikijs/types': 3.20.0
+
   '@shikijs/types@3.14.0':
     dependencies:
       '@shikijs/vscode-textmate': 10.0.2
       '@types/hast': 3.0.4
 
+  '@shikijs/types@3.20.0':
+    dependencies:
+      '@shikijs/vscode-textmate': 10.0.2
+      '@types/hast': 3.0.4
+
   '@shikijs/vscode-textmate@10.0.2': {}
 
   '@standard-schema/spec@1.0.0': {}
@@ -4362,7 +4165,7 @@ snapshots:
 
   '@types/acorn@4.0.6':
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
 
   '@types/chai@5.2.3':
     dependencies:
@@ -4494,11 +4297,7 @@ snapshots:
 
   '@types/estree-jsx@1.0.5':
     dependencies:
-      '@types/estree': 1.0.6
-
-  '@types/estree@1.0.5': {}
-
-  '@types/estree@1.0.6': {}
+      '@types/estree': 1.0.8
 
   '@types/estree@1.0.8': {}
 
@@ -4541,84 +4340,84 @@ snapshots:
 
   '@ungap/structured-clone@1.2.0': {}
 
-  '@vitest/expect@4.0.5':
+  '@vitest/expect@4.0.15':
     dependencies:
       '@standard-schema/spec': 1.0.0
       '@types/chai': 5.2.3
-      '@vitest/spy': 4.0.5
-      '@vitest/utils': 4.0.5
-      chai: 6.2.0
+      '@vitest/spy': 4.0.15
+      '@vitest/utils': 4.0.15
+      chai: 6.2.1
       tinyrainbow: 3.0.3
 
-  '@vitest/mocker@4.0.5(vite@6.1.0(yaml@2.8.1))':
+  '@vitest/mocker@4.0.15(vite@6.4.1(yaml@2.8.2))':
     dependencies:
-      '@vitest/spy': 4.0.5
+      '@vitest/spy': 4.0.15
       estree-walker: 3.0.3
       magic-string: 0.30.21
     optionalDependencies:
-      vite: 6.1.0(yaml@2.8.1)
+      vite: 6.4.1(yaml@2.8.2)
 
-  '@vitest/pretty-format@4.0.5':
+  '@vitest/pretty-format@4.0.15':
     dependencies:
       tinyrainbow: 3.0.3
 
-  '@vitest/runner@4.0.5':
+  '@vitest/runner@4.0.15':
     dependencies:
-      '@vitest/utils': 4.0.5
+      '@vitest/utils': 4.0.15
       pathe: 2.0.3
 
-  '@vitest/snapshot@4.0.5':
+  '@vitest/snapshot@4.0.15':
     dependencies:
-      '@vitest/pretty-format': 4.0.5
+      '@vitest/pretty-format': 4.0.15
       magic-string: 0.30.21
       pathe: 2.0.3
 
-  '@vitest/spy@4.0.5': {}
+  '@vitest/spy@4.0.15': {}
 
-  '@vitest/utils@4.0.5':
+  '@vitest/utils@4.0.15':
     dependencies:
-      '@vitest/pretty-format': 4.0.5
+      '@vitest/pretty-format': 4.0.15
       tinyrainbow: 3.0.3
 
-  '@volar/kit@2.4.11(typescript@5.9.3)':
+  '@volar/kit@2.4.27(typescript@5.9.3)':
     dependencies:
-      '@volar/language-service': 2.4.11
-      '@volar/typescript': 2.4.11
+      '@volar/language-service': 2.4.27
+      '@volar/typescript': 2.4.27
       typesafe-path: 0.2.2
       typescript: 5.9.3
       vscode-languageserver-textdocument: 1.0.12
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
 
-  '@volar/language-core@2.4.11':
+  '@volar/language-core@2.4.27':
     dependencies:
-      '@volar/source-map': 2.4.11
+      '@volar/source-map': 2.4.27
 
-  '@volar/language-server@2.4.11':
+  '@volar/language-server@2.4.27':
     dependencies:
-      '@volar/language-core': 2.4.11
-      '@volar/language-service': 2.4.11
-      '@volar/typescript': 2.4.11
+      '@volar/language-core': 2.4.27
+      '@volar/language-service': 2.4.27
+      '@volar/typescript': 2.4.27
       path-browserify: 1.0.1
       request-light: 0.7.0
       vscode-languageserver: 9.0.1
       vscode-languageserver-protocol: 3.17.5
       vscode-languageserver-textdocument: 1.0.12
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
 
-  '@volar/language-service@2.4.11':
+  '@volar/language-service@2.4.27':
     dependencies:
-      '@volar/language-core': 2.4.11
+      '@volar/language-core': 2.4.27
       vscode-languageserver-protocol: 3.17.5
       vscode-languageserver-textdocument: 1.0.12
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
 
-  '@volar/source-map@2.4.11': {}
+  '@volar/source-map@2.4.27': {}
 
-  '@volar/typescript@2.4.11':
+  '@volar/typescript@2.4.27':
     dependencies:
-      '@volar/language-core': 2.4.11
+      '@volar/language-core': 2.4.27
       path-browserify: 1.0.1
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
 
   '@vscode/emmet-helper@2.9.3':
     dependencies:
@@ -4636,6 +4435,10 @@ snapshots:
 
   acorn@8.15.0: {}
 
+  ajv-draft-04@1.0.0(ajv@8.17.1):
+    optionalDependencies:
+      ajv: 8.17.1
+
   ajv@8.17.1:
     dependencies:
       fast-deep-equal: 3.1.3
@@ -4651,6 +4454,8 @@ snapshots:
 
   ansi-regex@6.0.1: {}
 
+  ansi-regex@6.2.2: {}
+
   ansi-styles@4.3.0:
     dependencies:
       color-convert: 2.0.1
@@ -4680,26 +4485,27 @@ snapshots:
 
   astring@1.8.6: {}
 
-  astro-expressive-code@0.41.3(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1)):
+  astro-expressive-code@0.41.3(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2)):
     dependencies:
-      astro: 5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1)
+      astro: 5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2)
       rehype-expressive-code: 0.41.3
 
-  astro-mermaid@1.1.0(astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1))(mermaid@11.12.1):
+  astro-mermaid@1.2.0(astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2))(mermaid@11.12.2):
     dependencies:
-      astro: 5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1)
+      '@anthropic-ai/claude-code': 1.0.128
+      astro: 5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2)
       import-meta-resolve: 4.2.0
       mdast-util-to-string: 4.0.0
-      mermaid: 11.12.1
+      mermaid: 11.12.2
       unist-util-visit: 5.0.0
 
-  astro@5.15.2(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.1):
+  astro@5.16.5(rollup@4.52.5)(typescript@5.9.3)(yaml@2.8.2):
     dependencies:
       '@astrojs/compiler': 2.13.0
-      '@astrojs/internal-helpers': 0.7.4
-      '@astrojs/markdown-remark': 6.3.8
+      '@astrojs/internal-helpers': 0.7.5
+      '@astrojs/markdown-remark': 6.3.10
       '@astrojs/telemetry': 3.3.0
-      '@capsizecss/unpack': 3.0.0
+      '@capsizecss/unpack': 3.0.1
       '@oslojs/encoding': 1.1.0
       '@rollup/pluginutils': 5.3.0(rollup@4.52.5)
       acorn: 8.15.0
@@ -4713,7 +4519,7 @@ snapshots:
       cssesc: 3.0.0
       debug: 4.4.3
       deterministic-object-hash: 2.0.2
-      devalue: 5.4.2
+      devalue: 5.6.1
       diff: 5.2.0
       dlv: 1.1.3
       dset: 3.1.4
@@ -4726,36 +4532,37 @@ snapshots:
       html-escaper: 3.0.3
       http-cache-semantics: 4.2.0
       import-meta-resolve: 4.2.0
-      js-yaml: 4.1.0
+      js-yaml: 4.1.1
       magic-string: 0.30.21
-      magicast: 0.3.5
+      magicast: 0.5.1
       mrmime: 2.0.1
       neotraverse: 0.6.18
       p-limit: 6.2.0
-      p-queue: 8.1.0
-      package-manager-detector: 1.3.0
-      picocolors: 1.1.1
+      p-queue: 8.1.1
+      package-manager-detector: 1.6.0
+      piccolore: 0.1.3
       picomatch: 4.0.3
       prompts: 2.4.2
       rehype: 13.0.2
       semver: 7.7.3
-      shiki: 3.14.0
-      smol-toml: 1.4.2
-      tinyexec: 1.0.1
+      shiki: 3.20.0
+      smol-toml: 1.5.2
+      svgo: 4.0.0
+      tinyexec: 1.0.2
       tinyglobby: 0.2.15
       tsconfck: 3.1.6(typescript@5.9.3)
       ultrahtml: 1.6.0
       unifont: 0.6.0
       unist-util-visit: 5.0.0
-      unstorage: 1.17.1
+      unstorage: 1.17.3
       vfile: 6.0.3
-      vite: 6.4.1(yaml@2.8.1)
-      vitefu: 1.1.1(vite@6.4.1(yaml@2.8.1))
+      vite: 6.4.1(yaml@2.8.2)
+      vitefu: 1.1.1(vite@6.4.1(yaml@2.8.2))
       xxhash-wasm: 1.1.0
       yargs-parser: 21.1.1
       yocto-spinner: 0.2.3
       zod: 3.25.76
-      zod-to-json-schema: 3.24.6(zod@3.25.76)
+      zod-to-json-schema: 3.25.0(zod@3.25.76)
       zod-to-ts: 1.2.0(typescript@5.9.3)(zod@3.25.76)
     optionalDependencies:
       sharp: 0.34.4
@@ -4816,7 +4623,7 @@ snapshots:
     dependencies:
       ansi-align: 3.0.1
       camelcase: 8.0.0
-      chalk: 5.4.1
+      chalk: 5.6.2
       cli-boxes: 3.0.0
       string-width: 7.2.0
       type-fest: 4.34.1
@@ -4837,14 +4644,12 @@ snapshots:
 
   ccount@2.0.1: {}
 
-  chai@6.2.0: {}
+  chai@6.2.1: {}
 
   chalk-template@1.1.2:
     dependencies:
       chalk: 5.6.2
 
-  chalk@5.4.1: {}
-
   chalk@5.6.2: {}
 
   character-entities-html4@2.1.0: {}
@@ -4902,6 +4707,8 @@ snapshots:
 
   comma-separated-tokens@2.0.3: {}
 
+  commander@11.1.0: {}
+
   commander@14.0.2: {}
 
   commander@7.2.0: {}
@@ -4938,102 +4745,122 @@ snapshots:
     dependencies:
       uncrypto: 0.1.3
 
-  cspell-config-lib@9.2.2:
+  cspell-config-lib@9.4.0:
     dependencies:
-      '@cspell/cspell-types': 9.2.2
+      '@cspell/cspell-types': 9.4.0
       comment-json: 4.4.1
-      smol-toml: 1.4.2
-      yaml: 2.8.1
+      smol-toml: 1.5.2
+      yaml: 2.8.2
 
-  cspell-dictionary@9.2.2:
+  cspell-dictionary@9.4.0:
     dependencies:
-      '@cspell/cspell-pipe': 9.2.2
-      '@cspell/cspell-types': 9.2.2
-      cspell-trie-lib: 9.2.2
-      fast-equals: 5.3.2
+      '@cspell/cspell-pipe': 9.4.0
+      '@cspell/cspell-types': 9.4.0
+      cspell-trie-lib: 9.4.0
+      fast-equals: 5.4.0
 
-  cspell-gitignore@9.2.2:
+  cspell-gitignore@9.4.0:
     dependencies:
-      '@cspell/url': 9.2.2
-      cspell-glob: 9.2.2
-      cspell-io: 9.2.2
+      '@cspell/url': 9.4.0
+      cspell-glob: 9.4.0
+      cspell-io: 9.4.0
 
-  cspell-glob@9.2.2:
+  cspell-glob@9.4.0:
     dependencies:
-      '@cspell/url': 9.2.2
+      '@cspell/url': 9.4.0
       picomatch: 4.0.3
 
-  cspell-grammar@9.2.2:
+  cspell-grammar@9.4.0:
     dependencies:
-      '@cspell/cspell-pipe': 9.2.2
-      '@cspell/cspell-types': 9.2.2
+      '@cspell/cspell-pipe': 9.4.0
+      '@cspell/cspell-types': 9.4.0
 
-  cspell-io@9.2.2:
+  cspell-io@9.4.0:
     dependencies:
-      '@cspell/cspell-service-bus': 9.2.2
-      '@cspell/url': 9.2.2
+      '@cspell/cspell-service-bus': 9.4.0
+      '@cspell/url': 9.4.0
 
-  cspell-lib@9.2.2:
+  cspell-lib@9.4.0:
     dependencies:
-      '@cspell/cspell-bundled-dicts': 9.2.2
-      '@cspell/cspell-pipe': 9.2.2
-      '@cspell/cspell-resolver': 9.2.2
-      '@cspell/cspell-types': 9.2.2
-      '@cspell/dynamic-import': 9.2.2
-      '@cspell/filetypes': 9.2.2
-      '@cspell/strong-weak-map': 9.2.2
-      '@cspell/url': 9.2.2
+      '@cspell/cspell-bundled-dicts': 9.4.0
+      '@cspell/cspell-pipe': 9.4.0
+      '@cspell/cspell-resolver': 9.4.0
+      '@cspell/cspell-types': 9.4.0
+      '@cspell/dynamic-import': 9.4.0
+      '@cspell/filetypes': 9.4.0
+      '@cspell/strong-weak-map': 9.4.0
+      '@cspell/url': 9.4.0
       clear-module: 4.1.2
-      cspell-config-lib: 9.2.2
-      cspell-dictionary: 9.2.2
-      cspell-glob: 9.2.2
-      cspell-grammar: 9.2.2
-      cspell-io: 9.2.2
-      cspell-trie-lib: 9.2.2
+      cspell-config-lib: 9.4.0
+      cspell-dictionary: 9.4.0
+      cspell-glob: 9.4.0
+      cspell-grammar: 9.4.0
+      cspell-io: 9.4.0
+      cspell-trie-lib: 9.4.0
       env-paths: 3.0.0
-      gensequence: 7.0.0
+      gensequence: 8.0.8
       import-fresh: 3.3.1
       resolve-from: 5.0.0
       vscode-languageserver-textdocument: 1.0.12
       vscode-uri: 3.1.0
       xdg-basedir: 5.1.0
 
-  cspell-trie-lib@9.2.2:
+  cspell-trie-lib@9.4.0:
     dependencies:
-      '@cspell/cspell-pipe': 9.2.2
-      '@cspell/cspell-types': 9.2.2
-      gensequence: 7.0.0
+      '@cspell/cspell-pipe': 9.4.0
+      '@cspell/cspell-types': 9.4.0
+      gensequence: 8.0.8
 
-  cspell@9.2.2:
+  cspell@9.4.0:
     dependencies:
-      '@cspell/cspell-json-reporter': 9.2.2
-      '@cspell/cspell-pipe': 9.2.2
-      '@cspell/cspell-types': 9.2.2
-      '@cspell/dynamic-import': 9.2.2
-      '@cspell/url': 9.2.2
+      '@cspell/cspell-json-reporter': 9.4.0
+      '@cspell/cspell-pipe': 9.4.0
+      '@cspell/cspell-types': 9.4.0
+      '@cspell/dynamic-import': 9.4.0
+      '@cspell/url': 9.4.0
+      ansi-regex: 6.2.2
       chalk: 5.6.2
       chalk-template: 1.1.2
       commander: 14.0.2
-      cspell-config-lib: 9.2.2
-      cspell-dictionary: 9.2.2
-      cspell-gitignore: 9.2.2
-      cspell-glob: 9.2.2
-      cspell-io: 9.2.2
-      cspell-lib: 9.2.2
+      cspell-config-lib: 9.4.0
+      cspell-dictionary: 9.4.0
+      cspell-gitignore: 9.4.0
+      cspell-glob: 9.4.0
+      cspell-io: 9.4.0
+      cspell-lib: 9.4.0
       fast-json-stable-stringify: 2.1.0
       flatted: 3.3.3
       semver: 7.7.3
       tinyglobby: 0.2.15
 
+  css-select@5.2.2:
+    dependencies:
+      boolbase: 1.0.0
+      css-what: 6.2.2
+      domhandler: 5.0.3
+      domutils: 3.2.2
+      nth-check: 2.1.1
+
   css-selector-parser@3.0.5: {}
 
+  css-tree@2.2.1:
+    dependencies:
+      mdn-data: 2.0.28
+      source-map-js: 1.2.1
+
   css-tree@3.1.0:
     dependencies:
       mdn-data: 2.12.2
       source-map-js: 1.2.1
 
+  css-what@6.2.2: {}
+
   cssesc@3.0.0: {}
 
+  csso@5.0.5:
+    dependencies:
+      css-tree: 2.2.1
+
   cytoscape-cose-bilkent@4.1.0(cytoscape@3.33.1):
     dependencies:
       cose-base: 1.0.3
@@ -5236,8 +5063,6 @@ snapshots:
 
   dequal@2.0.3: {}
 
-  destr@2.0.3: {}
-
   destr@2.0.5: {}
 
   detect-libc@2.1.2:
@@ -5247,7 +5072,7 @@ snapshots:
     dependencies:
       base-64: 1.0.0
 
-  devalue@5.4.2: {}
+  devalue@5.6.1: {}
 
   devlop@1.1.0:
     dependencies:
@@ -5261,10 +5086,28 @@ snapshots:
 
   dlv@1.1.3: {}
 
+  dom-serializer@2.0.0:
+    dependencies:
+      domelementtype: 2.3.0
+      domhandler: 5.0.3
+      entities: 4.5.0
+
+  domelementtype@2.3.0: {}
+
+  domhandler@5.0.3:
+    dependencies:
+      domelementtype: 2.3.0
+
   dompurify@3.2.6:
     optionalDependencies:
       '@types/trusted-types': 2.0.7
 
+  domutils@3.2.2:
+    dependencies:
+      dom-serializer: 2.0.0
+      domelementtype: 2.3.0
+      domhandler: 5.0.3
+
   dset@3.1.4: {}
 
   emmet@2.4.7:
@@ -5296,34 +5139,6 @@ snapshots:
       esast-util-from-estree: 2.0.0
       vfile-message: 4.0.2
 
-  esbuild@0.24.2:
-    optionalDependencies:
-      '@esbuild/aix-ppc64': 0.24.2
-      '@esbuild/android-arm': 0.24.2
-      '@esbuild/android-arm64': 0.24.2
-      '@esbuild/android-x64': 0.24.2
-      '@esbuild/darwin-arm64': 0.24.2
-      '@esbuild/darwin-x64': 0.24.2
-      '@esbuild/freebsd-arm64': 0.24.2
-      '@esbuild/freebsd-x64': 0.24.2
-      '@esbuild/linux-arm': 0.24.2
-      '@esbuild/linux-arm64': 0.24.2
-      '@esbuild/linux-ia32': 0.24.2
-      '@esbuild/linux-loong64': 0.24.2
-      '@esbuild/linux-mips64el': 0.24.2
-      '@esbuild/linux-ppc64': 0.24.2
-      '@esbuild/linux-riscv64': 0.24.2
-      '@esbuild/linux-s390x': 0.24.2
-      '@esbuild/linux-x64': 0.24.2
-      '@esbuild/netbsd-arm64': 0.24.2
-      '@esbuild/netbsd-x64': 0.24.2
-      '@esbuild/openbsd-arm64': 0.24.2
-      '@esbuild/openbsd-x64': 0.24.2
-      '@esbuild/sunos-x64': 0.24.2
-      '@esbuild/win32-arm64': 0.24.2
-      '@esbuild/win32-ia32': 0.24.2
-      '@esbuild/win32-x64': 0.24.2
-
   esbuild@0.25.11:
     optionalDependencies:
       '@esbuild/aix-ppc64': 0.25.11
@@ -5361,7 +5176,7 @@ snapshots:
 
   estree-util-attach-comments@3.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
 
   estree-util-build-jsx@3.0.1:
     dependencies:
@@ -5374,7 +5189,7 @@ snapshots:
 
   estree-util-scope@1.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       devlop: 1.1.0
 
   estree-util-to-js@2.0.0:
@@ -5392,7 +5207,7 @@ snapshots:
 
   estree-walker@3.0.3:
     dependencies:
-      '@types/estree': 1.0.5
+      '@types/estree': 1.0.8
 
   eventemitter3@5.0.1: {}
 
@@ -5415,7 +5230,7 @@ snapshots:
 
   fast-deep-equal@3.1.3: {}
 
-  fast-equals@5.3.2: {}
+  fast-equals@5.4.0: {}
 
   fast-glob@3.3.3:
     dependencies:
@@ -5465,7 +5280,7 @@ snapshots:
   fsevents@2.3.3:
     optional: true
 
-  gensequence@7.0.0: {}
+  gensequence@8.0.8: {}
 
   get-caller-file@2.0.5: {}
 
@@ -5590,7 +5405,7 @@ snapshots:
 
   hast-util-to-estree@3.1.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       '@types/estree-jsx': 1.0.5
       '@types/hast': 3.0.4
       comma-separated-tokens: 2.0.3
@@ -5609,20 +5424,6 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  hast-util-to-html@9.0.4:
-    dependencies:
-      '@types/hast': 3.0.4
-      '@types/unist': 3.0.3
-      ccount: 2.0.1
-      comma-separated-tokens: 2.0.3
-      hast-util-whitespace: 3.0.0
-      html-void-elements: 3.0.0
-      mdast-util-to-hast: 13.2.0
-      property-information: 6.5.0
-      space-separated-tokens: 2.0.2
-      stringify-entities: 4.0.4
-      zwitch: 2.0.4
-
   hast-util-to-html@9.0.5:
     dependencies:
       '@types/hast': 3.0.4
@@ -5639,7 +5440,7 @@ snapshots:
 
   hast-util-to-jsx-runtime@2.3.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       '@types/hast': 3.0.4
       '@types/unist': 3.0.3
       comma-separated-tokens: 2.0.3
@@ -5777,6 +5578,10 @@ snapshots:
     dependencies:
       argparse: 2.0.1
 
+  js-yaml@4.1.1:
+    dependencies:
+      argparse: 2.0.1
+
   json-schema-traverse@1.0.0: {}
 
   jsonc-parser@2.3.1: {}
@@ -5829,10 +5634,10 @@ snapshots:
     dependencies:
       '@jridgewell/sourcemap-codec': 1.5.5
 
-  magicast@0.3.5:
+  magicast@0.5.1:
     dependencies:
-      '@babel/parser': 7.25.4
-      '@babel/types': 7.25.4
+      '@babel/parser': 7.28.5
+      '@babel/types': 7.28.5
       source-map-js: 1.2.1
 
   markdown-extensions@2.0.0: {}
@@ -5865,7 +5670,7 @@ snapshots:
       '@types/mdast': 4.0.4
       escape-string-regexp: 5.0.0
       unist-util-is: 6.0.0
-      unist-util-visit-parents: 6.0.1
+      unist-util-visit-parents: 6.0.2
 
   mdast-util-from-markdown@2.0.1:
     dependencies:
@@ -6023,11 +5828,13 @@ snapshots:
     dependencies:
       '@types/mdast': 4.0.4
 
+  mdn-data@2.0.28: {}
+
   mdn-data@2.12.2: {}
 
   merge2@1.4.1: {}
 
-  mermaid@11.12.1:
+  mermaid@11.12.2:
     dependencies:
       '@braintree/sanitize-url': 7.1.1
       '@iconify/utils': 3.0.2
@@ -6141,7 +5948,7 @@ snapshots:
 
   micromark-extension-mdx-expression@3.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       devlop: 1.1.0
       micromark-factory-mdx-expression: 2.0.1
       micromark-factory-space: 2.0.0
@@ -6153,7 +5960,7 @@ snapshots:
   micromark-extension-mdx-jsx@3.0.0:
     dependencies:
       '@types/acorn': 4.0.6
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       devlop: 1.1.0
       estree-util-is-identifier-name: 3.0.0
       micromark-factory-mdx-expression: 2.0.1
@@ -6169,7 +5976,7 @@ snapshots:
 
   micromark-extension-mdxjs-esm@3.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       devlop: 1.1.0
       micromark-core-commonmark: 2.0.1
       micromark-util-character: 2.1.0
@@ -6205,7 +6012,7 @@ snapshots:
 
   micromark-factory-mdx-expression@2.0.1:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       devlop: 1.1.0
       micromark-util-character: 2.1.0
       micromark-util-events-to-acorn: 2.0.2
@@ -6269,7 +6076,7 @@ snapshots:
   micromark-util-events-to-acorn@2.0.2:
     dependencies:
       '@types/acorn': 4.0.6
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       '@types/unist': 3.0.3
       devlop: 1.1.0
       estree-util-visit: 2.0.0
@@ -6346,16 +6153,12 @@ snapshots:
 
   nanoid@3.3.11: {}
 
-  nanoid@3.3.8: {}
-
   neotraverse@0.6.18: {}
 
   nlcst-to-string@4.0.0:
     dependencies:
       '@types/nlcst': 2.0.3
 
-  node-fetch-native@1.6.6: {}
-
   node-fetch-native@1.6.7: {}
 
   node-mock-http@1.0.3: {}
@@ -6368,10 +6171,18 @@ snapshots:
     dependencies:
       boolbase: 1.0.0
 
+  obug@2.1.1: {}
+
   ofetch@1.4.1:
     dependencies:
-      destr: 2.0.3
-      node-fetch-native: 1.6.6
+      destr: 2.0.5
+      node-fetch-native: 1.6.7
+      ufo: 1.6.1
+
+  ofetch@1.5.1:
+    dependencies:
+      destr: 2.0.5
+      node-fetch-native: 1.6.7
       ufo: 1.6.1
 
   ohash@2.0.11: {}
@@ -6384,11 +6195,17 @@ snapshots:
       regex: 6.0.1
       regex-recursion: 6.0.2
 
+  oniguruma-to-es@4.3.4:
+    dependencies:
+      oniguruma-parser: 0.12.1
+      regex: 6.0.1
+      regex-recursion: 6.0.2
+
   p-limit@6.2.0:
     dependencies:
       yocto-queue: 1.1.1
 
-  p-queue@8.1.0:
+  p-queue@8.1.1:
     dependencies:
       eventemitter3: 5.0.1
       p-timeout: 6.1.2
@@ -6397,6 +6214,8 @@ snapshots:
 
   package-manager-detector@1.3.0: {}
 
+  package-manager-detector@1.6.0: {}
+
   pagefind@1.3.0:
     optionalDependencies:
       '@pagefind/darwin-arm64': 1.3.0
@@ -6445,6 +6264,8 @@ snapshots:
 
   pathe@2.0.3: {}
 
+  piccolore@0.1.3: {}
+
   picocolors@1.1.1: {}
 
   picomatch@2.3.1: {}
@@ -6470,9 +6291,9 @@ snapshots:
       path-data-parser: 0.1.0
       points-on-curve: 0.2.0
 
-  postcss-nested@6.2.0(postcss@8.5.2):
+  postcss-nested@6.2.0(postcss@8.5.6):
     dependencies:
-      postcss: 8.5.2
+      postcss: 8.5.6
       postcss-selector-parser: 6.1.2
 
   postcss-selector-parser@6.1.2:
@@ -6480,20 +6301,13 @@ snapshots:
       cssesc: 3.0.0
       util-deprecate: 1.0.2
 
-  postcss@8.5.2:
-    dependencies:
-      nanoid: 3.3.8
-      picocolors: 1.1.1
-      source-map-js: 1.2.1
-
   postcss@8.5.6:
     dependencies:
       nanoid: 3.3.11
       picocolors: 1.1.1
       source-map-js: 1.2.1
 
-  prettier@2.8.7:
-    optional: true
+  prettier@3.7.4: {}
 
   prismjs@1.30.0: {}
 
@@ -6516,7 +6330,7 @@ snapshots:
 
   recma-build-jsx@1.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       estree-util-build-jsx: 3.0.1
       vfile: 6.0.3
 
@@ -6532,14 +6346,14 @@ snapshots:
 
   recma-parse@1.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       esast-util-from-js: 2.0.1
       unified: 11.0.5
       vfile: 6.0.3
 
   recma-stringify@1.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       estree-util-to-js: 2.0.0
       unified: 11.0.5
       vfile: 6.0.3
@@ -6593,7 +6407,7 @@ snapshots:
 
   rehype-recma@1.0.0:
     dependencies:
-      '@types/estree': 1.0.6
+      '@types/estree': 1.0.8
       '@types/hast': 3.0.4
       hast-util-to-estree: 3.1.0
     transitivePeerDependencies:
@@ -6602,7 +6416,7 @@ snapshots:
   rehype-stringify@10.0.1:
     dependencies:
       '@types/hast': 3.0.4
-      hast-util-to-html: 9.0.4
+      hast-util-to-html: 9.0.5
       unified: 11.0.5
 
   rehype@13.0.2:
@@ -6648,14 +6462,6 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  remark-rehype@11.1.1:
-    dependencies:
-      '@types/hast': 3.0.4
-      '@types/mdast': 4.0.4
-      mdast-util-to-hast: 13.2.0
-      unified: 11.0.5
-      vfile: 6.0.3
-
   remark-rehype@11.1.2:
     dependencies:
       '@types/hast': 3.0.4
@@ -6720,31 +6526,6 @@ snapshots:
 
   robust-predicates@3.0.2: {}
 
-  rollup@4.34.7:
-    dependencies:
-      '@types/estree': 1.0.6
-    optionalDependencies:
-      '@rollup/rollup-android-arm-eabi': 4.34.7
-      '@rollup/rollup-android-arm64': 4.34.7
-      '@rollup/rollup-darwin-arm64': 4.34.7
-      '@rollup/rollup-darwin-x64': 4.34.7
-      '@rollup/rollup-freebsd-arm64': 4.34.7
-      '@rollup/rollup-freebsd-x64': 4.34.7
-      '@rollup/rollup-linux-arm-gnueabihf': 4.34.7
-      '@rollup/rollup-linux-arm-musleabihf': 4.34.7
-      '@rollup/rollup-linux-arm64-gnu': 4.34.7
-      '@rollup/rollup-linux-arm64-musl': 4.34.7
-      '@rollup/rollup-linux-loongarch64-gnu': 4.34.7
-      '@rollup/rollup-linux-powerpc64le-gnu': 4.34.7
-      '@rollup/rollup-linux-riscv64-gnu': 4.34.7
-      '@rollup/rollup-linux-s390x-gnu': 4.34.7
-      '@rollup/rollup-linux-x64-gnu': 4.34.7
-      '@rollup/rollup-linux-x64-musl': 4.34.7
-      '@rollup/rollup-win32-arm64-msvc': 4.34.7
-      '@rollup/rollup-win32-ia32-msvc': 4.34.7
-      '@rollup/rollup-win32-x64-msvc': 4.34.7
-      fsevents: 2.3.3
-
   rollup@4.52.5:
     dependencies:
       '@types/estree': 1.0.8
@@ -6795,8 +6576,6 @@ snapshots:
       extend-shallow: 2.0.1
       kind-of: 6.0.3
 
-  semver@7.7.1: {}
-
   semver@7.7.3: {}
 
   sharp@0.34.4:
@@ -6840,6 +6619,17 @@ snapshots:
       '@shikijs/vscode-textmate': 10.0.2
       '@types/hast': 3.0.4
 
+  shiki@3.20.0:
+    dependencies:
+      '@shikijs/core': 3.20.0
+      '@shikijs/engine-javascript': 3.20.0
+      '@shikijs/engine-oniguruma': 3.20.0
+      '@shikijs/langs': 3.20.0
+      '@shikijs/themes': 3.20.0
+      '@shikijs/types': 3.20.0
+      '@shikijs/vscode-textmate': 10.0.2
+      '@types/hast': 3.0.4
+
   siginfo@2.0.0: {}
 
   sisteransi@1.0.5: {}
@@ -6853,6 +6643,8 @@ snapshots:
 
   smol-toml@1.4.2: {}
 
+  smol-toml@1.5.2: {}
+
   source-map-js@1.2.1: {}
 
   source-map@0.7.6: {}
@@ -6904,14 +6696,24 @@ snapshots:
 
   stylis@4.3.6: {}
 
+  svgo@4.0.0:
+    dependencies:
+      commander: 11.1.0
+      css-select: 5.2.2
+      css-tree: 3.1.0
+      css-what: 6.2.2
+      csso: 5.0.5
+      picocolors: 1.1.1
+      sax: 1.4.1
+
   tiny-inflate@1.0.3: {}
 
   tinybench@2.9.0: {}
 
-  tinyexec@0.3.2: {}
-
   tinyexec@1.0.1: {}
 
+  tinyexec@1.0.2: {}
+
   tinyglobby@0.2.15:
     dependencies:
       fdir: 6.5.0(picomatch@4.0.3)
@@ -6919,8 +6721,6 @@ snapshots:
 
   tinyrainbow@3.0.3: {}
 
-  to-fast-properties@2.0.0: {}
-
   to-regex-range@5.0.1:
     dependencies:
       is-number: 7.0.0
@@ -6935,18 +6735,15 @@ snapshots:
     optionalDependencies:
       typescript: 5.9.3
 
-  tslib@2.7.0:
-    optional: true
-
   tslib@2.8.1: {}
 
   type-fest@4.34.1: {}
 
   typesafe-path@0.2.2: {}
 
-  typescript-auto-import-cache@0.3.3:
+  typescript-auto-import-cache@0.3.6:
     dependencies:
-      semver: 7.7.1
+      semver: 7.7.3
 
   typescript@5.9.3: {}
 
@@ -7022,13 +6819,18 @@ snapshots:
       '@types/unist': 3.0.3
       unist-util-is: 6.0.0
 
+  unist-util-visit-parents@6.0.2:
+    dependencies:
+      '@types/unist': 3.0.3
+      unist-util-is: 6.0.0
+
   unist-util-visit@5.0.0:
     dependencies:
       '@types/unist': 3.0.3
       unist-util-is: 6.0.0
       unist-util-visit-parents: 6.0.1
 
-  unstorage@1.17.1:
+  unstorage@1.17.3:
     dependencies:
       anymatch: 3.1.3
       chokidar: 4.0.3
@@ -7036,7 +6838,7 @@ snapshots:
       h3: 1.15.4
       lru-cache: 10.4.3
       node-fetch-native: 1.6.7
-      ofetch: 1.4.1
+      ofetch: 1.5.1
       ufo: 1.6.1
 
   util-deprecate@1.0.2: {}
@@ -7058,16 +6860,7 @@ snapshots:
       '@types/unist': 3.0.3
       vfile-message: 4.0.2
 
-  vite@6.1.0(yaml@2.8.1):
-    dependencies:
-      esbuild: 0.24.2
-      postcss: 8.5.2
-      rollup: 4.34.7
-    optionalDependencies:
-      fsevents: 2.3.3
-      yaml: 2.8.1
-
-  vite@6.4.1(yaml@2.8.1):
+  vite@6.4.1(yaml@2.8.2):
     dependencies:
       esbuild: 0.25.11
       fdir: 6.5.0(picomatch@4.0.3)
@@ -7077,36 +6870,34 @@ snapshots:
       tinyglobby: 0.2.15
     optionalDependencies:
       fsevents: 2.3.3
-      yaml: 2.8.1
+      yaml: 2.8.2
 
-  vitefu@1.1.1(vite@6.4.1(yaml@2.8.1)):
+  vitefu@1.1.1(vite@6.4.1(yaml@2.8.2)):
     optionalDependencies:
-      vite: 6.4.1(yaml@2.8.1)
+      vite: 6.4.1(yaml@2.8.2)
 
-  vitest@4.0.5(@types/debug@4.1.12)(yaml@2.8.1):
+  vitest@4.0.15(yaml@2.8.2):
     dependencies:
-      '@vitest/expect': 4.0.5
-      '@vitest/mocker': 4.0.5(vite@6.1.0(yaml@2.8.1))
-      '@vitest/pretty-format': 4.0.5
-      '@vitest/runner': 4.0.5
-      '@vitest/snapshot': 4.0.5
-      '@vitest/spy': 4.0.5
-      '@vitest/utils': 4.0.5
-      debug: 4.4.3
+      '@vitest/expect': 4.0.15
+      '@vitest/mocker': 4.0.15(vite@6.4.1(yaml@2.8.2))
+      '@vitest/pretty-format': 4.0.15
+      '@vitest/runner': 4.0.15
+      '@vitest/snapshot': 4.0.15
+      '@vitest/spy': 4.0.15
+      '@vitest/utils': 4.0.15
       es-module-lexer: 1.7.0
       expect-type: 1.2.2
       magic-string: 0.30.21
+      obug: 2.1.1
       pathe: 2.0.3
       picomatch: 4.0.3
       std-env: 3.10.0
       tinybench: 2.9.0
-      tinyexec: 0.3.2
+      tinyexec: 1.0.2
       tinyglobby: 0.2.15
       tinyrainbow: 3.0.3
-      vite: 6.1.0(yaml@2.8.1)
+      vite: 6.4.1(yaml@2.8.2)
       why-is-node-running: 2.3.0
-    optionalDependencies:
-      '@types/debug': 4.1.12
     transitivePeerDependencies:
       - jiti
       - less
@@ -7116,79 +6907,79 @@ snapshots:
       - sass-embedded
       - stylus
       - sugarss
-      - supports-color
       - terser
       - tsx
       - yaml
 
-  volar-service-css@0.0.62(@volar/language-service@2.4.11):
+  volar-service-css@0.0.67(@volar/language-service@2.4.27):
     dependencies:
       vscode-css-languageservice: 6.3.0
       vscode-languageserver-textdocument: 1.0.12
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
 
-  volar-service-emmet@0.0.62(@volar/language-service@2.4.11):
+  volar-service-emmet@0.0.67(@volar/language-service@2.4.27):
     dependencies:
-      '@emmetio/css-parser': 0.4.0
+      '@emmetio/css-parser': 0.4.1
       '@emmetio/html-matcher': 1.3.0
       '@vscode/emmet-helper': 2.9.3
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
 
-  volar-service-html@0.0.62(@volar/language-service@2.4.11):
+  volar-service-html@0.0.67(@volar/language-service@2.4.27):
     dependencies:
-      vscode-html-languageservice: 5.3.0
+      vscode-html-languageservice: 5.6.1
       vscode-languageserver-textdocument: 1.0.12
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
 
-  volar-service-prettier@0.0.62(@volar/language-service@2.4.11):
+  volar-service-prettier@0.0.67(@volar/language-service@2.4.27)(prettier@3.7.4):
     dependencies:
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
+      prettier: 3.7.4
 
-  volar-service-typescript-twoslash-queries@0.0.62(@volar/language-service@2.4.11):
+  volar-service-typescript-twoslash-queries@0.0.67(@volar/language-service@2.4.27):
     dependencies:
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
 
-  volar-service-typescript@0.0.62(@volar/language-service@2.4.11):
+  volar-service-typescript@0.0.67(@volar/language-service@2.4.27):
     dependencies:
       path-browserify: 1.0.1
-      semver: 7.7.1
-      typescript-auto-import-cache: 0.3.3
+      semver: 7.7.3
+      typescript-auto-import-cache: 0.3.6
       vscode-languageserver-textdocument: 1.0.12
       vscode-nls: 5.2.0
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
 
-  volar-service-yaml@0.0.62(@volar/language-service@2.4.11):
+  volar-service-yaml@0.0.67(@volar/language-service@2.4.27):
     dependencies:
-      vscode-uri: 3.0.8
-      yaml-language-server: 1.15.0
+      vscode-uri: 3.1.0
+      yaml-language-server: 1.19.2
     optionalDependencies:
-      '@volar/language-service': 2.4.11
+      '@volar/language-service': 2.4.27
 
   vscode-css-languageservice@6.3.0:
     dependencies:
       '@vscode/l10n': 0.0.18
       vscode-languageserver-textdocument: 1.0.12
       vscode-languageserver-types: 3.17.5
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
 
-  vscode-html-languageservice@5.3.0:
+  vscode-html-languageservice@5.6.1:
     dependencies:
       '@vscode/l10n': 0.0.18
       vscode-languageserver-textdocument: 1.0.12
       vscode-languageserver-types: 3.17.5
-      vscode-uri: 3.0.8
+      vscode-uri: 3.1.0
 
   vscode-json-languageservice@4.1.8:
     dependencies:
@@ -7196,17 +6987,10 @@ snapshots:
       vscode-languageserver-textdocument: 1.0.12
       vscode-languageserver-types: 3.17.5
       vscode-nls: 5.2.0
-      vscode-uri: 3.0.8
-
-  vscode-jsonrpc@6.0.0: {}
+      vscode-uri: 3.1.0
 
   vscode-jsonrpc@8.2.0: {}
 
-  vscode-languageserver-protocol@3.16.0:
-    dependencies:
-      vscode-jsonrpc: 6.0.0
-      vscode-languageserver-types: 3.16.0
-
   vscode-languageserver-protocol@3.17.5:
     dependencies:
       vscode-jsonrpc: 8.2.0
@@ -7214,14 +6998,8 @@ snapshots:
 
   vscode-languageserver-textdocument@1.0.12: {}
 
-  vscode-languageserver-types@3.16.0: {}
-
   vscode-languageserver-types@3.17.5: {}
 
-  vscode-languageserver@7.0.0:
-    dependencies:
-      vscode-languageserver-protocol: 3.16.0
-
   vscode-languageserver@9.0.1:
     dependencies:
       vscode-languageserver-protocol: 3.17.5
@@ -7265,27 +7043,27 @@ snapshots:
 
   y18n@5.0.8: {}
 
-  yaml-language-server@1.15.0:
+  yaml-language-server@1.19.2:
     dependencies:
+      '@vscode/l10n': 0.0.18
       ajv: 8.17.1
+      ajv-draft-04: 1.0.0(ajv@8.17.1)
       lodash: 4.17.21
+      prettier: 3.7.4
       request-light: 0.5.8
       vscode-json-languageservice: 4.1.8
-      vscode-languageserver: 7.0.0
+      vscode-languageserver: 9.0.1
       vscode-languageserver-textdocument: 1.0.12
       vscode-languageserver-types: 3.17.5
-      vscode-nls: 5.2.0
-      vscode-uri: 3.0.8
-      yaml: 2.2.2
-    optionalDependencies:
-      prettier: 2.8.7
+      vscode-uri: 3.1.0
+      yaml: 2.7.1
 
-  yaml@2.2.2: {}
-
-  yaml@2.7.0: {}
+  yaml@2.7.1: {}
 
   yaml@2.8.1: {}
 
+  yaml@2.8.2: {}
+
   yargs-parser@21.1.1: {}
 
   yargs@17.7.2:
@@ -7306,7 +7084,7 @@ snapshots:
 
   yoctocolors@2.1.1: {}
 
-  zod-to-json-schema@3.24.6(zod@3.25.76):
+  zod-to-json-schema@3.25.0(zod@3.25.76):
     dependencies:
       zod: 3.25.76
 
diff --git a/src/components/navigation.ts b/src/components/navigation.ts
index e688e27..50b33d7 100644
--- a/src/components/navigation.ts
+++ b/src/components/navigation.ts
@@ -43,6 +43,10 @@ export const navigation = [
         label: "Letter of Recommendation and Character Reference Policy",
         link: "/about/recommendations",
       },
+      {
+        label: "Community Membership Eligibility",
+        link: "/about/community-membership-eligibility",
+      },
     ].sort((a, b) => a.label.localeCompare(b.label)),
   },
   {
@@ -735,6 +739,10 @@ export const navigation = [
         label: "Join Our Volunteer Team",
         link: "/staff/apply",
       },
+      {
+        label: "Self-Care Resources for Staff",
+        link: "/staff/self-care-resources",
+      },
       {
         label: "Staff Application Evaluation Rubric",
         link: "/staff/rubric",
@@ -747,6 +755,14 @@ export const navigation = [
             label: "Accessibility Coordination Training for Staff",
             link: "/staff/training/accessibility-coordination",
           },
+          {
+            label: "Bias Recognition and Mitigation Training for Staff",
+            link: "/staff/training/bias-recognition-mitigation",
+          },
+          {
+            label: "Child Safety Training for Staff",
+            link: "/staff/training/child-safety",
+          },
           {
             label: "Community Growth Specialist Training for Staff",
             link: "/staff/training/community-growth-specialist",
@@ -759,6 +775,14 @@ export const navigation = [
             label: "Conflict Resolution Training for Staff",
             link: "/staff/training/conflict-resolution",
           },
+          {
+            label: "Content Moderation Fundamentals Training for Staff",
+            link: "/staff/training/content-moderation-fundamentals",
+          },
+          {
+            label: "Criminal Activity Training for Staff",
+            link: "/staff/training/criminal-activity",
+          },
           {
             label: "Crisis Response Training for Staff",
             link: "/staff/training/crisis-response",
@@ -771,10 +795,22 @@ export const navigation = [
             label: "Data Analytics and Reporting Training for Staff",
             link: "/staff/training/data-analytics-reporting",
           },
+          {
+            label: "Data Privacy and GDPR Compliance Training for Staff",
+            link: "/staff/training/data-privacy-gdpr",
+          },
+          {
+            label: "De-escalation Techniques Training for Staff",
+            link: "/staff/training/de-escalation-techniques",
+          },
           {
             label: "Documentation and Transparency Training for Staff",
             link: "/staff/training/documentation-transparency",
           },
+          {
+            label: "Harassment and Bullying Response Training for Staff",
+            link: "/staff/training/harassment-bullying-response",
+          },
           {
             label: "Inclusive Moderation Training for Staff",
             link: "/staff/training/inclusive-moderation",
@@ -791,12 +827,12 @@ export const navigation = [
             label: "Technical Contributor Training for Staff",
             link: "/staff/training/technical-contributor",
           },
+          {
+            label: "Trauma-Informed Moderation Training for Staff",
+            link: "/staff/training/trauma-informed-moderation",
+          },
         ].sort((a, b) => a.label.localeCompare(b.label)),
       },
-      {
-        label: "Staff Policy Self-Assessment",
-        link: "/staff/policy-self-assessment",
-      },
     ].sort((a, b) => a.label.localeCompare(b.label)),
   },
   {
diff --git a/src/content/docs/about/community-membership-eligibility.md b/src/content/docs/about/community-membership-eligibility.md
new file mode 100644
index 0000000..ecff060
--- /dev/null
+++ b/src/content/docs/about/community-membership-eligibility.md
@@ -0,0 +1,83 @@
+---
+title: Community Membership Eligibility
+---
+
+**ELIGIBILITY REQUIREMENTS FOR FREE SERVICES**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Policy Overview
+
+This Community Membership Eligibility Policy ("Policy") establishes the eligibility requirements for accessing free services provided by NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+
+### 1.2. Scope of Application
+
+This Policy applies to eligibility requirements for the following free services:
+
+**(a)** Letters of recommendation and character references;  
+**(b)** Mock interviews and interview preparation;  
+**(c)** Portfolio reviews (resume, LinkedIn, GitHub, portfolio website reviews);  
+**(d)** Development reviews (code reviews, project planning consultations, technical writing reviews);  
+**(e)** Any other free services that require active community membership as a prerequisite.
+
+## 2. ELIGIBILITY REQUIREMENT - ACTIVE COMMUNITY MEMBERSHIP
+
+### 2.1. General Eligibility Standard
+
+**IMPORTANT: Free services are provided EXCLUSIVELY to active members of our community. These services are NOT available to the general public or individuals who are not actively engaged in our community.**
+
+### 2.2. Eligibility Criteria
+
+**REQUIRED**: Requesters MUST be active, engaged members of our community with demonstrated participation, such as:
+
+**(a)** Active participation in our mentorship programme;  
+**(b)** Regular, ongoing community engagement in our Discord server or other community platforms;  
+**(c)** Active volunteer work or contribution to community projects;  
+**(d)** Sustained, meaningful interaction demonstrating active community membership;  
+**(e)** Professional collaboration or work relationship within our community context (where applicable).
+
+### 2.3. Verification and Discretion
+
+**(a)** We will verify community membership and activity before accepting any service request;  
+**(b)** We reserve the right to decline requests from individuals who are not active community members, regardless of other factors;  
+**(c)** Casual acquaintanceship or minimal interaction does NOT qualify as active membership;  
+**(d)** We will not provide services for individuals we have not directly interacted with or who lack active community connection;  
+**(e)** Priority may be given to individuals from underrepresented groups in technology who are active community members.
+
+## 3. NOT AN ACTIVE COMMUNITY MEMBER?
+
+### 3.1. Becoming an Active Community Member
+
+If you are not currently an active member of our community but are interested in accessing our free services, we encourage you to join our Discord community and become an active participant. Active community membership involves regular engagement, participation in discussions, and meaningful contribution to our community.
+
+**Join our Discord community:** [https://chat.nhcarrigan.com](https://chat.nhcarrigan.com)
+
+Once you have established active community membership through regular participation and engagement, you will be eligible to request our free services. We look forward to welcoming you to our community!
+
+### 3.2. What Constitutes Active Membership
+
+Active community membership is demonstrated through:
+
+**(a)** Regular participation in community discussions and activities;  
+**(b)** Meaningful contributions to community projects or initiatives;  
+**(c)** Consistent engagement over a period of time (not just a single interaction);  
+**(d)** Positive, constructive participation that aligns with our community values;  
+**(e)** Building relationships with other community members through genuine interaction.
+
+## 4. LIMITATION OF LIABILITY AND DISCLAIMERS
+
+### 4.1. Reference to Comprehensive Liability Framework
+
+**IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
+
+### 4.2. Eligibility Disclaimers
+
+**(a)** Meeting eligibility criteria does not guarantee service provision;  
+**(b)** We reserve the right to decline service requests at our sole discretion;  
+**(c)** Eligibility determinations are final and not subject to appeal;  
+**(d)** This Policy may be updated at any time, and eligibility requirements may change.
+
+---
+
+*For questions about community membership eligibility or our free services, please contact us through our [Contact Policy](/about/contact).*
+
diff --git a/src/content/docs/about/contact.md b/src/content/docs/about/contact.md
index 00ac68a..5931192 100644
--- a/src/content/docs/about/contact.md
+++ b/src/content/docs/about/contact.md
@@ -128,7 +128,7 @@ Our Discord server allows for both quick and in-depth communication.
 
 ### 2.2. Code Repositories
 
-Our code repositories are all self-hosted. Git accounts are only granted to staff members.
+Our code repositories are all self-hosted. Git accounts are only granted to Team members (volunteers) and Staff (paid employees).
 
 - Link: https://git.nhcarrigan.com
 - Features:
@@ -199,7 +199,7 @@ LinkedIn serves as our primary professional networking platform.
 
 #### 4.1.1. Connecting on LinkedIn
 
-When sending a connection request, please include a brief message explaining your interest. We typically respond to LinkedIn messages within 2-3 business days.
+When sending a connection request, please include a brief message explaining your interest. We typically respond to LinkedIn messages within 7-10 business days.
 
 ### 4.2. Professional Inquiries
 
@@ -335,8 +335,8 @@ We offer several email addresses for specific types of inquiries. Please use the
 - Subject Line: Please use a clear, concise subject line that summarizes your inquiry.
 - Content: Provide all relevant details in your initial email to expedite the response process.
 - Attachments: If sending attachments, please mention them in the email body and ensure they are in common file formats.
-- Response Time: We aim to respond to all emails within 2 business days. Complex inquiries may require additional time.
-- Follow-ups: If you haven't received a response after 3 business days, feel free to send a polite follow-up.
+- Response Time: We aim to respond to all emails within 7-10 business days. Complex inquiries may require additional time.
+- Follow-ups: If you haven't received a response after 10 business days, feel free to send a polite follow-up.
 
 ### 5.14. Email Privacy and Security
 
@@ -413,7 +413,34 @@ By sending a direct message, you acknowledge that you have read and agreed to th
 
 **IMPORTANT: While we value direct communication, we strongly encourage the use of our public channels whenever possible to foster community engagement and shared learning. Direct messages are the lowest priority communication channel and may experience significant response delays.**
 
-## 7. LIMITATION OF LIABILITY AND DISCLAIMERS
+## 7. RESPONSE TIME GUIDELINES
+
+### 7.1. Standard Response Times
+
+All inquiries and communications are handled with a standard response time of **7-10 business days**. This applies to:
+
+- General inquiries and questions
+- Support requests
+- Policy clarification requests
+- Programme-related inquiries
+- Technical support requests
+- Security reports
+- Content reports and moderation appeals
+- All other communications
+
+### 7.2. Business Days Definition
+
+Business days are defined as Monday through Friday, excluding weekends and holidays. Response times are calculated from the time your message is received during business hours.
+
+### 7.3. Complex Inquiries
+
+Complex inquiries may require additional time beyond the standard 7-10 business days. In such cases, we will acknowledge your inquiry within the standard timeframe and provide an estimated completion date.
+
+### 7.4. Follow-Up Communications
+
+If you have not received a response after 10 business days, you may send a polite follow-up. Please avoid sending multiple follow-ups at shorter intervals, as this may delay response processing.
+
+## 8. LIMITATION OF LIABILITY AND DISCLAIMERS
 
 ### 7.1. Reference to Comprehensive Liability Framework
 
@@ -437,7 +464,7 @@ For general inquiries about this Policy or our communication channels:
 
 **Discord Community:** https://chat.nhcarrigan.com
 
-**Response Time:** Within 48 hours for general inquiries
+**Response Time:** Within 7-10 business days for general inquiries
 
 ### 8.2. Policy Questions
 
diff --git a/src/content/docs/about/development-reviews.md b/src/content/docs/about/development-reviews.md
index 4df73bb..e31f9d7 100644
--- a/src/content/docs/about/development-reviews.md
+++ b/src/content/docs/about/development-reviews.md
@@ -8,7 +8,7 @@ title: Development Review Policy
 
 ### 1.1. Policy Overview
 
-This Development Review Policy ("Policy") establishes the terms, conditions, and procedures governing requests for code reviews, project planning consultations, and technical writing reviews from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+This Development Review Policy ("Policy") establishes the terms, conditions, and procedures governing requests for code reviews, project planning consultations, and technical writing reviews from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ### 1.2. Service Availability and Eligibility
 
@@ -33,8 +33,8 @@ This Policy applies to:
 **Code Review Services:**
 **(a)** Review of specific code submissions, pull requests, or codebase sections;
 **(b)** Feedback on code quality, best practices, and potential improvements;
-**(c)** Suggestions for code organization, structure, and maintainability;
-**(d)** Recommendations for performance optimization, security considerations, and testing;
+**(c)** Suggestions for code organisation, structure, and maintainability;
+**(d)** Recommendations for performance optimisation, security considerations, and testing;
 **(e)** Code reviews are provided based on industry best practices and professional standards;
 **(f)** We reserve the right to decline code reviews if code is incomplete, inaccessible, or exceeds reasonable scope;
 **(g)** Code reviews focus on specific, bounded submissions rather than entire codebases.
@@ -56,7 +56,7 @@ This Policy applies to:
 **Technical Writing Review Services:**
 **(a)** Review of technical blog posts, articles, documentation, README files, or other technical writing;
 **(b)** Feedback on clarity, structure, technical accuracy, and audience appropriateness;
-**(c)** Suggestions for improving readability, organization, and presentation of technical content;
+**(c)** Suggestions for improving readability, organisation, and presentation of technical content;
 **(d)** Recommendations for formatting, code examples, and visual aids;
 **(e)** Technical writing reviews are provided based on technical communication best practices and professional standards;
 **(f)** We reserve the right to decline technical writing reviews if content is incomplete, inaccessible, or exceeds reasonable scope;
@@ -80,25 +80,7 @@ This Policy applies to:
 
 **IMPORTANT: Development reviews are FREE services provided EXCLUSIVELY to active members of our community. These services are NOT available to the general public or individuals who are not actively engaged in our community.**
 
-**Eligibility Criteria:**
-**(a)** **REQUIRED**: Requesters MUST be active, engaged members of our community with demonstrated participation, such as:
-    **(i)** Active participation in our mentorship programme;
-    **(ii)** Regular, ongoing community engagement in our Discord server or other community platforms;
-    **(iii)** Active volunteer work or contribution to community projects;
-    **(iv)** Sustained, meaningful interaction demonstrating active community membership;
-**(b)** We will verify community membership and activity before accepting any development review request;
-**(c)** We reserve the right to decline requests from individuals who are not active community members, regardless of other factors;
-**(d)** Casual or minimal community interaction does NOT qualify as active membership;
-**(e)** We will not provide development reviews for individuals we have not directly interacted with or who lack active community connection;
-**(f)** Priority may be given to individuals from underrepresented groups in technology who are active community members.
-
-**Not an Active Community Member?**
-
-If you are not currently an active member of our community but are interested in accessing development review services, we encourage you to join our Discord community and become an active participant. Active community membership involves regular engagement, participation in discussions, and meaningful contribution to our community.
-
-**Join our Discord community:** [https://chat.nhcarrigan.com](https://chat.nhcarrigan.com)
-
-Once you have established active community membership through regular participation and engagement, you will be eligible to request development review services. We look forward to welcoming you to our community!
+For comprehensive eligibility requirements, eligibility criteria, and information about becoming an active community member, please refer to our [Community Membership Eligibility Policy](/about/community-membership-eligibility).
 
 ### 3.2. Request Information Requirements
 
@@ -199,9 +181,9 @@ Once you have established active community membership through regular participat
 
 **Request Frequency:**
 **(a)** We may limit the number of development reviews provided to the same requester within a specified time period;
-**(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritized at our discretion;
+**(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritised at our discretion;
 **(c)** We reserve the right to decline requests if we determine development review provision would be excessive or burdensome;
-**(d)** Requesters should coordinate multiple review needs to minimize burden and ensure timely completion;
+**(d)** Requesters should coordinate multiple review needs to minimise burden and ensure timely completion;
 **(e)** Updated materials may be submitted for re-review after implementing previous feedback.
 
 ### 6.3. Scope Limitations
@@ -268,7 +250,7 @@ For questions about this Policy or development review requests:
 
 **Subject Line:** Development Review Policy Inquiry - [Brief Description]
 
-**Response Time:** Within 48 hours for Policy-related inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.2. Request Status Inquiries
 
@@ -278,7 +260,7 @@ For questions about the status of submitted development review requests:
 
 **Subject Line:** Development Review Request Status - [Your Name]
 
-**Response Time:** Within 48 hours for status inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.3. General Contact
 
diff --git a/src/content/docs/about/donate.md b/src/content/docs/about/donate.md
index 7a4d7a2..d4b4fe4 100644
--- a/src/content/docs/about/donate.md
+++ b/src/content/docs/about/donate.md
@@ -8,7 +8,7 @@ title: Donation and Support Policy
 
 ### 1.1. Policy Overview
 
-This Donation and Support Policy ("Policy") establishes the terms, conditions, and procedures governing voluntary financial contributions and other forms of support to NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+This Donation and Support Policy ("Policy") establishes the terms, conditions, and procedures governing voluntary financial contributions and other forms of support to NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ### 1.2. Legal Framework Integration
 
@@ -212,7 +212,7 @@ For questions about donations or support options:
 
 **Email:** donors@nhcarrigan.com
 
-**Response Time:** Within 48 hours for donation-related inquiries
+**Response Time:** Within 7-10 business days for donation-related inquiries
 
 ### 9.2. General Contact
 
diff --git a/src/content/docs/about/hire.md b/src/content/docs/about/hire.md
index b733d22..77668b6 100644
--- a/src/content/docs/about/hire.md
+++ b/src/content/docs/about/hire.md
@@ -8,7 +8,7 @@ title: Professional Services and Commission Policy
 
 ### 1.1. Policy Overview
 
-This Professional Services and Commission Policy ("Policy") establishes the terms, conditions, and procedures governing professional services, consulting engagements, and commission-based work provided by NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+This Professional Services and Commission Policy ("Policy") establishes the terms, conditions, and procedures governing professional services, consulting engagements, and commission-based work provided by NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ### 1.2. Legal Framework Integration
 
@@ -235,7 +235,7 @@ For inquiries about professional services or to submit commission requests:
 
 **Email:** contact@nhcarrigan.com
 
-**Response Time:** Within 48 hours for service inquiries
+**Response Time:** Within 7-10 business days for service inquiries
 
 ### 11.2. General Contact
 
diff --git a/src/content/docs/about/mentorship.md b/src/content/docs/about/mentorship.md
index 526e99e..227ff65 100644
--- a/src/content/docs/about/mentorship.md
+++ b/src/content/docs/about/mentorship.md
@@ -81,7 +81,17 @@ By enrolling in the Programme, Mentees acknowledge and agree that they have:
 **(d)** Additional resources and Programme updates are provided as part of programme participation;
 **(e)** We reserve the right to modify or discontinue specific resources or support services with reasonable notice.
 
-### 3.5. Service Limitations and Disclaimers
+### 3.5. Self-Guided Programme Structure
+
+**Programme Philosophy:**
+**(a)** The programme is designed to be self-guided and self-managed;
+**(b)** Participants work at their own pace with no mandatory deadlines or review requirements;
+**(c)** Comprehensive documentation, templates, and resources are provided to support independent learning;
+**(d)** Reviews, approvals, and support are optional and available upon request, not guaranteed;
+**(e)** Programme leadership and mentors are not monitoring every participant action or progress;
+**(f)** **IMPORTANT: To get the most value from the programme experience, participants should actively ask mentors questions as much as possible. Mentors are available to help, but they rely on participants to initiate contact and ask for assistance when needed.**
+
+### 3.6. Service Limitations and Disclaimers
 
 **IMPORTANT DISCLAIMERS:**
 **(a)** Programme services and resources are provided "as is" without warranties of any kind;
@@ -231,7 +241,7 @@ For questions about the Programme or to submit cancellation notices:
 
 **Email:** contact@nhcarrigan.com
 
-**Response Time:** Within 48 hours for Programme-related inquiries
+**Response Time:** Within 7-10 business days for Programme-related inquiries
 
 ### 11.2. General Contact
 
diff --git a/src/content/docs/about/mission.md b/src/content/docs/about/mission.md
index 52af06c..5a99aa5 100644
--- a/src/content/docs/about/mission.md
+++ b/src/content/docs/about/mission.md
@@ -2,7 +2,7 @@
 title: Mission Statement
 ---
 
-This Mission Statement ("Statement") articulates the core values and guiding principles of NHCarrigan ("The Company") in its efforts to build inclusive, ethical, and sustainable technology solutions and foster welcoming online communities. This Statement operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Policies, and all applicable legal protections by reference.
+This Mission Statement ("Statement") articulates the core values and guiding principles of NHCarrigan ("The Company") in its efforts to build inclusive, ethical, and sustainable technology solutions and foster welcoming online communities. This Statement operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ## 1. Core Values
 
@@ -30,7 +30,7 @@ Our projects are community-centric, encouraging collaboration and input from div
 
 The Company is committed to tearing down the systemic and social barriers that exist in the tech industry. We actively work to make the field more accessible to individuals from all backgrounds, particularly those who have historically been excluded.
 
-### 1.7. Challenging Toxic Behaviors
+### 1.7. Challenging Toxic Behaviours
 
 We recognise that toxic behaviours and exclusionary practices harm communities. The Company shall take a proactive stance in challenging these behaviours within our industry and within the tech communities we interact with, fostering spaces where collaboration, respect, and growth thrive.
 
diff --git a/src/content/docs/about/mock-interviews.md b/src/content/docs/about/mock-interviews.md
index ea025fb..9deb5c2 100644
--- a/src/content/docs/about/mock-interviews.md
+++ b/src/content/docs/about/mock-interviews.md
@@ -8,7 +8,7 @@ title: Mock Interview Policy
 
 ### 1.1. Policy Overview
 
-This Mock Interview Policy ("Policy") establishes the terms, conditions, and procedures governing requests for mock interviews and interview preparation sessions from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+This Mock Interview Policy ("Policy") establishes the terms, conditions, and procedures governing requests for mock interviews and interview preparation sessions from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ### 1.2. Service Availability and Eligibility
 
@@ -76,25 +76,7 @@ This Policy applies to:
 
 **IMPORTANT: Mock interviews are FREE services provided EXCLUSIVELY to active members of our community. These services are NOT available to the general public or individuals who are not actively engaged in our community.**
 
-**Eligibility Criteria:**
-**(a)** **REQUIRED**: Requesters MUST be active, engaged members of our community with demonstrated participation, such as:
-    **(i)** Active participation in our mentorship programme;
-    **(ii)** Regular, ongoing community engagement in our Discord server or other community platforms;
-    **(iii)** Active volunteer work or contribution to community projects;
-    **(iv)** Sustained, meaningful interaction demonstrating active community membership;
-**(b)** We will verify community membership and activity before accepting any mock interview request;
-**(c)** We reserve the right to decline requests from individuals who are not active community members, regardless of other factors;
-**(d)** Casual or minimal community interaction does NOT qualify as active membership;
-**(e)** We will not provide mock interviews for individuals we have not directly interacted with or who lack active community connection;
-**(f)** Priority may be given to individuals from underrepresented groups in technology who are active community members.
-
-**Not an Active Community Member?**
-
-If you are not currently an active member of our community but are interested in accessing mock interview services, we encourage you to join our Discord community and become an active participant. Active community membership involves regular engagement, participation in discussions, and meaningful contribution to our community.
-
-**Join our Discord community:** [https://chat.nhcarrigan.com](https://chat.nhcarrigan.com)
-
-Once you have established active community membership through regular participation and engagement, you will be eligible to request mock interview services. We look forward to welcoming you to our community!
+For comprehensive eligibility requirements, eligibility criteria, and information about becoming an active community member, please refer to our [Community Membership Eligibility Policy](/about/community-membership-eligibility).
 
 ### 3.2. Request Information Requirements
 
@@ -208,7 +190,7 @@ Once you have established active community membership through regular participat
 **(a)** We may limit the number of mock interviews provided to the same requester within a specified time period;
 **(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritized at our discretion;
 **(c)** We reserve the right to decline requests if we determine mock interview provision would be excessive or burdensome;
-**(d)** Requesters should coordinate multiple interview preparation needs to minimize burden and ensure timely scheduling;
+**(d)** Requesters should coordinate multiple interview preparation needs to minimise burden and ensure timely scheduling;
 **(e)** Follow-up mock interviews may be available after implementing previous feedback and additional preparation.
 
 ### 6.3. Prohibited Uses
@@ -266,7 +248,7 @@ For questions about this Policy or mock interview requests:
 
 **Subject Line:** Mock Interview Policy Inquiry - [Brief Description]
 
-**Response Time:** Within 48 hours for Policy-related inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.2. Request Status Inquiries
 
@@ -276,7 +258,7 @@ For questions about the status of submitted mock interview requests:
 
 **Subject Line:** Mock Interview Request Status - [Your Name]
 
-**Response Time:** Within 48 hours for status inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.3. General Contact
 
diff --git a/src/content/docs/about/portfolio-reviews.md b/src/content/docs/about/portfolio-reviews.md
index 50d021a..6dc8c27 100644
--- a/src/content/docs/about/portfolio-reviews.md
+++ b/src/content/docs/about/portfolio-reviews.md
@@ -8,7 +8,7 @@ title: Portfolio Review Policy
 
 ### 1.1. Policy Overview
 
-This Portfolio Review Policy ("Policy") establishes the terms, conditions, and procedures governing requests for reviews of resumes, LinkedIn profiles, GitHub profiles, portfolios, and related professional materials from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+This Portfolio Review Policy ("Policy") establishes the terms, conditions, and procedures governing requests for reviews of resumes, LinkedIn profiles, GitHub profiles, portfolios, and related professional materials from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ### 1.2. Service Availability and Eligibility
 
@@ -22,7 +22,7 @@ This Portfolio Review Policy ("Policy") establishes the terms, conditions, and p
 
 This Policy applies to:
 **(a)** All requests for resume reviews and feedback;
-**(b)** All requests for LinkedIn profile reviews and optimization suggestions;
+**(b)** All requests for LinkedIn profile reviews and optimisation suggestions;
 **(c)** All requests for GitHub profile reviews and improvement recommendations;
 **(d)** All requests for portfolio website reviews and feedback;
 **(e)** All requests for related professional profile materials reviews;
@@ -34,7 +34,7 @@ This Policy applies to:
 
 **Resume Review Services:**
 **(a)** Comprehensive review of resume content, formatting, and structure;
-**(b)** Feedback on technical skills presentation and organization;
+**(b)** Feedback on technical skills presentation and organisation;
 **(c)** Suggestions for improving clarity, impact, and ATS (Applicant Tracking System) compatibility;
 **(d)** Recommendations for highlighting relevant experience and projects;
 **(e)** Resume reviews are provided based on industry best practices and professional standards;
@@ -43,7 +43,7 @@ This Policy applies to:
 ### 2.2. LinkedIn Profile Reviews
 
 **LinkedIn Profile Review Services:**
-**(a)** Review of LinkedIn profile completeness and optimization;
+**(a)** Review of LinkedIn profile completeness and optimisation;
 **(b)** Feedback on headline, summary, and experience sections;
 **(c)** Suggestions for improving profile visibility and professional branding;
 **(d)** Recommendations for skills, endorsements, and recommendations;
@@ -54,9 +54,9 @@ This Policy applies to:
 
 **GitHub Profile Review Services:**
 **(a)** Review of GitHub profile README and pinned repositories;
-**(b)** Feedback on repository organization and documentation quality;
+**(b)** Feedback on repository organisation and documentation quality;
 **(c)** Suggestions for improving contribution graph visibility and project presentation;
-**(d)** Recommendations for profile optimization and professional presentation;
+**(d)** Recommendations for profile optimisation and professional presentation;
 **(e)** GitHub reviews are provided based on open source and developer community best practices;
 **(f)** We reserve the right to decline GitHub reviews if profiles are private or inaccessible.
 
@@ -87,25 +87,7 @@ This Policy applies to:
 
 **IMPORTANT: Portfolio reviews are FREE services provided EXCLUSIVELY to active members of our community. These services are NOT available to the general public or individuals who are not actively engaged in our community.**
 
-**Eligibility Criteria:**
-**(a)** **REQUIRED**: Requesters MUST be active, engaged members of our community with demonstrated participation, such as:
-    **(i)** Active participation in our mentorship programme;
-    **(ii)** Regular, ongoing community engagement in our Discord server or other community platforms;
-    **(iii)** Active volunteer work or contribution to community projects;
-    **(iv)** Sustained, meaningful interaction demonstrating active community membership;
-**(b)** We will verify community membership and activity before accepting any review request;
-**(c)** We reserve the right to decline requests from individuals who are not active community members, regardless of other factors;
-**(d)** Casual or minimal community interaction does NOT qualify as active membership;
-**(e)** We will not provide reviews for individuals we have not directly interacted with or who lack active community connection;
-**(f)** Priority may be given to individuals from underrepresented groups in technology who are active community members.
-
-**Not an Active Community Member?**
-
-If you are not currently an active member of our community but are interested in accessing portfolio review services, we encourage you to join our Discord community and become an active participant. Active community membership involves regular engagement, participation in discussions, and meaningful contribution to our community.
-
-**Join our Discord community:** [https://chat.nhcarrigan.com](https://chat.nhcarrigan.com)
-
-Once you have established active community membership through regular participation and engagement, you will be eligible to request portfolio review services. We look forward to welcoming you to our community!
+For comprehensive eligibility requirements, eligibility criteria, and information about becoming an active community member, please refer to our [Community Membership Eligibility Policy](/about/community-membership-eligibility).
 
 ### 3.2. Request Information Requirements
 
@@ -209,9 +191,9 @@ Once you have established active community membership through regular participat
 
 **Request Frequency:**
 **(a)** We may limit the number of reviews provided to the same requester within a specified time period;
-**(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritized at our discretion;
+**(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritised at our discretion;
 **(c)** We reserve the right to decline requests if we determine review provision would be excessive or burdensome;
-**(d)** Requesters should coordinate multiple review needs to minimize burden and ensure timely completion;
+**(d)** Requesters should coordinate multiple review needs to minimise burden and ensure timely completion;
 **(e)** Updated materials may be submitted for re-review after implementing previous feedback.
 
 ### 6.3. Prohibited Uses
@@ -268,7 +250,7 @@ For questions about this Policy or portfolio review requests:
 
 **Subject Line:** Portfolio Review Policy Inquiry - [Brief Description]
 
-**Response Time:** Within 48 hours for Policy-related inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.2. Request Status Inquiries
 
@@ -278,7 +260,7 @@ For questions about the status of submitted portfolio review requests:
 
 **Subject Line:** Portfolio Review Request Status - [Your Name]
 
-**Response Time:** Within 48 hours for status inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.3. General Contact
 
diff --git a/src/content/docs/about/recommendations.md b/src/content/docs/about/recommendations.md
index 64e7387..de32d71 100644
--- a/src/content/docs/about/recommendations.md
+++ b/src/content/docs/about/recommendations.md
@@ -8,7 +8,7 @@ title: Letter of Recommendation and Character Reference Policy
 
 ### 1.1. Policy Overview
 
-This Letter of Recommendation and Character Reference Policy ("Policy") establishes the terms, conditions, and procedures governing requests for letters of recommendation and character references from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, and all applicable legal protections by reference.
+This Letter of Recommendation and Character Reference Policy ("Policy") establishes the terms, conditions, and procedures governing requests for letters of recommendation and character references from NHCarrigan ("we," "us," "our," or "the Company"). This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference.
 
 ### 1.2. Service Availability and Eligibility
 
@@ -68,25 +68,7 @@ This Policy applies to:
 
 **IMPORTANT: Letters of recommendation and character references are FREE services provided EXCLUSIVELY to active members of our community. These services are NOT available to the general public or individuals who are not actively engaged in our community.**
 
-**Eligibility Criteria:**
-**(a)** **REQUIRED**: Requesters MUST be active, engaged members of our community with demonstrated participation, such as:
-    **(i)** Active participation in our mentorship programme;
-    **(ii)** Regular, ongoing community engagement in our Discord server or other community platforms;
-    **(iii)** Active volunteer work or contribution to community projects;
-    **(iv)** Sustained, meaningful interaction demonstrating active community membership;
-    **(v)** Professional collaboration or work relationship within our community context;
-**(b)** We will verify community membership and activity before accepting any recommendation request;
-**(c)** We reserve the right to decline requests from individuals who are not active community members, regardless of other factors;
-**(d)** Casual acquaintanceship or minimal interaction does NOT qualify as active membership;
-**(e)** We will not provide recommendations for individuals we have not directly interacted with or who lack active community connection.
-
-**Not an Active Community Member?**
-
-If you are not currently an active member of our community but are interested in accessing recommendation services, we encourage you to join our Discord community and become an active participant. Active community membership involves regular engagement, participation in discussions, and meaningful contribution to our community.
-
-**Join our Discord community:** [https://chat.nhcarrigan.com](https://chat.nhcarrigan.com)
-
-Once you have established active community membership through regular participation and engagement, you will be eligible to request recommendation services. We look forward to welcoming you to our community!
+For comprehensive eligibility requirements, eligibility criteria, and information about becoming an active community member, please refer to our [Community Membership Eligibility Policy](/about/community-membership-eligibility).
 
 ### 3.2. Request Information Requirements
 
@@ -182,7 +164,7 @@ Once you have established active community membership through regular participat
 **(a)** We may limit the number of recommendations provided to the same requester within a specified time period;
 **(b)** Multiple simultaneous requests from the same requester may be consolidated or prioritized at our discretion;
 **(c)** We reserve the right to decline requests if we determine recommendation provision would be excessive or burdensome;
-**(d)** Requesters should coordinate multiple recommendation needs to minimize burden and ensure timely completion.
+**(d)** Requesters should coordinate multiple recommendation needs to minimise burden and ensure timely completion.
 
 ### 6.3. Prohibited Uses
 
@@ -237,7 +219,7 @@ For questions about this Policy or recommendation requests:
 
 **Subject Line:** Recommendation Policy Inquiry - [Brief Description]
 
-**Response Time:** Within 48 hours for Policy-related inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.2. Request Status Inquiries
 
@@ -247,7 +229,7 @@ For questions about the status of submitted recommendation requests:
 
 **Subject Line:** Recommendation Request Status - [Your Name]
 
-**Response Time:** Within 48 hours for status inquiries
+**Response Time:** See our [Contact Policy](/about/contact) for response time expectations.
 
 ### 9.3. General Contact
 
diff --git a/src/content/docs/community/coc.md b/src/content/docs/community/coc.md
index 209f353..680cfd9 100644
--- a/src/content/docs/community/coc.md
+++ b/src/content/docs/community/coc.md
@@ -19,19 +19,7 @@ Our community is built upon the following core principles:
 
 ### 1.3. Legal Framework and Policy Integration
 
-This Code operates within and supplements our comprehensive legal and policy framework, including:
-
-**(a)** **Terms of Service**: Fundamental legal relationship and user obligations;
-
-**(b)** **Acceptable Use Policy**: Detailed prohibited activities and usage restrictions;
-
-**(c)** **Content and Moderation Policy**: Comprehensive content standards and moderation procedures;
-
-**(d)** **Privacy Policy**: Data protection and privacy rights;
-
-**(e)** **Limitation of Liability and Indemnification Policy**: Legal protections and risk allocation;
-
-**(f)** **All other applicable legal policies**: Export control, service level agreements, and specialised policies.
+This Code operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Acceptable Use Policy, Content and Moderation Policy, Limitation of Liability and Indemnification Policy, and all applicable legal protections by reference.
 
 **IMPORTANT**: Where this Code overlaps with our comprehensive legal policies, users are subject to both sets of requirements. For detailed enforcement procedures, content moderation standards, and legal protections, refer to the applicable specialised policies incorporated by reference.
 
@@ -248,11 +236,11 @@ Effective reports should include:
 
 #### 5.2.1. Initial Response Protocol
 Upon receiving a report, Community Leaders will:
-- Acknowledge receipt within 24 hours when possible
+- Acknowledge receipt within 7-10 business days when possible
 - Conduct an initial assessment of the report's severity and scope
 - Take immediate protective measures if necessary to ensure community safety
 - Recuse any Community Leaders who have conflicts of interest in the matter
-- Begin formal investigation procedures within 72 hours
+- Begin formal investigation procedures within 7-10 business days
 
 #### 5.2.2. Investigation Standards
 All investigations will adhere to the following standards:
@@ -534,7 +522,7 @@ Violations of advertising and promotion restrictions will be addressed through:
 
 #### 9.1.1. English as Primary Language
 The official language of Our Community is English, and all community interactions, discussions, and contributions should be conducted in English to ensure:
-- Clear communication among all community members
+- Clear communication amongst all community members
 - Effective moderation and community management
 - Consistency across all community platforms and activities
 - Accessibility for the broadest range of community members
diff --git a/src/content/docs/community/feedback.md b/src/content/docs/community/feedback.md
index b3b9d75..532971c 100644
--- a/src/content/docs/community/feedback.md
+++ b/src/content/docs/community/feedback.md
@@ -35,7 +35,7 @@ We believe that community members are the ultimate experts on their own experien
 
 ### 1.4. Legal Framework Integration
 
-This Policy operates within our comprehensive legal and policy framework, including our Terms of Service, Privacy Policy, Community Code of Conduct, and Community Leadership and Governance Policy, all of which are incorporated herein by reference.
+This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Community Leadership and Governance Policy, and all applicable legal protections by reference.
 
 ## 2. Feedback Channels and Communication Systems
 
@@ -208,7 +208,7 @@ When immediate policy changes are necessary for community safety:
 - **Regular policy effectiveness surveys** gathering community input on how well policies are meeting their intended objectives
 - **Community impact assessment** evaluating policy effects on different community groups and addressing unintended consequences
 - **Policy modification processes** incorporating community feedback and assessment results into ongoing policy improvement
-- **Community success metrics** developed collaboratively to measure progress toward shared community goals and values
+- **Community success metrics** developed collaboratively to measure progress towards shared community goals and values
 
 ## 5. Special Consultation and Participation Programs
 
@@ -222,7 +222,7 @@ When immediate policy changes are necessary for community safety:
 - **Cultural competency** in consultation design and facilitation to encourage authentic participation from diverse community members
 - **Language and accessibility support** removing barriers to participation for community members with diverse needs
 
-**Specialized Advisory Groups:**
+**Specialised Advisory Groups:**
 - **Rotating advisory panels** including community members from diverse backgrounds and experience levels
 - **Issue-specific consultation groups** bringing together community members with relevant expertise or lived experience
 - **Accessibility advisory groups** providing ongoing input on inclusion and accommodation needs and improvements
@@ -236,7 +236,7 @@ When immediate policy changes are necessary for community safety:
 - **Peer review and community refinement** processes helping improve community-driven proposals through collaborative development
 - **Implementation support** for community-approved initiatives including resource allocation and ongoing assistance
 
-**Community Organizing and Advocacy:**
+**Community Organising and Advocacy:**
 - **Community organising support** for members who want to advocate for specific changes or improvements
 - **Coalition building assistance** helping community members with shared interests collaborate effectively on improvement initiatives
 - **Advocacy training and resources** empowering community members to effectively participate in governance and change processes
@@ -267,7 +267,7 @@ When immediate policy changes are necessary for community safety:
 #### 6.1.1. Individual Feedback Acknowledgment
 
 **Personal Response Commitments:**
-- **Acknowledgment within 48 hours** for all individual feedback submissions and policy input
+- **Acknowledgment within 7-10 business days** for all individual feedback submissions and policy input
 - **Detailed responses within 14 days** addressing specific concerns, suggestions, and questions raised by community members
 - **Follow-up communication** ensuring community members feel heard and providing updates on how their input is being considered
 - **Personal consultation opportunities** for community members who need additional discussion or clarification about their feedback
diff --git a/src/content/docs/community/guide.md b/src/content/docs/community/guide.md
index abf4008..58c8a02 100644
--- a/src/content/docs/community/guide.md
+++ b/src/content/docs/community/guide.md
@@ -614,7 +614,7 @@ When platform features allow:
 #### 7.5.1. Respectful Responses to Warnings
 Community members should demonstrate respect for content warning practices by:
 - **Taking Warnings Seriously**: Never mock, dismiss, or minimise the importance of content warnings
-- **Individual Needs Recognition**: Understanding that warning needs vary among individuals
+- **Individual Needs Recognition**: Understanding that warning needs vary amongst individuals
 - **Gracious Compliance**: Accepting requests for additional warnings without defensiveness
 - **Supportive Behaviour**: Encouraging and normalising content warning usage
 
@@ -645,7 +645,7 @@ Conflicts, disagreements, and differences of opinion represent natural and inevi
 #### 8.1.2. Restorative Justice Principles
 Our conflict resolution approach emphasises:
 - **Relationship Repair**: Focus on healing and strengthening community relationships
-- **Mutual Understanding**: Encouraging empathy and perspective-taking among conflicting parties
+- **Mutual Understanding**: Encouraging empathy and perspective-taking amongst conflicting parties
 - **Learning Opportunities**: Using conflicts as chances for personal and community growth
 - **Collaborative Solutions**: Seeking win-win outcomes that address underlying needs and concerns
 - **Community Strengthening**: Leveraging conflict resolution to build more resilient community bonds
@@ -700,7 +700,7 @@ When emotions run high or productive communication becomes difficult:
 
 **Recognition Signs:**
 - Increasing emotional intensity or defensive responses
-- Circular arguments without progress toward resolution
+- Circular arguments without progress towards resolution
 - Personal attacks or escalatory language
 - Diminishing ability to listen or consider alternative perspectives
 
@@ -732,8 +732,8 @@ When direct communication fails to resolve conflicts, community-supported mediat
 Community members serving as mediators should:
 - **Maintain Neutrality**: Avoid taking sides or advocating for specific outcomes
 - **Facilitate Communication**: Help parties express themselves clearly and listen effectively
-- **Encourage Understanding**: Promote empathy and perspective-taking among parties
-- **Focus on Solutions**: Guide discussions toward constructive problem-solving
+- **Encourage Understanding**: Promote empathy and perspective-taking amongst parties
+- **Focus on Solutions**: Guide discussions towards constructive problem-solving
 - **Respect Confidentiality**: Maintain privacy about mediation discussions unless agreed otherwise
 
 ### 8.5. Staff Intervention and Escalation
@@ -926,7 +926,7 @@ When community enjoyment becomes consistently problematic:
 **Issue Recognition:**
 - Multiple members reporting similar negative experiences
 - Consistent patterns of conflict or dissatisfaction
-- Declining participation or enthusiasm among established members
+- Declining participation or enthusiasm amongst established members
 - Feedback indicating community culture issues
 
 **Systemic Solutions:**
@@ -951,7 +951,7 @@ Our community adopts a permissive approach to mini-moderation, recognising its v
 Appropriate mini-moderation includes:
 
 **Welcoming and Integration Support:**
-- Gently guiding new members toward understanding community norms and expectations
+- Gently guiding new members towards understanding community norms and expectations
 - Providing helpful information about community resources, channels, or practices
 - Offering assistance with platform-specific features or navigation
 - Sharing educational resources about community policies or inclusive practices
@@ -1043,7 +1043,7 @@ When mini-moderation becomes necessary:
 
 **Indirect Redirection:**
 - Model appropriate behaviour without explicitly correcting others
-- Redirect conversations toward constructive directions through your own contributions
+- Redirect conversations towards constructive directions through your own contributions
 - Ask clarifying questions that encourage reflection rather than making direct accusations
 - Provide positive alternatives that naturally guide discussions in better directions
 
diff --git a/src/content/docs/community/leadership.md b/src/content/docs/community/leadership.md
index 25b185a..10a83df 100644
--- a/src/content/docs/community/leadership.md
+++ b/src/content/docs/community/leadership.md
@@ -12,7 +12,7 @@ This Community Leadership and Governance Policy (hereinafter referred to as "the
 
 Our community leadership operates on the following foundational principles:
 
-**(a)** **Servant Leadership**: Leaders serve the community rather than wielding authority for personal benefit;
+**(a)** **Servant Leadership**: Leaders serve the community rather than wielding authority for personal benefit. For a comprehensive explanation of servant leadership principles and how they apply to all staff roles, see [Staff Role Definition and Principles](/staff/handbook#22-staff-role-definition-and-principles) in the Staff Handbook;
 
 **(b)** **Transparency**: Decision-making processes and rationales are clearly communicated to the community;
 
@@ -60,7 +60,7 @@ Our community leadership operates through a structured hierarchy designed to ens
 
 - **Moderators**: Front-line community moderation and member support
 - **Mentors**: New member guidance and peer support programmes
-- **Subject Matter Experts**: Specialized knowledge and educational support
+- **Subject Matter Experts**: Specialised knowledge and educational support
 - **Technical Contributors**: Development support and technical expertise for community platforms and tools
 - **Quality Assurance Coordinator**: Testing and quality control for community platforms and resources
 - **Data and Analytics Coordinator**: Community metrics analysis and reporting
@@ -271,7 +271,7 @@ Our community leadership operates through a structured hierarchy designed to ens
 
 **Data and Analytics Coordinator:**
 
-- Collect and analyze community engagement metrics and participation data
+- Collect and analyse community engagement metrics and participation data
 - Prepare regular reports on community health, growth trends, and member satisfaction
 - Manage community surveys and feedback analysis for leadership decision-making
 - Support leadership team with data insights and trend identification
@@ -319,7 +319,7 @@ Our community leadership operates through a structured hierarchy designed to ens
 - Monitor member satisfaction and engagement levels across the community
 - Mediate minor conflicts and facilitate communication between members
 - Collect member feedback and suggestions for community improvements
-- Maintain positive relationships and foster sense of belonging among community members
+- Maintain positive relationships and foster sense of belonging amongst community members
 
 **Documentation Support Technicians:**
 
diff --git a/src/content/docs/dev/contributing.md b/src/content/docs/dev/contributing.md
index d54f425..287f2f4 100644
--- a/src/content/docs/dev/contributing.md
+++ b/src/content/docs/dev/contributing.md
@@ -540,7 +540,7 @@ Help improve the project's stability by:
 Foster a welcoming and inclusive community by:
 
 - Welcoming new contributors and helping them get started
-- Organizing or participating in community events or meetups
+- Organising or participating in community events or meetups
 - Promoting the project on social media or relevant forums
 - Helping to moderate community discussions
 
@@ -566,7 +566,7 @@ If you have connections or experience in this area:
 
 - Help identify potential sponsors or grants
 - Assist with writing grant applications
-- Organize fundraising events or campaigns
+- Organise fundraising events or campaigns
 
 Or even make a donation yourself!
 
diff --git a/src/content/docs/legal/aup.md b/src/content/docs/legal/aup.md
index ad92fd3..f44616a 100644
--- a/src/content/docs/legal/aup.md
+++ b/src/content/docs/legal/aup.md
@@ -8,7 +8,7 @@ title: Acceptable Use Policy
 
 ### 1.1. Policy Purpose
 
-This Acceptable Use Policy ("AUP") establishes comprehensive guidelines for the appropriate use of all services, applications, and platforms provided by NHCarrigan ("we," "us," "our," or "the Company"). This AUP supplements our Terms of Service and other applicable policies to provide detailed guidance on acceptable and prohibited usage patterns.
+This Acceptable Use Policy ("AUP") establishes comprehensive guidelines for the appropriate use of all services, applications, and platforms provided by NHCarrigan ("we," "us," "our," or "the Company"). This AUP operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, and all applicable legal protections by reference, and supplements these policies to provide detailed guidance on acceptable and prohibited usage patterns.
 
 ### 1.2. Scope of Application
 
@@ -28,19 +28,7 @@ This AUP applies to all users of our Services, including:
 
 ### 1.3. Integration with Other Policies
 
-This AUP operates in conjunction with our comprehensive policy framework:
-
-**(a)** Our Terms of Service, which establish the fundamental legal relationship;
-
-**(b)** Our Community Code of Conduct, which governs community interactions;
-
-**(c)** Our Privacy Policy, which governs data collection and processing;
-
-**(d)** Our Service Level Agreement and Warranty Disclaimer, which define service expectations and warranties;
-
-**(e)** Our Content and Moderation Policy, which establishes detailed content standards and moderation procedures;
-
-**(f)** Our Limitation of Liability and Indemnification Policy, which governs all liability and risk allocation matters;
+This AUP operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Service Level Agreement, Content and Moderation Policy, Limitation of Liability and Indemnification Policy, and all applicable legal protections by reference.
 
 **(g)** Our Export Control and Sanctions Compliance Policy, which governs international trade compliance;
 
@@ -524,7 +512,7 @@ Users may appeal enforcement actions through:
 
 **(b)** **Evidence Submission**: Opportunity to provide evidence and explanations;
 
-**(c)** **Independent Review**: Review by staff members not involved in the original decision;
+**(c)** **Independent Review**: Review by Team members not involved in the original decision;
 
 **(d)** **Corrective Actions**: Opportunity to take corrective actions to address violations;
 
@@ -670,7 +658,7 @@ For questions about this AUP:
 
 **Subject Line:** AUP Inquiry - [Brief Description]
 
-**Response Time:** Within 3 business days for policy clarification requests
+**Response Time:** Within 7-10 business days for policy clarification requests
 
 ### 11.2. Violation Reporting
 
@@ -680,7 +668,7 @@ To report policy violations:
 
 **Subject Line:** Policy Violation Report - [Service/Platform]
 
-**Response Time:** Within 24 hours for urgent safety issues, 48 hours for standard reports
+**Response Time:** Within 7-10 business days for all reports
 
 ### 11.3. Appeals and Disputes
 
@@ -700,7 +688,7 @@ For technical issues related to policy compliance:
 
 **Discord Community:** https://chat.nhcarrigan.com
 
-**Response Time:** Within 48 hours for technical support requests
+**Response Time:** Within 7-10 business days for technical support requests
 
 ---
 
diff --git a/src/content/docs/legal/community-growth-policy.md b/src/content/docs/legal/community-growth-policy.md
index 9183d14..6869f51 100644
--- a/src/content/docs/legal/community-growth-policy.md
+++ b/src/content/docs/legal/community-growth-policy.md
@@ -30,7 +30,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 
 **Social Justice Alignment:**
 - **Anti-Oppression Focus**: Growth efforts that actively support marginalised communities
-- **Accessibility Prioritization**: Ensuring growth includes people with diverse abilities and needs
+- **Accessibility Prioritisation**: Ensuring growth includes people with diverse abilities and needs
 - **Economic Justice**: Growth that doesn't exclude people based on economic circumstances
 - **Environmental Responsibility**: Sustainable growth practices that minimise environmental impact
 - **Democratic Participation**: Growth that strengthens rather than dilutes community democracy
@@ -84,7 +84,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 
 **Platform-Specific Approaches:**
 - **Discord**: Share invites thoughtfully with context about what people can expect
-- **Reddit**: Participate authentically in relevant subreddits while mentioning community when appropriate
+- **Reddit**: Participate authentically in relevant subreddits whilst mentioning community when appropriate
 - **Bluesky/Twitter**: Share community content and values-aligned information with appropriate hashtags
 - **LinkedIn**: Professional content that demonstrates community values in professional contexts
 - **GitHub**: Technical contributions and documentation that showcase community technical work
@@ -117,7 +117,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 - **Accessibility Support**: Help ensure events are accessible to diverse participants
 - **Follow-Up Engagement**: Connect with new participants after events to support integration
 
-**Event Hosting and Organization:**
+**Event Hosting and Organisation:**
 - **Values Integration**: Ensure all events reflect and support community values
 - **Accessibility Planning**: Plan events that are accessible to people with diverse needs
 - **Inclusive Environment**: Create environments where diverse participants feel welcome
@@ -130,7 +130,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 - **Conference Participation**: Represent the community at relevant conferences and gatherings
 - **Workshop Facilitation**: Offer workshops that showcase community values and approach
 - **Panel Participation**: Participate in panels that advance community values and visibility
-- **Networking Events**: Network authentically while representing community values
+- **Networking Events**: Network authentically whilst representing community values
 - **Educational Presentations**: Present about community work and impact
 
 **Best Practices for External Representation:**
@@ -140,7 +140,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 - **Follow-Up Systems**: Have systems in place to follow up with interested individuals
 - **Community Coordination**: Coordinate with community leadership about external representation
 
-## 3. ORGANIZATIONAL GROWTH STRATEGIES
+## 3. ORGANISATIONAL GROWTH STRATEGIES
 
 ### 3.1. Partnership Development
 
@@ -182,7 +182,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 
 **Priority Communities:**
 - **Marginalised Identities**: Prioritise outreach to communities that are underrepresented in tech and social justice spaces
-- **Geographic Diversity**: Seek geographic diversity while respecting cultural differences
+- **Geographic Diversity**: Seek geographic diversity whilst respecting cultural differences
 - **Economic Accessibility**: Ensure growth includes people from diverse economic backgrounds
 - **Accessibility Needs**: Actively recruit people with disabilities and diverse accessibility needs
 - **Age Diversity**: Welcome participation across age groups and generational perspectives
@@ -198,7 +198,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 
 **Skill and Interest Alignment:**
 - **Technical Communities**: Outreach to technical communities interested in ethical technology
-- **Social Justice Organizations**: Connection with organisations working on related social justice issues
+- **Social Justice Organisations**: Connection with organisations working on related social justice issues
 - **Gaming Communities**: Authentic participation in gaming communities with shared values
 - **Educational Institutions**: Outreach to educational communities interested in community building
 - **Professional Networks**: Engagement with professional networks focused on ethical practices
@@ -261,7 +261,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 - **Accommodation Assessment**: Assessment of accessibility needs and accommodation provision
 - **Multiple Participation Options**: Information about different ways to participate based on capacity and interest
 - **Communication Preferences**: Respect for different communication styles and preferences
-- **Flexible Engagement**: Recognition that engagement levels and styles vary among community members
+- **Flexible Engagement**: Recognition that engagement levels and styles vary amongst community members
 - **Support Systems**: Connection to appropriate support systems and resources
 
 #### 4.1.2. Community Culture Integration
@@ -296,12 +296,12 @@ This Community Growth Policy establishes ethical guidelines for how community me
 - **Capacity Recognition**: Recognition that participation capacity varies and changes over time
 - **Rest and Recovery**: Normalization of breaks and reduced engagement periods
 - **Sustainable Volunteerism**: Sustainable approaches to volunteer engagement and responsibility
-- **Well-Being Priority**: Prioritization of member well-being over community productivity
+- **Well-Being Priority**: Prioritisation of member well-being over community productivity
 
 #### 4.2.2. Community Evolution and Adaptation
 
 **Growth-Responsive Community Development:**
-- **Culture Preservation**: Maintaining community culture and values while accommodating growth
+- **Culture Preservation**: Maintaining community culture and values whilst accommodating growth
 - **Structure Adaptation**: Adapting community structures to serve larger and more diverse membership
 - **Democracy Protection**: Ensuring growth doesn't undermine democratic participation and decision-making
 - **Quality Maintenance**: Maintaining community quality and values during periods of rapid growth
@@ -332,12 +332,12 @@ This Community Growth Policy establishes ethical guidelines for how community me
 - **Social Impact**: Measurement of social impact and community benefit
 - **Economic Sustainability**: Sustainable economic approaches to community operations
 - **Cultural Sustainability**: Preservation of community culture and values during growth
-- **Member Well-Being**: Prioritization of member well-being in growth planning
+- **Member Well-Being**: Prioritisation of member well-being in growth planning
 
 #### 5.1.2. Growth Rate Management
 
 **Sustainable Growth Pacing:**
-- **Organic Growth Priority**: Prioritization of organic growth over rapid expansion
+- **Organic Growth Priority**: Prioritisation of organic growth over rapid expansion
 - **Integration Capacity**: Growth that matches community capacity to integrate new members effectively
 - **Quality Maintenance**: Growth pacing that maintains community quality and member experience
 - **Resource Alignment**: Growth that aligns with available resources and support capacity
@@ -436,7 +436,7 @@ This Community Growth Policy establishes ethical guidelines for how community me
 **Long-Term Vision Development:**
 - **Community Vision**: Development of long-term vision for community growth and impact
 - **Strategic Planning**: Strategic planning for sustainable community development
-- **Impact Goals**: Setting and working toward long-term social impact goals
+- **Impact Goals**: Setting and working towards long-term social impact goals
 - **Innovation Integration**: Planning for integration of emerging technologies and approaches
 - **Movement Contribution**: Planning for community contribution to broader social justice movements
 
diff --git a/src/content/docs/legal/community-support-policy.md b/src/content/docs/legal/community-support-policy.md
index db98f6f..dbaaba2 100644
--- a/src/content/docs/legal/community-support-policy.md
+++ b/src/content/docs/legal/community-support-policy.md
@@ -8,7 +8,7 @@ title: Community Support Policy
 
 ### 1.1. Policy Statement
 
-This Community Support Policy establishes the framework for how community members can both seek and provide support within our community ecosystem. This policy is designed to create a safe, inclusive, and mutually supportive environment that honours our values of social justice, accessibility, and community empowerment while maintaining appropriate boundaries and safety standards.
+This Community Support Policy establishes the framework for how community members can both seek and provide support within our community ecosystem. This policy is designed to create a safe, inclusive, and mutually supportive environment that honours our values of social justice, accessibility, and community empowerment whilst maintaining appropriate boundaries and safety standards.
 
 ### 1.2. Integration with Community Values
 
@@ -66,7 +66,7 @@ This policy applies to all forms of support exchange within our community platfo
 - Accessibility assistance and accommodation support
 - Platform-specific guidance and orientation
 
-#### 2.1.2. Specialized Support Areas
+#### 2.1.2. Specialised Support Areas
 
 **Identity-Based Support:**
 - Support groups for specific identities and experiences
@@ -103,7 +103,7 @@ This policy applies to all forms of support exchange within our community platfo
 **Platform-Specific Guidelines:**
 - **Discord**: Use designated support channels (#general-support, #tech-help) or reach out to trusted community members
 - **Discord Forums**: Create posts in appropriate forum channels with clear, descriptive titles
-- **Reddit**: Utilize community-specific support threads and appropriate flair
+- **Reddit**: Utilise community-specific support threads and appropriate flair
 - **GitHub**: Use issue templates for bug reports, feature requests, and technical support
 - **Social Media**: Engage appropriately with community hashtags and threads
 
@@ -158,7 +158,7 @@ This policy applies to all forms of support exchange within our community platfo
 - **Communicate Clearly**: Share what you need and what would be helpful
 - **Be Open to Different Perspectives**: Community members bring diverse experiences and viewpoints
 - **Respect Advice Boundaries**: Understand the difference between peer support and professional advice
-- **Engage Authentically**: Be genuine while maintaining appropriate privacy boundaries
+- **Engage Authentically**: Be genuine whilst maintaining appropriate privacy boundaries
 - **Follow Through**: Let supporters know how their assistance worked out when appropriate
 
 **Privacy and Safety:**
@@ -307,7 +307,7 @@ This policy applies to all forms of support exchange within our community platfo
 
 ### 4.1. Discord Support Protocols
 
-#### 4.1.1. Channel Organization and Usage
+#### 4.1.1. Channel Organisation and Usage
 
 **Designated Support Channels:**
 - **#support**: General questions and peer support requests
@@ -319,7 +319,7 @@ This policy applies to all forms of support exchange within our community platfo
 - **Respect Consent**: Always ask before moving support to direct messages
 - **Maintain Documentation**: Keep records of concerning interactions for staff review
 - **Escalation Protocols**: Know when and how to involve Discord moderators and staff
-- **Privacy Protection**: Respect confidentiality while ensuring safety
+- **Privacy Protection**: Respect confidentiality whilst ensuring safety
 
 #### 4.1.2. Discord-Specific Safety Measures
 
@@ -335,7 +335,7 @@ This policy applies to all forms of support exchange within our community platfo
 
 **Post Guidelines:**
 - **Descriptive Titles**: Clear titles that indicate the type of support needed
-- **Appropriate Categorization**: Use correct flairs and categories for support requests
+- **Appropriate Categorisation**: Use correct flairs and categories for support requests
 - **Privacy Considerations**: Share only what you're comfortable being public
 - **Follow-Up Responsibility**: Update threads when situations resolve or change
 
@@ -462,7 +462,7 @@ This policy applies to all forms of support exchange within our community platfo
 - **Resource Databases**: Comprehensive databases of professional services
 - **Referral Processes**: Clear processes for connecting people to professional help
 - **Ongoing Coordination**: Coordination between community support and professional services
-- **Privacy Compliance**: Respect for privacy while ensuring safety
+- **Privacy Compliance**: Respect for privacy whilst ensuring safety
 - **Follow-Up Support**: Continued community support alongside professional services
 
 #### 5.2.2. Legal and Ethical Obligations
@@ -499,7 +499,7 @@ This policy applies to all forms of support exchange within our community platfo
 
 **Feedback and Evaluation:**
 - **Community Feedback**: Regular feedback collection from support recipients
-- **Peer Evaluation**: Peer feedback among support providers
+- **Peer Evaluation**: Peer feedback amongst support providers
 - **Staff Review**: Regular staff review of support quality and safety
 - **Continuous Improvement**: Ongoing improvement of support practices and resources
 - **Training Updates**: Regular updates to support training and resources
@@ -545,7 +545,7 @@ This policy applies to all forms of support exchange within our community platfo
 
 **Partnership and Collaboration:**
 - **Professional Service Partnerships**: Appropriate partnerships with professional service providers
-- **Community Organization Collaboration**: Collaboration with other community organisations
+- **Community Organisation Collaboration**: Collaboration with other community organisations
 - **Resource Sharing Networks**: Participation in resource sharing networks
 - **Best Practice Communities**: Participation in communities focused on peer support best practices
 - **Research Participation**: Appropriate participation in research on effective community support
diff --git a/src/content/docs/legal/content-moderation.md b/src/content/docs/legal/content-moderation.md
index d715cac..a305e83 100644
--- a/src/content/docs/legal/content-moderation.md
+++ b/src/content/docs/legal/content-moderation.md
@@ -32,23 +32,7 @@ This Policy applies to all content and user interactions across:
 
 ### 1.3. Integration with Other Policies
 
-This Policy operates in conjunction with our comprehensive policy framework:
-
-**(a)** Our Terms of Service, which establish the fundamental legal relationship;
-
-**(b)** Our Community Code of Conduct, which establishes behavioural expectations;
-
-**(c)** Our Acceptable Use Policy, which defines prohibited activities and usage patterns;
-
-**(d)** Our Privacy Policy, which governs data collection and processing in moderation activities;
-
-**(e)** Our Limitation of Liability and Indemnification Policy, which governs all liability and risk allocation matters;
-
-**(f)** Our Service Level Agreement and Warranty Disclaimer, which define service expectations;
-
-**(g)** Our Export Control and Sanctions Compliance Policy, which governs international compliance;
-
-**(h)** Our API Terms and Conditions, which govern developer services;
+This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Acceptable Use Policy, Limitation of Liability and Indemnification Policy, Service Level Agreement, Export Control and Sanctions Compliance Policy, API Terms and Conditions, and all applicable legal protections by reference.
 
 **(i)** Our Appeals Policy, which provides procedures for challenging moderation decisions;
 
@@ -928,7 +912,7 @@ For questions about our content policies:
 
 **Subject Line:** Content Policy Inquiry - [Brief Description]
 
-**Response Time:** Within 3 business days for policy clarification requests
+**Response Time:** Within 7-10 business days for policy clarification requests
 
 ### 12.2. Content Reporting
 
@@ -940,7 +924,7 @@ To report problematic content:
 
 **Emergency Reports:** For urgent safety concerns, use subject line "URGENT - Content Report"
 
-**Response Time:** Within 24 hours for urgent reports, 48 hours for standard reports
+**Response Time:** Within 7-10 business days for all reports
 
 ### 12.3. Moderation Appeals
 
@@ -952,7 +936,7 @@ For appeals of moderation decisions:
 
 **Process:** Follow detailed appeals process outlined in our Community Appeals Policy
 
-**Response Time:** Within 5 business days for appeal reviews
+**Response Time:** Within 7-10 business days for appeal reviews
 
 ### 12.4. Community Support
 
@@ -962,7 +946,7 @@ For general community support and guidance:
 
 **Discord Community:** https://chat.nhcarrigan.com
 
-**Response Time:** Within 48 hours for community support requests
+**Response Time:** Within 7-10 business days for community support requests
 
 **Live Chat:** Available during business hours for immediate assistance
 
diff --git a/src/content/docs/legal/crisis-mental-health.md b/src/content/docs/legal/crisis-mental-health.md
index ed055dc..154e383 100644
--- a/src/content/docs/legal/crisis-mental-health.md
+++ b/src/content/docs/legal/crisis-mental-health.md
@@ -28,7 +28,7 @@ This Crisis and Mental Health Management Policy ("Policy") establishes comprehen
 
 This Policy applies to:
 
-**(a)** All staff members, volunteers, and community moderators;
+**(a)** All Team members (volunteers), Staff (paid employees), and community moderators;
 
 **(b)** All platforms, services, and communication channels we operate;
 
@@ -42,13 +42,7 @@ This Policy applies to:
 
 ### 1.4. Integration with Other Policies
 
-This Policy operates in conjunction with:
-
-**(a)** Our Content and Moderation Policy, which governs harmful content including self-harm materials;
-
-**(b)** Our Privacy Policy, which governs confidentiality and information sharing;
-
-**(c)** Our Terms of Service, which establish fundamental service limitations;
+This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Content and Moderation Policy, and all applicable legal protections by reference.
 
 **(d)** Our Limitation of Liability Policy, which governs risk allocation;
 
diff --git a/src/content/docs/legal/export-control.md b/src/content/docs/legal/export-control.md
index 3c96d91..67d3d55 100644
--- a/src/content/docs/legal/export-control.md
+++ b/src/content/docs/legal/export-control.md
@@ -818,7 +818,7 @@ For export control and sanctions compliance matters:
 
 **Subject Line:** Export Control Compliance - [Brief Description]
 
-**Response Time:** Within 24 hours for compliance inquiries
+**Response Time:** Within 7-10 business days for compliance inquiries
 
 **Emergency Contact:** Available for urgent compliance matters
 
@@ -830,7 +830,7 @@ For license applications and government relations:
 
 **Subject Line:** Export License Matter - [License Type]
 
-**Response Time:** Within 2 business days for licensing matters
+**Response Time:** Within 7-10 business days for licensing matters
 
 **Government Relations:** Dedicated team for government agency coordination
 
@@ -856,7 +856,7 @@ For export control and sanctions training:
 
 **Training Portal:** Access to online training modules and resources
 
-**Response Time:** Within 3 business days for training requests
+**Response Time:** Within 7-10 business days for training requests
 
 ---
 
diff --git a/src/content/docs/legal/government.md b/src/content/docs/legal/government.md
index 98b7247..d5f9323 100644
--- a/src/content/docs/legal/government.md
+++ b/src/content/docs/legal/government.md
@@ -326,7 +326,7 @@ For media inquiries regarding government actions:
 
 **Email:** press@nhcarrigan.com
 
-**Response Time:** Within 24 hours for urgent matters
+**Response Time:** Within 7-10 business days for all matters
 
 ### 8.4. User Support
 
@@ -336,7 +336,7 @@ For users concerned about government access to their data:
 
 **Discord Community:** https://chat.nhcarrigan.com
 
-**Response Time:** Within 48 hours for privacy-related inquiries
+**Response Time:** Within 7-10 business days for privacy-related inquiries
 
 ## 9. FUTURE DEVELOPMENTS
 
diff --git a/src/content/docs/legal/liability.md b/src/content/docs/legal/liability.md
index b6ab48b..40ae871 100644
--- a/src/content/docs/legal/liability.md
+++ b/src/content/docs/legal/liability.md
@@ -12,19 +12,7 @@ This Limitation of Liability and Indemnification Policy ("Policy") establishes c
 
 ### 1.2. Integration with Other Legal Documents
 
-This Policy operates in conjunction with and supplements:
-
-**(a)** Our Terms of Service, which establish the fundamental user relationship;
-
-**(b)** Our Service Level Agreement, which defines service expectations and remedies;
-
-**(c)** Our Acceptable Use Policy, which defines prohibited activities;
-
-**(d)** Our Privacy Policy, which governs data collection and processing;
-
-**(e)** Our API Terms and Conditions, which govern developer services;
-
-**(f)** Any additional service-specific terms or agreements.
+This Policy operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Acceptable Use Policy, Service Level Agreement, API Terms and Conditions, and all applicable legal protections by reference.
 
 Where conflicts exist between documents, the most restrictive liability limitation shall apply to ensure maximum protection for the Company.
 
@@ -698,7 +686,7 @@ For questions about liability limitations and legal matters:
 
 **Subject Line:** Liability and Legal Inquiry - [Brief Description]
 
-**Response Time:** Within 5 business days for legal inquiries
+**Response Time:** Within 7-10 business days for legal inquiries
 
 **Legal Counsel:** All complex legal matters are reviewed by qualified legal counsel
 
@@ -712,7 +700,7 @@ For claims potentially subject to liability limitations:
 
 **Notice Requirement:** Formal notice required for all claims seeking damages
 
-**Response Time:** Within 10 business days for claim acknowledgement
+**Response Time:** Within 7-10 business days for claim acknowledgement
 
 ### 10.3. Insurance and Risk Management
 
@@ -724,7 +712,7 @@ For insurance and risk management coordination:
 
 **Coverage Questions:** Questions about insurance coverage and risk transfer
 
-**Response Time:** Within 7 business days for insurance-related inquiries
+**Response Time:** Within 7-10 business days for insurance-related inquiries
 
 ### 10.4. Emergency Legal Matters
 
@@ -736,7 +724,7 @@ For urgent legal matters requiring immediate attention:
 
 **Phone:** Emergency contact information available to qualified legal representatives
 
-**Response Time:** Within 24 hours for emergency legal matters
+**Response Time:** Within 7-10 business days for all legal matters
 
 ---
 
diff --git a/src/content/docs/legal/privacy.md b/src/content/docs/legal/privacy.md
index b0d4086..34161d5 100644
--- a/src/content/docs/legal/privacy.md
+++ b/src/content/docs/legal/privacy.md
@@ -202,13 +202,7 @@ To exercise any of these rights:
 
 ### 5.3. Response Timeframes
 
-We endeavour to respond to all privacy requests within:
-
-**(a)** **Simple requests:** Five (5) business days;
-
-**(b)** **Complex requests:** Thirty (30) days, with notification if additional time is required;
-
-**(c)** **Urgent security matters:** Within twenty-four (24) hours where possible.
+We endeavour to respond to all privacy requests within 7-10 business days. For complex requests that require additional time, we will notify you and respond within thirty (30) days as required by applicable data protection laws (including GDPR).
 
 ### 5.4. Limitations on Rights
 
diff --git a/src/content/docs/legal/security.md b/src/content/docs/legal/security.md
index d6c8953..5042fc4 100644
--- a/src/content/docs/legal/security.md
+++ b/src/content/docs/legal/security.md
@@ -466,7 +466,7 @@ For all security-related matters, including vulnerability reports, questions abo
 
 **Email:** security@nhcarrigan.com
 
-**Response Time:** We aim to respond to all security inquiries within 24 hours during business days
+**Response Time:** We aim to respond to all security inquiries within 7-10 business days
 
 **Emergency Contact:** For critical security issues requiring immediate attention, mark your email with [URGENT] in the subject line
 
@@ -484,11 +484,11 @@ If you are unable to use our primary email contact:
 
 We commit to maintaining the following response standards:
 
-**(a)** **Initial Acknowledgement:** All security reports acknowledged within 24-72 hours;
+**(a)** **Initial Acknowledgement:** All security reports acknowledged within 7-10 business days;
 
 **(b)** **Status Updates:** Regular progress updates provided at least weekly for active investigations;
 
-**(c)** **Technical Clarification:** Response to technical questions within 2-3 business days;
+**(c)** **Technical Clarification:** Response to technical questions within 7-10 business days;
 
 **(d)** **Escalation Path:** Clear escalation procedures for urgent matters or communication issues.
 
diff --git a/src/content/docs/legal/sla.md b/src/content/docs/legal/sla.md
index 67e392a..7a6eca0 100644
--- a/src/content/docs/legal/sla.md
+++ b/src/content/docs/legal/sla.md
@@ -12,15 +12,7 @@ This Service Level Agreement and Warranty Disclaimer ("SLA") establishes the ter
 
 ### 1.2. Integration with Other Policies
 
-This SLA supplements and operates in conjunction with:
-
-**(a)** Our Terms of Service, which govern the general terms of service usage;
-
-**(b)** Our Privacy Policy, which governs data collection and processing;
-
-**(c)** Our Acceptable Use Policy, which defines permissible usage patterns;
-
-**(d)** All other applicable policies and agreements.
+This SLA operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Acceptable Use Policy, and all applicable legal protections by reference.
 
 ### 1.3. Scope of Services Covered
 
@@ -250,7 +242,7 @@ To request Service Level remedies:
 
 **(c)** **Verification**: Allow reasonable time for our team to verify the claim against monitoring data;
 
-**(d)** **Resolution**: We will respond within 10 business days with our determination and any applicable remedies.
+**(d)** **Resolution**: We will respond within 7-10 business days with our determination and any applicable remedies.
 
 ## 7. FORCE MAJEURE AND EXTERNAL FACTORS
 
@@ -460,7 +452,7 @@ For questions about this SLA or service level issues:
 
 **Subject Line:** SLA Inquiry - [Brief Description]
 
-**Response Time:** Within 2 business days for SLA-related inquiries
+**Response Time:** Within 7-10 business days for SLA-related inquiries
 
 ### 14.2. Service Level Remedy Requests
 
@@ -470,7 +462,7 @@ For Service Level remedy requests:
 
 **Subject Line:** SLA Remedy Request - [Service Name]
 
-**Response Time:** Within 10 business days for remedy determinations
+**Response Time:** Within 7-10 business days for remedy determinations
 
 ### 14.3. Technical Support
 
@@ -480,7 +472,7 @@ For general technical support:
 
 **Discord Community:** https://chat.nhcarrigan.com
 
-**Response Time:** Within 48 hours for technical support requests
+**Response Time:** Within 7-10 business days for technical support requests
 
 ### 14.4. Legal and Compliance Matters
 
@@ -490,7 +482,7 @@ For legal matters related to this SLA:
 
 **Subject Line:** Legal Matter - SLA
 
-**Response Time:** Within 5 business days for legal inquiries
+**Response Time:** Within 7-10 business days for legal inquiries
 
 ---
 
diff --git a/src/content/docs/legal/subprocessors.md b/src/content/docs/legal/subprocessors.md
index f5c5705..666eb3a 100644
--- a/src/content/docs/legal/subprocessors.md
+++ b/src/content/docs/legal/subprocessors.md
@@ -432,7 +432,7 @@ For questions about subprocessor data processing:
 
 **Subject Line:** Subprocessor Data Processing Inquiry
 
-**Response Time:** Within 5 business days for standard inquiries
+**Response Time:** Within 7-10 business days for standard inquiries
 
 ### 8.2. Rights Requests
 
@@ -462,7 +462,7 @@ For technical issues related to third-party platform integrations:
 
 **Discord Community:** https://chat.nhcarrigan.com
 
-**Response Time:** Within 48 hours for technical support requests
+**Response Time:** Within 7-10 business days for technical support requests
 
 ## 9. COMPLIANCE AND REGULATORY INFORMATION
 
diff --git a/src/content/docs/legal/terms.md b/src/content/docs/legal/terms.md
index e0597e2..2abc4ba 100644
--- a/src/content/docs/legal/terms.md
+++ b/src/content/docs/legal/terms.md
@@ -392,7 +392,7 @@ All legal notices and formal communications should be sent to:
 
 ### 16.3. Business Hours
 
-We endeavour to respond to all inquiries within forty-eight (48) hours during normal business hours (Monday through Friday, 9:00 AM to 5:00 PM Pacific Standard Time).
+We endeavour to respond to all inquiries within 7-10 business days during normal business hours (Monday through Friday, 9:00 AM to 5:00 PM Pacific Standard Time).
 
 ---
 
diff --git a/src/content/docs/mentorship/00-faq.md b/src/content/docs/mentorship/00-faq.md
index ec7389f..3465e72 100644
--- a/src/content/docs/mentorship/00-faq.md
+++ b/src/content/docs/mentorship/00-faq.md
@@ -8,7 +8,7 @@ title: 00. Frequently Asked Questions
 
 ### 1.1. Policy Overview
 
-This Frequently Asked Questions Documentation (hereinafter referred to as "the FAQ") provides answers to common questions regarding our Mentorship Programme. This FAQ operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Frequently Asked Questions Documentation (hereinafter referred to as "the FAQ") provides answers to common questions regarding our Mentorship Programme. This FAQ operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Purpose and Scope
 
@@ -32,7 +32,7 @@ This FAQ addresses common questions and concerns regarding programme participati
 **Voluntary Donations:**
 - We welcome voluntary donations to support programme operations
 - Donations are entirely optional and do not affect programme participation or outcomes
-- Information about donation options is available at: [https://donate.nhcarrigan.com/](https://donate.nhcarrigan.com/)
+- For comprehensive information about donation options and policies, please refer to our [Donation and Support Policy](/about/donate)
 
 ## 3. PROGRAMME STRUCTURE AND SUPPORT
 
@@ -51,6 +51,7 @@ This FAQ addresses common questions and concerns regarding programme participati
 - Participants follow documentation and use provided resources independently
 - Reviews and approvals are optional and available upon request
 - Support is provided when participants ask for help, not through mandatory checkpoints
+- **IMPORTANT: To get the most value from the programme experience, participants should actively ask mentors questions as much as possible. Mentors are available to help, but they rely on participants to initiate contact and ask for assistance when needed.**
 - Community and peer support is encouraged throughout the programme
 
 ### 3.2. Response Time Expectations
@@ -67,8 +68,8 @@ This FAQ addresses common questions and concerns regarding programme participati
 **Response Time Guidelines:**
 - Most programme activities can be completed independently using provided documentation
 - If you have questions, feel free to ask in the #mentee-chat channel
-- If you have not received a response within three (3) business days, you may send a gentle reminder
-- Repeated communications at intervals of less than three (3) days may result in disciplinary action
+- If you have not received a response within 10 business days, you may send a gentle reminder
+- Repeated communications at intervals of less than 10 business days may result in disciplinary action
 - We appreciate your patience and understanding regarding response timelines
 
 ## 4. PROGRAMME WITHDRAWAL AND DISCONTINUATION
diff --git a/src/content/docs/mentorship/01-onboarding.md b/src/content/docs/mentorship/01-onboarding.md
index 2958cbc..11d022d 100644
--- a/src/content/docs/mentorship/01-onboarding.md
+++ b/src/content/docs/mentorship/01-onboarding.md
@@ -8,13 +8,13 @@ title: 01. Onboarding
 
 ### 1.1. Policy Overview
 
-This Onboarding Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for participants accepted into our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Onboarding Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for participants accepted into our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all individuals who have been accepted into our Mentorship Programme. All participants must complete the onboarding procedures set forth in this Documentation to gain full programme access.
 
-**IMPORTANT: This is a self-guided programme. Once you complete onboarding, you can work through the programme documentation at your own pace. Reviews and approvals are optional and available upon request.**
+**IMPORTANT: This is a self-guided programme. Once you complete onboarding, you can work through the programme documentation at your own pace. Reviews and approvals are optional and available upon request. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. APPLICATION ACCEPTANCE AND CONFIRMATION
 
diff --git a/src/content/docs/mentorship/02-goal-setting.md b/src/content/docs/mentorship/02-goal-setting.md
index 3acfeac..9bf282e 100644
--- a/src/content/docs/mentorship/02-goal-setting.md
+++ b/src/content/docs/mentorship/02-goal-setting.md
@@ -8,13 +8,13 @@ title: 02. Goal Setting
 
 ### 1.1. Policy Overview
 
-This Goal-Setting Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for goal-setting activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Goal-Setting Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for goal-setting activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme following completion of onboarding procedures. All participants should complete the goal-setting process set forth in this Documentation to proceed with programme activities.
 
-**IMPORTANT: This is a self-guided process. You will create your own roadmap using provided templates and examples. No approval is required to proceed.**
+**IMPORTANT: This is a self-guided process. You will create your own roadmap using provided templates and examples. No approval is required to proceed. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. GOAL-SETTING INITIATION
 
diff --git a/src/content/docs/mentorship/03-project-plan.md b/src/content/docs/mentorship/03-project-plan.md
index fad7bb9..0b511c9 100644
--- a/src/content/docs/mentorship/03-project-plan.md
+++ b/src/content/docs/mentorship/03-project-plan.md
@@ -8,13 +8,13 @@ title: 03. Project Planning
 
 ### 1.1. Policy Overview
 
-This Project Planning Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for flagship project planning within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Project Planning Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for flagship project planning within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme following completion of goal-setting procedures. All participants should complete the project planning process set forth in this Documentation to proceed with flagship project development.
 
-**IMPORTANT: This is a self-guided process. You will create your own project plan using provided examples and templates. No approval is required to proceed.**
+**IMPORTANT: This is a self-guided process. You will create your own project plan using provided examples and templates. No approval is required to proceed. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. PROJECT PLANNING INITIATION
 
diff --git a/src/content/docs/mentorship/04-user-stories.md b/src/content/docs/mentorship/04-user-stories.md
index bdd7b7f..bafa37a 100644
--- a/src/content/docs/mentorship/04-user-stories.md
+++ b/src/content/docs/mentorship/04-user-stories.md
@@ -8,13 +8,13 @@ title: 04. User Stories
 
 ### 1.1. Policy Overview
 
-This User Stories Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for user story development within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This User Stories Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for user story development within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme following completion of project planning procedures. All participants should complete the user story development process set forth in this Documentation to proceed with technical breakdown and development stages.
 
-**IMPORTANT: This is a self-guided process. You will create user stories independently using provided templates and examples. No review or approval is required to proceed.**
+**IMPORTANT: This is a self-guided process. You will create user stories independently using provided templates and examples. No review or approval is required to proceed. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. USER STORY DEVELOPMENT REQUIREMENTS
 
diff --git a/src/content/docs/mentorship/05-technical-breakdown.md b/src/content/docs/mentorship/05-technical-breakdown.md
index 654961c..eb4e625 100644
--- a/src/content/docs/mentorship/05-technical-breakdown.md
+++ b/src/content/docs/mentorship/05-technical-breakdown.md
@@ -8,13 +8,13 @@ title: 05. Technical Breakdown
 
 ### 1.1. Policy Overview
 
-This Technical Breakdown Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for technical breakdown activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Technical Breakdown Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for technical breakdown activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme following completion of user story development procedures. All participants should complete the technical breakdown process set forth in this Documentation to proceed with development work.
 
-**IMPORTANT: This is a self-guided process. You will fill out technical breakdown templates independently for each user story. No review or approval is required to proceed.**
+**IMPORTANT: This is a self-guided process. You will fill out technical breakdown templates independently for each user story. No review or approval is required to proceed. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. TECHNICAL BREAKDOWN INITIATION
 
diff --git a/src/content/docs/mentorship/06-priority-and-effort.md b/src/content/docs/mentorship/06-priority-and-effort.md
index 93cc61a..c4a5a74 100644
--- a/src/content/docs/mentorship/06-priority-and-effort.md
+++ b/src/content/docs/mentorship/06-priority-and-effort.md
@@ -8,13 +8,13 @@ title: 06. Priority and Effort
 
 ### 1.1. Policy Overview
 
-This Priority and Effort Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for priority and effort assignment within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Priority and Effort Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for priority and effort assignment within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme following completion of technical breakdown procedures. All participants should complete the priority and effort assignment process set forth in this Documentation to proceed with development work.
 
-**IMPORTANT: This is a self-guided process. You will assign priority and effort labels independently. No review or approval is required to proceed.**
+**IMPORTANT: This is a self-guided process. You will assign priority and effort labels independently. No review or approval is required to proceed. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. LABEL CREATION AND ASSIGNMENT
 
diff --git a/src/content/docs/mentorship/07-writing-code.md b/src/content/docs/mentorship/07-writing-code.md
index 458182c..b9f20ed 100644
--- a/src/content/docs/mentorship/07-writing-code.md
+++ b/src/content/docs/mentorship/07-writing-code.md
@@ -8,7 +8,7 @@ title: 07. Writing Code
 
 ### 1.1. Policy Overview
 
-This Writing Code Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for code development activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, Contributor Covenant, and all applicable legal protections by reference.
+This Writing Code Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for code development activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, Contributor Covenant, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
diff --git a/src/content/docs/mentorship/08-final-polish.md b/src/content/docs/mentorship/08-final-polish.md
index a98d908..7c8a475 100644
--- a/src/content/docs/mentorship/08-final-polish.md
+++ b/src/content/docs/mentorship/08-final-polish.md
@@ -8,13 +8,13 @@ title: 08. Final Polish
 
 ### 1.1. Policy Overview
 
-This Final Polish Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for final project polish, documentation, and deployment within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Final Polish Documentation (hereinafter referred to as "the Documentation") establishes mandatory procedures and requirements for final project polish, documentation, and deployment within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme whose flagship projects have reached a state suitable for resume presentation. All participants should complete the final polish procedures set forth in this Documentation before project completion.
 
-**IMPORTANT: This is a self-guided process. You will use provided checklists and templates to polish your project independently. Reviews and approvals are optional and available upon request.**
+**IMPORTANT: This is a self-guided process. You will use provided checklists and templates to polish your project independently. Reviews and approvals are optional and available upon request. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. FINAL POLISH INITIATION
 
@@ -46,10 +46,10 @@ When you believe your flagship project has reached a state where it can be proud
 - Code quality and maintainability
 - Best practices and industry standards
 - Security considerations
-- Performance optimization
+- Performance optimisation
 - Error handling
 - Test coverage
-- Code organization and structure
+- Code organisation and structure
 
 ### 3.2. Issue Resolution
 
diff --git a/src/content/docs/mentorship/09-career-prep.md b/src/content/docs/mentorship/09-career-prep.md
index 4349dfa..808ae42 100644
--- a/src/content/docs/mentorship/09-career-prep.md
+++ b/src/content/docs/mentorship/09-career-prep.md
@@ -8,13 +8,13 @@ title: 09. Career Prep
 
 ### 1.1. Policy Overview
 
-This Career Preparation Documentation (hereinafter referred to as "the Documentation") establishes procedures and requirements for career preparation activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Career Preparation Documentation (hereinafter referred to as "the Documentation") establishes procedures and requirements for career preparation activities within our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
 This Documentation applies to all participants in our Mentorship Programme who are ready to begin their job search. Career preparation resources and support are available as set forth in this Documentation.
 
-**IMPORTANT: This is a self-guided process. You will use provided resources, templates, and guides to prepare for your job search independently. Support is available upon request, but most activities can be completed using the resource library.**
+**IMPORTANT: This is a self-guided process. You will use provided resources, templates, and guides to prepare for your job search independently. Support is available upon request, but most activities can be completed using the resource library. For comprehensive information about the self-guided programme structure and how to get the most value from your mentorship experience, please refer to our [Mentorship Programme Terms and Conditions](/about/mentorship).**
 
 ## 2. CAREER PREPARATION RESOURCES
 
diff --git a/src/content/docs/mentorship/10-graduation.md b/src/content/docs/mentorship/10-graduation.md
index 3852159..bf5866d 100644
--- a/src/content/docs/mentorship/10-graduation.md
+++ b/src/content/docs/mentorship/10-graduation.md
@@ -8,7 +8,7 @@ title: 10. Graduation
 
 ### 1.1. Policy Overview
 
-This Graduation Documentation (hereinafter referred to as "the Documentation") establishes graduation criteria, procedures, and alumni programme information for our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
+This Graduation Documentation (hereinafter referred to as "the Documentation") establishes graduation criteria, procedures, and alumni programme information for our Mentorship Programme. This Documentation operates within our comprehensive legal and policy framework, incorporating our Terms of Service, Privacy Policy, Community Code of Conduct, Mentorship Programme Terms and Conditions, and all applicable legal protections by reference.
 
 ### 1.2. Scope and Applicability
 
diff --git a/src/content/docs/mentorship/resources/code-development.md b/src/content/docs/mentorship/resources/code-development.md
index b0627c4..c42c3be 100644
--- a/src/content/docs/mentorship/resources/code-development.md
+++ b/src/content/docs/mentorship/resources/code-development.md
@@ -24,7 +24,7 @@ See [Code Review Checklist](/mentorship/resources/code-review-checklist) for the
 ### Self-Review Questions
 
 **Code Quality:**
-- Is my code readable and well-organized?
+- Is my code readable and well-organised?
 - Are variable and function names clear?
 - Is the code properly commented?
 - Does the code follow project conventions?
@@ -38,7 +38,7 @@ See [Code Review Checklist](/mentorship/resources/code-review-checklist) for the
 **Testing:**
 - Are tests written and passing?
 - Is test coverage adequate?
-- Do tests actually test behavior?
+- Do tests actually test behaviour?
 
 **Security:**
 - Is sensitive data protected?
@@ -55,7 +55,7 @@ See [Code Review Checklist](/mentorship/resources/code-review-checklist) for the
 - Write self-documenting code
 - Add comments for complex logic
 
-**Organization:**
+**Organisation:**
 - Follow project structure conventions
 - Group related code together
 - Separate concerns appropriately
@@ -112,12 +112,12 @@ See [Code Review Checklist](/mentorship/resources/code-review-checklist) for the
 
 ### Performance
 
-**Optimization:**
-- Profile before optimizing
-- Optimize database queries
+**Optimisation:**
+- Profile before optimising
+- Optimise database queries
 - Minimize API calls
 - Use caching where appropriate
-- Optimize assets (images, CSS, JS)
+- Optimise assets (images, CSS, JS)
 
 ### Documentation
 
@@ -153,9 +153,9 @@ See [Code Review Checklist](/mentorship/resources/code-review-checklist) for the
 ### Testing Issues
 
 ❌ **No tests:** Always write tests
-❌ **Weak tests:** Test actual behavior
+❌ **Weak tests:** Test actual behaviour
 ❌ **Ignoring failing tests:** Fix them
-❌ **Testing implementation:** Test behavior
+❌ **Testing implementation:** Test behaviour
 
 ### Security Issues
 
diff --git a/src/content/docs/mentorship/resources/code-review-checklist.md b/src/content/docs/mentorship/resources/code-review-checklist.md
index 8c26d27..b220b77 100644
--- a/src/content/docs/mentorship/resources/code-review-checklist.md
+++ b/src/content/docs/mentorship/resources/code-review-checklist.md
@@ -9,7 +9,7 @@ Use this checklist to review your own code before merging pull requests or when
 ## Code Quality
 
 - [ ] Code follows project style guide and conventions
-- [ ] Code is readable and well-organized
+- [ ] Code is readable and well-organised
 - [ ] Variable and function names are clear and descriptive
 - [ ] Code is properly commented where necessary
 - [ ] No commented-out code or debugging statements left in
diff --git a/src/content/docs/mentorship/resources/final-polish-checklist.md b/src/content/docs/mentorship/resources/final-polish-checklist.md
index 523d165..1515d22 100644
--- a/src/content/docs/mentorship/resources/final-polish-checklist.md
+++ b/src/content/docs/mentorship/resources/final-polish-checklist.md
@@ -9,7 +9,7 @@ Use this checklist to ensure your flagship project is ready for professional pre
 ## Code Quality
 
 - [ ] All code follows project style guide
-- [ ] Code is clean, readable, and well-organized
+- [ ] Code is clean, readable, and well-organised
 - [ ] No commented-out code or debugging statements
 - [ ] Error handling is comprehensive
 - [ ] Code is properly commented where necessary
@@ -77,10 +77,10 @@ Use this checklist to ensure your flagship project is ready for professional pre
 ## Project Organization
 
 - [ ] Repository structure is clean and logical
-- [ ] Files are properly organized
+- [ ] Files are properly organised
 - [ ] Git history is clean and meaningful
-- [ ] Issues are properly labeled and organized
-- [ ] Project board is organized (if used)
+- [ ] Issues are properly labelled and organised
+- [ ] Project board is organised (if used)
 
 ## Professional Presentation
 
diff --git a/src/content/docs/mentorship/resources/final-polish.md b/src/content/docs/mentorship/resources/final-polish.md
index 08254ad..21a18ff 100644
--- a/src/content/docs/mentorship/resources/final-polish.md
+++ b/src/content/docs/mentorship/resources/final-polish.md
@@ -21,18 +21,18 @@ See [Final Polish Checklist](/mentorship/resources/final-polish-checklist) for t
 - Add missing comments
 - Fix code style inconsistencies
 
-### Code Organization
+### Code Organisation
 
 **Structure:**
-- Organize files logically
+- Organise files logically
 - Group related functionality
 - Separate concerns appropriately
 - Follow project conventions
 - Remove duplicate code
 
-### Performance Optimization
+### Performance Optimisation
 
-**Optimize:**
+**Optimise:**
 - Database queries
 - API calls
 - Asset loading
diff --git a/src/content/docs/mentorship/resources/project-planning.md b/src/content/docs/mentorship/resources/project-planning.md
index 3f537cb..cb693fe 100644
--- a/src/content/docs/mentorship/resources/project-planning.md
+++ b/src/content/docs/mentorship/resources/project-planning.md
@@ -9,14 +9,14 @@ title: Project Planning Resources
 ### Example: Task Management Application
 
 **Project Overview:**
-A full-stack task management application that allows users to create, organize, and track tasks with features like kanban boards, task dependencies, and project rewards.
+A full-stack task management application that allows users to create, organise, and track tasks with features like kanban boards, task dependencies, and project rewards.
 
 **Core Features:**
 1. User authentication and authorization
 2. Task creation and management
 3. Kanban board view
 4. Task dependencies
-5. Project organization
+5. Project organisation
 6. Reward system for completed projects
 7. Gamification elements (optional)
 
@@ -56,7 +56,7 @@ A full-stack task management application that allows users to create, organize,
 
 **Examples:**
 - Daily life: Meal planning, expense tracking, habit tracking
-- Tools: Code snippet manager, design asset organizer
+- Tools: Code snippet manager, design asset organiser
 - Hobbies: Music playlist creator, workout tracker, recipe manager
 - Industries: Healthcare apps, education tools, productivity software
 
@@ -66,7 +66,7 @@ A full-stack task management application that allows users to create, organize,
 "As a [user type], I need [what they need] because [why they need it]."
 
 **Example:**
-"As a developer, I need a way to organize and quickly access my code snippets because I waste time searching through notes and documentation."
+"As a developer, I need a way to organise and quickly access my code snippets because I waste time searching through notes and documentation."
 
 ### Step 3: Identify Core Features
 
diff --git a/src/content/docs/mentorship/resources/user-stories.md b/src/content/docs/mentorship/resources/user-stories.md
index d0608c7..4893390 100644
--- a/src/content/docs/mentorship/resources/user-stories.md
+++ b/src/content/docs/mentorship/resources/user-stories.md
@@ -76,7 +76,7 @@ As an authenticated user, I can create a new task so that I can track work that
 As an authenticated user, I can mark a task as complete so that I can track my progress.
 
 **Example 3:**
-As an authenticated user, I can organize tasks into projects so that I can group related work.
+As an authenticated user, I can organise tasks into projects so that I can group related work.
 
 **Example 4:**
 As an authenticated user, I can set task dependencies so that I can ensure tasks are completed in the correct order.
@@ -175,7 +175,7 @@ As an authenticated user, I can delete [resource] so that [value].
 - Edit content
 - Delete content
 - Search/filter content
-- Organize content
+- Organise content
 
 ### Social Features
 
@@ -205,5 +205,5 @@ As an authenticated user, I can delete [resource] so that [value].
 
 ---
 
-*User stories should be clear, focused, and user-centered. They guide development by keeping the focus on user value.*
+*User stories should be clear, focused, and user-centred. They guide development by keeping the focus on user value.*
 
diff --git a/src/content/docs/misc/templates.md b/src/content/docs/misc/templates.md
index af1544a..6138c8e 100644
--- a/src/content/docs/misc/templates.md
+++ b/src/content/docs/misc/templates.md
@@ -22,7 +22,9 @@ Our organisation does not provide legal advice. These templates are provided for
 
 ## 2. TEMPLATES
 
-### 2.1. DMCA Takedown Template
+### 2.1. Legal Templates
+
+#### 2.1.1. DMCA Takedown Template
 
 ```md
 To whom it may concern:
@@ -50,7 +52,9 @@ We swear, under penalty of perjury, that the information in this notification is
 If you have any questions, please feel free to reach out to us.
 ```
 
-### 2.2. LinkedIn Cold Outreach Response Template
+### 2.2. LinkedIn Templates
+
+#### 2.2.1. LinkedIn Cold Outreach Response Template
 
 ```md
 I would be more than happy to chat! You can schedule time directly on my calendar:
@@ -58,7 +62,7 @@ I would be more than happy to chat! You can schedule time directly on my calenda
 https://zcal.co/nhcarrigan/meet
 ```
 
-### 2.3. LinkedIn Post-Event Recommendation Template
+#### 2.2.2. LinkedIn Post-Event Recommendation Template
 
 ```md
 I had the absolute pleasure of working with [Participant's Name] during our [event name], where [they] consistently impressed me with [their] dedication, technical growth, and collaborative spirit.
@@ -72,101 +76,622 @@ By the end of the [event name], [Participant's Name] had delivered an outstandin
 I wholeheartedly recommend [Participant's Name] for any opportunity in tech. [They] bring not just technical ability, but the kind of energy and curiosity that makes any team stronger.
 ```
 
-### 2.4. LinkedIn Mentorship Recommendation Template
+#### 2.2.3. LinkedIn Mentorship Recommendation Template
 
 ```md
 I had the privilege of mentoring [Mentee's Name] through my 1:1 mentorship programme, and from our very first session, it was clear that [they] approached learning with curiosity, determination, and an eagerness to grow.
 
-Over the course of the programme, [Mentee's Name] set clear goals and worked diligently toward them—building both technical skills in [specific tech stack, tools, or concepts] and the professional confidence to apply those skills in real-world scenarios. [They] embraced feedback, sought out challenges, and consistently demonstrated the resilience needed to push past obstacles.
+Over the course of the programme, [Mentee's Name] set clear goals and worked diligently towards them—building both technical skills in [specific tech stack, tools, or concepts] and the professional confidence to apply those skills in real-world scenarios. [They] embraced feedback, sought out challenges, and consistently demonstrated the resilience needed to push past obstacles.
 
 What impressed me most was [their] commitment to personal and professional growth—not just in terms of technical ability, but also in communication, collaboration, and problem-solving. By the end of the mentorship, [Mentee's Name] had successfully delivered [describe final project or achievement], showing not only technical proficiency but also the ability to think critically and adapt to new situations.
 
 I am confident that [Mentee's Name] will continue to excel in their career. They bring the kind of focus, curiosity, and dedication that make them a valuable asset to any team, and I am proud to have played a part in their journey.
 ```
 
-### 2.5. Form Submission Declined Email Template
+### 2.3. Form Response Email Templates
+
+#### 2.3.1. Appeals Form - Approval Email Template
+
+Subject Line: `Appeal Decision - [Sanction Type] Appeal Upheld`
 
 ```md
-Hello,
+Dear [Appellant's Name],
 
-Thank you for your submission to our <form> form.
+Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
 
-We appreciate your interest in working with us. However, at this time we are not able to accept your submission.
+After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal has merit and meets the grounds for appeal as established in our policy.
 
-Please note that due to the large volume of form submissions we process, we are unable to provide personalised feedback. Here are some common submission issues we see:
+**Decision**: Your appeal has been upheld. The original disciplinary sanction has been [overturned/modified/reduced] as follows: [Insert specific details about the new decision].
 
-1. Low-effort Submission: Please ensure you are taking the time to provide detailed, well-thought responses. The more effort you put in, the more likely we will be able to accept it.
-2. Invalid Discord ID: Many of our submissions require you to provide your unique Discord ID - this is a 16 to 19 digit number that uniquely identifies your Discord account. If this is incorrect, we are unable to accept a submission. If you need help finding yours, please refer to https://dis.gd/findid
-3. Concerning Responses: If your responses to any of the form questions raise red flags, we decline your submission. Remember that you want to paint yourself in the best light here.
+**Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the appeal was successful. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
 
-We encourage you to take the time to consider these common points of failure, and would welcome a resubmission from you at any time.
+As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. The decision outlined above is effective immediately.
 
-If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
+We appreciate your engagement with our appeals process and your respect for our community standards. We look forward to your continued positive participation in our community.
+
+Regards,
 ```
 
-### 2.6. Volunteer Application Rejection Template
+#### 2.3.2. Appeals Form - Rejection Email Template
+
+Subject Line: `Appeal Decision - [Sanction Type] Appeal Dismissed`
 
 ```md
-Dear [Applicant’s Name],
+Dear [Appellant's Name],
+
+Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
+
+After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal does not meet the grounds for appeal as established in our policy.
+
+**Decision**: Your appeal has been dismissed. The original disciplinary sanction remains in full effect.
+
+**Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the original decision was appropriate. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
+
+As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. No further appeals or reviews are available through our internal processes.
+
+We understand that this decision may be disappointing. Our appeals process is designed to ensure fairness and transparency, and we have given your submission careful consideration. The original sanction was imposed in accordance with our community standards and policies, which are designed to maintain a safe and welcoming environment for all members.
+
+If you have any questions about this decision, please note that our Appeals Panel's determination is final. We appreciate your understanding and respect for our community standards and processes.
+
+Regards,
+```
+
+#### 2.3.3. Commissions Form - Approval Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your commission request! We are excited to work with you on [brief description of commission].
+
+We have reviewed your request and are pleased to accept it. We will begin working on your commission and will keep you updated on our progress.
+
+**Next Steps:**
+- [Insert specific next steps, timeline, or requirements here]
+- You will receive updates via [preferred contact method]
+- Expected completion date: [date if applicable]
+
+If you have any questions or need to make changes to your request, please don't hesitate to reach out to us.
+
+We look forward to creating something amazing for you!
+
+Best regards,
+```
+
+#### 2.3.4. Commissions Form - Rejection Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your interest in commissioning work from us. We appreciate you taking the time to submit your request.
+
+After careful review, we have decided not to proceed with your commission request at this time. This decision may be based on factors such as current workload, project scope, timeline constraints, or alignment with our services.
+
+Please note that due to the volume of requests we receive, we are unable to provide detailed feedback on every declined request.
+
+We encourage you to stay engaged with our community and projects. If your needs change or you have a different project in mind, we would welcome a new request in the future.
+
+If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Best regards,
+```
+
+#### 2.3.5. Community Recognition Form - Approval Email Template
+
+```md
+Hello [Nominator's Name],
+
+Thank you for taking the time to nominate [Nominee's Name] for community recognition! We truly appreciate you highlighting the positive contributions of community members.
+
+We are pleased to inform you that your nomination has been accepted and will be considered in our next recognition cycle. The recognition process involves review by our leadership team, and selected nominees will be celebrated through our community recognition programmes.
+
+**What Happens Next:**
+- Your nomination will be reviewed by our recognition committee
+- Selected nominees will be notified and celebrated publicly
+- Recognition may include awards, spotlights, or other forms of appreciation
+- All nominations help us build a more appreciative and inclusive community
+
+Thank you for helping us celebrate the amazing contributions of our community members. Your nomination makes a difference!
+
+If you have any questions, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Warm regards,
+```
+
+#### 2.3.6. Community Recognition Form - Rejection Email Template
+
+```md
+Hello [Nominator's Name],
+
+Thank you for taking the time to submit a nomination for community recognition. We truly appreciate your effort to highlight positive contributions in our community.
+
+After careful review, we have decided not to proceed with this nomination at this time. This decision may be based on factors such as eligibility criteria, timing, or alignment with our recognition programmes.
+
+Please note that due to the volume of nominations we receive, we are unable to provide detailed feedback on every declined nomination.
+
+We encourage you to continue recognising positive contributions in our community. There are many ways to show appreciation, including direct recognition, peer appreciation, and future nominations.
+
+If you have any questions about our recognition programmes, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you again for your engagement with our community.
+
+Warm regards,
+```
+
+#### 2.3.7. Contact Form - Approval Email Template
+
+```md
+Hello [Contact's Name],
+
+Thank you for reaching out to us through our contact form. We have received your message regarding [brief topic summary].
+
+We appreciate you taking the time to contact us and are pleased to confirm that we have received your inquiry. [Insert specific response or next steps here, such as:]
+
+- We will review your request and respond within [timeframe]
+- A team member will be in touch shortly
+- We have scheduled a follow-up [meeting/call/response] for [date/time]
+
+If you have any urgent questions or need immediate assistance, please don't hesitate to reach out in our Discord community: https://chat.nhcarrigan.com
+
+We look forward to connecting with you!
+
+Best regards,
+```
+
+#### 2.3.8. Contact Form - Rejection Email Template
+
+```md
+Hello [Contact's Name],
+
+Thank you for reaching out to us through our contact form. We have received your message regarding [brief topic summary].
+
+After reviewing your inquiry, we are unable to assist with your request at this time. This may be due to factors such as scope of services, current capacity, or alignment with our mission and values.
+
+Please note that due to the volume of inquiries we receive, we are unable to provide detailed feedback on every declined request.
+
+If you have questions about our services or policies, we encourage you to review our documentation at https://docs.nhcarrigan.com or join our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding.
+
+Best regards,
+```
+
+#### 2.3.9. Development Review Requests Form - Approval Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your development review request! We have reviewed your submission and are pleased to accept your request for review of [project/repository name or description].
+
+**Review Details:**
+- Review Type: [Code Review/Project Review/Architecture Review/etc.]
+- Materials to be Reviewed: [list of materials]
+- Expected Timeline: [timeline for review completion]
+
+**Next Steps:**
+- Our team will begin reviewing your materials
+- You will receive detailed feedback via [communication method]
+- We will provide constructive suggestions for improvement
+
+Please note that development reviews are provided as free services to active community members, and feedback is provided in good faith based on our expertise and best practices.
+
+If you have any questions or need to provide additional materials, please don't hesitate to reach out.
+
+We look forward to reviewing your work!
+
+Best regards,
+```
+
+#### 2.3.10. Development Review Requests Form - Rejection Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your interest in receiving a development review. We appreciate you taking the time to submit your request.
+
+After careful review, we have decided not to proceed with your development review request at this time. This decision may be based on factors such as:
+- Current review capacity and workload
+- Alignment with our review services and expertise
+- Community membership and engagement requirements
+- Project scope or complexity
+
+Please note that development reviews are provided as free services exclusively to active members of our community. If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant.
+
+If you have questions about our development review services or would like to resubmit in the future, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding.
+
+Best regards,
+```
+
+#### 2.3.11. Events Form - Approval Email Template
+
+```md
+Hello [Event Organiser's Name],
+
+Thank you for your event request! We are excited about your proposed event: [Event Name].
+
+We have reviewed your submission and are pleased to approve your event request. We look forward to supporting and promoting this event within our community.
+
+**Event Details:**
+- Event Name: [Event Name]
+- Proposed Date: [Date]
+- Event Type: [Type of event]
+
+**Next Steps:**
+- [Insert specific next steps, such as scheduling, promotion, or coordination details]
+- We will work with you to finalise event details
+- Event promotion will begin [timeline]
+
+If you have any questions or need to make changes to your event details, please don't hesitate to reach out to us.
+
+Thank you for contributing to our community through this event!
+
+Best regards,
+```
+
+#### 2.3.12. Events Form - Rejection Email Template
+
+```md
+Hello [Event Organiser's Name],
+
+Thank you for your interest in organising an event with our community. We appreciate you taking the time to submit your event request: [Event Name].
+
+After careful review, we have decided not to proceed with your event request at this time. This decision may be based on factors such as:
+- Current event calendar and capacity
+- Alignment with our community values and mission
+- Resource availability and support requirements
+- Event scope or logistics
+
+Please note that due to the volume of event requests we receive, we are unable to provide detailed feedback on every declined request.
+
+We encourage you to stay engaged with our community and consider submitting future event proposals. If you have questions about our event policies or would like to discuss alternative event formats, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding and continued engagement with our community.
+
+Best regards,
+```
+
+#### 2.3.13. Mock Interview Requests Form - Approval Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your mock interview request! We have reviewed your submission and are pleased to accept your request for a [technical/behavioural/combined] mock interview.
+
+**Interview Details:**
+- Interview Type: [Type]
+- Target Role: [Role if provided]
+- Interview Format: [Format]
+
+**Next Steps:**
+- We will coordinate with you to schedule your mock interview session
+- Mock interviews are typically conducted via [video call/voice call]
+- Sessions typically last between 30-60 minutes
+- You will receive preparation materials and session details via [communication method]
+
+Please note that mock interviews are provided as free services exclusively to active members of our community. We look forward to helping you prepare for your upcoming interview!
+
+If you have any questions or need to reschedule, please don't hesitate to reach out to us.
+
+Best regards,
+```
+
+#### 2.3.14. Mock Interview Requests Form - Rejection Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your interest in receiving a mock interview. We appreciate you taking the time to submit your request.
+
+After careful review, we have decided not to proceed with your mock interview request at this time. This decision may be based on factors such as:
+- Current interview capacity and availability
+- Community membership and engagement requirements
+- Interview type or scope alignment with our services
+- Scheduling constraints
+
+**IMPORTANT**: Mock interviews are provided as free services EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement.
+
+If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant. Once you have established active community membership through regular participation and engagement, you will be eligible to request mock interview services.
+
+If you have questions about our mock interview services or community membership, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding.
+
+Best regards,
+```
+
+#### 2.3.15. Portfolio Review Requests Form - Approval Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your portfolio review request! We have reviewed your submission and are pleased to accept your request for review of your [resume/LinkedIn profile/GitHub profile/portfolio website].
+
+**Review Details:**
+- Review Type: [Resume/LinkedIn/GitHub/Portfolio Review]
+- Materials to be Reviewed: [list of materials or links]
+
+**Next Steps:**
+- Our team will begin reviewing your materials
+- You will receive detailed feedback via [communication method]
+- We will provide constructive suggestions for improvement based on industry best practices
+
+Please note that portfolio reviews are provided as free services to active community members, and feedback is provided in good faith based on our expertise and professional standards.
+
+If you have any questions or need to provide additional materials, please don't hesitate to reach out.
+
+We look forward to reviewing your materials and helping you improve your professional presentation!
+
+Best regards,
+```
+
+#### 2.3.16. Portfolio Review Requests Form - Rejection Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your interest in receiving a portfolio review. We appreciate you taking the time to submit your request.
+
+After careful review, we have decided not to proceed with your portfolio review request at this time. This decision may be based on factors such as:
+- Current review capacity and workload
+- Community membership and engagement requirements
+- Material accessibility or completeness
+- Review type alignment with our services
+
+**IMPORTANT**: Portfolio reviews are provided as free services EXCLUSIVELY to active members of our community. These services are NOT available to the general public. To be eligible, you MUST be an active, engaged member of our community with demonstrated participation and engagement.
+
+If you are not currently an active community member, we encourage you to join our Discord community at https://chat.nhcarrigan.com and become an active participant. Once you have established active community membership through regular participation and engagement, you will be eligible to request portfolio review services.
+
+If you have questions about our portfolio review services or community membership, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding.
+
+Best regards,
+```
+
+#### 2.3.17. Recommendations Form - Approval Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your recommendation request! We have reviewed your submission and are pleased to accept your request for a recommendation.
+
+**Recommendation Details:**
+- Recommendation Type: [LinkedIn Recommendation/General Recommendation/etc.]
+- Context: [Brief context if provided]
+
+**Next Steps:**
+- We will prepare your recommendation based on our relationship and your contributions
+- Recommendations are typically provided via [LinkedIn/email/etc.]
+- You will receive a copy of the recommendation once it is completed
+- Expected completion: [timeline]
+
+Please note that recommendations are provided as free services in good faith, based on our relationship and knowledge of your work. We provide honest, accurate recommendations based on our direct experience with you.
+
+If you have any questions or need to provide additional context, please don't hesitate to reach out.
+
+We are happy to support you in your professional journey!
+
+Best regards,
+```
+
+#### 2.3.18. Recommendations Form - Rejection Email Template
+
+```md
+Hello [Requester's Name],
+
+Thank you for your interest in receiving a recommendation. We appreciate you taking the time to submit your request.
+
+After careful review, we have decided not to proceed with your recommendation request at this time. This decision may be based on factors such as:
+- Insufficient direct working relationship or interaction
+- Lack of sufficient context or experience to provide an accurate recommendation
+- Timeline constraints or capacity limitations
+- Alignment with our recommendation policy and standards
+
+Please note that we can only provide recommendations when we have sufficient direct experience and relationship with the requester to provide an honest, accurate, and meaningful recommendation.
+
+If you believe there has been an error or would like to discuss your request further, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding.
+
+Best regards,
+```
+
+#### 2.3.19. Staff Applications Form - Approval Email Template
+
+```md
+Dear [Applicant's Name],
 
 Thank you so much for taking the time to apply for a volunteer role with NHCarrigan. We truly appreciate your interest in contributing your time and energy to our community.
 
-After carefully reviewing your application, we’ve decided not to move forward with your candidacy for this volunteer position. Please don’t take this as a reflection of your value or potential—our selection process is highly competitive, and we often have to make very difficult decisions.
+After carefully reviewing your application, we are excited to inform you that we would like to move forward with your candidacy! We were impressed by [specific aspects of their application] and believe you would be a valuable addition to our team.
+
+**Next Steps:**
+- You will receive a separate email with your contract and onboarding materials
+- Please review the contract carefully and reach out with any questions or concerns
+- You can reach out to us on Discord (https://chat.nhcarrigan.com) or reply to this email if you have any questions or concerns
+
+We are thrilled about the possibility of working with you and look forward to welcoming you to our team. Thank you again for your interest and enthusiasm!
+
+Warm regards,
+```
+
+#### 2.3.20. Staff Applications Form - Onboarding Email Template
+
+```md
+Dear [New Staff Member's Name],
+
+Welcome to the NHCarrigan team! We are thrilled to have you join us and are excited to begin working together.
+
+**Getting Started:**
+
+1. **Join Our Discord Server:**
+   - Please join our Discord community at: https://chat.nhcarrigan.com
+   - This is where most of our team communication and collaboration happens
+
+2. **Access Credentials:**
+   - **Email:**
+     - Address: 
+     - Password:
+     - Can access email via web at https://mail.nhcarrigan.com/mail or through any email client/app. A reminder that this is only for work-related use. Please do not spam people and get our mail server blocked (I do have logs).
+   - **Gitea:** https://git.nhcarrigan.com
+     - Username:
+     - Password: 
+
+3. **Complete Your Training:**
+   - Please complete the policy assessment form for training: https://forms.nhcarrigan.com/o/docs/forms/nxaJyKBuKH9nrt3m5VC98w/4
+   - This is an important step to ensure you are familiar with our policies and procedures
+
+**Next Steps:**
+- Our team will be in touch shortly to discuss your role-specific responsibilities
+- Feel free to explore our documentation at https://docs.nhcarrigan.com
+
+If you have any questions or need assistance getting set up, please don't hesitate to reach out to us on Discord or reply to this email.
+
+We are excited to have you on board and look forward to working with you!
+
+Warm regards,
+```
+
+#### 2.3.21. Staff Applications Form - Rejection Email Template
+
+```md
+Dear [Applicant's Name],
+
+Thank you so much for taking the time to apply for a volunteer role with NHCarrigan. We truly appreciate your interest in contributing your time and energy to our community.
+
+After carefully reviewing your application, we've decided not to move forward with your candidacy for this volunteer position at this time. Please don't take this as a reflection of your value or potential—our selection process is highly competitive, and we often have to make very difficult decisions.
+
+Please note that due to the large volume of applications we receive, we are unable to provide personalised feedback. Here are some common application issues we see:
+
+1. Low-effort Application: Please ensure you are taking the time to provide detailed, well-thought responses. The more effort you put in, the more likely we will be able to accept your application.
+2. Invalid Discord ID: Applications require you to provide your unique Discord ID - this is a 16 to 19 digit number that uniquely identifies your Discord account. If this is incorrect, we are unable to accept an application. If you need help finding yours, please refer to https://dis.gd/findid
+3. Concerning Responses: If your responses to any of the application questions raise red flags, we decline your application. Remember that you want to paint yourself in the best light here.
 
 We still encourage you to stay engaged with our community spaces, events, and projects. There are always opportunities to connect, learn, and grow together, and we would love to see you continue to participate.
 
+We encourage you to take the time to consider these common points of failure, and would welcome a resubmission from you in the future.
+
 Thank you again for your interest and enthusiasm. We wish you the very best in all your endeavors and hope our paths cross again in the future.
 
 Warm regards,
-Naomi Carrigan
-CEO, NHCarrigan
 ```
 
-### 2.7. Meeting Request Confirmation Template
+#### 2.3.22. Testimonials Form - Approval Email Template
 
 ```md
-Hey <name>,
+Hello [Contributor's Name],
 
-Thank you for reaching out to schedule a meeting! I am excited to connect with you and get to know who you are.
+Thank you for sharing your testimonial with us! We have reviewed your submission and are pleased to accept it for publication.
 
-You may use this link to schedule a slot on my calendar: https://zcal.co/nhcarrigan/meet
+**Testimonial Details:**
+- Your testimonial will be reviewed and may be featured on our website, social media, or other promotional materials
+- We may edit your testimonial for length, clarity, or formatting whilst preserving your message and intent
+- You will be credited as [name/handle as provided]
 
-It looks like we share the <CYC|fCC|both|neither> communities, so you may choose that as your meeting location if you wish.
-OR
-It does not look like we share any Discord communities, so you will need to select NHCarrigan Discord as your meeting location.
+**Next Steps:**
+- Your testimonial will be added to our review queue
+- We will notify you when it is published (if applicable)
+- Thank you for helping others learn about our community and services!
 
-Please note that if you choose to meet in the NHCarrigan Discord, you will need to join our Discord community at https://chat.nhcarrigan.com in order to meet with us. When it is time for your scheduled meeting, you will need to join the "waiting-room" voice channel. We will drag you into our private voice chat when we are ready to chat with you.
+Your words help us build trust and connect with others who might benefit from our community. We truly appreciate you taking the time to share your experience.
 
-If you have any questions, please do not hesitate to reach out to us.
+If you have any questions or would like to make changes to your testimonial, please don't hesitate to reach out.
+
+Best regards,
 ```
 
-### 2.8. Mentorship Programme Welcome Template
+#### 2.3.23. Testimonials Form - Rejection Email Template
 
 ```md
-Hey <name>,
+Hello [Contributor's Name],
 
-Welcome to our mentorship programme! We are excited to support you and watch you learn and grow!
+Thank you for taking the time to submit a testimonial. We appreciate your interest in sharing your experience with our community.
 
-In order to participate, you will need to join our Discord community at https://chat.nhcarrigan.com - then, select the mentorship role from our self-selectable roles to gain access to the programme channels.
+After careful review, we have decided not to publish your testimonial at this time. This decision may be based on factors such as:
+- Content alignment with our community values and standards
+- Formatting or clarity requirements
+- Current testimonial collection needs
+- Verification or authenticity concerns
 
-You will receive further instructions once you have selected the role.
+Please note that due to the volume of testimonials we receive, we are unable to provide detailed feedback on every declined submission.
 
-Keep an eye on the Discord community for announcements and opportunities to collaborate!
+We encourage you to stay engaged with our community and consider submitting a testimonial in the future if your experience changes or if you have additional feedback to share.
 
-Congratulations again!
+If you have questions about our testimonial process, please reach out in our Discord community: https://chat.nhcarrigan.com
+
+Thank you for your understanding and continued engagement with our community.
+
+Best regards,
 ```
 
-### 2.9. Discord Bot Donation Copy Template
+### 2.4. Form Components
+
+#### 2.4.1. Form Consent for Email Communications
+
+Description:
+
+```
+At NHCarrigan, we are fully committed to respecting and protecting your privacy. We strictly adhere to a policy of non-disclosure regarding your personal data; we do not sell, trade, or transfer your information to outside parties. The contact details you provide will be used exclusively for the purpose of responding to your inquiry or addressing the subject of this form. For a complete overview of our data practices, please review our [Privacy Policy](https://docs.nhcarrigan.com/legal/privacy/).
+```
+
+Question: 
+
+```
+I agree to be contacted via email, solely for the purpose of addressing this submission.
+```
+
+#### 2.4.2. Form Image Header
+
+```html
+<div style="width: 100%; text-align: center"><img src="https://cdn.nhcarrigan.com/logo.png" style="width: 250px; height: 250px"></div>
+```
+
+#### 2.4.3. Form Confirmation
+
+Add this at the end of any form specific text.
+
+```
+If you'd like to stay up to date on everything we do, come hang out in our server! https://chat.nhcarrigan.com
+```
+
+### 2.5. Community & Communication Templates
+
+#### 2.5.1. Discord Server Introduction Template
+
+```md
+Hello~! I'm Naomi, a 34 year old transfem software engineer and community manager based in Washington. All of my work (and therefore most of my life) is spent online, so I'm always looking for new spaces and people to vibe with. Remote work can feel dreadfully isolating, and this is my attempt to combat that feeling.
+
+<insert bit about community here>
+``` 
+
+### 2.6. Gaming Templates
+
+#### 2.6.1. Guild Wars 2 Recruitment Advertisement Template
+
+This has to be sent in two chat messages because of the length.
+
+```
+Hiya friends~! Naomi's Newbies is a new guild that is really focused on helping newer players come to love the game, and supporting casual players who have busy schedules.
+```
+
+```
+We have no activity requirement, no rep requirement, a Discord community, and more! If you are interested, please whisper me and I will gladly invite you!
+```
+
+### 2.7. Donation Templates
+
+#### 2.7.1. Discord Bot Donation Copy Template
 
 These go in the bot SKUs:
 
-### Subscription Name
+##### 2.7.1.1. Subscription Name
 
 ```
 Sponsor Naomi
 ```
 
-### Subscription Description
+##### 2.7.1.2. Subscription Description
 
 ```
 **How Your Support Makes a Difference**
@@ -196,97 +721,77 @@ Every donation, regardless of size, contributes to this mission. Together, we're
 Thank you for considering a donation and being part of this important journey.
 ```
 
-### Benefit Name
+##### 2.7.1.3. Benefit Name
 
 ```
 Your donation:
 ```
 
-### Benefit Description
+##### 2.7.1.4. Benefit Description
 
 ```
 Helps a transfemme technology witch create free software, build inclusive communities, and guide others on their journey in tech.
 ```
 
-### Notes
+##### 2.7.1.5. Notes
 
 - Use my avatar for subscription
 - Use pentatrans for benefit
 
-### 2.10. Discord Server Introduction Template
+### 2.8. freeCodeCamp Templates
+
+#### 2.8.1. freeCodeCamp Sprint Issue Template
 
 ```md
-Hello~! I'm Naomi, a 34 year old transfem software engineer and community manager based in Washington. All of my work (and therefore most of my life) is spent online, so I'm always looking for new spaces and people to vibe with. Remote work can feel dreadfully isolating, and this is my attempt to combat that feeling.
+**Type:** Workshop/Lab/????  
+**Summary:**
 
-<insert bit about community here>
-``` 
+**User Stories**
+1. 
+2.
+3.
 
-### 2.11. Guild Wars 2 Recruitment Advertisement Template
+**Technical Notes**
+- 
+-
+-
 
-This has to be sent in two chat messages because of the length.
+## This issue is part of Naomi's sprint initiatives.
 
-```
-Hiya friends~! Naomi's Newbies is a new guild that is really focused on helping newer players come to love the game, and supporting casual players who have busy schedules.
+If you are interested in working on this issue, [join our Discord](https://chat.freecodecamp.org) and ping Naomi!
+
+### Action Items
+
+- [ ] Prototype created and PRed to https://github.com/freeCodeCamp/curriculumexpansion
+- [ ] Prototype reviewed + approved + merged by staff
+- [ ] Break prototype down into steps (if workshop) or individual "step" (if lab) - write description, hint text **only** (no tests yet), and seed code.
+- [ ] DRAFT PR opened on https://github.com/freeCodeCamp/freeCodeCamp
+- [ ] Team + Naomi review your steps, confirm the breakdown + user stories look good
+- [ ] Begin writing the actual test logic, refer to https://contribute.freecodecamp.org/curriculum-help/#js-helper for how to write tests for JS challenges
+- [ ] Mark PR as not a draft, team reviews + approves + merges
+- [ ] YOU DID IT GO CELEBRATE!
+
+### Other Details
+
+- Remember to keep an eye on your PRs and respond to review comments and suggestions
+- For workshops, refer to: https://contribute.freecodecamp.org/how-to-work-on-coding-challenges/
+- For labs, refer to: https://contribute.freecodecamp.org/how-to-work-on-labs/
+
+### Questions
+
+Ping Naomi in the sprint channel on Discord
 ```
 
-```
-We have no activity requirement, no rep requirement, a Discord community, and more! If you are interested, please whisper me and I will gladly invite you!
-```
-
-### 2.12. Form Consent for Email Communications
-
-Description:
-
-```
-At NHCarrigan, we are fully committed to respecting and protecting your privacy. We strictly adhere to a policy of non-disclosure regarding your personal data; we do not sell, trade, or transfer your information to outside parties. The contact details you provide will be used exclusively for the purpose of responding to your inquiry or addressing the subject of this form. For a complete overview of our data practices, please review our [Privacy Policy](https://docs.nhcarrigan.com/legal/privacy/).
-```
-
-Question: 
-
-```
-I agree to be contacted via email, solely for the purpose of addressing this submission.
-```
-
-### 2.13. Form Image Header
-
-```html
-<div style="width: 100%; text-align: center"><img src="https://cdn.nhcarrigan.com/logo.png" style="width: 250px; height: 250px"></div>
-```
-
-### 2.14. Form Confirmation
-
-Add this at the end of any form specific text.
-
-```
-If you'd like to stay up to date on everything we do, come hang out in our server! https://chat.nhcarrigan.com
-```
-
-### 2.15. Sanction Appeal Denial Email Template
-
-Subject Line: `Appeal Decision - [Sanction Type] Appeal Dismissed`
+#### 2.8.2. freeCodeCamp Sprint Progress Update
 
 ```md
-Dear [Appellant's Name],
+**Progress Update - <date>**
 
-Thank you for submitting your appeal regarding the disciplinary sanction imposed on [date of original sanction]. We acknowledge receipt of your appeal and have conducted a thorough review in accordance with our Community Disciplinary Appeals Policy.
-
-After careful consideration by the Appeals Panel, which included examination of all evidence and documentation, review of the original decision and its rationale, and assessment of your submissions and arguments, we have determined that your appeal does not meet the grounds for appeal as established in our policy.
-
-**Decision**: Your appeal has been dismissed. The original disciplinary sanction remains in full effect.
-
-**Reasoning**: [Insert detailed reasoning here, addressing the specific grounds raised in the appeal and explaining why the original decision was appropriate. This should reference procedural compliance, proportionality of the sanction, factual accuracy, evidence considered, and correct application of community policies.]
-
-As outlined in Section 8.1 of our Community Disciplinary Appeals Policy, decisions of the Appeals Panel are final and binding. No further appeals or reviews are available through our internal processes.
-
-We understand that this decision may be disappointing. Our appeals process is designed to ensure fairness and transparency, and we have given your submission careful consideration. The original sanction was imposed in accordance with our community standards and policies, which are designed to maintain a safe and welcoming environment for all members.
-
-If you have any questions about this decision, please note that our Appeals Panel's determination is final. We appreciate your understanding and respect for our community standards and processes.
-
-Regards,
-The Appeals Panel
-NHCarrigan Community Leadership
+<summarise what contributor said>
 ```
 
+## 3. DISCLAIMERS AND USAGE REQUIREMENTS
+
 ### 3.1. Reference to Comprehensive Liability Framework
 
 **IMPORTANT: Comprehensive liability limitations, damage exclusions, and maximum liability caps are set forth in our Limitation of Liability and Indemnification Policy, which is incorporated herein by reference.**
diff --git a/src/content/docs/projects/caelia.md b/src/content/docs/projects/caelia.md
index 26823d5..b8ef7b6 100644
--- a/src/content/docs/projects/caelia.md
+++ b/src/content/docs/projects/caelia.md
@@ -10,7 +10,7 @@ This section is for those interacting with a live instance of the Application.
 
 ### What is Caelia?
 
-Caelia is a Discord bot designed to help create more inclusive communities by gently notifying users when they may have used language that could be considered non-inclusive. The bot uses the Alex.js library to analyze messages and provide helpful suggestions for more inclusive alternatives.
+Caelia is a Discord bot designed to help create more inclusive communities by gently notifying users when they may have used language that could be considered non-inclusive. The bot uses the Alex.js library to analyse messages and provide helpful suggestions for more inclusive alternatives.
 
 ### How to Add Caelia to Your Server
 
@@ -199,7 +199,7 @@ src/
 
 - **Language Rules**: Enhancing Alex.js configuration for better accuracy
 - **Error Handling**: Improving error recovery and user experience
-- **Performance**: Optimizing message processing speed
+- **Performance**: Optimising message processing speed
 - **Features**: Adding new functionality while maintaining simplicity
 - **Documentation**: Improving user and developer documentation
 
diff --git a/src/content/docs/projects/cordelia-taryne.md b/src/content/docs/projects/cordelia-taryne.md
index 07733e8..ba6a3ef 100644
--- a/src/content/docs/projects/cordelia-taryne.md
+++ b/src/content/docs/projects/cordelia-taryne.md
@@ -2,7 +2,7 @@
 title: Cordelia Taryne
 ---
 
-Cordelia Taryne (hereinafter the "Application") is an AI-powered multi-purpose assistant Discord bot that leverages Anthropic's Claude AI to provide various text processing, analysis, and assistance features. The bot features a distinctive vampire personality named Cordelia with haughty and self-inflated characteristics, providing users with intelligent assistance while maintaining a unique character persona.
+Cordelia Taryne (hereinafter the "Application") is an AI-powered multi-purpose assistant Discord bot that leverages Anthropic's Claude AI to provide various text processing, analysis, and assistance features. The bot features a distinctive vampire personality named Cordelia with haughty and self-inflated characteristics, providing users with intelligent assistance whilst maintaining a unique character persona.
 
 ## 1. User Documentation
 
@@ -42,8 +42,8 @@ Cordelia Taryne offers the following slash commands:
 - **Access**: Requires active subscription
 
 #### `/mood`
-- **Description**: Analyze the sentiment and mood of text passages
-- **Parameters**: `text` (required, max 2000 characters) - The text to analyze
+- **Description**: Analyse the sentiment and mood of text passages
+- **Parameters**: `text` (required, max 2000 characters) - The text to analyse
 - **Usage**: `/mood text: I had an amazing day at the beach!`
 - **Access**: Requires active subscription
 
@@ -71,7 +71,7 @@ Most features require an active subscription. The bot uses Discord's premium sub
 Cordelia has a distinctive personality:
 - **Character**: A vampire assistant with a haughty and self-inflated demeanour
 - **Appearance**: Blonde hair in twin buns, pink-red cat-like eyes, pale skin, gold dress
-- **Behavior**: Subtly condescending but never directly rude or insulting
+- **Behaviour**: Subtly condescending but never directly rude or insulting
 - **Communication**: Professional assistance without role-playing text
 
 ### Support and Feedback
@@ -288,7 +288,7 @@ src/
 4. Test subscription gating and error handling
 5. Update documentation
 
-#### Modifying AI Behavior
+#### Modifying AI Behaviour
 1. Update personality configuration if needed
 2. Modify system prompts in relevant modules
 3. Test with various inputs and edge cases
diff --git a/src/content/docs/staff/apply.md b/src/content/docs/staff/apply.md
index ecc8a53..74ce41f 100644
--- a/src/content/docs/staff/apply.md
+++ b/src/content/docs/staff/apply.md
@@ -10,7 +10,7 @@ Unless explicitly stated otherwise in a separate written agreement, all position
 
 ### 1.2. Service Philosophy
 
-Our volunteer programme operates on servant leadership principles, emphasising service to the community, professional development opportunities, and meaningful contribution to creating inclusive online environments. All volunteer service operates within our comprehensive legal and policy framework.
+Our volunteer programme operates on **servant leadership principles**, emphasising service to the community, professional development opportunities, and meaningful contribution to creating inclusive online environments. For a comprehensive explanation of servant leadership, see [Staff Role Definition and Principles](/staff/handbook#22-staff-role-definition-and-principles) in the Staff Handbook. All volunteer service operates within our comprehensive legal and policy framework.
 
 ## 2. Available Volunteer Opportunities
 
diff --git a/src/content/docs/staff/handbook.md b/src/content/docs/staff/handbook.md
index 6aa405d..92d7f3c 100644
--- a/src/content/docs/staff/handbook.md
+++ b/src/content/docs/staff/handbook.md
@@ -4,7 +4,7 @@ title: Staff Handbook
 
 ## Introduction and Framework
 
-Welcome to our organisation. This Staff Handbook serves as a comprehensive guide to our policies, procedures, and expectations for all volunteer staff members. This handbook operates within our comprehensive legal and policy framework, which includes:
+Welcome to our organisation. This Staff Handbook serves as a comprehensive guide to our policies, procedures, and expectations for all Team members (volunteers). This handbook operates within our comprehensive legal and policy framework, which includes:
 
 **(a)** **Community Code of Conduct**: Fundamental behavioural standards and community values;
 
@@ -18,11 +18,11 @@ Welcome to our organisation. This Staff Handbook serves as a comprehensive guide
 
 **(f)** **Content and Moderation Policy**: Comprehensive moderation standards and enforcement procedures.
 
-**IMPORTANT: This handbook supplements but does not replace our comprehensive policy framework. All staff members are required to familiarise themselves with and adhere to all applicable policies, which are incorporated herein by reference.**
+**IMPORTANT: This handbook supplements but does not replace our comprehensive policy framework. All Team members are required to familiarise themselves with and adhere to all applicable policies, which are incorporated herein by reference.**
 
 ### Our Mission and Values
 
-We rely on every staff member, regardless of position, to help foster a safe, welcoming, and inclusive environment that serves our community's diverse needs. Your dedication, skills, and adherence to our standards are crucial in achieving our organisational mission of creating exceptional online communities.
+We rely on every Team member, regardless of position, to help foster a safe, welcoming, and inclusive environment that serves our community's diverse needs. Your dedication, skills, and adherence to our standards are crucial in achieving our organisational mission of creating exceptional online communities.
 
 By familiarising yourself with this handbook and our broader policy framework, you play a vital role in maintaining the integrity, inclusivity, and effectiveness of our organisation.
 
@@ -30,7 +30,7 @@ By familiarising yourself with this handbook and our broader policy framework, y
 
 ### 1.1. Flexible Engagement
 
-We recognise and deeply appreciate that our staff members are volunteers dedicating their time and effort to support our community. As such, we do not impose rigid activity quotas or specific engagement levels.
+We recognise and deeply appreciate that our Team members are volunteers dedicating their time and effort to support our community. As such, we do not impose rigid activity quotas or specific engagement levels.
 
 ### 1.2. Communication of Extended Absences
 
@@ -47,21 +47,33 @@ In cases of prolonged inactivity:
 - This policy helps maintain an engaged and responsive staff roster.
 - Please note that removal due to inactivity is not punitive and does not reflect negatively on your contributions.
 
-### 1.4. Returning to the Team
+### 1.4. Training Compliance and Dismissal
+
+**Mandatory Training Compliance:**
+
+All Team members must comply with mandatory training requirements:
+
+**(a)** **Initial Training:** Complete all required training and submit confirmation form during onboarding before beginning staff duties
+
+**(b)** **Annual Training:** Complete annual training review at the start of each calendar year and submit confirmation form by the specified deadline
+
+**(c)** **Dismissal for Non-Compliance:** Failure to complete annual training review and submit the required confirmation form by the deadline will result in immediate dismissal from Team positions. This policy ensures all Team members maintain current knowledge of policies and procedures essential for community safety and effective service.
+
+### 1.5. Returning to the Team
 
 We value your contributions and understand that life circumstances can change:
 
 - If you've been removed due to inactivity, you are always welcome to rejoin the staff team when your schedule permits.
 - To rejoin, please contact an admin.
 
-### 1.5. Balancing Commitments
+### 1.6. Balancing Commitments
 
 We encourage you to balance your volunteer work with your personal life and other commitments:
 
 - Your well-being is important to us. Never feel pressured to overextend yourself.
 - If you find your role becoming stressful or overly time-consuming, please discuss this with an admin.
 
-### 1.6. Recognition and Appreciation
+### 1.7. Recognition and Appreciation
 
 **Reference to Comprehensive Recognition Framework**: Detailed volunteer recognition, appreciation programmes, and wellness support systems are set forth in our Community Recognition and Appreciation Policy, which is incorporated herein by reference.
 
@@ -82,18 +94,38 @@ Our community leadership operates through a structured hierarchy, outlined in [a
 
 ### 2.2. Staff Role Definition and Principles
 
-As a staff member, you occupy a position of trust within our community operating under the servant leadership principle. All staff roles come with responsibilities and tools to ensure the safety and well-being of our community members. Key principles:
+#### 2.2.1. Servant Leadership Principle
 
-- Being a staff member does not elevate you above other community members
+As a Team member, you occupy a position of trust within our community operating under the **servant leadership principle**. This foundational principle guides all Team roles and responsibilities.
+
+**What is Servant Leadership?**
+
+Servant leadership is a philosophy and set of practices that enriches the lives of individuals, builds better organisations, and ultimately creates a more just and caring world. In our community context:
+
+**(a)** **Service-Oriented Leadership**: Team members serve the community rather than wielding authority for personal benefit. Your role exists to support and empower community members, not to exercise power over them.
+
+**(b)** **Community-Centred Focus**: All decisions and actions prioritise the well-being and growth of the community and its members. Personal interests or preferences are secondary to community needs.
+
+**(c)** **Empowerment and Support**: Team members work to enable community members to succeed, grow, and participate meaningfully. Rather than controlling or directing, Team members facilitate and support.
+
+**(d)** **Humility and Accountability**: Team members recognise that leadership is a responsibility, not a privilege. You are accountable to the community you serve through established accountability mechanisms.
+
+**(e)** **Inclusive Participation**: Servant leadership means ensuring all voices are heard, especially those of marginalised community members. Staff actively work to remove barriers to participation.
+
+**Key Principles for Team Members:**
+
+- Being a Team member does not elevate you above other community members
 - Your role is one of service and support, not authority or superiority
 - You serve the community rather than wielding authority for personal benefit
 - You are accountable to the community you serve through established accountability mechanisms
+- Leadership is demonstrated through service, not through exercising power
+- Success is measured by community member growth and well-being, not personal recognition
 
 ### 2.3. General Staff Expectations
 
 #### 2.3.1. Leading by Example
 
-As staff members, you are expected to exemplify the ideal community member:
+As Team members, you are expected to exemplify the ideal community member:
 
 - Be active and engaged within the community within your capacity and role
 - Strictly adhere to all community rules and guidelines
@@ -102,12 +134,12 @@ As staff members, you are expected to exemplify the ideal community member:
 
 #### 2.3.2. Balancing Roles and Responsibilities
 
-Remember that you are both a staff member and a community member:
+Remember that you are both a Team member and a community member:
 
-- Not every interaction requires official staff intervention
+- Not every interaction requires official Team intervention
 - Engage in regular social interactions with fellow community members
-- Maintain a balance between your staff duties and personal enjoyment within the community
-- Recognise when situations require your staff expertise versus when you can participate as a regular member
+- Maintain a balance between your Team duties and personal enjoyment within the community
+- Recognise when situations require your Team expertise versus when you can participate as a regular member
 
 #### 2.3.3. Platform Familiarity and Cross-Platform Coordination
 
@@ -115,7 +147,7 @@ Our community spans multiple platforms with coordinated governance:
 
 - You are entrusted with maintaining community standards across platforms, following consistent policies
 - Focus on supporting platforms you're comfortable with whilst maintaining policy consistency
-- Seek assistance or guidance from fellow staff members and leadership when dealing with unfamiliar situations
+- Seek assistance or guidance from fellow Team members and Leadership when dealing with unfamiliar situations
 - Coordinate with other platform teams to ensure cohesive community experience
 
 ### 2.4. Staff Standards and Accountability
@@ -128,7 +160,7 @@ Maintain exemplary conduct aligned with our community values:
 
 - Demonstrate respect, inclusivity, safety, and collaborative problem-solving in all interactions
 - Remain calm and objective, especially in challenging situations involving community safety
-- Model the behaviour expected of all community members whilst serving in your staff capacity
+- Model the behaviour expected of all community members whilst serving in your Team capacity
 - Use appropriate, inclusive language and maintain trauma-informed practices
 
 #### 2.4.2. Fairness, Consistency, and Evidence-Based Decision-Making
@@ -138,7 +170,7 @@ Apply policies and take actions consistently following established frameworks:
 - Treat all community members equally with dignity and respect regardless of background or circumstances
 - Make decisions based on community policies and evidence-based practices, not personal preferences
 - Follow progressive disciplinary frameworks and restorative justice principles when appropriate
-- Consider cultural sensitivity and accessibility needs in all staff decisions and actions
+- Consider cultural sensitivity and accessibility needs in all Team decisions and actions
 
 #### 2.4.3. Transparency and Community Accountability
 
@@ -153,7 +185,7 @@ Maintain transparency and accountability to the community:
 
 #### 2.5.1. Team Communication
 
-Maintain open lines of communication with your fellow staff members:
+Maintain open lines of communication with your fellow Team members:
 
 - Use designated channels (e.g., `#staff-chat`) to discuss community issues and seek guidance
 - Share experiences and seek advice when facing challenging situations
@@ -169,16 +201,68 @@ Stay informed and improve your skills:
 
 #### 2.5.3. Escalation Protocol
 
-Know when and how to escalate issues:
+**Universal Escalation Principles:**
 
-- Identify situations that require input from senior staff or administrators
-- Follow established procedures for escalating complex, sensitive, or high-impact matters
-- Understand the scope of your role and when issues exceed your authority or expertise
+All Team members must know when and how to escalate issues appropriately. Escalation ensures that complex, sensitive, or high-impact matters receive the appropriate level of attention and expertise.
+
+**When to Escalate:**
+
+**(a)** **Complexity Beyond Your Expertise**: Situations that exceed your knowledge, training, or authority level require escalation to Team members with appropriate expertise.
+
+**(b)** **Safety Concerns**: Any situation involving immediate or potential safety risks to community members requires immediate escalation to senior staff and appropriate coordinators (Crisis Response Coordinator, Child Safety Coordinator, etc.).
+
+**(c)** **Policy Ambiguity**: When policies are unclear or seem to conflict, escalate to leadership for clarification rather than making assumptions.
+
+**(d)** **High-Impact Decisions**: Decisions that significantly affect community members, community culture, or organisational operations should involve senior staff input.
+
+**(e)** **Legal or Compliance Concerns**: Any situation with potential legal implications or compliance requirements should be escalated to Legal and Policy Advisor or senior leadership.
+
+**(f)** **Team-Related Issues**: Conflicts or concerns involving other Team members should be escalated through appropriate channels to maintain professional boundaries.
+
+**(g)** **Repeated or Persistent Issues**: Patterns of problematic behaviour or recurring issues that haven't been resolved through standard interventions require escalation.
+
+**How to Escalate:**
+
+**(a)** **Use Appropriate Channels**: Escalate through designated staff channels (e.g., `#staff-chat` on Discord) or direct contact with relevant coordinators or senior staff.
+
+**(b)** **Provide Complete Context**: When escalating, include:
+- Clear description of the situation
+- Relevant background and history
+- Actions already taken
+- Evidence or documentation
+- Your assessment of urgency and risk level
+- Specific questions or support needed
+
+**(c)** **Maintain Communication**: Continue supporting the situation whilst escalation is in process. Don't abandon community members whilst waiting for escalation response.
+
+**(d)** **Follow Instructions**: Once escalation occurs, follow any specific directions from senior staff or coordinators whilst maintaining your role responsibilities.
+
+**(e)** **Document Appropriately**: Document escalation decisions and outcomes for accountability and learning purposes.
+
+**Escalation Timeframes:**
+
+- **Immediate (Within 15 minutes)**: Safety threats, crisis situations, child safety concerns
+- **Urgent (Within 1 hour)**: Harassment, significant policy violations, legal concerns
+- **Standard (Within 24 hours)**: Complex situations, policy questions, persistent issues
+- **Routine (Within 3-5 days)**: General questions, process improvements, non-urgent concerns
+
+**Context-Specific Escalation:**
+
+Different types of situations may require escalation to specific coordinators or teams:
+- **Crisis Response**: Escalate mental health crises to Crisis Response Coordinator
+- **Child Safety**: Escalate child safety concerns to Child Safety Coordinator
+- **Harassment**: Escalate harassment reports to Harassment Response Coordinator
+- **Technical Issues**: Escalate technical problems to Technical Administrators
+- **Policy Questions**: Escalate policy questions to Legal and Policy Advisor
+
+For detailed escalation procedures specific to different situations, refer to the relevant training documents (Crisis Response Training, Child Safety Training, Harassment Response Training, etc.).
 
 ### 2.6. Documentation and Transparency
 
 **Reference to Comprehensive Frameworks**: Detailed procedures, documentation requirements, and transparency systems are set forth in our Content and Moderation Policy and Community Leadership and Governance Policy, which are incorporated herein by reference.
 
+**Comprehensive Training Available**: For complete documentation procedures, requirements, and best practices, all Team members must complete the [Documentation and Transparency Training](/staff/training/documentation-transparency). This section provides a brief overview; refer to the training document for detailed guidance.
+
 #### 2.6.1. Action Documentation Requirements
 - All significant staff actions must be documented appropriately for transparency and consistency
 - Staff in moderation roles must log actions via our API system
@@ -191,7 +275,7 @@ Know when and how to escalate issues:
 - Training provided on relevant documentation systems and transparency requirements
 - Ongoing support available for technical and procedural questions related to your specific role
 
-## 3. Working With Fellow Staff Members
+## 3. Working With Fellow Team Members
 
 ### 3.1. Communication Channels
 
@@ -201,7 +285,7 @@ Know when and how to escalate issues:
 - Discord `#staff-chat` channel for real-time communication and coordination
 
 #### 3.1.2. Use of Staff Communication Channels
-- Utilize staff channels for:
+- Utilise staff channels for:
   - Discussing concerns and seeking guidance on community issues
   - Seeking advice on handling situations within your role
   - Requesting assistance with ongoing issues or projects
@@ -210,7 +294,7 @@ Know when and how to escalate issues:
 
 ### 3.2. Collaborative Problem-Solving
 
-- Approach fellow staff members for help and insights when needed
+- Approach fellow Team members for help and insights when needed
 - Be open to offering assistance when others request it within your expertise
 - Engage in constructive discussions to find optimal solutions
 - Collaborate effectively across different roles and specialties
@@ -218,7 +302,7 @@ Know when and how to escalate issues:
 ### 3.3. Team Unity and Public Image
 
 - Maintain a united front in public spaces
-- Avoid disagreeing with or criticizing fellow staff members in public forums
+- Avoid disagreeing with or criticising fellow Team members in public forums
 - If you have concerns about a staff action or a colleague's behaviour:
   - Address the issue privately in staff channels or through direct messages
   - Seek resolution through open and respectful dialogue
@@ -243,7 +327,7 @@ Know when and how to escalate issues:
 ### 3.5. Supporting Each Other
 
 - Recognise that staff work can be challenging and sometimes emotionally demanding
-- Offer emotional support and encouragement to fellow staff members
+- Offer emotional support and encouragement to fellow Team members
 - Share experiences and coping strategies for dealing with difficult situations
 - Promote a supportive team environment that prioritises member wellness
 
@@ -273,7 +357,7 @@ Know when and how to escalate issues:
 
 ### 3.10. Continuous Improvement
 
-- Be open to feedback from fellow staff members and leadership
+- Be open to feedback from fellow Team members and Leadership
 - Suggest improvements to processes, procedures, or team communication
 - Participate in team training, development activities, and skill-building opportunities
 
@@ -287,7 +371,7 @@ As a member of our team, you play a crucial role in ensuring a positive and smoo
 
 - Familiarize yourself with most of our projects to answer a wide range of questions.
 - Stay updated on recent changes or updates to our projects.
-- Utilize available resources (documentation, FAQs, wikis) to assist users effectively.
+- Utilise available resources (documentation, FAQs, wikis) to assist users effectively.
 
 ### 4.3. Handling User Inquiries
 
@@ -301,8 +385,8 @@ As a member of our team, you play a crucial role in ensuring a positive and smoo
 
 ### 4.4. Collaborative Problem-Solving
 
-- Utilize the staff chat in Discord for discussing complex user questions.
-- Engage with fellow staff members to collaboratively find solutions.
+- Utilise the staff chat in Discord for discussing complex user questions.
+- Engage with fellow Team members to collaboratively find solutions.
 - Share knowledge and insights to improve the team's overall support capabilities.
 
 ### 4.5. Follow-up
@@ -376,7 +460,7 @@ As a member of our team, you play a crucial role in ensuring a positive and smoo
 ### 6.1. Eligibility for Cross-Platform Roles
 
 - Once you have been selected for a staff position on any of our platforms, you become eligible to request staff access on additional platforms.
-- This opportunity is open to all current staff members in good standing.
+- This opportunity is open to all current Team members in good standing.
 
 ### 6.2. Requesting Additional Platform Access
 
@@ -427,7 +511,7 @@ As a member of our team, you play a crucial role in ensuring a positive and smoo
 
 #### 6.8.2. Community Accountability
 - Community feedback integration through surveys and input mechanisms
-- Transparent performance reporting while respecting individual privacy
+- Transparent performance reporting whilst respecting individual privacy
 - Responsive improvement planning based on community needs and feedback
 - Leadership development support and succession planning participation
 
@@ -435,7 +519,7 @@ As a member of our team, you play a crucial role in ensuring a positive and smoo
 
 ### 7.1. Comprehensive Policy Integration
 
-All staff members must comply with our complete legal and policy framework:
+All Team members must comply with our complete legal and policy framework:
 
 **(a)** **Terms of Service**: Fundamental legal obligations and user agreements;
 
@@ -465,17 +549,148 @@ All staff members must comply with our complete legal and policy framework:
 
 ## 8. Professional Development and Support
 
-### 8.1. Training and Education Programs
+### 8.1. Mandatory Training Requirements
 
-**Reference to Comprehensive Development Framework**: Detailed training programmes, professional development opportunities, and leadership skill enhancement are set forth in our Community Leadership and Governance Policy, which is incorporated herein by reference.
+**IMPORTANT: All Team members are required to complete comprehensive training review and submit confirmation forms. Failure to complete annual training requirements will result in dismissal from Team positions.**
 
-#### 8.1.1. Mandatory Training Components
-- Foundation training in community values, mission, and policy frameworks
-- Conflict resolution and mediation skills development
-- Accessibility and inclusive practices certification
-- Cultural competency and trauma-informed practices education
+This section establishes the mandatory training requirements for all Team members. All training documents reference these requirements; this handbook section is the authoritative source.
 
-#### 8.1.2. Ongoing Development Opportunities
+#### 8.1.1. Initial Onboarding Training
+
+Upon joining the Team, all new Team members must complete comprehensive initial onboarding training before beginning independent Team duties.
+
+**(a)** **Review All Required Documents:**
+
+**Staff Documents:**
+- Staff Handbook (this document)
+- Professional Conduct Standards for Volunteers
+
+**Community Policies:**
+- Community Code of Conduct
+- Community Leadership and Governance Policy
+- Community Recognition and Appreciation Policy
+- Community Feedback and Participation Policy
+- Appeals Policy
+
+**Legal and Policy Documents:**
+- Terms of Service
+- Privacy Policy
+- Acceptable Use Policy
+- Content and Moderation Policy
+- Limitation of Liability and Indemnification Policy
+- Crisis and Mental Health Management Policy
+- Community Support Policy
+- Community Growth Policy
+- Data Subprocessors Policy
+- Security Policy
+- DMCA Policy
+- Export Control Policy
+- Government Policy
+- SLA Policy
+- All other applicable legal policies
+
+**Training Documents (All):**
+- Documentation and Transparency Training
+- Data Privacy and GDPR Compliance Training
+- Crisis Response Training
+- Criminal Activity Training
+- Child Safety Training
+- Trauma-Informed Moderation Training
+- Bias Recognition and Mitigation Training
+- Harassment and Bullying Response Training
+- Content Moderation Fundamentals Training
+- De-escalation Techniques Training
+- Inclusive Moderation Training
+- Conflict Resolution Training
+- Community Support Specialist Training
+- Community Growth Specialist Training
+- Accessibility Coordination Training
+- Cross-Platform Coordination Training
+- Technical Contributor Training
+- Social Media Management Training
+- Mentorship Training Coordination Training
+- Data Analytics and Reporting Training
+- Self-Care Resources for Staff
+
+**(b)** **Submit Training Confirmation:**
+- Complete and submit the training confirmation form at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Confirmation must be submitted before beginning independent staff duties
+- Training completion is documented in staff records
+- Team members may not begin independent Team duties until training confirmation is submitted
+
+#### 8.1.2. Annual Training Requirements
+
+All Team members must complete annual training review at the start of each calendar year.
+
+**(a)** **Annual Review Timeline:**
+- Annual training review occurs at the start of each calendar year
+- All Team members must review all training documents, handbook, and legal policies
+- Review must be completed within the timeframe specified by leadership
+- Leadership will communicate specific deadlines each year
+
+**(b)** **Annual Confirmation Submission:**
+- Submit training confirmation form at [forms.nhcarrigan.com](https://forms.nhcarrigan.com) after completing review
+- Confirmation must be submitted by the deadline specified by leadership
+- **Failure to complete annual training review and submit confirmation form by the deadline will result in dismissal from staff positions**
+- This policy ensures all staff maintain current knowledge of policies and procedures essential for community safety and effective service
+
+**(c)** **Training Documentation:**
+- All training completions are documented in staff records
+- Training records are maintained for accountability and compliance purposes
+- Leadership monitors training completion status
+- Training documentation supports legal compliance and quality assurance
+
+#### 8.1.3. Annual Review Requirements
+
+All Team members must complete annual review processes at the start of each calendar year. These reviews are mandatory and support professional development, accountability, and continuous improvement.
+
+**(a)** **Annual Self-Review and Upward-Review:**
+- All Team members must complete the annual self-review and upward-review at the start of each calendar year
+- Reviews must be completed using the annual review form at [forms.nhcarrigan.com](https://forms.nhcarrigan.com/o/docs/forms/vWj3UYw6ezLDtkxRN3Nt1K/4)
+- Self-review facilitates honest self-reflection on performance and growth, covering role performance, community impact, collaboration, values alignment, self-care, growth, and feedback
+- Upward-review gathers feedback on leadership effectiveness and support for each supervisor or leader you report to
+- Reviews must be completed at the start of each calendar year within the timeframe specified by leadership
+- **Failure to complete annual self-review and upward-review by the deadline will result in dismissal from staff positions**
+
+**(b)** **Annual Policy Assessment:**
+- All Team members must complete the annual policy assessment at the start of each calendar year
+- The policy assessment evaluates understanding and comprehension of organisational policies, procedures, and community standards
+- Assessment must be completed using the policy assessment form at [forms.nhcarrigan.com](https://forms.nhcarrigan.com/o/docs/forms/nxaJyKBuKH9nrt3m5VC98w/4)
+- Assessment must be completed at the start of each calendar year within the timeframe specified by leadership
+- **The policy assessment is no longer self-evaluated; executives will review all assessments**
+- **Failure to complete annual policy assessment by the deadline will result in dismissal from staff positions**
+
+**(c)** **Executive Review Process:**
+- Executives will review both the annual self-review/upward-review and the policy assessment for each Team member
+- After review, executives will create a private thread in the `#staff-reviews` forum channel for each Team member
+- These private threads facilitate discussion, feedback, and development planning based on the review materials
+- Review discussions are confidential and used to support staff development and organisational improvement
+
+**(d)** **Review Timeline:**
+- Annual reviews (self-review, upward-review, and policy assessment) occur at the start of each calendar year
+- All reviews must be completed within the timeframe specified by leadership
+- Leadership will communicate specific deadlines each year
+- Reviews are integrated with quarterly performance check-ins and ongoing professional development
+
+#### 8.1.4. Training Content Areas
+
+Required training covers all major policy and operational areas:
+
+- Community values, code of conduct, and foundational principles
+- Staff handbook and professional conduct standards
+- Crisis and mental health management
+- Community support and growth principles
+- Moderation and enforcement procedures
+- Appeals and review processes
+- Privacy and data protection requirements
+- Content moderation and safety protocols
+- Accessibility and inclusion practices
+- Role-specific training materials
+- Legal and policy framework compliance
+
+**Reference to Comprehensive Development Framework**: Additional professional development opportunities, leadership skill enhancement, and ongoing learning resources are set forth in our Community Leadership and Governance Policy, which is incorporated herein by reference.
+
+#### 8.1.4. Ongoing Development Opportunities
 - Leadership coaching and mentorship programmes
 - External training and conference attendance support
 - Cross-functional experience and role advancement opportunities
@@ -483,6 +698,8 @@ All staff members must comply with our complete legal and policy framework:
 
 ### 8.2. Wellness and Support Systems
 
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides a brief overview; refer to the self-care resources document for comprehensive guidance.
+
 #### 8.2.1. Volunteer Wellness Priority
 - Recognition that volunteer well-being is essential for sustainable community service
 - Regular wellness check-ins and proactive intervention when support is needed
@@ -501,7 +718,7 @@ All staff members must comply with our complete legal and policy framework:
 
 This Staff Handbook represents our commitment to maintaining exceptional standards of volunteer leadership that serve our community's mission of fostering safe, welcoming, and inclusive environments. By joining our staff team, you become part of a comprehensive framework designed to support both your personal development and our collective success in community building.
 
-Your service as a volunteer staff member contributes to creating spaces where all community members can thrive, participate meaningfully, and experience genuine belonging. We are grateful for your dedication to this important work.
+Your service as a Team member contributes to creating spaces where all community members can thrive, participate meaningfully, and experience genuine belonging. We are grateful for your dedication to this important work.
 
 ---
 
diff --git a/src/content/docs/staff/hierarchy.md b/src/content/docs/staff/hierarchy.md
index e96fa0e..9d64fe2 100644
--- a/src/content/docs/staff/hierarchy.md
+++ b/src/content/docs/staff/hierarchy.md
@@ -38,6 +38,12 @@ stateDiagram
   stl --> mr
   stl --> ds
   out --> cg
+  mgr --> ac
+  legal --> cs2
+  hr --> crc
+  exec --> sc
+  legal --> hrc
+  exec --> hr
   exec:Executives (CEO, etc.)
   dir:Community Director
   legal:Legal and Policy Advisor
@@ -65,4 +71,10 @@ stateDiagram
   mr:Member Relation Specialist
   ds:Documentation Support Team
   cg:Community Growth Specialist
+  sc: Security Coordinator
+  hrc:Harassment Response Coordinator
+  cs2:Child Safety Coordinator
+  crc:Conflict Resolution Coordinator
+  ac:Appeals Coordinator
+  hr:Human Resources Advisor
 ```
diff --git a/src/content/docs/staff/policy-self-assessment.md b/src/content/docs/staff/policy-self-assessment.md
deleted file mode 100644
index c034a98..0000000
--- a/src/content/docs/staff/policy-self-assessment.md
+++ /dev/null
@@ -1,861 +0,0 @@
----
-title: Staff Policy Self-Assessment
----
-
-**COMPREHENSIVE POLICY KNOWLEDGE ASSESSMENT FOR STAFF**
-
-## Introduction
-
-This self-assessment tool is designed to help you evaluate your understanding and comprehension of our organisation's policies, procedures, and community standards. It covers all major policy areas that staff members are expected to know and apply in their roles.
-
-**How to Use This Assessment:**
-- Answer each question honestly and thoroughly
-- Review relevant policy documents for questions you're unsure about
-- Use this as a learning tool, not just a test
-- Discuss any areas of uncertainty with your supervisor or colleagues
-- Retake sections as needed after reviewing policy materials
-
-**Assessment Areas Covered:**
-1. Community Values and Code of Conduct
-2. Staff Handbook and Professional Conduct
-3. Crisis and Mental Health Management
-4. Community Support and Growth
-5. Moderation and Enforcement
-6. Appeals and Review Processes
-7. Privacy and Data Protection
-8. Content Moderation and Safety
-9. Accessibility and Inclusion
-10. Training-Specific Knowledge
-11. Legal and Policy Framework
-
----
-
-## Section 1: Community Values and Code of Conduct
-
-### 1.1. Foundational Principles
-
-**Question 1:** Our community explicitly rejects neutrality in the face of oppression. Explain what this means and how it should guide your actions as a staff member.
-
-*Your Answer:*
-
----
-
-**Question 2:** List and explain the five core values that guide our community:
-
-*Your Answer:*
-
----
-
-**Question 3:** A community member posts about experiencing discrimination but doesn't provide "proof." How should you respond and why?
-
-*Your Answer:*
-
----
-
-### 1.2. Prohibited Conduct
-
-**Question 4:** What is the difference between impact and intent when assessing harmful behaviour? Provide an example.
-
-*Your Answer:*
-
----
-
-**Question 5:** A user claims they're just "playing devil's advocate" when making arguments that harm marginalised community members. How do you respond?
-
-*Your Answer:*
-
----
-
-**Question 6:** Define microaggressions and provide three examples that might occur in online technical communities.
-
-*Your Answer:*
-
----
-
-### 1.3. Reporting and Enforcement
-
-**Question 7:** List the different ways community members can report Code of Conduct violations:
-
-*Your Answer:*
-
----
-
-**Question 8:** Explain the progressive disciplinary system and when each level is typically applied:
-
-*Your Answer:*
-
----
-
-**Question 9:** Where is our public transparency system located, and what information is documented there?
-
-*Your Answer:*
-
----
-
-## Section 2: Staff Handbook and Professional Conduct
-
-### 2.1. Role Definition and Expectations
-
-**Question 10:** Explain the "servant leadership" principle and how it applies to all staff roles:
-
-*Your Answer:*
-
----
-
-**Question 11:** What should you do if you anticipate being absent from staff duties for more than one week?
-
-*Your Answer:*
-
----
-
-**Question 12:** How do you balance being a staff member while also participating as a regular community member?
-
-*Your Answer:*
-
----
-
-### 2.2. Professional Standards
-
-**Question 13:** List five mandatory behaviours expected of all staff members:
-
-*Your Answer:*
-
----
-
-**Question 14:** What are the key principles for working collaboratively with fellow staff members?
-
-*Your Answer:*
-
----
-
-**Question 15:** If you disagree with a fellow staff member's decision, what should you do?
-
-*Your Answer:*
-
----
-
-### 2.3. Documentation and Accountability
-
-**Question 16:** What types of actions must be documented, and why is this important?
-
-*Your Answer:*
-
----
-
-**Question 17:** Explain how our performance review and accountability systems work:
-
-*Your Answer:*
-
----
-
-## Section 3: Crisis and Mental Health Management
-
-### 3.1. Crisis Recognition
-
-**Question 18:** List at least 5 warning signs that might indicate someone is experiencing a mental health crisis:
-
-*Your Answer:*
-
----
-
-**Question 19:** Explain the three risk assessment levels (High, Medium, Low) and appropriate response timeframes:
-
-*Your Answer:*
-
----
-
-**Question 20:** What should you NEVER do when someone is expressing mental health concerns?
-
-*Your Answer:*
-
----
-
-### 3.2. Response Protocols
-
-**Question 21:** When are we legally obligated to report mental health concerns to authorities?
-
-*Your Answer:*
-
----
-
-**Question 22:** Provide examples of appropriate and inappropriate responses to someone expressing suicidal thoughts:
-
-*Your Answer:*
-
----
-
-**Question 23:** List at least 5 crisis resources that should be readily available:
-
-*Your Answer:*
-
----
-
-### 3.3. Professional Boundaries
-
-**Question 24:** What are the limitations of peer support vs. professional mental health services?
-
-*Your Answer:*
-
----
-
-**Question 25:** How do you maintain appropriate boundaries while still being supportive?
-
-*Your Answer:*
-
----
-
-## Section 4: Community Support and Growth
-
-### 4.1. Community Support Framework
-
-**Question 26:** What are the four main categories of support available in our community?
-
-*Your Answer:*
-
----
-
-**Question 27:** When providing technical support, what information should you include in your response?
-
-*Your Answer:*
-
----
-
-**Question 28:** How do you handle a support request that exceeds your knowledge or capacity?
-
-*Your Answer:*
-
----
-
-### 4.2. Community Growth Principles
-
-**Question 29:** Explain our "quality over quantity" approach to community growth:
-
-*Your Answer:*
-
----
-
-**Question 30:** What does "values-driven growth" mean, and how does it guide outreach efforts?
-
-*Your Answer:*
-
----
-
-**Question 31:** List practices we should avoid when promoting community growth:
-
-*Your Answer:*
-
----
-
-### 4.3. New Member Integration
-
-**Question 32:** Describe the key elements of effective new member onboarding:
-
-*Your Answer:*
-
----
-
-**Question 33:** How do you ensure new members feel welcome while maintaining community standards?
-
-*Your Answer:*
-
----
-
-## Section 5: Moderation and Enforcement
-
-### 5.1. Inclusive Moderation Principles
-
-**Question 34:** What does "inclusive moderation" mean beyond just enforcing written rules?
-
-*Your Answer:*
-
----
-
-**Question 35:** How should you prioritise safety for marginalised community members in your moderation decisions?
-
-*Your Answer:*
-
----
-
-**Question 36:** A user says something that technically doesn't violate written rules but creates an unwelcoming environment. How do you respond?
-
-*Your Answer:*
-
----
-
-### 5.2. Conflict Resolution
-
-**Question 37:** List the four stages of conflict escalation and appropriate interventions for each:
-
-*Your Answer:*
-
----
-
-**Question 38:** When should you use restorative justice approaches vs. enforcement measures?
-
-*Your Answer:*
-
----
-
-**Question 39:** Describe the process for facilitating a discussion between conflicting parties:
-
-*Your Answer:*
-
----
-
-### 5.3. Cultural Competency
-
-**Question 40:** How do cultural differences in communication styles affect moderation decisions?
-
-*Your Answer:*
-
----
-
-**Question 41:** What is "tone policing" and why is it problematic?
-
-*Your Answer:*
-
----
-
-**Question 42:** How do you accommodate different cultural approaches to conflict while maintaining consistent community standards?
-
-*Your Answer:*
-
----
-
-## Section 6: Appeals and Review Processes
-
-### 6.1. Appeals Framework
-
-**Question 43:** What are the acceptable grounds for appealing a disciplinary decision?
-
-*Your Answer:*
-
----
-
-**Question 44:** What must an appellant complete before submitting an appeal?
-
-*Your Answer:*
-
----
-
-**Question 45:** Within what timeframe must appeals be submitted, and where do they go?
-
-*Your Answer:*
-
----
-
-### 6.2. Appeals Process
-
-**Question 46:** Describe the review process and typical timeline for appeals:
-
-*Your Answer:*
-
----
-
-**Question 47:** What are the possible outcomes when an appeal is reviewed?
-
-*Your Answer:*
-
----
-
-**Question 48:** Can someone appeal the same decision multiple times? What are the consequences of abuse of process?
-
-*Your Answer:*
-
----
-
-### 6.3. Review and Accountability
-
-**Question 49:** How do you handle a situation where a community member wants to appeal a decision you made?
-
-*Your Answer:*
-
----
-
-**Question 50:** What documentation should be maintained to support potential appeals processes?
-
-*Your Answer:*
-
----
-
-## Section 7: Privacy and Data Protection
-
-### 7.1. Data Collection and Use
-
-**Question 51:** What types of personal information do we collect from community members?
-
-*Your Answer:*
-
----
-
-**Question 52:** Under what circumstances can staff members access or share community member personal information?
-
-*Your Answer:*
-
----
-
-**Question 53:** How do privacy protections interact with transparency requirements for sanctions and documentation?
-
-*Your Answer:*
-
----
-
-### 7.2. Data Protection Principles
-
-**Question 54:** If a community member requests their personal data be deleted, what should you do?
-
-*Your Answer:*
-
----
-
-**Question 55:** When handling crisis situations, how do you balance privacy with safety obligations?
-
-*Your Answer:*
-
----
-
-**Question 56:** What are the key principles for protecting community member privacy in staff communications?
-
-*Your Answer:*
-
----
-
-## Section 8: Content Moderation and Safety
-
-### 8.1. Content Standards
-
-**Question 57:** Beyond explicit rule violations, what other factors should guide content moderation decisions?
-
-*Your Answer:*
-
----
-
-**Question 58:** How do you handle content that might be harmful to marginalised community members but doesn't explicitly violate written rules?
-
-*Your Answer:*
-
----
-
-**Question 59:** What is your approach to moderating content that involves complex cultural or contextual issues?
-
-*Your Answer:*
-
----
-
-### 8.2. Safety and Protection
-
-**Question 60:** Describe the process for handling reports of harassment that span multiple platforms:
-
-*Your Answer:*
-
----
-
-**Question 61:** How do you protect vulnerable community members while maintaining fair processes for all parties?
-
-*Your Answer:*
-
----
-
-**Question 62:** What steps should you take when content moderation decisions might impact community member safety?
-
-*Your Answer:*
-
----
-
-## Section 9: Accessibility and Inclusion
-
-### 9.1. Accessibility Principles
-
-**Question 63:** What are the key accessibility considerations for community platforms and activities?
-
-*Your Answer:*
-
----
-
-**Question 64:** How do you accommodate different communication styles and needs in your staff interactions?
-
-*Your Answer:*
-
----
-
-**Question 65:** If someone requests accommodations for participation, what is the process for evaluation and implementation?
-
-*Your Answer:*
-
----
-
-### 9.2. Inclusive Practices
-
-**Question 66:** Describe how you ensure that community events and discussions are inclusive of different time zones, languages, and cultural backgrounds:
-
-*Your Answer:*
-
----
-
-**Question 67:** What proactive steps can staff take to create more accessible and inclusive community environments?
-
-*Your Answer:*
-
----
-
-**Question 68:** How do you address barriers that might prevent marginalised community members from fully participating?
-
-*Your Answer:*
-
----
-
-## Section 10: Training-Specific Knowledge
-
-### 10.1. Role-Specific Competencies
-
-**Question 69:** If you're in a moderation role, list the core competencies required for effective conflict resolution:
-
-*Your Answer:*
-
----
-
-**Question 70:** For technical roles, what are the key areas of expertise needed to support community projects?
-
-*Your Answer:*
-
----
-
-**Question 71:** What ongoing training requirements apply to all staff positions?
-
-*Your Answer:*
-
----
-
-### 10.2. Specialized Knowledge Areas
-
-**Question 72:** If working with accessibility coordination, what are the key principles you need to understand?
-
-*Your Answer:*
-
----
-
-**Question 73:** For community growth roles, what are the ethical guidelines for outreach and recruitment?
-
-*Your Answer:*
-
----
-
-**Question 74:** In crisis response situations, what specialised training is required?
-
-*Your Answer:*
-
----
-
-## Section 11: Legal and Policy Framework
-
-### 11.1. Policy Integration
-
-**Question 75:** List the major policy documents that all staff members must understand and comply with:
-
-*Your Answer:*
-
----
-
-**Question 76:** When policies overlap or conflict, how should you determine which takes precedence?
-
-*Your Answer:*
-
----
-
-**Question 77:** How often are policies reviewed and updated, and how are changes communicated?
-
-*Your Answer:*
-
----
-
-### 11.2. Legal Obligations
-
-**Question 78:** What are our mandatory reporting obligations, and when do they apply?
-
-*Your Answer:*
-
----
-
-**Question 79:** How do privacy protections balance with transparency requirements?
-
-*Your Answer:*
-
----
-
-**Question 80:** What should you do if you're unsure about legal obligations in a specific situation?
-
-*Your Answer:*
-
----
-
-## Section 12: Practical Application Scenarios
-
-### 12.1. Complex Situations
-
-**Question 81:** A long-time community member makes transphobic comments. They claim they're "just asking questions" and "trying to understand." How do you handle this situation from first contact through resolution?
-
-*Your Answer:*
-
----
-
-**Question 82:** Two community members from different cultural backgrounds are having a conflict that seems to stem from communication style differences. Both feel misunderstood. Walk through your approach to resolving this.
-
-*Your Answer:*
-
----
-
-**Question 83:** A community member reports that they're feeling suicidal and asks you not to tell anyone. How do you balance their request for confidentiality with safety concerns?
-
-*Your Answer:*
-
----
-
-### 12.2. Edge Cases
-
-**Question 84:** A staff member is involved in a conflict with a community member. You need to address the situation but the usual procedures involve that staff member. What do you do?
-
-*Your Answer:*
-
----
-
-**Question 85:** Someone is promoting their commercial product in community spaces. They argue it's relevant to ongoing discussions and they're contributing value. How do you evaluate and respond?
-
-*Your Answer:*
-
----
-
-**Question 86:** A community member claims that our anti-oppression stance is "political" and they just want a "neutral" technical community. How do you respond?
-
-*Your Answer:*
-
----
-
-**Question 87:** A community member requests deletion of their personal data, but some of that data is part of documented policy violations that affect ongoing community safety. How do you handle this?
-
-*Your Answer:*
-
----
-
-**Question 88:** You notice that accessibility accommodations for an event are inadequate, but implementing proper accommodations would require significant resource changes. How do you approach this?
-
-*Your Answer:*
-
----
-
-## Section 13: Self-Reflection and Continuous Improvement
-
-### 13.1. Personal Assessment
-
-**Question 89:** Reflect on your own potential biases. What areas do you need to be most mindful about in your staff role?
-
-*Your Answer:*
-
----
-
-**Question 90:** What aspects of our policies do you find most challenging to implement, and why?
-
-*Your Answer:*
-
----
-
-**Question 91:** How do you plan to continue learning and improving in your staff role?
-
-*Your Answer:*
-
----
-
-### 13.2. Community Impact
-
-**Question 92:** How would you evaluate whether your actions as a staff member are effectively supporting our community values?
-
-*Your Answer:*
-
----
-
-**Question 93:** What feedback mechanisms are available for community members to assess staff performance?
-
-*Your Answer:*
-
----
-
-**Question 94:** If you received feedback that your approach was causing harm, how would you respond?
-
-*Your Answer:*
-
----
-
-## Section 14: Resource Knowledge
-
-### 14.1. Support Resources
-
-**Question 95:** List key mental health crisis resources for different regions:
-
-*Your Answer:*
-
----
-
-**Question 96:** Where can community members find technical documentation and support for our projects?
-
-*Your Answer:*
-
----
-
-**Question 97:** What resources are available for staff members who need support or consultation?
-
-*Your Answer:*
-
----
-
-### 14.2. External Resources
-
-**Question 98:** If someone needs legal advice, professional counselling, or other services outside our scope, how do you connect them with appropriate resources?
-
-*Your Answer:*
-
----
-
-## Section 15: Advanced Integration and Leadership
-
-### 15.1. Cross-Platform Coordination
-
-**Question 99:** How do you ensure consistent policy application across Discord, forums, Reddit, GitHub, and other community platforms?
-
-*Your Answer:*
-
----
-
-**Question 100:** When a conflict or issue spans multiple platforms, how do you coordinate response and documentation?
-
-*Your Answer:*
-
----
-
-### 15.2. Community Leadership and Governance
-
-**Question 101:** Describe how community feedback is integrated into policy development and modification:
-
-*Your Answer:*
-
----
-
-**Question 102:** What role do staff members play in our democratic governance and community decision-making processes?
-
-*Your Answer:*
-
----
-
-**Question 103:** How do you balance individual staff judgement with consistent policy application across the team?
-
-*Your Answer:*
-
----
-
-### 15.3. Training and Development
-
-**Question 104:** If you were to mentor a new staff member, what would be your approach to helping them understand our policies?
-
-*Your Answer:*
-
----
-
-**Question 105:** How do you stay current with policy updates and integrate new knowledge into your practice?
-
-*Your Answer:*
-
----
-
-**Question 106:** What would you do if you identified a gap in our current policies or training materials?
-
-*Your Answer:*
-
----
-
-### 15.4. Crisis and Emergency Situations
-
-**Question 107:** Describe your approach to handling a community-wide crisis that requires immediate response across multiple platforms:
-
-*Your Answer:*
-
----
-
-**Question 108:** How do you prioritise competing demands during high-stress situations while maintaining policy compliance?
-
-*Your Answer:*
-
----
-
-**Question 109:** What steps would you take if you suspected that another staff member was not following policies appropriately?
-
-*Your Answer:*
-
----
-
-**Question 110:** If you received conflicting guidance from different levels of leadership, how would you handle the situation?
-
-*Your Answer:*
-
----
-
-## Assessment Completion
-
-### Scoring Guide
-
-This is a learning tool rather than a pass/fail test. Use the following guide to evaluate your responses:
-
-**Excellent Understanding (4 points):** Complete, accurate answer that demonstrates deep comprehension and ability to apply knowledge
-
-**Good Understanding (3 points):** Mostly correct answer with minor gaps or areas for improvement
-
-**Basic Understanding (2 points):** Partially correct answer showing some knowledge but requiring further study
-
-**Needs Development (1 point):** Incomplete or incorrect answer indicating need for significant additional learning
-
-**No Understanding (0 points):** No answer provided or completely incorrect response
-
-### Next Steps Based on Your Results
-
-**440-385 points (Excellent Overall):** You demonstrate strong policy knowledge. Focus on continuous learning and practical application.
-
-**384-330 points (Good Overall):** You have solid understanding with some areas for improvement. Review specific sections where you scored lower.
-
-**329-275 points (Basic Overall):** You understand fundamentals but need additional study. Schedule focused review sessions with your supervisor.
-
-**274-220 points (Developing):** Significant gaps in knowledge require structured learning plan and additional training.
-
-**Below 220 points:** Comprehensive policy review needed before independent staff duties.
-
-### Action Planning
-
-Based on your assessment results:
-
-1. **Identify Weak Areas:** Which sections had the lowest scores?
-2. **Create Study Plan:** Schedule time to review relevant policy documents
-3. **Seek Support:** Discuss challenging areas with colleagues or supervisors
-4. **Practice Application:** Look for opportunities to apply knowledge in safe contexts
-5. **Schedule Reassessment:** Plan to retake weak sections after additional study
-
-### Documentation
-
-**Assessment Completion Date:** _______________
-
-**Overall Score:** _______ / 440 points
-
-**Areas for Improvement:**
-
-**Learning Plan:**
-
----
-
-**Supervisor Review**
-
-**Reviewed by:** _______________
-
-**Review Date:** _______________
-
-**Comments:**
-
-**Recommended Actions:**
-
----
-
-*This Policy Self-Assessment is designed to support continuous learning and professional development. It should be completed regularly and used as part of ongoing training and performance development discussions. For questions about specific policy areas or assessment results, contact leadership through designated staff channels.*
\ No newline at end of file
diff --git a/src/content/docs/staff/professional-conduct.md b/src/content/docs/staff/professional-conduct.md
index b1cc821..61af6b3 100644
--- a/src/content/docs/staff/professional-conduct.md
+++ b/src/content/docs/staff/professional-conduct.md
@@ -70,11 +70,11 @@ All volunteers representing our organisation are required to maintain the highes
 
 **(b)** **Conflict Management**: Address conflicts calmly, professionally, and in accordance with established procedures;
 
-**(c)** **Escalation Protocol**: Escalate issues appropriately through established channels when unable to resolve them directly;
+**(c)** **Escalation Protocol**: Escalate issues appropriately through established channels when unable to resolve them directly. For comprehensive escalation procedures, see [Escalation Protocol](/staff/handbook#253-escalation-protocol) in the Staff Handbook;
 
 **(d)** **Impartiality Maintenance**: Maintain strict impartiality when mediating disputes or addressing community issues.
 
-### 3.2. Organizational Representation Standards
+### 3.2. Organisational Representation Standards
 
 **(a)** **Continuous Representation**: Recognise that you represent the organisation at all times during volunteer activities;
 
@@ -184,13 +184,9 @@ All volunteers representing our organisation are required to maintain the highes
 
 ### 6.1. Mandatory Training Requirements
 
-**(a)** **Initial Training**: All volunteers must complete professional conduct training before beginning volunteer activities;
+**IMPORTANT: All staff members are required to complete comprehensive training review and submit confirmation forms. Failure to complete annual training requirements will result in dismissal from staff positions.**
 
-**(b)** **Ongoing Education**: Regular professional development workshops and updates are required;
-
-**(c)** **Specialized Training**: Conflict resolution, cultural competency, and crisis response training is mandatory for relevant positions;
-
-**(d)** **Refresher Courses**: Periodic refresher training on professional conduct standards is required.
+For complete information about mandatory training requirements, including initial onboarding, annual review, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook. This section provides a brief overview; refer to the handbook for comprehensive details.
 
 ### 6.2. Training Content and Curriculum
 
@@ -254,7 +250,7 @@ All volunteers representing our organisation are required to maintain the highes
 
 **(d)** **Leadership Development**: Recognition programmes that support leadership development and career advancement.
 
-### 7.4. Organizational Learning and Adaptation
+### 7.4. Organisational Learning and Adaptation
 
 **(a)** **Lessons Learned**: Integration of lessons learned from conduct issues and their resolution;
 
diff --git a/src/content/docs/staff/roles.md b/src/content/docs/staff/roles.md
index 5bea8a3..07f5f2a 100644
--- a/src/content/docs/staff/roles.md
+++ b/src/content/docs/staff/roles.md
@@ -10,7 +10,9 @@ This document provides comprehensive information about volunteer opportunities w
 
 ### 1.2. Volunteer Philosophy and Principles
 
-Our volunteer programme is built on servant leadership principles:
+Our volunteer programme is built on **servant leadership principles**. For a comprehensive explanation of servant leadership and how it applies to all staff roles, see [Staff Role Definition and Principles](/staff/handbook#22-staff-role-definition-and-principles) in the Staff Handbook.
+
+Key principles include:
 
 **(a)** **Service-Oriented Leadership**: Volunteers serve the community rather than wielding authority for personal benefit;
 
@@ -371,6 +373,213 @@ The Community Growth Specialist develops and implements comprehensive growth str
 - Understanding of community dynamics and member lifecycle management
 - Project management capabilities for executing complex growth initiatives
 
+### 4.9. Security Coordinator (Specialist Leadership)
+
+#### 4.9.1. Role Overview
+The Security Coordinator oversees community security operations, coordinates responses to criminal activity and security threats, and ensures compliance with legal reporting obligations whilst protecting community members and platform integrity.
+
+**Key Responsibilities:**
+- Coordinate responses to criminal activity and security threats within the community
+- Oversee evidence preservation and documentation for security incidents
+- Ensure compliance with legal reporting obligations and mandatory reporting requirements
+- Coordinate with law enforcement and external authorities when necessary
+- Develop and maintain security protocols and emergency response procedures
+- Provide security training and guidance to staff members
+- Monitor for patterns of criminal activity and security threats
+- Coordinate with Technical Administrators on cybersecurity and platform security matters
+- Maintain relationships with external security professionals and legal counsel
+- Document security incidents and maintain security records for legal compliance
+
+#### 4.9.2. Security and Legal Expertise
+**Essential Qualifications:**
+- Understanding of criminal activity recognition and appropriate response procedures
+- Knowledge of legal reporting obligations and mandatory reporting requirements
+- Experience with evidence preservation and documentation procedures
+- Strong understanding of cybersecurity threats and platform security
+- Ability to coordinate with law enforcement and external authorities appropriately
+
+**Preferred Experience:**
+- Professional security or law enforcement background
+- Legal education or paralegal certification
+- Experience with online community security and threat assessment
+- Knowledge of data protection and privacy laws affecting security operations
+- Crisis management and emergency response experience
+
+### 4.10. Harassment Response Coordinator (Specialist Leadership)
+
+#### 4.10.1. Role Overview
+The Harassment Response Coordinator oversees community harassment response operations, coordinates support for harassment victims, and ensures effective enforcement of anti-harassment policies whilst maintaining safe community environments.
+
+**Key Responsibilities:**
+- Coordinate responses to harassment and bullying reports within the community
+- Provide support and resources to harassment victims
+- Ensure consistent enforcement of anti-harassment policies and procedures
+- Coordinate with Crisis Response Coordinator for severe harassment situations
+- Develop and maintain harassment response protocols and victim support procedures
+- Provide harassment response training and guidance to staff members
+- Monitor for patterns of harassment and coordinate preventive measures
+- Coordinate with Legal and Policy Advisor on harassment policy development
+- Maintain relationships with external support resources and advocacy organisations
+- Document harassment incidents and maintain records for accountability and legal compliance
+
+#### 4.10.2. Harassment Response and Victim Support Expertise
+**Essential Qualifications:**
+- Understanding of harassment recognition and appropriate response procedures
+- Experience with victim support and trauma-informed care practices
+- Strong understanding of anti-harassment policies and enforcement procedures
+- Ability to coordinate comprehensive support for harassment victims
+- Knowledge of legal considerations related to harassment and bullying
+
+**Preferred Experience:**
+- Professional background in victim advocacy or support services
+- Training in trauma-informed practices and crisis intervention
+- Experience with online harassment and cyberbullying response
+- Knowledge of harassment laws and legal protections
+- Conflict resolution and mediation experience
+
+### 4.11. Child Safety Coordinator (Specialist Leadership)
+
+#### 4.11.1. Role Overview
+The Child Safety Coordinator oversees community child safety operations, coordinates responses to child safety concerns, and ensures compliance with legal reporting obligations whilst protecting minors and maintaining safe community environments.
+
+**Key Responsibilities:**
+- Coordinate responses to child safety concerns and reports within the community
+- Ensure compliance with legal reporting obligations and mandatory reporting requirements
+- Coordinate with law enforcement and child protection agencies when necessary
+- Develop and maintain child safety protocols and protection procedures
+- Provide child safety training and guidance to staff members
+- Monitor for grooming behaviours and other child safety threats
+- Coordinate age verification and access control measures
+- Coordinate with Security Coordinator on criminal activity involving minors
+- Maintain relationships with external child protection resources and agencies
+- Document child safety incidents and maintain records for legal compliance and accountability
+- Provide support and resources for minors and their families when appropriate
+- Oversee community environments to ensure they are safe for minors
+
+#### 4.11.2. Child Safety and Protection Expertise
+**Essential Qualifications:**
+- Understanding of child safety recognition and appropriate response procedures
+- Knowledge of legal reporting obligations and mandatory reporting requirements
+- Experience with child protection practices and trauma-informed care for minors
+- Strong understanding of grooming behaviours and online safety threats
+- Ability to coordinate comprehensive child safety responses
+- Knowledge of child protection laws and legal requirements
+
+**Preferred Experience:**
+- Professional background in child protection, social work, or related fields
+- Training in child safety, child protection, or youth services
+- Experience with online child safety and cyberbullying response
+- Knowledge of child protection laws and reporting requirements
+- Crisis intervention and trauma-informed care experience with minors
+
+### 4.12. Conflict Resolution Coordinator (Specialist Leadership)
+
+#### 4.12.1. Role Overview
+The Conflict Resolution Coordinator oversees community conflict resolution operations, facilitates mediation and restorative justice processes, and ensures effective resolution of disputes whilst maintaining community relationships and preventing escalation.
+
+**Key Responsibilities:**
+- Coordinate conflict resolution processes for interpersonal, group-level, and authority-based conflicts
+- Facilitate mediation and restorative justice processes for community disputes
+- Develop and maintain conflict resolution protocols and mediation procedures
+- Provide conflict resolution training and guidance to staff members
+- Monitor for early warning signs of conflict escalation and coordinate preventive interventions
+- Coordinate with Head Moderator on conflicts involving moderation decisions
+- Coordinate with Harassment Response Coordinator on conflicts involving harassment
+- Coordinate with Crisis Response Coordinator for conflicts involving mental health or safety concerns
+- Maintain relationships with external mediation resources and conflict resolution professionals
+- Document conflict resolution processes and outcomes for accountability and learning
+- Evaluate conflict resolution effectiveness and implement continuous improvements
+- Support community members in developing conflict resolution skills
+
+#### 4.12.2. Conflict Resolution and Mediation Expertise
+**Essential Qualifications:**
+- Understanding of conflict resolution principles and restorative justice approaches
+- Experience with mediation facilitation and dispute resolution processes
+- Strong communication and active listening skills for conflict facilitation
+- Ability to remain neutral and facilitate constructive dialogue
+- Understanding of trauma-informed conflict resolution practices
+- Knowledge of de-escalation techniques and conflict prevention strategies
+
+**Preferred Experience:**
+- Professional background in mediation, conflict resolution, or dispute resolution
+- Training in restorative justice, mediation, or conflict transformation
+- Experience with online community conflict resolution
+- Knowledge of conflict resolution theory and best practices
+- Experience facilitating difficult conversations and complex disputes
+- Understanding of cultural competency in conflict resolution
+
+### 4.13. Appeals Coordinator (Specialist Leadership)
+
+#### 4.13.1. Role Overview
+The Appeals Coordinator oversees community appeals processes, ensures independent and impartial review of appeals, and maintains accountability and transparency in appeals procedures whilst protecting community member rights.
+
+**Key Responsibilities:**
+- Coordinate appeals processes for moderation actions, disciplinary decisions, and policy applications
+- Ensure independent and impartial review of appeals by appropriate reviewers
+- Develop and maintain appeals procedures and review standards
+- Provide appeals process training and guidance to staff members
+- Coordinate appeals review panels and independent assessment processes
+- Ensure appeals processes are accessible and transparent to community members
+- Coordinate with Legal and Policy Advisor on appeals involving legal or policy questions
+- Coordinate with Head Moderator on appeals of moderation decisions
+- Maintain relationships with external appeals resources and independent reviewers
+- Document appeals processes and outcomes for accountability and transparency
+- Evaluate appeals process effectiveness and implement continuous improvements
+- Ensure appeals processes comply with community policies and legal requirements
+
+#### 4.13.2. Appeals and Review Expertise
+**Essential Qualifications:**
+- Understanding of appeals processes and independent review principles
+- Experience with impartial assessment and review procedures
+- Strong analytical skills for evaluating appeals and evidence
+- Ability to ensure procedural fairness and due process
+- Understanding of community policies and enforcement procedures
+- Knowledge of transparency and accountability requirements
+
+**Preferred Experience:**
+- Professional background in legal review, administrative appeals, or dispute resolution
+- Training in appeals processes, administrative law, or procedural fairness
+- Experience with community governance and accountability systems
+- Knowledge of appeals best practices and procedural standards
+- Experience conducting independent reviews and assessments
+- Understanding of community member rights and protections
+
+### 4.14. Human Resources Advisor (Specialist Leadership)
+
+#### 4.14.1. Role Overview
+The Human Resources Advisor oversees staff recruitment, performance management, staff relations, and staff wellness programmes, ensuring effective staff management practices and supporting volunteer staff development and retention.
+
+**Key Responsibilities:**
+- Coordinate staff recruitment and selection processes, including application review and selection committee coordination
+- Coordinate performance management processes including annual reviews, quarterly check-ins, and performance evaluations
+- Develop and maintain staff relations procedures and internal conflict resolution processes
+- Coordinate staff wellness programmes and burnout prevention initiatives
+- Coordinate staff recognition and appreciation programmes
+- Track staff policy compliance and training completion
+- Coordinate staff onboarding processes in collaboration with Training and Development Coordinator
+- Provide guidance on staff management best practices and volunteer service standards
+- Maintain staff records and documentation for accountability and compliance
+- Coordinate staff exit processes and transition support
+- Evaluate staff management effectiveness and implement continuous improvements
+- Support staff professional development and career advancement pathways
+
+#### 4.14.2. Human Resources and Staff Management Expertise
+**Essential Qualifications:**
+- Understanding of volunteer management and staff relations principles
+- Experience with recruitment, selection, and performance management processes
+- Strong interpersonal and communication skills for staff support
+- Ability to maintain confidentiality and handle sensitive staff matters
+- Understanding of staff wellness and burnout prevention strategies
+- Knowledge of volunteer service standards and best practices
+
+**Preferred Experience:**
+- Professional background in human resources, volunteer management, or staff relations
+- Training in performance management, recruitment, or organisational development
+- Experience with online community staff management
+- Knowledge of volunteer service legal considerations and best practices
+- Experience with staff recognition and appreciation programmes
+- Understanding of staff development and retention strategies
+
 ## 5. Volunteer Leadership Opportunities
 
 ### 5.1. Community Moderators
@@ -515,10 +724,10 @@ Quality Assurance Coordinators ensure the quality and consistency of community p
 ### 5.6. Data and Analytics Coordinator
 
 #### 5.6.1. Role Overview
-Data and Analytics Coordinators collect and analyze community engagement data to provide insights that support leadership decision-making and community improvement initiatives.
+Data and Analytics Coordinators collect and analyse community engagement data to provide insights that support leadership decision-making and community improvement initiatives.
 
 **Key Responsibilities:**
-- Collect and analyze community engagement metrics and participation data
+- Collect and analyse community engagement metrics and participation data
 - Prepare regular reports on community health, growth trends, and member satisfaction
 - Manage community surveys and feedback analysis for leadership decision-making
 - Support leadership team with data insights and trend identification
@@ -610,7 +819,7 @@ Member Relations Specialists focus on fostering positive relationships within th
 - Monitor member satisfaction and engagement levels across the community
 - Mediate minor conflicts and facilitate communication between members
 - Collect member feedback and suggestions for community improvements
-- Maintain positive relationships and foster sense of belonging among community members
+- Maintain positive relationships and foster sense of belonging amongst community members
 
 #### 6.4.2. Relationship Building Skills
 **Required Experience:**
diff --git a/src/content/docs/staff/self-care-resources.md b/src/content/docs/staff/self-care-resources.md
new file mode 100644
index 0000000..23e3042
--- /dev/null
+++ b/src/content/docs/staff/self-care-resources.md
@@ -0,0 +1,453 @@
+---
+title: Self-Care Resources for Staff
+---
+
+**ESSENTIAL RESOURCE FOR ALL STAFF MEMBERS**
+
+## 1. INTRODUCTION AND PURPOSE
+
+### 1.1. Why Self-Care Matters
+
+Staff work in online communities can be emotionally demanding, involving exposure to conflict, crisis situations, harassment, trauma, and community distress. Effective self-care is essential for:
+
+- **Sustainable Service**: Maintaining long-term ability to serve the community effectively
+- **Personal Well-Being**: Protecting your own mental health and emotional wellness
+- **Quality Service**: Ensuring you can provide high-quality support when community members need it
+- **Preventing Burnout**: Avoiding compassion fatigue and emotional exhaustion
+- **Professional Boundaries**: Maintaining appropriate boundaries between work and personal life
+
+### 1.2. Self-Care Is Not Selfish
+
+Self-care is not selfish or indulgent—it is a professional responsibility. Taking care of yourself enables you to take better care of others. When you prioritise your well-being, you can:
+
+- Respond more effectively to community needs
+- Make better decisions under pressure
+- Maintain empathy and compassion
+- Avoid making mistakes due to exhaustion or stress
+- Model healthy boundaries for community members
+
+## 2. UNDERSTANDING THE EMOTIONAL IMPACT OF STAFF WORK
+
+### 2.1. Common Emotional Challenges
+
+**Secondary Trauma (Vicarious Trauma):**
+- Emotional and psychological impact of exposure to others' trauma
+- Can occur from supporting community members experiencing crisis, harassment, or abuse
+- Symptoms may include anxiety, sadness, emotional numbness, intrusive thoughts
+
+**Compassion Fatigue:**
+- Emotional exhaustion from caring for others
+- Reduced ability to feel empathy or compassion
+- Feeling overwhelmed by others' suffering
+- Difficulty separating work from personal life
+
+**Burnout:**
+- Physical, emotional, and mental exhaustion
+- Feelings of cynicism or detachment
+- Reduced sense of accomplishment
+- Loss of motivation or interest in work
+
+**Emotional Labour:**
+- Managing your own emotions whilst supporting others
+- Maintaining professional composure in difficult situations
+- Balancing empathy with boundaries
+
+### 2.2. Warning Signs
+
+**Physical Symptoms:**
+- Fatigue, exhaustion, or difficulty sleeping
+- Headaches, tension, or physical pain
+- Changes in appetite or eating patterns
+- Difficulty concentrating or making decisions
+
+**Emotional Symptoms:**
+- Anxiety, irritability, or mood swings
+- Feelings of sadness, hopelessness, or numbness
+- Difficulty experiencing joy or pleasure
+- Increased sensitivity or emotional reactivity
+
+**Professional Symptoms:**
+- Decreased effectiveness or quality of work
+- Avoidance of difficult situations or responsibilities
+- Cynicism or negative attitude towards community members
+- Difficulty maintaining professional boundaries
+
+**Personal Symptoms:**
+- Relationship strain or social withdrawal
+- Loss of interest in activities you used to enjoy
+- Difficulty separating work from personal life
+- Feeling overwhelmed or unable to cope
+
+## 3. SELF-CARE STRATEGIES
+
+### 3.1. Physical Self-Care
+
+**Rest and Sleep:**
+- Prioritise adequate sleep (7-9 hours per night)
+- Establish consistent sleep schedule
+- Create relaxing bedtime routine
+- Avoid screens before bed
+- Take breaks during work sessions
+
+**Exercise and Movement:**
+- Regular physical activity (even short walks help)
+- Stretching or yoga for stress relief
+- Outdoor activities when possible
+- Movement breaks during long work sessions
+
+**Nutrition and Hydration:**
+- Regular, balanced meals
+- Stay hydrated throughout the day
+- Limit caffeine and alcohol
+- Avoid skipping meals due to work
+
+**Medical Care:**
+- Regular medical check-ups
+- Address physical health concerns promptly
+- Take prescribed medications as directed
+- Don't ignore physical symptoms
+
+### 3.2. Emotional Self-Care
+
+**Emotional Awareness:**
+- Regular check-ins with your emotional state
+- Identify and name your feelings
+- Recognise emotional triggers
+- Notice patterns in your emotional responses
+
+**Emotional Processing:**
+- Journaling about difficult experiences
+- Talking with trusted friends or colleagues
+- Professional counselling or therapy when needed
+- Creative expression (art, music, writing)
+
+**Stress Management:**
+- Deep breathing exercises
+- Meditation or mindfulness practices
+- Progressive muscle relaxation
+- Grounding techniques for anxiety
+
+**Emotional Boundaries:**
+- Set clear limits on work time and availability
+- Learn to say "no" when overwhelmed
+- Don't take responsibility for others' emotions
+- Separate your identity from your staff role
+
+### 3.3. Professional Self-Care
+
+**Work-Life Balance:**
+- Set clear boundaries between work and personal time
+- Designate specific times for staff work
+- Take regular breaks and days off
+- Don't check staff channels during personal time
+
+**Workload Management:**
+- Recognise when you're taking on too much
+- Communicate workload concerns to supervisors
+- Delegate or share responsibilities when appropriate
+- Say no to additional commitments when overwhelmed
+
+**Professional Development:**
+- Continue learning and skill development
+- Attend training and professional development opportunities
+- Seek feedback and support from colleagues
+- Celebrate successes and accomplishments
+
+**Professional Boundaries:**
+- Maintain appropriate boundaries with community members
+- Don't provide professional services beyond your role
+- Recognise limitations and refer when appropriate
+- Avoid over-investing emotionally in individual situations
+
+### 3.4. Social Self-Care
+
+**Supportive Relationships:**
+- Maintain connections with friends and family
+- Build relationships outside of staff work
+- Spend time with people who support and energize you
+- Avoid relationships that drain or stress you
+
+**Peer Support:**
+- Connect with other staff members for mutual support
+- Participate in staff debriefing sessions
+- Share experiences and learn from colleagues
+- Build supportive relationships within the staff team
+
+**Community Engagement:**
+- Participate in community activities as a regular member
+- Engage in hobbies and interests outside of staff work
+- Build relationships with community members as peers
+- Maintain social connections beyond staff responsibilities
+
+**Social Boundaries:**
+- Don't feel obligated to be available 24/7
+- Take time away from community spaces when needed
+- Maintain personal relationships separate from staff work
+- Protect your personal time and space
+
+### 3.5. Mental and Cognitive Self-Care
+
+**Mental Stimulation:**
+- Engage in activities that challenge and interest you
+- Continue learning and intellectual growth
+- Pursue hobbies and interests
+- Read, study, or engage in creative activities
+
+**Mental Rest:**
+- Take breaks from mentally demanding work
+- Practice mindfulness or meditation
+- Engage in activities that don't require intense focus
+- Allow your mind to rest and recharge
+
+**Perspective Maintenance:**
+- Remember the positive impact of your work
+- Focus on what you can control
+- Accept limitations and imperfections
+- Maintain realistic expectations
+
+**Cognitive Boundaries:**
+- Don't ruminate on difficult situations
+- Set limits on how much you think about work
+- Practice letting go of things outside your control
+- Focus on present moment rather than worrying about future
+
+## 4. CONTEXT-SPECIFIC SELF-CARE CONSIDERATIONS
+
+### 4.1. Crisis Response Work
+
+**Additional Considerations:**
+- Increased risk of secondary trauma from exposure to crisis situations
+- Need for immediate debriefing after difficult crisis responses
+- Regular check-ins with Crisis Response Coordinator
+- Access to professional mental health support
+- Clear boundaries about when to step back from crisis work
+
+**Self-Care Practices:**
+- Debrief immediately after crisis situations
+- Limit exposure to crisis content when possible
+- Take breaks between crisis responses
+- Use grounding techniques when feeling overwhelmed
+- Access professional support when needed
+
+### 4.2. Harassment Response Work
+
+**Additional Considerations:**
+- Exposure to harmful content and behaviour
+- Risk of secondary trauma from supporting victims
+- Need for emotional support and validation
+- Importance of maintaining boundaries with perpetrators
+- Regular supervision and support
+
+**Self-Care Practices:**
+- Limit exposure to harmful content when possible
+- Take breaks after reviewing harassment reports
+- Connect with supportive colleagues
+- Practice self-compassion and validation
+- Access trauma-informed support resources
+
+### 4.3. Child Safety Work
+
+**Additional Considerations:**
+- High emotional impact of child safety concerns
+- Risk of secondary trauma from exposure to grooming or abuse
+- Need for professional support and supervision
+- Importance of maintaining professional boundaries
+- Regular debriefing and support
+
+**Self-Care Practices:**
+- Mandatory debriefing after child safety incidents
+- Access to professional counselling or support
+- Clear boundaries between work and personal life
+- Regular supervision and support from Child Safety Coordinator
+- Practice self-compassion and recognise emotional impact
+
+### 4.4. Moderation and Conflict Resolution Work
+
+**Additional Considerations:**
+- Exposure to conflict and difficult interactions
+- Emotional labour of managing others' emotions
+- Need for patience and emotional regulation
+- Importance of maintaining neutrality and boundaries
+- Regular support and skill development
+
+**Self-Care Practices:**
+- Take breaks between difficult moderation actions
+- Practice de-escalation techniques for yourself
+- Connect with colleagues for support and debriefing
+- Maintain perspective on your role and limitations
+- Celebrate successful resolutions and positive outcomes
+
+## 5. SUPPORT SYSTEMS AND RESOURCES
+
+### 5.1. Internal Support Systems
+
+**Peer Support:**
+- Regular check-ins with other staff members
+- Staff debriefing sessions after difficult situations
+- Peer mentoring and support relationships
+- Team meetings focused on support and wellness
+- Mutual aid and assistance amongst staff
+
+**Supervisory Support:**
+- Regular meetings with supervisors to discuss challenges
+- Access to additional resources and support
+- Workload management and distribution
+- Recognition of difficult work and contributions
+- Professional development opportunities
+
+**Leadership Support:**
+- Access to leadership team for guidance and support
+- Clear communication channels for concerns
+- Supportive response to requests for help
+- Recognition and appreciation for contributions
+- Flexible arrangements for personal circumstances
+
+### 5.2. Professional Resources
+
+**Mental Health Support:**
+- Access to counselling and mental health resources
+- Employee assistance programs (if available)
+- Support groups for professionals in similar roles
+- Trauma-informed therapy resources
+- Crisis support when needed
+
+**Professional Development:**
+- Training on self-care and wellness
+- Education on secondary trauma and burnout prevention
+- Skills development for managing difficult situations
+- Access to professional resources and networks
+- Career development support
+
+### 5.3. External Resources
+
+**Crisis Support:**
+- National Suicide Prevention Lifeline: 988 (US)
+- Crisis Text Line: Text HOME to 741741 (US)
+- Samaritans: 116 123 (UK)
+- Local crisis support services
+
+**Mental Health Resources:**
+- Psychology Today therapist directory
+- BetterHelp online therapy
+- Local community mental health centres
+- Support groups and peer support networks
+
+**Professional Support:**
+- Professional associations and networks
+- Online communities for community managers
+- Training and conference opportunities
+- Mentorship and coaching resources
+
+## 6. RECOGNISING WHEN YOU NEED HELP
+
+### 6.1. Signs You May Need Additional Support
+
+**Seek Professional Help If You Experience:**
+- Persistent feelings of depression, anxiety, or hopelessness
+- Difficulty functioning in daily life
+- Thoughts of self-harm or suicide
+- Substance use to cope with stress
+- Significant changes in sleep, appetite, or energy
+- Inability to separate work from personal life
+- Persistent physical symptoms without medical cause
+- Relationship problems related to work stress
+
+### 6.2. How to Get Help
+
+**Internal Resources:**
+- Contact your supervisor or leadership team
+- Reach out to Crisis Response Coordinator
+- Access staff support channels
+- Request workload adjustments or time off
+
+**External Resources:**
+- Contact mental health professionals
+- Access crisis support services
+- Join support groups
+- Seek professional counselling or therapy
+
+**Emergency Situations:**
+- If you are in immediate danger, contact emergency services (911, 999, 112, 000)
+- If you are having thoughts of self-harm, contact crisis support immediately
+- Don't hesitate to seek help—your well-being is important
+
+## 7. PREVENTING BURNOUT
+
+### 7.1. Early Warning Signs
+
+**Recognise Early Signs:**
+- Feeling tired or exhausted more often
+- Difficulty concentrating or making decisions
+- Increased irritability or emotional reactivity
+- Loss of interest in work or activities
+- Physical symptoms (headaches, tension, sleep problems)
+- Feeling overwhelmed or unable to cope
+- Withdrawing from social activities or relationships
+
+### 7.2. Prevention Strategies
+
+**Proactive Measures:**
+- Regular self-assessment of stress levels and well-being
+- Consistent self-care practices
+- Clear boundaries between work and personal life
+- Regular breaks and time off
+- Workload management and balance
+- Supportive relationships and connections
+- Professional development and growth
+
+**Early Intervention:**
+- Address warning signs promptly
+- Communicate concerns to supervisors
+- Adjust workload or responsibilities when needed
+- Take time off when necessary
+- Access support resources early
+- Don't wait until burnout is severe
+
+## 8. MAINTAINING LONG-TERM WELLNESS
+
+### 8.1. Sustainable Practices
+
+**Build Sustainable Habits:**
+- Integrate self-care into daily routines
+- Make self-care a priority, not an afterthought
+- Regular check-ins with yourself about well-being
+- Adjust practices as needs change
+- Celebrate progress and positive changes
+
+**Long-Term Strategies:**
+- Develop diverse self-care practices
+- Build strong support networks
+- Maintain work-life balance
+- Continue learning and growth
+- Regular professional development
+- Periodic assessment of work satisfaction and well-being
+
+### 8.2. Community and Organisational Support
+
+**How the Organisation Supports You:**
+- Flexible volunteer arrangements
+- Recognition and appreciation systems
+- Professional development opportunities
+- Access to support resources
+- Clear boundaries and expectations
+- Supportive leadership and supervision
+
+**Your Role in Supporting Others:**
+- Model healthy self-care practices
+- Support colleagues who may be struggling
+- Participate in team support activities
+- Share resources and strategies
+- Create supportive team culture
+
+---
+
+## COMMITMENT TO STAFF WELL-BEING
+
+Your well-being is essential to your ability to serve the community effectively. Self-care is not optional—it is a professional responsibility and organisational priority. We are committed to supporting your wellness and providing resources to help you maintain sustainable, effective service.
+
+If you are struggling, please reach out. Support is available, and seeking help is a sign of strength, not weakness.
+
+---
+
+*This Self-Care Resources document is part of our comprehensive staff support system. For questions about self-care resources or to access support, please contact leadership through designated staff channels or reach out to your supervisor.*
+
diff --git a/src/content/docs/staff/training/accessibility-coordination.md b/src/content/docs/staff/training/accessibility-coordination.md
index 9f5bdcf..de8931a 100644
--- a/src/content/docs/staff/training/accessibility-coordination.md
+++ b/src/content/docs/staff/training/accessibility-coordination.md
@@ -2,13 +2,13 @@
 title: Accessibility Coordination Training for Staff
 ---
 
-**SPECIALIZED TRAINING FOR ACCESSIBILITY COORDINATORS**
+**SPECIALISED TRAINING FOR ACCESSIBILITY COORDINATORS**
 
 ## 1. INTRODUCTION AND SCOPE
 
 ### 1.1. Purpose and Mission
 
-This training provides comprehensive guidance for staff members serving as Accessibility Coordinators within our community ecosystem. Accessibility coordination is fundamental to our organisational commitment to creating inclusive spaces that welcome and empower individuals with disabilities and diverse accessibility needs.
+This training provides comprehensive guidance for Team members serving as Accessibility Coordinators within our community ecosystem. Accessibility coordination is fundamental to our organisational commitment to creating inclusive spaces that welcome and empower individuals with disabilities and diverse accessibility needs.
 
 ### 1.2. Role Definition and Importance
 
@@ -20,7 +20,7 @@ This training provides comprehensive guidance for staff members serving as Acces
 - **Policy Development**: Developing and maintaining accessibility policies and procedures
 - **Technology Assessment**: Evaluating and improving the accessibility of community technology platforms
 
-### 1.3. Integration with Organizational Values
+### 1.3. Integration with Organisational Values
 
 **Accessibility as Social Justice:**
 - **Disability Rights**: Understanding disability as a social justice issue and advocating for disability rights
@@ -128,7 +128,7 @@ This training provides comprehensive guidance for staff members serving as Acces
 
 ### 3.2. Assistive Technology Compatibility
 
-#### 3.2.1. Screen Reader Optimization
+#### 3.2.1. Screen Reader Optimisation
 
 **Screen Reader Testing:**
 - **NVDA**: Free, open-source screen reader testing
@@ -303,7 +303,7 @@ This training provides comprehensive guidance for staff members serving as Acces
 
 #### 6.1.2. Advanced Accessibility Training
 
-**Specialized Skills Development:**
+**Specialised Skills Development:**
 - **Accessibility Testing**: Training on accessibility testing methods and tools
 - **Accommodation Coordination**: Skills in coordinating and implementing accommodations
 - **Policy Development**: Training on developing and implementing accessibility policies
@@ -417,7 +417,7 @@ This training provides comprehensive guidance for staff members serving as Acces
 
 **Community Impact Assessment:**
 - **Culture Change**: Assessment of changes in community culture regarding disability and accessibility
-- **Awareness Growth**: Evaluation of increased disability awareness among community members
+- **Awareness Growth**: Evaluation of increased disability awareness amongst community members
 - **Leadership Development**: Development of disabled community members as leaders
 - **Systemic Change**: Assessment of systemic changes that improve accessibility
 
@@ -445,73 +445,59 @@ This training provides comprehensive guidance for staff members serving as Acces
 - **Best Practice Sharing**: Sharing accessibility best practices with broader community
 - **Industry Leadership**: Leadership in accessibility within our industry and community sector
 
-## 9. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 9. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 9.1. Accessibility Coordinator Competencies
+### 9.1. Scenario 1: Accommodation Request
 
-#### 9.1.1. Essential Knowledge and Skills
+**Situation**: A community member with a visual disability requests accommodations to participate in community activities. They need content in alternative formats, screen reader compatibility, and modifications to how information is presented. You're not sure what's possible or how to implement accommodations.
 
-**Accessibility Expertise:**
-- **Legal Knowledge**: Thorough understanding of accessibility laws, regulations, and standards
-- **Technical Skills**: Ability to assess and improve digital accessibility across platforms
-- **Accommodation Coordination**: Skills in coordinating and implementing individual accommodations
-- **Policy Development**: Experience developing and implementing accessibility policies
+**Your Response:**
+1. How do you approach this accommodation request?
+2. How do you determine what accommodations are reasonable and possible?
+3. How do you work collaboratively with the community member?
+4. How do you coordinate with technical teams?
+5. How do you implement accommodations?
+6. How do you ensure accommodations are effective?
 
-**Advocacy and Leadership:**
-- **Disability Rights Understanding**: Deep understanding of disability rights and social justice
-- **Community Engagement**: Skills in meaningfully engaging disabled community members
-- **Training and Education**: Ability to provide effective accessibility training and education
-- **Systemic Change**: Understanding of how to create systemic change for accessibility
+**Correct Answer**: Approach with respect and collaboration, work with community member to understand specific needs, consult with technical and accessibility teams, explore multiple accommodation options, implement accommodations promptly, test with community member using their assistive technology, provide ongoing support and adjustments.
 
-#### 9.1.2. Professional Development
+### 9.2. Scenario 2: Accessibility Barrier Report
 
-**Certification and Credentials:**
-- **Accessibility Certifications**: Relevant professional certifications in accessibility (CPACC, WAS, etc.)
-- **Continuing Education**: Ongoing education in accessibility best practices and emerging standards
-- **Professional Networks**: Active participation in accessibility professional communities
-- **Conference Participation**: Regular participation in accessibility conferences and training
+**Situation**: Multiple community members report accessibility barriers on the platform. Some barriers affect screen reader users, others affect keyboard navigation, and some affect users with cognitive disabilities. The barriers are preventing full participation.
 
-**Skill Development:**
-- **Technical Training**: Regular training on accessibility testing tools and methods
-- **Legal Updates**: Staying current with changes in accessibility laws and regulations
-- **Community Engagement**: Developing skills in community engagement and participatory design
-- **Leadership Development**: Building leadership skills for accessibility advocacy and change
+**Your Response:**
+1. How do you prioritise addressing these barriers?
+2. How do you assess the impact of each barrier?
+3. How do you coordinate fixes across different teams?
+4. How do you communicate progress to affected community members?
+5. How do you prevent future barriers?
+6. How do you ensure comprehensive accessibility?
 
-### 9.2. Training and Assessment
+**Correct Answer**: Prioritise based on impact and number of users affected, assess each barrier's impact on participation, coordinate with technical teams for fixes, communicate progress transparently, implement accessibility testing processes, involve disabled community members in testing, ensure comprehensive accessibility improvements.
 
-#### 9.2.1. Progressive Competency Development
+### 9.3. Scenario 3: Universal Design Implementation
 
-**Foundation Level:**
-- **Disability Awareness**: Basic understanding of disability culture and rights
-- **Accessibility Principles**: Understanding of universal design and accessibility principles
-- **Legal Basics**: Basic knowledge of accessibility laws and requirements
-- **Community Values**: Integration of accessibility with organisational mission and values
+**Situation**: The community is planning a new feature that will be used by all members. You want to ensure it's accessible from the start rather than retrofitting accessibility later.
 
-**Intermediate Level:**
-- **Technical Assessment**: Ability to conduct basic accessibility assessments
-- **Accommodation Coordination**: Skills in coordinating individual accommodations
-- **Training Delivery**: Ability to provide basic accessibility training to staff and community
-- **Policy Implementation**: Experience implementing accessibility policies and procedures
+**Your Response:**
+1. How do you integrate accessibility from the beginning?
+2. How do you involve disabled community members in design?
+3. How do you ensure universal design principles are followed?
+4. How do you test for accessibility during development?
+5. How do you coordinate with design and development teams?
+6. How do you ensure the feature is accessible to all?
 
-**Advanced Level:**
-- **Strategic Leadership**: Leadership in accessibility strategy and long-term planning
-- **Complex Problem Solving**: Ability to solve complex accessibility challenges
-- **Community Advocacy**: Leadership in disability rights advocacy and systemic change
-- **Innovation Development**: Development of innovative accessibility solutions and approaches
+**Correct Answer**: Integrate accessibility from design phase, involve disabled community members as co-designers, apply universal design principles, conduct accessibility testing throughout development, coordinate closely with all teams, ensure feature works for all users including those using assistive technologies, test comprehensively before launch.
 
-#### 9.2.2. Performance Standards
+## 10. TRAINING REQUIREMENTS
 
-**Effectiveness Measures:**
-- **Accessibility Improvement**: Measurable improvement in community accessibility over time
-- **Community Satisfaction**: High satisfaction among disabled community members
-- **Staff Development**: Successful development of accessibility knowledge and skills among staff
-- **Legal Compliance**: Consistent compliance with accessibility laws and standards
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
 
-**Professional Standards:**
-- **Ethical Practice**: Adherence to ethical standards in accessibility work
-- **Community Accountability**: Accountability to disabled community members and their needs
-- **Continuous Learning**: Commitment to ongoing learning and professional development
-- **Innovation and Excellence**: Striving for excellence and innovation in accessibility practice
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/bias-recognition-mitigation.md b/src/content/docs/staff/training/bias-recognition-mitigation.md
new file mode 100644
index 0000000..ecf76ad
--- /dev/null
+++ b/src/content/docs/staff/training/bias-recognition-mitigation.md
@@ -0,0 +1,659 @@
+---
+title: Bias Recognition and Mitigation Training for Staff
+---
+
+**ESSENTIAL TRAINING FOR ALL MODERATION STAFF**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides essential guidance for Team members on recognising, understanding, and mitigating personal biases in moderation decisions. Everyone has biases—conscious and unconscious—that can affect how we interpret situations and make decisions. This training helps Team members develop self-awareness and implement practices to ensure fair, consistent moderation that serves all community members equitably.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive moderation and inclusion framework:
+
+**(a)** **Inclusive Moderation Policy**: Principles for moderation that considers impact on marginalised community members;
+
+**(b)** **Community Code of Conduct**: Behavioural expectations and social justice principles;
+
+**(c)** **Content and Moderation Policy**: Enforcement procedures and content standards;
+
+**(d)** **Conflict Resolution Policy**: Procedures for resolving disputes fairly;
+
+**(e)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Critical Understanding
+
+**Everyone Has Biases:**
+- Having biases doesn't make you a bad person
+- Biases are natural cognitive shortcuts
+- Recognising biases is the first step to mitigating them
+- The goal is awareness and mitigation, not perfection
+- Ongoing self-reflection and growth are essential
+
+**Our Commitment:**
+- We commit to recognising and addressing our biases
+- We prioritise fairness and equity in moderation
+- We support each other in bias recognition and mitigation
+- We create systems to reduce bias impact
+- We continuously learn and improve
+
+## 2. UNDERSTANDING BIAS
+
+### 2.1. What Is Bias?
+
+#### 2.1.1. Definition and Types
+
+**Bias** is a tendency, inclination, or prejudice towards or against something or someone. Biases can be:
+- **Conscious**: Aware of the bias and its influence
+- **Unconscious**: Not aware of the bias but still influenced by it
+- **Implicit**: Automatic associations that affect judgements
+- **Explicit**: Conscious beliefs and attitudes
+
+**Types of Bias:**
+- **Confirmation Bias**: Tendency to seek information that confirms existing beliefs
+- **Affinity Bias**: Preference for people similar to ourselves
+- **Halo Effect**: Positive impression in one area influences overall impression
+- **Horns Effect**: Negative impression in one area influences overall impression
+- **Anchoring Bias**: Relying too heavily on first piece of information
+- **Availability Bias**: Overestimating probability of events we can easily recall
+- **Attribution Bias**: Explaining others' behaviour differently than our own
+
+#### 2.1.2. How Bias Affects Moderation
+
+**Decision-Making Impact:**
+- Biases can influence how we interpret situations
+- Biases affect who we believe and how seriously we take reports
+- Biases influence what we consider "normal" or "acceptable"
+- Biases affect how we assess severity and impact
+- Biases influence consequences we assign
+
+**Community Impact:**
+- Biased moderation creates unfair experiences
+- Marginalised community members often face more bias
+- Bias can reinforce systemic oppression
+- Bias undermines community trust and safety
+- Bias creates barriers to participation
+
+### 2.2. Sources of Bias
+
+#### 2.2.1. Personal Experiences and Background
+
+**Life Experiences:**
+- Our personal experiences shape our perspectives
+- Cultural background influences what we consider normal
+- Education and exposure affect our understanding
+- Personal relationships influence our judgements
+- Past experiences create expectations and assumptions
+
+**Identity Factors:**
+- Our own identities affect how we perceive others
+- Privilege can create blind spots
+- Marginalization can create different perspectives
+- Intersectional identities create complex perspectives
+- Personal experiences with discrimination vary
+
+#### 2.2.2. Cognitive Processes
+
+**Mental Shortcuts:**
+- Our brains use shortcuts to process information quickly
+- These shortcuts can lead to biased conclusions
+- We often don't recognise when shortcuts are inaccurate
+- Stress and fatigue increase reliance on shortcuts
+- Familiar patterns feel safer than unfamiliar ones
+
+**Social Influences:**
+- We're influenced by social groups and communities
+- Media and cultural messages shape our perceptions
+- Social norms affect what we consider acceptable
+- Peer pressure can influence our judgements
+- Authority figures can shape our perspectives
+
+## 3. RECOGNISING PERSONAL BIASES
+
+### 3.1. Self-Reflection and Awareness
+
+#### 3.1.1. Self-Assessment Techniques
+
+**Regular Self-Reflection:**
+- **Journaling**: Regular reflection on moderation decisions
+- **Pattern Analysis**: Looking for patterns in your decisions
+- **Feedback Seeking**: Actively seeking feedback from others
+- **Case Review**: Reviewing past cases for bias indicators
+- **Questioning Assumptions**: Regularly questioning your assumptions
+
+**Bias Indicators:**
+- Consistently interpreting situations in similar ways
+- Having strong emotional reactions to certain topics or people
+- Making quick judgements without full information
+- Defensiveness when bias is pointed out
+- Difficulty understanding others' perspectives
+
+#### 3.1.2. Common Bias Patterns in Moderation
+
+**Identity-Based Biases:**
+- Treating reports from certain groups less seriously
+- Interpreting behaviour differently based on identity
+- Assuming intent based on identity
+- Applying different standards to different groups
+- Failing to recognise privilege and power dynamics
+
+**Communication Style Biases:**
+- Preferring certain communication styles
+- Interpreting tone differently based on identity
+- Assuming meaning based on style rather than content
+- Dismissing concerns expressed in certain ways
+- Valuing certain forms of expression over others
+
+**Relationship Biases:**
+- Treating friends or familiar members differently
+- Being harder on people you don't like
+- Giving benefit of doubt to certain people
+- Assuming good intent from certain people
+- Assuming bad intent from certain people
+
+### 3.2. Recognising Bias in Decisions
+
+#### 3.2.1. Decision-Making Patterns
+
+**Warning Signs of Bias:**
+- Making decisions very quickly without reflection
+- Strong emotional reactions influencing decisions
+- Inconsistent application of policies
+- Different standards for similar situations
+- Difficulty explaining reasoning for decisions
+
+**Pattern Recognition:**
+- Review decisions for patterns over time
+- Look for differences in how you treat different groups
+- Identify situations where you make assumptions
+- Notice when you feel defensive about decisions
+- Recognise when you're making exceptions
+
+#### 3.2.2. Feedback and External Perspective
+
+**Seeking Feedback:**
+- Ask colleagues to review your decisions
+- Request feedback from diverse perspectives
+- Participate in peer review processes
+- Welcome constructive criticism
+- Learn from others' perspectives
+
+**Using External Perspective:**
+- Consult with colleagues on difficult cases
+- Get second opinions on decisions
+- Use team discussions to challenge assumptions
+- Learn from case studies and examples
+- Participate in bias training and discussions
+
+## 4. COMMON BIASES IN MODERATION
+
+### 4.1. Identity-Based Biases
+
+#### 4.1.1. Racial and Ethnic Bias
+
+**Common Patterns:**
+- Interpreting behaviour differently based on race or ethnicity
+- Assuming intent based on racial or ethnic identity
+- Applying different standards to different racial groups
+- Failing to recognise racial microaggressions
+- Dismissing concerns about racism
+
+**Mitigation Strategies:**
+- Educate yourself about racial bias and microaggressions
+- Question assumptions about behaviour based on race
+- Listen to and believe experiences of people of colour
+- Recognise your own racial privilege and blind spots
+- Consult with diverse perspectives on racial issues
+
+#### 4.1.2. Gender and Sexuality Bias
+
+**Common Patterns:**
+- Interpreting behaviour differently based on gender
+- Assuming intent based on gender identity or expression
+- Applying different standards based on gender
+- Failing to recognise gender-based harassment
+- Dismissing concerns about sexism or transphobia
+
+**Mitigation Strategies:**
+- Educate yourself about gender bias and discrimination
+- Question assumptions about behaviour based on gender
+- Listen to and believe experiences of marginalised genders
+- Recognise your own gender privilege and blind spots
+- Use inclusive language and respect identities
+
+#### 4.1.3. Disability and Neurodivergence Bias
+
+**Common Patterns:**
+- Interpreting behaviour through ableist lens
+- Assuming intent based on disability or neurodivergence
+- Applying neurotypical standards to all behaviour
+- Failing to recognise ableist discrimination
+- Dismissing accessibility concerns
+
+**Mitigation Strategies:**
+- Educate yourself about disability and neurodivergence
+- Question assumptions about "normal" behaviour
+- Listen to and believe experiences of disabled people
+- Recognise your own ableist assumptions
+- Consider accessibility and accommodation needs
+
+### 4.2. Cognitive Biases
+
+#### 4.2.1. Confirmation Bias
+
+**How It Manifests:**
+- Seeking information that confirms initial impression
+- Interpreting ambiguous information to support conclusion
+- Dismissing information that contradicts initial assessment
+- Remembering cases that support your perspective
+- Overvaluing evidence that confirms beliefs
+
+**Mitigation Strategies:**
+- Actively seek disconfirming evidence
+- Consider alternative interpretations
+- Question initial impressions
+- Review all evidence before deciding
+- Consult with others who may see things differently
+
+#### 4.2.2. Affinity Bias
+
+**How It Manifests:**
+- Preferring people similar to yourself
+- Giving benefit of doubt to similar people
+- Being harder on people different from you
+- Assuming good intent from similar people
+- Assuming bad intent from different people
+
+**Mitigation Strategies:**
+- Recognise when you feel affinity with someone
+- Question whether affinity is influencing decisions
+- Apply consistent standards regardless of similarity
+- Seek diverse perspectives on decisions
+- Build relationships with diverse community members
+
+#### 4.2.3. Anchoring Bias
+
+**How It Manifests:**
+- Relying too heavily on first information received
+- Difficulty adjusting assessment with new information
+- First impression strongly influences final decision
+- Giving disproportionate weight to initial report
+- Struggling to change mind even with new evidence
+
+**Mitigation Strategies:**
+- Gather comprehensive information before deciding
+- Reassess decisions as new information emerges
+- Question initial impressions
+- Consider multiple perspectives
+- Be willing to change assessment with new evidence
+
+## 5. MITIGATION STRATEGIES
+
+### 5.1. Individual Mitigation Practices
+
+#### 5.1.1. Self-Awareness Practices
+
+**Regular Reflection:**
+- **Daily Reflection**: Brief reflection on decisions made
+- **Weekly Review**: Review of decisions for patterns
+- **Monthly Analysis**: Deeper analysis of bias patterns
+- **Annual Assessment**: Comprehensive bias self-assessment
+- **Ongoing Learning**: Continuous education about bias
+
+**Questioning Practices:**
+- **Why Questions**: Why do I think this? Why do I feel this way?
+- **What If Questions**: What if I'm wrong? What if I'm missing something?
+- **How Questions**: How might someone else see this? How might my bias affect this?
+- **Who Questions**: Who benefits from this decision? Who might be harmed?
+
+#### 5.1.2. Decision-Making Practices
+
+**Structured Decision-Making:**
+- **Gather Information**: Collect comprehensive information before deciding
+- **Consider Alternatives**: Actively consider alternative interpretations
+- **Check Assumptions**: Identify and question your assumptions
+- **Seek Perspective**: Consult with others for different perspectives
+- **Document Reasoning**: Write down your reasoning to identify bias
+
+**Bias-Checking Questions:**
+- Would I interpret this differently if the person had different identity?
+- Am I making assumptions based on identity or background?
+- Am I applying consistent standards?
+- What would someone with different perspective think?
+- Am I being influenced by personal feelings or relationships?
+
+### 5.2. Team and System Mitigation
+
+#### 5.2.1. Peer Review and Consultation
+
+**Peer Review Processes:**
+- Regular peer review of moderation decisions
+- Structured review processes for difficult cases
+- Diverse perspectives in review teams
+- Constructive feedback and discussion
+- Learning from review processes
+
+**Consultation Practices:**
+- Consult with colleagues on difficult cases
+- Seek diverse perspectives before deciding
+- Use team discussions to challenge assumptions
+- Learn from others' approaches and perspectives
+- Build collective understanding
+
+#### 5.2.2. Systematic Approaches
+
+**Structured Processes:**
+- Standardized decision-making frameworks
+- Checklists to ensure comprehensive consideration
+- Documentation requirements that reveal reasoning
+- Review processes that catch bias
+- Appeals processes that provide checks
+
+**Diversity and Inclusion:**
+- Diverse moderation teams
+- Regular bias training and discussions
+- Inclusive decision-making processes
+- Community input and feedback
+- Continuous improvement based on outcomes
+
+## 6. CULTURAL COMPETENCY AND BIAS
+
+### 6.1. Understanding Cultural Differences
+
+#### 6.1.1. Cultural Bias Patterns
+
+**Common Cultural Biases:**
+- Assuming your cultural norms are universal
+- Interpreting behaviour through your cultural lens
+- Dismissing cultural differences as "wrong"
+- Failing to recognise cultural context
+- Applying monocultural standards
+
+**Impact on Moderation:**
+- Misinterpreting cultural communication styles
+- Applying inappropriate cultural standards
+- Failing to recognise cultural discrimination
+- Creating exclusionary environments
+- Harming cultural community members
+
+#### 6.1.2. Developing Cultural Competency
+
+**Learning Practices:**
+- Educate yourself about different cultures
+- Learn about cultural communication styles
+- Understand cultural context and history
+- Recognise your own cultural assumptions
+- Build relationships with diverse cultural communities
+
+**Application in Moderation:**
+- Consider cultural context in decisions
+- Recognise cultural communication differences
+- Apply culturally appropriate standards
+- Support cultural community members
+- Create inclusive cultural environments
+
+### 6.2. Language and Communication Bias
+
+#### 6.2.1. Language-Based Biases
+
+**Common Patterns:**
+- Preferring native English speakers
+- Interpreting tone differently based on language proficiency
+- Dismissing concerns expressed in non-native English
+- Assuming meaning based on language proficiency
+- Applying different standards to language use
+
+**Mitigation Strategies:**
+- Recognise language proficiency differences
+- Consider language barriers in communication
+- Provide language support when needed
+- Don't assume intent based on language proficiency
+- Support non-native English speakers
+
+#### 6.2.2. Communication Style Biases
+
+**Style Differences:**
+- Direct vs. indirect communication styles
+- High-context vs. low-context communication
+- Emotional expression differences
+- Formality level differences
+- Nonverbal communication differences
+
+**Mitigation Strategies:**
+- Recognise different communication styles
+- Don't assume meaning based on style
+- Consider cultural communication differences
+- Adapt your communication style when needed
+- Support diverse communication styles
+
+## 7. INTERSECTIONALITY AND BIAS
+
+### 7.1. Understanding Intersectionality
+
+#### 7.1.1. Intersectional Bias
+
+**Multiple Identities:**
+- People have multiple intersecting identities
+- Bias can affect people differently based on intersections
+- Some intersections face compounded bias
+- Intersectional experiences are unique
+- Need to consider intersections in moderation
+
+**Common Intersectional Biases:**
+- Failing to recognise intersectional experiences
+- Applying single-identity lens to intersectional people
+- Dismissing intersectional discrimination
+- Assuming experiences based on single identity
+- Missing intersectional power dynamics
+
+#### 7.1.2. Intersectional Moderation
+
+**Consideration Practices:**
+- Consider multiple identities in decisions
+- Recognise intersectional power dynamics
+- Support intersectional community members
+- Address intersectional discrimination
+- Create inclusive intersectional environments
+
+### 7.2. Power Dynamics and Bias
+
+#### 7.2.1. Recognising Power Imbalances
+
+**Power Factors:**
+- Staff vs. community member status
+- Established vs. new member status
+- Popular vs. less popular members
+- Privileged vs. marginalised identities
+- Technical expertise and knowledge
+
+**Bias in Power Dynamics:**
+- Favouring powerful over less powerful
+- Believing powerful over less powerful
+- Applying different standards based on power
+- Failing to recognise power abuse
+- Reinforcing power imbalances
+
+#### 7.2.2. Addressing Power Bias
+
+**Mitigation Strategies:**
+- Recognise power dynamics in situations
+- Question whether power is influencing decisions
+- Support less powerful community members
+- Hold powerful members accountable
+- Create systems that reduce power bias
+
+## 8. PRACTICAL APPLICATION
+
+### 8.1. Bias-Checking in Moderation Decisions
+
+#### 8.1.1. Decision-Making Framework
+
+**Before Making Decision:**
+1. **Gather Information**: Collect comprehensive information
+2. **Identify Assumptions**: List your assumptions
+3. **Question Assumptions**: Challenge your assumptions
+4. **Consider Alternatives**: Think of alternative interpretations
+5. **Check for Bias**: Use bias-checking questions
+6. **Consult Others**: Get diverse perspectives
+7. **Make Decision**: Make informed, bias-checked decision
+8. **Document Reasoning**: Write down your reasoning
+9. **Review Later**: Review decision for bias patterns
+
+#### 8.1.2. Case Study Analysis
+
+**Reviewing Cases for Bias:**
+- **Pattern Analysis**: Look for patterns in your decisions
+- **Identity Analysis**: Consider how identity affected decisions
+- **Consistency Check**: Ensure consistent standards
+- **Impact Assessment**: Assess impact on different groups
+- **Learning Integration**: Learn from analysis for future
+
+### 8.2. Ongoing Improvement
+
+#### 8.2.1. Continuous Learning
+
+**Learning Practices:**
+- Regular bias training and education
+- Reading about bias and discrimination
+- Participating in discussions about bias
+- Learning from case studies and examples
+- Seeking feedback and learning from mistakes
+
+**Skill Development:**
+- Developing self-awareness skills
+- Building cultural competency
+- Improving decision-making processes
+- Enhancing consultation and collaboration
+- Strengthening bias mitigation practices
+
+#### 8.2.2. Community Feedback Integration
+
+**Feedback Collection:**
+- Regular community feedback on moderation
+- Surveys and assessments
+- Direct feedback from community members
+- Analysis of moderation outcomes
+- Identification of bias patterns
+
+**Improvement Integration:**
+- Use feedback to identify bias issues
+- Adjust practices based on feedback
+- Communicate improvements to community
+- Continue monitoring and improvement
+- Build trust through demonstrated improvement
+
+## 9. SELF-CARE AND GROWTH
+
+### 9.1. Managing the Emotional Aspects
+
+#### 9.1.1. Emotional Challenges
+
+**Common Emotions:**
+- **Defensiveness**: Feeling defensive when bias is pointed out
+- **Guilt**: Feeling guilty about having biases
+- **Shame**: Feeling ashamed of biased decisions
+- **Frustration**: Frustration with ongoing bias work
+- **Overwhelm**: Feeling overwhelmed by bias recognition
+
+**Normalizing Emotions:**
+- These emotions are normal and expected
+- Having biases doesn't make you a bad person
+- Recognising bias is growth, not failure
+- Ongoing work is part of the process
+- Support is available for this work
+
+#### 9.1.2. Growth Mindset
+
+**Embracing Growth:**
+- View bias recognition as learning opportunity
+- See mistakes as chances to grow
+- Welcome feedback as gift
+- Commit to continuous improvement
+- Celebrate progress and growth
+
+### 9.2. Support Systems
+
+#### 9.2.1. Team Support
+
+**Peer Support:**
+- Regular discussions about bias with colleagues
+- Sharing experiences and learning together
+- Supporting each other in bias recognition
+- Creating safe space for growth
+- Celebrating progress together
+
+**Supervisory Support:**
+- Regular check-ins with supervisors
+- Access to resources and training
+- Support for bias recognition work
+- Recognition of growth and improvement
+- Professional development opportunities
+
+#### 9.2.2. Professional Resources
+
+**External Support:**
+- Bias training and workshops
+- Books and resources on bias
+- Professional development opportunities
+- Communities of practice
+- Counselling and support when needed
+
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 10.1. Scenario 1: Cultural Communication Difference
+
+**Situation**: You're reviewing a moderation case. The person involved is from a cultural background different from yours, and their communication style seems "rude" or "aggressive" to you based on your cultural norms. However, you're not sure if this is a cultural communication difference or an actual policy violation.
+
+**Your Response:**
+1. How do you assess whether this is a cultural difference or a violation?
+2. What bias-checking questions should you ask yourself?
+3. Who should you consult before making a decision?
+4. How do you ensure you're not applying your cultural standards unfairly?
+5. What factors do you consider in your decision?
+
+**Correct Answer**: Consider cultural context, recognise your own cultural assumptions, consult with colleagues familiar with the culture, assess actual policy violation rather than communication style, apply consistent standards regardless of cultural background, document reasoning clearly.
+
+### 10.2. Scenario 2: Pattern Recognition
+
+**Situation**: During a quarterly review of your moderation decisions, you notice a pattern: you consistently give warnings to people you know well or who are similar to you, but issue suspensions to people you don't know for similar violations.
+
+**Your Response:**
+1. What type of bias might this indicate?
+2. How do you investigate this pattern?
+3. What steps do you take to address this bias?
+4. How do you ensure consistency going forward?
+5. How do you document this self-reflection?
+
+**Correct Answer**: This indicates possible affinity bias. Review decisions objectively, identify patterns, seek peer review, apply consistent standards regardless of familiarity, use bias-checking questions before decisions, document self-reflection and improvement efforts.
+
+### 10.3. Scenario 3: Receiving Bias Feedback
+
+**Situation**: A community member points out that your moderation decision seems biased. They explain why they believe your decision was influenced by bias. You initially feel defensive and think they're wrong.
+
+**Your Response:**
+1. How do you manage your defensive reaction?
+2. What steps do you take to review the decision?
+3. How do you use bias-checking questions?
+4. Who do you consult for peer review?
+5. How do you respond to the community member?
+6. What do you do if you discover bias in your decision?
+
+**Correct Answer**: Acknowledge defensive reaction, thank them for feedback, review decision objectively using bias-checking questions, seek peer review from diverse perspectives, correct decision if bias found, communicate transparently, learn and improve practices.
+
+## 11. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Bias Recognition and Mitigation Training document is part of our comprehensive staff development programme designed to ensure fair, equitable moderation that serves all community members. Bias recognition and mitigation is ongoing work that requires commitment, self-reflection, and continuous improvement. For questions about bias recognition or to report training completion, please contact designated leadership through staff channels.*
+
diff --git a/src/content/docs/staff/training/child-safety.md b/src/content/docs/staff/training/child-safety.md
new file mode 100644
index 0000000..db5866f
--- /dev/null
+++ b/src/content/docs/staff/training/child-safety.md
@@ -0,0 +1,534 @@
+---
+title: Child Safety Training for Staff
+---
+
+**MANDATORY TRAINING FOR ALL TEAM MEMBERS**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides essential guidance for all Team members on recognising, responding to, and managing child safety concerns within our community. Child safety is our highest priority, and all Team members must be prepared to respond appropriately to any situation involving minors or potential child safety risks.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive safety and protection framework:
+
+**(a)** **Community Code of Conduct**: Behavioural expectations and community safety standards;
+
+**(b)** **Content and Moderation Policy**: Enforcement procedures and content restrictions;
+
+**(c)** **Crisis Response Policy**: Emergency response procedures for safety concerns;
+
+**(d)** **Staff Handbook**: General staff responsibilities and expectations;
+
+**(e)** **Legal Compliance Requirements**: Mandatory reporting obligations and legal responsibilities.
+
+### 1.3. Critical Disclaimer
+
+**REMEMBER: WE ARE NOT CHILD PROTECTION PROFESSIONALS**
+
+- We cannot conduct investigations or make determinations about child safety
+- Our role is limited to recognition, immediate response, and appropriate escalation
+- We must maintain clear professional boundaries at all times
+- When in doubt, escalate immediately to senior staff and appropriate authorities
+- Legal reporting obligations may require immediate action regardless of uncertainty
+
+## 2. UNDERSTANDING CHILD SAFETY IN ONLINE COMMUNITIES
+
+### 2.1. Types of Child Safety Concerns
+
+#### 2.1.1. Direct Safety Threats (IMMEDIATE ACTION REQUIRED)
+
+**Physical Safety Threats:**
+- Direct threats of harm to minors
+- Grooming behaviours targeting minors
+- Attempts to arrange in-person meetings with minors
+- Requests for personal information from minors (addresses, school names, etc.)
+- Sharing of inappropriate content with minors
+
+**Online Safety Threats:**
+- Attempts to move conversations to private platforms
+- Requests for photos or videos from minors
+- Pressure to keep conversations secret
+- Requests for personal identifying information
+- Attempts to isolate minors from support systems
+
+#### 2.1.2. Content Safety Concerns (ESCALATE WITHIN 15 MINUTES)
+
+**Inappropriate Content:**
+- Sexual content shared with or by minors
+- Age-inappropriate discussions initiated by adults
+- Requests for inappropriate content from minors
+- Sharing of adult content in spaces accessible to minors
+- Inappropriate language or topics directed at minors
+
+**Boundary Violations:**
+- Adults forming inappropriate relationships with minors
+- Excessive private messaging between adults and minors
+- Adults attempting to become "friends" with minors inappropriately
+- Sharing personal adult problems or issues with minors
+- Attempts to gain inappropriate influence over minors
+
+#### 2.1.3. Environmental Safety Concerns (RESPOND WITHIN 1 HOUR)
+
+**Unsafe Community Environments:**
+- Spaces where minors are exposed to harmful content
+- Lack of appropriate moderation in minor-accessible areas
+- Inadequate age verification or protection measures
+- Environments where grooming behaviours could occur unnoticed
+- Insufficient reporting mechanisms for minors
+
+**Policy and Process Gaps:**
+- Missing or inadequate child safety policies
+- Insufficient staff training on child safety
+- Lack of clear reporting procedures
+- Inadequate response to previous child safety concerns
+- Gaps in age verification or access controls
+
+### 2.2. Recognising Grooming Behaviours
+
+#### 2.2.1. Grooming Indicators
+
+**Early Stage Grooming:**
+- Adults seeking out and initiating contact with minors
+- Compliments and flattery designed to build trust
+- Finding common interests to create connection
+- Offering special attention or privileges
+- Attempts to become a "trusted friend" or "mentor"
+
+**Escalation Patterns:**
+- Moving conversations to private channels
+- Requesting personal information gradually
+- Testing boundaries with increasingly inappropriate content
+- Creating secrets and asking minors to keep things private
+- Isolating minors from their support systems
+
+**Advanced Grooming:**
+- Explicit requests for photos, videos, or personal information
+- Attempts to arrange in-person meetings
+- Threats or manipulation if the minor doesn't comply
+- Requests for sexual content or conversations
+- Attempts to normalize inappropriate behaviour
+
+#### 2.2.2. Red Flags and Warning Signs
+
+**Communication Patterns:**
+- Adults who primarily interact with minors rather than peers
+- Excessive private messaging between adults and specific minors
+- Adults who seem to have many "young friends"
+- Conversations that seem inappropriate for the relationship
+- Adults who become defensive when questioned about interactions with minors
+
+**Behavioural Indicators:**
+- Attempts to bypass community safety measures
+- Requests to use platforms with less oversight
+- Attempts to discourage minors from reporting concerns
+- Adults who seem overly interested in minors' personal lives
+- Patterns of boundary-testing behaviour
+
+## 3. IMMEDIATE RESPONSE PROCEDURES
+
+### 3.1. Direct Safety Threat Response Protocol
+
+**IMMEDIATE ACTIONS (Within 5 minutes):**
+
+1. **DO NOT DELAY** - Child safety concerns require immediate action
+2. **PRESERVE EVIDENCE** - Screenshot all relevant communications immediately
+3. **ESCALATE IMMEDIATELY** - Notify senior staff and child safety coordinator in staff chat
+4. **DO NOT CONFRONT** - Do not directly confront suspected perpetrators
+5. **PROTECT THE MINOR** - Ensure the minor is safe and supported
+6. **DOCUMENT EVERYTHING** - Record all relevant information whilst it's fresh
+
+**Example Response Template:**
+```
+URGENT CHILD SAFETY CONCERN
+
+[Brief description of concern]
+[User IDs involved]
+[Platform/channel where incident occurred]
+[Time and date]
+[Screenshots attached]
+
+Escalating immediately to child safety coordinator and senior staff.
+```
+
+### 3.2. Content Safety Concern Response Protocol
+
+**ACTIONS (Within 15 minutes):**
+
+1. **REMOVE CONTENT** - Immediately remove inappropriate content from public view
+2. **PRESERVE EVIDENCE** - Document and preserve all relevant content
+3. **PROTECT MINORS** - Ensure affected minors are safe and supported
+4. **ESCALATE** - Notify child safety coordinator and senior staff
+5. **DOCUMENT** - Create comprehensive documentation of the incident
+6. **FOLLOW UP** - Ensure appropriate follow-up actions are taken
+
+**Example Response Template:**
+```
+"I've identified inappropriate content involving minors. I've removed the content from public view and preserved evidence. I'm escalating this to our child safety coordinator immediately. The affected minors are being contacted to ensure their safety and provide support."
+```
+
+### 3.3. Environmental Safety Concern Response Protocol
+
+**ACTIONS (Within 1 hour):**
+
+1. **ASSESS RISK** - Evaluate the level of risk to minors
+2. **IMPLEMENT PROTECTIONS** - Take immediate steps to protect minors
+3. **DOCUMENT CONCERNS** - Record all identified safety gaps
+4. **ESCALATE** - Report concerns to senior staff and child safety coordinator
+5. **DEVELOP SOLUTIONS** - Work with team to address identified gaps
+6. **MONITOR** - Ensure improvements are effective
+
+## 4. LEGAL OBLIGATIONS AND REPORTING REQUIREMENTS
+
+### 4.1. Mandatory Reporting Obligations
+
+#### 4.1.1. When Reporting Is Required
+
+**Legal Requirements:**
+- **Suspected Abuse or Neglect**: Any reasonable suspicion of child abuse or neglect
+- **Grooming Behaviours**: Any suspected grooming or predatory behaviour targeting minors
+- **Inappropriate Content**: Distribution of inappropriate content involving minors
+- **Exploitation**: Any suspected exploitation of minors
+- **Immediate Danger**: Any situation where a minor appears to be in immediate danger
+
+**Jurisdictional Considerations:**
+- Reporting requirements vary by jurisdiction
+- Some jurisdictions require reporting by all adults
+- Some jurisdictions have specific requirements for organisations
+- When in doubt, consult with legal counsel and report
+- Multiple jurisdictions may require reporting to multiple agencies
+
+#### 4.1.2. How to Report
+
+**Internal Reporting:**
+1. **Immediate Escalation**: Notify child safety coordinator and senior staff immediately
+2. **Documentation**: Provide comprehensive documentation of concerns
+3. **Follow Procedures**: Follow established internal reporting procedures
+4. **Coordination**: Coordinate with other Team members as appropriate
+
+**External Reporting:**
+- **Child Protection Services**: Report to appropriate child protection agency
+- **Law Enforcement**: Report to law enforcement when criminal activity is suspected
+- **National Center for Missing & Exploited Children (NCMEC)**: Report online exploitation through CyberTipline
+- **Platform Reporting**: Report to platform administrators when appropriate
+- **Legal Counsel**: Consult with legal counsel for guidance on reporting obligations
+
+### 4.2. Documentation Requirements
+
+#### 4.2.1. Essential Information to Document
+
+**Incident Details:**
+- **Date and Time**: Exact date and time of incident or discovery
+- **Platform and Location**: Where the incident occurred
+- **Parties Involved**: All user IDs and any known identifying information
+- **Content**: Screenshots, logs, and descriptions of all relevant content
+- **Actions Taken**: All actions taken in response to the incident
+
+**Context Information:**
+- **Historical Context**: Any previous interactions or concerns involving the parties
+- **Witnesses**: Any other staff or community members who witnessed the incident
+- **Minor Information**: Age of minor(s) involved (if known) and any safety concerns
+- **Risk Assessment**: Assessment of immediate and ongoing risk to minors
+- **Follow-up Plans**: Planned follow-up actions and monitoring
+
+#### 4.2.2. Privacy and Confidentiality
+
+**Protecting Minors:**
+- **Minimize Disclosure**: Share information only on a need-to-know basis
+- **Secure Storage**: Store all documentation securely and access-controlled
+- **Anonymization**: Use anonymization when sharing for training or improvement purposes
+- **Consent Considerations**: Consider minor and guardian consent when appropriate
+
+**Legal Requirements:**
+- **Retention Policies**: Follow legal requirements for document retention
+- **Access Controls**: Limit access to authorized personnel only
+- **Legal Holds**: Preserve documentation when legal action is possible
+- **Confidentiality**: Maintain confidentiality whilst fulfilling reporting obligations
+
+## 5. ESCALATION PROCEDURES
+
+**Reference to Comprehensive Escalation Procedures**: For universal escalation principles and general escalation procedures, see [Escalation Protocol](/staff/handbook#253-escalation-protocol) in the Staff Handbook. This section provides child-safety-specific escalation steps.
+
+### 5.1. When to Escalate
+
+**ALWAYS ESCALATE IMMEDIATELY:**
+- Any direct safety threat to a minor
+- Any suspected grooming behaviour
+- Any inappropriate content involving minors
+- Any situation where a minor appears to be in immediate danger
+- Any request for personal information from a minor by an adult
+- Any attempt to arrange in-person meetings with minors
+- Any situation where you feel uncertain about appropriate response
+
+### 5.2. How to Escalate
+
+**Internal Escalation:**
+1. **Staff Chat Alert**: Post urgent alert in staff chat with @child-safety-coordinator
+2. **Direct Contact**: Contact child safety coordinator directly if available
+3. **Senior Staff Notification**: Notify senior staff and leadership immediately
+4. **Documentation**: Provide all documentation and context immediately
+5. **Follow Instructions**: Follow any specific directions from senior staff
+
+**Emergency Escalation:**
+- **Immediate Danger**: Contact emergency services if minor is in immediate physical danger
+- **@Naomi Alert**: Alert @Naomi immediately for critical situations
+- **Legal Counsel**: Consult legal counsel for guidance on reporting obligations
+- **External Authorities**: Report to appropriate child protection or law enforcement agencies
+
+### 5.3. Escalation Chain
+
+**Standard Escalation:**
+1. Child Safety Coordinator
+2. Senior Staff / Leadership
+3. Legal Counsel (if needed)
+4. External Authorities (as required by law)
+
+**Emergency Escalation:**
+1. Emergency Services (if immediate physical danger)
+2. Child Safety Coordinator
+3. Senior Staff / Leadership
+4. Legal Counsel
+5. External Authorities
+
+## 6. COMMUNICATION WITH MINORS AND FAMILIES
+
+### 6.1. Communicating with Minors
+
+#### 6.1.1. Supportive Communication
+
+**Do's:**
+- **Believe and Validate**: Believe minors who report concerns and validate their experiences
+- **Reassure Safety**: Reassure minors that their safety is the priority
+- **Explain Process**: Explain what will happen next in age-appropriate language
+- **Provide Support**: Connect minors with appropriate support resources
+- **Maintain Boundaries**: Maintain appropriate professional boundaries
+
+**Don'ts:**
+- **Don't Investigate**: Do not attempt to conduct your own investigation
+- **Don't Promise Outcomes**: Do not promise specific outcomes or consequences
+- **Don't Minimise**: Do not minimise concerns or suggest they're overreacting
+- **Don't Blame**: Do not suggest the minor did anything wrong
+- **Don't Share Details**: Do not share details about actions taken against others
+
+#### 6.1.2. Age-Appropriate Communication
+
+**Younger Minors (Under 13):**
+- Use simple, clear language
+- Focus on safety and support
+- Avoid graphic details
+- Emphasise that they did the right thing by reporting
+- Involve guardians/parents as appropriate
+
+**Teenagers (13-17):**
+- Respect their autonomy whilst ensuring safety
+- Provide clear information about what will happen
+- Offer choices when appropriate
+- Connect with appropriate support resources
+- Respect privacy whilst maintaining safety
+
+### 6.2. Communicating with Families
+
+#### 6.2.1. When and How to Contact Families
+
+**When to Contact:**
+- When a minor reports a safety concern
+- When inappropriate content involving a minor is discovered
+- When grooming behaviour targeting a minor is suspected
+- When legal reporting requirements mandate family notification
+- When a minor requests family involvement
+
+**How to Contact:**
+- **Respect Privacy**: Respect minor and family privacy preferences when possible
+- **Clear Communication**: Provide clear, factual information about concerns
+- **Support Resources**: Connect families with appropriate support resources
+- **Follow Legal Requirements**: Follow legal requirements for family notification
+- **Professional Boundaries**: Maintain professional boundaries in all communications
+
+#### 6.2.2. Supporting Families
+
+**Information Provision:**
+- Provide clear information about what happened
+- Explain what actions are being taken
+- Share available support resources
+- Answer questions within appropriate boundaries
+- Provide ongoing updates as appropriate
+
+**Resource Connection:**
+- Connect families with child protection resources
+- Provide information about reporting to authorities
+- Share resources for supporting minors who have experienced harm
+- Connect with mental health resources if needed
+- Provide information about online safety resources
+
+## 7. PREVENTION STRATEGIES
+
+### 7.1. Community Safety Measures
+
+#### 7.1.1. Age Verification and Access Controls
+
+**Age Verification:**
+- Implement appropriate age verification measures
+- Clearly mark spaces intended for adults only
+- Restrict adult-only content to verified adult spaces
+- Provide clear age-appropriate spaces for minors
+- Regularly review and update age verification processes
+
+**Access Controls:**
+- Limit private messaging between adults and minors
+- Monitor interactions in minor-accessible spaces
+- Implement reporting mechanisms easily accessible to minors
+- Provide clear safety information for minors
+- Regularly audit access controls and safety measures
+
+#### 7.1.2. Moderation and Monitoring
+
+**Proactive Moderation:**
+- Active moderation in all minor-accessible spaces
+- Regular monitoring of interactions involving minors
+- Pattern recognition for grooming behaviours
+- Quick response to inappropriate content
+- Regular safety audits of community spaces
+
+**Community Education:**
+- Provide age-appropriate online safety education for minors
+- Educate community members about appropriate interactions with minors
+- Share information about recognising and reporting grooming behaviours
+- Provide resources for parents and guardians
+- Regular community reminders about safety policies
+
+### 7.2. Staff Training and Preparedness
+
+#### 7.2.1. Ongoing Training
+
+**Regular Updates:**
+- Quarterly child safety training updates
+- Regular review of grooming behaviour indicators
+- Updates on legal reporting requirements
+- Training on new platforms and safety features
+- Case study reviews and learning sessions
+
+**Skill Development:**
+- Recognition of grooming behaviours
+- Appropriate response procedures
+- Documentation best practices
+- Communication with minors and families
+- Legal compliance and reporting
+
+#### 7.2.2. Policy and Process Improvement
+
+**Continuous Improvement:**
+- Regular review of child safety policies
+- Updates based on new threats and patterns
+- Improvement of reporting and response procedures
+- Enhancement of prevention measures
+- Integration of community feedback
+
+## 8. SELF-CARE AND EMOTIONAL SUPPORT
+
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides child-safety-specific considerations; refer to the self-care resources document for comprehensive guidance.
+
+### 8.1. Child Safety-Specific Self-Care Considerations
+
+#### 8.1.1. Understanding the Impact
+
+**Additional Considerations for Child Safety Work:**
+- High emotional impact of child safety concerns
+- Risk of secondary trauma from exposure to grooming or abuse
+- Need for professional support and supervision
+- Importance of maintaining professional boundaries
+- Regular debriefing and support
+
+**Self-Care Practices:**
+- Mandatory debriefing after child safety incidents
+- Access to professional counselling or support
+- Clear boundaries between work and personal life
+- Regular supervision and support from Child Safety Coordinator
+- Practice self-compassion and recognise emotional impact
+
+### 8.2. Support Systems
+
+#### 8.2.1. Team Support
+
+**Peer Support:**
+- Regular check-ins with colleagues working on child safety
+- Debriefing sessions after difficult incidents
+- Sharing successful strategies and lessons learned
+- Mutual support and understanding
+- Celebration of positive outcomes
+
+**Supervisory Support:**
+- Regular meetings with supervisors to discuss challenges
+- Access to additional resources and support
+- Workload management and distribution
+- Recognition of difficult work
+- Professional development opportunities
+
+#### 8.2.2. Professional Resources
+
+**Mental Health Support:**
+- Access to counselling and mental health resources
+- Support groups for professionals working in child safety
+- Trauma-informed therapy resources
+- Crisis support when needed
+- Ongoing mental health maintenance
+
+**Professional Development:**
+- Training on trauma-informed practices
+- Education on secondary trauma and burnout prevention
+- Skills development for managing difficult situations
+- Access to professional resources and networks
+- Career development support
+
+## 9. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 9.1. Scenario 1: Suspected Grooming Behaviour
+
+**Situation**: You notice an adult community member frequently private messaging a 15-year-old member. The adult has been asking personal questions about the minor's school, friends, and family. The adult recently asked the minor to keep their conversations "just between us."
+
+**Your Response:**
+1. What risk level is this?
+2. What immediate actions should you take?
+3. What evidence should you preserve?
+4. Who should you escalate to?
+5. How would you communicate with the minor?
+
+**Correct Answer**: High-risk situation requiring immediate escalation. Preserve all evidence, notify child safety coordinator immediately, and ensure the minor is supported whilst maintaining appropriate boundaries.
+
+### 9.2. Scenario 2: Inappropriate Content Discovery
+
+**Situation**: A community member reports finding inappropriate sexual content in a channel accessible to minors. The content appears to have been shared by an adult member who may not have realised minors could access the channel.
+
+**Your Response:**
+1. What immediate actions are required?
+2. How do you protect minors who may have seen the content?
+3. What documentation is needed?
+4. What follow-up actions are necessary?
+5. How do you prevent similar incidents?
+
+### 9.3. Scenario 3: Minor Reporting Concern
+
+**Situation**: A 14-year-old community member contacts you privately to report that an adult member has been asking them for photos and trying to get them to move their conversation to a different platform. The minor is scared but doesn't want to "get anyone in trouble."
+
+**Your Response:**
+1. How do you support and reassure the minor?
+2. What immediate safety actions are needed?
+3. How do you handle the minor's concerns about reporting?
+4. What evidence needs to be preserved?
+5. What reporting obligations exist?
+
+## 10. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Child Safety Training document is part of our comprehensive Team development programme designed to ensure the highest level of protection for minors in our community. Child safety is our highest priority, and all Team members must complete this training before assuming moderation responsibilities. For questions about child safety procedures or to report training completion, please contact the Child Safety Coordinator through designated Team channels.*
+
diff --git a/src/content/docs/staff/training/community-growth-specialist.md b/src/content/docs/staff/training/community-growth-specialist.md
index 35c1013..d7cab8a 100644
--- a/src/content/docs/staff/training/community-growth-specialist.md
+++ b/src/content/docs/staff/training/community-growth-specialist.md
@@ -2,13 +2,13 @@
 title: Community Growth Specialist Training for Staff
 ---
 
-**SPECIALIZED TRAINING FOR COMMUNITY GROWTH AND OUTREACH SPECIALISTS**
+**SPECIALISED TRAINING FOR COMMUNITY GROWTH AND OUTREACH SPECIALISTS**
 
 ## 1. INTRODUCTION AND SCOPE
 
 ### 1.1. Purpose and Strategic Mission
 
-This training provides comprehensive guidance for staff members serving as Community Growth Specialists within our community ecosystem. Community growth is not just about increasing numbers—it's about strategically building a diverse, inclusive, and sustainable community that advances our social justice mission while maintaining the quality and values that make our community special.
+This training provides comprehensive guidance for Team members serving as Community Growth Specialists within our community ecosystem. Community growth is not just about increasing numbers—it's about strategically building a diverse, inclusive, and sustainable community that advances our social justice mission whilst maintaining the quality and values that make our community special.
 
 ### 1.2. Community Growth Specialist Responsibilities
 
@@ -88,7 +88,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 **Impact Monitoring:**
 - **Community Health Metrics**: Regular monitoring of community health during growth periods
-- **Member Satisfaction**: Tracking member satisfaction among both new and existing members
+- **Member Satisfaction**: Tracking member satisfaction amongst both new and existing members
 - **Engagement Quality**: Monitoring quality of community engagement and interaction
 - **Conflict Indicators**: Watching for increased conflict or tension during growth periods
 
@@ -128,8 +128,8 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 #### 3.2.1. Community-Based Outreach
 
-**Partner Organization Collaboration:**
-- **Diversity Organizations**: Partnerships with organisations serving underrepresented groups in tech
+**Partner Organisation Collaboration:**
+- **Diversity Organisations**: Partnerships with organisations serving underrepresented groups in tech
 - **Educational Institutions**: Partnerships with schools, bootcamps, and training programmes
 - **Professional Associations**: Collaboration with professional associations focused on diversity
 - **Community Centres**: Partnerships with community centres and local organisations
@@ -158,8 +158,8 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 #### 3.3.1. Strategic Partnership Identification
 
-**Mission-Aligned Organizations:**
-- **Social Justice Organizations**: Partnerships with organisations working on social justice issues
+**Mission-Aligned Organisations:**
+- **Social Justice Organisations**: Partnerships with organisations working on social justice issues
 - **Education and Training**: Partnerships with educational institutions and training programmes
 - **Professional Development**: Partnerships with organisations focused on professional development
 - **Technology Access**: Partnerships with organisations working to improve technology access
@@ -235,8 +235,8 @@ This training provides comprehensive guidance for staff members serving as Commu
 #### 4.2.2. Distribution Strategy
 
 **Multi-Platform Approach:**
-- **Platform Optimization**: Optimizing content for each specific platform and audience
-- **Cross-Platform Consistency**: Maintaining consistent message while adapting format
+- **Platform Optimisation**: Optimising content for each specific platform and audience
+- **Cross-Platform Consistency**: Maintaining consistent message whilst adapting format
 - **Algorithm Understanding**: Understanding platform algorithms and optimising for visibility
 - **Engagement Strategy**: Strategies for meaningful engagement rather than just broadcasting
 
@@ -267,7 +267,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 #### 5.1.2. Quality and Health Metrics
 
 **Community Health Indicators:**
-- **Member Satisfaction**: Satisfaction levels among both new and existing members
+- **Member Satisfaction**: Satisfaction levels amongst both new and existing members
 - **Community Engagement**: Quality and depth of community engagement and participation
 - **Conflict Rates**: Rates of conflict and their resolution during growth periods
 - **Support Usage**: Usage of community support services and resources
@@ -336,7 +336,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 **Resource Protection:**
 - **Sustainable Resource Use**: Using community resources sustainably without depleting them
-- **Fair Distribution**: Ensuring resources are distributed fairly among all community members
+- **Fair Distribution**: Ensuring resources are distributed fairly amongst all community members
 - **Growth Investment**: Investing growth-related resources back into community improvement
 - **Capacity Management**: Managing capacity to ensure quality support for all members
 
@@ -353,8 +353,8 @@ This training provides comprehensive guidance for staff members serving as Commu
 **Cultural Preservation:**
 - **Value Protection**: Protecting core community values during growth and change
 - **Culture Maintenance**: Maintaining positive community culture and atmosphere
-- **Identity Preservation**: Preserving community identity while welcoming new perspectives
-- **Evolution Management**: Managing natural community evolution while maintaining core mission
+- **Identity Preservation**: Preserving community identity whilst welcoming new perspectives
+- **Evolution Management**: Managing natural community evolution whilst maintaining core mission
 
 #### 6.2.2. Avoiding Tokenism and Superficial Diversity
 
@@ -383,7 +383,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 - **Mutual Benefit**: Ensuring partnerships provide mutual benefit rather than one-sided extraction
 
 **Due Diligence Process:**
-- **Organizational Research**: Thorough research on potential partner organisations
+- **Organisational Research**: Thorough research on potential partner organisations
 - **Reputation Assessment**: Assessing reputation and track record of potential partners
 - **Conflict Assessment**: Identifying potential conflicts of interest or value misalignment
 - **Community Input**: Including community input in partnership evaluation and decision-making
@@ -429,76 +429,62 @@ This training provides comprehensive guidance for staff members serving as Commu
 **Social Movement Connection:**
 - **Justice Movement Alignment**: Aligning community growth with broader social justice movements
 - **Intersectional Advocacy**: Advocating for intersectional approaches to technology inclusion
-- **Systemic Change**: Working toward systemic changes that improve technology accessibility
-- **Community Organizing**: Supporting community organising efforts related to technology justice
+- **Systemic Change**: Working towards systemic changes that improve technology accessibility
+- **Community Organising**: Supporting community organising efforts related to technology justice
 
-## 8. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 8. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 8.1. Community Growth Specialist Competencies
+### 8.1. Scenario 1: Ethical Growth Opportunity
 
-#### 8.1.1. Essential Skills Assessment
+**Situation**: A large technology company approaches you about a partnership that could significantly increase community membership. However, the company has a history of discriminatory practices and doesn't align with your community's social justice values. The partnership would bring resources and visibility.
 
-**Strategic Thinking:**
-- **Growth Strategy Development**: Ability to develop comprehensive, ethical growth strategies
-- **Market Analysis**: Skills in analysing target markets and identifying growth opportunities
-- **Impact Assessment**: Ability to assess and predict impact of growth strategies
-- **Sustainability Planning**: Skills in planning for sustainable, long-term community growth
+**Your Response:**
+1. How do you evaluate this partnership opportunity?
+2. How do you balance growth goals with community values?
+3. What questions do you ask about the potential partner?
+4. How do you involve community members in the decision?
+5. How do you decline if the partnership doesn't align?
+6. How do you find alternative growth opportunities?
 
-**Relationship Building:**
-- **Partnership Development**: Skills in identifying, developing, and managing strategic partnerships
-- **Community Engagement**: Ability to engage authentically with diverse communities and individuals
-- **Trust Building**: Skills in building trust and credibility with potential community members
-- **Conflict Resolution**: Ability to resolve conflicts and challenges in partnership and outreach work
+**Correct Answer**: Evaluate partnership against community values and social justice mission, prioritise values over growth, ask about partner's commitment to diversity and inclusion, involve community members in evaluation, decline partnerships that don't align with values, seek alternative growth opportunities that advance mission.
 
-#### 8.1.2. Specialized Competencies
+### 8.2. Scenario 2: Rapid Growth Challenge
 
-**Diversity and Inclusion:**
-- **Cultural Competency**: Understanding of diverse cultural backgrounds and their impact on community participation
-- **Anti-Oppression Analysis**: Ability to analyze and address systemic barriers to community participation
-- **Inclusive Outreach**: Skills in conducting outreach that genuinely welcomes marginalised communities
-- **Intersectional Understanding**: Understanding of how multiple identities affect community access and participation
+**Situation**: A viral post brings thousands of new members to the community in a short period. The rapid growth is overwhelming existing moderation and support systems, and some new members don't align with community values. Existing members are feeling displaced and concerned about community culture.
 
-**Brand and Communication:**
-- **Brand Management**: Skills in managing community brand and reputation
-- **Message Development**: Ability to develop compelling, authentic messages for diverse audiences
-- **Content Creation**: Skills in creating engaging, educational content that attracts aligned individuals
-- **Multi-Platform Communication**: Ability to communicate effectively across diverse platforms and channels
+**Your Response:**
+1. How do you manage rapid growth whilst maintaining community quality?
+2. How do you onboard new members effectively?
+3. How do you protect existing community culture?
+4. How do you scale moderation and support?
+5. How do you address concerns from existing members?
+6. How do you ensure sustainable growth?
 
-### 8.2. Training and Development Program
+**Correct Answer**: Implement onboarding processes, scale moderation and support quickly, protect community culture through clear communication of values, address existing member concerns, ensure new members understand community values, balance growth with quality, implement sustainable growth practices.
 
-#### 8.2.1. Foundation Training
+### 8.3. Scenario 3: Diversity Growth Initiative
 
-**Core Competency Training:**
-- **Community Values**: Comprehensive training on community values and social justice mission
-- **Ethical Growth**: Training on ethical community growth principles and practices
-- **Diversity and Inclusion**: Training on diversity, equity, inclusion, and anti-oppression principles
-- **Partnership Development**: Training on strategic partnership identification and management
+**Situation**: Community leadership want to increase diversity, particularly amongst underrepresented groups in technology. You need to develop strategies to attract and retain diverse members whilst ensuring authentic inclusion.
 
-**Skill Development:**
-- **Communication Skills**: Advanced communication skills for diverse audiences and contexts
-- **Research and Analysis**: Skills in market research, data analysis, and impact assessment
-- **Project Management**: Project management skills for complex growth initiatives
-- **Relationship Management**: Skills in building and maintaining professional relationships
+**Your Response:**
+1. How do you develop strategies to attract diverse members?
+2. How do you ensure authentic inclusion, not just numbers?
+3. How do you involve diverse community members in growth planning?
+4. How do you address barriers to participation?
+5. How do you measure success beyond numbers?
+6. How do you ensure retention of diverse members?
 
-#### 8.2.2. Advanced Development and Performance Standards
+**Correct Answer**: Develop strategies that address barriers to participation, involve diverse community members in planning, focus on authentic inclusion and belonging, address systemic barriers, measure success through participation and belonging metrics, ensure retention through ongoing support and inclusion, advance equity goals.
 
-**Ongoing Development:**
-- **Industry Knowledge**: Continuous learning about technology industry trends and opportunities
-- **Social Justice Education**: Ongoing education about social justice issues and movements
-- **Growth Innovation**: Development of innovative approaches to ethical community growth
-- **Leadership Development**: Development of leadership skills for community growth and influence
+## 9. TRAINING REQUIREMENTS
 
-**Performance Standards:**
-- **Growth Achievement**: Achievement of ethical growth goals while maintaining community quality
-- **Diversity Progress**: Measurable progress on community diversity and inclusion goals
-- **Partnership Success**: Successful development and management of strategic partnerships
-- **Community Impact**: Demonstrable positive impact on community mission and social justice goals
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
 
-**Professional Excellence:**
-- **Ethical Practice**: Consistent adherence to ethical growth practices and community values
-- **Innovation**: Development of innovative approaches to community growth challenges
-- **Collaboration**: Excellent collaboration with community members and partner organisations
-- **Mission Advancement**: Significant contribution to advancement of community mission and social justice goals
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/community-support-specialist.md b/src/content/docs/staff/training/community-support-specialist.md
index f58fa2a..0308a2e 100644
--- a/src/content/docs/staff/training/community-support-specialist.md
+++ b/src/content/docs/staff/training/community-support-specialist.md
@@ -8,7 +8,7 @@ title: Community Support Specialist Training for Staff
 
 ### 1.1. Purpose and Mission
 
-This training provides comprehensive guidance for staff members serving as Community Support Specialists within our community ecosystem. Community support is foundational to creating welcoming, inclusive environments where all community members can thrive, with particular attention to supporting marginalised individuals and removing barriers to participation.
+This training provides comprehensive guidance for Team members serving as Community Support Specialists within our community ecosystem. Community support is foundational to creating welcoming, inclusive environments where all community members can thrive, with particular attention to supporting marginalised individuals and removing barriers to participation.
 
 ### 1.2. Community Support Team Structure
 
@@ -98,7 +98,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 **Empathetic Response:**
 - **Perspective Taking**: Genuinely trying to understand situations from the community member's perspective
-- **Emotional Resonance**: Connecting with the emotional experience while maintaining professional boundaries
+- **Emotional Resonance**: Connecting with the emotional experience whilst maintaining professional boundaries
 - **Cultural Empathy**: Understanding how cultural background affects experiences and perspectives
 - **Intersectional Awareness**: Recognising how multiple identities affect individual experiences
 
@@ -137,7 +137,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 **Resource Knowledge:**
 - **Internal Resources**: Comprehensive knowledge of all community resources and services
 - **External Resources**: Understanding of external resources relevant to community member needs
-- **Specialized Services**: Knowledge of specialised services for specific populations or needs
+- **Specialised Services**: Knowledge of specialised services for specific populations or needs
 - **Emergency Resources**: Quick access to crisis and emergency resources
 
 **Navigation Support:**
@@ -168,7 +168,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 **Problem Resolution:**
 - **Direct Resolution**: Directly resolving issues within scope of authority
-- **Coordination**: Coordinating with other staff members for complex issues
+- **Coordination**: Coordinating with other Team members for complex issues
 - **Timeline Management**: Managing timelines and expectations for issue resolution
 - **Communication**: Keeping community members informed throughout resolution process
 
@@ -209,7 +209,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 **Creative Support:**
 - **Idea Development**: Helping community members develop and refine content ideas
 - **Structure Guidance**: Providing guidance on content structure and organisation
-- **Quality Improvement**: Helping improve content quality while respecting creator vision
+- **Quality Improvement**: Helping improve content quality whilst respecting creator vision
 - **Accessibility Integration**: Ensuring content meets accessibility standards
 
 **Resource Provision:**
@@ -263,13 +263,13 @@ This training provides comprehensive guidance for staff members serving as Commu
 **User Experience:**
 - **Usability Testing**: Testing documentation usability with diverse community members
 - **Navigation Improvement**: Improving documentation organisation and navigation
-- **Search Optimization**: Optimizing documentation for searchability and findability
+- **Search Optimisation**: Optimising documentation for searchability and findability
 - **Feedback Integration**: Integrating user feedback to improve documentation quality
 
 #### 4.5.2. Knowledge Management
 
 **Information Architecture:**
-- **Organization Systems**: Developing clear, logical organisation systems for information
+- **Organisation Systems**: Developing clear, logical organisation systems for information
 - **Version Control**: Maintaining version control and historical records of documentation changes
 - **Cross-Reference Systems**: Creating cross-reference systems for related information
 - **Archive Management**: Managing archived information and historical documentation
@@ -311,7 +311,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 #### 5.2.1. Sustained Support
 
 **Support Coordination:**
-- **Team Coordination**: Coordinating with other staff members and specialists for comprehensive support
+- **Team Coordination**: Coordinating with other Team members and specialists for comprehensive support
 - **Resource Mobilization**: Mobilizing long-term support resources and services
 - **Progress Monitoring**: Monitoring progress and adjusting support as needs change
 - **Boundary Maintenance**: Maintaining appropriate professional boundaries during crisis support
@@ -327,7 +327,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 **Community Communication:**
 - **Appropriate Disclosure**: Determining appropriate level of community communication about crises
 - **Rumour Management**: Managing rumours and misinformation during crisis situations
-- **Community Support**: Mobilizing community support while respecting privacy
+- **Community Support**: Mobilising community support whilst respecting privacy
 - **Healing Facilitation**: Facilitating community healing after traumatic incidents
 
 ## 6. TECHNOLOGY AND ACCESSIBILITY
@@ -352,7 +352,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 **Built-in Accessibility:**
 - **Platform Features**: Understanding built-in accessibility features across community platforms
-- **Settings Optimization**: Helping community members optimise accessibility settings
+- **Settings Optimisation**: Helping community members optimise accessibility settings
 - **Keyboard Navigation**: Supporting effective keyboard navigation of platforms
 - **Mobile Accessibility**: Supporting mobile accessibility features and apps
 
@@ -374,7 +374,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 
 **Platform-Specific Skills:**
 - **Community Platform Training**: Comprehensive training on community platform usage
-- **Feature Utilization**: Teaching effective use of platform features and tools
+- **Feature Utilisation**: Teaching effective use of platform features and tools
 - **Communication Tools**: Supporting effective use of communication and collaboration tools
 - **Privacy and Security**: Teaching privacy and security best practices
 
@@ -405,7 +405,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 - **Outcome Measurement**: Tracking outcomes and success of support interventions
 
 **Privacy Protection:**
-- **Confidentiality Maintenance**: Maintaining confidentiality while documenting necessary information
+- **Confidentiality Maintenance**: Maintaining confidentiality whilst documenting necessary information
 - **Consent for Documentation**: Obtaining appropriate consent for documentation and information sharing
 - **Secure Storage**: Ensuring secure storage of all support documentation
 - **Access Controls**: Limiting access to support documentation to appropriate personnel
@@ -464,7 +464,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 - **Empathy Fatigue**: Recognising signs of empathy fatigue and compassion exhaustion
 - **Secondary Trauma**: Understanding secondary trauma from supporting community members experiencing crisis
 - **Emotional Regulation**: Developing skills in emotional regulation during challenging support situations
-- **Boundary Management**: Maintaining appropriate emotional boundaries while providing effective support
+- **Boundary Management**: Maintaining appropriate emotional boundaries whilst providing effective support
 
 **Impact Management:**
 - **Stress Recognition**: Recognising early signs of stress and burnout
@@ -502,7 +502,7 @@ This training provides comprehensive guidance for staff members serving as Commu
 - **Communication**: Maintaining open, honest communication with team members about challenges and needs
 - **Leadership Support**: Seeking appropriate support from leadership when needed
 
-#### 8.2.2. Organizational Support
+#### 8.2.2. Organisational Support
 
 **Resource Access:**
 - **Training and Development**: Access to ongoing training and professional development opportunities
@@ -516,67 +516,59 @@ This training provides comprehensive guidance for staff members serving as Commu
 - **Feedback and Evaluation**: Regular feedback and performance evaluation to support professional growth
 - **Community Impact**: Recognition of positive impact on community member lives and well-being
 
-## 9. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 9. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 9.1. Core Competency Assessment
+### 9.1. Scenario 1: Complex Support Request
 
-#### 9.1.1. Essential Skills
+**Situation**: A community member contacts you with multiple overlapping needs: they're experiencing technical difficulties, feeling overwhelmed by community participation, dealing with accessibility barriers, and struggling with mental health. They're not sure where to start or what help is available.
 
-**Communication and Interpersonal:**
-- **Active Listening**: Demonstrated proficiency in active listening and empathetic response
-- **Inclusive Communication**: Consistent use of inclusive, accessible communication practices
-- **Conflict De-escalation**: Skills in de-escalating conflicts and managing difficult conversations
-- **Cultural Competency**: Understanding and respect for diverse cultural backgrounds and perspectives
+**Your Response:**
+1. How do you assess and prioritise their needs?
+2. How do you provide person-centred support?
+3. How do you connect them with appropriate resources?
+4. How do you manage multiple support needs simultaneously?
+5. How do you follow up to ensure needs are met?
+6. How do you maintain boundaries whilst being supportive?
 
-**Support and Problem-Solving:**
-- **Assessment Skills**: Ability to accurately assess community member needs and appropriate support
-- **Resource Navigation**: Comprehensive knowledge of available resources and effective connection skills
-- **Crisis Response**: Basic crisis response skills and knowledge of escalation procedures
-- **Follow-up**: Consistent follow-up and monitoring of support outcomes
+**Correct Answer**: Conduct comprehensive assessment, prioritise based on urgency and impact, provide person-centred support that respects their agency, connect with multiple resources (technical, accessibility, mental health), coordinate support across areas, follow up regularly, maintain professional boundaries, support their self-determination.
 
-#### 9.1.2. Role-Specific Competencies
+### 9.2. Scenario 2: Crisis Support Situation
 
-**Technical Support:**
-- **Technical Troubleshooting**: Ability to diagnose and resolve common technical issues
-- **Accessibility Knowledge**: Understanding of assistive technologies and accessibility accommodations
-- **Documentation Skills**: Skills in creating clear, accessible technical documentation
-- **User Education**: Ability to teach technical skills effectively to diverse learners
+**Situation**: While providing technical support, a community member shares that they're experiencing a mental health crisis. They mention feeling hopeless and having thoughts of self-harm, but say they don't want to burden anyone.
 
-**Content and Documentation:**
-- **Writing and Editing**: Strong writing and editing skills for various types of content
-- **Information Organisation**: Skills in organising and structuring information for accessibility
-- **Quality Assurance**: Ability to maintain high quality standards while respecting diverse perspectives
-- **Collaboration**: Effective collaboration with content creators and community members
+**Your Response:**
+1. How do you recognise this as a crisis situation?
+2. How do you respond immediately whilst maintaining boundaries?
+3. What resources do you provide?
+4. How do you escalate appropriately?
+5. How do you balance support with your limitations?
+6. How do you follow up?
 
-### 9.2. Training and Development Program
+**Correct Answer**: Recognise crisis indicators, respond with empathy and care, provide immediate crisis resources (hotlines, emergency services), escalate to crisis response team immediately, maintain boundaries (don't provide therapy), encourage professional help, follow up as directed, document appropriately.
 
-#### 9.2.1. Foundation Training
+### 9.3. Scenario 3: Accessibility Accommodation Request
 
-**Initial Training Requirements:**
-- **Community Values**: Comprehensive training on community values and mission
-- **Support Philosophy**: Training on person-centred, trauma-informed support approaches
-- **Communication Skills**: Intensive training in inclusive communication and active listening
-- **Crisis Response**: Basic crisis response training and escalation procedures
+**Situation**: A community member with a disability requests accommodations to participate fully in the community. They need specific modifications to how content is presented and how they can interact with the platform. You're not sure what accommodations are possible or reasonable.
 
-**Ongoing Development:**
-- **Monthly Skills Training**: Regular skills development training on relevant support topics
-- **Quarterly Review**: Regular review and assessment of support effectiveness and areas for growth
-- **Annual Competency Assessment**: Comprehensive annual assessment of support competencies
-- **Professional Development**: Access to external professional development opportunities
+**Your Response:**
+1. How do you approach this accommodation request?
+2. How do you determine what accommodations are possible?
+3. How do you work collaboratively with the community member?
+4. How do you coordinate with technical and accessibility teams?
+5. How do you ensure accommodations are implemented?
+6. How do you follow up to ensure effectiveness?
 
-#### 9.2.2. Performance Standards
+**Correct Answer**: Approach with respect and collaboration, work with community member to understand needs, consult with accessibility and technical teams, explore multiple accommodation options, implement accommodations promptly, test effectiveness with community member, provide ongoing support and adjustments as needed.
 
-**Quality Indicators:**
-- **Community Satisfaction**: High satisfaction ratings from community members receiving support
-- **Issue Resolution**: Effective resolution of support issues within appropriate timeframes
-- **Resource Connection**: Successful connection of community members with appropriate resources
-- **Team Collaboration**: Effective collaboration and coordination with other support team members
+## 10. TRAINING REQUIREMENTS
 
-**Professional Growth:**
-- **Skill Development**: Continuous development of relevant support skills and knowledge
-- **Innovation**: Contribution of innovative approaches to support challenges
-- **Leadership**: Development of leadership skills within support team context
-- **Community Impact**: Demonstrable positive impact on community member experience and outcomes
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/conflict-resolution.md b/src/content/docs/staff/training/conflict-resolution.md
index 4868ea3..f3e1eac 100644
--- a/src/content/docs/staff/training/conflict-resolution.md
+++ b/src/content/docs/staff/training/conflict-resolution.md
@@ -2,13 +2,13 @@
 title: Conflict Resolution Training for Staff
 ---
 
-**ESSENTIAL TRAINING FOR ALL COMMUNITY STAFF MEMBERS**
+**ESSENTIAL TRAINING FOR ALL COMMUNITY TEAM MEMBERS**
 
 ## 1. INTRODUCTION AND FRAMEWORK
 
 ### 1.1. Purpose and Importance
 
-This training provides comprehensive guidance for staff members on preventing, managing, and resolving conflicts within our community. Effective conflict resolution is essential for maintaining a healthy community environment and ensuring that disputes don't escalate into harmful situations that drive away community members.
+This training provides comprehensive guidance for Team members on preventing, managing, and resolving conflicts within our community. Effective conflict resolution is essential for maintaining a healthy community environment and ensuring that disputes don't escalate into harmful situations that drive away community members.
 
 ### 1.2. Our Approach to Conflict Resolution
 
@@ -68,7 +68,7 @@ This training operates within our comprehensive policy framework:
 #### 2.1.3. Authority-Based Conflicts
 
 **Characteristics:**
-- Disputes involving community leadership or staff members
+- Disputes involving community leadership or Team members
 - Challenges to moderation decisions or community policies
 - Conflicts arising from enforcement actions or consequences
 - Disagreements about community governance or decision-making
@@ -76,7 +76,7 @@ This training operates within our comprehensive policy framework:
 **Examples:**
 - Appeals of moderation actions or disciplinary decisions
 - Challenges to community policies or their implementation
-- Disputes about staff member conduct or decision-making
+- Disputes about Team member conduct or decision-making
 - Conflicts about transparency or accountability in leadership
 
 #### 2.1.4. Values-Based Conflicts
@@ -185,6 +185,8 @@ This training operates within our comprehensive policy framework:
 
 #### 3.2.2. De-escalation Techniques
 
+**Reference to Comprehensive De-escalation Training**: For detailed de-escalation techniques, communication strategies, and practical application guidance, see [De-escalation Techniques Training](/staff/training/de-escalation-techniques). This section provides a brief overview; refer to the de-escalation training document for comprehensive guidance.
+
 **Immediate Response Strategies:**
 - **Pause and Cool Down**: Suggest breaks in heated discussions
 - **Refocus on Issues**: Redirect from personal attacks to substantive concerns
@@ -215,7 +217,7 @@ This training operates within our comprehensive policy framework:
 - **Primary Parties**: Directly involved individuals
 - **Secondary Parties**: Community members affected by or involved in the conflict
 - **Community Impact**: Broader effects on community culture and participation
-- **Staff Involvement**: Whether staff members are parties to the conflict
+- **Team Involvement**: Whether Team members are parties to the conflict
 
 **Context Considerations:**
 - **Historical Context**: Previous interactions between parties
@@ -230,7 +232,7 @@ This training operates within our comprehensive policy framework:
 2. **Document Situation**: Record key details while information is fresh
 3. **Separate if Needed**: Prevent further escalation through temporary separation
 4. **Assess Resources**: Determine what support and intervention resources are needed
-5. **Coordinate with Team**: Involve other staff members as appropriate
+5. **Coordinate with Team**: Involve other Team members as appropriate
 
 **Communication Approach:**
 - Contact all primary parties to understand their perspectives
@@ -548,7 +550,7 @@ This training operates within our comprehensive policy framework:
 #### 7.2.1. Quality Assurance
 
 **Regular Review Processes:**
-- **Peer Review**: Regular review of conflict resolution decisions by other staff members
+- **Peer Review**: Regular review of conflict resolution decisions by other Team members
 - **Outcome Assessment**: Follow-up evaluation of resolution effectiveness and lasting impact
 - **Process Improvement**: Regular refinement of conflict resolution procedures based on experience
 - **Training Updates**: Incorporation of lessons learned into ongoing staff training
@@ -564,12 +566,12 @@ This training operates within our comprehensive policy framework:
 **Ongoing Skill Development:**
 - Regular training updates on conflict resolution techniques and best practices
 - Cross-cultural competency development and cultural humility training
-- Trauma-informed practices training for working with community members experiencing distress
+- Trauma-informed practices training for working with community members experiencing distress (see [Trauma-Informed Moderation Training](/staff/training/trauma-informed-moderation) for comprehensive guidance)
 - Advanced mediation and restorative justice training for complex situations
 
 **Support Systems:**
-- **Peer Consultation**: Regular opportunities to discuss challenging cases with other staff members
-- **Supervision and Mentoring**: Support from experienced staff members and leadership
+- **Peer Consultation**: Regular opportunities to discuss challenging cases with other Team members
+- **Supervision and Mentoring**: Support from experienced Team members and Leadership
 - **Professional Resources**: Access to external training, resources, and professional development
 - **Wellness Support**: Resources and support for managing the emotional impact of conflict resolution work
 
@@ -582,7 +584,7 @@ This training operates within our comprehensive policy framework:
 **Managing Large-Scale Conflicts:**
 - **Stakeholder Mapping**: Identify all parties and their interests in complex conflicts
 - **Phased Resolution**: Break complex conflicts into manageable phases and components
-- **Multiple Facilitators**: Assign different staff members to work with different parties or aspects
+- **Multiple Facilitators**: Assign different Team members to work with different parties or aspects
 - **Community Healing**: Plan for broader community healing and relationship repair
 
 **Example Scenario**: Community divided over policy changes affecting multiple groups
@@ -594,11 +596,11 @@ This training operates within our comprehensive policy framework:
 
 #### 8.1.2. Staff-Community Member Conflicts
 
-**When Staff Are Parties to Conflicts:**
-- **Recusal Procedures**: Ensure conflicted staff members don't participate in resolution decisions
-- **Independent Review**: Utilize staff members or leadership without conflicts of interest
-- **External Mediation**: Consider bringing in external mediators for serious staff-community conflicts
-- **Accountability Measures**: Apply same community standards to staff members involved in conflicts
+**When Team Members Are Parties to Conflicts:**
+- **Recusal Procedures**: Ensure conflicted Team members don't participate in resolution decisions
+- **Independent Review**: Utilise Team members or Leadership without conflicts of interest
+- **External Mediation**: Consider bringing in external mediators for serious Team-community conflicts
+- **Accountability Measures**: Apply same community standards to Team members involved in conflicts
 
 **Maintaining Community Trust:**
 - **Transparency**: Provide clear communication about how staff conflicts are handled
@@ -632,35 +634,25 @@ This training operates within our comprehensive policy framework:
 
 ## 9. SELF-CARE AND EMOTIONAL MANAGEMENT
 
-### 9.1. Managing the Emotional Impact
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides conflict-resolution-specific considerations; refer to the self-care resources document for comprehensive guidance.
+
+### 9.1. Conflict Resolution-Specific Self-Care Considerations
 
 #### 9.1.1. Understanding Emotional Labour
 
-**Recognising Emotional Demands:**
-- Conflict resolution work involves significant emotional labour and stress
-- Exposure to community distress and interpersonal harm can affect staff wellbeing
-- Maintaining neutrality and empathy simultaneously can be emotionally challenging
-- Repeated exposure to conflict can lead to compassion fatigue and burnout
+**Additional Considerations for Conflict Resolution Work:**
+- Exposure to conflict and difficult interactions
+- Emotional labour of managing others' emotions
+- Need for patience and emotional regulation
+- Importance of maintaining neutrality and boundaries
+- Regular support and skill development
 
-**Signs of Emotional Strain:**
-- **Physical Symptoms**: Fatigue, headaches, tension, sleep disturbances
-- **Emotional Symptoms**: Irritability, anxiety, detachment, overwhelming sadness
-- **Professional Symptoms**: Decreased empathy, cynicism, reduced effectiveness, avoidance of conflict situations
-- **Personal Symptoms**: Relationship strain, social withdrawal, loss of personal interests
-
-#### 9.1.2. Emotional Regulation Strategies
-
-**During Conflict Resolution:**
-- **Breathing Techniques**: Use deep breathing to maintain calm during difficult conversations
-- **Grounding Exercises**: Techniques to stay present and focused during emotional situations
-- **Emotional Awareness**: Regular check-ins with own emotional state during conflict work
-- **Professional Boundaries**: Maintain appropriate emotional distance while remaining empathetic
-
-**Between Conflict Situations:**
-- **Debriefing**: Process difficult situations with colleagues or supervisors
-- **Reflection**: Regular self-reflection on emotional responses and triggers
-- **Restoration**: Engage in activities that restore emotional equilibrium and energy
-- **Professional Support**: Access counselling or professional support when needed
+**Self-Care Practices:**
+- Take breaks between difficult moderation actions
+- Practice de-escalation techniques for yourself
+- Connect with colleagues for support and debriefing
+- Maintain perspective on your role and limitations
+- Celebrate successful resolutions and positive outcomes
 
 ### 9.2. Support Systems and Resources
 
@@ -668,7 +660,7 @@ This training operates within our comprehensive policy framework:
 
 **Peer Support Networks:**
 - **Regular Check-ins**: Scheduled team meetings focused on emotional wellbeing and support
-- **Buddy Systems**: Pairing staff members for mutual support and consultation
+- **Buddy Systems**: Pairing Team members for mutual support and consultation
 - **Debriefing Sessions**: Structured debriefing after difficult conflict resolution situations
 - **Shared Learning**: Regular sharing of successful strategies and lessons learned
 
@@ -692,67 +684,59 @@ This training operates within our comprehensive policy framework:
 - **Personal Time**: Adequate time off and vacation policies
 - **Wellness Programs**: Access to wellness resources and programmes
 
-## 10. CERTIFICATION AND COMPETENCY DEVELOPMENT
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 10.1. Core Competency Requirements
+### 10.1. Scenario 1: Interpersonal Conflict Escalation
 
-#### 10.1.1. Essential Skills Assessment
+**Situation**: Two community members who were previously friends are now in an escalating conflict. What started as a disagreement about a technical approach has become personal attacks, name-calling, and threats. Other community members are taking sides, and the conflict is disrupting multiple channels.
 
-**Communication Skills:**
-- **Active Listening**: Demonstrated ability to listen empathetically and understand multiple perspectives
-- **De-escalation**: Skills in reducing tension and preventing conflict escalation
-- **Cultural Competency**: Understanding of cultural differences in communication and conflict resolution
-- **Trauma-Informed Communication**: Ability to communicate sensitively with community members who have experienced harm
+**Your Response:**
+1. How do you assess the severity and stage of this conflict?
+2. What immediate actions do you take to prevent further escalation?
+3. How do you separate the parties if needed?
+4. How do you approach each party individually?
+5. What de-escalation techniques do you use?
+6. How do you facilitate resolution or determine if resolution isn't possible?
 
-**Conflict Analysis:**
-- **Situation Assessment**: Ability to accurately assess conflict severity, context, and appropriate interventions
-- **Stakeholder Analysis**: Understanding of how to identify and work with all parties affected by conflicts
-- **Power Dynamics**: Recognition of power imbalances and marginalization factors in conflicts
-- **Systems Thinking**: Understanding of how individual conflicts connect to broader community dynamics
+**Correct Answer**: Assess as high-severity conflict in entrenchment stage. Immediately separate parties, stop personal attacks, meet individually with each party to understand perspectives, use de-escalation techniques, assess if resolution is possible, facilitate discussion if both parties willing, or take protective action if not.
 
-**Resolution Processes:**
-- **Facilitation Skills**: Ability to facilitate productive discussions between conflicting parties
-- **Mediation Techniques**: Understanding of formal and informal mediation processes
-- **Restorative Justice**: Knowledge of restorative approaches and when they're appropriate
-- **Enforcement Decisions**: Ability to make fair, consistent enforcement decisions when resolution isn't possible
+### 10.2. Scenario 2: Conflict Involving Marginalised Community Member
 
-#### 10.1.2. Advanced Competencies
+**Situation**: A marginalised community member reports experiencing discrimination from another member. The other member claims they were "just joking" and that the marginalised member is "overreacting." Other community members are dismissing the concern as "not a big deal."
 
-**Specialized Skills:**
-- **Multi-Party Conflict Management**: Ability to manage complex conflicts involving multiple parties or community-wide disputes
-- **Crisis Conflict Resolution**: Skills in managing conflicts that escalate to crisis levels
-- **Cross-Cultural Mediation**: Advanced skills in resolving conflicts across cultural differences
-- **Trauma-Informed Practices**: Advanced understanding of trauma responses and trauma-informed conflict resolution
+**Your Response:**
+1. How do you prioritise supporting the marginalised community member?
+2. How do you address the discriminatory behaviour?
+3. How do you handle the "just joking" defence?
+4. How do you address community members dismissing the concern?
+5. What educational intervention is appropriate?
+6. How do you ensure community safety going forward?
 
-### 10.2. Training and Certification Process
+**Correct Answer**: Prioritise support for marginalised member, validate their experience, address discriminatory behaviour with education about impact, explain that intent doesn't negate impact, address dismissive community responses, provide education about discrimination and community values, take protective measures, ensure ongoing safety.
 
-#### 10.2.1. Foundation Training Requirements
+### 10.3. Scenario 3: Staff-Community Member Conflict
 
-**Initial Training:**
-1. **Complete All Required Reading**: This training document and related policy documents
-2. **Shadow Experienced Staff**: Observe experienced staff managing conflicts and resolution processes
-3. **Practice Scenarios**: Complete practice scenarios with feedback from experienced staff
-4. **Skills Assessment**: Demonstrate core competencies in controlled practice situations
+**Situation**: A community member reports that a Team member was dismissive and rude to them during a moderation interaction. The Team member says the community member was being difficult and they were just doing their job. The community member feels their concerns weren't taken seriously.
 
-**Ongoing Development:**
-- **Monthly Training Sessions**: Regular skill development and case study analysis
-- **Quarterly Reviews**: Assessment of conflict resolution effectiveness and areas for growth
-- **Annual Training Updates**: Comprehensive training updates and competency reassessment
-- **Professional Development**: Opportunities for advanced training and specialisation
+**Your Response:**
+1. How do you handle a conflict where staff are involved?
+2. What recusal procedures do you follow?
+3. How do you ensure fair and independent review?
+4. How do you address power dynamics?
+5. How do you maintain community trust?
+6. What accountability measures apply?
 
-#### 10.2.2. Performance Standards
+**Correct Answer**: Ensure conflicted Team member doesn't participate in resolution, use independent Team members for review, address power dynamics explicitly, apply same community standards to Team members, provide transparent communication about process, take appropriate accountability measures, maintain community trust through fair process.
 
-**Quality Indicators:**
-- **Resolution Effectiveness**: Success rate in achieving lasting conflict resolution
-- **Community Satisfaction**: Feedback from community members involved in conflict resolution
-- **Consistency**: Consistent application of conflict resolution principles and processes
-- **Professional Growth**: Demonstrated continued learning and skill development
+## 11. TRAINING REQUIREMENTS
 
-**Accountability Measures:**
-- **Peer Review**: Regular review of conflict resolution decisions by other qualified staff
-- **Community Feedback**: Regular collection and integration of community feedback on conflict resolution
-- **Documentation Quality**: Thorough, accurate documentation of conflict resolution processes and outcomes
-- **Ethical Standards**: Adherence to ethical standards for conflict resolution and community service
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/content-moderation-fundamentals.md b/src/content/docs/staff/training/content-moderation-fundamentals.md
new file mode 100644
index 0000000..29b8903
--- /dev/null
+++ b/src/content/docs/staff/training/content-moderation-fundamentals.md
@@ -0,0 +1,737 @@
+---
+title: Content Moderation Fundamentals Training for Staff
+---
+
+**ESSENTIAL TRAINING FOR ALL MODERATION STAFF**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides fundamental guidance for Team members on content moderation principles, practices, and decision-making. Content moderation is the process of reviewing, evaluating, and taking action on user-generated content to ensure it complies with community guidelines and maintains safe, welcoming environments.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive moderation framework:
+
+**(a)** **Content and Moderation Policy**: Primary policy governing content standards and enforcement;
+
+**(b)** **Community Code of Conduct**: Behavioural expectations and community standards;
+
+**(c)** **Inclusive Moderation Policy**: Principles for moderation that considers impact on marginalised members;
+
+**(d)** **Conflict Resolution Policy**: Procedures for resolving disputes related to content;
+
+**(e)** **Harassment Response Policy**: Procedures for responding to harassing content;
+
+**(f)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Core Moderation Principles
+
+**Consistency:**
+- Apply policies consistently across all content
+- Similar violations receive similar responses
+- Fair and predictable moderation practices
+- Community members can anticipate outcomes
+
+**Fairness:**
+- Consider context and circumstances
+- Apply policies equitably to all members
+- Avoid bias and favouritism
+- Provide opportunities for appeal
+
+**Transparency:**
+- Clear communication about moderation actions
+- Explain reasoning for decisions
+- Provide information about policies
+- Maintain transparency logs and documentation
+
+**Safety:**
+- Prioritise community member safety
+- Remove harmful content promptly
+- Protect vulnerable community members
+- Maintain safe, welcoming environments
+
+## 2. CONTENT MODERATION BASICS
+
+### 2.1. What Is Content Moderation?
+
+#### 2.1.1. Definition and Purpose
+
+**Content Moderation** is the practice of monitoring and managing user-generated content to ensure it complies with community guidelines, legal requirements, and platform policies.
+
+**Purposes of Moderation:**
+- **Safety**: Protect community members from harm
+- **Compliance**: Ensure content complies with laws and policies
+- **Quality**: Maintain content quality and relevance
+- **Community Health**: Foster positive community culture
+- **Trust**: Build and maintain community trust
+
+#### 2.1.2. Types of Content Moderation
+
+**Proactive Moderation:**
+- Reviewing content before it's published
+- Automated filtering and detection
+- Pre-approval processes
+- Queue-based moderation systems
+
+**Reactive Moderation:**
+- Responding to user reports
+- Reviewing flagged content
+- Investigating complaints
+- Addressing violations after publication
+
+**Hybrid Approaches:**
+- Combination of proactive and reactive
+- Automated detection with human review
+- Risk-based moderation approaches
+- Scalable moderation systems
+
+### 2.2. Moderation Decision-Making
+
+#### 2.2.1. Decision-Making Framework
+
+**Assessment Process:**
+1. **Review Content**: Examine content thoroughly
+2. **Check Policies**: Determine applicable policies
+3. **Assess Context**: Consider context and circumstances
+4. **Evaluate Impact**: Assess impact on community and individuals
+5. **Make Decision**: Determine appropriate action
+6. **Document**: Record decision and reasoning
+7. **Communicate**: Inform relevant parties
+8. **Follow Up**: Monitor and follow up as needed
+
+**Key Considerations:**
+- **Policy Violation**: Does content violate policies?
+- **Severity**: How severe is the violation?
+- **Context**: What is the context of the content?
+- **Impact**: What is the impact on community and individuals?
+- **History**: What is the user's history?
+- **Intent**: What was the intent (when relevant)?
+
+#### 2.2.2. Context Analysis
+
+**Contextual Factors:**
+- **Platform and Location**: Where did content appear?
+- **Audience**: Who was the intended audience?
+- **Timing**: When was content posted?
+- **Relationship**: What is the relationship between parties?
+- **History**: What is the history of interactions?
+- **Culture**: What are the cultural considerations?
+
+**Context Importance:**
+- Same content may have different meaning in different contexts
+- Context affects severity and impact assessment
+- Context informs appropriate response
+- Context helps avoid over-moderation or under-moderation
+- Context supports fair and appropriate decisions
+
+## 3. POLICY VIOLATION ASSESSMENT
+
+### 3.1. Identifying Violations
+
+#### 3.1.1. Policy Categories
+
+**Safety Violations:**
+- Threats of violence or harm
+- Doxxing or privacy violations
+- Harassment or bullying
+- Hate speech or discrimination
+- Content that creates safety risks
+
+**Content Quality Violations:**
+- Spam or unwanted content
+- Off-topic or irrelevant content
+- Low-quality or disruptive content
+- Repetitive or excessive content
+- Content that degrades discussion quality
+
+**Legal Violations:**
+- Copyright infringement
+- Illegal content or activities
+- Defamation or libel
+- Content violating laws or regulations
+- Content requiring legal compliance
+
+**Community Standards Violations:**
+- Violations of community guidelines
+- Inappropriate behaviour or language
+- Disruptive or toxic behaviour
+- Content that harms community culture
+- Behavior inconsistent with community values
+
+#### 3.1.2. Severity Assessment
+
+**Severity Levels:**
+
+**Critical (IMMEDIATE ACTION):**
+- Immediate safety threats
+- Criminal activity
+- Severe harassment or abuse
+- Content requiring immediate removal
+- Situations requiring immediate protective action
+
+**High (RESPOND WITHIN 1 HOUR):**
+- Serious policy violations
+- Significant harm to individuals or community
+- Content requiring prompt removal
+- Situations requiring significant intervention
+- Repeated or egregious violations
+
+**Moderate (RESPOND WITHIN 24 HOURS):**
+- Clear policy violations
+- Moderate impact on community
+- Content requiring removal or modification
+- Situations requiring intervention
+- First-time or minor violations
+
+**Low (RESPOND WITHIN 48 HOURS):**
+- Minor policy violations
+- Limited impact on community
+- Content requiring warning or education
+- Situations requiring minimal intervention
+- Edge cases or ambiguous situations
+
+### 3.2. Edge Cases and Ambiguity
+
+#### 3.2.1. Handling Ambiguity
+
+**When Content Is Ambiguous:**
+- Content that could be interpreted multiple ways
+- Situations where policy application is unclear
+- Edge cases not clearly covered by policies
+- Context-dependent situations
+- Cultural or linguistic differences
+
+**Approach to Ambiguity:**
+- Gather more information
+- Consult with colleagues
+- Consider context carefully
+- Apply principles and values
+- Err on side of safety when uncertain
+- Document reasoning for decisions
+
+#### 3.2.2. Grey Areas
+
+**Common Grey Areas:**
+- Satire, humour, or parody
+- Educational or academic content
+- Historical or news content
+- Creative expression or art
+- Cultural or linguistic differences
+- Context-dependent situations
+
+**Handling Grey Areas:**
+- Consider intent and context
+- Assess impact on community
+- Apply community values and principles
+- Consult with team when needed
+- Document reasoning carefully
+- Provide clear explanation to users
+
+## 4. MODERATION ACTIONS
+
+### 4.1. Types of Moderation Actions
+
+#### 4.1.1. Content Actions
+
+**Content Removal:**
+- Delete violating content
+- Remove from public view
+- Preserve evidence when needed
+- Notify user of removal
+- Explain reason for removal
+
+**Content Modification:**
+- Edit or redact portions
+- Add warnings or labels
+- Move to different location
+- Limit visibility or access
+- Require changes before approval
+
+**Content Warnings:**
+- Add content warnings
+- Label sensitive content
+- Provide context or explanation
+- Allow user choice to view
+- Protect vulnerable community members
+
+#### 4.1.2. User Actions
+
+**Warnings:**
+- Formal warnings about violations
+- Explanation of policy violation
+- Guidance on expected behaviour
+- Information about consequences
+- Opportunity to correct behaviour
+
+**Restrictions:**
+- Temporary restrictions on posting
+- Limited access to certain features
+- Restricted participation in discussions
+- Supervised or moderated interactions
+- Time-limited restrictions
+
+**Suspensions:**
+- Temporary suspension from community
+- Time-limited removal of access
+- Clear explanation of suspension
+- Information about reinstatement
+- Opportunity for appeal
+
+**Bans:**
+- Permanent removal from community
+- Reserved for severe or repeated violations
+- Clear explanation of ban
+- Information about appeal process
+- Protection of community safety
+
+### 4.2. Progressive Enforcement
+
+#### 4.2.1. Escalation Framework
+
+**Progressive Approach:**
+- Start with education and warnings
+- Escalate based on severity and history
+- Provide opportunities for correction
+- Apply consequences proportionally
+- Maintain consistency and fairness
+
+**Escalation Factors:**
+- **Severity**: More severe violations escalate faster
+- **History**: Repeat violations escalate faster
+- **Response**: User response affects escalation
+- **Impact**: Greater impact escalates faster
+- **Intent**: Malicious intent escalates faster
+
+#### 4.2.2. Consistency in Enforcement
+
+**Maintaining Consistency:**
+- Apply policies consistently
+- Similar violations receive similar responses
+- Consider history and context
+- Document reasoning for decisions
+- Review for consistency regularly
+
+**Challenges to Consistency:**
+- Different moderators may interpret differently
+- Context affects appropriate response
+- Policies may need interpretation
+- Situations may be unique
+- Balancing consistency with context
+
+## 5. DOCUMENTATION AND TRANSPARENCY
+
+### 5.1. Documentation Requirements
+
+#### 5.1.1. Essential Documentation
+
+**Incident Documentation:**
+- Date, time, and platform
+- User(s) involved
+- Content or behaviour in question
+- Policy violation identified
+- Evidence (screenshots, logs, etc.)
+- Action taken and reasoning
+- Follow-up plans
+
+**Decision Documentation:**
+- Policy applied
+- Context considered
+- Reasoning for decision
+- Severity assessment
+- Action taken
+- Communication sent
+- Follow-up required
+
+#### 5.1.2. Documentation Standards
+
+**Quality Standards:**
+- Accurate and complete information
+- Clear and objective language
+- Sufficient detail for understanding
+- Consistent format and structure
+- Accessible to authorized personnel
+- Preserved for appropriate duration
+
+**Privacy Considerations:**
+- Protect user privacy
+- Limit access to authorized personnel
+- Anonymize when sharing for training
+- Secure storage of sensitive information
+- Balance transparency with privacy
+
+### 5.2. Transparency Practices
+
+#### 5.2.1. User Communication
+
+**Clear Communication:**
+- Explain moderation actions clearly
+- Provide reason for action
+- Reference specific policy violations
+- Offer opportunity for clarification
+- Provide information about appeals
+
+**Communication Best Practices:**
+- Use clear, respectful language
+- Avoid jargon or technical terms
+- Provide context and explanation
+- Offer support and resources
+- Maintain professional tone
+
+#### 5.2.2. Community Transparency
+
+**Transparency Logs:**
+- Public transparency about moderation
+- General information about actions taken
+- Statistics and trends
+- Policy updates and changes
+- Community education and information
+
+**Balancing Transparency:**
+- Protect user privacy
+- Maintain community safety
+- Provide useful information
+- Build trust and accountability
+- Support community understanding
+
+## 6. APPEALS AND REVIEW
+
+### 6.1. Appeal Process
+
+#### 6.1.1. User Appeals
+
+**Appeal Rights:**
+- Users can appeal moderation actions
+- Clear process for submitting appeals
+- Fair review of appeals
+- Timely response to appeals
+- Opportunity to provide additional information
+
+**Appeal Process:**
+1. User submits appeal
+2. Appeal reviewed by different moderator
+3. Additional information gathered if needed
+4. Decision made on appeal
+5. User notified of decision
+6. Action taken if appeal granted
+
+#### 6.1.2. Appeal Considerations
+
+**Review Factors:**
+- Original violation and evidence
+- User's explanation and additional information
+- Context and circumstances
+- Policy application and interpretation
+- Consistency with other decisions
+- Community impact and safety
+
+**Appeal Outcomes:**
+- **Upheld**: Original action confirmed
+- **Modified**: Action adjusted
+- **Reversed**: Action removed
+- **New Action**: Different action taken
+- **Clarification**: Additional explanation provided
+
+### 6.2. Quality Assurance
+
+#### 6.2.1. Peer Review
+
+**Review Processes:**
+- Regular peer review of moderation decisions
+- Review of difficult or controversial cases
+- Consistency checks across moderators
+- Learning and improvement opportunities
+- Quality assurance and accountability
+
+**Review Benefits:**
+- Catch errors or inconsistencies
+- Learn from different perspectives
+- Improve moderation practices
+- Ensure quality and fairness
+- Build team knowledge and skills
+
+#### 6.2.2. Continuous Improvement
+
+**Improvement Practices:**
+- Regular review of moderation practices
+- Analysis of trends and patterns
+- Community feedback integration
+- Policy updates and refinements
+- Training and skill development
+
+**Learning from Experience:**
+- Review successful moderation
+- Learn from mistakes
+- Identify improvement opportunities
+- Update practices and procedures
+- Share knowledge and best practices
+
+## 7. SPECIAL CONSIDERATIONS
+
+### 7.1. Context-Dependent Moderation
+
+#### 7.1.1. Cultural Considerations
+
+**Cultural Sensitivity:**
+- Recognise cultural differences
+- Understand cultural context
+- Avoid cultural bias
+- Respect cultural expressions
+- Support cultural diversity
+
+**Cultural Moderation:**
+- Consider cultural context in decisions
+- Avoid imposing single cultural standard
+- Support cultural community members
+- Educate about cultural differences
+- Create inclusive cultural environments
+
+#### 7.1.2. Language Considerations
+
+**Language Differences:**
+- Recognise language proficiency differences
+- Consider language barriers
+- Understand translation limitations
+- Support non-native speakers
+- Avoid language-based bias
+
+**Language Moderation:**
+- Consider language context in decisions
+- Provide language support when needed
+- Don't assume intent based on language
+- Support multilingual community members
+- Create inclusive language environments
+
+### 7.2. Platform-Specific Considerations
+
+#### 7.2.1. Different Platforms
+
+**Platform Differences:**
+- Different platforms have different norms
+- Content format affects interpretation
+- Audience and context vary by platform
+- Platform features affect moderation
+- Platform limitations affect options
+
+**Platform-Specific Moderation:**
+- Understand platform-specific norms
+- Adapt moderation to platform context
+- Use platform-appropriate actions
+- Consider platform limitations
+- Support platform-specific needs
+
+#### 7.2.2. Cross-Platform Coordination
+
+**Coordination Needs:**
+- Consistent standards across platforms
+- Shared user history and context
+- Coordinated responses when needed
+- Cross-platform pattern recognition
+- Unified community experience
+
+**Coordination Practices:**
+- Share information appropriately
+- Coordinate responses when needed
+- Maintain consistency across platforms
+- Recognise cross-platform patterns
+- Support unified community experience
+
+## 8. MODERATION TOOLS AND SYSTEMS
+
+### 8.1. Moderation Tools
+
+#### 8.1.1. Content Review Tools
+
+**Review Interfaces:**
+- Queues for reviewing reported content
+- Filters and search capabilities
+- Bulk actions and workflows
+- Tagging and categorisation
+- History and context views
+
+**Efficiency Tools:**
+- Keyboard shortcuts and hotkeys
+- Templates for common responses
+- Quick actions for common violations
+- Automation for routine tasks
+- Integration with other systems
+
+#### 8.1.2. Communication Tools
+
+**User Communication:**
+- Direct messaging capabilities
+- Notification systems
+- Email or platform messaging
+- Public or private communication
+- Template and automation options
+
+**Team Communication:**
+- Internal communication channels
+- Case discussion and collaboration
+- Escalation and coordination
+- Knowledge sharing
+- Team support and resources
+
+### 8.2. Automation and AI
+
+#### 8.2.1. Automated Moderation
+
+**Automation Uses:**
+- Spam detection and filtering
+- Obvious violation detection
+- Content categorisation
+- Queue prioritisation
+- Routine task automation
+
+**Automation Limitations:**
+- Cannot replace human judgement
+- May have false positives or negatives
+- Requires human review for complex cases
+- Needs regular monitoring and adjustment
+- Should support, not replace, human moderators
+
+#### 8.2.2. Human-AI Collaboration
+
+**Effective Collaboration:**
+- AI handles routine tasks
+- Humans handle complex decisions
+- AI supports human decision-making
+- Humans review and correct AI decisions
+- Continuous improvement of both
+
+**Best Practices:**
+- Use automation appropriately
+- Maintain human oversight
+- Review automated decisions
+- Improve automation based on feedback
+- Support human moderators effectively
+
+## 9. SELF-CARE AND PROFESSIONAL DEVELOPMENT
+
+### 9.1. Managing Moderation Workload
+
+#### 9.1.1. Workload Challenges
+
+**Common Challenges:**
+- High volume of content to review
+- Emotional impact of harmful content
+- Decision fatigue from constant decisions
+- Pressure to respond quickly
+- Balancing quality with efficiency
+
+**Impact Management:**
+- Recognise signs of stress or burnout
+- Take breaks and rest regularly
+- Manage workload effectively
+- Seek support when needed
+- Practice self-care
+
+#### 9.1.2. Self-Care Practices
+
+**Individual Self-Care:**
+- Regular breaks and rest
+- Physical exercise and movement
+- Healthy eating and sleep habits
+- Engaging in enjoyable activities
+- Accessing support and counselling
+
+**Professional Self-Care:**
+- Setting boundaries
+- Managing workload
+- Seeking peer support
+- Continuing education
+- Celebrating successes
+
+### 9.2. Professional Development
+
+#### 9.2.1. Skill Development
+
+**Core Skills:**
+- Policy interpretation and application
+- Context analysis and assessment
+- Communication and explanation
+- Documentation and transparency
+- Decision-making and judgement
+
+**Advanced Skills:**
+- Complex case handling
+- Cross-cultural competency
+- Trauma-informed practices
+- De-escalation techniques
+- Leadership and mentoring
+
+#### 9.2.2. Ongoing Learning
+
+**Learning Practices:**
+- Regular training and education
+- Reading about moderation best practices
+- Learning from case studies
+- Participating in discussions
+- Seeking feedback and improvement
+
+**Continuous Improvement:**
+- Review and reflect on decisions
+- Learn from mistakes
+- Update practices based on experience
+- Share knowledge with team
+- Contribute to improvement efforts
+
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 10.1. Scenario 1: Ambiguous Content Report
+
+**Situation**: You receive a report about content that could be interpreted multiple ways. The content might violate a policy, but the context is unclear. The content could be satire, educational, or an actual violation depending on interpretation.
+
+**Your Response:**
+1. How do you assess this ambiguous situation?
+2. What information do you gather?
+3. How do you consider context?
+4. Who do you consult?
+5. How do you make a decision?
+6. How do you document your reasoning?
+
+**Correct Answer**: Gather comprehensive information, consider full context, assess actual policy violation rather than potential interpretation, consult with colleagues for different perspectives, apply moderation principles consistently, document reasoning clearly including context considerations, err on side of caution when uncertain.
+
+### 10.2. Scenario 2: Progressive Enforcement
+
+**Situation**: A user received their first warning for a minor policy violation (low severity). They continue the same behaviour after the warning, posting similar content that violates the same policy.
+
+**Your Response:**
+1. What is the appropriate response to continued violations?
+2. How do you assess severity?
+3. How do you consider the user's history?
+4. What action do you take?
+5. How do you communicate the escalation?
+6. How do you document the progressive enforcement?
+
+**Correct Answer**: Assess continued behaviour as escalation factor. Consider severity (still minor), history (repeat violation after warning), and impact. Escalate to restriction or suspension based on progressive enforcement framework. Communicate clearly why action escalated, reference previous warning, explain consequences of continued violations, provide appeal information, document progressive enforcement clearly.
+
+### 10.3. Scenario 3: User Appeal
+
+**Situation**: A user appeals a moderation action, saying they didn't understand the policy, the action was unfair, and they want it reversed. They provide additional context they say wasn't considered.
+
+**Your Response:**
+1. How do you review this appeal?
+2. What factors do you consider?
+3. How do you assess the original decision?
+4. How do you evaluate new information?
+5. What decision do you make?
+6. How do you communicate your decision?
+
+**Correct Answer**: Review appeal fairly and objectively. Review original decision and evidence, consider user's explanation and new information, assess whether original decision was correct, evaluate if new information changes assessment, make decision based on policy and evidence, communicate decision clearly with reasoning, provide information about further appeal options if applicable.
+
+## 11. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Content Moderation Fundamentals Training document is part of our comprehensive staff development programme designed to ensure effective, fair, and consistent content moderation that maintains safe, welcoming community environments. Content moderation is an ongoing practice that requires skill, judgement, and continuous learning. For questions about content moderation or to report training completion, please contact designated leadership through staff channels.*
+
diff --git a/src/content/docs/staff/training/criminal-activity.md b/src/content/docs/staff/training/criminal-activity.md
new file mode 100644
index 0000000..1f54e20
--- /dev/null
+++ b/src/content/docs/staff/training/criminal-activity.md
@@ -0,0 +1,620 @@
+---
+title: Criminal Activity Training for Staff
+---
+
+**MANDATORY TRAINING FOR ALL TEAM MEMBERS**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides essential guidance for all Team members on recognising, responding to, and managing criminal activity within our community. Team members must be prepared to identify potential criminal activity, respond appropriately, and ensure compliance with legal obligations whilst protecting community members and maintaining platform integrity.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive safety and legal compliance framework:
+
+**(a)** **Community Code of Conduct**: Behavioural expectations and community safety standards;
+
+**(b)** **Content and Moderation Policy**: Enforcement procedures and content restrictions;
+
+**(c)** **Crisis Response Policy**: Emergency response procedures for safety concerns;
+
+**(d)** **Child Safety Policy**: Procedures for protecting minors and reporting child exploitation;
+
+**(e)** **Legal Compliance Requirements**: Mandatory reporting obligations and legal responsibilities;
+
+**(f)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Critical Disclaimer
+
+**REMEMBER: WE ARE NOT LAW ENFORCEMENT PROFESSIONALS**
+
+- We cannot conduct criminal investigations or make legal determinations
+- Our role is limited to recognition, immediate response, evidence preservation, and appropriate escalation
+- We must maintain clear professional boundaries and avoid interfering with law enforcement investigations
+- When in doubt, escalate immediately to senior staff and appropriate authorities
+- Legal reporting obligations may require immediate action regardless of uncertainty
+- Do not attempt to investigate or confront suspected criminals
+
+## 2. UNDERSTANDING CRIMINAL ACTIVITY IN ONLINE COMMUNITIES
+
+### 2.1. Types of Criminal Activity
+
+#### 2.1.1. Violent Crimes and Threats (IMMEDIATE ACTION REQUIRED)
+
+**Threats of Violence:**
+- Direct threats of physical harm to individuals or groups
+- Threats of mass violence or terrorism
+- Threats involving weapons or explosives
+- Threats targeting specific individuals or locations
+- Threats made in response to conflicts or disputes
+
+**Stalking and Harassment:**
+- Persistent unwanted contact that causes fear
+- Tracking or monitoring of individuals without consent
+- Threats combined with unwanted contact
+- Pattern of harassment that escalates to threats
+- Cyberstalking behaviours targeting community members
+
+**Doxxing and Privacy Violations:**
+- Unauthorized release of personal identifying information
+- Publishing addresses, phone numbers, or other private information
+- Attempts to locate or identify individuals without consent
+- Sharing information intended to enable harassment or harm
+- Coercion through threat of information release
+
+#### 2.1.2. Financial Crimes (ESCALATE WITHIN 15 MINUTES)
+
+**Fraud and Scams:**
+- Phishing attempts targeting community members
+- Advance fee fraud schemes
+- Investment scams and Ponzi schemes
+- Romance scams and catfishing
+- Impersonation for financial gain
+
+**Money Laundering:**
+- Suspicious financial transactions or requests
+- Attempts to move funds through community platforms
+- Requests for payment in unusual forms (gift cards, cryptocurrency)
+- Patterns suggesting money laundering operations
+- Connections between accounts suggesting criminal networks
+
+**Theft and Identity Theft:**
+- Unauthorized access to accounts or information
+- Identity theft attempts
+- Credit card fraud or unauthorized charges
+- Account takeover attempts
+- Social engineering for financial gain
+
+#### 2.1.3. Cybercrime (ESCALATE WITHIN 15 MINUTES)
+
+**Hacking and Unauthorized Access:**
+- Attempts to gain unauthorized access to systems
+- Distribution of hacking tools or instructions
+- Account compromise attempts
+- Malware distribution
+- Denial of service attack planning or execution
+
+**Data Breaches:**
+- Unauthorized access to user data
+- Attempts to extract or sell user information
+- Breaches of platform security
+- Distribution of stolen credentials
+- Sale of compromised accounts
+
+**Online Exploitation:**
+- Sextortion schemes
+- Revenge porn distribution
+- Non-consensual image sharing
+- Coercion through digital means
+- Exploitation of vulnerable individuals
+
+#### 2.1.4. Illegal Content Distribution (ESCALATE WITHIN 15 MINUTES)
+
+**Copyright Infringement:**
+- Distribution of pirated software, media, or content
+- Large-scale copyright violation operations
+- Commercial piracy activities
+- Distribution of cracked software or media
+- Organised piracy networks
+
+**Illegal Material:**
+- Distribution of illegal drugs or substances
+- Sale of illegal goods or services
+- Distribution of weapons or weapon components
+- Human trafficking indicators or advertisements
+- Other illegal goods or services
+
+#### 2.1.5. Extremism and Terrorism (IMMEDIATE ACTION REQUIRED)
+
+**Terrorist Content:**
+- Content promoting or glorifying terrorism
+- Recruitment materials for terrorist organisations
+- Instructions for carrying out attacks
+- Threats of terrorist activity
+- Material supporting designated terrorist organisations
+
+**Extremist Activity:**
+- Content promoting violent extremism
+- Recruitment for extremist groups
+- Planning or coordination of extremist activities
+- Distribution of extremist propaganda
+- Radicalization attempts targeting community members
+
+### 2.2. Recognising Criminal Activity Patterns
+
+#### 2.2.1. Behavioural Indicators
+
+**Suspicious Communication Patterns:**
+- Rapid account creation and deletion
+- Use of multiple accounts for similar purposes
+- Evasive responses to questions about identity or purpose
+- Inconsistent information across interactions
+- Attempts to avoid verification or identification
+
+**Coordination Indicators:**
+- Multiple accounts coordinating activities
+- Organised campaigns or operations
+- Network of accounts working together
+- Rapid spread of criminal content or schemes
+- Patterns suggesting organised criminal activity
+
+#### 2.2.2. Content Indicators
+
+**Red Flag Language:**
+- Requests for personal or financial information
+- Pressure to act quickly or keep things secret
+- Requests to move conversations to private platforms
+- Offers that seem too good to be true
+- Threats or coercion attempts
+
+**Suspicious Requests:**
+- Requests for money or financial assistance
+- Requests for personal identifying information
+- Requests to share accounts or credentials
+- Requests to participate in suspicious activities
+- Requests to keep activities secret from others
+
+## 3. IMMEDIATE RESPONSE PROCEDURES
+
+### 3.1. Violent Crimes and Threats Response Protocol
+
+**IMMEDIATE ACTIONS (Within 5 minutes):**
+
+1. **DO NOT DELAY** - Threats of violence require immediate action
+2. **PRESERVE EVIDENCE** - Screenshot all relevant communications immediately
+3. **ESCALATE IMMEDIATELY** - Notify senior staff and security coordinator in staff chat
+4. **DO NOT CONFRONT** - Do not directly confront suspected perpetrators
+5. **PROTECT TARGETS** - Ensure potential targets are notified and protected
+6. **DOCUMENT EVERYTHING** - Record all relevant information whilst it's fresh
+7. **CONTACT AUTHORITIES** - Report to law enforcement if threat appears credible
+
+**Example Response Template:**
+```
+URGENT CRIMINAL ACTIVITY CONCERN - THREAT OF VIOLENCE
+
+[Brief description of threat]
+[User IDs involved]
+[Platform/channel where threat occurred]
+[Time and date]
+[Target information if known]
+[Screenshots attached]
+
+Escalating immediately to security coordinator and senior staff.
+Law enforcement notification recommended.
+```
+
+### 3.2. Financial Crimes Response Protocol
+
+**ACTIONS (Within 15 minutes):**
+
+1. **PRESERVE EVIDENCE** - Document and preserve all relevant communications and transactions
+2. **PROTECT VICTIMS** - Notify potential victims and provide support resources
+3. **REMOVE CONTENT** - Remove fraudulent content from public view immediately
+4. **ESCALATE** - Notify security coordinator and senior staff
+5. **DOCUMENT** - Create comprehensive documentation of the incident
+6. **REPORT** - Report to appropriate authorities (FBI Internet Crime Complaint Center, local law enforcement)
+7. **FOLLOW UP** - Ensure appropriate follow-up actions are taken
+
+**Example Response Template:**
+```
+CRIMINAL ACTIVITY CONCERN - FINANCIAL FRAUD
+
+[Description of fraudulent activity]
+[User IDs involved]
+[Platform/channel where activity occurred]
+[Time and date]
+[Victim information if known]
+[Screenshots and evidence attached]
+
+Escalating to security coordinator. Reporting to appropriate authorities.
+```
+
+### 3.3. Cybercrime Response Protocol
+
+**ACTIONS (Within 15 minutes):**
+
+1. **SECURE SYSTEMS** - Take immediate steps to secure affected systems
+2. **PRESERVE EVIDENCE** - Document all evidence of cybercrime activity
+3. **PROTECT USERS** - Notify affected users and provide security guidance
+4. **ESCALATE** - Notify security coordinator and technical team immediately
+5. **DOCUMENT** - Create comprehensive documentation of the incident
+6. **REPORT** - Report to appropriate cybercrime authorities
+7. **MITIGATE** - Take steps to prevent further damage or spread
+
+### 3.4. Illegal Content Distribution Response Protocol
+
+**ACTIONS (Within 15 minutes):**
+
+1. **REMOVE CONTENT** - Immediately remove illegal content from public view
+2. **PRESERVE EVIDENCE** - Document and preserve evidence for authorities
+3. **ESCALATE** - Notify security coordinator and senior staff
+4. **DOCUMENT** - Create comprehensive documentation of the incident
+5. **REPORT** - Report to appropriate authorities (copyright holders, law enforcement)
+6. **FOLLOW UP** - Ensure appropriate follow-up actions are taken
+
+### 3.5. Extremism and Terrorism Response Protocol
+
+**IMMEDIATE ACTIONS (Within 5 minutes):**
+
+1. **DO NOT DELAY** - Extremist content requires immediate action
+2. **REMOVE CONTENT** - Immediately remove extremist content
+3. **PRESERVE EVIDENCE** - Document and preserve all evidence
+4. **ESCALATE** - Notify security coordinator and senior staff immediately
+5. **REPORT** - Report to appropriate counter-terrorism authorities
+6. **PROTECT COMMUNITY** - Take steps to protect community members from radicalization
+7. **DOCUMENT** - Create comprehensive documentation
+
+## 4. LEGAL OBLIGATIONS AND REPORTING REQUIREMENTS
+
+### 4.1. Mandatory Reporting Obligations
+
+#### 4.1.1. When Reporting Is Required
+
+**Legal Requirements:**
+- **Threats of Violence**: Credible threats of violence must be reported to law enforcement
+- **Child Exploitation**: Any suspected child exploitation must be reported (see Child Safety Policy)
+- **Terrorism**: Content promoting terrorism or terrorist activities must be reported
+- **Financial Crimes**: Significant financial crimes may require reporting to financial authorities
+- **Cybercrime**: Serious cybercrime may require reporting to cybercrime units
+- **Data Breaches**: Data breaches may require reporting to data protection authorities
+
+**Jurisdictional Considerations:**
+- Reporting requirements vary by jurisdiction
+- Some crimes require reporting in multiple jurisdictions
+- International crimes may require reporting to multiple agencies
+- When in doubt, consult with legal counsel and report
+- Different types of crimes require reporting to different agencies
+
+#### 4.1.2. How to Report
+
+**Internal Reporting:**
+1. **Immediate Escalation**: Notify security coordinator and senior staff immediately
+2. **Documentation**: Provide comprehensive documentation of concerns
+3. **Follow Procedures**: Follow established internal reporting procedures
+4. **Coordination**: Coordinate with other Team members as appropriate
+
+**External Reporting:**
+- **Law Enforcement**: Report to local law enforcement for violent crimes and threats
+- **FBI Internet Crime Complaint Center (IC3)**: Report cybercrime and online fraud
+- **National Center for Missing & Exploited Children (NCMEC)**: Report child exploitation
+- **Counter-Terrorism Authorities**: Report terrorism-related content
+- **Financial Authorities**: Report significant financial crimes
+- **Legal Counsel**: Consult with legal counsel for guidance on reporting obligations
+
+### 4.2. Documentation Requirements
+
+#### 4.2.1. Essential Information to Document
+
+**Incident Details:**
+- **Date and Time**: Exact date and time of incident or discovery
+- **Platform and Location**: Where the incident occurred
+- **Parties Involved**: All user IDs and any known identifying information
+- **Content**: Screenshots, logs, and descriptions of all relevant content
+- **Actions Taken**: All actions taken in response to the incident
+- **Evidence**: All preserved evidence and documentation
+
+**Context Information:**
+- **Historical Context**: Any previous interactions or concerns involving the parties
+- **Witnesses**: Any other staff or community members who witnessed the incident
+- **Victim Information**: Information about any victims (whilst respecting privacy)
+- **Risk Assessment**: Assessment of immediate and ongoing risk
+- **Follow-up Plans**: Planned follow-up actions and monitoring
+
+#### 4.2.2. Evidence Preservation
+
+**Preservation Requirements:**
+- **Screenshots**: Take screenshots of all relevant content immediately
+- **Logs**: Preserve all relevant logs and system records
+- **Communications**: Preserve all relevant communications and messages
+- **Metadata**: Preserve metadata when possible (timestamps, IP addresses, etc.)
+- **Chain of Custody**: Maintain clear chain of custody for all evidence
+
+**Legal Considerations:**
+- **Admissibility**: Ensure evidence is preserved in a way that maintains admissibility
+- **Privacy**: Balance evidence preservation with privacy requirements
+- **Retention**: Follow legal requirements for evidence retention
+- **Access Controls**: Limit access to evidence to authorized personnel only
+- **Legal Holds**: Preserve evidence when legal action is possible
+
+## 5. ESCALATION PROCEDURES
+
+### 5.1. When to Escalate
+
+**ALWAYS ESCALATE IMMEDIATELY:**
+- Any threat of violence
+- Any suspected child exploitation
+- Any terrorism-related content
+- Any credible threat to community safety
+- Any significant financial crime
+- Any serious cybercrime
+- Any situation where you feel uncertain about appropriate response
+
+### 5.2. How to Escalate
+
+**Internal Escalation:**
+1. **Staff Chat Alert**: Post urgent alert in staff chat with @security-coordinator
+2. **Direct Contact**: Contact security coordinator directly if available
+3. **Senior Staff Notification**: Notify senior staff and leadership immediately
+4. **Documentation**: Provide all documentation and context immediately
+5. **Follow Instructions**: Follow any specific directions from senior staff
+
+**Emergency Escalation:**
+- **Immediate Danger**: Contact emergency services if there is immediate physical danger
+- **@Naomi Alert**: Alert @Naomi immediately for critical situations
+- **Legal Counsel**: Consult legal counsel for guidance on reporting obligations
+- **External Authorities**: Report to appropriate law enforcement or regulatory agencies
+
+### 5.3. Escalation Chain
+
+**Standard Escalation:**
+1. Security Coordinator
+2. Senior Staff / Leadership
+3. Legal Counsel (if needed)
+4. External Authorities (as required by law)
+
+**Emergency Escalation:**
+1. Emergency Services (if immediate physical danger)
+2. Security Coordinator
+3. Senior Staff / Leadership
+4. Legal Counsel
+5. External Authorities
+
+## 6. COMMUNICATION AND COORDINATION
+
+### 6.1. Communicating with Victims
+
+#### 6.1.1. Victim Support
+
+**Do's:**
+- **Believe and Validate**: Believe victims and validate their experiences
+- **Provide Support**: Connect victims with appropriate support resources
+- **Explain Process**: Explain what will happen next in clear language
+- **Maintain Privacy**: Respect victim privacy and confidentiality
+- **Provide Resources**: Share resources for reporting to authorities and getting help
+
+**Don'ts:**
+- **Don't Investigate**: Do not attempt to conduct your own investigation
+- **Don't Promise Outcomes**: Do not promise specific outcomes or consequences
+- **Don't Minimise**: Do not minimise the seriousness of the crime
+- **Don't Blame**: Do not suggest the victim did anything wrong
+- **Don't Share Details**: Do not share details about actions taken against perpetrators
+
+#### 6.1.2. Resource Connection
+
+**Support Resources:**
+- **Law Enforcement**: Information about reporting to law enforcement
+- **Victim Support Services**: Connect with victim support organisations
+- **Legal Resources**: Information about legal options and resources
+- **Counselling Services**: Connect with counselling and mental health resources
+- **Financial Recovery**: Resources for financial crime victims
+
+### 6.2. Coordinating with Authorities
+
+#### 6.2.1. Law Enforcement Cooperation
+
+**When Working with Law Enforcement:**
+- **Follow Legal Requirements**: Comply with all legal requirements and orders
+- **Preserve Evidence**: Ensure all evidence is properly preserved
+- **Provide Information**: Provide requested information within legal boundaries
+- **Maintain Boundaries**: Maintain appropriate boundaries and avoid interfering with investigations
+- **Document Interactions**: Document all interactions with law enforcement
+
+**Legal Considerations:**
+- **Warrants and Subpoenas**: Comply with legal warrants and subpoenas
+- **Privacy Rights**: Balance compliance with user privacy rights
+- **Legal Counsel**: Consult legal counsel when dealing with law enforcement requests
+- **Documentation**: Maintain documentation of all law enforcement interactions
+- **User Notification**: Notify users of law enforcement requests when legally required
+
+#### 6.2.2. Platform Security Coordination
+
+**Internal Coordination:**
+- **Security Team**: Coordinate with security team for technical responses
+- **Legal Team**: Coordinate with legal team for compliance and reporting
+- **Senior Leadership**: Keep senior leadership informed of significant incidents
+- **Cross-Platform**: Coordinate with other platforms when appropriate
+- **Documentation**: Ensure all teams have necessary information
+
+## 7. PREVENTION STRATEGIES
+
+### 7.1. Community Safety Measures
+
+#### 7.1.1. Detection and Monitoring
+
+**Proactive Monitoring:**
+- Monitor for patterns of criminal activity
+- Use automated tools to detect suspicious behavior
+- Regular review of high-risk areas and interactions
+- Pattern recognition for common criminal schemes
+- Regular security audits and assessments
+
+**Community Education:**
+- Provide education about common scams and frauds
+- Share information about recognising criminal activity
+- Educate community members about online safety
+- Provide resources for reporting suspicious activity
+- Regular reminders about security best practices
+
+#### 7.1.2. Access Controls and Verification
+
+**Account Security:**
+- Implement appropriate account verification measures
+- Monitor for suspicious account creation patterns
+- Implement rate limiting and access controls
+- Regular review of account security measures
+- Quick response to account compromise reports
+
+**Content Controls:**
+- Automated detection of suspicious content
+- Manual review of flagged content
+- Quick removal of criminal content
+- Prevention of content re-upload
+- Regular review of content moderation effectiveness
+
+### 7.2. Staff Training and Preparedness
+
+#### 7.2.1. Ongoing Training
+
+**Regular Updates:**
+- Quarterly criminal activity training updates
+- Regular review of new criminal schemes and patterns
+- Updates on legal reporting requirements
+- Training on new platforms and security features
+- Case study reviews and learning sessions
+
+**Skill Development:**
+- Recognition of criminal activity patterns
+- Appropriate response procedures
+- Evidence preservation best practices
+- Documentation requirements
+- Legal compliance and reporting
+
+#### 7.2.2. Policy and Process Improvement
+
+**Continuous Improvement:**
+- Regular review of criminal activity policies
+- Updates based on new threats and patterns
+- Improvement of detection and response procedures
+- Enhancement of prevention measures
+- Integration of community feedback
+
+## 8. SELF-CARE AND EMOTIONAL SUPPORT
+
+### 8.1. Managing the Emotional Impact
+
+#### 8.1.1. Understanding the Impact
+
+**Emotional Demands:**
+- Exposure to criminal activity can be distressing and traumatic
+- Supporting victims of crime requires emotional resilience
+- Dealing with threats and violence can be frightening
+- Maintaining professional boundaries whilst providing support can be difficult
+- Repeated exposure can lead to secondary trauma and burnout
+
+**Signs of Emotional Strain:**
+- **Physical Symptoms**: Fatigue, headaches, sleep disturbances, tension
+- **Emotional Symptoms**: Anxiety, fear, anger, emotional numbness
+- **Professional Symptoms**: Decreased effectiveness, avoidance, difficulty making decisions
+- **Personal Symptoms**: Relationship strain, social withdrawal, loss of interest in activities
+
+#### 8.1.2. Self-Care Strategies
+
+**During Incidents:**
+- **Take Breaks**: Take breaks when needed during difficult situations
+- **Seek Support**: Reach out to colleagues or supervisors for support
+- **Maintain Boundaries**: Remember your role and maintain professional boundaries
+- **Focus on Impact**: Remember the positive impact of protecting community members
+
+**Between Incidents:**
+- **Debriefing**: Participate in debriefing sessions after difficult incidents
+- **Professional Support**: Access counselling or professional support when needed
+- **Restoration**: Engage in activities that restore emotional equilibrium
+- **Reflection**: Regular self-reflection on emotional responses and needs
+
+### 8.2. Support Systems
+
+#### 8.2.1. Team Support
+
+**Peer Support:**
+- Regular check-ins with colleagues working on criminal activity response
+- Debriefing sessions after difficult incidents
+- Sharing successful strategies and lessons learned
+- Mutual support and understanding
+- Celebration of positive outcomes
+
+**Supervisory Support:**
+- Regular meetings with supervisors to discuss challenges
+- Access to additional resources and support
+- Workload management and distribution
+- Recognition of difficult work
+- Professional development opportunities
+
+#### 8.2.2. Professional Resources
+
+**Mental Health Support:**
+- Access to counselling and mental health resources
+- Support groups for professionals working in security and safety
+- Trauma-informed therapy resources
+- Crisis support when needed
+- Ongoing mental health maintenance
+
+**Professional Development:**
+- Training on trauma-informed practices
+- Education on secondary trauma and burnout prevention
+- Skills development for managing difficult situations
+- Access to professional resources and networks
+- Career development support
+
+## 9. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 9.1. Scenario 1: Threat of Violence
+
+**Situation**: A community member posts a detailed threat of violence targeting a specific individual, including specific location and time information. The threat appears to be in response to a personal dispute.
+
+**Your Response:**
+1. What risk level is this?
+2. What immediate actions should you take?
+3. What evidence should you preserve?
+4. Who should you escalate to?
+5. Should law enforcement be contacted?
+
+**Correct Answer**: High-risk situation requiring immediate escalation. Preserve all evidence, notify security coordinator immediately, contact law enforcement, and ensure the potential target is notified and protected.
+
+### 9.2. Scenario 2: Financial Fraud Scheme
+
+**Situation**: Multiple community members report receiving messages from an account claiming to be a Team member, requesting gift cards or cryptocurrency payments to resolve account issues. The messages include urgent language and threats of account suspension.
+
+**Your Response:**
+1. What type of criminal activity is this?
+2. What immediate actions are required?
+3. How do you protect potential victims?
+4. What documentation is needed?
+5. What reporting obligations exist?
+
+### 9.3. Scenario 3: Suspicious Account Activity
+
+**Situation**: You notice a pattern of accounts being created, used to send suspicious messages requesting personal information, and then deleted. The accounts appear to be part of a coordinated operation targeting community members.
+
+**Your Response:**
+1. What criminal activity indicators are present?
+2. How do you investigate without interfering with potential law enforcement investigation?
+3. What evidence should be preserved?
+4. What prevention measures should be implemented?
+5. When should authorities be notified?
+
+## 10. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Criminal Activity Training document is part of our comprehensive Team development programme designed to ensure appropriate recognition and response to criminal activity whilst protecting community members and maintaining legal compliance. Criminal activity response is critical to community safety, and all Team members must complete this training before assuming moderation responsibilities. For questions about criminal activity procedures or to report training completion, please contact the Security Coordinator through designated Team channels.*
+
diff --git a/src/content/docs/staff/training/crisis-response.md b/src/content/docs/staff/training/crisis-response.md
index bf26532..a85da21 100644
--- a/src/content/docs/staff/training/crisis-response.md
+++ b/src/content/docs/staff/training/crisis-response.md
@@ -2,13 +2,13 @@
 title: Crisis Response Training for Staff
 ---
 
-**MANDATORY TRAINING FOR ALL STAFF MEMBERS**
+**MANDATORY TRAINING FOR ALL TEAM MEMBERS**
 
 ## 1. INTRODUCTION AND SCOPE
 
 ### 1.1. Purpose of This Training
 
-This training document provides essential guidance for all staff members on recognising, responding to, and managing mental health crises and emergency situations within our community. This training is mandatory for all staff members and must be completed before assuming moderation responsibilities.
+This training document provides essential guidance for all Team members on recognising, responding to, and managing mental health crises and emergency situations within our community. This training is mandatory for all Team members and must be completed before assuming moderation responsibilities.
 
 ### 1.2. Integration with Existing Policies
 
@@ -35,7 +35,7 @@ This training operates within our comprehensive crisis management framework:
 
 ### 2.1. Understanding Crisis Indicators
 
-Staff members must be able to identify potential crisis situations. Learn to recognise these indicators:
+Team members must be able to identify potential crisis situations. Learn to recognise these indicators:
 
 #### 2.1.1. High-Risk Indicators (IMMEDIATE ACTION REQUIRED)
 
@@ -129,7 +129,7 @@ I'm getting additional support for you right now."
 
 **Example Response Template:**
 ```
-"Thank you for sharing this with us. It sounds like you're going through a really difficult time. While I can't provide professional counseling, I want to connect you with resources that can help:
+"Thank you for sharing this with us. It sounds like you're going through a really difficult time. While I can't provide professional counselling, I want to connect you with resources that can help:
 
 [List appropriate resources based on user's location if known]
 
@@ -157,6 +157,8 @@ Taking care of your mental health is really important. Have you considered reach
 
 ## 4. ESCALATION PROCEDURES
 
+**Reference to Comprehensive Escalation Procedures**: For universal escalation principles and general escalation procedures, see [Escalation Protocol](/staff/handbook#253-escalation-protocol) in the Staff Handbook. This section provides crisis-specific escalation steps.
+
 ### 4.1. When to Escalate
 
 **ALWAYS ESCALATE:**
@@ -302,19 +304,29 @@ Taking care of your mental health is really important. Have you considered reach
 
 ## 8. SELF-CARE FOR STAFF
 
-### 8.1. Emotional Impact Management
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides crisis-response-specific considerations; refer to the self-care resources document for comprehensive guidance.
 
-**Crisis work can be emotionally demanding:**
-- Recognise signs of burnout or compassion fatigue
-- Use debriefing sessions after difficult situations
-- Set appropriate boundaries between work and personal life
-- Seek support when needed
+### 8.1. Crisis Response-Specific Self-Care Considerations
+
+**Additional Considerations for Crisis Work:**
+- Increased risk of secondary trauma from exposure to crisis situations
+- Need for immediate debriefing after difficult crisis responses
+- Regular check-ins with Crisis Response Coordinator
+- Access to professional mental health support
+- Clear boundaries about when to step back from crisis work
+
+**Self-Care Practices:**
+- Debrief immediately after crisis situations
+- Limit exposure to crisis content when possible
+- Take breaks between crisis responses
+- Use grounding techniques when feeling overwhelmed
+- Access professional support when needed
 
 ### 8.2. Available Support Systems
 
-**For Staff Members:**
-- Peer support through staff channels
-- Debriefing sessions with senior staff
+**For Team Members:**
+- Peer support through Team channels
+- Debriefing sessions with senior Team members
 - Access to counselling resources
 - Flexibility to step back when needed
 
@@ -360,37 +372,15 @@ Taking care of your mental health is really important. Have you considered reach
 3. When would you escalate?
 4. How do you balance artistic expression with safety concerns?
 
-## 10. CERTIFICATION REQUIREMENTS
+## 10. TRAINING REQUIREMENTS
 
-### 10.1. Training Completion
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
 
-To complete this crisis response training, staff members must:
-
-1. **Read this document thoroughly**
-2. **Complete practice scenarios** with senior staff review
-3. **Demonstrate resource knowledge** in mock situations
-4. **Show understanding of escalation procedures**
-5. **Acknowledge understanding of limitations and boundaries**
-
-### 10.2. Ongoing Requirements
-
-**Quarterly:**
-- Participate in crisis response refresher sessions
-- Review updated resources and procedures
-- Practice scenarios with team members
-
-**Annually:**
-- Complete comprehensive crisis response assessment
-- Update resource knowledge
-- Participate in advanced training sessions
-
-### 10.3. Documentation
-
-All crisis response training completion and updates must be documented in staff records for:
-- Accountability and quality assurance
-- Legal compliance requirements
-- Performance evaluation purposes
-- Continuous improvement tracking
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records
 
 ---
 
diff --git a/src/content/docs/staff/training/cross-platform-coordination.md b/src/content/docs/staff/training/cross-platform-coordination.md
index ced5406..7873c6e 100644
--- a/src/content/docs/staff/training/cross-platform-coordination.md
+++ b/src/content/docs/staff/training/cross-platform-coordination.md
@@ -2,13 +2,13 @@
 title: Cross-Platform Coordination Training for Staff
 ---
 
-**ESSENTIAL TRAINING FOR MULTI-PLATFORM STAFF MEMBERS**
+**ESSENTIAL TRAINING FOR MULTI-PLATFORM TEAM MEMBERS**
 
 ## 1. INTRODUCTION AND SCOPE
 
 ### 1.1. Purpose and Importance
 
-This training provides guidance for staff members who work across multiple platforms within our community ecosystem. Cross-platform coordination is essential for creating a cohesive community experience while respecting the unique characteristics and requirements of each platform.
+This training provides guidance for Team members who work across multiple platforms within our community ecosystem. Cross-platform coordination is essential for creating a cohesive community experience whilst respecting the unique characteristics and requirements of each platform.
 
 ### 1.2. Multi-Platform Community Structure
 
@@ -66,7 +66,7 @@ This training operates within our policy framework:
 
 ### 2.3. Consistent User Experience
 
-**User Expectation**: Community members should feel they're interacting with the same organisation regardless of platform, while experiencing platform-appropriate features and workflows.
+**User Expectation**: Community members should feel they're interacting with the same organisation regardless of platform, whilst experiencing platform-appropriate features and workflows.
 
 ## 3. UNDERSTANDING PLATFORM-SPECIFIC CHARACTERISTICS
 
@@ -233,7 +233,7 @@ This training operates within our policy framework:
 **Platform Adaptations:**
 - Adjust formality level to platform norms
 - Use platform-specific features appropriately
-- Respect platform culture while maintaining standards
+- Respect platform culture whilst maintaining standards
 - Adapt communication style to audience expectations
 
 #### 4.3.2. Cross-Platform User Support
@@ -324,7 +324,7 @@ This training operates within our policy framework:
 ### 6.2. Forum-Specific Responsibilities
 
 #### 6.2.1. Content Curation
-- Organize and categorise discussion topics
+- Organise and categorise discussion topics
 - Create informative and educational content
 - Moderate long-form discussions and debates
 - Maintain knowledge base and FAQ resources
@@ -333,7 +333,7 @@ This training operates within our policy framework:
 - **Thread Management**: Move, merge, and organise discussion threads
 - **User Management**: Handle user accounts, permissions, and restrictions
 - **Content Tools**: Edit, format, and enhance community-generated content
-- **Search and Organization**: Maintain findable, well-organised content
+- **Search and Organisation**: Maintain findable, well-organised content
 
 ### 6.3. Repository-Specific Responsibilities
 
@@ -390,7 +390,7 @@ This training operates within our policy framework:
 
 **Solutions:**
 - Reasonable workload distribution and rotation
-- Specialization with cross-training for coverage
+- Specialisation with cross-training for coverage
 - Clear boundaries and scope definitions
 - Support systems and wellness programmes
 
@@ -545,61 +545,65 @@ This training operates within our policy framework:
 - Best practice sharing and knowledge transfer
 - Professional development and training requests
 
-## 10. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 10.1. Cross-Platform Coordinator Qualifications
+### 10.1. Scenario 1: Cross-Platform Crisis Coordination
 
-#### 10.1.1. Required Competencies
+**Situation**: A crisis situation occurs that affects multiple platforms simultaneously. The crisis involves a safety threat that's being discussed across Discord, forums, and social media. Information is spreading rapidly and inconsistently across platforms.
 
-**Technical Skills:**
-- Proficiency with all relevant platforms and their moderation tools
-- Understanding of platform-specific features and limitations
-- Ability to adapt communication style to different platform cultures
-- Knowledge of integration tools and coordination systems
+**Your Response:**
+1. How do you coordinate response across all platforms?
+2. How do you ensure consistent messaging?
+3. How do you share information appropriately between platforms?
+4. How do you prevent misinformation from spreading?
+5. How do you coordinate with platform-specific staff?
+6. How do you ensure comprehensive response?
 
-**Communication Skills:**
-- Clear, consistent messaging across different contexts
-- Cultural sensitivity and inclusive communication practices
-- Crisis communication and de-escalation abilities
-- Professional representation of community values
+**Correct Answer**: Coordinate immediately with all platform teams, ensure consistent messaging across platforms, share information appropriately whilst respecting platform contexts, prevent misinformation through coordinated communication, work closely with platform-specific staff, ensure comprehensive response that addresses crisis on all platforms.
 
-**Leadership Skills:**
-- Team coordination and collaboration capabilities
-- Problem-solving and decision-making under pressure
-- Conflict resolution and mediation skills
-- Mentoring and training abilities for platform-specific staff
+### 10.2. Scenario 2: Policy Inconsistency Report
 
-#### 10.1.2. Training Requirements
+**Situation**: A community member reports that the same behaviour resulted in different moderation actions on different platforms. They received a warning on Discord but were banned on the forum for the same behaviour. They're confused and feel the moderation is inconsistent.
 
-**Foundation Training:**
-- Complete all platform-specific training modules
-- Demonstrate competency in each platform's moderation tools
-- Pass assessment on cross-platform policy consistency
-- Complete crisis response and inclusive moderation training
+**Your Response:**
+1. How do you investigate this inconsistency?
+2. How do you determine if different actions were appropriate?
+3. How do you address the community member's concern?
+4. How do you ensure consistency going forward?
+5. How do you coordinate policy application across platforms?
+6. How do you communicate about platform-specific considerations?
 
-**Advanced Training:**
-- Cross-platform event coordination and management
-- Advanced crisis response and multi-platform coordination
-- Leadership and mentoring skills for cross-platform teams
-- Continuous education on emerging platforms and technologies
+**Correct Answer**: Investigate both actions, assess if platform-specific context justified different actions, address community member concern transparently, ensure consistent policy application whilst recognising valid platform differences, coordinate policy application across platforms, communicate clearly about consistency and platform considerations.
 
-### 10.2. Performance Standards and Evaluation
+### 10.3. Scenario 3: Cross-Platform Event Coordination
 
-#### 10.2.1. Regular Assessment Framework
+**Situation**: The community is planning a major event that will happen across multiple platforms simultaneously. The event involves Discord voice channels, forum discussions, social media promotion, and GitHub collaboration. Coordination is complex and requires seamless experience.
 
-**Quarterly Performance Reviews:**
-- Cross-platform coordination effectiveness evaluation
-- Community feedback integration and response assessment
-- Policy consistency and adaptation quality review
-- Professional development progress and goal setting
+**Your Response:**
+1. How do you coordinate event logistics across platforms?
+2. How do you ensure consistent experience?
+3. How do you manage communication across platforms?
+4. How do you handle technical issues on different platforms?
+5. How do you coordinate staff support?
+6. How do you ensure event success across all platforms?
 
-**Annual Comprehensive Assessment:**
+**Correct Answer**: Plan event logistics comprehensively, coordinate with all platform teams, ensure consistent experience and messaging, manage communication channels effectively, prepare for technical issues, coordinate staff support across platforms, monitor event across all platforms, ensure seamless experience.
+
+## 11. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 - 360-degree feedback from community members and staff across platforms
 - Cross-platform initiative leadership and success evaluation
 - Crisis response and complex situation management assessment
 - Long-term strategic thinking and community building contribution
 
-#### 10.2.2. Continuous Development Requirements
+#### 11.2.2. Continuous Development Requirements
 
 **Ongoing Learning:**
 - Monthly platform update training and adaptation
diff --git a/src/content/docs/staff/training/data-analytics-reporting.md b/src/content/docs/staff/training/data-analytics-reporting.md
index 4612bf4..1c72782 100644
--- a/src/content/docs/staff/training/data-analytics-reporting.md
+++ b/src/content/docs/staff/training/data-analytics-reporting.md
@@ -2,13 +2,13 @@
 title: Data Analytics and Reporting Training for Staff
 ---
 
-**SPECIALIZED TRAINING FOR DATA AND ANALYTICS COORDINATORS**
+**SPECIALISED TRAINING FOR DATA AND ANALYTICS COORDINATORS**
 
 ## 1. INTRODUCTION AND SCOPE
 
 ### 1.1. Purpose and Strategic Importance
 
-This training provides comprehensive guidance for staff members serving as Data and Analytics Coordinators within our community ecosystem. Data analytics plays a crucial role in understanding community health, measuring progress toward our social justice goals, and making evidence-based decisions that better serve marginalised community members.
+This training provides comprehensive guidance for Team members serving as Data and Analytics Coordinators within our community ecosystem. Data analytics plays a crucial role in understanding community health, measuring progress towards our social justice goals, and making evidence-based decisions that better serve marginalised community members.
 
 ### 1.2. Data and Analytics Coordinator Responsibilities
 
@@ -50,7 +50,7 @@ This training provides comprehensive guidance for staff members serving as Data
 **Community Health Indicators:**
 - **Satisfaction Metrics**: Community member satisfaction with platforms, services, and experiences
 - **Retention Rates**: Member retention and factors affecting long-term engagement
-- **Support Utilization**: Usage of community support services and resources
+- **Support Utilisation**: Usage of community support services and resources
 - **Conflict and Resolution**: Frequency and types of conflicts, and resolution effectiveness
 
 #### 2.1.2. Data Collection Ethics
@@ -339,10 +339,10 @@ This training provides comprehensive guidance for staff members serving as Data
 - **Data Pipeline Automation**: Automated data processing and analysis pipelines
 - **Quality Assurance**: Automated quality assurance checks in data processing
 
-**Workflow Optimization:**
+**Workflow Optimisation:**
 - **Process Automation**: Automation of routine data processing and analysis tasks
 - **Template Development**: Development of templates and frameworks for common analyses
-- **Collaboration Tools**: Tools for collaborating on data analysis with other staff members
+- **Collaboration Tools**: Tools for collaborating on data analysis with other Team members
 - **Documentation Automation**: Automated documentation of data processing and analysis procedures
 
 ## 7. REPORTING AND COMMUNICATION
@@ -433,7 +433,7 @@ This training provides comprehensive guidance for staff members serving as Data
 - **Cloud Platforms**: Experience with cloud-based analytics platforms and tools
 - **API Integration**: Skills in integrating with various APIs for data collection
 
-**Specialized Tools:**
+**Specialised Tools:**
 - **Business Intelligence**: Experience with business intelligence and dashboard tools
 - **Survey Platforms**: Proficiency with survey platforms and data collection tools
 - **Version Control**: Use of version control systems for code and analysis documentation
@@ -453,7 +453,7 @@ This training provides comprehensive guidance for staff members serving as Data
 - **Accuracy and Integrity**: Maintaining the highest standards of accuracy and integrity in data analysis
 - **Confidentiality**: Protecting confidential information and respecting privacy
 - **Competence**: Maintaining and developing professional competence in data analysis
-- **Objectivity**: Maintaining objectivity while acknowledging the value-driven nature of community work
+- **Objectivity**: Maintaining objectivity whilst acknowledging the value-driven nature of community work
 
 #### 8.2.2. Continuous Learning and Development
 
@@ -469,67 +469,59 @@ This training provides comprehensive guidance for staff members serving as Data
 - **Conference Participation**: Regular participation in relevant conferences and professional development
 - **Peer Learning**: Engaging in peer learning and knowledge sharing with other data professionals
 
-## 9. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 9. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 9.1. Data and Analytics Coordinator Competencies
+### 9.1. Scenario 1: Privacy-Compliant Data Collection
 
-#### 9.1.1. Essential Skills Assessment
+**Situation**: You need to collect data to analyse community engagement patterns, but you're concerned about privacy compliance. The data collection involves tracking user activity, participation patterns, and demographic information for equity analysis.
 
-**Technical Proficiency:**
-- **Statistical Analysis**: Demonstrated proficiency in statistical analysis methods and interpretation
-- **Data Management**: Skills in secure, privacy-compliant data management and storage
-- **Visualization and Reporting**: Ability to create accessible, compelling data visualisations and reports
-- **Privacy Compliance**: Understanding of privacy laws and ethical data use practices
+**Your Response:**
+1. How do you ensure data collection is privacy-compliant?
+2. What legal basis do you have for processing this data?
+3. How do you minimise data collection?
+4. How do you obtain appropriate consent or ensure legitimate interest?
+5. How do you protect sensitive data?
+6. How do you communicate data use to community members?
 
-**Community Focus:**
-- **Social Justice Analytics**: Understanding of how to use data to advance social justice goals
-- **Community Engagement**: Skills in engaging community members in data collection and analysis
-- **Cultural Competency**: Understanding of how cultural factors affect data collection and interpretation
-- **Equity Measurement**: Ability to design and implement metrics for measuring equity and inclusion
+**Correct Answer**: Ensure lawful basis for processing, minimise data collection to what's necessary, use anonymization and aggregation where possible, obtain consent or ensure legitimate interest applies, implement strong security measures, communicate data use transparently, respect data subject rights, follow privacy by design principles.
 
-#### 9.1.2. Advanced Competencies
+### 9.2. Scenario 2: Equity Analysis Request
 
-**Strategic Analysis:**
-- **Predictive Analytics**: Ability to develop and use predictive models for community planning
-- **Impact Measurement**: Skills in measuring the impact of community programmes and initiatives
-- **Trend Analysis**: Advanced skills in identifying and analysing long-term community trends
-- **Research Design**: Ability to design and implement research studies for community insight
+**Situation**: Community leadership want to analyse whether moderation actions are applied equitably across different demographic groups. They want data on moderation actions broken down by various identity factors to identify potential bias.
 
-**Leadership and Communication:**
-- **Data Storytelling**: Exceptional skills in communicating data insights to diverse audiences
-- **Training and Education**: Ability to train others in data literacy and analysis
-- **Policy Development**: Skills in using data to inform policy development and decision-making
-- **Community Advocacy**: Using data to advocate for community needs and social justice
+**Your Response:**
+1. How do you design this analysis ethically?
+2. How do you protect privacy whilst analysing equity?
+3. How do you ensure the analysis doesn't perpetuate harm?
+4. How do you involve affected community members?
+5. How do you present findings in a way that advances equity?
+6. How do you use findings to drive positive change?
 
-### 9.2. Training and Performance Standards
+**Correct Answer**: Design analysis to advance equity goals, use aggregated anonymized data, involve affected community members in analysis design, ensure analysis doesn't perpetuate harm, present findings to drive positive change, use findings to address inequities, maintain privacy protections throughout.
 
-#### 9.2.1. Certification Requirements
+### 9.3. Scenario 3: Data Breach During Analysis
 
-**Technical Certifications:**
-- **Relevant Professional Certifications**: Appropriate professional certifications in data analysis or research
-- **Privacy and Ethics Training**: Certification in data privacy and ethical research practices
-- **Statistical Software Proficiency**: Demonstrated proficiency in relevant statistical software and programming languages
-- **Platform-Specific Training**: Training on community-specific platforms and data sources
+**Situation**: While working on data analysis, you discover that a dataset containing personal information was accidentally shared with unauthorized personnel. The dataset includes user activity data and some identifying information.
 
-**Community-Specific Training:**
-- **Community Values Integration**: Training on integrating community values into data analysis work
-- **Cultural Competency**: Training on culturally responsive research and data analysis methods
-- **Social Justice Analytics**: Training on using data analysis to advance social justice goals
-- **Community Engagement**: Training on engaging community members as partners in research and analysis
+**Your Response:**
+1. How do you respond immediately?
+2. How do you assess the severity of the breach?
+3. What documentation is required?
+4. When must you notify authorities?
+5. When must you notify affected users?
+6. How do you prevent future breaches?
 
-#### 9.2.2. Performance Evaluation
+**Correct Answer**: Contain breach immediately, assess severity and risk, document comprehensively, notify supervisory authority within 72 hours if high risk, notify affected users without undue delay if high risk, implement additional security measures, review and improve data handling procedures.
 
-**Effectiveness Measures:**
-- **Analysis Quality**: High quality, accurate, and insightful data analysis
-- **Community Impact**: Demonstrable positive impact on community decision-making and improvement
-- **Privacy Compliance**: Consistent adherence to privacy laws and ethical data use standards
-- **Communication Effectiveness**: Effective communication of data insights to diverse stakeholders
+## 10. TRAINING REQUIREMENTS
 
-**Professional Development:**
-- **Continuous Learning**: Ongoing professional development and skill enhancement
-- **Innovation**: Development of innovative approaches to community data analysis
-- **Collaboration**: Effective collaboration with community members and other staff
-- **Leadership**: Leadership in promoting data literacy and evidence-based decision-making
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/data-privacy-gdpr.md b/src/content/docs/staff/training/data-privacy-gdpr.md
new file mode 100644
index 0000000..739e755
--- /dev/null
+++ b/src/content/docs/staff/training/data-privacy-gdpr.md
@@ -0,0 +1,874 @@
+---
+title: Data Privacy and GDPR Compliance Training for Staff
+---
+
+**MANDATORY TRAINING FOR ALL TEAM MEMBERS**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides essential guidance for all Team members on data privacy principles, GDPR compliance, and proper handling of user data. All Team members who interact with user data must understand privacy laws, user rights, and our obligations to protect personal information.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive privacy and data protection framework:
+
+**(a)** **Privacy Policy**: Primary policy governing our data collection and processing practices;
+
+**(b)** **Community Code of Conduct**: Behavioural expectations and community safety standards;
+
+**(c)** **Content and Moderation Policy**: Enforcement procedures and content restrictions;
+
+**(d)** **Data Subprocessors Policy**: Information about third-party data processing;
+
+**(e)** **Security Policy**: Technical safeguards for data protection;
+
+**(f)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Critical Disclaimer
+
+**REMEMBER: WE ARE NOT LEGAL PROFESSIONALS**
+
+- We cannot provide legal advice about data privacy
+- Our role is to implement privacy policies and procedures correctly
+- When in doubt about privacy requirements, escalate to legal counsel
+- Privacy laws vary by jurisdiction and are complex
+- User privacy rights must be respected and protected at all times
+
+## 2. UNDERSTANDING DATA PRIVACY FUNDAMENTALS
+
+### 2.1. What Is Personal Data?
+
+#### 2.1.1. Definition of Personal Data
+
+**Personal Data** is any information that can identify or be used to identify a natural person, either directly or indirectly.
+
+**Direct Identifiers:**
+- Names, usernames, email addresses
+- Phone numbers, physical addresses
+- IP addresses, device identifiers
+- Account numbers, user IDs
+
+**Indirect Identifiers:**
+- Location data, timezone information
+- Behavioural patterns, usage data
+- Preferences, interests, activity logs
+- Any combination of data that can identify an individual
+
+#### 2.1.2. Special Categories of Personal Data
+
+**Sensitive Personal Data** (requires enhanced protection):
+- Racial or ethnic origin
+- Political opinions
+- Religious or philosophical beliefs
+- Trade union membership
+- Health information
+- Sexual orientation or gender identity
+- Biometric data
+- Criminal convictions or offences
+
+**Special Handling Requirements:**
+- Requires explicit consent for processing
+- Additional security measures required
+- Stricter retention and deletion requirements
+- Enhanced user rights and protections
+
+### 2.2. Core Privacy Principles
+
+#### 2.2.1. Lawfulness, Fairness, and Transparency
+
+**Lawfulness:**
+- Personal data must be processed lawfully
+- Must have a legal basis for processing
+- Cannot process data in violation of laws
+
+**Fairness:**
+- Processing must be fair to data subjects
+- Cannot mislead or deceive users about data use
+- Must respect user expectations
+
+**Transparency:**
+- Users must be informed about data processing
+- Privacy policies must be clear and accessible
+- Users must understand how their data is used
+
+#### 2.2.2. Purpose Limitation and Data Minimisation
+
+**Purpose Limitation:**
+- Data collected only for specified, legitimate purposes
+- Cannot use data for incompatible purposes
+- Must clearly communicate purposes to users
+
+**Data Minimisation:**
+- Collect only data necessary for stated purposes
+- Do not collect excessive or unnecessary data
+- Regularly review and delete unnecessary data
+
+#### 2.2.3. Accuracy and Storage Limitation
+
+**Accuracy:**
+- Personal data must be accurate and kept up to date
+- Take reasonable steps to correct inaccurate data
+- Allow users to correct their own data
+
+**Storage Limitation:**
+- Keep data only as long as necessary
+- Delete data when no longer needed
+- Have clear retention policies and schedules
+
+#### 2.2.4. Integrity and Confidentiality
+
+**Security:**
+- Protect data against unauthorized access
+- Protect against loss, destruction, or damage
+- Implement appropriate technical and organisational measures
+
+**Confidentiality:**
+- Limit access to personal data
+- Only share data with authorized personnel
+- Maintain confidentiality of user information
+
+## 3. GDPR AND DATA PROTECTION REGULATIONS
+
+### 3.1. Understanding GDPR
+
+#### 3.1.1. GDPR Scope and Applicability
+
+**When GDPR Applies:**
+- Processing personal data of individuals in the European Economic Area (EEA)
+- Regardless of where the organisation is located
+- Applies to both controllers and processors
+- Covers all types of personal data processing
+
+**Key GDPR Principles:**
+- **Lawful Basis**: Must have legal basis for processing
+- **Consent**: Must be freely given, specific, informed, and unambiguous
+- **Rights**: Data subjects have extensive rights
+- **Accountability**: Organisations must demonstrate compliance
+- **Breach Notification**: Must notify authorities and users of breaches
+
+#### 3.1.2. Legal Bases for Processing
+
+**Consent:**
+- User has given clear consent for specific processing
+- Can be withdrawn at any time
+- Must be as easy to withdraw as to give
+
+**Contract:**
+- Processing necessary for contract performance
+- User is party to the contract
+- Processing is necessary for contract
+
+**Legal Obligation:**
+- Processing required by law
+- Legal requirement exists
+- Processing is necessary to comply
+
+**Vital Interests:**
+- Processing necessary to protect life or physical safety
+- Emergency situations
+- Cannot reasonably obtain consent
+
+**Public Task:**
+- Processing necessary for public interest or official authority
+- Organisation exercises official authority
+- Processing is necessary for task
+
+**Legitimate Interests:**
+- Processing necessary for legitimate interests
+- Interests not overridden by user rights
+- Balance test required
+
+### 3.2. Other Data Protection Regulations
+
+#### 3.2.1. Regional Privacy Laws
+
+**California Consumer Privacy Act (CCPA):**
+- Applies to California residents
+- Right to know, delete, and opt-out
+- Non-discrimination requirements
+- Disclosure requirements
+
+**Personal Information Protection and Electronic Documents Act (PIPEDA):**
+- Applies to Canadian residents
+- Consent requirements
+- Individual access rights
+- Breach notification requirements
+
+**Other Jurisdictions:**
+- Various state and national privacy laws
+- Sector-specific regulations
+- International data transfer restrictions
+- Local data localization requirements
+
+#### 3.2.2. Cross-Border Data Transfers
+
+**Transfer Restrictions:**
+- Many jurisdictions restrict international data transfers
+- Adequate safeguards required for transfers
+- Standard contractual clauses may be needed
+- Privacy Shield and adequacy decisions
+
+**Compliance Requirements:**
+- Identify all data transfers
+- Ensure appropriate safeguards
+- Document transfer mechanisms
+- Monitor for regulatory changes
+
+## 4. DATA SUBJECT RIGHTS
+
+### 4.1. Understanding User Rights
+
+#### 4.1.1. Right of Access
+
+**What Users Can Request:**
+- Confirmation that their data is being processed
+- Access to their personal data
+- Information about processing purposes
+- Information about data retention
+- Information about data sharing
+
+**Response Requirements:**
+- Respond within 30 days (GDPR) or applicable timeframe
+- Provide data in commonly used format
+- Explain processing purposes
+- Identify data recipients or categories
+- Explain retention periods
+
+**How to Handle Access Requests:**
+1. Verify identity of requester
+2. Locate all relevant personal data
+3. Review data for third-party information
+4. Prepare response with requested information
+5. Provide data securely
+6. Document the request and response
+
+#### 4.1.2. Right to Rectification
+
+**What Users Can Request:**
+- Correction of inaccurate personal data
+- Completion of incomplete personal data
+- Update of outdated information
+
+**Response Requirements:**
+- Respond within 30 days (GDPR) or applicable timeframe
+- Make corrections without undue delay
+- Notify third parties if data shared
+- Document corrections made
+
+**How to Handle Rectification Requests:**
+1. Verify identity of requester
+2. Verify accuracy of requested changes
+3. Make corrections to data
+4. Update all systems where data stored
+5. Notify relevant third parties if necessary
+6. Confirm completion with user
+
+#### 4.1.3. Right to Erasure ("Right to Be Forgotten")
+
+**When Erasure Required:**
+- Data no longer necessary for original purposes
+- User withdraws consent and no other legal basis
+- User objects to processing and no overriding legitimate interest
+- Data processed unlawfully
+- Erasure required for legal compliance
+
+**Exceptions to Erasure:**
+- Exercise of right to freedom of expression
+- Legal compliance obligations
+- Public interest archiving
+- Legal claims establishment or defence
+- Legitimate interests that override erasure request
+
+**How to Handle Erasure Requests:**
+1. Verify identity of requester
+2. Assess if erasure is required or exception applies
+3. Identify all locations where data is stored
+4. Delete data from all systems
+5. Notify third parties if data shared
+6. Confirm completion with user
+7. Document erasure for compliance records
+
+#### 4.1.4. Right to Restrict Processing
+
+**When Restriction Required:**
+- User contests data accuracy
+- Processing is unlawful but user opposes erasure
+- Data no longer needed but user needs it for legal claims
+- User objects to processing pending verification
+
+**Effect of Restriction:**
+- Data can be stored but not processed
+- Except with user consent or for legal claims
+- User must be notified before restriction lifted
+
+#### 4.1.5. Right to Data Portability
+
+**What Users Can Request:**
+- Receive their data in structured, commonly used format
+- Transmit data directly to another controller
+- Applies to data provided by user and processed by consent or contract
+
+**Response Requirements:**
+- Provide data in machine-readable format
+- Respond within 30 days (GDPR) or applicable timeframe
+- Provide data securely
+- Include all relevant data
+
+#### 4.1.6. Right to Object
+
+**When Users Can Object:**
+- Processing based on legitimate interests
+- Processing for direct marketing
+- Processing for research or statistics (with restrictions)
+
+**Response Requirements:**
+- Stop processing unless compelling legitimate grounds
+- Respond to objection within timeframe
+- Explain decision if objection overridden
+
+### 4.2. Handling Data Subject Requests
+
+#### 4.2.1. Request Verification
+
+**Identity Verification:**
+- Verify identity before processing requests
+- Use secure methods for verification
+- Protect against fraudulent requests
+- Balance security with user convenience
+
+**Verification Methods:**
+- Email confirmation from registered address
+- Account login verification
+- Additional security questions if needed
+- Government-issued ID for sensitive requests
+
+#### 4.2.2. Request Processing
+
+**Timeline Management:**
+- Acknowledge receipt within timeframe
+- Process requests within legal deadlines
+- Extend deadlines only when necessary and permitted
+- Keep users informed of progress
+
+**Documentation:**
+- Document all data subject requests
+- Record request details and responses
+- Maintain audit trail of actions taken
+- Track response times and outcomes
+
+#### 4.2.3. Exceptions and Limitations
+
+**When Requests Can Be Limited:**
+- Manifestly unfounded or excessive requests
+- Requests that would affect others' rights
+- Legal obligations that prevent compliance
+- Legitimate interests that override request
+
+**Handling Limitations:**
+- Explain why request is limited
+- Provide partial response when possible
+- Document reasons for limitation
+- Inform user of right to complain
+
+## 5. DATA BREACH RESPONSE
+
+### 5.1. Understanding Data Breaches
+
+#### 5.1.1. Definition of Data Breach
+
+**Data Breach** is a security incident that results in accidental or unlawful destruction, loss, alteration, or unauthorized disclosure of or access to personal data.
+
+**Types of Breaches:**
+- **Confidentiality Breach**: Unauthorized access to or disclosure of data
+- **Integrity Breach**: Unauthorized alteration of data
+- **Availability Breach**: Accidental or unlawful loss of access to data
+
+**Examples:**
+- Hacking or unauthorized system access
+- Accidental data sharing or email errors
+- Loss or theft of devices containing data
+- Insider threats or malicious employees
+- System failures or technical errors
+
+#### 5.1.2. Breach Severity Assessment
+
+**High-Risk Breaches:**
+- Involve sensitive personal data
+- Affect large numbers of individuals
+- Result in identity theft or financial harm
+- Involve children's data
+- Require immediate notification
+
+**Medium-Risk Breaches:**
+- Involve standard personal data
+- Affect moderate numbers of individuals
+- Limited potential for harm
+- May require notification
+
+**Low-Risk Breaches:**
+- Involve minimal personal data
+- Affect few individuals
+- Very limited potential for harm
+- May not require notification
+
+### 5.2. Breach Response Procedures
+
+#### 5.2.1. Immediate Response (Within 1 Hour)
+
+**Upon Discovering a Breach:**
+1. **CONTAIN THE BREACH** - Take immediate steps to stop ongoing breach
+2. **DOCUMENT DISCOVERY** - Record when and how breach was discovered
+3. **ASSESS SCOPE** - Determine what data and how many users affected
+4. **ESCALATE IMMEDIATELY** - Notify security coordinator and senior staff
+5. **PRESERVE EVIDENCE** - Document all relevant information
+6. **SECURE SYSTEMS** - Take steps to prevent further breaches
+
+**Example Response Template:**
+```
+URGENT DATA BREACH INCIDENT
+
+[Description of breach]
+[When discovered]
+[What data affected]
+[How many users affected]
+[Current containment status]
+[Initial assessment of risk]
+
+Escalating immediately to security coordinator and senior staff.
+```
+
+#### 5.2.2. Breach Investigation (Within 24 Hours)
+
+**Investigation Steps:**
+1. **Determine Cause** - Identify how breach occurred
+2. **Assess Impact** - Determine full scope of breach
+3. **Identify Affected Data** - Catalogue all affected personal data
+4. **Identify Affected Users** - Determine which users are affected
+5. **Assess Risk** - Evaluate risk to individuals
+6. **Develop Remediation Plan** - Plan steps to address breach
+
+#### 5.2.3. Breach Notification
+
+**Regulatory Notification:**
+- **GDPR**: Notify supervisory authority within 72 hours if high risk
+- **CCPA**: Notify Attorney General if affecting 500+ California residents
+- **PIPEDA**: Notify Privacy Commissioner if real risk of significant harm
+- **Other Jurisdictions**: Follow applicable notification requirements
+
+**User Notification:**
+- **GDPR**: Notify users without undue delay if high risk
+- **CCPA**: Notify affected California residents
+- **Other Jurisdictions**: Follow applicable notification requirements
+- **Content**: Explain breach, what data affected, what users should do
+
+**Notification Content:**
+- Description of breach
+- What personal data was affected
+- Likely consequences of breach
+- Measures taken or proposed to address breach
+- Advice on steps users can take
+- Contact information for questions
+
+## 6. DATA PROCESSING IN MODERATION AND SUPPORT
+
+### 6.1. Privacy in Moderation Activities
+
+#### 6.1.1. Data Collection in Moderation
+
+**What Data We Collect:**
+- User reports and complaints
+- Evidence of policy violations
+- Communication logs and messages
+- User account information
+- Behavioural patterns and history
+
+**Legal Basis:**
+- **Legitimate Interest**: Maintaining community safety and enforcing policies
+- **Legal Obligation**: Compliance with legal requirements
+- **Consent**: When users voluntarily report issues
+
+**Privacy Considerations:**
+- Collect only data necessary for moderation
+- Minimize data collection where possible
+- Protect sensitive information in reports
+- Limit access to moderation data
+
+#### 6.1.2. Data Sharing in Moderation
+
+**When Data Can Be Shared:**
+- With other Team members for moderation purposes
+- With law enforcement when legally required
+- With affected parties when necessary for safety
+- With legal counsel for legal advice
+
+**Privacy Protections:**
+- Share only necessary information
+- Use secure communication channels
+- Limit access to need-to-know basis
+- Document all data sharing
+
+### 6.2. Privacy in Support Activities
+
+#### 6.2.1. Data Collection in Support
+
+**What Data We Collect:**
+- User support requests and communications
+- Account information for troubleshooting
+- Technical information for problem resolution
+- User preferences and settings
+
+**Legal Basis:**
+- **Contract**: Providing support services
+- **Legitimate Interest**: Improving services and user experience
+- **Consent**: When users provide additional information
+
+**Privacy Considerations:**
+- Collect only data necessary for support
+- Protect sensitive information in support requests
+- Secure storage of support communications
+- Appropriate retention and deletion
+
+#### 6.2.2. Data Minimisation in Support
+
+**Best Practices:**
+- Ask only for information needed to help
+- Don't collect unnecessary personal details
+- Use anonymized data when possible
+- Delete support data when no longer needed
+- Respect user privacy preferences
+
+## 7. PRIVACY BY DESIGN AND DEFAULT
+
+### 7.1. Implementing Privacy by Design
+
+#### 7.1.1. Privacy by Design Principles
+
+**Proactive Not Reactive:**
+- Anticipate privacy issues before they occur
+- Build privacy into systems from the start
+- Don't wait for problems to address privacy
+
+**Privacy as Default:**
+- Default settings should be most privacy-protective
+- Users shouldn't have to opt-in to privacy
+- Maximum privacy should be automatic
+
+**Full Functionality:**
+- Privacy shouldn't compromise functionality
+- Find solutions that protect privacy and enable features
+- Balance privacy with user experience
+
+**End-to-End Security:**
+- Security throughout data lifecycle
+- From collection to deletion
+- Appropriate security measures at each stage
+
+**Visibility and Transparency:**
+- Users should understand data processing
+- Clear communication about privacy practices
+- Honest and open about data use
+
+**Respect for User Privacy:**
+- User interests are paramount
+- Respect user choices and preferences
+- Empower users to control their data
+
+#### 7.1.2. Practical Implementation
+
+**System Design:**
+- Minimize data collection in system architecture
+- Build access controls into systems
+- Implement encryption and security measures
+- Design for data deletion and portability
+
+**Process Design:**
+- Privacy considerations in all processes
+- Data minimisation in workflows
+- Secure handling procedures
+- Regular privacy reviews
+
+### 7.2. Privacy Impact Assessments
+
+#### 7.2.1. When to Conduct PIAs
+
+**High-Risk Processing Requires PIA:**
+- Systematic and extensive evaluation of individuals
+- Large-scale processing of sensitive data
+- Systematic monitoring of public areas
+- New technologies or processing methods
+
+**PIA Process:**
+1. Describe processing and purposes
+2. Assess necessity and proportionality
+3. Identify and assess risks to individuals
+4. Identify measures to address risks
+5. Document assessment and measures
+6. Review and update regularly
+
+#### 7.2.2. Risk Assessment
+
+**Identifying Risks:**
+- Unauthorized access to data
+- Loss or destruction of data
+- Unauthorized disclosure of data
+- Discrimination or other adverse effects
+- Loss of user control over data
+
+**Mitigating Risks:**
+- Technical measures (encryption, access controls)
+- Organisational measures (policies, training)
+- Contractual measures (data processing agreements)
+- Regular reviews and updates
+
+## 8. THIRD-PARTY DATA PROCESSING
+
+### 8.1. Working with Subprocessors
+
+#### 8.1.1. Subprocessor Requirements
+
+**Due Diligence:**
+- Assess subprocessor privacy practices
+- Verify compliance with applicable laws
+- Review security measures
+- Check data processing agreements
+
+**Contractual Requirements:**
+- Data processing agreements required
+- Must specify processing purposes
+- Must include security requirements
+- Must address data subject rights
+- Must address breach notification
+
+#### 8.1.2. Monitoring Subprocessors
+
+**Ongoing Monitoring:**
+- Regular reviews of subprocessor practices
+- Monitor for compliance issues
+- Review security incidents
+- Assess continued suitability
+
+**Managing Subprocessor Changes:**
+- Notify users of significant changes
+- Update data processing agreements
+- Assess impact on data subjects
+- Ensure continued compliance
+
+### 8.2. Data Processing Agreements
+
+#### 8.2.1. Required Contract Terms
+
+**Essential Terms:**
+- Subject matter and duration of processing
+- Nature and purpose of processing
+- Types of personal data processed
+- Categories of data subjects
+- Obligations and rights of controller
+
+**Subprocessor Obligations:**
+- Process data only on documented instructions
+- Ensure persons processing data are bound by confidentiality
+- Implement appropriate security measures
+- Assist controller with data subject requests
+- Assist controller with breach notifications
+- Delete or return data at end of processing
+
+#### 8.2.2. International Transfers
+
+**Transfer Mechanisms:**
+- Adequacy decisions
+- Standard contractual clauses
+- Binding corporate rules
+- Certification mechanisms
+- Codes of conduct
+
+**Compliance Requirements:**
+- Identify all international transfers
+- Ensure appropriate transfer mechanisms
+- Document transfer mechanisms
+- Monitor for regulatory changes
+
+## 9. DOCUMENTATION AND ACCOUNTABILITY
+
+### 9.1. Privacy Documentation Requirements
+
+#### 9.1.1. Required Documentation
+
+**Processing Records:**
+- Purposes of processing
+- Categories of data subjects and personal data
+- Categories of recipients
+- Transfers to third countries
+- Retention periods
+- Security measures
+
+**Policy Documentation:**
+- Privacy policies and notices
+- Data processing procedures
+- Breach response procedures
+- Data subject request procedures
+- Staff training records
+
+#### 9.1.2. Maintaining Documentation
+
+**Documentation Standards:**
+- Keep documentation up to date
+- Review and update regularly
+- Ensure accuracy and completeness
+- Make accessible to relevant staff
+- Maintain audit trails
+
+### 9.2. Accountability and Compliance
+
+#### 9.2.1. Demonstrating Compliance
+
+**Compliance Measures:**
+- Privacy policies and procedures
+- Staff training and awareness
+- Technical and organisational measures
+- Regular audits and assessments
+- Documentation of compliance efforts
+
+**Regulatory Cooperation:**
+- Respond to regulatory inquiries
+- Provide requested documentation
+- Cooperate with investigations
+- Implement corrective measures
+- Maintain good faith compliance
+
+#### 9.2.2. Regular Reviews
+
+**Review Schedule:**
+- Annual comprehensive privacy review
+- Quarterly review of high-risk processing
+- Regular review of policies and procedures
+- Review after significant changes
+- Review after incidents or breaches
+
+**Review Process:**
+- Assess current practices
+- Identify gaps or issues
+- Develop improvement plans
+- Implement changes
+- Document reviews and changes
+
+## 10. SELF-CARE AND PROFESSIONAL DEVELOPMENT
+
+### 10.1. Managing Privacy Workload
+
+#### 10.1.1. Understanding the Demands
+
+**Privacy Work Challenges:**
+- Complex and evolving regulations
+- High stakes and legal consequences
+- Balancing privacy with functionality
+- Managing user expectations
+- Keeping up with regulatory changes
+
+**Stress Management:**
+- Recognise signs of stress
+- Take breaks when needed
+- Seek support from colleagues
+- Maintain work-life balance
+- Access professional support when needed
+
+#### 10.1.2. Professional Development
+
+**Ongoing Learning:**
+- Stay current with privacy regulations
+- Attend privacy training and conferences
+- Read privacy publications and updates
+- Participate in privacy communities
+- Pursue privacy certifications
+
+**Skill Development:**
+- Technical privacy skills
+- Legal and regulatory knowledge
+- Communication and user relations
+- Risk assessment and management
+- Documentation and compliance
+
+### 10.2. Support Systems
+
+#### 10.2.1. Team Support
+
+**Peer Support:**
+- Regular check-ins with privacy team
+- Sharing knowledge and best practices
+- Collaborative problem-solving
+- Mutual support and understanding
+- Celebration of successes
+
+**Supervisory Support:**
+- Regular meetings with supervisors
+- Access to resources and training
+- Workload management
+- Recognition of contributions
+- Career development support
+
+#### 10.2.2. Professional Resources
+
+**External Support:**
+- Privacy professional associations
+- Legal counsel for complex issues
+- Privacy consultants when needed
+- Regulatory guidance resources
+- Peer networks and communities
+
+## 11. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 11.1. Scenario 1: Data Subject Access Request
+
+**Situation**: A user requests access to all their personal data. They want to know what information you have about them, how it's being used, and who it's been shared with.
+
+**Your Response:**
+1. What is the timeframe for responding to this request?
+2. What information must you provide?
+3. How do you verify the user's identity?
+4. What steps do you take to gather all relevant data?
+5. How do you present the information to the user?
+
+**Correct Answer**: Respond within 30 days, verify identity securely, search all systems for relevant data, provide comprehensive information including data, processing purposes, retention periods, and data recipients, present in clear format.
+
+### 11.2. Scenario 2: Data Breach Discovery
+
+**Situation**: You discover that a Team member accidentally sent an email containing user email addresses to the wrong distribution list. Fifty people who shouldn't have received the email now have access to user email addresses.
+
+**Your Response:**
+1. What are your immediate actions?
+2. How do you assess the severity and risk?
+3. What information must be documented?
+4. When must you notify supervisory authorities?
+5. When must you notify affected users?
+6. What measures do you take to prevent further harm?
+
+**Correct Answer**: Contain breach immediately, assess risk level, document comprehensively, notify supervisory authority within 72 hours if high risk, notify users without undue delay if high risk, take steps to prevent further breaches, implement additional security measures.
+
+### 11.3. Scenario 3: Data Erasure Request with Legal Exception
+
+**Situation**: A user requests deletion of their account data. However, you know there's an ongoing moderation investigation involving their account that may require the data for legal purposes or potential legal claims.
+
+**Your Response:**
+1. Can you refuse this erasure request?
+2. What exceptions might apply?
+3. How do you assess whether an exception applies?
+4. What do you communicate to the user?
+5. How do you document your decision?
+
+**Correct Answer**: Yes, exceptions apply for legal compliance or legal claims. Assess if data needed for ongoing investigation or potential legal action. Document assessment clearly. Explain to user that erasure is restricted due to legal exception, explain why, and inform them when data will be deleted.
+
+## 12. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Data Privacy and GDPR Compliance Training document is part of our comprehensive Team development programme designed to ensure proper handling of user data and compliance with data protection regulations. Data privacy is critical to user trust and legal compliance, and all Team members must complete this training before handling user data. For questions about data privacy procedures or to report training completion, please contact the Privacy Officer through designated Team channels.*
+
diff --git a/src/content/docs/staff/training/de-escalation-techniques.md b/src/content/docs/staff/training/de-escalation-techniques.md
new file mode 100644
index 0000000..031eab7
--- /dev/null
+++ b/src/content/docs/staff/training/de-escalation-techniques.md
@@ -0,0 +1,807 @@
+---
+title: De-escalation Techniques Training for Staff
+---
+
+**ESSENTIAL TRAINING FOR ALL MODERATION STAFF**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides comprehensive guidance for Team members on de-escalation techniques for managing highly emotional, tense, or potentially volatile situations in online communities. Effective de-escalation prevents situations from escalating into conflicts, protects community members, and maintains safe, welcoming environments.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive moderation and safety framework:
+
+**(a)** **Conflict Resolution Policy**: Procedures for resolving disputes (de-escalation prevents escalation to conflicts);
+
+**(b)** **Crisis Response Policy**: Procedures for responding to mental health crises (de-escalation is first response);
+
+**(c)** **Harassment Response Policy**: Procedures for responding to harassment (de-escalation may prevent escalation);
+
+**(d)** **Trauma-Informed Moderation Policy**: Principles for moderation that considers trauma (de-escalation avoids re-traumatization);
+
+**(e)** **Content and Moderation Policy**: Enforcement procedures and content standards;
+
+**(f)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Critical Understanding
+
+**De-escalation Is Prevention:**
+- De-escalation prevents situations from becoming conflicts or crises
+- Early intervention is more effective than later intervention
+- De-escalation protects community members and community safety
+- Not all situations can or should be de-escalated
+- De-escalation requires skill, practice, and self-awareness
+
+**When De-escalation Is Appropriate:**
+- Situations involving high emotions or tension
+- Misunderstandings or miscommunications
+- Situations that can be resolved through communication
+- When parties are open to resolution
+- When safety can be maintained through de-escalation
+
+**When De-escalation May Not Be Appropriate:**
+- Situations involving immediate safety threats
+- Harassment or abuse that requires protective action
+- Criminal activity that requires law enforcement
+- When de-escalation attempts enable harm
+- When parties are not open to resolution
+
+## 2. UNDERSTANDING ESCALATION
+
+### 2.1. What Is Escalation?
+
+#### 2.1.1. Definition and Stages
+
+**Escalation** is the process by which situations become more intense, serious, or dangerous. Escalation typically progresses through stages:
+
+**Stage 1: Tension**
+- Initial disagreement or concern
+- Mild emotional responses
+- Communication still possible
+- Opportunity for easy resolution
+
+**Stage 2: Agitation**
+- Increased emotional responses
+- Defensive communication
+- Reduced listening and understanding
+- Requires active intervention
+
+**Stage 3: Aggression**
+- Hostile communication
+- Personal attacks or threats
+- Limited rational communication
+- Significant intervention required
+
+**Stage 4: Crisis**
+- Extreme emotional responses
+- Threats or dangerous behaviour
+- Safety concerns
+- Immediate protective action required
+
+#### 2.1.2. Escalation Triggers
+
+**Common Triggers:**
+- Feeling attacked or criticised
+- Perceived injustice or unfairness
+- Threats to identity or values
+- Loss of control or agency
+- Past trauma or negative experiences
+- Power imbalances or authority
+- Miscommunication or misunderstanding
+- Stress or external pressures
+
+**Online-Specific Triggers:**
+- Public callouts or criticism
+- Moderation actions or consequences
+- Perceived favouritism or bias
+- Privacy violations or doxxing
+- Exclusion or ostracism
+- Platform limitations or technical issues
+
+### 2.2. Recognising Escalation Patterns
+
+#### 2.2.1. Early Warning Signs
+
+**Emotional Indicators:**
+- Increased emotional language
+- Stronger emotional reactions
+- Defensive responses
+- Reduced rational communication
+- Escalating language intensity
+
+**Behavioural Indicators:**
+- Repeated messages or posts
+- Tagging multiple people
+- Moving to different platforms
+- Recruiting others to support
+- Threatening language or behaviour
+
+**Communication Patterns:**
+- Shift from issue-focused to person-focused
+- Increase in personal attacks
+- Reduction in listening or understanding
+- Escalating demands or ultimatums
+- Refusal to engage constructively
+
+#### 2.2.2. Risk Assessment
+
+**Low Risk:**
+- Mild emotional responses
+- Issue-focused communication
+- Willingness to discuss and resolve
+- No threats or safety concerns
+- Open to de-escalation
+
+**Moderate Risk:**
+- Strong emotional responses
+- Some personal elements
+- Defensive communication
+- Potential for escalation
+- May require intervention
+
+**High Risk:**
+- Extreme emotional responses
+- Threats or dangerous language
+- Safety concerns
+- Refusal to engage constructively
+- May require protective action
+
+## 3. DE-ESCALATION PRINCIPLES
+
+### 3.1. Core Principles
+
+#### 3.1.1. Safety First
+
+**Physical and Psychological Safety:**
+- Ensure safety of all parties
+- Address immediate safety threats first
+- Don't de-escalate at expense of safety
+- Take protective action when needed
+- Support community member safety
+
+**Safety in De-escalation:**
+- Maintain your own safety
+- Don't put yourself in dangerous situations
+- Recognise when de-escalation isn't appropriate
+- Escalate to protective action when needed
+- Support community member safety throughout
+
+#### 3.1.2. Calm and Centred Presence
+
+**Maintaining Calm:**
+- Stay calm and composed yourself
+- Don't match emotional intensity
+- Breathe and ground yourself
+- Maintain professional boundaries
+- Model calm, respectful communication
+
+**Centred Presence:**
+- Be present and focused
+- Listen actively and fully
+- Avoid distractions or multitasking
+- Show genuine care and concern
+- Demonstrate stability and reliability
+
+#### 3.1.3. Empathy and Understanding
+
+**Showing Empathy:**
+- Acknowledge feelings and experiences
+- Validate concerns and perspectives
+- Show understanding of their position
+- Demonstrate care and concern
+- Avoid dismissing or minimising
+
+**Understanding Perspectives:**
+- Try to understand their perspective
+- Consider their experiences and context
+- Recognise valid concerns
+- Acknowledge their feelings
+- Show respect for their position
+
+#### 3.1.4. Non-Judgemental Approach
+
+**Avoiding Judgement:**
+- Don't judge their feelings or reactions
+- Avoid labelling or categorising
+- Don't assume intent or motivation
+- Avoid blame or criticism
+- Focus on understanding, not judging
+
+**Open-Minded Approach:**
+- Be open to different perspectives
+- Consider multiple interpretations
+- Avoid jumping to conclusions
+- Stay curious and open
+- Focus on resolution, not blame
+
+### 3.2. Communication Principles
+
+#### 3.2.1. Active Listening
+
+**Listening Skills:**
+- Give full attention to speaker
+- Listen without interrupting
+- Pay attention to emotions and tone
+- Notice nonverbal cues when possible
+- Clarify understanding through questions
+
+**Reflective Listening:**
+- Reflect back what you hear
+- Paraphrase to confirm understanding
+- Acknowledge emotions and feelings
+- Summarise key points
+- Validate their experience
+
+#### 3.2.2. Clear and Respectful Communication
+
+**Clear Communication:**
+- Use clear, simple language
+- Avoid jargon or technical terms
+- Be direct and honest
+- Provide clear information
+- Ensure understanding
+
+**Respectful Communication:**
+- Use respectful language and tone
+- Avoid inflammatory or triggering language
+- Show respect for their position
+- Maintain dignity and respect
+- Avoid condescension or patronizing
+
+## 4. DE-ESCALATION TECHNIQUES
+
+### 4.1. Verbal De-escalation Techniques
+
+#### 4.1.1. Language and Phrasing
+
+**Supportive Language:**
+- "I understand this is important to you"
+- "I can see you're feeling [emotion]"
+- "Help me understand your perspective"
+- "What would help resolve this situation?"
+- "I want to work together to find a solution"
+
+**Language to Avoid:**
+- "Calm down" or "Relax"
+- "You're overreacting"
+- "That's not a big deal"
+- "You need to..."
+- "You should..."
+
+**Effective Phrasing:**
+- Use "I" statements rather than "you" statements
+- Ask open-ended questions
+- Offer choices and options
+- Focus on solutions, not problems
+- Acknowledge and validate feelings
+
+#### 4.1.2. Questioning Techniques
+
+**Open-Ended Questions:**
+- "Can you help me understand what happened?"
+- "What would help resolve this for you?"
+- "How can we work together on this?"
+- "What are your concerns about this?"
+- "What would you like to see happen?"
+
+**Clarifying Questions:**
+- "When you say [X], do you mean [Y]?"
+- "Can you help me understand [specific point]?"
+- "What specifically concerns you about this?"
+- "What would make this better for you?"
+- "What information would help?"
+
+**Avoid Leading Questions:**
+- Don't ask questions that assume answers
+- Don't ask questions that imply blame
+- Don't ask questions that escalate tension
+- Don't ask questions that are actually statements
+- Don't ask questions that are manipulative
+
+### 4.2. Behavioural De-escalation Techniques
+
+#### 4.2.1. Space and Time
+
+**Providing Space:**
+- Suggest taking a break
+- Allow time to process and calm
+- Don't pressure immediate response
+- Respect need for space
+- Offer to continue conversation later
+
+**Time Management:**
+- Don't rush the process
+- Allow adequate time for de-escalation
+- Be patient with the process
+- Recognise that de-escalation takes time
+- Don't force quick resolution
+
+#### 4.2.2. Redirection and Refocusing
+
+**Redirection Techniques:**
+- Redirect from person to issue
+- Redirect from past to present/future
+- Redirect from blame to solutions
+- Redirect from emotions to facts
+- Redirect from problems to possibilities
+
+**Refocusing Techniques:**
+- Refocus on common goals
+- Refocus on shared values
+- Refocus on solutions
+- Refocus on positive outcomes
+- Refocus on moving forward
+
+### 4.3. Emotional De-escalation Techniques
+
+#### 4.3.1. Emotional Validation
+
+**Validating Emotions:**
+- Acknowledge their feelings
+- Validate their emotional experience
+- Show understanding of their emotions
+- Don't dismiss or minimise feelings
+- Recognise emotions as valid
+
+**Validation Language:**
+- "I can see you're feeling [emotion]"
+- "It makes sense that you would feel [emotion]"
+- "Your feelings are valid"
+- "I understand why you might feel [emotion]"
+- "It's understandable that you're feeling [emotion]"
+
+#### 4.3.2. Emotional Regulation Support
+
+**Supporting Regulation:**
+- Model calm and regulation
+- Provide stability and consistency
+- Offer reassurance and support
+- Create safe, predictable environment
+- Support their self-regulation
+
+**Regulation Techniques:**
+- Suggest breathing exercises
+- Recommend taking breaks
+- Offer support and resources
+- Provide calming information
+- Support self-care and coping
+
+## 5. PLATFORM-SPECIFIC DE-ESCALATION
+
+### 5.1. Text-Based De-escalation
+
+#### 5.1.1. Written Communication Challenges
+
+**Challenges:**
+- Lack of nonverbal cues
+- Tone can be misinterpreted
+- Emotions harder to convey
+- Slower communication
+- Limited context
+
+**Strategies:**
+- Use clear, explicit language
+- Acknowledge limitations of text
+- Ask clarifying questions
+- Provide context and explanation
+- Use emoji or tone indicators when helpful
+
+#### 5.1.2. Text-Based Techniques
+
+**Effective Text Communication:**
+- Use clear, simple language
+- Break complex messages into parts
+- Provide context and explanation
+- Ask questions to ensure understanding
+- Summarise and confirm understanding
+
+**Avoiding Escalation in Text:**
+- Don't use all caps or excessive punctuation
+- Avoid sarcasm or ambiguous language
+- Don't send multiple rapid messages
+- Avoid inflammatory or triggering language
+- Take time to craft thoughtful responses
+
+### 5.2. Voice and Video De-escalation
+
+#### 5.2.1. Voice Communication
+
+**Advantages:**
+- Tone and inflection available
+- Faster communication
+- More personal connection
+- Better emotional understanding
+- More natural conversation flow
+
+**Techniques:**
+- Use calm, steady tone
+- Speak slowly and clearly
+- Pause to allow processing
+- Use active listening skills
+- Show empathy through tone
+
+#### 5.2.2. Video Communication
+
+**Advantages:**
+- Full nonverbal communication
+- Facial expressions visible
+- Body language available
+- Strongest personal connection
+- Best emotional understanding
+
+**Techniques:**
+- Maintain calm, open body language
+- Make appropriate eye contact
+- Show empathy through expressions
+- Use active listening skills
+- Create safe, comfortable environment
+
+## 6. DE-ESCALATION IN SPECIFIC SITUATIONS
+
+### 6.1. Moderation Action De-escalation
+
+#### 6.1.1. Responding to Moderation Reactions
+
+**Common Reactions:**
+- Anger or frustration about moderation
+- Feeling unfairly treated
+- Defensive responses
+- Requests for explanation
+- Appeals or challenges
+
+**De-escalation Approach:**
+- Acknowledge their feelings
+- Provide clear explanation
+- Listen to their concerns
+- Address misunderstandings
+- Offer resolution options
+
+**Example Response:**
+"I understand you're feeling frustrated about the moderation action. I'd like to explain why this action was taken and hear your perspective. Can we discuss this together?"
+
+#### 6.1.2. Appeal and Challenge De-escalation
+
+**When Users Appeal:**
+- Listen to their appeal respectfully
+- Review the situation fairly
+- Explain your decision clearly
+- Address their concerns
+- Provide resolution options
+
+**De-escalation Strategies:**
+- Acknowledge their right to appeal
+- Show you're taking their appeal seriously
+- Provide clear process and timeline
+- Address their concerns directly
+- Offer fair resolution
+
+### 6.2. Conflict De-escalation
+
+**Reference to Comprehensive Conflict Resolution Training**: For detailed conflict resolution procedures, mediation techniques, and comprehensive conflict management guidance, see [Conflict Resolution Training](/staff/training/conflict-resolution). This section provides de-escalation techniques for conflicts; refer to the conflict resolution training document for complete conflict resolution processes.
+
+#### 6.2.1. Interpersonal Conflicts
+
+**De-escalating Conflicts:**
+- Separate parties if needed
+- Listen to each party separately
+- Identify underlying issues
+- Find common ground
+- Facilitate resolution
+
+**Techniques:**
+- Acknowledge each party's perspective
+- Validate their feelings
+- Refocus on issues, not personalities
+- Find shared interests or goals
+- Facilitate collaborative solution
+
+#### 6.2.2. Group Conflicts
+
+**De-escalating Group Conflicts:**
+- Address conflict early
+- Identify key issues and parties
+- Facilitate group discussion
+- Find common ground
+- Support collaborative resolution
+
+**Techniques:**
+- Create safe space for discussion
+- Set ground rules for communication
+- Facilitate respectful dialogue
+- Focus on issues, not individuals
+- Support group problem-solving
+
+### 6.3. Crisis De-escalation
+
+#### 6.3.1. Mental Health Crises
+
+**De-escalating Mental Health Crises:**
+- Prioritise safety
+- Stay calm and supportive
+- Listen and validate
+- Provide resources and support
+- Connect with appropriate help
+
+**Important Considerations:**
+- Don't attempt to provide therapy
+- Focus on safety and support
+- Connect with professional help
+- Follow crisis response procedures
+- Maintain appropriate boundaries
+
+#### 6.3.2. Safety Crises
+
+**De-escalating Safety Crises:**
+- Prioritize immediate safety
+- Take protective action when needed
+- Don't de-escalate at expense of safety
+- Connect with appropriate authorities
+- Support community member safety
+
+**When De-escalation Isn't Appropriate:**
+- Immediate safety threats
+- Criminal activity
+- Severe harassment or abuse
+- When de-escalation enables harm
+- When protective action is required
+
+## 7. LIMITATIONS AND BOUNDARIES
+
+### 7.1. When De-escalation Isn't Appropriate
+
+#### 7.1.1. Safety Concerns
+
+**Immediate Safety Threats:**
+- Threats of violence
+- Doxxing or privacy violations
+- Stalking behaviours
+- Criminal activity
+- Severe harassment or abuse
+
+**Response:**
+- Take immediate protective action
+- Don't attempt de-escalation
+- Escalate to appropriate authorities
+- Support victim safety
+- Follow safety protocols
+
+#### 7.1.2. Unwillingness to Engage
+
+**Signs of Unwillingness:**
+- Refusal to engage constructively
+- Continued escalation despite attempts
+- Threats or ultimatums
+- Manipulation or abuse
+- Pattern of harmful behaviour
+
+**Response:**
+- Recognise limitations
+- Don't continue ineffective de-escalation
+- Take appropriate protective action
+- Set clear boundaries
+- Escalate as needed
+
+### 7.2. Professional Boundaries
+
+#### 7.2.1. Maintaining Boundaries
+
+**Important Boundaries:**
+- Don't take responsibility for others' emotions
+- Don't enable harmful behaviour
+- Maintain professional role
+- Don't become emotionally enmeshed
+- Set clear limits
+
+**Boundary Setting:**
+- Clearly communicate boundaries
+- Enforce boundaries consistently
+- Don't compromise boundaries for de-escalation
+- Recognise when boundaries are crossed
+- Take action when boundaries violated
+
+#### 7.2.2. Self-Protection
+
+**Protecting Yourself:**
+- Maintain your own safety
+- Don't put yourself in dangerous situations
+- Recognise your limitations
+- Seek support when needed
+- Take breaks and practice self-care
+
+**Recognising Limits:**
+- Know when you're not effective
+- Recognise when you need support
+- Know when to escalate
+- Understand your role and limitations
+- Practice self-awareness
+
+## 8. PRACTICAL APPLICATION
+
+### 8.1. De-escalation Scenarios
+
+#### 8.1.1. Scenario 1: Angry Response to Moderation
+
+**Situation**: A community member is very angry about a moderation action, posting multiple angry messages and threatening to leave.
+
+**De-escalation Steps:**
+1. Acknowledge their feelings: "I can see you're feeling very upset about this."
+2. Provide explanation: "Let me explain why this action was taken."
+3. Listen to concerns: "I'd like to hear your perspective on this."
+4. Address misunderstandings: "I think there may have been a misunderstanding."
+5. Offer resolution: "How can we work together to resolve this?"
+
+**Key Techniques:**
+- Validate emotions
+- Provide clear information
+- Listen actively
+- Address concerns directly
+- Offer collaborative solution
+
+#### 8.1.2. Scenario 2: Escalating Conflict
+
+**Situation**: Two community members are in an escalating conflict, with personal attacks and threats.
+
+**De-escalation Steps:**
+1. Intervene early: "I'd like to help resolve this situation."
+2. Separate if needed: "Let's pause and take a moment."
+3. Acknowledge both perspectives: "I can see both of you have valid concerns."
+4. Refocus on issues: "Let's focus on the issues, not personal attacks."
+5. Facilitate resolution: "How can we find a solution that works for everyone?"
+
+**Key Techniques:**
+- Early intervention
+- Separation when needed
+- Validation of perspectives
+- Refocusing on issues
+- Facilitating resolution
+
+### 8.2. Practice and Skill Development
+
+#### 8.2.1. Regular Practice
+
+**Practice Opportunities:**
+- Role-play scenarios with colleagues
+- Review past de-escalation attempts
+- Practice techniques in low-stakes situations
+- Seek feedback from colleagues
+- Learn from successful de-escalations
+
+**Skill Development:**
+- Regular training and education
+- Learning from case studies
+- Practising techniques
+- Building confidence
+- Continuous improvement
+
+#### 8.2.2. Reflection and Learning
+
+**Reflection Practices:**
+- Reflect on de-escalation attempts
+- Identify what worked and what didn't
+- Learn from mistakes
+- Celebrate successes
+- Continuously improve
+
+**Learning from Experience:**
+- Review successful de-escalations
+- Analyse unsuccessful attempts
+- Learn from colleagues' experiences
+- Stay current with best practices
+- Adapt and improve techniques
+
+## 9. SELF-CARE AND SUPPORT
+
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides de-escalation-specific considerations; refer to the self-care resources document for comprehensive guidance.
+
+### 9.1. De-escalation-Specific Self-Care Considerations
+
+#### 9.1.1. Emotional Impact
+
+**Additional Considerations for De-escalation Work:**
+- De-escalation work can be emotionally demanding
+- Exposure to high emotions can be draining
+- Managing difficult situations can be stressful
+- Balancing de-escalation with other responsibilities
+- Recognising when you need support
+
+**Self-Care Practices:**
+- Take breaks between difficult de-escalation situations
+- Practice grounding techniques when feeling overwhelmed
+- Connect with colleagues for support and debriefing
+- Maintain perspective on your role and limitations
+- Access professional support when needed
+
+### 9.2. Support Systems
+
+**Team Support:**
+- Regular debriefing with colleagues
+- Sharing experiences and learning
+- Supporting each other
+- Celebrating successes
+- Providing mutual aid
+
+**Professional Support:**
+- Access to counselling when needed
+- Professional development opportunities
+- Regular training and education
+- Recognition and appreciation
+- Workload management
+
+### 9.3. Continuous Improvement
+
+#### 9.3.1. Ongoing Learning
+
+**Learning Practices:**
+- Regular training and education
+- Reading about de-escalation techniques
+- Learning from case studies
+- Practising techniques
+- Seeking feedback and improvement
+
+**Skill Development:**
+- Building de-escalation skills
+- Developing communication abilities
+- Enhancing emotional intelligence
+- Improving conflict resolution
+- Strengthening support skills
+
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 10.1. Scenario 1: Angry Response to Moderation
+
+**Situation**: A community member is very angry about a moderation action you took. They're posting multiple angry messages, using strong language, and threatening to leave the community. Their messages are becoming increasingly emotional and personal.
+
+**Your Response:**
+1. What stage of escalation is this?
+2. How do you maintain a calm and centred presence?
+3. What de-escalation techniques do you use?
+4. What language do you use in your response?
+5. How do you acknowledge their feelings?
+6. How do you facilitate resolution?
+
+**Correct Answer**: This is agitation stage moving towards aggression. Stay calm, don't match emotional intensity, use supportive language ("I understand this is important to you"), acknowledge their feelings, provide clear explanation, listen actively, offer collaborative resolution, provide space if needed.
+
+### 10.2. Scenario 2: Escalating Conflict Between Members
+
+**Situation**: Two community members are in an escalating conflict. What started as a disagreement about a topic has become personal attacks, name-calling, and threats. The conflict is disrupting the community and other members are getting involved.
+
+**Your Response:**
+1. How do you intervene in this escalating conflict?
+2. Do you separate the parties?
+3. How do you acknowledge both perspectives?
+4. How do you refocus from personal attacks to issues?
+5. How do you facilitate resolution?
+6. What follow-up is needed?
+
+**Correct Answer**: Intervene early, separate parties if needed, acknowledge both perspectives and validate feelings, refocus from personal attacks to underlying issues, facilitate respectful discussion, find common ground, support collaborative resolution, monitor and follow up.
+
+### 10.3. Scenario 3: Threats During Escalation
+
+**Situation**: During a heated discussion, someone makes threats of violence. They're very emotional and seem to be escalating rapidly. The threats appear to be in response to feeling attacked or wronged.
+
+**Your Response:**
+1. Is de-escalation appropriate here?
+2. What is your priority?
+3. What actions do you take?
+4. How do you balance de-escalation with safety?
+5. When do you stop attempting de-escalation?
+
+**Correct Answer**: Safety is priority. Threats of violence require immediate protective action, not de-escalation attempts. Take immediate protective measures, remove threatening content, protect potential targets, escalate to security coordinator, document everything, report to authorities if credible threat.
+
+## 11. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This De-escalation Techniques Training document is part of our comprehensive staff development programme designed to prevent escalation and maintain safe, welcoming community environments. Effective de-escalation requires skill, practice, and self-awareness, and is an ongoing learning process. For questions about de-escalation techniques or to report training completion, please contact designated leadership through staff channels.*
+
diff --git a/src/content/docs/staff/training/documentation-transparency.md b/src/content/docs/staff/training/documentation-transparency.md
index fd159a6..173031b 100644
--- a/src/content/docs/staff/training/documentation-transparency.md
+++ b/src/content/docs/staff/training/documentation-transparency.md
@@ -2,13 +2,13 @@
 title: Documentation and Transparency Training for Staff
 ---
 
-**MANDATORY TRAINING FOR ALL STAFF MEMBERS**
+**MANDATORY TRAINING FOR ALL TEAM MEMBERS**
 
 ## 1. INTRODUCTION AND IMPORTANCE
 
 ### 1.1. Purpose and Scope
 
-This training provides comprehensive guidance for all staff members on documentation practices and transparency requirements within our community. Proper documentation and transparency are essential for accountability, consistency, legal compliance, and community trust.
+This training provides comprehensive guidance for all Team members on documentation practices and transparency requirements within our community. Proper documentation and transparency are essential for accountability, consistency, legal compliance, and community trust.
 
 ### 1.2. Why Documentation and Transparency Matter
 
@@ -28,7 +28,7 @@ This training provides comprehensive guidance for all staff members on documenta
 - Provides evidence of good-faith efforts and proper procedures
 - Documents compliance with legal requirements and policies
 - Creates records needed for legal proceedings if necessary
-- Protects both organisation and individual staff members
+- Protects both organisation and individual Team members
 
 ### 1.3. Integration with Existing Systems
 
@@ -51,11 +51,11 @@ This training operates within our comprehensive framework:
 **Essential Requirements:**
 - **Factual Accuracy**: Record only verifiable facts, not interpretations or assumptions
 - **Complete Context**: Include sufficient context for others to understand decisions
-- **Timely Recording**: Document actions and decisions promptly while information is fresh
+- **Timely Recording**: Document actions and decisions promptly whilst information is fresh
 - **Objective Language**: Use neutral, professional language without bias or emotion
 
 **Documentation Standards:**
-- **Who**: All parties involved, including staff members taking action
+- **Who**: All parties involved, including Team members taking action
 - **What**: Specific actions taken, policies applied, and decisions made
 - **When**: Exact dates and times of incidents and responses
 - **Where**: Platforms, channels, or locations where incidents occurred
@@ -91,14 +91,14 @@ This training operates within our comprehensive framework:
 **Complex Incident Documentation:**
 - **Background Context**: Relevant history or patterns leading to incident
 - **Multiple Perspectives**: Documentation of different viewpoints when relevant
-- **Consultation Notes**: Input from other staff members or leadership
+- **Consultation Notes**: Input from other Team members or Leadership
 - **Escalation Process**: Steps taken to involve senior staff or external authorities
 - **Resolution Outcomes**: Final resolution and effectiveness assessment
 
 #### 2.2.2. Ongoing Monitoring Documentation
 
 **Pattern Recognition Records:**
-- **Behavior Patterns**: Documentation of concerning behaviour patterns over time
+- **Behaviour Patterns**: Documentation of concerning behaviour patterns over time
 - **Escalation Tracking**: How situations have developed or escalated
 - **Intervention Effectiveness**: Success or failure of various intervention attempts
 - **Risk Assessment**: Current risk levels and monitoring requirements
@@ -124,8 +124,8 @@ This training operates within our comprehensive framework:
 **System Features:**
 - **Real-time Logging**: Actions are logged immediately when taken
 - **Searchable Database**: Community can search and review moderation history
-- **Anonymous Protection**: Personal information is protected while maintaining transparency
-- **Staff Identification**: Shows which staff member took each action
+- **Anonymous Protection**: Personal information is protected whilst maintaining transparency
+- **Team Identification**: Shows which Team member took each action
 - **Appeal Tracking**: Documents appeal processes and outcomes
 
 #### 3.1.2. What Gets Logged in Hikari
@@ -179,7 +179,7 @@ This training operates within our comprehensive framework:
 **Date/Time**: [Exact timestamp]
 **Platform**: [Discord/Forum/Repository/etc.]
 **User(s) Involved**: [Anonymized identifiers]
-**Staff Member**: [Your name/identifier]
+**Team Member**: [Your name/identifier]
 **Policy Violated**: [Specific policy section]
 **Description**: [Factual description of incident]
 **Evidence**: [Screenshots/logs/witnesses]
@@ -257,8 +257,8 @@ This training operates within our comprehensive framework:
 
 **Content Redaction:**
 - **Selective Quoting**: Include only relevant portions of content
-- **Context Preservation**: Maintain enough context for understanding while protecting privacy
-- **Sensitive Content Removal**: Remove personal details while preserving policy violation evidence
+- **Context Preservation**: Maintain enough context for understanding whilst protecting privacy
+- **Sensitive Content Removal**: Remove personal details whilst preserving policy violation evidence
 - **Multiple Version Management**: Maintain both full records and redacted public versions
 
 ## 5. DOCUMENTATION FOR DIFFERENT TYPES OF ACTIONS
@@ -285,7 +285,7 @@ This training operates within our comprehensive framework:
 
 **Warnings and Cautions:**
 - **Warning Level**: Informal guidance, formal warning, or final warning
-- **Specific Behaviors**: Exact behaviours or actions that prompted warning
+- **Specific Behaviours**: Exact behaviours or actions that prompted warning
 - **Expectations**: Clear expectations for future behaviour
 - **Resources Provided**: Educational materials or support resources offered
 - **Timeline**: Timeframe for expected behaviour improvement
@@ -327,7 +327,7 @@ This training operates within our comprehensive framework:
 
 **Quality Assurance Reviews:**
 - **Review Trigger**: What prompted the quality assurance review
-- **Review Team**: Which staff members participated in the review
+- **Review Team**: Which Team members participated in the review
 - **Standards Assessment**: How action measured against community standards
 - **Consistency Check**: Comparison with similar situations and actions
 - **Recommendations**: Suggestions for improvement or policy clarification
@@ -341,7 +341,7 @@ This training operates within our comprehensive framework:
 
 **Clarity Principles:**
 - **Simple Language**: Use clear, straightforward language without unnecessary jargon
-- **Active Voice**: Use active voice when possible ("Staff member issued warning" rather than "Warning was issued")
+- **Active Voice**: Use active voice when possible ("Team member issued warning" rather than "Warning was issued")
 - **Specific Details**: Include specific facts rather than general descriptions
 - **Logical Organisation**: Present information in logical order with clear connections
 
@@ -422,7 +422,7 @@ This training operates within our comprehensive framework:
 - **Seek Understanding**: Try to understand underlying concerns behind defensive responses
 
 **Emotional Situations:**
-- **Acknowledge Feelings**: Validate emotions while maintaining professional boundaries
+- **Acknowledge Feelings**: Validate emotions whilst maintaining professional boundaries
 - **Provide Support**: Offer appropriate support resources when users are distressed
 - **Clear Boundaries**: Maintain clear boundaries about what support you can and cannot provide
 - **Follow-up**: Appropriate follow-up to ensure ongoing support when needed
@@ -470,9 +470,9 @@ This training operates within our comprehensive framework:
 - **Improvement Identification**: Identify areas for improvement in your own documentation practices
 
 **Peer Review Participation:**
-- **Colleague Review**: Regular review of documentation by other staff members
+- **Colleague Review**: Regular review of documentation by other Team members
 - **Feedback Integration**: Incorporate feedback from peer reviews into improved practices
-- **Knowledge Sharing**: Share documentation best practices with other staff members
+- **Knowledge Sharing**: Share documentation best practices with other Team members
 - **Collaborative Improvement**: Work with team to improve overall documentation quality
 
 #### 8.1.2. Systematic Quality Improvement
@@ -495,7 +495,7 @@ This training operates within our comprehensive framework:
 
 **Learning from Cases:**
 - **Anonymized Examples**: Develop anonymized case studies for training purposes
-- **Success Analysis**: Analyze successful interventions and their documentation
+- **Success Analysis**: Analyse successful interventions and their documentation
 - **Challenge Review**: Review challenging cases to improve future responses
 - **Best Practice Identification**: Identify and document best practices for different situations
 
@@ -581,67 +581,15 @@ This training operates within our comprehensive framework:
 - **Appeal Support**: Provide documentation that supports fair appeal processes
 - **Trust Building**: Use documentation practices to build and maintain community trust
 
-## 10. TRAINING COMPLETION AND CERTIFICATION
+## 10. TRAINING REQUIREMENTS
 
-### 10.1. Competency Requirements
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
 
-#### 10.1.1. Essential Skills Demonstration
-
-**Documentation Skills:**
-- **Complete Documentation**: Demonstrate ability to create complete, accurate documentation
-- **Appropriate Privacy**: Show understanding of privacy requirements and anonymization techniques
-- **Professional Communication**: Exhibit professional writing and communication skills
-- **System Proficiency**: Show proficiency with documentation systems and tools
-
-**Transparency Skills:**
-- **Public Communication**: Demonstrate ability to communicate transparently with community
-- **Conflict Navigation**: Show skills in handling difficult conversations about moderation decisions
-- **Educational Approach**: Exhibit ability to use transparency for community education and improvement
-- **Feedback Integration**: Show ability to receive and integrate community feedback
-
-#### 10.1.2. Practical Application
-
-**Scenario-Based Assessment:**
-- **Documentation Scenarios**: Complete realistic documentation scenarios with feedback
-- **Privacy Scenarios**: Demonstrate appropriate privacy protection in complex situations
-- **Communication Scenarios**: Practice transparent communication in challenging situations
-- **Appeal Scenarios**: Practice documentation and communication for appeal processes
-
-**Real-World Application:**
-- **Supervised Practice**: Complete real documentation under supervision with feedback
-- **Peer Review**: Participate in peer review processes for documentation quality
-- **Community Interaction**: Practice transparent communication with community members
-- **Continuous Learning**: Show commitment to ongoing learning and improvement
-
-### 10.2. Ongoing Development and Support
-
-#### 10.2.1. Continuous Learning Requirements
-
-**Regular Training:**
-- **Monthly Updates**: Participate in monthly training updates on documentation practices
-- **Policy Changes**: Complete training on policy changes and their documentation implications
-- **System Updates**: Learn new features and capabilities of documentation systems
-- **Best Practice Sharing**: Participate in best practice sharing with other staff members
-
-**Advanced Development:**
-- **Specialized Training**: Complete specialised training for complex documentation situations
-- **Leadership Development**: Training for staff members who will train others
-- **System Administration**: Technical training for staff members who will manage documentation systems
-- **Legal Updates**: Training on legal developments affecting documentation requirements
-
-#### 10.2.2. Support Systems
-
-**Peer Support:**
-- **Documentation Partners**: Pairing with experienced staff for ongoing support and guidance
-- **Team Reviews**: Regular team reviews of documentation practices and challenges
-- **Problem Solving**: Collaborative problem-solving for difficult documentation situations
-- **Knowledge Sharing**: Regular sharing of tips, techniques, and lessons learned
-
-**Leadership Support:**
-- **Supervisory Guidance**: Regular guidance from supervisors on documentation quality and compliance
-- **Professional Development**: Support for professional development opportunities
-- **Resource Access**: Access to necessary tools, systems, and resources for effective documentation
-- **Feedback and Recognition**: Regular feedback and recognition for quality documentation practices
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/harassment-bullying-response.md b/src/content/docs/staff/training/harassment-bullying-response.md
new file mode 100644
index 0000000..efeb05d
--- /dev/null
+++ b/src/content/docs/staff/training/harassment-bullying-response.md
@@ -0,0 +1,675 @@
+---
+title: Harassment and Bullying Response Training for Staff
+---
+
+**MANDATORY TRAINING FOR ALL TEAM MEMBERS**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides essential guidance for all Team members on recognising, responding to, and managing harassment and bullying within our community. Harassment and bullying create unsafe environments and drive away community members, particularly those from marginalised groups. All Team members must be prepared to respond effectively to protect community members and maintain safe spaces.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive safety and protection framework:
+
+**(a)** **Community Code of Conduct**: Behavioural expectations and anti-harassment standards;
+
+**(b)** **Content and Moderation Policy**: Enforcement procedures and content restrictions;
+
+**(c)** **Conflict Resolution Policy**: Procedures for resolving disputes (harassment may escalate to conflicts);
+
+**(d)** **Crisis Response Policy**: Emergency response procedures for severe harassment situations;
+
+**(e)** **Child Safety Policy**: Special procedures for harassment involving minors;
+
+**(f)** **Criminal Activity Policy**: Procedures for harassment that constitutes criminal activity;
+
+**(g)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Critical Understanding
+
+**Harassment vs. Conflict:**
+- **Harassment**: Unwanted, targeted behaviour intended to harm, intimidate, or control
+- **Conflict**: Disagreement or dispute between parties with different perspectives
+- Harassment requires immediate protective action; conflicts may benefit from mediation
+- Harassment victims need protection and support; conflict parties may both need resolution
+
+**Our Stance:**
+- Zero tolerance for harassment and bullying
+- We believe and support harassment victims
+- We prioritise victim safety over perpetrator comfort
+- We take harassment seriously regardless of intent
+
+## 2. UNDERSTANDING HARASSMENT AND BULLYING
+
+### 2.1. Definition and Types
+
+#### 2.1.1. What Is Harassment?
+
+**Harassment** is unwanted, targeted behaviour that creates an intimidating, hostile, or offensive environment. It is characterized by:
+- **Unwanted**: Behaviour not welcomed by the recipient
+- **Targeted**: Directed at specific individuals or groups
+- **Persistent**: Often repeated or ongoing
+- **Harmful**: Causes emotional, psychological, or physical harm
+- **Power Imbalance**: Often involves power differentials
+
+**Key Characteristics:**
+- Behaviour that a reasonable person would find offensive
+- Creates hostile or intimidating environment
+- Interferes with ability to participate in community
+- Based on protected characteristics or personal attributes
+
+#### 2.1.2. Types of Harassment
+
+**Identity-Based Harassment:**
+- Harassment based on race, ethnicity, or national origin
+- Harassment based on gender, gender identity, or sexual orientation
+- Harassment based on disability or health conditions
+- Harassment based on religion or belief
+- Harassment based on age or other protected characteristics
+
+**Behavioural Harassment:**
+- Cyberbullying and online harassment
+- Stalking and unwanted contact
+- Doxxing and privacy violations
+- Threats and intimidation
+- Exclusion and ostracism
+
+**Sexual Harassment:**
+- Unwanted sexual comments or advances
+- Sexual jokes or innuendo
+- Sharing sexual content without consent
+- Pressure for sexual favours or relationships
+- Sexualized insults or attacks
+
+**Professional Harassment:**
+- Harassment targeting someone's work or contributions
+- Undermining professional reputation
+- Sabotaging work or projects
+- Exclusion from professional opportunities
+- Professional retaliation
+
+### 2.2. Understanding Bullying
+
+#### 2.2.1. What Is Bullying?
+
+**Bullying** is repeated, aggressive behaviour intended to harm someone perceived as vulnerable. It involves:
+- **Repetition**: Behaviour occurs multiple times
+- **Power Imbalance**: Perpetrator has more power than victim
+- **Intent to Harm**: Behaviour intended to cause harm
+- **Targeting**: Directed at specific individuals
+
+**Bullying vs. Harassment:**
+- Bullying often focuses on power and control
+- Harassment may be based on protected characteristics
+- Both create hostile environments
+- Both require immediate intervention
+
+#### 2.2.2. Forms of Bullying
+
+**Direct Bullying:**
+- Verbal attacks and insults
+- Physical threats or intimidation
+- Public humiliation or shaming
+- Direct threats or coercion
+
+**Indirect Bullying:**
+- Social exclusion and ostracism
+- Spreading rumors or lies
+- Encouraging others to exclude or attack
+- Undermining reputation or work
+
+**Cyberbullying:**
+- Harassment through digital platforms
+- Sharing embarrassing content
+- Creating fake accounts to attack
+- Coordinated attacks from multiple accounts
+
+## 3. RECOGNISING HARASSMENT AND BULLYING
+
+### 3.1. Warning Signs and Indicators
+
+#### 3.1.1. Behavioural Indicators of Harassment
+
+**Perpetrator Behaviours:**
+- Repeated unwanted contact after being asked to stop
+- Escalating behaviour when boundaries are set
+- Targeting specific individuals or groups
+- Using power or influence to intimidate
+- Refusing to respect "no" or boundaries
+- Isolating victims from support systems
+- Spreading rumors or false information
+- Coordinating attacks with others
+
+**Pattern Recognition:**
+- Behaviour escalates over time
+- Multiple targets over time
+- Similar patterns with different victims
+- Defensive or dismissive responses when confronted
+- History of boundary violations
+
+#### 3.1.2. Victim Indicators
+
+**Signs Someone Is Being Harassed:**
+- Sudden withdrawal from community activities
+- Changes in communication patterns
+- Expressing fear or discomfort about specific individuals
+- Avoiding certain spaces or topics
+- Reporting feeling unsafe or unwelcome
+- Changes in behaviour or personality
+- Expressing anxiety or distress
+- Mentioning unwanted contact or attention
+
+**Behavioural Changes:**
+- Decreased participation in discussions
+- Avoiding certain community members
+- Reluctance to speak up or contribute
+- Defensive or anxious responses
+- Mentioning wanting to leave community
+
+### 3.2. Context and Severity Assessment
+
+#### 3.2.1. Severity Levels
+
+**Severe Harassment (IMMEDIATE ACTION REQUIRED):**
+- Threats of violence or harm
+- Doxxing or privacy violations
+- Stalking behaviours
+- Sexual harassment or assault
+- Coordinated attacks
+- Harassment targeting minors
+- Harassment that creates immediate safety risk
+
+**Moderate Harassment (RESPOND WITHIN 1 HOUR):**
+- Persistent unwanted contact
+- Identity-based harassment
+- Professional harassment affecting work
+- Exclusion or ostracism campaigns
+- Spreading false information
+- Harassment affecting ability to participate
+
+**Mild Harassment (RESPOND WITHIN 24 HOURS):**
+- Isolated incidents of unwanted behaviour
+- Boundary violations
+- Inappropriate comments or jokes
+- Minor exclusion behaviours
+- Behaviour that may escalate if not addressed
+
+#### 3.2.2. Context Considerations
+
+**Power Dynamics:**
+- Harassment from Team member to community member (severe)
+- Harassment from established member to new member (moderate-severe)
+- Harassment between peers (moderate)
+- Harassment from community member to staff (severe)
+
+**Impact Assessment:**
+- Number of people affected
+- Severity of impact on victims
+- Community-wide effects
+- Potential for escalation
+- Historical context and patterns
+
+**Marginalization Factors:**
+- Harassment targeting marginalised individuals (more severe)
+- Intersectional harassment (multiple forms of marginalization)
+- Harassment that reinforces systemic oppression
+- Harassment that creates exclusionary environment
+
+## 4. IMMEDIATE RESPONSE PROCEDURES
+
+### 4.1. Severe Harassment Response Protocol
+
+**IMMEDIATE ACTIONS (Within 15 minutes):**
+
+1. **PROTECT THE VICTIM** - Take immediate steps to ensure victim safety
+2. **STOP THE HARASSMENT** - Remove harassing content and prevent further contact
+3. **PRESERVE EVIDENCE** - Screenshot and document all harassment immediately
+4. **ESCALATE IMMEDIATELY** - Notify senior staff and harassment coordinator
+5. **SUPPORT THE VICTIM** - Contact victim to provide support and resources
+6. **DOCUMENT EVERYTHING** - Create comprehensive documentation
+7. **CONSIDER LEGAL ACTION** - Assess if criminal activity or legal action needed
+
+**Example Response Template:**
+```
+URGENT HARASSMENT INCIDENT
+
+[Description of harassment]
+[Victim information]
+[Perpetrator information]
+[Platform/channel where occurred]
+[Time and date]
+[Severity assessment]
+[Evidence attached]
+
+Immediate protective measures taken: [list]
+Escalating to harassment coordinator and senior staff.
+Victim contacted and provided support resources.
+```
+
+### 4.2. Moderate Harassment Response Protocol
+
+**ACTIONS (Within 1 hour):**
+
+1. **ACKNOWLEDGE THE REPORT** - Respond to victim promptly
+2. **ASSESS THE SITUATION** - Gather information and evidence
+3. **TAKE PROTECTIVE MEASURES** - Implement appropriate protections
+4. **DOCUMENT THE INCIDENT** - Create comprehensive documentation
+5. **ESCALATE** - Notify harassment coordinator
+6. **SUPPORT VICTIM** - Provide support and resources
+7. **ADDRESS PERPETRATOR** - Take appropriate action against perpetrator
+
+**Example Response Template:**
+```
+HARASSMENT INCIDENT REPORT
+
+[Description of harassment]
+[Parties involved]
+[Platform/channel]
+[Time and date]
+[Evidence attached]
+
+Assessment: Moderate severity
+Protective measures implemented: [list]
+Escalating to harassment coordinator.
+```
+
+### 4.3. Mild Harassment Response Protocol
+
+**ACTIONS (Within 24 hours):**
+
+1. **ACKNOWLEDGE CONCERN** - Respond to report promptly
+2. **GATHER INFORMATION** - Collect relevant details and evidence
+3. **ASSESS PATTERNS** - Check for previous incidents or patterns
+4. **ADDRESS BEHAVIOR** - Take appropriate action to stop behaviour
+5. **DOCUMENT** - Create documentation of incident and response
+6. **FOLLOW UP** - Monitor situation and follow up with victim
+
+## 5. SUPPORTING HARASSMENT VICTIMS
+
+### 5.1. Victim-Centred Approach
+
+#### 5.1.1. Core Principles
+
+**Believe and Validate:**
+- Believe victims when they report harassment
+- Validate their experiences and feelings
+- Don't question or minimise their experiences
+- Recognise that harassment is never the victim's fault
+
+**Empowerment:**
+- Give victims choices about how to proceed
+- Respect their decisions about reporting and action
+- Support their autonomy and agency
+- Don't pressure them into actions they don't want
+
+**Safety First:**
+- Prioritise victim safety above all else
+- Take immediate protective measures
+- Respect victim's privacy and confidentiality
+- Don't require victims to confront perpetrators
+
+#### 5.1.2. Communication with Victims
+
+**Do's:**
+- **Listen Actively**: Give full attention and listen without judgement
+- **Believe**: Express belief and validation
+- **Support**: Offer support and resources
+- **Explain Process**: Explain what will happen next
+- **Respect Choices**: Respect victim's decisions about how to proceed
+- **Maintain Privacy**: Protect victim's privacy and confidentiality
+
+**Don'ts:**
+- **Don't Blame**: Never suggest victim did anything wrong
+- **Don't Minimise**: Don't minimise the seriousness of harassment
+- **Don't Question**: Don't question why victim didn't report sooner
+- **Don't Pressure**: Don't pressure victim into actions they don't want
+- **Don't Share Details**: Don't share victim's information without consent
+- **Don't Require Confrontation**: Don't require victim to confront perpetrator
+
+### 5.2. Providing Resources and Support
+
+#### 5.2.1. Immediate Support Resources
+
+**Emotional Support:**
+- Crisis support hotlines and services
+- Counselling and mental health resources
+- Peer support groups
+- Online support communities
+- Trauma-informed support services
+
+**Practical Support:**
+- Information about reporting options
+- Legal resources and advice
+- Safety planning resources
+- Technical support for blocking and privacy
+- Community support and connection
+
+#### 5.2.2. Ongoing Support
+
+**Follow-Up:**
+- Check in with victims regularly
+- Monitor for continued harassment
+- Provide ongoing support and resources
+- Adjust protective measures as needed
+- Support recovery and healing
+
+**Community Support:**
+- Connect victims with supportive community members
+- Facilitate supportive spaces
+- Address community-wide impacts
+- Prevent isolation and exclusion
+- Support reintegration when ready
+
+## 6. ADDRESSING PERPETRATORS
+
+### 6.1. Perpetrator Response Procedures
+
+#### 6.1.1. Immediate Actions
+
+**When Addressing Perpetrators:**
+1. **STOP THE BEHAVIOR** - Clearly communicate that behaviour must stop
+2. **DOCUMENT** - Document all interactions and responses
+3. **ASSESS RESPONSE** - Evaluate perpetrator's response to intervention
+4. **IMPLEMENT CONSEQUENCES** - Apply appropriate consequences
+5. **MONITOR** - Monitor for continued or escalated behaviour
+
+**Communication Approach:**
+- Clear and direct about what behaviour is unacceptable
+- Explain impact of behaviour on victims
+- Set clear expectations for change
+- Explain consequences of continued behaviour
+- Provide opportunity for education and change when appropriate
+
+#### 6.1.2. Progressive Response Framework
+
+**Educational Response:**
+- Clear explanation of why behaviour is harmful
+- Education about impact on victims
+- Resources for learning and growth
+- Opportunity to change behaviour
+- Monitoring and support for change
+
+**Restrictive Response:**
+- Temporary restrictions on community participation
+- Limited access to certain spaces or features
+- Required supervision or monitoring
+- No-contact orders with victims
+- Probationary periods with clear expectations
+
+**Protective Response:**
+- Removal from community spaces
+- Permanent restrictions or bans
+- Public accountability when necessary for community safety
+- Coordination with other platforms when appropriate
+- Legal action when harassment is criminal
+
+### 6.2. Accountability and Consequences
+
+#### 6.2.1. Determining Appropriate Consequences
+
+**Factors to Consider:**
+- Severity and impact of harassment
+- History of previous incidents
+- Perpetrator's response to intervention
+- Risk of continued or escalated harassment
+- Community safety and protection needs
+
+**Consequence Principles:**
+- Consequences should match severity and impact
+- Consider potential for rehabilitation and change
+- Prioritize victim safety and community protection
+- Be consistent with previous similar cases
+- Document reasoning for accountability
+
+#### 6.2.2. Rehabilitation and Change
+
+**When Rehabilitation Is Appropriate:**
+- Perpetrator shows genuine remorse and understanding
+- Perpetrator commits to specific behaviour changes
+- Harassment was not severe or criminal
+- Perpetrator engages with education and support
+- Community safety can be maintained
+
+**Rehabilitation Process:**
+- Required education and training
+- Clear behavioural expectations
+- Monitoring and accountability
+- Support for positive change
+- Gradual restoration of privileges with continued monitoring
+
+## 7. PREVENTION STRATEGIES
+
+### 7.1. Proactive Community Culture
+
+#### 7.1.1. Creating Safe Environments
+
+**Community Culture:**
+- Clear anti-harassment policies and expectations
+- Active promotion of respectful behaviour
+- Celebration of diversity and inclusion
+- Quick response to harassment reports
+- Support for victims and accountability for perpetrators
+
+**Community Education:**
+- Regular reminders about anti-harassment policies
+- Education about recognising and reporting harassment
+- Resources for bystander intervention
+- Information about support resources
+- Clear communication about consequences
+
+#### 7.1.2. Early Intervention
+
+**Pattern Recognition:**
+- Monitor for early warning signs
+- Address boundary violations promptly
+- Intervene before behaviour escalates
+- Provide education and support early
+- Prevent escalation to severe harassment
+
+**Bystander Intervention:**
+- Educate community about bystander intervention
+- Encourage supportive responses to harassment
+- Provide tools for safe intervention
+- Support bystanders who intervene
+- Recognise and celebrate positive intervention
+
+### 7.2. Staff Training and Preparedness
+
+#### 7.2.1. Ongoing Training
+
+**Regular Updates:**
+- Quarterly harassment response training updates
+- Review of new harassment patterns and tactics
+- Updates on best practices and research
+- Case study reviews and learning sessions
+- Training on supporting specific populations
+
+**Skill Development:**
+- Recognition of harassment patterns
+- Victim support and communication
+- Perpetrator response and accountability
+- Documentation and evidence preservation
+- Prevention and early intervention
+
+#### 7.2.2. Policy and Process Improvement
+
+**Continuous Improvement:**
+- Regular review of harassment policies
+- Updates based on new patterns and threats
+- Improvement of response procedures
+- Enhancement of prevention measures
+- Integration of community feedback
+
+## 8. DOCUMENTATION AND ACCOUNTABILITY
+
+### 8.1. Comprehensive Documentation
+
+#### 8.1.1. Incident Documentation
+
+**Essential Information:**
+- Date, time, and platform where harassment occurred
+- Victim and perpetrator information
+- Description of harassment behaviour
+- Evidence (screenshots, logs, witnesses)
+- Impact on victim and community
+- Actions taken and responses
+- Follow-up plans and monitoring
+
+**Privacy Considerations:**
+- Protect victim privacy and confidentiality
+- Limit access to authorized personnel
+- Anonymize when sharing for training
+- Secure storage of sensitive information
+- Balance transparency with privacy protection
+
+#### 8.1.2. Pattern Documentation
+
+**Tracking Patterns:**
+- Document patterns of harassment behaviour
+- Track repeat perpetrators
+- Identify community-wide issues
+- Monitor effectiveness of responses
+- Identify prevention opportunities
+
+### 8.2. Accountability and Review
+
+#### 8.2.1. Quality Assurance
+
+**Regular Review:**
+- Review harassment response effectiveness
+- Assess victim satisfaction and outcomes
+- Evaluate perpetrator accountability
+- Identify areas for improvement
+- Ensure consistency in responses
+
+**Community Feedback:**
+- Collect feedback from harassment victims
+- Gather community input on harassment policies
+- Assess community safety and trust
+- Identify gaps in prevention or response
+- Integrate feedback into improvements
+
+#### 8.2.2. Transparency and Communication
+
+**Appropriate Transparency:**
+- Public transparency about harassment policies
+- General information about response procedures
+- Accountability measures when appropriate for community safety
+- Privacy protection for individual cases
+- Balance transparency with victim protection
+
+## 9. SELF-CARE AND EMOTIONAL SUPPORT
+
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides harassment-response-specific considerations; refer to the self-care resources document for comprehensive guidance.
+
+### 9.1. Harassment Response-Specific Self-Care Considerations
+
+#### 9.1.1. Understanding the Impact
+
+**Additional Considerations for Harassment Response Work:**
+- Exposure to harmful content and behaviour
+- Risk of secondary trauma from supporting victims
+- Need for emotional support and validation
+- Importance of maintaining boundaries with perpetrators
+- Regular supervision and support
+
+**Self-Care Practices:**
+- Limit exposure to harmful content when possible
+- Take breaks after reviewing harassment reports
+- Connect with supportive colleagues
+- Practice self-compassion and validation
+- Access trauma-informed support resources
+
+### 9.2. Support Systems
+
+#### 9.2.1. Team Support
+
+**Peer Support:**
+- Regular check-ins with colleagues working on harassment response
+- Debriefing sessions after difficult incidents
+- Sharing successful strategies and lessons learned
+- Mutual support and understanding
+- Celebration of positive outcomes
+
+**Supervisory Support:**
+- Regular meetings with supervisors to discuss challenges
+- Access to additional resources and support
+- Workload management and distribution
+- Recognition of difficult work
+- Professional development opportunities
+
+#### 9.2.2. Professional Resources
+
+**Mental Health Support:**
+- Access to counselling and mental health resources
+- Support groups for professionals working in harassment response
+- Trauma-informed therapy resources
+- Crisis support when needed
+- Ongoing mental health maintenance
+
+**Professional Development:**
+- Training on trauma-informed practices
+- Education on secondary trauma and burnout prevention
+- Skills development for managing difficult situations
+- Access to professional resources and networks
+- Career development support
+
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 10.1. Scenario 1: Persistent Harassment Report
+
+**Situation**: A community member reports that another member has been sending them unwanted messages for two weeks, asking personal questions, trying to move conversations to private platforms, and making them feel uncomfortable. The behaviour has been escalating.
+
+**Your Response:**
+1. What risk level is this?
+2. What immediate actions should you take?
+3. How do you protect and support the victim?
+4. What evidence should you preserve?
+5. Who should you escalate to?
+6. How do you address the perpetrator?
+
+**Correct Answer**: Moderate to high risk depending on escalation. Immediately protect victim, preserve all evidence (screenshots, logs, timestamps), contact victim to provide support, escalate to harassment coordinator, assess perpetrator response and take appropriate action.
+
+### 10.2. Scenario 2: Harassment Appeal
+
+**Situation**: After taking action against a harasser, they appeal saying the victim "overreacted" and they were "just being friendly." They claim the victim misunderstood their intentions.
+
+**Your Response:**
+1. How do you review this appeal?
+2. What factors do you consider?
+3. How do you balance perpetrator's perspective with victim's experience?
+4. What do you communicate to both parties?
+5. How do you document your decision?
+
+**Correct Answer**: Review all evidence objectively, consider victim's perspective and impact, assess whether behaviour meets harassment definition regardless of intent, maintain decision if harassment occurred, explain reasoning clearly to both parties, document comprehensively.
+
+### 10.3. Scenario 3: Victim Requests No Action
+
+**Situation**: A harassment victim reports harassment but asks you not to take action because they're afraid of retaliation from the perpetrator. They want you to "just be aware" of the situation.
+
+**Your Response:**
+1. Can you honour their request to take no action?
+2. How do you balance victim's wishes with community safety?
+3. What protective measures can you take?
+4. How do you support the victim?
+5. What do you communicate to the victim?
+
+**Correct Answer**: Cannot ignore harassment for community safety, but can take protective measures that minimise victim exposure. Take necessary protective action (restrictions, no-contact orders), explain why action is needed for community safety, provide ongoing support to victim, monitor situation closely.
+
+## 11. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Harassment and Bullying Response Training document is part of our comprehensive Team development programme designed to ensure effective recognition and response to harassment whilst protecting victims and maintaining safe community environments. Harassment response is critical to community safety, and all Team members must complete this training before assuming moderation responsibilities. For questions about harassment response procedures or to report training completion, please contact the Harassment Response Coordinator through designated Team channels.*
+
diff --git a/src/content/docs/staff/training/inclusive-moderation.md b/src/content/docs/staff/training/inclusive-moderation.md
index c7faf83..b2eba5e 100644
--- a/src/content/docs/staff/training/inclusive-moderation.md
+++ b/src/content/docs/staff/training/inclusive-moderation.md
@@ -8,7 +8,7 @@ title: Inclusive Moderation Training for Staff
 
 ### 1.1. Purpose and Importance
 
-This training provides essential guidance for staff members on conducting moderation that upholds our community's core values of inclusivity, respect, and safety. Inclusive moderation goes beyond enforcing rules—it requires understanding the impact of our decisions on marginalised community members and actively working to create welcoming spaces for all.
+This training provides essential guidance for Team members on conducting moderation that upholds our community's core values of inclusivity, respect, and safety. Inclusive moderation goes beyond enforcing rules—it requires understanding the impact of our decisions on marginalised community members and actively working to create welcoming spaces for all.
 
 ### 1.2. Our Community's Social Justice Stance
 
@@ -26,7 +26,7 @@ This training operates within our comprehensive policy framework:
 
 **(c)** **Community Leadership and Governance Policy**: Accountability mechanisms and leadership standards;
 
-**(d)** **Staff Handbook**: General expectations for all staff members.
+**(d)** **Staff Handbook**: General expectations for all Team members.
 
 ## 2. UNDERSTANDING INCLUSIVE MODERATION
 
@@ -101,7 +101,7 @@ This training operates within our comprehensive policy framework:
 
 ### 3.3. Recognising Microaggressions
 
-**Microaggressions**: Subtle, often unconscious acts of discrimination that communicate bias toward marginalised groups.
+**Microaggressions**: Subtle, often unconscious acts of discrimination that communicate bias towards marginalised groups.
 
 **Examples in Tech Communities:**
 - "You're so articulate!" (implying surprise that a person of colour speaks well)
@@ -257,6 +257,8 @@ This training operates within our comprehensive policy framework:
 
 ### 5.2. Trauma-Informed Communication
 
+**Reference to Comprehensive Trauma-Informed Training**: For detailed trauma-informed moderation practices, understanding trauma responses, and comprehensive trauma-informed guidance, see [Trauma-Informed Moderation Training](/staff/training/trauma-informed-moderation). This section provides a brief overview; refer to the trauma-informed moderation training document for comprehensive guidance.
+
 #### 5.2.1. Understanding Trauma Responses
 
 **Common Trauma Responses:**
@@ -273,6 +275,8 @@ This training operates within our comprehensive policy framework:
 
 #### 5.2.2. De-escalation Techniques
 
+**Reference to Comprehensive De-escalation Training**: For detailed de-escalation techniques, communication strategies, and practical application guidance, see [De-escalation Techniques Training](/staff/training/de-escalation-techniques). This section provides a brief overview; refer to the de-escalation training document for comprehensive guidance.
+
 **When Someone Is Activated:**
 1. **Stay Calm**: Don't mirror heightened emotions
 2. **Validate**: Acknowledge their feelings are real and understandable
@@ -300,7 +304,7 @@ This training operates within our comprehensive policy framework:
 - Emphasise that inclusive communities require some behavioural boundaries
 - Reference community agreement and voluntary participation
 
-#### 6.1.3. "I Don't See Color/Gender/etc." Claims
+#### 6.1.3. "I Don't See Colour/Gender/etc." Claims
 
 **Response Strategy:**
 - Explain why "colorblindness" can be harmful
@@ -345,7 +349,7 @@ This training operates within our comprehensive policy framework:
 - Others emphasise egalitarian relationships
 - Power distance affects how people interact with moderators
 
-**Moderation Implication**: Adapt your communication style while maintaining consistent standards.
+**Moderation Implication**: Adapt your communication style whilst maintaining consistent standards.
 
 ### 7.2. Global Inclusivity Considerations
 
@@ -449,17 +453,61 @@ This training operates within our comprehensive policy framework:
 3. **Pattern Interruption**: Stop the pile-on before it escalates
 4. **Community Standards**: Reinforce expectations about believing marginalised voices
 
-## 10. ONGOING DEVELOPMENT AND SUPPORT
+## 10. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 10.1. Continuous Learning Requirements
+### 10.1. Scenario 1: Conflicting Marginalizations
 
-#### 10.1.1. Regular Training Updates
+**Situation**: A person of colour makes transphobic comments, and a white trans person responds with racially insensitive language. Both parties claim the other started it and that their own comments were justified responses.
+
+**Your Response:**
+1. How do you address both forms of harm without prioritising one over the other?
+2. How do you consider different power dynamics and systemic contexts?
+3. How do you help both parties understand intersectionality?
+4. How do you focus on creating safety for all marginalised individuals?
+5. What moderation actions do you take?
+6. How do you facilitate learning and growth?
+
+**Correct Answer**: Address both harms equally, recognise different systemic contexts (transphobia from person of colour vs. racism from white person), provide education about intersectionality, focus on community safety for all marginalised members, take appropriate action against both forms of discrimination, facilitate understanding and growth.
+
+### 10.2. Scenario 2: "Devil's Advocate" Pattern
+
+**Situation**: A user consistently plays "devil's advocate" on issues affecting marginalised communities, arguing for positions that cause harm. When called out, they say they're "just asking questions" and "trying to understand both sides." Marginalised community members are feeling silenced and unwelcome.
+
+**Your Response:**
+1. How do you recognise this as a pattern rather than isolated incidents?
+2. How do you explain the impact of "devil's advocate" arguments?
+3. How do you reinforce community values against oppression?
+4. How do you set boundaries about what positions are welcome?
+5. What moderation action is appropriate?
+6. How do you support marginalised community members?
+
+**Correct Answer**: Recognise pattern of harmful behaviour, explain how "devil's advocate" silences marginalised voices, reinforce community stance against oppression, set clear boundaries that some positions aren't open for debate, take progressive enforcement action, support and validate marginalised community members.
+
+### 10.3. Scenario 3: Gaslighting Marginalised Experiences
+
+**Situation**: Multiple users question a marginalised person's account of discrimination, suggesting they're "imagining things" or "being too sensitive." The marginalised person feels isolated and unsupported, and other marginalised members are watching and feeling unsafe.
+
+**Your Response:**
+1. How do you immediately support the marginalised person?
+2. How do you address the gaslighting behaviour?
+3. How do you stop the pile-on before it escalates?
+4. How do you reinforce community standards about believing marginalised voices?
+5. What actions do you take against gaslighting?
+6. How do you create safety for other marginalised members?
+
+**Correct Answer**: Immediately validate marginalised person's experience, address gaslighting as harmful behaviour, stop pile-on immediately, reinforce community standards about believing marginalised voices, take action against gaslighting behaviour, create clear safety message for all marginalised members, provide ongoing support.
+
+## 11. ONGOING DEVELOPMENT AND SUPPORT
+
+### 11.1. Continuous Learning Requirements
+
+#### 11.1.1. Regular Training Updates
 
 **Monthly**: Review new scenarios and community developments
 **Quarterly**: Update knowledge of best practices and resources
 **Annually**: Complete comprehensive inclusive moderation assessment
 
-#### 10.1.2. Learning Resources
+#### 11.1.2. Learning Resources
 
 **Essential Reading:**
 - Academic research on inclusive communities
@@ -467,9 +515,9 @@ This training operates within our comprehensive policy framework:
 - Current events affecting marginalised communities
 - Best practices from other inclusive organisations
 
-### 10.2. Support Systems for Staff
+### 11.2. Support Systems for Staff
 
-#### 10.2.1. Peer Support and Consultation
+#### 11.2.1. Peer Support and Consultation
 
 **Available Resources:**
 - Staff consultation channels for difficult situations
@@ -477,7 +525,7 @@ This training operates within our comprehensive policy framework:
 - Regular team discussions about inclusive practices
 - Access to subject matter experts on specific issues
 
-#### 10.2.2. Personal Impact Management
+#### 11.2.2. Personal Impact Management
 
 **Self-Care Considerations:**
 - Recognise emotional labour of inclusive moderation
@@ -485,35 +533,15 @@ This training operates within our comprehensive policy framework:
 - Maintain boundaries to prevent burnout
 - Celebrate progress and positive community changes
 
-## 11. CERTIFICATION AND ASSESSMENT
+## 12. TRAINING REQUIREMENTS
 
-### 11.1. Training Completion Requirements
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
 
-**To Complete Inclusive Moderation Training:**
-
-1. **Read and Understand** this complete training document
-2. **Complete Practice Scenarios** with senior staff review
-3. **Demonstrate Knowledge** of inclusive communication principles
-4. **Show Understanding** of community social justice stance
-5. **Commit to Ongoing Learning** and application of inclusive practices
-
-### 11.2. Ongoing Assessment Methods
-
-#### 11.2.1. Practical Application Review
-
-**Quarterly Assessment:**
-- Review of moderation decisions for inclusive principles
-- Feedback from marginalised community members
-- Self-reflection on growth areas
-- Goal setting for continued improvement
-
-#### 11.2.2. Community Impact Evaluation
-
-**Annual Review:**
-- Assessment of overall community inclusivity
-- Analysis of participation patterns among marginalised groups
-- Review of community feedback on moderation practices
-- Adjustment of training and practices based on outcomes
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/mentorship-training-coordination.md b/src/content/docs/staff/training/mentorship-training-coordination.md
index 29148c8..8422143 100644
--- a/src/content/docs/staff/training/mentorship-training-coordination.md
+++ b/src/content/docs/staff/training/mentorship-training-coordination.md
@@ -2,13 +2,13 @@
 title: Mentorship and Training Coordination for Staff
 ---
 
-**SPECIALIZED TRAINING FOR TRAINING & DEVELOPMENT COORDINATORS**
+**SPECIALISED TRAINING FOR TRAINING & DEVELOPMENT COORDINATORS**
 
 ## 1. INTRODUCTION AND SCOPE
 
 ### 1.1. Purpose and Educational Mission
 
-This training provides comprehensive guidance for staff members serving as Training and Development Coordinators within our community ecosystem. These roles are crucial for building capacity, developing skills, and fostering growth among community members and staff, particularly with focus on supporting underrepresented groups in technology and community leadership.
+This training provides comprehensive guidance for Team members serving as Training and Development Coordinators within our community ecosystem. These roles are crucial for building capacity, developing skills, and fostering growth amongst community members and Team members, particularly with focus on supporting underrepresented groups in technology and community leadership.
 
 ### 1.2. Training and Development Coordinator Responsibilities
 
@@ -167,7 +167,7 @@ This training provides comprehensive guidance for staff members serving as Train
 - **Interactive Workshops**: Live and recorded interactive workshop sessions
 - **Peer Learning Sessions**: Facilitated peer learning and discussion groups
 
-### 3.2. Specialized Training Programmes
+### 3.2. Specialised Training Programmes
 
 #### 3.2.1. Technical Skill Development
 
@@ -487,67 +487,59 @@ This training provides comprehensive guidance for staff members serving as Train
 - **Knowledge Sharing**: Sharing successful models with other organisations and communities
 - **Adaptation Guidance**: Guidance for adapting successful models to different contexts
 
-## 8. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 8. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 8.1. Training and Development Coordinator Competencies
+### 8.1. Scenario 1: Mentorship Relationship Challenge
 
-#### 8.1.1. Essential Skills and Knowledge
+**Situation**: A mentorship relationship is struggling. The mentor feels the mentee isn't putting in effort, and the mentee feels the mentor is too demanding and doesn't understand their learning style. Both are frustrated and considering ending the relationship.
 
-**Educational Expertise:**
-- **Adult Learning Principles**: Understanding of how adults learn and effective teaching methods
-- **Curriculum Development**: Skills in designing and developing effective educational curricula
-- **Assessment and Evaluation**: Expertise in assessing learning outcomes and programme effectiveness
-- **Inclusive Education**: Knowledge of inclusive education practices and accessibility
+**Your Response:**
+1. How do you assess the mentorship relationship?
+2. How do you support both mentor and mentee?
+3. How do you facilitate communication and understanding?
+4. How do you address different learning styles?
+5. How do you determine if the relationship should continue?
+6. How do you support either party if the relationship ends?
 
-**Programme Management:**
-- **Project Management**: Skills in managing complex educational programmes and initiatives
-- **Resource Management**: Effective management of staff, budget, and material resources
-- **Quality Assurance**: Skills in maintaining and improving programme quality
-- **Strategic Planning**: Ability to develop long-term educational strategy aligned with community needs
+**Correct Answer**: Assess relationship through individual conversations, support both parties, facilitate communication about expectations and learning styles, address learning style differences, help both understand each other's perspectives, determine if relationship can be salvaged or should end, support transition if relationship ends.
 
-#### 8.1.2. Specialized Competencies
+### 8.2. Scenario 2: Training Programme Development
 
-**Mentorship and Coaching:**
-- **Mentorship Programme Design**: Expertise in designing effective mentorship programmes
-- **Mentor Training**: Skills in training and supporting effective mentors
-- **Relationship Facilitation**: Ability to facilitate effective mentorship and learning relationships
-- **Conflict Resolution**: Skills in resolving conflicts and challenges in educational settings
+**Situation**: Community members request training on a technical topic, but you need to ensure the training is accessible, inclusive, and serves diverse learners. Some community members have different learning styles, language needs, and accessibility requirements.
 
-**Community Development:**
-- **Community Engagement**: Skills in engaging diverse community members in educational programmes
-- **Cultural Competency**: Understanding of how cultural factors affect learning and development
-- **Social Justice**: Understanding of how education can address systemic barriers and create equity
-- **Leadership Development**: Expertise in developing leadership capacity within communities
+**Your Response:**
+1. How do you design inclusive training?
+2. How do you accommodate different learning styles?
+3. How do you ensure accessibility?
+4. How do you address language needs?
+5. How do you involve community members in design?
+6. How do you evaluate training effectiveness?
 
-### 8.2. Professional Development and Certification
+**Correct Answer**: Design training with universal design principles, accommodate multiple learning styles, ensure full accessibility, provide language support, involve diverse community members in design, evaluate effectiveness through feedback and outcomes, continuously improve based on feedback.
 
-#### 8.2.1. Training Requirements
+### 8.3. Scenario 3: Educational Conflict Resolution
 
-**Foundation Training:**
-- **Adult Education Principles**: Comprehensive training in adult education theory and practice
-- **Inclusive Education**: Training in creating inclusive, accessible learning environments
-- **Programme Development**: Training in educational programme design and implementation
-- **Community Engagement**: Training in effective community engagement and outreach
+**Situation**: During a training session, a conflict arises between participants. One participant makes comments that others find exclusionary, and the conflict is disrupting the learning environment. Participants are taking sides and the training can't continue effectively.
 
-**Advanced Training:**
-- **Educational Research**: Training in educational research methods and evaluation
-- **Leadership Development**: Advanced training in developing leadership capacity
-- **Innovation and Change**: Training in educational innovation and organisational change
-- **Strategic Planning**: Training in strategic planning and long-term programme development
+**Your Response:**
+1. How do you address the conflict while maintaining learning environment?
+2. How do you handle exclusionary comments?
+3. How do you support all participants?
+4. How do you facilitate learning despite conflict?
+5. How do you prevent future conflicts?
+6. How do you ensure inclusive learning environment?
 
-#### 8.2.2. Ongoing Professional Development
+**Correct Answer**: Address conflict immediately, handle exclusionary comments with education about impact, support all participants, facilitate learning by addressing conflict constructively, prevent future conflicts through clear expectations and inclusive practices, ensure safe and inclusive learning environment for all.
 
-**Continuous Learning Requirements:**
-- **Industry Updates**: Stay current with developments in adult education and community development
-- **Research Engagement**: Regular engagement with educational research and best practices
-- **Professional Networks**: Active participation in professional education and development networks
-- **Conference Participation**: Regular participation in relevant conferences and training events
+## 9. TRAINING REQUIREMENTS
 
-**Performance Standards:**
-- **Programme Effectiveness**: Demonstrated effectiveness in educational programme outcomes
-- **Community Impact**: Measurable positive impact on community capacity and development
-- **Innovation**: Regular innovation and improvement in educational practices
-- **Professional Growth**: Ongoing professional growth and development in educational leadership
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/social-media-management.md b/src/content/docs/staff/training/social-media-management.md
index 2e69624..8284c8c 100644
--- a/src/content/docs/staff/training/social-media-management.md
+++ b/src/content/docs/staff/training/social-media-management.md
@@ -8,7 +8,7 @@ title: Social Media Management Training for Staff
 
 ### 1.1. Purpose and Importance
 
-This training provides comprehensive guidance for staff members responsible for managing our community's presence across multiple social media platforms. Social media management is critical for brand representation, community outreach, crisis communication, and maintaining our reputation as an inclusive, professional organisation.
+This training provides comprehensive guidance for Team members responsible for managing our community's presence across multiple social media platforms. Social media management is critical for brand representation, community outreach, crisis communication, and maintaining our reputation as an inclusive, professional organisation.
 
 ### 1.2. Multi-Platform Social Media Ecosystem
 
@@ -30,7 +30,7 @@ Our social media presence spans multiple platforms, each with unique characteris
 
 **(h)** **Other Platforms**: Emerging platforms and specialised communities.
 
-### 1.3. Integration with Organizational Values
+### 1.3. Integration with Organisational Values
 
 Our social media presence must consistently reflect our core values:
 
@@ -51,7 +51,7 @@ Our social media presence must consistently reflect our core values:
 #### 2.1.1. Community Server Operations
 
 **Server Management:**
-- **Channel Organization**: Maintain clear, accessible channel structures
+- **Channel Organisation**: Maintain clear, accessible channel structures
 - **Role Management**: Appropriate role assignments and permission structures
 - **Bot Integration**: Effective use of moderation and utility bots
 - **Event Coordination**: Community events, gaming sessions, educational workshops
@@ -111,14 +111,14 @@ Our social media presence must consistently reflect our core values:
 - **Educational Content**: Share knowledge and expertise with professional community
 
 **Professional Tone:**
-- **Authoritative Voice**: Demonstrate expertise while remaining approachable
+- **Authoritative Voice**: Demonstrate expertise whilst remaining approachable
 - **Industry Language**: Use appropriate professional terminology
 - **Networking Focus**: Build relationships with industry professionals
 - **Value-Driven Content**: Consistently promote organisational values
 
 #### 2.3.2. LinkedIn-Specific Strategies
 
-**Platform Optimization:**
+**Platform Optimisation:**
 - **Profile Management**: Maintain professional, complete organisational profile
 - **Connection Strategy**: Strategic networking with industry professionals
 - **Content Publishing**: Regular articles and posts about industry topics
@@ -194,7 +194,7 @@ Our social media presence must consistently reflect our core values:
 #### 3.2.1. Content Calendar Management
 
 **Strategic Planning:**
-- **Monthly Themes**: Organize content around monthly themes and initiatives
+- **Monthly Themes**: Organise content around monthly themes and initiatives
 - **Event Coordination**: Plan content around community events and milestones
 - **Seasonal Considerations**: Adapt content for seasons, holidays, and industry events
 - **Crisis Preparedness**: Maintain flexibility for crisis communication needs
@@ -202,7 +202,7 @@ Our social media presence must consistently reflect our core values:
 **Content Types:**
 - **Educational Content**: Tutorials, guides, best practices, industry insights
 - **Community Spotlights**: Member achievements, contributions, success stories
-- **Organizational Updates**: News, policy changes, new initiatives
+- **Organisational Updates**: News, policy changes, new initiatives
 - **Interactive Content**: Polls, Q&As, live sessions, community challenges
 
 #### 3.2.2. Cross-Platform Content Coordination
@@ -322,7 +322,7 @@ Our social media presence must consistently reflect our core values:
 #### 5.2.1. Authentic Engagement
 
 **Transparency Requirements:**
-- **Organizational Identity**: Clear identification as organisational representative
+- **Organisational Identity**: Clear identification as organisational representative
 - **Sponsored Content**: Proper disclosure of sponsored or paid content
 - **Conflict of Interest**: Disclosure of relevant conflicts of interest
 - **Personal vs. Professional**: Clear boundaries between personal and professional accounts
@@ -400,7 +400,7 @@ Our social media presence must consistently reflect our core values:
 **Content Strategy Evolution:**
 - **Trend Adaptation**: Adjust strategy based on platform and industry trends
 - **Audience Feedback**: Incorporate audience preferences and feedback
-- **Performance Optimization**: Focus resources on highest-performing content and platforms
+- **Performance Optimisation**: Focus resources on highest-performing content and platforms
 - **Innovation Integration**: Experiment with new formats and features
 
 ## 7. TEAM COORDINATION AND COLLABORATION
@@ -442,7 +442,7 @@ Our social media presence must consistently reflect our core values:
 **Skill Development:**
 - **Content Creation**: Development of graphic design, video editing, and content creation skills
 - **Analytics Proficiency**: Advanced training in social media analytics and data analysis
-- **Crisis Management**: Specialized training in crisis communication and management
+- **Crisis Management**: Specialised training in crisis communication and management
 - **Cultural Competency**: Ongoing education about inclusive communication and cultural sensitivity
 
 ## 8. PLATFORM-SPECIFIC ADVANCED STRATEGIES
@@ -469,7 +469,7 @@ Our social media presence must consistently reflect our core values:
 - **Community Guidelines**: Develop comprehensive community guidelines and rules
 - **Moderation Team**: Build and train volunteer moderation teams
 - **Content Curation**: Curate high-quality content and educational resources
-- **Community Events**: Organize AMAs, contests, and community challenges
+- **Community Events**: Organise AMAs, contests, and community challenges
 
 ### 8.2. Professional Platform Excellence
 
@@ -489,47 +489,59 @@ Our social media presence must consistently reflect our core values:
 - **Code Review Excellence**: Maintain high standards in public code reviews
 - **Developer Education**: Educational content for developers and contributors
 
-## 9. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 9. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 9.1. Core Competency Assessment
+### 9.1. Scenario 1: Social Media Crisis Response
 
-#### 9.1.1. Platform Proficiency
+**Situation**: A negative situation involving the community goes viral on social media. Misinformation is spreading, community members are being harassed, and the situation is escalating rapidly across multiple platforms. The community's reputation is at risk.
 
-**Technical Skills:**
-- **Multi-Platform Management**: Proficiency across all relevant social media platforms
-- **Content Creation**: Basic graphic design, video editing, and content creation skills
-- **Analytics Understanding**: Ability to interpret and act on social media analytics
-- **Crisis Communication**: Demonstrated ability to handle crisis communication
+**Your Response:**
+1. How do you respond immediately to the crisis?
+2. How do you address misinformation?
+3. How do you protect community members from harassment?
+4. How do you communicate transparently?
+5. How do you coordinate response across platforms?
+6. How do you manage community reputation?
 
-**Communication Skills:**
-- **Brand Voice Consistency**: Maintain consistent brand voice across platforms
-- **Community Engagement**: Effective engagement with diverse community members
-- **Professional Writing**: High-quality written communication for different audiences
-- **Cultural Sensitivity**: Inclusive communication that respects diverse perspectives
+**Correct Answer**: Respond immediately with clear communication, address misinformation with facts, protect community members from harassment, communicate transparently about situation and response, coordinate response across all social media platforms, manage reputation through consistent messaging and actions, follow up appropriately.
 
-#### 9.1.2. Strategic Thinking
+### 9.2. Scenario 2: Inappropriate Content Response
 
-**Planning and Execution:**
-- **Content Strategy Development**: Create comprehensive content strategies
-- **Campaign Planning**: Plan and execute successful social media campaigns
-- **Crisis Management**: Develop and implement crisis communication plans
-- **Performance Analysis**: Analyze performance and adapt strategies accordingly
+**Situation**: Community members report that inappropriate or harmful content was posted on the community's social media account. The content violates community values and has offended marginalised community members. The content has been shared and is getting attention.
 
-### 9.2. Ongoing Development Requirements
+**Your Response:**
+1. How do you respond immediately?
+2. How do you address the harm caused?
+3. How do you communicate with affected community members?
+4. How do you prevent similar incidents?
+5. How do you restore community trust?
+6. How do you ensure accountability?
 
-#### 9.2.1. Continuous Learning
+**Correct Answer**: Remove content immediately, acknowledge harm caused, communicate with affected community members, apologise appropriately, implement processes to prevent similar incidents, restore trust through actions and transparency, ensure accountability for mistake, learn and improve.
 
-**Monthly Requirements:**
-- **Platform Updates**: Stay current with platform changes and new features
-- **Industry Trends**: Monitor and analyze social media and community management trends
-- **Community Feedback**: Regular collection and analysis of community feedback
-- **Performance Review**: Monthly analysis of social media performance and metrics
+### 9.3. Scenario 3: Content Strategy Development
 
-**Quarterly Development:**
-- **Advanced Training**: Participate in advanced social media management training
-- **Strategy Review**: Comprehensive review and adjustment of social media strategy
-- **Tool Evaluation**: Evaluate and potentially adopt new social media management tools
-- **Professional Networking**: Engage with other social media professionals and industry leaders
+**Situation**: Community leadership want to develop a social media content strategy that attracts diverse new members whilst authentically representing community values. The strategy needs to balance growth, authenticity, and inclusion.
+
+**Your Response:**
+1. How do you develop an authentic content strategy?
+2. How do you ensure content represents community values?
+3. How do you attract diverse audiences?
+4. How do you balance growth with authenticity?
+5. How do you involve community members in content creation?
+6. How do you measure strategy effectiveness?
+
+**Correct Answer**: Develop strategy that authentically represents community values, ensure content advances social justice mission, attract diverse audiences through inclusive content, balance growth with authenticity, involve diverse community members in content creation, measure effectiveness through engagement and alignment metrics.
+
+## 10. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
 
 ---
 
diff --git a/src/content/docs/staff/training/technical-contributor.md b/src/content/docs/staff/training/technical-contributor.md
index 023039d..4d1c762 100644
--- a/src/content/docs/staff/training/technical-contributor.md
+++ b/src/content/docs/staff/training/technical-contributor.md
@@ -8,7 +8,7 @@ title: Technical Contributor Training for Staff
 
 ### 1.1. Purpose and Technical Context
 
-This training provides comprehensive guidance for staff members serving as Technical Contributors within our community ecosystem. Technical Contributors play a crucial role in maintaining, developing, and improving the technological infrastructure that supports our community platforms and services.
+This training provides comprehensive guidance for Team members serving as Technical Contributors within our community ecosystem. Technical Contributors play a crucial role in maintaining, developing, and improving the technological infrastructure that supports our community platforms and services.
 
 ### 1.2. Technical Contributor Responsibilities
 
@@ -358,41 +358,53 @@ This training provides comprehensive guidance for staff members serving as Techn
 - **Contingency Planning**: Comprehensive contingency planning for various risk scenarios
 - **Regular Review**: Regular review and updating of risk assessments and mitigation plans
 
-## 7. CERTIFICATION AND COMPETENCY REQUIREMENTS
+## 7. PRACTICE SCENARIOS AND TRAINING EXERCISES
 
-### 7.1. Technical Competency Assessment
+### 7.1. Scenario 1: Accessibility Implementation
 
-#### 7.1.1. Core Technical Skills
+**Situation**: You're developing a new feature for the community platform. The feature is functionally complete but isn't accessible to users with disabilities. Community members are requesting accessibility improvements, and you need to retrofit accessibility into existing code.
 
-**Programming and Development:**
-- **Language Proficiency**: Demonstrated proficiency in relevant programming languages and frameworks
-- **Software Architecture**: Understanding of software architecture principles and design patterns
-- **Database Management**: Skills in database design, optimisation, and management
-- **API Development**: Experience in designing, developing, and maintaining APIs
+**Your Response:**
+1. How do you prioritize accessibility improvements?
+2. How do you implement accessibility retroactively?
+3. How do you test with assistive technologies?
+4. How do you involve disabled community members in testing?
+5. How do you ensure comprehensive accessibility?
+6. How do you prevent future accessibility issues?
 
-**Infrastructure and DevOps:**
-- **Version Control**: Advanced proficiency with Git and collaborative development workflows
-- **CI/CD Systems**: Experience with continuous integration and continuous deployment systems
-- **Cloud Platforms**: Proficiency with relevant cloud platforms and services
-- **Monitoring and Logging**: Skills in system monitoring, logging, and performance analysis
+**Correct Answer**: Prioritize accessibility as high priority, implement accessibility improvements systematically, test with assistive technologies, involve disabled community members in testing, ensure comprehensive accessibility, implement accessibility testing in development process, prevent future issues through accessibility-first development.
 
-#### 7.1.2. Community-Specific Competencies
+### 7.2. Scenario 2: Security Vulnerability Discovery
 
-**Accessibility Development:**
-- **WCAG Standards**: Thorough understanding of web accessibility standards and implementation
-- **Assistive Technology**: Experience testing with assistive technologies and accessibility tools
-- **Inclusive Design**: Skills in developing inclusive, accessible user interfaces and experiences
-- **Accessibility Auditing**: Ability to conduct accessibility audits and implement improvements
+**Situation**: You discover a security vulnerability in the platform that could expose user data. The vulnerability affects a feature used by many community members. You need to fix it quickly while minimising disruption.
 
-**Privacy and Security:**
-- **Privacy by Design**: Understanding of privacy principles and their technical implementation
-- **Security Best Practices**: Knowledge of security best practices and vulnerability prevention
-- **Data Protection**: Skills in implementing data protection and privacy compliance measures
-- **Incident Response**: Ability to respond effectively to security incidents and breaches
+**Your Response:**
+1. How do you respond immediately to the vulnerability?
+2. How do you assess the severity and impact?
+3. How do you coordinate the fix?
+4. How do you communicate with community members?
+5. How do you prevent data exposure?
+6. How do you prevent future vulnerabilities?
 
-### 7.2. Training and Professional Development
+**Correct Answer**: Respond immediately, assess severity and impact, coordinate fix quickly, communicate transparently with community members about issue and fix, prevent data exposure through immediate mitigation, implement security improvements, prevent future vulnerabilities through security practices.
 
-#### 7.2.1. Ongoing Education Requirements
+### 7.3. Scenario 3: Performance Optimization Request
+
+**Situation**: Community members report that the platform is slow and unresponsive, particularly affecting members with slower internet connections or older devices. Performance issues are creating barriers to participation.
+
+**Your Response:**
+1. How do you identify performance bottlenecks?
+2. How do you prioritize performance improvements?
+3. How do you optimize for diverse connection speeds?
+4. How do you ensure performance doesn't compromise accessibility?
+5. How do you test performance improvements?
+6. How do you monitor ongoing performance?
+
+**Correct Answer**: Identify bottlenecks through performance analysis, prioritize improvements that affect most users, optimize for diverse connection speeds and devices, ensure performance improvements don't compromise accessibility, test improvements comprehensively, monitor performance ongoing, ensure equitable access.
+
+### 8.1. Training and Professional Development
+
+#### 8.1.1. Ongoing Education Requirements
 
 **Technical Skills Development:**
 - **Technology Updates**: Stay current with developments in relevant technologies and frameworks
@@ -406,7 +418,7 @@ This training provides comprehensive guidance for staff members serving as Techn
 - **Privacy Protection**: Ongoing education about privacy laws, regulations, and technical implementation
 - **Community Needs**: Understanding of how technology can better serve community needs and values
 
-#### 7.2.2. Leadership Development
+#### 8.1.2. Leadership Development
 
 **Technical Leadership:**
 - **Project Management**: Skills in technical project management and team leadership
@@ -420,6 +432,16 @@ This training provides comprehensive guidance for staff members serving as Techn
 - **Strategic Planning**: Skills in long-term technical planning and roadmap development
 - **Change Management**: Ability to manage technical changes and transitions effectively
 
+## 8. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
 ---
 
 *This Technical Contributor Training document is part of our comprehensive staff development programme designed to ensure technical excellence in service of community values and social justice. For questions about technical contribution standards or to report training completion, please contact the Technical Manager or designated technical leadership through staff channels.*
diff --git a/src/content/docs/staff/training/trauma-informed-moderation.md b/src/content/docs/staff/training/trauma-informed-moderation.md
new file mode 100644
index 0000000..59f9eff
--- /dev/null
+++ b/src/content/docs/staff/training/trauma-informed-moderation.md
@@ -0,0 +1,575 @@
+---
+title: Trauma-Informed Moderation Training for Staff
+---
+
+**ESSENTIAL TRAINING FOR ALL MODERATION STAFF**
+
+## 1. INTRODUCTION AND SCOPE
+
+### 1.1. Purpose of This Training
+
+This training document provides essential guidance for Team members on conducting moderation through a trauma-informed lens. Trauma is common, and many community members have experienced trauma that affects how they interact online. Trauma-informed moderation recognises the impact of trauma, avoids re-traumatization, and creates safer, more supportive community environments.
+
+### 1.2. Integration with Existing Policies
+
+This training operates within our comprehensive safety and support framework:
+
+**(a)** **Crisis Response Policy**: Procedures for responding to mental health crises;
+
+**(b)** **Community Support Policy**: Guidelines for supporting community members;
+
+**(c)** **Inclusive Moderation Policy**: Principles for moderation that considers impact;
+
+**(d)** **Harassment Response Policy**: Procedures for responding to harassment;
+
+**(e)** **Child Safety Policy**: Special considerations for minors who may have experienced trauma;
+
+**(f)** **Staff Handbook**: General staff responsibilities and expectations.
+
+### 1.3. Critical Understanding
+
+**Trauma Is Common:**
+- Many people have experienced trauma
+- Trauma affects how people interact and respond
+- Online interactions can trigger trauma responses
+- Moderation actions can re-traumatize if not done carefully
+- Trauma-informed approaches benefit all community members
+
+**Our Approach:**
+- We recognise that trauma is common and affects behaviour
+- We avoid re-traumatization in our moderation practices
+- We create safe, supportive environments for trauma survivors
+- We support community members who have experienced trauma
+- We prioritise safety and healing in our moderation
+
+## 2. UNDERSTANDING TRAUMA
+
+### 2.1. What Is Trauma?
+
+#### 2.1.1. Definition and Types
+
+**Trauma** is an emotional response to a deeply distressing or disturbing event that overwhelms an individual's ability to cope. Trauma can result from:
+- **Single Events**: One-time traumatic experiences
+- **Ongoing Trauma**: Repeated or prolonged traumatic experiences
+- **Complex Trauma**: Multiple traumatic experiences over time
+- **Historical Trauma**: Trauma passed through generations
+- **Vicarious Trauma**: Trauma from witnessing or hearing about others' trauma
+
+**Types of Trauma:**
+- **Physical Trauma**: Physical abuse, assault, accidents
+- **Emotional Trauma**: Emotional abuse, neglect, loss
+- **Sexual Trauma**: Sexual abuse, assault, exploitation
+- **Psychological Trauma**: Psychological abuse, manipulation, gaslighting
+- **Systemic Trauma**: Discrimination, oppression, marginalization
+
+#### 2.1.2. Impact of Trauma
+
+**How Trauma Affects People:**
+- **Emotional Impact**: Anxiety, depression, fear, anger, numbness
+- **Physical Impact**: Sleep disturbances, physical symptoms, hypervigilance
+- **Cognitive Impact**: Difficulty concentrating, memory issues, dissociation
+- **Behavioural Impact**: Avoidance, hypervigilance, difficulty trusting
+- **Relational Impact**: Difficulty forming relationships, social withdrawal
+
+**Online Impact:**
+- Trauma can affect how people communicate online
+- Online interactions can trigger trauma responses
+- Moderation actions can feel threatening to trauma survivors
+- Community conflicts can be re-traumatizing
+- Supportive environments can aid healing
+
+### 2.2. Trauma Responses
+
+#### 2.2.1. Common Trauma Responses
+
+**Fight Response:**
+- Aggressive or defensive behaviour
+- Anger and confrontation
+- Standing up for self or others
+- Can appear as "difficult" behaviour
+
+**Flight Response:**
+- Avoidance and withdrawal
+- Leaving situations or spaces
+- Disengaging from community
+- Can appear as "unresponsive" behaviour
+
+**Freeze Response:**
+- Shutting down or dissociation
+- Inability to respond or act
+- Feeling stuck or paralysed
+- Can appear as "non-responsive" behaviour
+
+**Fawn Response:**
+- People-pleasing and compliance
+- Avoiding conflict at all costs
+- Difficulty setting boundaries
+- Can appear as "passive" behaviour
+
+#### 2.2.2. Recognising Trauma Responses
+
+**Behavioural Indicators:**
+- Strong emotional reactions to seemingly minor triggers
+- Avoidance of certain topics or situations
+- Hypervigilance or constant alertness
+- Difficulty trusting others
+- Difficulty setting boundaries
+- People-pleasing or excessive compliance
+- Aggressive or defensive responses
+- Withdrawal or disengagement
+
+**Communication Patterns:**
+- Difficulty expressing needs or boundaries
+- Over-apologising or self-blame
+- Defensive responses to feedback
+- Difficulty accepting help or support
+- Strong reactions to authority or power
+- Difficulty with conflict or disagreement
+
+## 3. TRAUMA-INFORMED PRINCIPLES
+
+### 3.1. Core Principles
+
+#### 3.1.1. Safety
+
+**Physical and Psychological Safety:**
+- Create physically and psychologically safe environments
+- Ensure community members feel safe to participate
+- Address threats to safety immediately
+- Provide clear safety information
+- Support community members in feeling safe
+
+**Safety in Moderation:**
+- Moderation actions should not feel threatening
+- Provide clear information about moderation actions
+- Avoid punitive or shaming language
+- Ensure moderation processes feel safe
+- Support community members through moderation processes
+
+#### 3.1.2. Trustworthiness and Transparency
+
+**Building Trust:**
+- Be consistent and reliable in moderation
+- Communicate clearly and honestly
+- Follow through on commitments
+- Be transparent about processes and decisions
+- Build trust through consistent actions
+
+**Transparency in Moderation:**
+- Explain moderation actions clearly
+- Provide context for decisions
+- Be honest about limitations and processes
+- Communicate expectations clearly
+- Build trust through transparency
+
+#### 3.1.3. Peer Support and Collaboration
+
+**Supportive Relationships:**
+- Facilitate supportive peer relationships
+- Create opportunities for connection
+- Support community members supporting each other
+- Recognise and value peer support
+- Create supportive community culture
+
+**Collaborative Moderation:**
+- Involve community members in moderation when appropriate
+- Seek input and feedback from community
+- Collaborate with community members on solutions
+- Value community member perspectives
+- Build collaborative moderation processes
+
+#### 3.1.4. Empowerment and Choice
+
+**Empowering Community Members:**
+- Provide choices and control when possible
+- Support community member agency
+- Respect community member decisions
+- Provide information for informed decisions
+- Empower community members to advocate for themselves
+
+**Choice in Moderation:**
+- Provide options when possible
+- Respect community member choices
+- Support community member agency in moderation processes
+- Provide information for informed participation
+- Empower community members in moderation
+
+#### 3.1.5. Cultural, Historical, and Gender Considerations
+
+**Cultural Sensitivity:**
+- Recognise cultural differences in trauma experiences
+- Understand historical trauma and its impact
+- Recognise gender differences in trauma experiences
+- Consider intersectional trauma experiences
+- Respect cultural approaches to healing
+
+**Application in Moderation:**
+- Consider cultural context in moderation
+- Recognise historical and systemic trauma
+- Understand gender-specific trauma considerations
+- Consider intersectional experiences
+- Apply culturally sensitive moderation approaches
+
+## 4. TRAUMA-INFORMED MODERATION PRACTICES
+
+### 4.1. Communication Practices
+
+#### 4.1.1. Trauma-Informed Language
+
+**Supportive Language:**
+- Use clear, direct, and non-threatening language
+- Avoid punitive or shaming language
+- Use "I" statements rather than accusatory language
+- Acknowledge feelings and experiences
+- Provide information without judgement
+
+**Language to Avoid:**
+- Punitive or shaming language
+- Dismissive or minimising language
+- Blaming or accusatory language
+- Threatening or intimidating language
+- Language that invalidates experiences
+
+**Example Moderation Messages:**
+
+**Trauma-Informed:**
+"I noticed that your recent messages may have violated our community guidelines. I'd like to discuss this with you and find a way forward that works for everyone. Would you be open to a conversation about this?"
+
+**Not Trauma-Informed:**
+"Your behaviour is unacceptable and violates our rules. You need to stop immediately or face consequences."
+
+#### 4.1.2. Clear and Predictable Communication
+
+**Predictability:**
+- Provide clear information about moderation processes
+- Explain what will happen and when
+- Set clear expectations
+- Follow through on commitments
+- Provide updates and information
+
+**Clarity:**
+- Use clear, simple language
+- Avoid jargon or technical language
+- Provide context and explanation
+- Answer questions clearly
+- Ensure understanding
+
+### 4.2. Moderation Process Practices
+
+#### 4.2.1. Non-Punitive Approaches
+
+**Restorative Approaches:**
+- Focus on repair and healing rather than punishment
+- Address harm whilst supporting growth
+- Provide opportunities for learning and change
+- Support accountability without shame
+- Create pathways for reintegration
+
+**Avoiding Re-Traumatization:**
+- Avoid public shaming or humiliation
+- Don't require public apologies
+- Avoid punitive language or threats
+- Don't isolate or exclude unnecessarily
+- Support rather than punish
+
+#### 4.2.2. Supportive Moderation Actions
+
+**Supportive Responses:**
+- Provide resources and support
+- Connect with appropriate help
+- Offer choices and options
+- Support community member agency
+- Facilitate healing and growth
+
+**Protective Measures:**
+- Take protective measures when needed
+- Support community member safety
+- Address threats and harm
+- Provide safe spaces
+- Support recovery and healing
+
+### 4.3. Recognising and Responding to Trauma Triggers
+
+#### 4.3.1. Common Triggers
+
+**Content Triggers:**
+- Discussions of abuse, violence, or trauma
+- Graphic or disturbing content
+- Content that reminds of past trauma
+- Discussions of triggering topics
+- Content that invalidates experiences
+
+**Interaction Triggers:**
+- Conflict or confrontation
+- Authority figures or power dynamics
+- Being called out or criticised
+- Feeling attacked or threatened
+- Loss of control or agency
+
+**Environmental Triggers:**
+- Unsafe or hostile environments
+- Lack of support or resources
+- Isolation or exclusion
+- Power imbalances
+- Unpredictable or chaotic environments
+
+#### 4.3.2. Responding to Triggered Responses
+
+**Recognising Triggered Responses:**
+- Strong emotional reactions
+- Withdrawal or avoidance
+- Defensive or aggressive responses
+- Dissociation or shutting down
+- Difficulty communicating or responding
+
+**Supportive Responses:**
+- Acknowledge and validate the response
+- Provide safety and support
+- Avoid further triggering
+- Offer resources and help
+- Support recovery and regulation
+
+**Moderation Considerations:**
+- Don't punish trauma responses
+- Provide support and understanding
+- Address underlying issues when possible
+- Support community member safety
+- Facilitate healing and recovery
+
+## 5. SUPPORTING TRAUMA SURVIVORS
+
+### 5.1. Creating Safe Environments
+
+#### 5.1.1. Safety Measures
+
+**Physical Safety:**
+- Address threats to physical safety immediately
+- Remove harmful content or individuals
+- Provide safe spaces and channels
+- Support community member safety
+- Monitor for safety threats
+
+**Psychological Safety:**
+- Create psychologically safe environments
+- Address harassment and abuse
+- Support community member well-being
+- Provide resources and support
+- Facilitate healing and recovery
+
+#### 5.1.2. Supportive Resources
+
+**Mental Health Resources:**
+- Crisis support hotlines and services
+- Counselling and therapy resources
+- Support groups and communities
+- Online mental health resources
+- Trauma-specific support resources
+
+**Community Support:**
+- Peer support and connection
+- Supportive community spaces
+- Mentorship and guidance
+- Community resources and information
+- Supportive relationships
+
+### 5.2. Supporting Recovery and Healing
+
+#### 5.2.1. Healing-Centred Approaches
+
+**Supporting Healing:**
+- Recognise and validate experiences
+- Support community member agency
+- Provide resources and support
+- Facilitate connection and community
+- Support growth and recovery
+
+**Avoiding Re-Traumatization:**
+- Avoid triggering content or interactions
+- Don't require retelling of trauma
+- Support community member boundaries
+- Respect community member choices
+- Provide safe, supportive environments
+
+#### 5.2.2. Long-Term Support
+
+**Ongoing Support:**
+- Check in with community members regularly
+- Provide ongoing resources and support
+- Support community member participation
+- Facilitate connection and community
+- Support continued healing and growth
+
+**Community Integration:**
+- Support reintegration into community
+- Facilitate positive community connections
+- Support community member contributions
+- Recognise and value community members
+- Create inclusive, supportive environments
+
+## 6. SELF-CARE FOR STAFF
+
+**Comprehensive Self-Care Resources**: For detailed self-care strategies, emotional support resources, and wellness practices, see [Self-Care Resources for Staff](/staff/self-care-resources). This section provides trauma-informed-moderation-specific considerations; refer to the self-care resources document for comprehensive guidance.
+
+### 6.1. Trauma-Informed Moderation-Specific Self-Care Considerations
+
+#### 6.1.1. Understanding Secondary Trauma
+
+**Additional Considerations for Trauma-Informed Work:**
+- Frequent exposure to trauma content
+- Supporting many trauma survivors
+- Personal trauma history may increase risk
+- Need for regular supervision and support
+- Importance of maintaining professional boundaries
+
+**Self-Care Practices:**
+- Regular debriefing after supporting trauma survivors
+- Access to professional counselling or support
+- Clear boundaries between work and personal life
+- Regular supervision and support
+- Practice self-compassion and recognise emotional impact
+
+### 6.2. Support Systems
+
+#### 6.2.1. Team Support
+
+**Team Support:**
+- Regular team check-ins and debriefing
+- Peer support and mutual aid
+- Sharing experiences and learning together
+- Supporting each other through difficult situations
+- Celebrating successes together
+
+#### 6.2.2. Organisational Support
+
+**Organisational Support:**
+- Access to counselling and mental health resources
+- Reasonable workload and expectations
+- Time off and breaks
+- Professional development opportunities
+- Recognition and appreciation
+
+## 7. PRACTICAL APPLICATION
+
+### 7.1. Trauma-Informed Moderation Scenarios
+
+#### 7.1.1. Scenario 1: Strong Emotional Response
+
+**Situation**: A community member has a strong emotional reaction to a moderation action, becoming very upset and defensive.
+
+**Trauma-Informed Response:**
+- Acknowledge and validate their feelings
+- Provide clear, non-threatening explanation
+- Offer to discuss and find solution together
+- Provide support and resources
+- Avoid further escalation or confrontation
+
+**Not Trauma-Informed Response:**
+- Dismissing or minimising their reaction
+- Escalating consequences for emotional response
+- Using punitive or threatening language
+- Requiring immediate compliance
+- Ignoring their concerns or feelings
+
+#### 7.1.2. Scenario 2: Avoidance and Withdrawal
+
+**Situation**: A community member withdraws from community after a conflict, avoiding participation and communication.
+
+**Trauma-Informed Response:**
+- Respect their need for space
+- Reach out with supportive, non-pressuring communication
+- Offer support and resources
+- Provide options and choices
+- Support their agency and decisions
+
+**Not Trauma-Informed Response:**
+- Pressuring them to participate
+- Requiring immediate response
+- Punishing withdrawal
+- Ignoring their need for space
+- Dismissing their concerns
+
+### 7.2. Integrating Trauma-Informed Practices
+
+#### 7.2.1. Daily Practices
+
+**Regular Practices:**
+- Use trauma-informed language in all communications
+- Consider trauma impact in all moderation decisions
+- Provide clear, predictable information
+- Support community member agency and choice
+- Create safe, supportive environments
+
+**Ongoing Practices:**
+- Regular training and education
+- Self-reflection and self-awareness
+- Seeking feedback and learning
+- Supporting colleagues in trauma-informed work
+- Continuous improvement and growth
+
+#### 7.2.2. System-Wide Integration
+
+**Organisational Practices:**
+- Trauma-informed policies and procedures
+- Staff training and support
+- Community education and resources
+- Supportive community culture
+- Continuous improvement and evaluation
+
+## 8. PRACTICE SCENARIOS AND TRAINING EXERCISES
+
+### 8.1. Scenario 1: Strong Emotional Response to Moderation
+
+**Situation**: A community member has a very strong emotional reaction to a moderation action you took. They become extremely upset and defensive, posting multiple messages saying they feel "attacked" and "unsafe." Their reaction seems disproportionate to the moderation action.
+
+**Your Response:**
+1. How do you interpret this strong emotional reaction?
+2. What trauma-informed principles should guide your response?
+3. What language should you use in your communication?
+4. How do you avoid re-traumatization?
+5. What support can you provide?
+6. How do you balance necessary moderation action with trauma-informed care?
+
+**Correct Answer**: Recognise possible trauma response, use trauma-informed approach: acknowledge feelings, use clear non-threatening language, provide support and resources, avoid punitive language, maintain necessary moderation action whilst being trauma-informed, offer choices when possible.
+
+### 8.2. Scenario 2: Community Member Withdrawal
+
+**Situation**: After a community conflict, a community member completely withdraws from the community. They stop participating in discussions, avoid all communication, and seem to have disappeared. They were previously very active.
+
+**Your Response:**
+1. What might this withdrawal indicate?
+2. How do you recognise this as a possible trauma response?
+3. How do you reach out supportively?
+4. What support can you offer?
+5. How do you respect their need for space while offering support?
+6. What do you avoid doing?
+
+**Correct Answer**: Recognise possible flight/freeze trauma response. Respect their need for space, reach out with supportive non-pressuring communication, offer support and resources, provide choices, avoid pressuring participation, create safe space for return when ready.
+
+### 8.3. Scenario 3: Moderation Action with Known Trauma History
+
+**Situation**: You need to take moderation action against someone, but you know from previous interactions that they have experienced trauma. You're concerned that the moderation action might trigger them or cause re-traumatization.
+
+**Your Response:**
+1. Can you avoid taking necessary moderation action?
+2. How do you take action in a trauma-informed way?
+3. What language and approach do you use?
+4. How do you provide support while maintaining boundaries?
+5. What do you avoid doing?
+6. How do you follow up?
+
+**Correct Answer**: Cannot avoid necessary action, but take action using trauma-informed approach: clear non-threatening communication, explain reasoning, provide support and resources, offer choices when possible, avoid punitive language or public shaming, follow up supportively, maintain professional boundaries.
+
+## 9. TRAINING REQUIREMENTS
+
+This training document is part of the comprehensive mandatory training curriculum. For complete information about initial onboarding requirements, annual review requirements, training confirmation submission, and compliance policies, see [Mandatory Training Requirements](/staff/handbook#81-mandatory-training-requirements) in the Staff Handbook.
+
+**Key Points:**
+- This document must be reviewed during initial onboarding and annually thereafter
+- Training confirmation must be submitted at [forms.nhcarrigan.com](https://forms.nhcarrigan.com)
+- Failure to complete annual training review will result in dismissal from staff positions
+- All training completions are documented in staff records for accountability, legal compliance, and quality assurance
+
+---
+
+*This Trauma-Informed Moderation Training document is part of our comprehensive staff development programme designed to create safer, more supportive community environments that avoid re-traumatization and support healing. Trauma-informed moderation is an ongoing practice that requires commitment, self-awareness, and continuous learning. For questions about trauma-informed moderation or to report training completion, please contact designated leadership through staff channels.*
+
diff --git a/test/projects.spec.ts b/test/projects.spec.ts
index d4ea3eb..d2c8186 100644
--- a/test/projects.spec.ts
+++ b/test/projects.spec.ts
@@ -44,7 +44,7 @@ const convertTitleCaseToKebabCase = (string_: string): string => {
 };
 
 describe("projects documentation", () => {
-  it("should include all public projects", async() => {
+  it("should include all public projects", {timeout: 10000}, async() => {
     expect.hasAssertions();
     const projects = await getProjects();
     const docs = await readdir(join(__dirname, "..", "src", "content", "docs", "projects"));