Skip to content

Commit cd04064

Browse files
Verified the procedure, reviewed, and fixed all the issues.
1 parent c575fc5 commit cd04064

1 file changed

Lines changed: 14 additions & 14 deletions

File tree

articles/azure-web-pubsub/tutorial-serverless-notification.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ In this tutorial, you learn how to:
6969

7070
## Create and run the functions locally
7171

72-
1. Make sure you have [Azure Functions Core Tools](https://github.com/Azure/azure-functions-core-tools#installing) installed. And then create an empty directory for the project. Run command under this working directory.
72+
1. Make sure you have [Azure Functions Core Tools](https://github.com/Azure/azure-functions-core-tools#installing) installed. Now, create an empty directory for the project. Run command under this working directory. Use one of the given options below.
7373

7474
# [JavaScript](#tab/javascript)
7575
```bash
@@ -91,10 +91,10 @@ In this tutorial, you learn how to:
9191
func init --worker-runtime python
9292
```
9393

94-
2. Install `Microsoft.Azure.WebJobs.Extensions.WebPubSub`.
94+
2. Follow the steps to install `Microsoft.Azure.WebJobs.Extensions.WebPubSub`.
9595

9696
# [JavaScript](#tab/javascript)
97-
Update `host.json`'s extensionBundle to version _3.3.0_ or later to get Web PubSub support.
97+
Update `host.json`'s extensionBundle to version _3.3.0_ or later to get Web PubSub support. For updating the `host.json`, open the file in editor, and then replace the existing version extensionBundle to version _3.3.0_ or later.
9898
```json
9999
{
100100
"version": "2.0",
@@ -117,7 +117,7 @@ In this tutorial, you learn how to:
117117
118118
119119
# [Python](#tab/python)
120-
Update `host.json`'s extensionBundle to version _3.3.0_ or later to get Web PubSub support.
120+
Update `host.json`'s extensionBundle to version _3.3.0_ or later to get Web PubSub support. For updating the `host.json`, open the file in editor, and then replace the existing version extensionBundle to version _3.3.0_ or later.
121121
```json
122122
{
123123
"version": "2.0",
@@ -133,7 +133,7 @@ In this tutorial, you learn how to:
133133
func new -n index -t HttpTrigger
134134
```
135135
# [JavaScript](#tab/javascript)
136-
- Update `index/function.json` and copy following json codes.
136+
- Create a folder index and make a new file fuction.json inside the folder. Update `index/function.json` and copy following json codes.
137137
```json
138138
{
139139
"bindings": [
@@ -155,7 +155,7 @@ In this tutorial, you learn how to:
155155
]
156156
}
157157
```
158-
- Update `index/index.js` and copy following codes.
158+
- In the index folder, create a new file index.js. Update `index/index.js` and copy following codes.
159159
```js
160160
var fs = require('fs');
161161
var path = require('path');
@@ -276,7 +276,7 @@ In this tutorial, you learn how to:
276276
]
277277
}
278278
```
279-
- Update `negotiate/index.js` and copy following codes.
279+
- Create a folder negotiate and update `negotiate/index.js` and copy following codes.
280280
```js
281281
module.exports = function (context, req, connection) {
282282
context.res = { body: connection };
@@ -317,7 +317,7 @@ In this tutorial, you learn how to:
317317
```
318318
319319
# [Python](#tab/python)
320-
- Update `negotiate/function.json` and copy following json codes.
320+
- Create a folder negotiate and update `negotiate/function.json` and copy following json codes.
321321
```json
322322
{
323323
"scriptFile": "__init__.py",
@@ -358,7 +358,7 @@ In this tutorial, you learn how to:
358358
func new -n notification -t TimerTrigger
359359
```
360360
# [JavaScript](#tab/javascript)
361-
- Update `notification/function.json` and copy following json codes.
361+
- Create a folder notification and update `notification/function.json` and copy following json codes.
362362
```json
363363
{
364364
"bindings": [
@@ -377,7 +377,7 @@ In this tutorial, you learn how to:
377377
]
378378
}
379379
```
380-
- Update `notification/index.js` and copy following codes.
380+
- Create a folder notification and update `notification/index.js` and copy following codes.
381381
```js
382382
module.exports = function (context, myTimer) {
383383
context.bindings.actions = {
@@ -443,7 +443,7 @@ In this tutorial, you learn how to:
443443
```
444444
445445
# [Python](#tab/python)
446-
- Update `notification/function.json` and copy following json codes.
446+
- Create a folder notification and update `notification/function.json` and copy following json codes.
447447
```json
448448
{
449449
"scriptFile": "__init__.py",
@@ -565,7 +565,7 @@ Before you can deploy your function code to Azure, you need to create three reso
565565
566566
Use the following commands to create these items.
567567
568-
1. If you haven't done so already, sign in to Azure:
568+
1. Sign in to Azure:
569569
570570
```azurecli
571571
az login
@@ -612,7 +612,7 @@ Use the following commands to create these items.
612612
613613
1. Deploy the function project to Azure:
614614
615-
After you have successfully created your function app in Azure, you're now ready to deploy your local functions project by using the [func azure functionapp publish](../azure-functions/functions-run-local.md) command.
615+
Once you create your function app in Azure, you're now ready to deploy your local functions project by using the [func azure functionapp publish](../azure-functions/functions-run-local.md) command.
616616
617617
```bash
618618
func azure functionapp publish <FUNCIONAPP_NAME> --publish-local-settings
@@ -627,7 +627,7 @@ Use the following commands to create these items.
627627
628628
If you're not going to continue to use this app, delete all resources created by this doc with the following steps so you don't incur any charges:
629629
630-
1. In the Azure portal, select **Resource groups** on the far left, and then select the resource group you created. You may use the search box to find the resource group by its name instead.
630+
1. In the Azure portal, select **Resource groups** on the far left, and then select the resource group you created. Use the search box to find the resource group by its name instead.
631631
632632
1. In the window that opens, select the resource group, and then select **Delete resource group**.
633633

0 commit comments

Comments
 (0)