Update to Google Cloud Messaging document

Update to Google Cloud Messaging document

BUG=none
TBR=kalman@chromium.org

Committed: https://crrev.com/2772be9375a45782ba302812837a12ad13e3c268
Cr-Commit-Position: refs/heads/master@{#299952}

[jianli, 2014-09-12 18:57:35]

jianli@chromium.org changed reviewers:
+ mkearney@chromium.org

[mkearney1, 2014-10-02 00:52:49]

Main comments are simple enough and will hopefully remove some confusion about
linking to Android docs simply by warning the developer that's what they are
linking to.

It might be a good idea to add a note about this too-- though I'm hoping the
better approach is to aim for a generic set of server docs and update our links
once these are in place.

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
File chrome/common/extensions/docs/templates/articles/cloudMessaging.html
(right):

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
chrome/common/extensions/docs/templates/articles/cloudMessaging.html:146: GCM
connection server in one of two ways as described
Replace 'here' with something more descriptive, like:

"as described in the Android <a href="">Implementing GCM Server</a> document"

We will change this link to generic docs once they exist.

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
chrome/common/extensions/docs/templates/articles/cloudMessaging.html:171:
supports sending upstream messages from the client to your server. Your server
Same as comment above. Replace 'here' with something more descriptive, like:

"as described in the Android <a href="GCM Cloud Connection Server"></a>
document"

We will change this link to generic docs once they exist.

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
chrome/common/extensions/docs/templates/articles/cloudMessaging.html:306: 
Again, make sure to state specifically that you are linking to Android docs, and
put in the actual title of those docs (as described above). Do this for all
three hrefs below.

[jianli, 2014-10-14 18:00:43]

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
File chrome/common/extensions/docs/templates/articles/cloudMessaging.html
(right):

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
chrome/common/extensions/docs/templates/articles/cloudMessaging.html:146: GCM
connection server in one of two ways as described
On 2014/10/02 00:52:49, mkearney1 wrote:
> Replace 'here' with something more descriptive, like:
> 
> "as described in the Android <a href="">Implementing GCM Server</a> document"
> 
> We will change this link to generic docs once they exist.

Done.

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
chrome/common/extensions/docs/templates/articles/cloudMessaging.html:171:
supports sending upstream messages from the client to your server. Your server
On 2014/10/02 00:52:49, mkearney1 wrote:
> Same as comment above. Replace 'here' with something more descriptive, like:
> 
> "as described in the Android <a href="GCM Cloud Connection Server"></a>
> document"
> 
> We will change this link to generic docs once they exist.

Done.

https://codereview.chromium.org/564163002/diff/1/chrome/common/extensions/doc...
chrome/common/extensions/docs/templates/articles/cloudMessaging.html:306: 
On 2014/10/02 00:52:49, mkearney1 wrote:
> Again, make sure to state specifically that you are linking to Android docs,
and
> put in the actual title of those docs (as described above). Do this for all
> three hrefs below.

Done.

[mkearney1, 2014-10-16 16:28:50]

lgtm

[jianli, 2014-10-16 18:45:05]

The CQ bit was checked by jianli@chromium.org

[commit-bot: I haz the power, 2014-10-16 18:47:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/564163002/20001

[commit-bot: I haz the power, 2014-10-16 18:47:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/564163002/20001

[commit-bot: I haz the power, 2014-10-16 18:47:06]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-16 18:47:06]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[jianli, 2014-10-16 18:51:36]

The CQ bit was checked by jianli@chromium.org

[commit-bot: I haz the power, 2014-10-16 18:53:08]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/564163002/20001

[commit-bot: I haz the power, 2014-10-16 19:20:52]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-10-16 19:23:20]

Patchset 2 (id:??) landed as
https://crrev.com/2772be9375a45782ba302812837a12ad13e3c268
Cr-Commit-Position: refs/heads/master@{#299952}