Acrolinx edits

Author: Karthigasree

articles/migrate/concepts-assessment-calculation.md

@@ -154,7 +154,7 @@ To calculate readiness, the assessment reviews the server properties and operati
 
 For an Azure VM Assessment, the assessment reviews the following properties of an on-premises VM to determine whether it can run on Azure VMs.
 
-Property | Details | Azure readiness status
+**Property** | **Details** | **Azure readiness status**
 --- | --- | ---
 **Boot type** | Azure supports UEFI boot type for OS mentioned [here](./common-questions-server-migration.md#which-operating-systems-are-supported-for-migration-of-uefi-based-machines-to-azure)| Not ready if the boot type is UEFI and Operating System running on the VM is: Windows Server 2003/Windows Server 2003 R2/Windows Server 2008/Windows Server 2008 R2
 **Cores** | Each server must have no more than 128 cores, which is the maximum number an Azure VM supports.<br><br> If performance history is available, Azure Migrate considers the utilized cores for comparison. If the assessment settings specify a comfort factor, the number of utilized cores is multiplied by the comfort factor.<br><br> If there's no performance history, Azure Migrate uses the allocated cores to apply the comfort factor. | Ready if the number of cores is within the limit
@@ -189,8 +189,9 @@ Other operating systems like Oracle Solaris, Apple macOS, and FreeBSD | Azure do
 OS specified as **Other** in vCenter Server | Azure Migrate can't identify the OS in this case. | Unknown readiness. Ensure that Azure supports the OS running inside the VM.
 32-bit operating systems | The server might start in Azure, but Azure might not provide full support. | Conditionally ready for Azure. Consider upgrading to a 64-bit OS before migrating to Azure.
 
-### Security Readiness
-Assessments also determine readiness of the recommended target for Microsoft Defender for Servers. A server is marked as Ready for Microsoft Defender for Servers if it satisfies the following conditions:
+### Security readiness
+
+Assessments also determine readiness of the recommended target for Microsoft Defender for Servers. A server is marked as Ready for Microsoft Defender for Servers if it has the following:
 - Minimum 2 vCores (4 vCores preferred)
 - Minimum 1 GB RAM (4 GB preferred)
 - 2 GB of disk space
@@ -203,8 +204,8 @@ Assessments also determine readiness of the recommended target for Microsoft Def
    - Oracle Linux 7.2+, 8
    - CentOS Linux 7.2+
    - Amazon Linux 2
-- For other operating systems, it is marked as **Ready with Conditions**.
-If a server is not ready to be migrated to Azure, it is marked as **Not Ready for Microsoft Defender for Servers**.
+- For other Operating Systems, the server is marked as **Ready with Conditions**.
+If a server is not ready to be migrated to Azure, it is marked as **Not Ready** for Microsoft Defender for Servers.
 
 
 ## Calculating sizing
@@ -356,7 +357,7 @@ Cost is calculated using the following logic:
 
 Assessment calculates the total monthly storage costs by aggregating the storage costs of all servers. Currently, the calculation doesn't consider offers specified in the assessment settings.
 
-### Security Cost
+### Security cost
 For servers recommended for Azure VM, if they're ready to run Defender for Server, the Defender for Server cost (Plan 2) per server for that region is added. The assessment aggregates the cost across all servers to calculate the total monthly security cost.
 
 Costs are displayed in the currency specified in the assessment settings.

articles/migrate/concepts-azure-sql-assessment-calculation.md

@@ -139,12 +139,12 @@ If you select the target deployment type as **Recommended** in the Azure SQL ass
 > [!NOTE]
 > In the recommended deployment strategy, if the source SQL Server is good fit for all three deployment targets- SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database, the assessment recommends a specific option that optimizes your cost and fits within the size and performance boundaries.
 
-### Security Readiness
+### Security readiness
 
-If the database/instance is marked as Ready for the target deployment type Azure SQL DB/MI, it is automatically considered Ready for Microsoft Defender for SQL. 
-If the database/instance is marked as Ready for the target deployment type SQL Server on Azure VM, it is considered Ready for Microsoft Defender for SQL if it is running any of these versions -  
+If the database/instance is marked as **Ready** for the target deployment type Azure SQL DB/MI, it is automatically considered **Ready** for Microsoft Defender for SQL. 
+If the database/instance is marked as **Ready** for the target deployment type SQL Server on Azure VM, it is considered **Ready** for Microsoft Defender for SQL if it is running any of these versions:
 - SQL Server versions 2012, 2014, 2016, 2017, 2019, 2022
-- For all other versions, it is marked as Ready with Conditions
+- For all other versions, it is marked as **Ready with Conditions**.
 
 
 ## Calculate sizing
@@ -256,6 +256,7 @@ This section provides guidance to configure the target resource and steps to mig
 
 ## Calculate monthly costs
 After sizing recommendations are complete, Azure SQL assessment calculates the compute and storage costs for the recommended Azure SQL configurations using an internal pricing API. It aggregates the compute and storage cost across all instances to calculate the total monthly compute cost. 
+
 ### Compute cost
 - To calculate the compute cost for an Azure SQL configuration, the assessment considers the following properties:
     - Azure Hybrid Benefit for SQL and Windows licenses
@@ -279,7 +280,8 @@ After sizing recommendations are complete, Azure SQL assessment calculates the c
 - **Azure SQL Managed Instance**
     - There's no storage cost added for the first 32 GB/instance/month storage and additional storage cost is added for storage in 32 GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql/sql-managed-instance/single/).
 
-### Security Cost
+### Security cost
+
 For SQL Server instances and DBs recommended for SQL Server on Azure VM, Azure SQL MI or Azure SQL DB, if they're ready to run Defender for SQL, the Defender for SQL per SQL Server instance for that region is added. For DBs recommended to Azure SQL DB, cost is rolled up at instance level.
 
         

articles/migrate/concepts-azure-webapps-assessment-calculation.md

@@ -78,7 +78,7 @@ Azure App Service readiness for web apps is based on feature compatibility check
 1. If there are any compatibility issues that may block the migration to a specific target deployment type, the readiness is marked as **Not ready** with **issue** details and recommended remediation guidance.
 1. If the discovery is still in progress or there are any discovery issues for a web app, the readiness is marked as **Unknown** as the assessment couldn't compute the readiness for that web app.
 
-### Security Readiness
+### Security readiness
 If the web app is marked as **Ready** or **Ready with conditions** for Azure App Service, it is marked as **Ready** for Microsoft Defender for App Service.
 
 
@@ -117,7 +117,7 @@ P1v3  | 16
 > [!NOTE]
 > Your App Service plan can be scaled up and down at any time. [Learn more](../app-service/overview-hosting-plans.md#what-if-my-app-needs-more-capabilities-or-features).
 
-### Security Cost
+### Security cost
 For web apps that have been recommended to App Service plans, the security cost is calculated per App Service plan that has been recommended.