modifies the type

docs/pages/auth-concept/authentication.md

@@ -81,7 +81,7 @@ components:
 
 ```
 
-**The Client asyncapi.yaml file does not need to implement all the security requirements in the server, it only needs to implement the ones that it uses like `userPassword` here.**
+**The Client asyncapi.yaml file does not need to implement all the security requirements in the server, it only needs to implement the ones that it uses like *userPassword* here.**
 
 
 Glee can act as both a server and a client. Hence the need for `serverAuth` and `clientAuth`. Glee acts as a client when the server name is included in the `x-remoteServers` property in the `asyncapi.yaml` file.
@@ -116,6 +116,11 @@ export async function serverAuth({ authProps, done }) {
   }
 }
 ```
+**Parameters for done():**
+
+- Authentication Result (Boolean): true for success, false for failure.
+- HTTP Status Code (Integer): Code for authentication failure (e.g., 401 for Unauthorized).
+- Status Message (String): Description of the authentication result (e.g., "Unauthorized").
 
 When `true` is passed to the done parameter, the server/broker knows to go ahead and allow the client to connect, which means authentication has succeeded. However if the `done` parameter is called with `false` then the server knows to throw an error message and reject the client, which means authenticatio has failed.
 

docs/pages/auth-concept/bearerToken.md

@@ -61,7 +61,7 @@ components:
 
 ```
 
-**The Client asyncapi.yaml file does't need to implement all the security requirements in the server, it only needs to implement the ones that it uses like `http (bearer token)` here.**
+**The Client asyncapi.yaml file does't need to implement all the security requirements in the server, it only needs to implement the ones that it uses like &*http (bearer token)* here.**
 
 ### Client Side
 

docs/pages/auth-concept/httpApiKey.md

@@ -64,7 +64,7 @@ components:
 
 The `httpApiKey` could be in either the header or query parameter.
 
-**The Client asyncapi.yaml file does not need to implement all the security requirements in the server, it only needs to implement the ones that it uses like `httpApiKey` here.**
+**The Client asyncapi.yaml file does not need to implement all the security requirements in the server, it only needs to implement the ones that it uses like *httpApiKey* here.**
 
 ### Client Side
 

docs/pages/auth-concept/userPassword.md

@@ -57,7 +57,7 @@ components:
 
 ```
 
-**The Client asyncapi.yaml file does not need to implement all the security requirements in the server, it only needs to implement the ones that it uses like `userPassword` here.**
+**The Client asyncapi.yaml file does not need to implement all the security requirements in the server, it only needs to implement the ones that it uses like &*userPassword* here.**
 
 ### Client Side