Minor fixes for storybook pages (#5746) (#5748)

mgamis-msft · web-flow · commit f7120d023bd6 · 2025-03-27T18:11:50.000-04:00
diff --git a/packages/storybook8/stories/Composites/GettingStarted.mdx b/packages/storybook8/stories/Composites/GettingStarted.mdx
@@ -105,15 +105,15 @@ The following classes and interfaces handle some of the major features of the Az
 In our quickstart, we will be using the `CallAdapter` and `ChatAdapter` to power the `CallComposite` and `ChatComposite` respectively.
 Before we initialize the actual composite components, we need to set up the adapters that will power them first.
 These adapters take care of the entire state of the composites truly making them a turn-key solution.
-To setup the adapters, developers needs to pass information on the call or chat they want to join.
+To setup the adapters, developers need to pass information on the call or chat they want to join.
 
 The adapters require access tokens, group IDs, or thread IDs to be setup.
 For this quickstart, the access tokens required need to have both `chat` and `VoIP` scopes.
 For more information on access tokens see: [Identity Model](https://docs.microsoft.com/azure/communication-services/concepts/identity-model#access-tokens)
 These elements come from services that go through the proper steps to generate these IDs and pass them to the client application.
 For more information, see: [Client Server Architecture](https://learn.microsoft.com/en-us/azure/communication-services/concepts/ui-library/ui-library-use-cases?pivots=platform-web#recommended-architecture).
-For Example: The Group Chat composite expects that the `userId` associated to the `token` being used to initialize it has already been joined to the `threadId` being provided.
-If the token hasn't been joined to the thread ID, then the Group Chat composite will fail.
+For example: The Group Chat composite expects that the `userId` associated to the `token` being used to initialize it has already been joined to the `threadId` being provided.
+If the token hasn't been joined to the `threadId`, then the Group Chat composite will fail.
 For more information on chat, see: [Getting Started with Chat](https://docs.microsoft.com/azure/communication-services/quickstarts/chat/get-started?pivots=programming-language-csharp)
 
 Go to the `src` folder inside of [ui-library-quickstart-composites](https://github.com/Azure-Samples/communication-services-javascript-quickstarts/tree/main/ui-library-quickstart-composites) and look for the file `App.tsx`.
diff --git a/packages/storybook8/stories/StatefulClient/BestPractices.mdx b/packages/storybook8/stories/StatefulClient/BestPractices.mdx
@@ -8,11 +8,11 @@ We are sharing some of our recommended best practices when handling state with A
 
 ## Use the Stateful Clients
 
-Managing the complex state of a calling or chat sesion can be challenging. This was a complex problem we found we were in and we think many of our developer community
+Managing the complex state of a calling or chat session can be challenging. This was a complex problem we found we were in and we think many of our developer community
 will run into this challenge themselves. We wanted to find a convenient way to store this information on the client in a way that plays nicely with our components we are offering.
 By using the stateful client for calling or chat, you are on our recommended path for powering your own communications experience using Azure Communication Services.
 
-## Use usePropsFor
+## Use `usePropsFor`
 
 If you are using our provided UI Components, `usePropsFor` will help you get integrated with the underlying functionality quickly. This provides a series of properties our
 provided components are expecting from the stateful client to render an experience your users will be expecting. This is the fastest way to get your experience up and running with Azure Communication Services.
diff --git a/packages/storybook8/stories/StatefulClient/Chat/Docs.mdx b/packages/storybook8/stories/StatefulClient/Chat/Docs.mdx
@@ -82,13 +82,13 @@ npm run start
 
 The following classes and interfaces from the Azure Communication Services UI client library are referenced in this quickstart:
 
-| Name                                                                                                                            | Description                                                                              |
-| ------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
-| [ChatClient](https://azuresdkdocs.blob.core.windows.net/$web/javascript/azure-communication-chat/1.0.0/classes/chatclient.html) | Low-level chat library client.                                                           |
-| [createStatefulChatClient](.?path=/docs/stateful-client-overview--docs#chat-statefulclient)                                     | Method to translate low-level library client into a stateful client for the UI Library   |
-| [ChatClientProvider](./?path=/docs/stateful-client-react-hooks-setting-up--docs#chat)                                           | Provider allows access to the Stateful Chat Client to the components inside of it        |
-| [ChatThreadClientProvider](./?path=/docs/stateful-client-react-hooks-setting-up--docs#chat)                                     | Provider allows access to the Stateful Chat Thread Client to the components inside of it |
-| [usePropsFor](.?path=/docs/stateful-client-react-hooks-usepropsfor--docs#usepropsfor-chat-app-example)                          | Hook to generate required props to enable UI Components                                  |
+| Name                                                                                                                       | Description                                                                              |
+| -------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
+| [ChatClient](https://learn.microsoft.com/en-us/javascript/api/@azure/communication-chat/chatclient?view=azure-node-latest) | Low-level chat library client.                                                           |
+| [createStatefulChatClient](.?path=/docs/stateful-client-overview--docs#chat-statefulclient)                                | Method to translate low-level library client into a stateful client for the UI Library   |
+| [ChatClientProvider](./?path=/docs/stateful-client-react-hooks-setting-up--docs#chat)                                      | Provider allows access to the Stateful Chat Client to the components inside of it        |
+| [ChatThreadClientProvider](./?path=/docs/stateful-client-react-hooks-setting-up--docs#chat)                                | Provider allows access to the Stateful Chat Thread Client to the components inside of it |
+| [usePropsFor](.?path=/docs/stateful-client-react-hooks-usepropsfor--docs#usepropsfor-chat-app-example)                     | Hook to generate required props to enable UI Components                                  |
 
 ## Instantiate Stateful Chat Client and Chat Thread Client
 
