AWS Security ChangesHomeSearch

AWS medialive documentation change

Service: medialive · 2026-04-07 · Documentation low

File: medialive/latest/ug/pipeline-lock.md

Summary

Changed terminology from 'video aligned pipeline locking' to 'video aligned locking' in two places and updated link text

Security assessment

This change is a terminology update for consistency. It does not introduce, modify, or address any security-related content. The change is purely editorial.

Diff

diff --git a/medialive/latest/ug/pipeline-lock.md b/medialive/latest/ug/pipeline-lock.md
index b92e0b9dc..c8e4e56be 100644
--- a//medialive/latest/ug/pipeline-lock.md
+++ b//medialive/latest/ug/pipeline-lock.md
@@ -34 +34 @@ When you use pipeline locking mode, you can choose the method that MediaLive use
-  * Video alignment: MediaLive uses visual signature comparison between encoders to synchronize the pipelines. This method does not require embedded timecodes and is useful when your input sources lack timecodes or have unreliable timecodes. For more information, see [Requirements for video aligned pipeline locking](./pipeline-locking-verify-input.html#pipeline-locking-video-alignment-inputs).
+  * Video alignment: MediaLive uses visual signature comparison between encoders to synchronize the pipelines. This method does not require embedded timecodes and is useful when your input sources lack timecodes or have unreliable timecodes. For more information, see [Requirements for video aligned locking](./pipeline-locking-verify-input.html#pipeline-locking-video-alignment-inputs).
@@ -56 +56 @@ When you use pipeline locking mode, you can choose the method that MediaLive use
-**Video aligned** pipeline locking applies only to the following types of outputs:
+**Video aligned** locking applies only to the following types of outputs: