Update frequently-asked-questions.md

Author: Juliako

articles/media-services/latest/frequently-asked-questions.md

@@ -228,9 +228,9 @@ A sample boot.xml file:
 
 Since Media Services v3 allows an Asset to have multiple StreamingLocators. You can have
 
-1. One ContentKeyPolicy with license_type = "persistent", ContentKeyPolicyRestriction with claim on "persistent", and its StreamingLocator;
-1. Another ContentKeyPolicy with license_type="nonpersistent", ContentKeyPolicyRestriction with claim on "nonpersistent", and its StreamingLocator.
-1. The two StreamingLocators have different ContentKey.
+* One ContentKeyPolicy with license_type = "persistent", ContentKeyPolicyRestriction with claim on "persistent", and its StreamingLocator;
+* Another ContentKeyPolicy with license_type="nonpersistent", ContentKeyPolicyRestriction with claim on "nonpersistent", and its StreamingLocator.
+* The two StreamingLocators have different ContentKey.
 
 Depending on business logic of custom STS, different claims are issued in the JWT token. With the token, only the corresponding license can be obtained and only the corresponding URL can be played.
 
@@ -241,17 +241,17 @@ five different security levels are outlined. This section explains how the secur
 
 The Google's "Widevine DRM Architecture Review" doc defines the following three security levels:
 
-1. Security Level 1: All content processing, cryptography, and control are performed within the Trusted Execution Environment (TEE). In some implementation models, security processing may be performed in different chips.
-1. Security Level 2: Performs cryptography (but not video processing) within the TEE: decrypted buffers are returned to the application domain and processed through separate video hardware or software. At level 2, however, cryptographic information is still processed only within the TEE.
-1. Security Level 3 Does not have a TEE on the device. Appropriate measures may be taken to protect the cryptographic information and decrypted content on host operating system. A Level 3 implementation may also include a hardware cryptographic engine, but that only enhances performance, not security.
+* Security Level 1: All content processing, cryptography, and control are performed within the Trusted Execution Environment (TEE). In some implementation models, security processing may be performed in different chips.
+* Security Level 2: Performs cryptography (but not video processing) within the TEE: decrypted buffers are returned to the application domain and processed through separate video hardware or software. At level 2, however, cryptographic information is still processed only within the TEE.
+* Security Level 3 Does not have a TEE on the device. Appropriate measures may be taken to protect the cryptographic information and decrypted content on host operating system. A Level 3 implementation may also include a hardware cryptographic engine, but that only enhances performance, not security.
 
 At the same time, in [Azure Media Services documentation on Widevine license template](widevine-license-template-overview.md), the security_level property of content_key_specs can have the following five different values (client robustness requirements for playback):
 
-1. Software-based white-box crypto is required.
-1. Software crypto and an obfuscated decoder is required.
-1. The key material and crypto operations must be performed within a hardware backed TEE.
-1. The crypto and decoding of content must be performed within a hardware backed TEE.
-1. The crypto, decoding, and all handling of the media (compressed and uncompressed) must be handled within a hardware backed TEE.
+* Software-based white-box crypto is required.
+* Software crypto and an obfuscated decoder is required.
+* The key material and crypto operations must be performed within a hardware backed TEE.
+* The crypto and decoding of content must be performed within a hardware backed TEE.
+* The crypto, decoding, and all handling of the media (compressed and uncompressed) must be handled within a hardware backed TEE.
 
 Both security levels are defined by Google Widevine. The difference is in its usage level: architecture level or API level. The five security levels are used in the Widevine API. The content_key_specs object, which
 contains security_level is deserialized and passed to the Widevine global delivery service by Azure Media Services Widevine license service. The table below shows the mapping between the two sets of security levels.
@@ -266,11 +266,11 @@ contains security_level is deserialized and passed to the Widevine global delive
 
 There are two ways to improve download speed:
 
-1. Enable CDN so that end users are more likely to hit CDN instead of origin/streaming endpoint for content download. If user hits streaming endpoint, each HLS segment or DASH fragment is dynamically packaged and encrypted. Even though this latency is in millisecond scale for each segment/fragment, when you have an hour long video, the accumulated latency can be large causing longer download.
-1. Provide end users the option to selectively download video quality layers and audio tracks instead of all contents. For offline mode, there is no point to download all of the quality layers. There are two ways to achieve this:
+* Enable CDN so that end users are more likely to hit CDN instead of origin/streaming endpoint for content download. If user hits streaming endpoint, each HLS segment or DASH fragment is dynamically packaged and encrypted. Even though this latency is in millisecond scale for each segment/fragment, when you have an hour long video, the accumulated latency can be large causing longer download.
+* Provide end users the option to selectively download video quality layers and audio tracks instead of all contents. For offline mode, there is no point to download all of the quality layers. There are two ways to achieve this:
 
-   1. Client controlled: either player app auto selects or user selects video  quality layer and audio tracks to download;
-   1. Service controlled: one can use Dynamic Manifest feature in Azure Media Services to create a (global) filter, which limits HLS playlist or DASH MPD to a single video quality layer and selected audio tracks. Then the download URL presented to end users will include this filter.
+   * Client controlled: either player app auto selects or user selects video  quality layer and audio tracks to download;
+   * Service controlled: one can use Dynamic Manifest feature in Azure Media Services to create a (global) filter, which limits HLS playlist or DASH MPD to a single video quality layer and selected audio tracks. Then the download URL presented to end users will include this filter.
 
 ## Next steps