Merge branch 'more-laa' of https://github.com/batamig/azure-docs-pr into more-laa

Author: batamig

articles/sentinel/data-connectors/cisco-software-defined-wan.md

@@ -82,7 +82,7 @@ Azure Monitor Agent will be used to collect the syslog data into Microsoft senti
 9. Select Next: Destination.
 10. Select Add destination and add Destination type, Subscription and Account or namespace.
 11. Select Add data source. Select Next: Review + create.
-12. Select Create. Wait for 20 minutes. In Microsoft Sentinel or Azure Monitor, verify that the Azure Monitor Agent is running on your VM.
+12. Select Create. Wait for 20 minutes. In Microsoft Sentinel or Azure Monitor, verify that the Azure Monitor agent is running on your VM.
 [Reference link](/azure/sentinel/forward-syslog-monitor-agent)
 
 2. Steps to ingest Netflow data to Microsoft sentinel

articles/sentinel/data-connectors/windows-firewall-events-via-ama.md

@@ -11,7 +11,7 @@ ms.collection: sentinel-data-connector
 
 # Windows Firewall Events via AMA (Preview) connector for Microsoft Sentinel
 
-Windows Firewall is a Microsoft Windows application that filters information coming to your system from the internet and blocking potentially harmful programs. The firewall software blocks most programs from communicating through the firewall. To stream your Windows Firewall application logs collected from your machines, use the Azure Monitor Agent (AMA) to stream those logs to the Microsoft Sentinel workspace. 
+Windows Firewall is a Microsoft Windows application that filters information coming to your system from the internet and blocking potentially harmful programs. The firewall software blocks most programs from communicating through the firewall. To stream your Windows Firewall application logs collected from your machines, use the Azure Monitor agent (AMA) to stream those logs to the Microsoft Sentinel workspace. 
 
 A configured data collection endpoint (DCE) is required to be linked with the data collection rule (DCR) created for the AMA to collect logs. For this connector, a DCE is automatically created in the same region as the workspace. If you already use a DCE stored in the same region, it's possible to change the default created DCE and use your existing one through the API. DCEs can be located in your resources with **SentinelDCE** prefix in the resource name.
 

articles/sentinel/entities-reference.md

@@ -153,7 +153,7 @@ The following section contains a more in-depth look at the full schemas of each
 | **NetBiosName** | String | The host name (pre-Windows 2000). |
 | **IoTDevice** | Entity ([IoT Device](#iot-device)) | The IoT Device entity (if this host represents an IoT Device). |
 | **AzureID** | String | The Azure resource ID of the VM, if known. |
-| **OMSAgentID** | String | The OMS agent ID, if the host has a [legacy OMS agent](/azure/azure-monitor/agents/log-analytics-agent) installed. |
+| **OMSAgentID** | String | The OMS agent ID, if the host has OMS agent installed. |
 | **OSFamily** | Enum? | One of the following values: <li>Linux<li>Windows<li>Android<li>IOS<li>Mac |
 | **OSVersion** | String | A free-text representation of the operating system.<br>This field is meant to hold specific versions the are more fine-grained than OSFamily, or future values not supported by OSFamily enumeration. |
 | **IsDomainJoined** | Bool | Indicates whether this host belongs to a domain. |

articles/sentinel/sap/collect-sap-hana-audit-logs.md

@@ -36,9 +36,9 @@ For more information, see [Ingest syslog and CEF messages to Microsoft Sentinel
 
 1. Sign into your HANA database operating system as a user with sudo privileges.
 
-1. Install an agent on your machine and confirm that your machine is connected. For more information, see [Azure Monitor Agent](/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal).
+1. Install an agent on your machine and confirm that your machine is connected. For more information, see [Install and manage Azure Monitor Agent](/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal).
 
-1. Configure your agent to collect Syslog data. For more information, see [Azure Monitor Agent](/azure/azure-monitor/agents/data-collection-syslog).
+1. Configure your agent to collect Syslog data. For more information, see [Collect Syslog events with Azure Monitor Agent](/azure/azure-monitor/agents/data-collection-syslog).
 
     > [!TIP]
     > Because the facilities where HANA database events are saved can change between different distributions, we recommend that you add all facilities. Check them against your Syslog logs, and then remove any that aren't relevant.