edits to faq

Author: ktoliver

articles/defender-for-cloud/faq-defender-for-servers.yml

@@ -17,17 +17,17 @@ sections:
       - question: |
           Can I enable Defender for Servers on a subset of machines in a subscription?
         answer: |
-          No. When you enable Microsoft Defender for Servers on an Azure subscription or on a connected AWS account or GCP project, all the connected machines are protected by Defender for Servers. This includes servers that don't have the Log Analytics agent and Azure Monitor agent installed.
+          No. When you enable Microsoft Defender for Servers on an Azure subscription or on a connected AWS account or GCP project, all connected machines are protected by Defender for Servers. This includes servers that don't have the Log Analytics agent and Azure Monitor agent installed.
 
       - question: |
           Can I get a discount if I already have a Microsoft Defender for Endpoint license?
         answer: |
-          If you already have a license for Microsoft Defender for Endpoint for Servers, you won't have to pay for that part of your Microsoft Defender for Servers Plan 2 license. 
+          If you already have a license for Microsoft Defender for Endpoint for your servers, you don't pay for that part of your Microsoft Defender for Servers Plan 2 license. 
 
           To request your discount, contact the Defender for Cloud support team through the Azure portal.
 
           - Provide the relevant workspace ID, region, and number of Defender for Endpoint for servers licenses that are applied for machines in the workspace.
-          - The discount will be effective starting from the approval date. The discount won't be retroactive.
+          - The discount is effective starting on the approval date. The discount isn't retroactive.
 
       - question: |
           What servers do I pay for in a subscription?
@@ -40,9 +40,9 @@ sections:
           --- | --- | ---
           Starting | VM starting up. | Not billed
           Running | Normal working state. | Billed
-          Stopping | Transitional, moves to Stopped state when finished. | Billed
+          Stopping | Transitional. Moves to Stopped state when finished. | Billed
           Stopped | VM shut down from within guest OS or by using PowerOff APIs. Hardware is still allocated, and the machine remains on the host. | Billed
-          Deallocating | Transitional, moves to Deallocated state when finished. | Not billed
+          Deallocating | Transitional. Moves to Deallocated state when finished. | Not billed
           Deallocated | VM stopped and removed from the host. | Not billed 
 
           **Azure Arc machines:**
@@ -51,14 +51,14 @@ sections:
           --- | --- | ---
           Connecting | Servers connected, but heartbeat not yet received. | Not billed
           Connected | Receiving regular heartbeat from Connected Machine agent. | Billed
-          Offline/Disconnected | No heartbeat received with 15-30 minutes. | Not billed
+          Offline/Disconnected | No heartbeat received in 15-30 minutes. | Not billed
           Expired | If disconnected for 45 days, status might change to Expired. | Not billed
 
   
       - question: |
-          Do I need to enable Defender for Servers on the subscription and on workspace?
+          Do I need to enable Defender for Servers on the subscription and on the workspace?
         answer: |
-          When you enable a Defender for Servers plan ay the subscription level, Defender for Cloud automatically enables the plan on your default workspaces. If you use a custom workspace, select the workspace to enable the plan. Here's more information:
+          When you enable a Defender for Servers plan at the subscription level, Defender for Cloud automatically enables the plan on your default workspaces. If you use a custom workspace, select the workspace to enable the plan. Here's more information:
           
           - If you turn on Defender for Servers for a subscription and for a connected custom workspace, you aren't charged for both. The system identifies unique VMs.
           - If you enable Defender for Servers on cross-subscription workspaces:
@@ -67,16 +67,16 @@ sections:
           
           
       - question: |
-          Iss the free allowance applied per workspace or per machine?
+          Is the free allowance applied per workspace or per machine?
         answer: |
           For every VM that's connected to the workspace, you get 500 MB of free data ingestion per day. The allowance is specifically for the security data types that are directly collected by Defender for Cloud.
           
-          This allowance is a daily rate that's averaged across all nodes. Your total daily free limit is equal to `[number of machines]` × 500 MB. Even if some machines send 100 MB and others send 800 MB, if the total doesn't exceed your total daily free limit, you aren't charged extra.
+          This allowance is a daily rate that's averaged across all nodes. Your total daily free limit is equal to \[number of machines\] × 500 MB. Even if some machines send 100 MB and others send 800 MB, if the total doesn't exceed your total daily free limit, you aren't charged extra.
 
       - question: |
           What data types are included in the daily allowance?
         answer: |
-          Defender for Cloud billing is closely tied to the billing for Log Analytics. [Microsoft Defender for Servers](defender-for-servers-introduction.md) provides a 500 MB per node per day allocation for machines against the following subset of [security data types](/azure/azure-monitor/reference/tables/tables-category#security):
+          Defender for Cloud billing is closely tied to the billing for Log Analytics. [Microsoft Defender for Servers](defender-for-servers-introduction.md) provides an allocation of 500 MB per node per day for machines against the following subset of [security data types](/azure/azure-monitor/reference/tables/tables-category#security):
 
           - [SecurityAlert](/azure/azure-monitor/reference/tables/securityalert)
           - [SecurityBaseline](/azure/azure-monitor/reference/tables/securitybaseline)
@@ -88,12 +88,12 @@ sections:
           - [ProtectionStatus](/azure/azure-monitor/reference/tables/protectionstatus)
           - [Update](/azure/azure-monitor/reference/tables/update) and [UpdateSummary](/azure/azure-monitor/reference/tables/updatesummary) when the Update Management solution isn't running in the workspace or solution targeting is enabled.
 
-          If the workspace is in the legacy per node pricing tier, the Defender for Cloud and Log Analytics allocations are combined and applied jointly to all billable ingested data.
+          If the workspace is in the legacy per-node pricing tier, the Defender for Cloud and Log Analytics allocations are combined and applied jointly to all billable ingested data.
 
       - question: |
           Am I charged for machines that don't have Log Analytics installed?
         answer: |
-          Yes. When you enable Microsoft Defender for Servers on an Azure subscription or a connected AWS account or GCP project, you're charged for all machines that are connected to your Azure subscription or your AWS account. The term *machines* includes Azure virtual machines, Azure Virtual Machine Scale Sets instances, and Azure Arc-enabled servers. Machines that don't have Log Analytics installed are covered by protections that don't depend on the Log Analytics agent.
+          Yes. When you enable Defender for Servers on an Azure subscription, connected AWS account, or connected GCP project, you're charged for all machines that are connected to your Azure subscription or your AWS account. The term *machines* includes Azure virtual machines, instances of Azure Virtual Machine Scale Sets, and Azure Arc-enabled servers. Machines that don't have Log Analytics installed are covered by protections that don't depend on the Log Analytics agent.
 
       - question: |
           If an agent reports to multiple workspaces, am I charged twice?