[NTP] Rephrase the comment in components/ntp_snippets/OWNERS.

components/ntp_snippets/OWNERS

Index: components/ntp_snippets/OWNERS
diff --git a/components/ntp_snippets/OWNERS b/components/ntp_snippets/OWNERS
index d4be5146e84d8b52e206fa6fe58bf49d27bd6467..c8c8515dcc5a3517fbba37c89eac68f78b4f8bdc 100644
--- a/components/ntp_snippets/OWNERS
+++ b/components/ntp_snippets/OWNERS
@@ -1,11 +1,10 @@
-# Main owners:
 bauerb@chromium.org
 jkrcal@chromium.org
 treib@chromium.org
 
-# For ios:
-noyau@chromium.org
-
-# Fallback, in case all of the above are OOO:
+# Unsure who to ask? Choose from the above.

[Marc Treib, 2017/02/02 14:27:31]

nitty nit: It's kinda weird that this comment is attached to this block, but
really concerns the above one. Not sure how to formulate it better though.

[sfiera, 2017/02/02 14:41:07]

I think that `git cl owners` will show you a comment that's after the username
it suggests. So, I think a more useful way of formatting the file would be:

bauerb@chromium.org    # primary owner
vitaliii@chromium.org  # secondary owner, primary for offline
noyau@chromium.org     # ios owner

so that someone that runs the command will have a good idea whether to accept
the suggestion or hold out for another.

[vitaliii, 2017/02/03 08:59:04]

I see your point. However, previously we had no end line comments for a very
long time and I do not recall getting random CLs to review. Thus, I assume that
suggested usage is rather unlikely. Let's try as it is in this CL and if we
start getting random CLs, then move to your approach. 

 markusheintz@chromium.org
 vitaliii@chromium.org
+
+# For ios:
+noyau@chromium.org