edits

Author: John Deutscher

articles/media-services/media-services-specifications-live-timed-metadata.md

@@ -168,7 +168,7 @@ Refer to [MS-SSTR-Ingest] for requirements on live stream ingest. The following
 
 Each sparse fragment consists of a Movie Fragment Box (‘moof’) and Media Data Box (‘mdat’), where the ‘mdat’ box is the binary message.
 
-In order to achieve frame-accurate insertion of ads, the encoder MUST split the fragment at the presentation time where the cue is required to be inserted.  A new fragment MUST be created that begins with a newly created IDR frame, or Stream Access Points (SAP) of type 1 or 2, as defined in [ISO-14496-12] Annex I. This allows the Azure Media Packager to properly generate an HLS manifest (with precised signaling) and a DASH multi-period manifest where the new Period begins at the frame-accurate splice conditioned presentation time.
+In order to achieve frame-accurate insertion of ads, the encoder MUST split the fragment at the presentation time where the cue is required to be inserted.  A new fragment MUST be created that begins with a newly created IDR frame, or Stream Access Points (SAP) of type 1 or 2, as defined in [ISO-14496-12] Annex I. This allows the Azure Media Packager to properly generate an HLS manifest and a DASH multi-period manifest where the new Period begins at the frame-accurate splice conditioned presentation time.
 
 ### 2.2.1 Live Server Manifest Box