Merge pull request #78767 from Juliako/patch-76

Update live-events-outputs-concept.md

Author: PRMerger13

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

@@ -12,7 +12,7 @@ ms.workload: media
 ms.tgt_pltfrm: na
 ms.devlang: ne
 ms.topic: article
-ms.date: 06/03/2019
+ms.date: 06/04/2019
 ms.author: juliako
 
 ---
@@ -75,17 +75,17 @@ Once the Live Event is created, you can get ingest URLs that you will provide to
 
 You can either use non-vanity URLs or vanity URLs. 
 
+> [!NOTE] 
+> For an ingest URL to be predictive, set the "vanity" mode.
+
 * Non-vanity URL
 
     Non-vanity URL is the default mode in AMS v3. You potentially get the Live Event quickly but ingest URL is known only when the live event is started. The URL will change if you do stop/start the Live Event. <br/>Non-Vanity is useful in scenarios when an end user wants to stream using an app where the app wants to get a live event ASAP and having a dynamic ingest URL is not a problem.
 * Vanity URL
 
     Vanity mode is preferred by large media broadcasters who use hardware broadcast encoders and don't want to re-configure their encoders when they start the Live Event. They want a predictive ingest URL, which does not change over time.
 
-    To specity this mode, you set `vanityUrl` to `true` at creation time (default is `false`).
-
-> [!NOTE] 
-> For an ingest URL to be predictive, you need to use "vanity" mode and pass your own access token (to avoid a random token in the URL).
+    To specify this mode, you set `vanityUrl` to `true` at creation time (default is `false`). You also need to pass your own access token (to avoid a random token in the URL). Set `LiveEventInput.accessToken` to a a unique identifier at creation time. Once the mode is set it cannot be updated.
 
 ### Live ingest URL naming rules