[Docs] Update "generating a token" section to include link to the server-side docs

Packages/StreamVideo/Runtime/Core/LowLevelClient/StreamVideoLowLevelClient.cs

@@ -83,6 +83,7 @@ var sfuWebSocket
                 serializer, timeService, networkMonitor, applicationInfo, logs, config);
         }
 
+        //StreamTodo: review if this is valid for video SDK
         /// <summary>
         /// Create Development Authorization Token. Dev tokens work only if you enable "Disable Auth Checks" in your project's Dashboard.
         /// Dev tokens bypasses authorization and should only be used during development and never in production!

docusaurus/docs/Unity/03-guides/01-client-auth.mdx

@@ -53,11 +53,10 @@ public class VideoClient : MonoBehaviour
 
 ### Generating a token
 
-* Tokens need to be generated server side. You can use our server side SDKs to quickly add support for this.
-Typically you integrate this into the part of your codebase where you login or register users.
-The tokens provide a way to authenticate a user or give access to a specific set of calls.
+Tokens provide a way to authenticate a user or give access to a specific set of calls. They're similar to passwords but offer more flexibility, allowing you to set the expiry date. For security reasons, tokens need to be generated server-side.
+Typically, you integrate this into the part of your codebase where you login or register users. You can use our server-side SDKs to easily add support for this. For detailed instruction, refer to our server-side docs on [installation](https://getstream.io/video/docs/api/#installation) and [creating-users-and-user-tokens](https://getstream.io/video/docs/api/#creating-users-and-user-tokens).
 
-* Here's a valid user and token to help you get started on the client side, before integrating with your backend API.
+Here's a valid user and token to help you get started on the client side before integrating with your backend API:
 
 <TokenSnippet sampleApp='meeting' displayStyle='credentials'/>