Merge pull request #125015 from ArieHein/Spelling-Wave-12

ttorble · web-flow · commit 222e930494b4 · 2024-12-03T15:45:24.000Z
Spelling Fixes - Wave 12
diff --git a/articles/azure-web-pubsub/howto-configure-application-firewall.md b/articles/azure-web-pubsub/howto-configure-application-firewall.md
@@ -102,7 +102,7 @@ The application firewall rules only take effect when the access token contains t
 Below is an example to add userId and insert a unique placeholder in the access token:
 
 ```cs
-// The GUID role wont have any effect. But it esures this token's uniqueness when using rule ThrottleByJwtSignatureRule.
+// The GUID role wont have any effect. But it ensures this token's uniqueness when using rule ThrottleByJwtSignatureRule.
 var url = service.GetClientAccessUri((userId: "user1" , roles: new string[] {  "webpubsub.joinLeaveGroup.group1", Guid.NewGuid().ToString()});
 ```
 
diff --git a/articles/azure-web-pubsub/howto-enable-geo-replication.md b/articles/azure-web-pubsub/howto-enable-geo-replication.md
@@ -35,7 +35,7 @@ Contoso **could** set up another Web PubSub resource in Canada Central which is
 
 All of the above takes engineering resources away from focusing on product innovation.
 
-![Diagram of using two Azure Web PubSub instances to handle traffic from two countries. ](./media/howto-enable-geo-replication/web-pubsub-multiple.png "Mutiple Web PubSub Example")
+![Diagram of using two Azure Web PubSub instances to handle traffic from two countries. ](./media/howto-enable-geo-replication/web-pubsub-multiple.png "Multiple Web PubSub Example")
 
 ### Harnessing the geo-replication feature
 With the geo-replication feature, Contoso can now establish a replica in Canada Central, effectively overcoming the above-mentioned challenges. The developer team is glad to find out that they don't need to make any code changes. It's as easy as clicking a few buttons on Azure portal. The developer team is also happy to share with the stakeholders that as Contoso plans to enter the European market, they simply need to add another replica in Europe. 
diff --git a/articles/azure-web-pubsub/howto-generate-client-access-url.md b/articles/azure-web-pubsub/howto-generate-client-access-url.md
@@ -270,7 +270,7 @@ You could also use Microsoft Entra ID and generate the token by invoking [Genera
     We use [CURL](https://curl.se/) tool to show how to invoke the REST APIs. The tool is bundled into Windows 10/11, and you could install the tool following [Install CURL](https://curl.se/download.html).
 
     ```bash
-    # set neccessory values, replace the placeholders with your actual values
+    # set necessary values, replace the placeholders with your actual values
     export TenantId=<your_tenant_id>
     export ClientId=<your_client_id>
     export ClientSecret=<your_client_secret>
diff --git a/articles/azure-web-pubsub/howto-integrate-app-gateway.md b/articles/azure-web-pubsub/howto-integrate-app-gateway.md
@@ -136,7 +136,7 @@ app.get("/negotiate", async (req, res) => {
     url
   })
 }
-// Every 2 seconds, we ask Web PubSub service to send all connected clients the messsage "hello, world"
+// Every 2 seconds, we ask Web PubSub service to send all connected clients the message "hello, world"
 setInterval(() => {
   webpubsub.sendToAll("hello, world", { contentType: "text/plain" });
 }, 2000);
@@ -230,7 +230,7 @@ app.get("/negotiate", async (req, res) => {
 
 Find the public IP of your Application Gateway resource and set the environment variable. 
 ```bash
-export appGatewayEndpoint="<replace with the public IP of your Applciation Gateway resource>"
+export appGatewayEndpoint="<replace with the public IP of your Application Gateway resource>"
 ```
 
 Three points to note. 
diff --git a/articles/azure-web-pubsub/howto-integrate-app-service.md b/articles/azure-web-pubsub/howto-integrate-app-service.md
@@ -120,7 +120,7 @@ git clone https://github.com/Azure/awps-webapp-sample.git
 ## Configure upstream server to handle events coming from Web PubSub
 Whenever a client sends a message to Web PubSub service, the service sends an HTTP request to an endpoint you specify. This mechanism is what your backend server uses to further process messages, for example, if you can persist messages in a database of choice. 
 
-As is with HTTP requests, Web PubSub service needs to know where to locate your application server. Since the backend application is now deployed to App Service, we get a publically accessible domain name for it. 
+As is with HTTP requests, Web PubSub service needs to know where to locate your application server. Since the backend application is now deployed to App Service, we get a publicly accessible domain name for it. 
 1. Show and store the value of `name` somewhere.
     ```azurecli-interactive
     az webapp config hostname list \
diff --git a/articles/azure-web-pubsub/howto-scale-manual-scale.md b/articles/azure-web-pubsub/howto-scale-manual-scale.md
@@ -19,7 +19,7 @@ The scale settings take a few minutes to apply. In rare cases, it may take aroun
 For information about the pricing and capacities of individual Web PubSub Service, see [Azure Web PubSub Service Pricing Details](https://azure.microsoft.com/pricing/details/web-pubsub/).  
 
 > [!NOTE]
-> Changing Web PubSub Service from **Free** tier to **Standard** or **Premium** tier or vice versa, the public service IP will be changed and it usually takes 30-60 minutes to propagate the change to DNS servers across the entire internet. Chaning tiers between  **Standard** and **Premium** will not change the public IP.
+> Changing Web PubSub Service from **Free** tier to **Standard** or **Premium** tier or vice versa, the public service IP will be changed and it usually takes 30-60 minutes to propagate the change to DNS servers across the entire internet. Changing tiers between  **Standard** and **Premium** will not change the public IP.
 > Your service might be unreachable before DNS gets updated. Generally it’s not recommended to change your pricing tier too often.
 
 
diff --git a/articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md b/articles/azure-web-pubsub/howto-web-pubsub-tunnel-tool.md
@@ -111,7 +111,7 @@ SET WebPubSubConnectionString=<your connection string>
       npm start
       ```
 
-1. Now switch to **Client** tab, select `Connect` to start a test WebSocket connection to the Azure Web PubSub service. You would see the traffic goes through Web PubSub to Local Tunnel and finally reaches the upstream server. The tunnel tab provides the details of the request and responses, providing you with a vivid view of what is requesting your upstream server and what is reponding from the upstream server.
+1. Now switch to **Client** tab, select `Connect` to start a test WebSocket connection to the Azure Web PubSub service. You would see the traffic goes through Web PubSub to Local Tunnel and finally reaches the upstream server. The tunnel tab provides the details of the request and responses, providing you with a vivid view of what is requesting your upstream server and what is responding from the upstream server.
 
    :::image type="content" alt-text="Screenshot of starting the test WebSocket connection and send message." source="media\howto-web-pubsub-tunnel-tool\overview-client.png" :::
 
diff --git a/articles/azure-web-pubsub/quickstarts-push-messages-from-server.md b/articles/azure-web-pubsub/quickstarts-push-messages-from-server.md
@@ -455,7 +455,7 @@ dotnet run $connection_string "myHub1" "Hello World"
 
 ```text
 # On the command shell used for running the "subscribe" program, you should see the received the messaged logged there. 
-# Try running the same "subscribe" program in multiple command shells, which simluates more than clients. 
+# Try running the same "subscribe" program in multiple command shells, which simulates more than clients. 
 # Try running the "publish" program several times and you see messages being delivered in real-time to all these clients.   
 Message received: Hello World
 ```
diff --git a/articles/azure-web-pubsub/reference-client-sdk-javascript.md b/articles/azure-web-pubsub/reference-client-sdk-javascript.md
@@ -43,7 +43,7 @@ A client uses `Client Access URL` to connect and authenticate with the service,
 As shown in the diagram, the client has the permissions to send messages to and join a specific group named **`group1`**. 
 
 ```js
-// Imports the client libray
+// Imports the client library
 const { WebPubSubClient } = require("@azure/web-pubsub-client");
 
 // Instantiates the client object
diff --git a/articles/azure-web-pubsub/socket-io-howto-integrate-web-app.md b/articles/azure-web-pubsub/socket-io-howto-integrate-web-app.md
@@ -90,7 +90,7 @@ Run the following command to get a copy of the application code.
     # bash
     zip -r app.zip *
 
-    # Poweshell
+    # Powershell
     ```
 
 1. Compress into a zip
diff --git a/articles/azure-web-pubsub/socket-io-serverless-function-binding.md b/articles/azure-web-pubsub/socket-io-serverless-function-binding.md
@@ -26,7 +26,7 @@ This article explains how to use Socket.IO serverless integrate with Azure Funct
 [Samples](https://github.com/Azure/azure-webpubsub/tree/main/sdk/webpubsub-socketio-extension/examples)
 
 > [!IMPORTANT]
-> Azure Function bindings can only integrate with Web PubSub for Socket.IO in Serverlesse Mode.
+> Azure Function bindings can only integrate with Web PubSub for Socket.IO in Serverless Mode.
 
 ### Authenticate and Connection String
 
diff --git a/articles/azure-web-pubsub/socketio-troubleshoot-common-issues.md b/articles/azure-web-pubsub/socketio-troubleshoot-common-issues.md
@@ -159,7 +159,7 @@ In this case, `package.json` could be:
 ```
 
 Then you should run `yarn install --flat`. It installs all the dependencies, but only allow one version for each package. On the first run, it prompts you to choose a single version for each package that is depended on at multiple version ranges. 
-For our case, it could prompt you to choose versions of `socket.io`, `enigne.io`, `engine.io-parser` and maybe more. Make sure their versions are matched with each other according to [the native implementation of `socket.io` package](https://github.com/socketio/socket.io/) and [`engine.io` package](https://github.com/socketio/engine.io/).
+For our case, it could prompt you to choose versions of `socket.io`, `engine.io`, `engine.io-parser` and maybe more. Make sure their versions are matched with each other according to [the native implementation of `socket.io` package](https://github.com/socketio/socket.io/) and [`engine.io` package](https://github.com/socketio/engine.io/).
 
 The final versions are added to your `package.json`` under a resolutions field.
 ```json
diff --git a/articles/azure-web-pubsub/tutorial-build-chat.md b/articles/azure-web-pubsub/tutorial-build-chat.md
@@ -18,7 +18,7 @@ In this tutorial, you learn how to:
 > [!div class="checklist"]
 > * Create a Web PubSub service instance
 > * Configure event handler settings for Azure Web PubSub
-> * Hanlde events in the app server and build a real-time chat app
+> * Handle events in the app server and build a real-time chat app
 
 [!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
@@ -904,7 +904,7 @@ Open `http://localhost:8080/index.html`. You can input your user name and start
 
 In previous sections, we demonstrate how to use [negotiate](#add-negotiate-endpoint) endpoint to return the Web PubSub service URL and the JWT access token for the clients to connect to Web PubSub service. In some cases, for example, edge devices that have limited resources, clients might prefer direct connect to Web PubSub resources. In such cases, you can configure `connect` event handler to lazy auth the clients, assign user ID to the clients, specify the groups the clients join once they connect, configure the permissions the clients have and WebSocket subprotocol as the WebSocket response to the client, etc. Details please refer to [connect event handler spec](./reference-cloud-events.md#connect). 
 
-Now let's use `connect` event handler to acheive the similar as what the [negotiate](#add-negotiate-endpoint) section does.
+Now let's use `connect` event handler to achieve the similar as what the [negotiate](#add-negotiate-endpoint) section does.
 
 ### Update hub settings
 
@@ -923,7 +923,7 @@ az webpubsub hub update -n "<your-unique-resource-name>" -g "myResourceGroup" --
 
 Now let's update upstream logic to handle connect event. We could also remove the negotiate endpoint now. 
 
-As similar to what we do in negotiate endpoint as demo purpose, we also read id from the query parameters. In connect event, the original client query is preserved in connect event requet body.
+As similar to what we do in negotiate endpoint as demo purpose, we also read id from the query parameters. In connect event, the original client query is preserved in connect event request body.
 
 # [C#](#tab/csharp)
 
diff --git a/articles/azure-web-pubsub/tutorial-pub-sub-messages.md b/articles/azure-web-pubsub/tutorial-pub-sub-messages.md
@@ -77,7 +77,7 @@ Each Web PubSub resource must have a unique name. Replace &lt;your-unique-resour
 az webpubsub create --resource-group myResourceGroup --name <your-unique-resource-name> --location EastUS --sku Free_F1
 ```
 
-The output of this command shows properties of the newly created resource. Take note of the following roperties:
+The output of this command shows properties of the newly created resource. Take note of the following properties:
 
 * **name**: The Web PubSub name you provided in the `--name` parameter above.
 * **hostName**: In the example, the host name is `<your-unique-resource-name>.webpubsub.azure.com/`.
diff --git a/articles/azure-web-pubsub/tutorial-serverless-notification.md b/articles/azure-web-pubsub/tutorial-serverless-notification.md
@@ -658,7 +658,7 @@ In this tutorial, you learn how to:
     And checking the running logs, you can visit your local host static page by visiting: `http://localhost:7071/api/index`.
     
     > [!NOTE]
-    > Some browers automatically redirect to `https` that leads to wrong url. Suggest to use `Edge` and double check the url if rendering is not success.
+    > Some browsers automatically redirect to `https` that leads to wrong url. Suggest to use `Edge` and double check the url if rendering is not success.
 
 ## Deploy Function App to Azure
 
diff --git a/articles/azure-web-pubsub/tutorial-subprotocol.md b/articles/azure-web-pubsub/tutorial-subprotocol.md
@@ -217,7 +217,7 @@ Now let's create a web application using the `json.webpubsub.azure.v1` subprotoc
     
     service = WebPubSubServiceClient.from_connection_string(sys.argv[1], hub='stream')
     
-    class Resquest(SimpleHTTPRequestHandler):
+    class Request(SimpleHTTPRequestHandler):
         def do_GET(self):
             if self.path == '/':
                 self.path = 'public/index.html'
@@ -238,7 +238,7 @@ Now let's create a web application using the `json.webpubsub.azure.v1` subprotoc
             print('Usage: python server.py <connection-string>')
             exit(1)
     
-        server = HTTPServer(('localhost', 8080), Resquest)
+        server = HTTPServer(('localhost', 8080), Request)
         print('server started')
         server.serve_forever()
     
