fix typo

Author: DominikMe

articles/communication-services/.openpublishing.redirection.communication-services.json

@@ -2,7 +2,7 @@
     "redirections": [
         {
             "source_path_from_root": "/articles/communication-services/concepts/client-and-server-architecture.md",
-            "redirect_url": "/articles/communication-services/concepts/identity-model#client-services-architecture",
+            "redirect_url": "/articles/communication-services/concepts/identity-model#client-server-architecture",
             "redirect_document_id": false
         },
         {

articles/communication-services/concepts/authentication.md

@@ -99,4 +99,4 @@ The user identity is intended to act as a primary key for logs and metrics colle
 > [Trusted authentication service hero sample](../samples/trusted-auth-sample.md)
 
 For more information, see the following articles:
-- [Learn about client and server architecture](../concepts/identity-model#client-services-architecture)
+- [Learn about client and server architecture](../concepts/identity-model#client-server-architecture)

articles/communication-services/quickstarts/identity/access-tokens.md

@@ -18,7 +18,7 @@ ms.custom: mode-other, devx-track-azurecli, devx-track-extended-java, devx-track
 
 Access tokens enable Azure Communication Services SDKs to [authenticate](../../concepts/authentication.md) directly against Azure Communication Services as a particular identity. You need to create access tokens if you want your users to join a call or chat thread within your application. 
 
-This article describes how to use the Azure Communication Services SDKs to create identities and manage your access tokens. For production use cases, we recommend that you generate access tokens on a server-side service as described in [Client and server architecture](../../concepts/identity-model#client-services-architecture).
+This article describes how to use the Azure Communication Services SDKs to create identities and manage your access tokens. For production use cases, we recommend that you generate access tokens on a server-side service as described in [Client and server architecture](../../concepts/identity-model#client-server-architecture).
 
 ::: zone pivot="platform-azcli"
 [!INCLUDE [Azure CLI](./includes/access-tokens/access-token-az-cli.md)]
@@ -75,5 +75,5 @@ To learn more about how to send an email using the Azure Communication Services
 
  - [Learn about authentication](../../concepts/authentication.md)
  - [Add chat to your app](../chat/get-started.md)
- - [Learn about client and server architecture](../../concepts/identity-model#client-services-architecture)
+ - [Learn about client and server architecture](../../concepts/identity-model#client-server-architecture)
  - [Deploy trusted authentication service hero sample](../../samples/trusted-auth-sample.md)

articles/communication-services/tutorials/building-app-start.md

@@ -461,5 +461,5 @@ You might also want to:
 
 - [Add chat to your app](../quickstarts/chat/get-started.md)
 - [Create user access tokens](../quickstarts/identity/access-tokens.md)
-- [Learn about client and server architecture](../concepts/identity-model#client-services-architecture)
+- [Learn about client and server architecture](../concepts/identity-model#client-server-architecture)
 - [Learn about authentication](../concepts/authentication.md)

articles/communication-services/tutorials/events-playbook.md

@@ -108,7 +108,7 @@ Attendee experience can be directly embedded into an application or platform usi
 
 2.	Before developers dive into using [Azure Communication Services](../overview.md), they must [create a resource](../quickstarts/create-communication-resource.md?pivots=platform-azp&tabs=windows&preserve-view=true).
 
-3.	Once a resource is created, developers must [generate access tokens](../quickstarts/identity/access-tokens.md?pivots=programming-language-javascript&preserve-view=true) for attendees to access Azure Communication Services. We recommend using a [trusted service architecture](../concepts/identity-model#client-services-architecture).
+3.	Once a resource is created, developers must [generate access tokens](../quickstarts/identity/access-tokens.md?pivots=programming-language-javascript&preserve-view=true) for attendees to access Azure Communication Services. We recommend using a [trusted service architecture](../concepts/identity-model#client-server-architecture).
 
 4.	Developers can leverage [headless SDKs](../concepts/teams-interop.md) or [UI Library](../concepts/ui-library/ui-library-overview.md) using the join link URL to join the Teams meeting through [Teams Interoperability](../concepts/teams-interop.md). Details below:
 

articles/communication-services/tutorials/file-sharing-tutorial-acs-chat.md

@@ -378,7 +378,7 @@ You may also want to:
 
 - [Add chat to your app](../quickstarts/chat/get-started.md)
 - [Creating user access tokens](../quickstarts/identity/access-tokens.md)
-- [Learn about client and server architecture](../concepts/identity-model#client-services-architecture)
+- [Learn about client and server architecture](../concepts/identity-model#client-server-architecture)
 - [Learn about authentication](../concepts/authentication.md)
 - [Add file sharing with UI Library in Teams Interoperability Chat](./file-sharing-tutorial-interop-chat.md)
 - [Add file sharing with UI Library in Azure Communication Services Chat](./file-sharing-tutorial-acs-chat.md)

articles/communication-services/tutorials/file-sharing-tutorial-interop-chat.md

@@ -124,7 +124,7 @@ You may also want to:
 - [Check UI Library use cases](../concepts/ui-library/ui-library-use-cases.md)
 - [Add chat to your app](../quickstarts/chat/get-started.md)
 - [Creating user access tokens](../quickstarts/identity/access-tokens.md)
-- [Learn about client and server architecture](../concepts/identity-model#client-services-architecture)
+- [Learn about client and server architecture](../concepts/identity-model#client-server-architecture)
 - [Learn about authentication](../concepts/authentication.md)
 - [Add file sharing with UI Library in Azure Azure Communication Services end user Service Chat](./file-sharing-tutorial-acs-chat.md)
 - [Add inline image with UI Library in Teams Interoperability Chat](./inline-image-tutorial-interop-chat.md)

articles/communication-services/tutorials/hmac-header-tutorial.md

@@ -43,5 +43,5 @@ You might also want to:
 
 - [Add chat to your app](../quickstarts/chat/get-started.md)
 - [Create user access tokens](../quickstarts/identity/access-tokens.md)
-- [Learn about client and server architecture](../concepts/identity-model#client-services-architecture)
+- [Learn about client and server architecture](../concepts/identity-model#client-server-architecture)
 - [Learn about authentication](../concepts/authentication.md)

articles/communication-services/tutorials/includes/trusted-service-js.md

@@ -30,7 +30,7 @@ For this tutorial we'll be creating an Azure Function that will serve as a trust
 
 This service is responsible for authenticating users to Azure Communication Services. Users of your Communication Services applications will require an `Access Token` in order to participate in chat threads and VoIP calls. The Azure Function will work as a trusted middleman between the user and the Communication Services. This allows you to provision access tokens without exposing your resource connection string to your users.
 
-For more information, see the [client-server architecture](../../concepts/identity-model#client-services-architecture) and [authentication and authorization](../../concepts/authentication.md) conceptual documentation.
+For more information, see the [client-server architecture](../../concepts/identity-model#client-server-architecture) and [authentication and authorization](../../concepts/authentication.md) conceptual documentation.
 
 ## Setting up
 

articles/communication-services/tutorials/inline-image-tutorial-interop-chat.md

@@ -121,7 +121,7 @@ You might also want to:
 - [Check UI Library use cases](../concepts/ui-library/ui-library-use-cases.md)
 - [Add chat to your app](../quickstarts/chat/get-started.md)
 - [Create user access tokens](../quickstarts/identity/access-tokens.md)
-- [Learn about client and server architecture](../concepts/identity-model#client-services-architecture)
+- [Learn about client and server architecture](../concepts/identity-model#client-server-architecture)
 - [Learn about authentication](../concepts/authentication.md)
 - [Add file sharing with UI Library in Azure Communication Services Chat](./file-sharing-tutorial-acs-chat.md)
 - [Add file sharing with UI Library in Teams Interoperability Chat](./file-sharing-tutorial-interop-chat.md)