fixed errors

Author: IngridAtMicrosoft

articles/media-services/latest/TOC.yml

@@ -516,7 +516,7 @@
     - name: Subclip a video
       href: transform-subclip-video-how-to.md
       displayName: clip, highlight, clips, edit, edit decision list, edl, trim, head, tail, clipping, trimming, editing, subclipping, remove
-    - name: Customize encoder tranforms
+    - name: Customize encoder transforms
       href: transform-custom-transform-how-to.md
       displayName: custom, preset, custom preset, custom encoding, user defined, customize, presets, transcode, encode, encoding, encoder, MES, Standard encoder, .NET, transform, custom transform
     - name: Create an overlay transform

articles/media-services/latest/concept-media-reserved-units.md

@@ -19,15 +19,15 @@ ms.author: inhenkel
 
 [!INCLUDE [media services api v3 logo](./includes/v3-hr.md)]
 
-Media Reserved Units (MRUs) were previously used in Azure Media Services v2 to control encoding concurrency and performance. You no longer need to manage MRUs or request quota increases for any media services account as the system will automatically scale up and down based on load. You will also see performance that is equal to or improved in comparison to using MRUs. 
+Media Reserved Units (MRUs) were previously used in Azure Media Services v2 to control encoding concurrency and performance. You no longer need to manage MRUs or request quota increases for any media services account as the system will automatically scale up and down based on load. You'll also see performance that is equal to or improved in comparison to using MRUs. 
 
-If you have an account that was created using a version prior to the 2020-05-01 API, you will still have access to API’s for managing MRUs, however none of the MRU configuration that you set will be used to control encoding concurrency or performance. If you don’t see the option to manage MRUs in the Azure portal, you have an account that was created with the 2020-05-01 API or later. 
+If you have an account that was created using a version prior to the 2020-05-01 API, you'll still have access to APIs for managing MRUs, however none of the MRU configuration that you set will be used to control encoding concurrency or performance. If you don’t see the option to manage MRUs in the Azure portal, you have an account that was created with the 2020-05-01 API or later. 
 
 ## Billing
 
-While there were previously charges for Media Reserved Units, as of April 17, 2021 there are no longer any charges for accounts that have configuration for Media Reserved Units. For more information on billing for encoding jobs, please see [Encoding video and audio with Media Services](encoding-concept.md)
+While there were previously charges for Media Reserved Units, as of April 17, 2021 there are no longer any charges for accounts that have configuration for Media Reserved Units. For more information on billing for encoding jobs, see [Encoding video and audio with Media Services](encoding-concept.md)
 
-For accounts created in with the **2020-05-01** version of the API (i.e. the v3 version) or through the Azure portal, scaling and media reserved units are no longer required. Scaling is now automatically handled by the service internally. Media reserved units are no longer needed or supported for any Azure Media Services account. See [Media reserved units (legacy)](concept-media-reserved-units.md) for additional information.
+For accounts created in with the **2020-05-01** version of the API, that is, the v3 version, or through the Azure portal, scaling and media reserved units are no longer required. Scaling is now automatically handled by the service internally. Media reserved units are no longer needed or supported for any Azure Media Services account. See [Media reserved units (legacy)](concept-media-reserved-units.md) for additional information.
 
 ## See also
 

articles/media-services/latest/drm-get-content-key-policy-how-to.md

@@ -15,7 +15,7 @@ ms.author: inhenkel
 
 One of the key design principles of the v3 API is to make the API more secure. v3 APIs do not return secrets or credentials on **Get** or **List** operations. See the detailed explanation here: For more information, see [Azure RBAC and Media Services accounts](security-rbac-concept.md)
 
-The example in this article shows how to to get a signing key from the existing policy.
+The example in this article shows how to get a signing key from the existing policy.
 
 ## Download
 

articles/media-services/latest/encode-concept-preset-overrides.md

@@ -32,7 +32,7 @@ When encoding or using analytics with Media Services you can define custom prese
 
 Preset overrides allow you the ability to pass in a customized preset that will override the settings supplied to a transform object after it was first created.  This property is available on the [job output asset](/dotnet/api/microsoft.azure.management.media.models.joboutputasset) when submitting a new job to a transform.
 
-This can be useful for situations where you need to override some properties of your custom defined transforms, or a property on a built-in preset. For example, consider the scenario where you have created a custom transform that uses the [audio analyzer built-in preset](/rest/api/media/transforms/create-or-update#audioanalyzerpreset), but you initially set up that preset to use the audio language setting of "en-us" for English.  This would result in a transform where each jobs submitted would be sent to the speech-to-text transcription engine as US English only. Every job submitted to that transform would be locked to the "en-us" language setting. You could work around this scenario by having a transform defined for every language, but that would be much more difficult to manage and you could hit transform quota limitations in your account.
+This can be useful for situations where you need to override some properties of your custom defined transforms, or a property on a built-in preset. For example, consider the scenario where you have created a custom transform that uses the [audio analyzer built-in preset](/rest/api/media/transforms/create-or-update#audioanalyzerpreset), but you initially set up that preset to use the audio language setting of "en-us" for English.  This would result in a transform where each job submitted would be sent to the speech-to-text transcription engine as US English only. Every job submitted to that transform would be locked to the "en-us" language setting. You could work around this scenario by having a transform defined for every language, but that would be much more difficult to manage and you could hit transform quota limitations in your account.
 To best solve for this scenario, you use a preset override on the job output asset prior to submitting the job to the transform.  You can then define a single "Audio transcription" transform and pass in the required language settings per-job.
 
 The preset override provides you a way to pass in a new custom preset definition with each job submitted to the transform. This property is available on the [job output](/dotnet/api/microsoft.azure.management.media.models.joboutput) entity in all SDK versions based off the 2021-06-01 version of the API.
@@ -45,7 +45,7 @@ For reference, see the [presetOverride](https://github.com/Azure/azure-rest-api-
 
 ## Example of preset override in .NET
 
-A complete example using the .NET SDK for Media Services showing how to use preset override with a basic audio analyzer transform is available in github.
+A complete example using the .NET SDK for Media Services showing how to use preset override with a basic audio analyzer transform is available in GitHub.
 See the [Analyze a media file with a audio analyzer preset](https://github.com/Azure-Samples/media-services-v3-dotnet/tree/main/AudioAnalytics/AudioAnalyzer) sample for details on how to use the preset override property of the job output.
 
 ## Sample code of preset override in .NET

articles/media-services/latest/encode-dynamic-packaging-concept.md

@@ -26,7 +26,7 @@ The advantages of just-in-time packaging are the following:
 * You can store all your files in standard MP4 file format
 * You do not need to store multiple copies of static packaged HLS and DASH formats in blob storage, reducing the amount of video content stored and lowering your overall costs of storage
 * You can instantly take advantage of new protocol updates and changes to the specifications as they evolve over time without need of re-packaging the static content in your catalog
-* You can deliver content with our without encryption and DRM using the same MP4 files in storage
+* You can deliver content with or without encryption and DRM using the same MP4 files in storage
 * You can dynamically filter or alter the manifests with simple asset-level or global filters to remove specific tracks, resolutions, languages, or provide shorter highlight clips from the same MP4 files without re-encoding or re-rendering the content. 
 
 ## To prepare your source files for delivery

articles/media-services/latest/job-download-results-how-to.md

@@ -19,7 +19,7 @@ This article demonstrates how to download the results using Java and .NET SDKs.
 
 ## Methods
 
-## [.NEt](#tab/net/)
+## [.NET](#tab/net/)
 
 ```csharp
 /// <summary>
@@ -66,6 +66,8 @@ private async static Task DownloadResults(IAzureMediaServicesClient client, stri
 }
 ```
 
+## Code sample
+
 See the full code sample: [EncodingWithMESPredefinedPreset](https://github.com/Azure-Samples/media-services-v3-dotnet/blob/main/VideoEncoding/Encoding_PredefinedPreset/Program.cs)
 
 ---

articles/media-services/latest/job-input-from-http-how-to.md

@@ -22,6 +22,8 @@ In Media Services v3, when you submit Jobs to process your videos, you have to t
 > [!TIP]
 > Before you start developing, review [Developing with Media Services v3 APIs](media-services-apis-overview.md) (includes information on accessing APIs, naming conventions, etc.)
 
+## Methods
+
 ## [.NET](#tab/net/)
 
 ## .NET sample

articles/media-services/latest/release-notes.md

@@ -285,7 +285,7 @@ Azure Media Services is now available in the Norway East region in the Azure por
 
 ### Basic Audio Analysis
 
-The Audio Analysis preset now includes a Basic mode pricing tier. The new Basic Audio Analyzer mode provides a low-cost option to extract speech transcription, and format output captions and subtitles. This mode performs speech-to-text transcription and generation of a VTT subtitle/caption file. The output of this mode includes an Insights JSON file including only the keywords, transcription,and timing information. Automatic language detection and speaker diarization are not included in this mode. See the list of [supported languages.](analyze-video-audio-files-concept.md#built-in-presets)
+The Audio Analysis preset now includes a Basic mode pricing tier. The new Basic Audio Analyzer mode provides a low-cost option to extract speech transcription, and format output captions and subtitles. This mode performs speech-to-text transcription and generation of a VTT subtitle/caption file. The output of this mode includes an Insights JSON file including only the keywords, transcription, and timing information. Automatic language detection and speaker diarization are not included in this mode. See the list of [supported languages.](analyze-video-audio-files-concept.md#built-in-presets)
 
 Customers using Indexer v1 and Indexer v2 should migrate to the Basic Audio Analysis preset.
 
@@ -596,7 +596,7 @@ Starting with this release, you can use Resource Manager templates to create Liv
 The following improvements were introduced:
 
 - Ingest from HTTP(s) URLs or Azure Blob Storage SAS URLs.
-- Specify you own container names for Assets. 
+- Specify your own container names for Assets.
 - Easier output support to create custom workflows with Azure Functions.
 
 #### New Transform object

articles/media-services/latest/transform-create-copy-video-audio-how-to.md

@@ -16,7 +16,7 @@ ms.author: inhenkel
 
 This article shows how to create a `CopyVideo/CopyAudio` transform.
 
-This transform allows you have input video / input audio streams copied from the input asset to the output asset without any changes. This can be of value with multi bitrate encoding output where the input video and/or audio would be part of the output. It simply writes the manifest and other files needed to stream content.
+This transform allows you to have input video/input audio streams copied from the input asset to the output asset without any changes. This can be of value with multi bitrate encoding output where the input video and/or audio would be part of the output. It simply writes the manifest and other files needed to stream content.
 
 ## Prerequisites
 

articles/media-services/latest/transform-crop-how-to.md

@@ -28,7 +28,7 @@ Cropping is a pre-processing stage, so the *cropping parameters* in the encoding
 
 For example, your input video has a resolution of 1920x1080 pixels (16:9 aspect ratio), but has black bars (pillar boxes) at the left and right, so that only a 4:3 window or 1440x1080 pixels contains active video. You can crop the black bars, and encode the 1440x1080 area.
 
-## [.NEt](#tab/net/)
+## [.NET](#tab/net/)
 
 ## Transform code