Merge pull request #246710 from alexbuckgit/alexbuckgit/docutune-autopr-20230729-210427-8387361-ignore-build

[BULK] DocuTune - Fix formatting issues (part 5)

Author: ttorble

articles/communication-services/tutorials/end-of-call-survey-tutorial.md

@@ -17,21 +17,21 @@ ms.subservice: calling
 
 # Use the End of Call Survey to collect user feedback
 
-> [!NOTE] 
+> [!NOTE]
 > End of Call Survey is currently supported only for our JavaScript / Web SDK.
 
 This tutorial shows you how to use the Azure Communication Services End of Call Survey for JavaScript / Web SDK.
 
 
 ## Prerequisites
 
--	An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
--	[Node.js](https://nodejs.org/) active Long Term Support(LTS) versions are recommended.
+- [Node.js](https://nodejs.org/) active Long Term Support(LTS) versions are recommended.
 
--	An active Communication Services resource. [Create a Communication Services resource](../quickstarts/create-communication-resource.md). Survey results are tied to single Communication Services resources.
--	An active Log Analytics Workspace, also known as Azure Monitor Logs. See [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md).
--	To conduct a survey with custom questions using free form text, you need an [App Insight resource](../../azure-monitor/app/create-workspace-resource.md#create-a-workspace-based-resource).
+- An active Communication Services resource. [Create a Communication Services resource](../quickstarts/create-communication-resource.md). Survey results are tied to single Communication Services resources.
+- An active Log Analytics Workspace, also known as Azure Monitor Logs. See [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md).
+- To conduct a survey with custom questions using free form text, you need an [App Insight resource](../../azure-monitor/app/create-workspace-resource.md#create-a-workspace-based-resource).
 
 
 > [!IMPORTANT]
@@ -44,7 +44,7 @@ The End of Call Survey feature should be used after the call ends. Users can rat
 
 The following code snips show an example of one-to-one call. After the end of the call, your application can show a survey UI and once the user chooses a rating, your application should call the feature API to submit the survey with the user choices.
 
-We encourage you to use the default rating scale. However, you can submit a survey with custom rating scale. You can check out the [sample application](https://github.com/Azure-Samples/communication-services-web-calling-tutorial/blob/main/Project/src/MakeCall/CallSurvey.js) for the sample API usage.  
+We encourage you to use the default rating scale. However, you can submit a survey with custom rating scale. You can check out the [sample application](https://github.com/Azure-Samples/communication-services-web-calling-tutorial/blob/main/Project/src/MakeCall/CallSurvey.js) for the sample API usage.
 
 
 ### Rate call only - no custom scale
@@ -85,7 +85,7 @@ call.feature(Features.CallSurvey).submitSurvey({
 ```
 
 ### Handle errors the SDK can send
- ``` javascript 
+ ``` javascript
 call.feature(Features.CallSurvey).submitSurvey({
     overallRating: { score: 3 }
 }).catch((e) => console.log('error when submitting survey: ' + e))
@@ -95,7 +95,7 @@ call.feature(Features.CallSurvey).submitSurvey({
 
 ## Find different types of errors
 
- 
+
 
 ### Failures while submitting survey:
 
@@ -126,7 +126,7 @@ The API will return the following error messages if data validation fails or the
 ```
 
 - One 408 (timeout) when event discarded:
- 
+
 ```
 { message: "Please try again.", code: 408 }
 ```
@@ -137,15 +137,15 @@ The API will return the following error messages if data validation fails or the
 ### Default survey API configuration
 
 | API Rating Categories | Cutoff Value* | Input Range | Comments |
-| ----------- | ----------- | -------- | -------- | 
+| ----------- | ----------- | -------- | -------- |
 | Overall Call | 2 | 1 - 5 | Surveys a calling participant’s overall quality experience on a scale of 1-5. A response of 1 indicates an imperfect call experience and 5 indicates a perfect call. The cutoff value of 2 means that a customer response of 1 or 2 indicates a less than perfect call experience.  |
 | Audio |   2 | 1 - 5  | A response of 1 indicates an imperfect audio experience and 5 indicates no audio issues were experienced.  |
 | Video |   2 | 1 - 5 |  A response of 1 indicates an imperfect video experience and 5 indicates no video issues were experienced. |
 | Screenshare | 2 | 1 - 5   |  A response of 1 indicates an imperfect screen share experience and 5 indicates no screen share issues were experienced. |
 
 
 
-> [!NOTE] 
+> [!NOTE]
 >A question’s indicated cutoff value in the API is the threshold that Microsoft uses when analyzing your survey data. When you customize the cutoff value or Input Range, Microsoft analyzes your survey data according to your customization.
 
 
@@ -167,17 +167,17 @@ about their audio, video, and screen share experience. You can also
 customize input ranges to suit your needs. The default input range is 1
 to 5 for Overall Call, Audio, Video, and
 Screenshare. However, each API value can be customized from a minimum of
-0 to maximum of 100. 
+0 to maximum of 100.
 
 ### Customization examples
 
 
 | API Rating Categories | Cutoff Value* | Input Range |
-| ----------- | ----------- | -------- |  
-| Overall Call   |   0 - 100    |  0 - 100     |     
-|  Audio  |   0 - 100    |   0 - 100    |     
-|  Video  |    0 - 100   |   0 - 100    |     
-|  Screenshare  |   0 - 100    |   0 - 100    |     
+| ----------- | ----------- | -------- |
+| Overall Call   |   0 - 100    |  0 - 100     |
+|  Audio  |   0 - 100    |   0 - 100    |
+|  Video  |    0 - 100   |   0 - 100    |
+|  Screenshare  |   0 - 100    |   0 - 100    |
 
    > [!NOTE]
    > A question’s indicated cutoff value in the API is the threshold that Microsoft uses when analyzing your survey data. When you customize the cutoff value or Input Range, Microsoft analyzes your survey data according to your customization.
@@ -189,11 +189,11 @@ In addition to using the End of Call Survey API you can create your own survey q
 -  Build a UI in your application that will serve custom questions to the user and gather their input, lets assume that your application gathered responses as a string in the `improvementSuggestion` variable
 
 -  Submit survey results to ACS and send user response using App Insights:
-	``` javascript
-	currentCall.feature(SDK.Features.CallSurvey).submitSurvey(survey).then(res => {
-	// `improvementSuggesstion` contains custom, user response
+    ``` javascript
+    currentCall.feature(SDK.Features.CallSurvey).submitSurvey(survey).then(res => {
+    // `improvementSuggesstion` contains custom, user response
         if (improvementSuggestion !== '') {
-        	appInsights.trackEvent({
+            appInsights.trackEvent({
                     name: "CallSurvey", properties: {
                         // Survey ID to correlate the survey
                         id: res.id,
@@ -202,9 +202,9 @@ In addition to using the End of Call Survey API you can create your own survey q
                     }
                 });
          }
-	});
-	appInsights.flush();
-	```
+    });
+    appInsights.flush();
+    ```
 User responses that were sent using AppInsights are available under your App Insights workspace. You can use [Workbooks](../../update-center/workbooks.md) to query between multiple resources, correlate call ratings and custom survey data. Steps to correlate the call ratings and custom survey data:
 -  Create new [Workbooks](../../update-center/workbooks.md) (Your ACS Resource -> Monitoring -> Workbooks -> New) and query Call Survey data from your ACS resource.
 -  Add new query (+Add -> Add query)
@@ -234,34 +234,33 @@ User responses that were sent using AppInsights are available under your App Ins
 
 > [!IMPORTANT]
 > You must enable a Diagnostic Setting in Azure Monitor to send the log data of your surveys to a Log Analytics workspace, Event Hubs, or an Azure storage account to receive and analyze your survey data. If you do not send survey data to one of these options your survey data will not be stored and will be lost. To enable these logs for your Communications Services, see: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md)
-	
 
 ### View survey data with a Log Analytics workspace
 
-You need to enable a Log Analytics Workspace to both store the log data of your surveys and access survey results. To enable these logs for your Communications Service, see: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md). 
+You need to enable a Log Analytics Workspace to both store the log data of your surveys and access survey results. To enable these logs for your Communications Service, see: [End of Call Survey Logs](../concepts/analytics/logs/end-of-call-survey-logs.md).
 
--	You can also integrate your Log Analytics workspace with Power BI, see: [Integrate Log Analytics with Power BI](../../../articles/azure-monitor/logs/log-powerbi.md).
+- You can also integrate your Log Analytics workspace with Power BI, see: [Integrate Log Analytics with Power BI](../../../articles/azure-monitor/logs/log-powerbi.md).
 
 ## Best practices
 Here are our recommended survey flows and suggested question prompts for consideration. Your development can use our recommendation or use customized question prompts and flows for your visual interface.
 
 **Question 1:** How did the users perceive their overall call quality experience?
-We recommend you start the survey by only asking about the participants’ overall quality. If you separate the first and second questions, it helps to only collect responses to Audio, Video, and Screen Share issues if a survey participant indicates they experienced call quality issues. 
+We recommend you start the survey by only asking about the participants’ overall quality. If you separate the first and second questions, it helps to only collect responses to Audio, Video, and Screen Share issues if a survey participant indicates they experienced call quality issues.
 
 
--	Suggested prompt: “How was the call quality?” 
--	API Question Values: Overall Call
+- Suggested prompt: “How was the call quality?”
+- API Question Values: Overall Call
 
 **Question 2:** Did the user perceive any Audio, Video, or Screen Sharing issues in the call?
 If a survey participant responded to Question 1 with a score at or below the cutoff value for the overall call, then present the second question.
 
--	Suggested prompt: “What could have been better?” 
--	API Question Values: Audio, Video, and Screenshare 
+- Suggested prompt: “What could have been better?”
+- API Question Values: Audio, Video, and Screenshare
 
 ### Surveying Guidelines
--	Avoid survey burnout, don’t survey all call participants.
--	The order of your questions matters. We recommend you randomize the sequence of optional tags in Question 2 in case respondents focus most of their feedback on the first prompt they visually see.
--	Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.
+- Avoid survey burnout, don’t survey all call participants.
+- The order of your questions matters. We recommend you randomize the sequence of optional tags in Question 2 in case respondents focus most of their feedback on the first prompt they visually see.
+- Consider using surveys for separate Azure Communication Services Resources in controlled experiments to identify release impacts.
 
 
 ## Next steps
@@ -270,6 +269,6 @@ If a survey participant responded to Question 1 with a score at or below the cut
 
 - Learn more about the End of Call Survey, see: [End of Call Survey overview](../concepts/voice-video-calling/end-of-call-survey-concept.md)
 
--	Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
+- Learn how to use the Log Analytics workspace, see: [Log Analytics Tutorial](../../../articles/azure-monitor/logs/log-analytics-tutorial.md)
 
--	Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)
+- Create your own queries in Log Analytics, see: [Get Started Queries](../../../articles/azure-monitor/logs/get-started-queries.md)

articles/cosmos-db/cassandra/troubleshoot-nohostavailable-exception.md

@@ -12,15 +12,15 @@ ms.custom: ignite-2022
 ---
 
 # Troubleshoot NoHostAvailableException and NoNodeAvailableException
-NoHostAvailableException is a top-level wrapper exception with many possible causes and inner exceptions, many of which can be client-related. This exception tends to occur if there are some issues with the cluster or connection settings, or if one or more Cassandra nodes are unavailable. 
+NoHostAvailableException is a top-level wrapper exception with many possible causes and inner exceptions, many of which can be client-related. This exception tends to occur if there are some issues with the cluster or connection settings, or if one or more Cassandra nodes are unavailable.
 
 This article explores possible reasons for this exception, and it discusses specific details about the client driver that's being used.
 
 ## Driver settings
 One of the most common causes of NoHostAvailableException is the default driver settings. We recommend that you use the [settings](#code-sample) listed at the end of this article. Here is some explanatory information:
 
 - The default value of the connections per host is 1, which we don't recommend for Azure Cosmos DB. We do recommend a minimum value of 10. Although more aggregated Request Units (RU) are provided, increase the connection count. The general guideline is 10 connections per 200,000 RU.
-- Use the Azure Cosmos DB retry policy to handle intermittent throttling responses. For more information, see the Azure Cosmos DB extension libraries: 
+- Use the Azure Cosmos DB retry policy to handle intermittent throttling responses. For more information, see the Azure Cosmos DB extension libraries:
    - [Driver 3 extension library](https://github.com/Azure/azure-cosmos-cassandra-extensions)
    - [Driver 4 extension library](https://github.com/Azure/azure-cosmos-cassandra-extensions/tree/release/java-driver-4/1.0.1)
 - For multi-region accounts, use the Azure Cosmos DB load-balancing policy in the extension.
@@ -54,7 +54,7 @@ Apply one of the following options:
 
 ### All hosts tried for query failed
 When the client is set to connect to a region other than the primary contact point region, during the initial few seconds at startup, you'll get one of the following exception messages:
- 
+
 - For Java driver 3: `Exception in thread "main" com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried)at [email protected]/com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:83)`
 
 - For Java driver 4: `No node was available to execute the query`
@@ -76,29 +76,29 @@ Use CosmosLoadBalancingPolicy in [Java driver 3](https://github.com/Azure/azure-
     // https://docs.datastax.com/en/developer/java-driver/3.6/manual/socket_options/
     SocketOptions socketOptions = new SocketOptions()
         .setReadTimeoutMillis(90000); // default 12000
-    
+
     // connection pooling options (default values are 1s)
     // https://docs.datastax.com/en/developer/java-driver/3.6/manual/pooling/
     PoolingOptions poolingOptions = new PoolingOptions()
         .setCoreConnectionsPerHost(HostDistance.LOCAL, 10) // default 1
         .setMaxConnectionsPerHost(HostDistance.LOCAL, 10) // default 1
         .setCoreConnectionsPerHost(HostDistance.REMOTE, 10) // default 1
         .setMaxConnectionsPerHost(HostDistance.REMOTE, 10); //default 1
-    
+
     // Azure Cosmos DB load balancing policy
     String Region = "West US";
     CosmosLoadBalancingPolicy cosmosLoadBalancingPolicy = CosmosLoadBalancingPolicy.builder()
         .withWriteDC(Region)
         .withReadDC(Region)
         .build();
-    
+
     // Azure Cosmos DB retry policy
     CosmosRetryPolicy retryPolicy = CosmosRetryPolicy.builder()
         .withFixedBackOffTimeInMillis(5000)
         .withGrowingBackOffTimeInMillis(1000)
         .withMaxRetryCount(5)
         .build();
-    
+
     Cluster cluster = Cluster.builder()
         .addContactPoint(EndPoint).withPort(10350)
         .withCredentials(UserName, Password)
@@ -115,7 +115,7 @@ Use CosmosLoadBalancingPolicy in [Java driver 3](https://github.com/Azure/azure-
     // driver configurations
     // https://docs.datastax.com/en/developer/java-driver/4.6/manual/core/configuration/
     ProgrammaticDriverConfigLoaderBuilder configBuilder = DriverConfigLoader.programmaticBuilder();
-        
+
     // connection settings
     // https://docs.datastax.com/en/developer/java-driver/4.6/manual/core/pooling/
     configBuilder
@@ -124,7 +124,7 @@ Use CosmosLoadBalancingPolicy in [Java driver 3](https://github.com/Azure/azure-
         .withDuration(DefaultDriverOption.REQUEST_TIMEOUT, Duration.ofSeconds(90)) // default 2
         .withClass(DefaultDriverOption.RECONNECTION_POLICY_CLASS, ConstantReconnectionPolicy.class) // default ExponentialReconnectionPolicy
         .withBoolean(DefaultDriverOption.METADATA_TOKEN_MAP_ENABLED, false); // default true
-        
+
     // load balancing settings
     // https://docs.datastax.com/en/developer/java-driver/4.6/manual/core/load_balancing/
     String Region = "West US";
@@ -138,7 +138,7 @@ Use CosmosLoadBalancingPolicy in [Java driver 3](https://github.com/Azure/azure-
     // retry policy
     // https://docs.datastax.com/en/developer/java-driver/4.6/manual/core/retries/
     configBuilder
-    	.withClass(DefaultDriverOption.RETRY_POLICY_CLASS, CosmosRetryPolicy.class)
+        .withClass(DefaultDriverOption.RETRY_POLICY_CLASS, CosmosRetryPolicy.class)
         .withInt(CosmosRetryPolicyOption.FIXED_BACKOFF_TIME, 5000)
         .withInt(CosmosRetryPolicyOption.GROWING_BACKOFF_TIME, 1000)
         .withInt(CosmosRetryPolicyOption.MAX_RETRIES, 5);

articles/cosmos-db/postgresql/reference-metadata.md

@@ -411,7 +411,7 @@ function.
 
 -   Setting a node capacity exception by hostname pattern:
 
-	```postgresql
+    ```postgresql
     CREATE FUNCTION v2_node_double_capacity(nodeidarg int)
         RETURNS boolean AS $$
         SELECT