Ensure/document that the first parameter to the native messaging host is the origin

chrome/common/extensions/docs/templates/articles/nativeMessaging.html

 <h1>Native Messaging</h1>
 <p>
 Extensions and apps can exchange messages with native applications using an API
 that is similar to the other <a href="messaging">message passing APIs</a>.
 Native applications that support this feature must register a
 <em>native messaging host</em> that knows how to communicate with the extension.
 Chrome starts the host in a separate process and communicates with it using
 standard input and standard output streams.
 
 <h2 id="native-messaging-host">Native messaging host</h2>
@@ skipping 111 matching lines @@
 Chrome starts each native messaging host in a separate process and communicates
 with it using standard input (<code>stdin</code>) and standard output
 (<code>stdout</code>). The same format is used to send messages in both
 directions: each message is serialized using JSON, UTF-8 encoded
 and is preceded with 32-bit message length in native byte order.
 The maximum size of a single message from the native messaging host is 1 MB,
 mainly to protect Chrome from misbehaving native applications. The maximum
 size of the message sent to the native messaging host is 4 GB.
 
 <p>
+The first argument to the native messaging host is the origin of the caller,
+usually <code>chrome-extension://[ID of whitelisted extension]</code>.
+This allows native messaging hosts to identify the source of the message when
+multiple extensions are specified in the <code>allowed_origins</code> key in the
+<a href="#native-messaging-host-manifest">native messaging host manifest</a>.
+<br>
+<b><em>Warning</em></b>: In Windows, in Chrome 54 and earlier, the origin was
+passed as the second parameter instead of the first parameter.
+
+<p>
 When a messaging port is created using $(ref:runtime.connectNative) Chrome
 starts native messaging host process and keeps it running until the port is
 destroyed. On the other hand, when a message is sent using
 $(ref:runtime.sendNativeMessage), without creating a messaging port, Chrome starts
 a new native messaging host process for each message. In that case the first
 message generated by the host process is handled as a response to the original
 request, i.e. Chrome will pass it to the response callback specified when
 $(ref:runtime.sendNativeMessage) is called. All other messages generated by the
 native messaging host in that case are ignored.
 
 <p>
-On Windows, the native messaging host gets passed a command line argument with
+On Windows, the native messaging host is also passed a command line argument with
 a handle to the calling chrome native window: <code>--parent-window=&ltdecimal
 handle value&gt</code>. This lets the native messaging host create native UI
 windows that are correctly focused.
 
 <h2 id="native-messaging-client">Connecting to a native application</h2>
 <p>
 Sending and receiving messages to and from a native application is very similar
 to cross-extension messaging. The main difference is that
 $(ref:runtime.connectNative) is used instead of $(ref:runtime.connect),
 and $(ref:runtime.sendNativeMessage) is used instead of $(ref:runtime.sendMessage).
@@ skipping 122 matching lines @@
 and
 <a href="https://developer.chrome.com/extensions/examples/api/nativeMessaging/host.zip">sample host</a>.
 
 Run <code>install_host.bat</code> (Windows) or
 <code>install_host.sh</code> (Linux / OS X) to install the native messaging
 host.
 Then <a href="getstarted#unpacked">load the app</a> and interact with the app.
 Run <code>uninstall_host.bat</code> or <code>uninstall_host.sh</code> to
 unregister the native messaging host when you are done.