client side encryption, freshness updates

articles/storage/storage-analytics.md

@@ -22,13 +22,13 @@
 
 Azure Storage Analytics performs logging and provides metrics data for a storage account. You can use this data to trace requests, analyze usage trends, and diagnose issues with your storage account.
 
-To use Storage Analytics, you must enable it individually for each service you want to monitor. You can enable it from the [Azure Management Portal](https://manage.windowsazure.com/); for details, see [How To Monitor a Storage Account](http://www.azure.com/manage/services/storage/how-to-monitor-a-storage-account/). You can also enable Storage Analytics programmatically via the REST API or the client library. Use the [Get Blob Service Properties](https://msdn.microsoft.com/en-us/library/hh452239.aspx), [Get Queue Service Properties](https://msdn.microsoft.com/en-us/library/hh452243.aspx), and [Get Table Service Properties](https://msdn.microsoft.com/en-us/library/hh452238.aspx) operations to enable Storage Analytics for each service.
+To use Storage Analytics, you must enable it individually for each service you want to monitor. You can enable it from the [Azure Management Portal](https://manage.windowsazure.com/); for details, see [How To Monitor a Storage Account](http://www.azure.com/manage/services/storage/how-to-monitor-a-storage-account/). You can also enable Storage Analytics programmatically via the REST API or the client library. Use the [Get Blob Service Properties](https://msdn.microsoft.com/library/hh452239.aspx), [Get Queue Service Properties](https://msdn.microsoft.com/library/hh452243.aspx), and [Get Table Service Properties](https://msdn.microsoft.com/library/hh452238.aspx) operations to enable Storage Analytics for each service.
 
 The aggregated data is stored in a well-known blob (for logging) and in well-known tables (for metrics), which may be accessed using the Blob service and Table service APIs.
 
 Storage Analytics has a 20TB limit on the amount of stored data that is independent of the total limit for your storage account. For more information on billing and data retention policies, see [Storage Analytics and Billing](https://msdn.microsoft.com/library/hh360997.aspx). For more information on storage account limits, see [Azure Storage Scalability and Performance Targets](https://msdn.microsoft.com/library/dn249410.aspx).
 
-For an in-depth guide on using Storage Analytics and other tools to identify, diagnose, and troubleshoot Azure Storage-related issues, see [Monitor, diagnose, and troubleshoot Microsoft Azure Storage](http://azure.microsoft.com/documentation/articles/storage-monitoring-diagnosing-troubleshooting/).
+For an in-depth guide on using Storage Analytics and other tools to identify, diagnose, and troubleshoot Azure Storage-related issues, see [Monitor, diagnose, and troubleshoot Microsoft Azure Storage](storage-monitoring-diagnosing-troubleshooting.md).
 
 
 ## About Storage Analytics Logging

articles/storage/storage-import-export-service.md

@@ -274,7 +274,7 @@ For export jobs, you can view and copy the BitLocker keys generated by the servi
 - No. All drives must be BitLocker-prepared.
 
 **Do I need to perform any disk preparation when creating an export job?**
-- No, but some pre-checks are recommended. Check the number of disks required using Azure Import/Export tool's [PreviewExport](https://msdn.microsoft.com/en-us/library/azure/dn722414.aspx) command. It helps you preview drive usage for the blobs you selected, based on the size of the drives you are going to use. Also check that you can read/write to the hard drive that will be shipped for the export job.
+- No, but some pre-checks are recommended. Check the number of disks required using Azure Import/Export tool's [PreviewExport](https://msdn.microsoft.com/library/azure/dn722414.aspx) command. It helps you preview drive usage for the blobs you selected, based on the size of the drives you are going to use. Also check that you can read/write to the hard drive that will be shipped for the export job.
 
 ### Shipping