Merge pull request #204521 from tamram/patch-31

Update client-side-encryption.md

Author: PRMerger12

articles/storage/blobs/client-side-encryption.md

@@ -7,7 +7,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: article
-ms.date: 07/11/2022
+ms.date: 07/12/2022
 ms.author: tamram
 ms.reviewer: ozgun
 ms.subservice: blobs
@@ -225,6 +225,8 @@ For a sample project that shows how to migrate data from client-side encryption
 
 For a sample project that shows how to migrate data from client-side encryption v1 to v2 and how to encrypt data with client-side encryption v2 in Python, see [Client Side Encryption Migration from V1 to V2](https://github.com/wastore/azure-storage-samples-for-python/tree/master/ClientSideEncryptionToServerSideEncryptionMigrationSamples/ClientSideEncryptionV1ToV2).
 
+---
+
 ## Client-side encryption and performance
 
 Keep in mind that encrypting your storage data results in additional performance overhead. When you use client-side encryption in your application, the client library must securely generate the CEK and IV, encrypt the content itself, communicate with your chosen keystore for key-enveloping, and format and upload additional metadata. This overhead varies depending on the quantity of data being encrypted. We recommend that customers always test their applications for performance during development.