Fixing links

Author: JimDaly

powerapps-docs/developer/common-data-service/org-service/use-executeAsync.md

@@ -15,22 +15,22 @@ search.app:
   - PowerApps
   - D365CE
 ---
-# Use ExecuteAsync to execute messages asynchronously  
+# Use ExecuteAsync to execute messages asynchronously
 
-Except for two, all data operations using the SDK assemblies are synchronous. 
+Except for two, all data operations using the SDK assembly request classes are synchronous.
 
-Importing a solution is one operation which can require considerable resources, so there is an option to execute this operation asynchronously using the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> class. The <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromote> performs similar resource intensive operations.
+Importing a solution is one operation which can require considerable resources, so there is an option to execute this operation asynchronously using the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> request class. The <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest> request class performs similar resource intensive operations.
 
 Importing a solution asynchronously improves system performance by postponing message execution until some later time when the server load may be less. Interactive users do not have to wait for the target message to execute before they can continue. This is especially useful when importing solutions which may take a few minutes or more to execute.  
 
 > [!NOTE]
->  <xref:Microsoft.Crm.Sdk.Messages.ImportSolutionRequest> and <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromote> the only messages can be used with the `ExecuteAsync` message.  
+>  <xref:Microsoft.Crm.Sdk.Messages.ImportSolutionRequest> and <xref:Microsoft.Crm.Sdk.Messages.DeleteAndPromoteRequest> are the only request classes that can be used with the `ExecuteAsync` message.
   
-Use the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> message to execute a message asynchronously. You configure the request and pass the request instance as an argument to <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*>. <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncResponse> returns with the ID of the asynchronous job. You can (optionally) query the job using the ID to find out its current state.  
+Use the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncRequest> request class to execute a message asynchronously. You configure the request and pass the request instance as an argument to <xref:Microsoft.Xrm.Sdk.IOrganizationService>.<xref:Microsoft.Xrm.Sdk.IOrganizationService.Execute*>. <xref:Microsoft.Xrm.Sdk.Messages.ExecuteAsyncResponse> returns with the ID of the asynchronous job. You can (optionally) query the job using the ID to find out its current state.  
 
-You can use the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> message queue multiple solutions to be imported asynchronously.To do this, add one or more `ExecuteAsync` message requests to an `ExecuteMultiple` message request. Due to throttling restrictions that improve overall system performance, only one message running asynchronously is allowed to execute at a time for each organization.
+You can use the <xref:Microsoft.Xrm.Sdk.Messages.ExecuteMultipleRequest> request class to queue multiple solutions to be imported asynchronously.To do this, add one or more `ExecuteAsync` message requests to an `ExecuteMultiple` message request. Due to throttling restrictions that improve overall system performance, only one message running asynchronously is allowed to execute at a time for each organization.
 
-For more information about the `ExecuteMultiple` message request, see [Execute multiple requests using the Organization service](execute-multiple-requests.md).  
+For more information about the `ExecuteMultiple` message, see [Execute multiple requests using the Organization service](execute-multiple-requests.md).  
 
 ## Example