docs: Apply Acrolinx clarity improvements to loading-remote file

Author: VanMSFT

docs/integration-services/run-manage-packages-programmatically/loading-and-running-a-remote-package-programmatically.md

@@ -17,15 +17,15 @@ helpviewer_keywords:
 
 [!INCLUDE[sqlserver-ssis](../../includes/applies-to-version/sqlserver-ssis.md)]
 
-  To run remote packages from a local computer that doesn't have [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed, start the packages so that they run on the remote computer on which [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is installed. You do this by having the local computer use [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent, a Web service, or a remote component to start the packages on the remote computer. If you try to start the remote packages directly from the local computer, the packages load onto and try to run from the local computer. If the local computer doesn't have [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed, the packages don't run.  
+  To run remote packages from a local computer that doesn't have [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed, start the packages so that they run on the remote computer where [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is installed. To accomplish this goal, have the local computer use [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent, a Web service, or a remote component to start the packages on the remote computer. If you try to start the remote packages directly from the local computer, the packages load onto and try to run from the local computer. If the local computer doesn't have [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed, the packages don't run.  
 
 > [!NOTE]  
->  You can't run packages outside [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] on a client computer that doesn't have [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed, and the terms of your [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] licensing might not let you install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] on additional computers. [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is a server component and isn't redistributable to client computers.  
+>  You can't run packages outside [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)] on a client computer unless [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is installed. The terms of your [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] licensing might not let you install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] on other computers. [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is a server component and isn't redistributable to client computers.  
   
- Alternately, you can run a remote package from a local computer that has [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed. For more information, see [Loading and Running a Local Package Programmatically](../../integration-services/run-manage-packages-programmatically/loading-and-running-a-local-package-programmatically.md).  
+ Alternatively, you can run a remote package from a local computer that has [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] installed. For more information, see [Loading and Running a Local Package Programmatically](../../integration-services/run-manage-packages-programmatically/loading-and-running-a-local-package-programmatically.md).  
 
 ##  <a name="top"></a> Running a Remote Package on the Remote Computer  
- As mentioned above, there are multiple ways in which you can run a remote package on a remote server:  
+ There are multiple ways to run a remote package on a remote server:  
 
 - [Use SQL Server Agent to run the remote package programmatically](#agent)  
 
@@ -137,7 +137,7 @@ namespace LaunchSSISPackageAgent_CS
 ```  
 
 ###  <a name="service"></a> Using a Web Service or Remote Component to Run a Remote Package Programmatically  
- The previous solution for running packages programmatically on the server doesn't require any custom code on the server. However, you might prefer a solution that doesn't rely on SQL Server Agent to execute packages. The following example demonstrates a Web service that can be created on the server to start [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages locally, and a test application that can be used to call the Web service from a client computer. If you prefer to create a remote component instead of a Web service, you can use the same code logic with very few changes in a remote component. However a remote component might require more extensive configuration than a Web service.  
+ The previous solution for running packages programmatically on the server doesn't require any custom code on the server. However, you might prefer a solution that doesn't rely on SQL Server Agent to execute packages. The following example shows how to create a Web service on the server to start [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] packages locally, and a test application to call the Web service from a client computer. If you prefer to create a remote component instead of a Web service, you can use the same code logic with few changes in a remote component. However a remote component might require more extensive configuration than a Web service.  
 
 > [!IMPORTANT]  
 >  With its default settings for authentication and authorization, a Web service generally doesn't have sufficient permissions to access SQL Server or the file system to load and execute packages. You might have to assign appropriate permissions to the Web service by configuring its authentication and authorization settings in the **web.config** file and assigning database and file system permissions as appropriate. A complete discussion of Web, database, and file system permissions is beyond the scope of this topic.  
@@ -149,7 +149,7 @@ namespace LaunchSSISPackageAgent_CS
  The following code samples show how to create and test the Web service.  
 
 #### Creating the Web Service  
- An [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] package can be loaded directly from a file, directly from SQL Server, or from the SSIS Package Store, which manages package storage in both SQL Server and special file system folders. This sample supports all the available options by using a **Select Case** or **switch** construct to select the appropriate syntax for starting the package and to concatenate the input arguments appropriately. The LaunchPackage Web service method returns the result of package execution as an integer instead of a <xref:Microsoft.SqlServer.Dts.Runtime.DTSExecResult> value so that client computers don't require a reference to any [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] assemblies.  
+ You can load an [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] package directly from a file, from SQL Server, or from the SSIS Package Store. The SSIS Package Store manages package storage in both SQL Server and special file system folders. This sample supports all the available options by using a **Select Case** or **switch** construct to select the appropriate syntax for starting the package and to concatenate the input arguments appropriately. The LaunchPackage Web service method returns the result of package execution as an integer instead of a <xref:Microsoft.SqlServer.Dts.Runtime.DTSExecResult> value so that client computers don't require a reference to any [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] assemblies.  
 
 ###### To create a Web service to run packages on the server programmatically