more updates

Author: Juliako

articles/azure-video-indexer/indexing-configuration-guide.md

@@ -12,7 +12,7 @@ When indexing videos, users can use the default settings or adjusting many of th
 
 This article explains each of the options and the impact of each option to enable informed decisions when indexing. The article discusses the [Azure Video Indexer website](https://www.videoindexer.ai/) experience but the same options apply when submitting jobs through the API (see the [API guide](video-indexer-use-apis.md)). When indexing large volumes, follow he [at-scale guide](considerations-when-use-at-scale.md).  
 
-## Upload options
+## Upload and indexing options
 
 The initial upload screen presents options to define the video name, source language, and privacy settings.  
 
@@ -22,20 +22,25 @@ All the other setting options appear if you select Advanced options.
 
 :::image type="content" source="./media/indexing-configuration-guide/advanced-configuration.png" alt-text="The screen presents advanced options to define the video name, source language, and privacy settings."::: 
 
-## Default Settings 
+### Default Settings 
 
-By default, Azure Video Indexer is configured to a video source language of English, Privacy of private, Standard audio and video setting, and Streaming quality of single bitrate. This topic describes each option in detail
+By default, Azure Video Indexer is configured to a video source language of English, Privacy of private, Standard audio and video setting, and Streaming quality of single bitrate. 
+
+> [!TIP]
+> This topic describes each indexing option in detail.
 
 Below are a few examples of when using the default setting might not be a good fit: 
 
 - If you need insights observed people or matched person that is only available through Advanced Video. 
-- If you're only using Video Indexer for transcription and translation, indexing of both Audio & Video isn’t required, Basic audio should suffice. 
-- If you're consuming Video Indexer insights but have no need to generate a new media file, streaming isn’t necessary and No streaming should be selected to avoid the encoding job and its associated cost.  
+- If you're only using Azure Video Indexer for transcription and translation, indexing of both Audio & Video isn’t required, Basic audio should suffice. 
+- If you're consuming Azure Video Indexer insights but have no need to generate a new media file, streaming isn't necessary and **No streaming** should be selected to avoid the encoding job and its associated cost.  
 - If a video is primarily in a language that isn't English.  
 
-## Video source language 
+### Video source language 
+
+If you're aware of the language spoken in the video, select the language from the video source language list. If you're unsure of the language of the video, choose **Auto-detect single language**. When uploading and indexing your video, Azure Video Indexer will use language identification (LID) to detect the videos language and generate transcription and insights with the detected language. 
 
-If you're aware of the language spoken in the video, select the language from the Video source language list. If you're unsure of the language of the video, choose **Auto-detect single language**. When uploading and indexing your video and Video Indexer will use language identification (LID) to detect the videos language and generate transcription and insights with the detected language. If the video may contain multiple languages and you aren't sure which ones, select **Auto-detect multi-language**; in this case, multi-language (MLID) detection will be applied when uploading and indexing your video. 
+If the video may contain multiple languages and you aren't sure which ones, select **Auto-detect multi-language**. In this case, multi-language (MLID) detection will be applied when uploading and indexing your video. 
 
 While auto-detect is a great option when the language in your videos varies, there are two points to consider when using LID or MLID: 
 
@@ -52,9 +57,9 @@ This option allows you to determine if the insights should only be accessible to
 
 When indexing a video with the default settings, beware each of the audio and video indexing options may be priced differently. See [Azure Video Indexer pricing](https://azure.microsoft.com/pricing/details/video-indexer/) for details. 
 
-Below are the indexing type options with details of their insights provided. To modify the indexing type, select **Advanced settings*.. 
+Below are the indexing type options with details of their insights provided. To modify the indexing type, select **Advanced settings**. 
 
-|Audio only|Video only |Audio & Video 
+|Audio only|Video only |Audio & Video |
 |---|---|---|
 |Basic |||
 |Standard| Standard |Standard |
@@ -86,11 +91,14 @@ When indexing a video, you can decide if encoding of the file should occur which
 
 Upload > Encode (optional) > Index & Analysis > Publish for streaming (optional) 
 
-Encoding and streaming operations are performed by and billed by Azure Media Services. There are more operations associated with creation of a streaming video; a Streaming Endpoint and the egress traffic that depends on the number of video playbacks, video playback length, and the video quality (bitrate).  
+Encoding and streaming operations are performed by and billed by Azure Media Services. There are more operations associated with creation of a streaming video: 
+
+- a Streaming Endpoint and 
+- the egress traffic that depends on the number of video playbacks, video playback length, and the video quality (bitrate).  
 
-There are several aspects that influence the total costs of the encoding job. The first is if the encoding is with single or adaptive streaming. This will create either a single output or multiple encoding quality outputs. Each output is billed separately and depends on the source quality of the video you uploaded to Video Indexer.  
+There are several aspects that influence the total costs of the encoding job. The first is if the encoding is with single or adaptive streaming. This will create either a single output or multiple encoding quality outputs. Each output is billed separately and depends on the source quality of the video you uploaded to Azure Video Indexer.  
 
-For Media Services pricing information, see [pricing](https://azure.microsoft.com/pricing/details/media-services/#pricing) for encoding pricing details. 
+For Media Services encoding pricing details, see [pricing](https://azure.microsoft.com/pricing/details/media-services/#pricing). 
 
 When indexing a video, default streaming settings are applied. Below are the streaming type options that can be modified if you, select **Advanced** settings and go to **Streaming quality**. 
 
@@ -99,20 +107,22 @@ When indexing a video, default streaming settings are applied. Below are the str
 
 **Single bitrate** - With Single Bitrate, the standard Media Services encoder cost will apply for the output. If the video height is greater than or equal to 720p HD, Azure Video Indexer encodes it with a resolution of 1280 x 720. Otherwise, it's encoded as 640 x 468. The default setting is content-aware encoding. 
 
-**Adaptive bitrate** - With Adaptive Bitrate, if you upload a video in 720p HD single bitrate to Video Indexer and select Adaptive Bitrate, the encoder will use [AdaptiveStreaming preset](/rest/api/media/transforms/create-or-update?tabs=HTTP#encodernamedpreset). An output of 720p HD (no output exceeding 720p HD is created) and several lower quality outputs are created (for playback on smaller screens/low bandwidth environments). Each output will use the Media Encoder Standard base price and apply a multiplier for each output. The multiplier is 2x for HD, 1x for non-HD, and 0.25 for audio and billing is per minute of the input video. 
-
-Example: If you index a video in the US East region that is 40 minutes in length and is 720p HP and have selecting the streaming option of Adaptive Bitrate, 3 outputs will be created - 1 HD (multiplied by 2), 1 SD (multiplied by 1) and 1 audio track (multiplied by 0.25). This will total to (2+1+0.25) * 40 = 130 billable output minutes.  
-
-Output minutes (standard encoder): 130 x $0.015/minute = $1.95 
+**Adaptive bitrate** - With Adaptive Bitrate, if you upload a video in 720p HD single bitrate to Azure Video Indexer and select Adaptive Bitrate, the encoder will use the [AdaptiveStreaming](/rest/api/media/transforms/create-or-update?tabs=HTTP#encodernamedpreset) preset. An output of 720p HD (no output exceeding 720p HD is created) and several lower quality outputs are created (for playback on smaller screens/low bandwidth environments). Each output will use the Media Encoder Standard base price and apply a multiplier for each output. The multiplier is 2x for HD, 1x for non-HD, and 0.25 for audio and billing is per minute of the input video. 
 
 **No streaming** 
 
-Insights are generated but no streaming operation is performed and the video isn't available on the Video Indexer website.  When No streaming is selected, you aren't billed for encoding. 
+Insights are generated but no streaming operation is performed and the video isn't available on the Azure Video Indexer website.  When No streaming is selected, you aren't billed for encoding. 
 
-## Customizing content models - People/Animated characters and Brand categories 
+## Customizing content models - people, animated characters, and brand categories 
 
 Azure Video Indexer allows you to customize some of its models to be adapted to your specific use case. These models include animated characters, brands, language, and person. If you have customized models, this section enables you to configure if one of the created models should be used for the indexing. 
 
+## Pricing calculation example
+
+If you index a video in the US East region that is 40 minutes in length and is 720p HP and have selecting the streaming option of **Adaptive bitrate**, 3 outputs will be created - 1 HD (multiplied by 2), 1 SD (multiplied by 1) and 1 audio track (multiplied by 0.25). This will total to (2+1+0.25) * 40 = 130 billable output minutes.  
+
+Output minutes (standard encoder): 130 x $0.015/minute = $1.95 
+
 ## Next steps
 
 Learn more about [language support and supported languages](language-support.md).