Merge pull request #106235 from Juliako/live

fixed the wording

Author: PRMerger18

articles/media-services/latest/concepts-overview.md

@@ -42,7 +42,7 @@ The fundamental concepts described in these topics should be reviewed prior to s
 |Analyzing content (Video Indexer)|Media Services v3 lets you extract insights from your video and audio files using Media Services v3 presets. To analyze your content using Media Services v3 presets, you need to create **Transforms** and **Jobs**.<br/><br/>If you want more detailed insights, use [Video Indexer](https://docs.microsoft.com/azure/media-services/video-indexer/) directly.|[Analyzing video and audio files](analyzing-video-audio-files-concept.md)|
 |Packaging and delivery|Once your content is encoded, you can take advantage of **Dynamic Packaging**. In Media Services, a **Streaming Endpoint** is the dynamic packaging service used to deliver media content to client players. To make videos in the output asset available to clients for playback, you have to create a **Streaming Locator** and then build streaming URLs. <br/><br/>When creating the **Streaming Locator**, in addition to asset's name, you need to specify **Streaming Policy**. **Streaming Policies** enable you to define streaming protocols and encryption options (if any) for your **Streaming Locators**. Dynamic Packaging is used whether you stream your content live or on-demand. <br/><br/>You can use Media Services **Dynamic Manifests** to stream only a specific rendition or subclips of your video.|[Dynamic packaging](dynamic-packaging-overview.md)<br/><br/>[Streaming Endpoints](streaming-endpoint-concept.md)<br/><br/>[Streaming Locators](streaming-locators-concept.md)<br/><br/>[Streaming Policies](streaming-policy-concept.md)<br/><br/>[Dynamic manifests](filters-dynamic-manifest-overview.md)<br/><br/>[Filters](filters-concept.md)|
 |Content protection|With Media Services, you can deliver your live and on-demand content encrypted dynamically with Advanced Encryption Standard (AES-128) or/and any of the three major digital rights management (DRM) systems: Microsoft PlayReady, Google Widevine, and Apple FairPlay. Media Services also provides a service for delivering AES keys and DRM (PlayReady, Widevine, and FairPlay) licenses to authorized clients. <br/><br/>If specifying encryption options on your stream, create the **Content Key Policy** and associate it with your **Streaming Locator**. The **Content Key Policy** enables you to configure how the content key is delivered to end clients.<br/><br/> Try to reuse policies whenever the same options are needed.| [Content Key Policies](content-key-policy-concept.md)<br/><br/>[Content protection](content-protection-overview.md)|
-|Live streaming|Media Services enables you to deliver live events to your customers on the Azure cloud. **Live Events** are responsible for ingesting and processing the live video feeds. When you create a **Live Event**, an input endpoint is created that you can use to send a live signal from a remote encoder. Once you have the stream flowing into the **Live Event**, you can begin the streaming event by creating an **Asset**, **Live Output**, and **Streaming Locator**. **Live Output** will archive the stream  into the **Asset** and make it available to viewers through the **Streaming Endpoint**. A **Live Event** can be one of two types: **pass-through** and **live encoding**.|[Live streaming overview](live-streaming-overview.md)<br/><br/>[Live Events and Live Outputs](live-events-outputs-concept.md)|
+|Live streaming|Media Services enables you to deliver live events to your customers on the Azure cloud. **Live Events** are responsible for ingesting and processing the live video feeds. When you create a **Live Event**, an input endpoint is created that you can use to send a live signal from a remote encoder. Once you have the stream flowing into the **Live Event**, you can begin the streaming event by creating an **Asset**, **Live Output**, and **Streaming Locator**. **Live Output** will archive the stream  into the **Asset** and make it available to viewers through the **Streaming Endpoint**. A live event can be set to either a *pass-through* (an on-premises live encoder sends a multiple bitrate stream) or *live encoding* (an on-premises live encoder sends a single bitrate stream). |[Live streaming overview](live-streaming-overview.md)<br/><br/>[Live Events and Live Outputs](live-events-outputs-concept.md)|
 |Monitoring with Event Grid|To see the progress of the job, you should use **Event Grid**. Media Services also emits the Live event types. With Event Grid, your apps can listen for and react to events from virtually all Azure services, as well as custom sources. |[Handling Event Grid events](reacting-to-media-services-events.md)<br/><br/>[Schemas](media-services-event-schemas.md)|
 |Monitoring with Azure Monitor|Monitor metrics and diagnostic logs that help you understand how your applications are performing with Azure Monitor.|[Metrics and diagnostic logs](media-services-metrics-diagnostic-logs.md)<br/><br/>[Diagnostic logs schemas](media-services-diagnostic-logs-schema.md)|
 |Player clients|You can use Azure Media Player to play back media content streamed by Media Services on a wide variety of browsers and devices. Azure Media Player utilizes industry standards, such as HTML5, Media Source Extensions (MSE), and Encrypted Media Extensions (EME) to provide an enriched adaptive streaming experience. |[Azure Media Player overview](use-azure-media-player.md)|

articles/media-services/latest/dynamic-packaging-overview.md

@@ -90,7 +90,7 @@ See the list of Media Encoder Standard [formats and codecs](media-encoder-standa
 
 ## Live streaming workflow
 
-A live event can be one of two types: pass-through or live encoding. 
+A live event can be set to either a *pass-through* (an on-premises live encoder sends a multiple bitrate stream) or *live encoding* (an on-premises live encoder sends a single bitrate stream). 
 
 Here's a common workflow for live streaming with Dynamic Packaging:
 

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

@@ -1,6 +1,6 @@
 ---
 title: Azure Media Services LiveEvent types | Microsoft Docs
-description: In Azure Media Services, a Live Event can be one of two types, live encoding and pass-through. This article shows a detailed table that compares Live Event types. 
+description: In Azure Media Services, a live event can be set to either a *pass-through* or *live encoding*. This article shows a detailed table that compares Live Event types. 
 services: media-services
 documentationcenter: ''
 author: Juliako
@@ -18,7 +18,9 @@ ms.author: juliako
 ---
 # Live Event types comparison
 
-In Azure Media Services, a  [Live Event](https://docs.microsoft.com/rest/api/media/liveevents) can be one of two types: live encoding and pass-through. 
+In Azure Media Services, a  [Live Event](https://docs.microsoft.com/rest/api/media/liveevents) can be set to either a *pass-through* (an on-premises live encoder sends a multiple bitrate stream) or *live encoding* (an on-premises live encoder sends a single bitrate stream). 
+
+This articles compares features of the live event types.
 
 ## Types comparison 
 

articles/media-services/latest/live-events-outputs-concept.md

@@ -30,7 +30,7 @@ Azure Media Services lets you deliver live events to your customers on the Azure
 
 ## Live Event types
 
-A [Live Event](https://docs.microsoft.com/rest/api/media/liveevents) can be one of two types: pass-through or live encoding. The types are set during creation using [LiveEventEncodingType](https://docs.microsoft.com/rest/api/media/liveevents/create#liveeventencodingtype):
+A [Live Event](https://docs.microsoft.com/rest/api/media/liveevents) can be set to either a *pass-through* (an on-premises live encoder sends a multiple bitrate stream) or *live encoding* (an on-premises live encoder sends a single bitrate stream). 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 stream passes through the Live Event without any further processing. Also called the pass-through mode.
 * **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/bitrates pairs.

articles/media-services/latest/live-streaming-overview.md

@@ -48,7 +48,7 @@ Dynamic filtering is used to control the number of tracks, formats, bitrates, an
 
 ## Live Event types
 
-[Live Events](https://docs.microsoft.com/rest/api/media/liveevents) are responsible for ingesting and processing the live video feeds. A Live Event can be one of two types: pass-through and live encoding. For details about live streaming in Media Services v3, see [Live Events and Live Outputs](live-events-outputs-concept.md).
+[Live Events](https://docs.microsoft.com/rest/api/media/liveevents) are responsible for ingesting and processing the live video feeds. A live event can be set to either a *pass-through* (an on-premises live encoder sends a multiple bitrate stream) or *live encoding* (an on-premises live encoder sends a single bitrate stream). For details about live streaming in Media Services v3, see [Live Events and Live Outputs](live-events-outputs-concept.md).
 
 ### Pass-through
 

articles/media-services/latest/recommended-on-premises-live-encoders.md

@@ -110,7 +110,7 @@ As an Azure Media Services on-premises encoder partner, Media Services promotes
 ### Pass-through Live Event verification
 
 1. In your Media Services account, make sure that the **Streaming Endpoint** is running. 
-2. Create and start the **pass-through** Live Event. <br/> For more information, see [Live Event states and billing](live-event-states-billing.md).
+2. Create and start the **pass-through** live event. <br/> For more information, see [Live Event states and billing](live-event-states-billing.md).
 3. Get the ingest URLs and configure your on-premises encoder to use the URL to send a multi-bitrate live stream to Media Services.
 4. Get the preview URL and use it to verify that the input from the encoder is actually being received.
 5. Create a new **Asset** object.