updated acrolinx.

Author: AbdullahBell

articles/ddos-protection/ddos-optimization-guide.md

@@ -18,7 +18,7 @@ When designing your architecture, balance security requirements with financial c
 - What's the spending pattern for DDoS protection across your workloads?
 - How will you maximize protection investment through better resource selection and utilization?
 
-A cost-optimized DDoS protection strategy isn't always the lowest cost option. You'll need to balance security effectiveness with financial efficiency. Tactical cost-cutting can create security vulnerabilities. To achieve long-term protection and financial responsibility, create a strategy with [risk-based prioritization](/azure/well-architected/cost-optimization/principles), continuous monitoring, and repeatable processes.
+A cost-optimized DDoS protection strategy isn't always the lowest cost option. You need to balance security effectiveness with financial efficiency. Tactical cost-cutting can create security vulnerabilities. To achieve long-term protection and financial responsibility, create a strategy with [risk-based prioritization](/azure/well-architected/cost-optimization/principles), continuous monitoring, and repeatable processes.
 
 Start with the recommended approaches and justify the benefits for your security requirements. After you set your strategy, use these principles through regular assessment and optimization cycles. For comprehensive guidance on cost management, see [Azure Cost Management documentation](/azure/cost-management-billing/) and the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).
 
@@ -71,7 +71,7 @@ Protection needs change as your infrastructure evolves. Set up continuous monito
 | **Set up cost alerts** when DDoS protection spending approaches predefined budget thresholds. | Proactive notifications prevent budget overruns and enable timely adjustments to protection strategy. You can respond to cost increases before they impact other initiatives. To create cost alerts, see [Monitor usage and spending with cost alerts in Cost Management](/azure/cost-management-billing/costs/cost-mgt-alerts-monitor-usage-spending). |
 | **Conduct quarterly reviews** of protected resources and their business criticality to identify optimization opportunities. | Regular reviews ensure protection investments remain aligned with business priorities. You can identify resources that no longer need protection or require upgraded protection based on changing importance. |
 | **Monitor attack patterns** and protection effectiveness to optimize coverage decisions. [View alerts in Microsoft Defender for Cloud](ddos-view-alerts-defender-for-cloud.md) and utilize [DDoS Protection logs in Log Analytics workspace](ddos-view-diagnostic-logs.md). | Understanding actual threat patterns enables data-driven protection decisions. You can adjust protection levels based on real attack data rather than theoretical risks. |
-| **Track protection ROI and implement lifecycle management** using [cost management best practices](/azure/cost-management-billing/costs/cost-analysis-common-uses) to measure value and decommission unnecessary protection. | ROI measurement demonstrates protection value and guides future investment decisions. Regular cleanup of inactive or non-critical resources prevents spending growth that doesn't align with business value while freeing budget for higher-priority resources. |
+| **Track protection ROI and implement lifecycle management** using [cost management best practices](/azure/cost-management-billing/costs/cost-analysis-common-uses) to measure value and decommission unnecessary protection. | ROI measurement demonstrates protection value and guides future investment decisions. Regular cleanup of inactive or noncritical resources prevents spending growth that doesn't align with business value while freeing budget for higher-priority resources. |
 
 ## Next steps
 

articles/ddos-protection/ddos-pricing-guide.md

@@ -40,7 +40,7 @@ Let's assume you have only one subscription in your tenant. If you create a Netw
 
 In this same scenario with 10 Public IP addresses, if you enable IP Protection for each Public IP address, you're billed per protected IP resource.
 
-Under this scenario, it's more cost effective to enable IP Protection for each Public IP address. For environments with more than 15 Public IP addresses, it's more cost effective to create a Network Protection plan. 
+Under this scenario, its more cost effective to enable IP Protection for each Public IP address. For environments with more than 15 Public IP addresses, it's more cost effective to create a Network Protection plan. 
 
 **Cost comparison analysis:**
 - Network Protection: Fixed monthly cost for up to 100 IP addresses
@@ -53,11 +53,11 @@ This scenario illustrates cost benefits for large organizations with multiple su
 
 #### Multiple subscriptions with Network Protection
 
-An enterprise has 3 subscriptions with the following public IP distribution:
+An enterprise has three subscriptions with the following public IP distribution:
 - Subscription A: 25 public IPs (production workloads)
 - Subscription B: 15 public IPs (staging environment)  
 - Subscription C: 8 public IPs (development environment)
-- **Total: 48 public IPs across 3 subscriptions**
+- **Total: 48 public IPs across three subscriptions**
 
 With Network Protection, you create one plan that covers all subscriptions under the tenant:
 - Cost: Single monthly Network Protection plan fee (covers up to 100 IPs across all subscriptions)
@@ -94,15 +94,15 @@ This scenario shows cost implications for applications with fluctuating public I
 
 Consider an e-commerce platform that scales during peak seasons:
 
-#### Regular operations (9 months)
+#### Regular operations (nine months)
 - 8 public IPs needed
-- IP Protection cost: Per-IP rate × 8 resources × 9 months
+- IP Protection cost: Per-IP rate × eight resources × nine months
 
-#### Peak season (3 months) 
+#### Peak season (three months) 
 - 25 public IPs needed during holiday season
 - Two options:
-  1. **IP Protection**: Per-IP rate × 25 resources × 3 months
-  2. **Temporary Network Protection**: Monthly plan rate × 3 months
+  1. **IP Protection**: Per-IP rate × 25 resources × three months
+  2. **Temporary Network Protection**: Monthly plan rate × three months
 
 **Annual cost comparison analysis:**
 - IP Protection only: Higher total cost due to linear scaling during peak periods
@@ -121,7 +121,7 @@ Network Protection provides additional value beyond basic DDoS mitigation that s
 ### Cost Protection Guarantee
 Network Protection includes a cost protection guarantee that provides service credits for additional Azure costs incurred during a documented DDoS attack. This includes:
 - Data transfer costs from scale-out operations
-- Additional compute costs for auto-scaling responses
+- Additional compute costs for autoscaling responses
 - Other documented Azure service costs directly attributable to DDoS attacks
 
 ### DDoS Rapid Response (DRR)