Merge pull request #53344 from MicrosoftDocs/BharathNimmala-MSFT-patch-17

(AzureCXP) Fixing Typo

Author: ktoliver

articles/azure-monitor/platform/manage-cost-storage.md

@@ -29,7 +29,7 @@ In this article we review how you can proactively monitor ingested data volume a
 
 The default pricing for Log Analytics is a **Pay-As-You-Go** model based on data volume ingested and optionally for longer data retention. Data volume is measured as the size of the data that will be stored. Each Log Analytics workspace is charged as a separate service and contributes to the bill for your Azure subscription. The amount of data ingestion can be considerable depending on the following factors: 
 
-  - Number of management solutions enabled and their configuration (e.g. 
+  - Number of management solutions enabled and their configuration
   - Number of VMs monitored
   - Type of data collected from each monitored VM 
 
@@ -592,4 +592,4 @@ There are some additional Log Analytics limits, some of which depend on the Log
 - To configure an effective   event collection policy, review [Azure Security Center filtering policy](../../security-center/security-center-enable-data-collection.md).
 - Change [performance counter configuration](data-sources-performance-counters.md).
 - To modify your event collection settings, review [event log configuration](data-sources-windows-events.md).
-- To modify your syslog collection settings, review [syslog configuration](data-sources-syslog.md).
+- To modify your syslog collection settings, review [syslog configuration](data-sources-syslog.md).