chore: upgrade docusaurus and fixed broken links

package.json

@@ -32,9 +32,9 @@
   },
   "dependencies": {
     "@algolia/client-search": "^4.22.0",
-    "@docusaurus/core": "^3.0.1",
-    "@docusaurus/preset-classic": "^3.0.1",
-    "@docusaurus/theme-mermaid": "^3.0.1",
+    "@docusaurus/core": "^3.2.1",
+    "@docusaurus/preset-classic": "^3.2.1",
+    "@docusaurus/theme-mermaid": "^3.2.1",
     "@mdx-js/react": "^3.0.0",
     "clsx": "^2.1.0",
     "prism-react-renderer": "^2.3.1",
@@ -44,8 +44,8 @@
     "search-insights": "^2.13.0"
   },
   "devDependencies": {
-    "@docusaurus/module-type-aliases": "^3.0.1",
-    "@docusaurus/types": "^3.0.1",
+    "@docusaurus/module-type-aliases": "^3.2.1",
+    "@docusaurus/types": "^3.2.1",
     "@tsconfig/docusaurus": "^2.0.2",
     "@types/react": "^18.2.46",
     "typescript": "^5.3.3"

versioned_docs/version-1.9.0/guides/collaboration.md

@@ -93,7 +93,7 @@ The developer who does not have access to download a cluster's kubeconfig can us
 2. You will be presented with a screen containing your public key. The associated private key is stored securely in a local database.
 3. Copy or download your public key.
 4. Send the public key to your cluster admin and wait for them to generate and send you back an encrypted context.
-5. Once you have an encrypted context you can [add it](/guides/using-desktop-app?id=adding-a-context) using the Desktop app or the [CLI](/references/command-line?id=add).
+5. Once you have an encrypted context you can [add it](/guides/using-desktop-app.mdx?id=adding-a-context) using the Desktop app or the [CLI](/references/command-line?id=add).
 
 #### Using the CLI
 

versioned_docs/version-1.9.0/tutorials/mount.mdx

@@ -6,7 +6,7 @@ import Prerequisites from './_fragments/prerequisites.md'
 
 # Developing with Remote Volumes
 
-In this tutorial we expore how developers can locally mount cluster volumes in their local workstation so that their local code can read or write to these volumes.
+In this tutorial we explore how developers can locally mount cluster volumes in their local workstation so that their local code can read or write to these volumes.
 
 When working on a service locally, developers may want to see the data being used by the same service running in their cluster. Seeing this data locally is quite difficult, however, because the data is stored remotely in a Persistent Volume, and only visible from within running pods. Copying the data locally can be cumbersome, and is a real challenge to keep in sync.
 
@@ -107,7 +107,7 @@ If you don't have the Desktop installed, you can run the Intercept using the CLI
 Open `packages/core/index.js` in your IDE and set the port on Line 10 be equal to the local port specified in the Intercept. If you ran the Intercept using the Development Profile this port needs to be changed to `4000`.
 
 :::note
-If you haven't already instantiated the cluster configuration for running the Core service locally, follow the steps under [Setting up a Teleport](/tutorials/core?id=setting-up-a-teleport)
+If you haven't already instantiated the cluster configuration for running the Core service locally, follow the steps under [Setting up a Teleport](/tutorials/core.mdx?id=setting-up-a-teleport)
 :::
 
 Run the Core service locally: