fix: fixing rendering errors of glee docs

asyncapi · Aug 31, 2024 · 361a211 · 361a211
1 parent 3933958
commit 361a211
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/pages/bearerToken.md b/docs/pages/bearerToken.md
@@ -81,7 +81,7 @@ export async function clientAuth({ parsedAsyncAPI, serverName }) {
 }
 ```
 
-Glee will utilize the `token` for server authentication, employing it in the header with the format: `Authorization: Bearer {token}`.
+Glee will utilize the `token` for server authentication, employing it in the header with the format: `Authorization: Bearer \{token\}`.
 
 ### Server Side
 

diff --git a/docs/pages/installation.md b/docs/pages/installation.md
@@ -100,7 +100,7 @@ These scripts serve different development stages:
 
 #### Setting up `asyncapi.yaml` and Required Directories
 
-Craft an `asyncapi.yaml` file capable of receiving a "hello {name}" message via WebSocket (`ws`) protocol on the `hello` channel. Define the operation ID as `onHello`, indicating the function to be called, and set the payload type to string for publishing on that channel.
+Craft an `asyncapi.yaml` file capable of receiving a "hello \{name\}" message via WebSocket (`ws`) protocol on the `hello` channel. Define the operation ID as `onHello`, indicating the function to be called, and set the payload type to string for publishing on that channel.
 
 ```yaml
 # AsyncAPI Specification for Hello, Glee!
-Original file line number
+Diff line change
@@ Expand Up @@
     }
     ```
-    Glee will utilize the `token` for server authentication, employing it in the header with the format: `Authorization: Bearer {token}`.
+    Glee will utilize the `token` for server authentication, employing it in the header with the format: `Authorization: Bearer \{token\}`.
     ### Server Side
@@ Expand Down @@