Skip to content

Commit b623db3

Browse files
authored
Merge pull request #215992 from alexbuckgit/alexbuckgit/docutune-autopr-20221026-151459-1873386
[BULK] Fix code block formatting issues (part 6)
2 parents fddb0b0 + 88d89a2 commit b623db3

File tree

7 files changed

+332
-343
lines changed

7 files changed

+332
-343
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -477,4 +477,4 @@ Open function host index page: `http://localhost:7071/api/index` to view the rea
477477
> [Azure Web PubSub bindings for Azure Functions](./reference-functions-bindings.md)
478478
479479
> [!div class="nextstepaction"]
480-
> [Explore more Azure Web PubSub samples](https://github.com/Azure/azure-webpubsub/tree/main/samples)
480+
> [Explore more Azure Web PubSub samples](https://github.com/Azure/azure-webpubsub/tree/main/samples)

articles/cloud-services/cloud-services-configure-ssl-certificate-portal.md

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -43,12 +43,9 @@ Next, you must include information about the certificate in your service definit
4343
## Step 2: Modify the service definition and configuration files
4444
Your application must be configured to use the certificate, and an HTTPS endpoint must be added. As a result, the service definition and service configuration files need to be updated.
4545

46-
1. In your development environment, open the service definition file
47-
(CSDEF), add a **Certificates** section within the **WebRole**
48-
section, and include the following information about the
49-
certificate (and intermediate certificates):
46+
1. In your development environment, open the service definition file (CSDEF), add a **Certificates** section within the **WebRole** section, and include the following information about the certificate (and intermediate certificates):
5047

51-
```xml
48+
```xml
5249
<WebRole name="CertificateTesting" vmsize="Small">
5350
...
5451
<Certificates>
@@ -84,7 +81,7 @@ Your application must be configured to use the certificate, and an HTTPS endpoin
8481
2. In your service definition file, add an **InputEndpoint** element
8582
within the **Endpoints** section to enable HTTPS:
8683

87-
```xml
84+
```xml
8885
<WebRole name="CertificateTesting" vmsize="Small">
8986
...
9087
<Endpoints>
@@ -99,7 +96,7 @@ Your application must be configured to use the certificate, and an HTTPS endpoin
9996
the **Sites** section. This element adds an HTTPS binding to map the
10097
endpoint to your site:
10198

102-
```xml
99+
```xml
103100
<WebRole name="CertificateTesting" vmsize="Small">
104101
...
105102
<Sites>
@@ -120,7 +117,7 @@ Your application must be configured to use the certificate, and an HTTPS endpoin
120117
value with that of your certificate. The following code sample provides
121118
details of the **Certificates** section, except for the thumbprint value.
122119

123-
```xml
120+
```xml
124121
<Role name="Deployment">
125122
...
126123
<Certificates>
@@ -188,6 +185,3 @@ connect to it using HTTPS.
188185
* Learn how to [deploy a cloud service](cloud-services-how-to-create-deploy-portal.md).
189186
* Configure a [custom domain name](cloud-services-custom-domain-name-portal.md).
190187
* [Manage your cloud service](cloud-services-how-to-manage-portal.md).
191-
192-
193-

articles/cloud-services/cloud-services-nodejs-chat-app-socketio.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ The following steps create the cloud service project that will host the Socket.I
3636
1. From the **Start Menu** or **Start Screen**, search for **Windows PowerShell**. Finally, right-click **Windows PowerShell** and select **Run As Administrator**.
3737

3838
![Azure PowerShell icon][powershell-menu]
39+
3940
2. Create a directory called **c:\\node**.
4041

4142
```powershell
@@ -60,20 +61,23 @@ The following steps create the cloud service project that will host the Socket.I
6061
![The output of the new-azureservice and add-azurenodeworkerrolecmdlets](./media/cloud-services-nodejs-chat-app-socketio/socketio-1.png)
6162
6263
## Download the Chat Example
64+
6365
For this project, we will use the chat example from the [Socket.IO
6466
GitHub repository]. Perform the following steps to download the example
6567
and add it to the project you previously created.
6668
6769
1. Create a local copy of the repository by using the **Clone** button. You may also use the **ZIP** button to download the project.
6870
6971
![A browser window viewing https://github.com/LearnBoost/socket.io/tree/master/examples/chat, with the ZIP download icon highlighted](./media/cloud-services-nodejs-chat-app-socketio/socketio-22.png)
72+
7073
2. Navigate the directory structure of the local repository until you arrive at the **examples\\chat**
7174
directory. Copy the contents of this directory to the
7275
**C:\\node\\chatapp\\WorkerRole1** directory created earlier.
7376
7477
![Explorer, displaying the contents of the examples\\chat directory extracted from the archive][chat-contents]
7578
7679
The highlighted items in the screenshot above are the files copied from the **examples\\chat** directory
80+
7781
3. In the **C:\\node\\chatapp\\WorkerRole1** directory, delete the **server.js** file, and then rename the **app.js** file to **server.js**. This removes the default **server.js** file created previously by the **Add-AzureNodeWorkerRole** cmdlet and replaces it with the application file from the chat example.
7882
7983
### Modify Server.js and Install Modules
@@ -82,6 +86,7 @@ make some minor modifications. Perform the following steps to the
8286
server.js file:
8387
8488
1. Open the **server.js** file in Visual Studio or any text editor.
89+
8590
2. Find the **Module dependencies** section at the beginning of server.js and change the line containing **sio = require('..//..//lib//socket.io')** to **sio = require('socket.io')** as shown below:
8691
8792
```js
@@ -120,6 +125,7 @@ Azure emulator:
120125
following:
121126
122127
![The output of the npm install command][The-output-of-the-npm-install-command]
128+
123129
2. Since this example was originally a part of the Socket.IO GitHub
124130
repository, and directly referenced the Socket.IO library by
125131
relative path, Socket.IO was not referenced in the package.json
@@ -130,6 +136,7 @@ Azure emulator:
130136
```
131137
132138
### Test and Deploy
139+
133140
1. Launch the emulator by issuing the following command:
134141
135142
```powershell
@@ -143,21 +150,22 @@ Azure emulator:
143150
> Reinstall AzureAuthoringTools v 2.7.1 and AzureComputeEmulator v 2.7 - make sure that version matches.
144151
145152
2. Open a browser and navigate to `http://127.0.0.1`.
153+
146154
3. When the browser window opens, enter a nickname and then hit enter.
147155
This will allow you to post messages as a specific nickname. To test
148156
multi-user functionality, open additional browser windows using the
149157
same URL and enter different nicknames.
150158
151159
![Two browser windows displaying chat messages from User1 and User2](./media/cloud-services-nodejs-chat-app-socketio/socketio-8.png)
160+
152161
4. After testing the application, stop the emulator by issuing the
153162
following command:
154163
155164
```powershell
156165
PS C:\node\chatapp\WorkerRole1> Stop-AzureEmulator
157166
```
158167
159-
5. To deploy the application to Azure, use the
160-
**Publish-AzureServiceProject** cmdlet. For example:
168+
5. To deploy the application to Azure, use the **Publish-AzureServiceProject** cmdlet. For example:
161169
162170
```powershell
163171
PS C:\node\chatapp\WorkerRole1> Publish-AzureServiceProject -ServiceName mychatapp -Location "East US" -Launch
@@ -167,25 +175,20 @@ Azure emulator:
167175
> Be sure to use a unique name, otherwise the publish process will fail. After the deployment has completed, the browser will open and navigate to the deployed service.
168176
>
169177
> If you receive an error stating that the provided subscription name doesn't exist in the imported publish profile, you must download and import the publishing profile for your subscription before deploying to Azure. See the **Deploying the Application to Azure** section of [Build and deploy a Node.js application to an Azure Cloud Service](./cloud-services-nodejs-develop-deploy-app.md)
170-
>
171-
>
172178
173179
![A browser window displaying the service hosted on Azure][completed-app]
174180
175181
> [!NOTE]
176182
> If you receive an error stating that the provided subscription name doesn't exist in the imported publish profile, you must download and import the publishing profile for your subscription before deploying to Azure. See the **Deploying the Application to Azure** section of [Build and deploy a Node.js application to an Azure Cloud Service](./cloud-services-nodejs-develop-deploy-app.md)
177-
>
178-
>
179183
180184
Your application is now running on Azure, and can relay chat
181185
messages between different clients using Socket.IO.
182186
183187
> [!NOTE]
184188
> For simplicity, this sample is limited to chatting between users connected to the same instance. This means that if the cloud service creates two worker role instances, users will only be able to chat with others connected to the same worker role instance. To scale the application to work with multiple role instances, you could use a technology like Service Bus to share the Socket.IO store state across instances. For examples, see the Service Bus Queues and Topics usage samples in the [Azure SDK for Node.js GitHub repository](https://github.com/WindowsAzure/azure-sdk-for-node).
185-
>
186-
>
187189
188190
## Next steps
191+
189192
In this tutorial you learned how to create a basic chat application hosted in an Azure Cloud Service. To learn how to host this application in an Azure Website, see [Build a Node.js Chat Application with Socket.IO on an Azure Web Site][chatwebsite].
190193
191194
For more information, see also the [Node.js Developer Center](/azure/developer/javascript/).
@@ -206,7 +209,6 @@ For more information, see also the [Node.js Developer Center](/azure/developer/j
206209
[chat example]: https://github.com/LearnBoost/socket.io/tree/master/examples/chat
207210
[chat-example-view]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-22.png
208211
209-
210212
[chat-contents]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-5.png
211213
[The-output-of-the-npm-install-command]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-7.png
212-
[The output of the Publish-AzureService command]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-9.png
214+
[The output of the Publish-AzureService command]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-9.png

articles/cognitive-services/Bing-Image-Search/includes/quickstarts/image-search-client-library-java.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ Install the Bing Image Search client library dependencies by using Maven, Gradle
5353

5454
1. Using `bingImages().search()`, send the HTTP request containing the search query. Save the response as a `ImagesModel`.
5555

56-
```java
56+
```java
5757
ImagesModel imageResults = client.bingImages().search()
5858
.withQuery(searchTerm)
5959
.withMarket("en-us")
@@ -91,4 +91,4 @@ else {
9191
* [Try an online interactive demo](https://azure.microsoft.com/services/cognitive-services/bing-image-search-api/)
9292
* [Java samples for the Azure Cognitive Services SDK](https://github.com/Azure-Samples/cognitive-services-java-sdk-samples)
9393
* [Azure Cognitive Services Documentation](../../../index.yml)
94-
* [Bing Image Search API reference](/rest/api/cognitiveservices-bingsearch/bing-images-api-v7-reference)
94+
* [Bing Image Search API reference](/rest/api/cognitiveservices-bingsearch/bing-images-api-v7-reference)

0 commit comments

Comments
 (0)