Merge pull request #108052 from Juliako/patch-6

Update media-services-content-protection-overview.md

Author: PRMerger20

articles/media-services/previous/media-services-content-protection-overview.md

@@ -31,13 +31,18 @@ The following image illustrates the Media Services content protection workflow:
 This article explains concepts and terminology relevant to understanding content protection with Media Services. The article also provides links to articles that discuss how to protect content. 
 
 ## Dynamic encryption
- You can use Media Services to deliver your content encrypted dynamically with AES clear key or DRM encryption by using PlayReady, Widevine, or FairPlay. Currently, you can encrypt the HTTP Live Streaming (HLS), MPEG DASH, and Smooth Streaming formats. Encryption on progressive downloads is not supported. Each encryption method supports the following streaming protocols:
 
+You can use Media Services to deliver your content encrypted dynamically with AES clear key or DRM encryption by using PlayReady, Widevine, or FairPlay. If content is encrypted with an AES clear key and is sent over HTTPS, it is not in clear until it reaches the client. 
+
+Each encryption method supports the following streaming protocols:
+ 
 - AES: MPEG-DASH, Smooth Streaming, and HLS
 - PlayReady: MPEG-DASH, Smooth Streaming, and HLS
 - Widevine: MPEG-DASH
 - FairPlay: HLS
 
+Encryption on progressive downloads is not supported. 
+
 To encrypt an asset, you need to associate an encryption content key with your asset and also configure an authorization policy for the key. Content keys can be specified or automatically generated by Media Services.
 
 You also need to configure the asset's delivery policy. If you want to stream a storage-encrypted asset, make sure to specify how you want to deliver it by configuring the asset delivery policy.
@@ -49,9 +54,6 @@ Customers often wonder whether they should use AES encryption or a DRM system. T
 
 PlayReady, Widevine, and FairPlay all provide a higher level of encryption compared to AES-128 clear key encryption. The content key is transmitted in an encrypted format. Additionally, decryption is handled in a secure environment at the operating system level, where it's more difficult for a malicious user to attack. DRM is recommended for use cases where the viewer might not be a trusted party and you require the highest level of security.
 
-> [!NOTE]
-> If content is encrypted with a clear key and it is sent over HTTPS, the content is not in clear until it reaches the client.
-
 ## Storage encryption
 You can use storage encryption to encrypt your clear content locally by using AES 256-bit encryption. You then can upload it to Azure Storage, where it's stored encrypted at rest. Assets protected with storage encryption are automatically unencrypted and placed in an encrypted file system prior to encoding. The assets are optionally re-encrypted prior to uploading back as a new output asset. The primary use case for storage encryption is when you want to secure your high-quality input media files with strong encryption at rest on disk.
 
@@ -96,6 +98,7 @@ The following considerations apply:
 * Encryption type doesn't have to be specified in the URL if only one encryption was applied to the asset.
 * Encryption type is case insensitive.
 * The following encryption types can be specified:
+
   * **cenc**: For PlayReady or Widevine (common encryption)
   * **cbcs-aapl**: For FairPlay (AES CBC encryption)
   * **cbc**: For AES envelope encryption