Upgrade docusaurus

docs/faq.md

@@ -226,7 +226,7 @@ will return the wire error.
 Alternatively, if you wish to cancel the operation and immediately stop
 the client stream, see [below](#cancel-stream) to cancel the operation.
 
-### How do I cancel a client response stream in Connect-Go?
+### How do I cancel a client response stream in Connect-Go? {#cancel-stream}
 
 To cancel and abort a stream, call the cancel function of the underlying
 context associated with the stream. This context is provided on stream

docs/kotlin/getting-started.md

@@ -226,7 +226,8 @@ The Protobuf dependency can be what the current project is already using. Make s
 versions between the runtime and the Google Java plugin version. Here we are using the latest version.
 :::
 
-<details><summary>Having trouble with Gradle files? Here is what one might look like: </summary>
+<details>
+<summary>Having trouble with Gradle files? Here is what one might look like: </summary>
 
 ```groovy title="app/build.gradle"
 plugins {
@@ -282,7 +283,7 @@ dependencies {
 
 :::note
 
-The default for my Android Studio isn't set up with Gradle `kts`. The examples here will is using
+The default for Android Studio isn't set up with Gradle `kts`. The examples here are using
 classic Gradle with Groovy. With Gradle `kts`, the changes are pretty similar for the dependency
 declarations.
 

docs/node/testing.md

@@ -131,7 +131,7 @@ We do not recommend using [`fastify.inject()`](https://fastify.dev/docs/v1.14.x/
 for testing Connect routes. `fastify.inject()` is a great tool, but using it means you have to handle details of the
 protocol like `Content-Type` headers and status codes yourself. This is rather straight-forward for Connect unary,
 but much less so for streaming RPCs, or the gRPC or gRPC-Web protocols.
-:::note
+:::
 
 ### Testing with an in-memory server
 

docs/protocol.md

@@ -143,23 +143,23 @@ general-purpose HTTP tools.
 * **Unary-Call-Specification** → Method-Post Path Unary-Content-Type \[Connect-Protocol-Version\] \[Timeout\] \[Content-Encoding\] \[Accept-Encoding\]
 * **Method-Post** → ":method POST"
 * **Path** → ":path" "/" [Routing-Prefix "/"] Procedure-Name ; case-sensitive
-* **Routing-Prefix** → {_arbitrary prefix_}
-* **Procedure-Name** → {_IDL-specific service & method name_} ; see [Protocol Buffers](#protobuf)
-* **Message-Codec** → ("proto" / "json" / {_custom_})
+* **Routing-Prefix** → \{_arbitrary prefix_\}
+* **Procedure-Name** → \{_IDL-specific service & method name_\} ; see [Protocol Buffers](#protobuf)
+* **Message-Codec** → ("proto" / "json" / \{_custom_\})
 * **Unary-Content-Type** → "content-type" "application/" Message-Codec
 * **Connect-Protocol-Version** → "connect-protocol-version" "1"
 * **Timeout** → "connect-timeout-ms" Timeout-Milliseconds
-* **Timeout-Milliseconds** → {_positive integer as ASCII string of at most 10 digits_}
+* **Timeout-Milliseconds** → \{_positive integer as ASCII string of at most 10 digits_\}
 * **Content-Encoding** → "content-encoding" Content-Coding
-* **Content-Coding** → "identity" / "gzip" / "br" / "zstd" / {_custom_}
+* **Content-Coding** → "identity" / "gzip" / "br" / "zstd" / \{_custom_\}
 * **Accept-Encoding** → "accept-encoding" Content-Coding \*("," [" "] Content-Coding) ; subset of HTTP quality value syntax
 * **Leading-Metadata** → Custom-Metadata
 * **Custom-Metadata** → ASCII-Metadata / Binary-Metadata
 * **ASCII-Metadata** → Header-Name ASCII-Value
-* **Binary-Metadata** → {Header-Name "-bin"} {base64-encoded value}
+* **Binary-Metadata** → \{Header-Name "-bin"\} \{base64-encoded value\}
 * **Header-Name** → 1\*( %x30-39 / %x61-7A / "\_" / "-" / ".") ; 0-9 a-z \_ - .
 * **ASCII-Value** → 1\*( %x20-%x7E ) ; space & printable ASCII
-* **Bare-Message** → *{binary octet}
+* **Bare-Message** → *\{binary octet\}
 
 **Unary-Request-Headers** are sent as — and have the same semantics as
 — HTTP headers. Servers may respond with an error if the client sends too
@@ -215,7 +215,7 @@ content.
 * **Unary-Get-Call-Specification** → Method-Get Path "?" Query-Get \[Timeout\] \[Accept-Encoding\]
 * **Method-Get** → ":method GET"
 * **Query-Get** → Message-Query Encoding-Query \[Base64-Query\] \[Compression-Query\] \[Connect-Version-Query\]
-* **Message-Query** → "message=" (*{percent-encoded octet})
+* **Message-Query** → "message=" (*\{percent-encoded octet\})
 * **Base64-Query** → "&base64=1"
 * **Encoding-Query** → "&encoding=" Message-Codec
 * **Compression-Query** → "&compression=" Content-Coding
@@ -299,10 +299,10 @@ an HTTP status code of 400.
 
 * **Unary-Response** → Unary-Response-Headers Bare-Message
 * **Unary-Response-Headers** → HTTP-Status Unary-Content-Type \[Content-Encoding\] \[Accept-Encoding\] \*Leading-Metadata \*Prefixed-Trailing-Metadata
-* **HTTP-Status** → ":status" ("200" / {_error code translated to HTTP_})
+* **HTTP-Status** → ":status" ("200" / \{_error code translated to HTTP_\})
 * **Prefixed-Trailing-Metadata** → Prefixed-ASCII-Metadata / Prefixed-Binary-Metadata
 * **Prefixed-ASCII-Metadata** → Prefixed-Header-Name ASCII-Value
-* **Prefixed-Binary-Metadata** → {Prefixed-Header-Name "-bin"} {base64-encoded value}
+* **Prefixed-Binary-Metadata** → \{Prefixed-Header-Name "-bin"\} \{base64-encoded value\}
 * **Prefixed-Header-Name** → "trailer-" Header-Name
 
 **Unary-Response-Headers** are sent as — and have the same semantics as
@@ -422,13 +422,13 @@ RPC types may be unavailable.
 * **Streaming-Request** → Streaming-Request-Headers \*Enveloped-Message
 * **Streaming-Request-Headers** → Streaming-Call-Specification \*Leading-Metadata
 * **Streaming-Call-Specification** → Method-Post Path Streaming-Content-Type \[Connect-Protocol-Version\] \[Timeout\] \[Streaming-Content-Encoding\] \[Streaming-Accept-Encoding\]
-* **Streaming-Content-Type** → "content-type" "application/connect+" ("proto" / "json" / {_custom_})
+* **Streaming-Content-Type** → "content-type" "application/connect+" ("proto" / "json" / \{_custom_\})
 * **Streaming-Content-Encoding** → "connect-content-encoding" Content-Coding
 * **Streaming-Accept-Encoding** → "connect-accept-encoding" Content-Coding \*("," [" "] Content-Coding)
 * **Enveloped-Message** → Envelope-Flags Message-Length Message
 * **Envelope-Flags** → %d0-255 ; 8 bitwise flags encoded as 1 byte unsigned integer
-* **Message-Length** → {_length of Message_} ; encoded as 4 byte unsigned integer, big-endian
-* **Message** → *{binary octet}
+* **Message-Length** → \{_length of Message_\} ; encoded as 4 byte unsigned integer, big-endian
+* **Message** → *\{binary octet\}
 
 If **Streaming-Content-Type** does not begin with "application/connect+",
 servers should respond with an HTTP status of 415 Unsupported Media Type. This
@@ -643,7 +643,7 @@ After a successful RPC, `EndStreamResponse` can be as simple as `{}`.
 
 When used with Protocol Buffer IDL,
 
-* **Procedure-Name** → ?( {_proto package name_} "." ) {_service name_} "/" {_method name_}
+* **Procedure-Name** → ?( \{_proto package name_\} "." ) \{_service name_\} "/" \{_method name_\}
 * **Unary-Content-Type** → "content-type application/" ("proto" / "json")
 * **Streaming-Content-Type** → "content-type application/connect+" ("proto" / "json")
 

docs/swift/getting-started.md

@@ -3,7 +3,7 @@ title: Getting started
 sidebar_position: 1
 ---
 
-Connect-Swift is a small library (<200KB!) that provides support for using
+Connect-Swift is a small library (\<200KB!) that provides support for using
 generated, type-safe, and idiomatic Swift APIs to communicate with your app's
 servers using [Protocol Buffers (Protobuf)][protobuf]. It works with the Connect, gRPC, and gRPC-Web protocols.
 
@@ -197,7 +197,11 @@ At this point, your app should build successfully.
 
 To create the chat view, replace the contents of `ContentView.swift` with:
 
-<details><summary>Click to expand <code>ContentView.swift</code></summary>
+<details>
+
+<summary>
+    Click to expand <code>ContentView.swift</code>
+</summary>
 
 ```swift
 import Combine
@@ -320,7 +324,10 @@ struct ContentView: View {
 
 Lastly, replace the contents of `ElizaApp.swift` with:
 
-<details><summary>Click to expand <code>ElizaApp.swift</code></summary>
+<details>
+<summary>
+Click to expand <code>ElizaApp.swift</code>
+</summary>
 
 ```swift
 import Connect
@@ -397,7 +404,9 @@ If you'd like to use gRPC as the transport protocol in the above example,
 simply change the following lines after ensuring you have
 [included the `ConnectNIO` library dependency](#add-the-connect-swift-package):
 
-<details><summary>Click to expand</summary>
+<details>
+
+<summary>Click to expand</summary>
 
 ```swift
 //highlight-next-line
@@ -483,7 +492,7 @@ using the gRPC protocol for a few reasons:
   as well as the ability to register custom
   [compression algorithms](./using-clients.md#compression)
   and [interceptors](./interceptors.md).
-- **Binary size.** The Connect-Swift library is very small (<200KB)
+- **Binary size.** The Connect-Swift library is very small (\<200KB)
   and does not require any third party networking dependencies when using
   it with the Connect and gRPC-Web protocols. When using it with gRPC,
   the binary size is a bit bigger (~2.4MB) due to the SwiftNIO dependency

docs/swift/testing.md

@@ -79,7 +79,10 @@ When the production `connect-swift` plugin is invoked, it outputs
 - A protocol interface ending with `*ClientInterface`
 - A production implementation that conforms to the protocol and ends with `*Client`
 
-<details><summary>Click to expand <code>eliza.connect.swift</code></summary>
+<details>
+<summary>
+Click to expand <code>eliza.connect.swift</code>
+</summary>
 
 ```swift
 import Connect
@@ -130,7 +133,10 @@ When the mock `connect-swift-mocks` plugin is invoked, it outputs a
 `.mock.swift` file which includes an implementation ending with `*ClientMock`
 that conforms to the same interface as the production client:
 
-<details><summary>Click to expand <code>eliza.mock.swift</code></summary>
+<details>
+<summary>
+Click to expand <code>eliza.mock.swift</code>
+</summary>
 
 ```swift
 import Combine