Update live-event-types-comparison.md

Author: Juliako

articles/media-services/latest/live-event-types-comparison.md

@@ -22,11 +22,11 @@ In Azure Media Services, a  [Live Event](https://docs.microsoft.com/rest/api/med
 
 ## Types comparison 
 
-The following table compares features of the Live Event types. The types are set during creation using these properties:
+The following table compares features of the Live Event types. The types are set during creation using [LiveEventEncodingType](https://docs.microsoft.com/rest/api/media/liveevents/create#liveeventencodingtype):
 
 * **LiveEventEncodingType.None** - An on-premises live encoder sends a multiple bitrate stream. The ingested streams passes through the Live Event without any further processing. 
-* **LiveEventEncodingType.Standard** - An on-premises live encoder sends a single-bitrate stream to the Live Event and Media Services creates multiple bitrate streams. If the contribution feed is of 720p or higher resolution, the **Default720p** preset will encode a set of 6 resolution/bit rate pairs (details follow later in the article).
-* **LiveEventEncodingType.Premium1080p** - An on-premises live encoder sends a single-bitrate stream to the Live Event and Media Services creates multiple bitrate streams. The Default1080p preset specifies the output set of resolution/bit rate pairs (details follow later in the article). 
+* **LiveEventEncodingType.Standard** - An on-premises live encoder sends a single bitrate stream to the Live Event and Media Services creates multiple bitrate streams. If the contribution feed is of 720p or higher resolution, the **Default720p** preset will encode a set of 6 resolution/bitrate pairs (details follow later in the article).
+* **LiveEventEncodingType.Premium1080p** - An on-premises live encoder sends a single bitrate stream to the Live Event and Media Services creates multiple bitrate streams. The Default1080p preset specifies the output set of resolution/bitrate pairs (details follow later in the article). 
 
 | Feature | Pass-through Live Event | Standard or Premium1080p Live Event |
 | --- | --- | --- |
@@ -58,7 +58,7 @@ The following table compares features of the Live Event types. The types are set
 
 ## System presets
 
-The resolutions and bitrates contained in the output from the live encoder is determined by the [presetName](https://docs.microsoft.com/rest/api/media/liveevents/create#liveeventencoding). If using a **Standard** live encoder (LiveEventEncodingType.Standard), then the *Default720p* preset specifies a set of 6 resolution/bit rate pairs described below. Otherwise, if using a **Premium1080p** live encoder (LiveEventEncodingType.Premium1080p), then the *Default1080p* preset specifies the output set of resolution/bit rate pairs.
+The resolutions and bitrates contained in the output from the live encoder are determined by the [presetName](https://docs.microsoft.com/rest/api/media/liveevents/create#liveeventencoding). If using a **Standard** live encoder (LiveEventEncodingType.Standard), then the *Default720p* preset specifies a set of 6 resolution/bitrate pairs described below. Otherwise, if using a **Premium1080p** live encoder (LiveEventEncodingType.Premium1080p), then the *Default1080p* preset specifies the output set of resolution/bitrate pairs.
 
 > [!NOTE]
 > You cannot apply the Default1080p preset to a Live Event if it has been setup for Standard live encoding - you will get an error. You will also get an error if you try to apply the Default720p preset to a Premium1080p live encoder.
@@ -78,7 +78,7 @@ If the contribution feed is of 720p or higher resolution, the **Default720p** pr
 
 > [!NOTE]
 > If you need to customize the live encoding preset, please open a support ticket via Azure Portal. You should specify the desired table of resolution and bitrates. Do verify that there is only one layer at 720p, and at most 6 layers. Also do specify that you are requesting a preset for a Standard live encoder.
-> The specific values of the bit rates and resolutions may be adjusted over time
+> The specific values of the bitrates and resolutions may be adjusted over time
 
 ### Output Video Streams for Default1080p
 
@@ -95,11 +95,11 @@ If the contribution feed is of 1080p resolution, the **Default1080p** preset wil
 
 > [!NOTE]
 > If you need to customize the live encoding preset, please open a support ticket via Azure Portal. You should specify the desired table of resolution and bitrates. Do verify that there is only one layer at 1080p, and at most 6 layers. Also do specify that you are requesting a preset for a Premium1080p live encoder.
-> The specific values of the bit rates and resolutions may be adjusted over time.
+> The specific values of the bitrates and resolutions may be adjusted over time.
 
 ### Output Audio Stream for Default720p and Default1080p
 
-For both *Default720p* and *Default1080p* presets, audio is encoded to stereo AAC-LC at 128 kbps, sampling rate of 48 kHz.
+For both *Default720p* and *Default1080p* presets, audio is encoded to stereo AAC-LC at 128 kbps. The sampling rate follows that of the audio track in the contribution feed.
 
 ## Implicit properties of the live encoder
 
@@ -111,13 +111,13 @@ The live encoder follows the [GOP](https://en.wikipedia.org/wiki/Group_of_pictur
 
 ### Frame rate
 
-The live encoder also follows the durations of the individual video frames in the contribution feed - which means the output layers will have frames with the same durations. Hence, it is recommended that you configure the on-premises encoder to produce a contribution feed that has fixed frame rate (at most 30 frames/second). This will ensure that the outgoing HLS and MPEG DASH streams from the service also has fixed frame rates durations. Small variations in frame rates are likely to be tolerated by most devices, but your on-premises live encoder should not be dropping frames (eg. under low battery conditions).
+The live encoder also follows the durations of the individual video frames in the contribution feed - which means the output layers will have frames with the same durations. Hence, it is recommended that you configure the on-premises encoder to produce a contribution feed that has fixed frame rate (at most 30 frames/second). This will ensure that the outgoing HLS and MPEG DASH streams from the service also has fixed frame rates durations. Small variations in frame rates may be tolerated by most devices, but there is no guarantee that the live encoder will produce an output that will play correctly. Your on-premises live encoder should not be dropping frames (eg. under low battery conditions) or varying the frame rate in any way.
 
 ### Resolution of contribution feed and output layers
 
 The live encoder is configured to avoid upconverting the contribution feed. As a result the maximum resolution of the output layers will not exceed that of the contribution feed.
 
-For example, if you send a contribution feed at 720p to a Live Event configured for Default1080p live encoding, the output will only have 5 layers, starting with 720p at 3Mbps, going down to 1080p at 200 kbps. Or if you send a contribution feed at 360p into a Live Event configured for Standard live encoding, the output will contain 3 layers (at resolutions of 288p, 216p, and 192p). In the degenerate case, if you send a contribution feed of, say, 160x90 pixels to a Standard live encoder, the output will contain one layer at 160x90 resolution at 200 kbps.
+For example, if you send a contribution feed at 720p to a Live Event configured for Default1080p live encoding, the output will only have 5 layers, starting with 720p at 3Mbps, going down to 1080p at 200 kbps. Or if you send a contribution feed at 360p into a Live Event configured for Standard live encoding, the output will contain 3 layers (at resolutions of 288p, 216p, and 192p). In the degenerate case, if you send a contribution feed of, say, 160x90 pixels to a Standard live encoder, the output will contain one layer at 160x90 resolution at the same bitrate as that of the contribution feed.
 
 ### Bitrate of contribution feed and output layers