update docusaurus from 3.0.1 to 3.4.0 (#1490)

* update docusaurus from 3.0.1 to 3.4.0

* fix some broken links

* fixes incorrect links

* adds text change to test link

* changes anchor text

* fixes culprit link breaking build

---------

Co-authored-by: zachary painter <[email protected]>

Author: kenjenkins

content/docs/capabilities/routing.mdx

@@ -84,7 +84,7 @@ Once a Route is created, the Metric Name field will populate. You can use this n
     - https://b.example.com
 ```
 
-A load balancing weight may be associated with a particular upstream by appending `,[weight]` to the URL. The exact behavior depends on your [`lb_policy`](/docs/reference/routes/load-balancing#load-balancing-policy) setting. See [Load Balancing](@site/content/docs/capabilities/load-balancing.md) for example [configurations](@site/content/docs/capabilities/load-balancing.md#load-balancing-weight).
+A load balancing weight may be associated with a particular upstream by appending `,[weight]` to the URL. The exact behavior depends on your [`lb_policy`](/docs/reference/routes/load-balancing#load-balancing-policy) setting. See [Load Balancing](/docs/capabilities/load-balancing) for example [configurations](/docs/capabilities/load-balancing#load-balancing-weight).
 
 Must be `tcp` if `from` is `tcp+https`.
 

content/docs/core/upgrading.mdx

@@ -271,10 +271,10 @@ For Open Source, please use IdP Claims passed by your IdP.
   - [Okta](https://developer.okta.com/docs/guides/customize-tokens-groups-claim/main)
   - [Auth0](https://auth0.com/docs/customize/extensions/authorization-extension/configure-authorization-extension#add-authorization-information-to-the-token-issued)
   - [Azure](https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-group-claims)
-  - [Cognito](/docs/identity-providers/cognito.html#group-based-policies)
+  - [Cognito](/docs/identity-providers/cognito##getting-groups)
 - You may need adjust requested scopes via `idp_scopes` config option.
 - visit your authenticate endpoint `/.pomerium` route to check the group claims are passed by your IdP.
-- use `claim/` [PPL criteria](/docs/capabilities/ppl.html#criteria)
+- use `claim/` [PPL criteria](/docs/capabilities/ppl#criteria)
 
 ```yaml
 routes:
@@ -447,7 +447,7 @@ With the v0.13 release, routes may contain [multiple `to` URLs](/docs/reference/
 - Configurable [load balancing policies](/docs/reference/routes/load-balancing#load-balancing-policy)
 - Configurable [load balancing weight](/docs/reference/routes/to)
 
-See [Load Balancing](@site/content/docs/capabilities/load-balancing.md) for more information on using this feature set.
+See [Load Balancing](/docs/capabilities/load-balancing) for more information on using this feature set.
 
 #### Dynamic certificate updates
 

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

@@ -17,7 +17,7 @@ Make sure you’ve completed the following guides:
 
 - [**Build a Simple Route**](/docs/courses/fundamentals/zero-build-routes)
 - [**Build a Simple Policy**](/docs/courses/fundamentals/zero-build-policies)
-- [**Single Sign-on with JWTs**](/docs/courses/fundamentals/zero-single-sign-on)
+- [**Single Sign-on (SSO)**](/docs/courses/fundamentals/zero-single-sign-on)
 - [**Build Advanced Policies**](/docs/courses/fundamentals/zero-advanced-policies)
 
 Each tutorial builds on the same configuration files. In this tutorial, you’ll build new routes with some of Pomerium’s route-level settings.
@@ -62,7 +62,7 @@ Save your route and apply your changeset.
 
 ### Pass identity headers (per route)
 
-[Pass Identity Headers](/docs/reference/routes/pass-identity-headers-per-route) is a route-level setting that forwards the user's JWT to the upstream application in a signed HTTP header. The HTTP header must use the (case insensitive) `x-pomerium-jwt-assertion` format. You configured this setting in the [previous guide](docs/courses/fundamentals/zero-single-sign-on), but let's see how it looks as a request header.
+[Pass Identity Headers](/docs/reference/routes/pass-identity-headers-per-route) is a route-level setting that forwards the user's JWT to the upstream application in a signed HTTP header. The HTTP header must use the (case insensitive) `x-pomerium-jwt-assertion` format. You configured this setting in the [previous guide](/docs/courses/fundamentals/zero-single-sign-on), but let's see how it looks as a request header.
 
 In the Zero Console:
 

content/docs/internals/connection.mdx

@@ -70,7 +70,7 @@ Different timeouts apply at various stages of the connection lifecycle:
 
 - **Request timeout**: This timeout applies to the total time a request can take, which includes connection establishment, request forwarding, processing at the upstream service, and response forwarding. If a complete response is not received within the set timeout, Pomerium will return an error to the client. This timeout can be configured via the [`timeout_write`](/docs/reference/global-timeouts) parameter. It may need adjustment, for instance, when handling large uploads.
 
-- **Upstream timeout**: This timeout applies to the time a request takes to travel from Pomerium to the upstream service and back. It can be configured per-route via the [`timeout`](/docs/reference/routes/timeouts#route-timeout) parameter and is considered part of the request timeout. By default, it aligns with the global [`default_upstream_timeout`](docs/reference/default-upstream-timeout) setting.
+- **Upstream timeout**: This timeout applies to the time a request takes to travel from Pomerium to the upstream service and back. It can be configured per-route via the [`timeout`](/docs/reference/routes/timeouts#route-timeout) parameter and is considered part of the request timeout. By default, it aligns with the global [`default_upstream_timeout`](/docs/reference/default-upstream-timeout) setting.
 
 ![Example of HTTP request lifecycle and timeout settings](./img/timeouts-http-request/timeouts-http-diagram.png)
 

content/docs/reference/routes/to.mdx

@@ -71,7 +71,7 @@ Multiple upstream resources can be targeted by using a list instead of a single
 
 ### Set load balancing weight
 
-A load balancing weight may be associated with a particular upstream by appending `,[weight]` to the URL. The exact behavior depends on your [`lb_policy`](/docs/reference/routes/load-balancing#load-balancing-policy) setting. See [Load Balancing](@site/content/docs/capabilities/load-balancing.md) for example [configurations](@site/content/docs/capabilities/load-balancing.md#load-balancing-weight).
+A load balancing weight may be associated with a particular upstream by appending `,[weight]` to the URL. The exact behavior depends on your [`lb_policy`](/docs/reference/routes/load-balancing#load-balancing-policy) setting. See [Load Balancing](/docs/capabilities/load-balancing) for example [configurations](/docs/capabilities/load-balancing#load-balancing-weight).
 
 ```yaml
 - from: https://example.com

package.json

@@ -17,11 +17,11 @@
     "format-check": "prettier --check ."
   },
   "dependencies": {
-    "@docusaurus/core": "^3.0.1",
-    "@docusaurus/preset-classic": "^3.0.1",
-    "@docusaurus/theme-common": "^3.0.1",
-    "@docusaurus/theme-mermaid": "3.0.1",
-    "@docusaurus/types": "^3.0.1",
+    "@docusaurus/core": "^3.4.0",
+    "@docusaurus/preset-classic": "^3.4.0",
+    "@docusaurus/theme-common": "^3.4.0",
+    "@docusaurus/theme-mermaid": "^3.4.0",
+    "@docusaurus/types": "^3.4.0",
     "@emotion/react": "^11.11.3",
     "@emotion/styled": "^11.11.0",
     "@mdx-js/react": "^3.0.0",