Fix some error

Author: zackliu

articles/azure-web-pubsub/socket-io-serverless-overview.md

@@ -21,15 +21,15 @@ With the increasing adoption of serverless computing, we're introducing a new mo
 |Architecture|Use persistent connection for both servers and clients | Clients use persistent connections but servers use RESTful APIs and webhook event handlers in a stateless manner|
 |SDKs and Languages| Official JavaScript server SDKs together with [Extension library for Web PubSub for Socket.IO SDK](https://www.npmjs.com/package/@azure/web-pubsub-socket.io) is required; All compatible clients|No mandatory SDKs or languages. Use [Socket.IO Function binding](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.WebPubSubForSocketIO) to simplified integrate with Azure Function; All compatible clients|
 |Network Accessibility| The server doesn't need to expose network access as it proactively makes connection to the service|The server needs to expose network access to the service|
-|Feature supports|Most features are supported except some unsupported features: [Unsupported server APIs of Socket.IO](./socketio-supported-server-apis.md)|See list of supported features: [Supported functionality and RESTful APIs](./socketio-serverless-protocol.md#supported-functionality-and-restful-apis)|
+|Feature supports|Most features are supported except some unsupported features: [Unsupported server APIs of Socket.IO](./socket-io-supported-server-apis.md)|See list of supported features: [Supported functionality and RESTful APIs](./socketio-serverless-protocol.md#supported-functionality-and-restful-apis)|
 
 ## Next steps
 
 This article provides you with an overview of the Serverless Mode of Web PubSub for Socket.IO.
 
 > [!div class="nextstepaction"]
-> [Tutorial: Build chat app with Azure Function in Serverless Mode](./socketio-serverless-tutorial.md)
+> [Tutorial: Build chat app with Azure Function in Serverless Mode](./socket-io-serverless-tutorial.md)
 >
-> [Serverless Protocols](./socketio-serverless-protocol.md)
+> [Serverless Protocols](./socket-io-serverless-protocol.md)
 >
-> [Serverless Function Binding](./socketio-serverless-function-binding.md)
+> [Serverless Function Binding](./socket-io-serverless-function-binding.md)

articles/azure-web-pubsub/socket-io-serverless-protocol.md

@@ -11,7 +11,7 @@ ms.topic: how-to
 
 # Socket.IO Serverless Mode Specification (Preview)
 
-This document describes the details of serverless support. As the Socket.IO supports including the serverless supports highly depends on the Web PubSub service's existing interface, it introduces many complicated transforming and mapping. For most users, we suggest using Azure Function bindings together with Serverless Mode. You can walk through a tutorial [Tutorial: Build chat app with Azure Function in Serverless Mode](./socketio-serverless-tutorial.md)
+This document describes the details of serverless support. As the Socket.IO supports including the serverless supports highly depends on the Web PubSub service's existing interface, it introduces many complicated transforming and mapping. For most users, we suggest using Azure Function bindings together with Serverless Mode. You can walk through a tutorial [Tutorial: Build chat app with Azure Function in Serverless Mode](./socket-io-serverless-tutorial.md)
 
 ## Lifetime workflow
 

articles/azure-web-pubsub/socket-io-serverless-quickstart.md

@@ -88,7 +88,7 @@ We need to do two steps to deploy the sample app.
     func azure functionapp publish <function-app-name>
     ```
 
-- Configure the Web PubSub for Socket.IO to add a hub setting which can send request to the Function App. As per the limitation of Function App's Webhook provider, you need to get an extension key populated by Function. Get more details in [Trigger Binding](./socketio-serverless-function-binding.md#trigger-binding). And as we use identity-based authentication, in the hub settings, you need to assign the target resource, which is the clientId of the Service Principal created before.
+- Configure the Web PubSub for Socket.IO to add a hub setting which can send request to the Function App. As per the limitation of Function App's Webhook provider, you need to get an extension key populated by Function. Get more details in [Trigger Binding](./socket-io-serverless-function-binding.md#trigger-binding). And as we use identity-based authentication, in the hub settings, you need to assign the target resource, which is the clientId of the Service Principal created before.
 
     ```bash
     code=$(az functionapp keys list -g <resource-group> -n <function-name> --query systemKeys.socketio_extension -o tsv)
@@ -109,4 +109,4 @@ https://<function-endpoint>/api/index
 Next, you can follow the tutorial to write the app step by step:
 
 > [!div class="nextstepaction"]
-> [Tutorial: Build chat app with Azure Function in Serverless Mode](./socketio-serverless-tutorial.md)
+> [Tutorial: Build chat app with Azure Function in Serverless Mode](./socket-io-serverless-tutorial.md)

articles/azure-web-pubsub/socket-io-serverless-tutorial-python.md

@@ -47,24 +47,24 @@ You should follow the steps to initiate a local Azure Function project.
     func init SocketIOProject --worker-runtime python
     ```
 
-This command creates a Python-based Function project. And enter the folder `SocketIOProject` to run the following commands.
+    This command creates a Python-based Function project. And enter the folder `SocketIOProject` to run the following commands.
 
 1. Currently, the Function Bundle doesn't include Socket.IO Function Binding, so you need to manually add the package.
 
     1. To eliminate the function bundle reference, edit the host.json file and remove the following lines.
 
-    ```json
-    "extensionBundle": {
-        "id": "Microsoft.Azure.Functions.ExtensionBundle",
-        "version": "[4.*, 5.0.0)"
-    }
-    ```
+        ```json
+        "extensionBundle": {
+            "id": "Microsoft.Azure.Functions.ExtensionBundle",
+            "version": "[4.*, 5.0.0)"
+        }
+        ```
 
     1. Run the command:
 
-    ```bash
-    func extensions install -p Microsoft.Azure.WebJobs.Extensions.WebPubSubForSocketIO -v 1.0.0-beta.4
-    ```
+        ```bash
+        func extensions install -p Microsoft.Azure.WebJobs.Extensions.WebPubSubForSocketIO -v 1.0.0-beta.4
+        ```
 
 1. Replace the content in `function_app.py` with the codes:
 
@@ -109,18 +109,18 @@ This command creates a Python-based Function project. And enter the folder `Sock
             return func.HttpResponse(f.read(), mimetype='text/html')
     ```
 
-Here's the explanation of these functions:
+    Here's the explanation of these functions:
 
-- `publish_data`: This function updates the NASDAQ index every second with a random change and broadcasts it to connected clients with Socket.IO Output Binding.
+    - `publish_data`: This function updates the NASDAQ index every second with a random change and broadcasts it to connected clients with Socket.IO Output Binding.
 
-- `negotiate`: This function response a negotiation result to the client.
+    - `negotiate`: This function response a negotiation result to the client.
 
-- `index`: This function returns a static HTML page.
+    - `index`: This function returns a static HTML page.
 
 
-Then add a `index.html` file
+    Then add a `index.html` file
 
-Create the index.html file with the content:
+    Create the index.html file with the content:
 
     ```html
     <!DOCTYPE html>
@@ -234,28 +234,28 @@ Create the index.html file with the content:
     </html>
     ```
 
-The key part in the `index.html`:
+    The key part in the `index.html`:
 
-    ```javascript
-    async function init() {
-        const negotiateResponse = await fetch(`/api/negotiate`);
-        if (!negotiateResponse.ok) {
-            console.log("Failed to negotiate, status code =", negotiateResponse.status);
-            return;
+        ```javascript
+        async function init() {
+            const negotiateResponse = await fetch(`/api/negotiate`);
+            if (!negotiateResponse.ok) {
+                console.log("Failed to negotiate, status code =", negotiateResponse.status);
+                return;
+            }
+            const negotiateJson = await negotiateResponse.json();
+            socket = io(negotiateJson.endpoint, {
+                path: negotiateJson.path,
+                query: { access_token: negotiateJson.token}
+            });
+
+            socket.on('update', (index) => {
+                updateIndexCore(index);
+            });
         }
-        const negotiateJson = await negotiateResponse.json();
-        socket = io(negotiateJson.endpoint, {
-            path: negotiateJson.path,
-            query: { access_token: negotiateJson.token}
-        });
-
-        socket.on('update', (index) => {
-            updateIndexCore(index);
-        });
-    }
-    ```
+        ```
 
-It first negotiates with the Function App to get the Uri and the path to the service. And register a callback to update index.
+    It first negotiates with the Function App to get the Uri and the path to the service. And register a callback to update index.
 
 ## How to run the App locally
 
@@ -288,27 +288,27 @@ Azure Functions requires a storage account to work even running in local. Choose
 
 Update the project to use the Azure Blob Storage connection string.
 
-    ```bash
-    func settings add AzureWebJobsStorage "<storage-connection-string>"
-    ```
+```bash
+func settings add AzureWebJobsStorage "<storage-connection-string>"
+```
 
 ---
 
 ### Set up configuration of Web PubSub for Socket.IO
 
 Add connection string to the Function APP:
 
-    ```bash
-    func settings add WebPubSubForSocketIOConnectionString "<connection string>"
-    ```
+```bash
+func settings add WebPubSubForSocketIOConnectionString "<connection string>"
+```
 
 ### Run Sample App
 
 After tunnel tool is running, you can run the Function App locally:
 
-    ```bash
-    func start
-    ```
+```bash
+func start
+```
 
 And visit the webpage at `http://localhost:7071/api/index`. 
 
@@ -318,4 +318,4 @@ And visit the webpage at `http://localhost:7071/api/index`.
 Next, you can try to use Bicep to deploy the app online with identity-based authentication:
 
 > [!div class="nextstepaction"]
-> [Quickstart: Build chat app with Azure Function in Socket.IO Serverless Mode](./socketio-serverless-quickstart.md)
+> [Quickstart: Build chat app with Azure Function in Socket.IO Serverless Mode](./socket-io-serverless-quickstart.md)

articles/azure-web-pubsub/socket-io-serverless-tutorial.md

@@ -47,7 +47,7 @@ You should follow the steps to initiate a local Azure Function project.
     func init SocketIOProject --worker-runtime javascript --model V4
     ```
 
-This command creates a JavaScript project. And enter the folder `SocketIOProject` to run the following commands.
+    This command creates a JavaScript project. And enter the folder `SocketIOProject` to run the following commands.
 
 1. Currently, the Function Bundle doesn't include Socket.IO Function Binding, so you need to manually add the package.
 
@@ -58,7 +58,7 @@ This command creates a JavaScript project. And enter the folder `SocketIOProject
             "id": "Microsoft.Azure.Functions.ExtensionBundle",
             "version": "[4.*, 5.0.0)"
         }
-    ```
+        ```
 
     1. Run the command:
 
@@ -72,7 +72,7 @@ This command creates a JavaScript project. And enter the folder `SocketIOProject
     func new --template "Http Trigger" --name negotiate
     ```
 
-Open the file in `src/functions/negotiate.js` and replace with the following code:
+    Open the file in `src/functions/negotiate.js` and replace with the following code:
 
     ```js
     const { app, input } = require('@azure/functions');
@@ -98,15 +98,15 @@ Open the file in `src/functions/negotiate.js` and replace with the following cod
     });
     ```
 
-This step creates a function `negotiate` with Http Trigger and `SocketIONegotiation` output binding, which means you can use an Http call to trigger the function and return a negotiation result that generated by `SocketIONegotiation` binding.
+    This step creates a function `negotiate` with Http Trigger and `SocketIONegotiation` output binding, which means you can use an Http call to trigger the function and return a negotiation result that generated by `SocketIONegotiation` binding.
 
 1. Create a function for handing messages.
 
     ```bash
     func new --template "Http Trigger" --name message
     ```
 
-Open the file `src/functions/message.js` and replace with the following code:
+    Open the file `src/functions/message.js` and replace with the following code:
 
     ```js
     const { app, output, trigger } = require('@azure/functions');
@@ -141,7 +141,7 @@ Open the file `src/functions/message.js` and replace with the following code:
     });
     ```
 
-This uses `SocketIOTrigger` to get triggered by a Socket.IO client message and use `SocketIO` binding to broadcast messages to namespace.
+    This uses `SocketIOTrigger` to get triggered by a Socket.IO client message and use `SocketIO` binding to broadcast messages to namespace.
 
 1. Create a function to return an index html for visiting.
 
@@ -261,47 +261,47 @@ Azure Functions requires a storage account to work even running in local. Choose
 
 1. Install the Azurite
 
-    ```bash
-    npm install -g azurite
-    ```
+```bash
+npm install -g azurite
+```
 
 1. Start the Azurite storage emulator:
 
-    ```bash
-    azurite -l azurite -d azurite\debug.log
-    ```
+```bash
+azurite -l azurite -d azurite\debug.log
+```
 
 1. Make sure the `AzureWebJobsStorage` in *local.settings.json* set to `UseDevelopmentStorage=true`.
 
 #### [Azure Blob Storage](#tab/azure-blob-storage) 
 
 Update the project to use the Azure Blob Storage connection string.
 
-    ```bash
-    func settings add AzureWebJobsStorage "<storage-connection-string>"
-    ```
+```bash
+func settings add AzureWebJobsStorage "<storage-connection-string>"
+```
 
 ---
 
 ### Set up configuration of Web PubSub for Socket.IO
 
 1. Add connection string to the Function APP:
 
-    ```bash
-    func settings add WebPubSubForSocketIOConnectionString "<connection string>"
-    ```
+```bash
+func settings add WebPubSubForSocketIOConnectionString "<connection string>"
+```
 
 1. Add hub settings to the Web PubSub for Socket.IO
 
-    ```bash
-    az webpubsub hub create -n <resource name> -g <resource group> --hub-name hub --event-handler url-template="tunnel:///runtime/webhooks/socketio" user-event-pattern="*"
-    ```
+```bash
+az webpubsub hub create -n <resource name> -g <resource group> --hub-name hub --event-handler url-template="tunnel:///runtime/webhooks/socketio" user-event-pattern="*"
+```
 
 The connection string can be obtained by the Azure CLI command
 
-    ```azcli
-    az webpubsub key show -g <resource group> -n <resource name>
-    ```
+```azcli
+az webpubsub key show -g <resource group> -n <resource name>
+```
 
 The output contains `primaryConnectionString` and `secondaryConnectionString`, and either is available.
 
@@ -323,15 +323,15 @@ An easiest way to achieve it's to use [Tunnel Tool](../azure-web-pubsub/howto-we
     awps-tunnel run --hub hub --connection "<connection string>" --upstream http://127.0.0.1:7071
     ```
 
-The `--upstream` is the url that local Azure Function exposes. The port may be different and you can check the output when starting the function in the next step.
+    The `--upstream` is the url that local Azure Function exposes. The port may be different and you can check the output when starting the function in the next step.
 
 ### Run Sample App
 
 After tunnel tool is running, you can run the Function App locally:
 
-    ```bash
-    func start
-    ```
+```bash
+func start
+```
 
 And visit the webpage at `http://localhost:7071/api/index`. 
 
@@ -341,4 +341,4 @@ And visit the webpage at `http://localhost:7071/api/index`.
 Next, you can try to use Bicep to deploy the app online with identity-based authentication:
 
 > [!div class="nextstepaction"]
-> [Quickstart: Build chat app with Azure Function in Socket.IO Serverless Mode](./socketio-serverless-quickstart.md)
+> [Quickstart: Build chat app with Azure Function in Socket.IO Serverless Mode](./socket-io-serverless-quickstart.md)