Apply suggestions from code review

Co-authored-by: Scott Addie <10702007+scottaddie@users.noreply.github.com>

docs/azure/sdk/protocol-convenience-methods.md

@@ -12,15 +12,15 @@ The Azure SDK client libraries provide an interface to Azure services by transla
 
 ## Understand protocol and convenience methods
 
-The Azure SDK for .NET client libraries can expose two different categories of methods to make requests to an Azure service:
+An Azure SDK for .NET client library can expose two different categories of methods to make requests to an Azure service:
 
 - **Protocol methods** provide a thin wrapper around the underlying REST API for a corresponding Azure service. These methods map primitive input parameters to HTTP request values and return a raw HTTP response object.
 
 - **Convenience methods** provide a convenience layer over the lower-level protocol layer to add support for the .NET type system and other benefits. Convenience methods accept primitives or .NET model types as parameters and map them to the body of an underlying REST API request. These methods also handle various details of request and response management to allow developers to focus on sending and receiving data objects, instead of lower-level concerns.
 
 ### Azure SDK client library dependency patterns
 
-Protocol and convenience methods implement slightly different patterns based on the underlying package dependency chain of the respective library. The Azure SDK for .NET client libraries depend on one of two different core libraries:
+Protocol and convenience methods implement slightly different patterns based on the underlying package dependency chain of the respective library. An Azure SDK for .NET client library depends on one of two different foundational libraries:
 
 - [**Azure.Core**](/dotnet/api/overview/azure/core-readme) provides shared primitives, abstractions, and helpers for building modern Azure SDK client libraries. These libraries follow the [Azure SDK Design Guidelines for .NET](https://azure.github.io/azure-sdk/dotnet_introduction.html) and use package names and namespaces prefixed with *Azure*, such as [`Azure.Storage.Blobs`](/dotnet/api/overview/azure/storage.blobs-readme).
 
@@ -46,7 +46,7 @@ The coding patterns and types used by client library protocol and convenience me
 
 ### Libraries that depend on Azure.Core
 
-Many Azure SDK client libraries depend on the `Azure.Core` library. For example, the [`Azure.AI.ContentSafety`](/dotnet/api/overview/azure/ai.contentsafety-readme) library depends on the `Azure.Core` library and provides a `ContentSafetyClient` class that exposes both protocol and convenience methods.
+Azure SDK client libraries adhering to the [latest design guidelines](https://azure.github.io/azure-sdk/general_introduction.html) depend on the `Azure.Core` library. For example, the [`Azure.AI.ContentSafety`](/dotnet/api/overview/azure/ai.contentsafety-readme) library depends on the `Azure.Core` library and provides a `ContentSafetyClient` class that exposes both protocol and convenience methods.
 
 ### [Convenience method](#tab/convenience-methods)
 
@@ -106,7 +106,7 @@ The preceding code demonstrates the following `System.ClientModel` protocol meth
 - Calls the `GetRawResponse` method to access the response data.
 
 > [!NOTE]
-> The preceding code configures the `ClientErrorBehaviors.NoThrow` for the `RequestOptions`. This option prevents non-success service responses status codes from throwing an exception, which means the app code should manually handle the response status code checks.
+> The preceding code configures the [ClientErrorBehaviors.NoThrow](/dotnet/api/system.clientmodel.primitives.clienterrorbehaviors) behavior for the `RequestOptions`. This option prevents non-success service responses status codes from throwing an exception, which means the app code should manually handle the response status code checks.
 
 ---
 

docs/azure/sdk/snippets/protocol-convenience-methods/AzureCoreConvenience/Program.cs

@@ -2,7 +2,7 @@
 using Azure.Identity;
 
 // Create the client
-var safetyClient = new ContentSafetyClient(
+ContentSafetyClient safetyClient = new(
     new Uri("https://contentsafetyai.cognitiveservices.azure.com/"),
     new DefaultAzureCredential());
 

docs/azure/sdk/snippets/protocol-convenience-methods/AzureCoreProtocol/Program.cs

@@ -4,7 +4,7 @@
 using Azure.Identity;
 
 // Create the client
-var safetyClient = new ContentSafetyClient(
+ContentSafetyClient safetyClient = new(
     new Uri("https://contentsafetyai.cognitiveservices.azure.com/"),
     new DefaultAzureCredential());
 
@@ -17,9 +17,12 @@
 // Call the protocol method
 Response response = safetyClient.AnalyzeText(
     prompt, 
-    new RequestContext() { ErrorOptions = ErrorOptions.NoThrow});
+    new RequestContext()
+    {
+        ErrorOptions = ErrorOptions.NoThrow
+    });
 
-// Any response code other than 200 from Azure ContentSafety AnalyzeText REST API is not considered a success response
+// Any non-200 response code from Azure AI Content Safety AnalyzeText REST API isn't considered a success response.
 // See REST API details at https://azure-ai-content-safety-api-docs.developer.azure-api.net/api-details#api=content-safety-service-2023-10-01&operation=TextOperations_AnalyzeText
 if (response.Status != 200) 
 {

docs/azure/sdk/snippets/protocol-convenience-methods/SCMConvenience/Program.cs

@@ -8,7 +8,7 @@
 
 // Call the convenience method
 ChatCompletion completion
-    = chatClient.CompleteChat("What is Azure?");
+    = chatClient.CompleteChat("What is Microsoft Azure?");
 
 // Display the results
 Console.WriteLine($"{completion.Role}: {completion.Content}");