Fix typo and tweak wording

Author: linda33wj

articles/purview/register-scan-sap-bw.md

@@ -26,46 +26,44 @@ The supported SAP BW versions are 7.3 to 7.5. SAP BW4/HANA is not supported.
 
 When scanning SAP BW source, Azure Purview supports extracting technical metadata including:
 
-    - Instance
-    - InfoArea
-    - InfoSet
-    - InfoSet query
-    - Classic InfoSet
-    - InfoObject including unit of measurement, time characteristic, navigation attribute, data packet characteristic, currency, characteristic, field, key figure
-    - Data store object (DSO)
-    - Aggregation level
-    - Open hub destination
-    - Query including the query condition
-    - Query view
-    - HybridProvider
-    - MultiProvider
-    - InfoCube
-    - Aggregate
-    - Dimension
-    - Time dimension
-
-    Info area, Info object, DSO (does not support ADSO yet), aggregation level, info set, infot set query. Classic info set, open hub destination, query, query view, hybrid provider, multi provider, info cube, aggregate cube.
+- Instance
+- InfoArea
+- InfoSet
+- InfoSet query
+- Classic InfoSet
+- InfoObject including unit of measurement, time characteristic, navigation attribute, data packet characteristic, currency, characteristic, field, key figure
+- Data store object (DSO)
+- Aggregation level
+- Open hub destination
+- Query including the query condition
+- Query view
+- HybridProvider
+- MultiProvider
+- InfoCube
+- Aggregate
+- Dimension
+- Time dimension
 
 ## Prerequisites
 
 * An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 * An active [Azure Purview resource](create-catalog-portal.md).
 
-* You will need to be a Data Source Administrator and Data Reader to register a source and manage it in the Azure Purview Studio. See our [Azure Purview Permissions page](catalog-permissions.md) for details.
+* You need Data Source Administrator and Data Reader permissions to register a source and manage it in Azure Purview Studio. For more information about permissions, see [Access control in Azure Purview](catalog-permissions.md).
 
 * Set up the latest [self-hosted integration runtime](https://www.microsoft.com/download/details.aspx?id=39717). For more information, see [the create and configure a self-hosted integration runtime guide](manage-integration-runtimes.md).
 
 * Ensure [JDK 11](https://www.oracle.com/java/technologies/javase-jdk11-downloads.html) is installed on the machine where the self-hosted integration runtime is installed.
 
 * Ensure Visual C++ Redistributable for Visual Studio 2012 Update 4 is installed on the self-hosted integration runtime machine. If you don't have this update installed, [you can download it here](https://www.microsoft.com/download/details.aspx?id=30679).
 
-* The connector reads metadata from SAP using the [SAP Java Connector (JCo)](https://support.sap.com/en/product/connectors/jco.html) 3.0 API. Make sure the Java Connector is available on your machine where self-hosted integration runtime is installed. Make sure that you are using the correct JCo distribution for your environment. Make sure the **sapjco3.jar** and **sapjco3.dll** files are available.
+* The connector reads metadata from SAP using the [SAP Java Connector (JCo)](https://support.sap.com/en/product/connectors/jco.html) 3.0 API. Make sure the Java Connector is available on your machine where self-hosted integration runtime is installed. Make sure that you use the correct JCo distribution for your environment, and the **sapjco3.jar** and **sapjco3.dll** files are available.
 
     > [!Note]
     > The driver should be accessible to all accounts in the machine. Don't put it in a path under user account.
 
-* Deploy the metadata extraction ABAP function module on the SAP server by following the steps mentioned in [ABAP functions deployment guide](abap-functions-deployment-guide.md). You will need an ABAP developer account to create the RFC function module on the SAP server. The user account requires sufficient permissions to connect to the SAP server and execute the following RFC function modules:
+* Deploy the metadata extraction ABAP function module on the SAP server by following the steps mentioned in [ABAP functions deployment guide](abap-functions-deployment-guide.md). You need an ABAP developer account to create the RFC function module on the SAP server. The user account requires sufficient permissions to connect to the SAP server and execute the following RFC function modules:
 
     * STFC_CONNECTION (check connectivity)
     * RFC_SYSTEM_INFO (check system information)
@@ -93,7 +91,7 @@ On the **Register sources (SAP BW)** screen, do the following:
 
 1. Enter the **Application server** name to connect to SAP BW source. It can also be an IP address of the SAP application server host.
 
-1. Enter the SAP **System number**. This is a integer between 0 and 99.
+1. Enter the SAP **System number**. It's an integer between 0 and 99.
 
 1. Select a collection or create a new one (Optional).
 
@@ -107,7 +105,7 @@ Follow the steps below to scan SAP BW to automatically identify assets and class
 
 ### Create and run scan
 
-1. In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it is not set up, use the steps mentioned [here](./manage-integration-runtimes.md) to create a self-hosted integration runtime.
+1. In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it isn't set up, use the steps mentioned [here](./manage-integration-runtimes.md) to create a self-hosted integration runtime.
 
 1. Navigate to **Sources**
 
@@ -127,7 +125,7 @@ Follow the steps below to scan SAP BW to automatically identify assets and class
         * Provide a user ID to connect to SAP server in the User name input field.
         * Store the user password used to connect to SAP server in the secret key.
 
-    1. **Client ID**: Enter the SAP Client ID. This is a three-digit numeric number from 000 to 999.
+    1. **Client ID**: Enter the SAP Client ID. It's a three-digit numeric number from 000 to 999.
 
     1. **JCo library path**: The directory path where the JCo libraries are located.