NaCl documentation: update FAQ and examples

NaCl documentation: update FAQ and examples

A few updates to the documentation, a developer pointed out some of the docs weren't quite clear.

TBR= sbc@chromium.org, jmedley@chromium.org
BUG=none
TEST=none

Committed: https://crrev.com/bd7a27361b8a72157ddbf25733a521022641481c
Cr-Commit-Position: refs/heads/master@{#315345}

[jpmedley, 2015-02-09 16:25:35]

lgtm

[JF, 2015-02-09 17:26:47]

New patchsets have been uploaded after l-g-t-m from jmedley@chromium.org

[JF, 2015-02-09 17:40:57]

The CQ bit was checked by jfb@chromium.org

[commit-bot: I haz the power, 2015-02-09 17:41:33]

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

[commit-bot: I haz the power, 2015-02-09 17:41:33]

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

[commit-bot: I haz the power, 2015-02-09 17:41:34]

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,
_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.

[JF, 2015-02-09 17:53:35]

jfb@chromium.org changed reviewers:
+ sbc@chromium.org
- sb@chromium.org

[JF, 2015-02-09 17:53:41]

The CQ bit was checked by jfb@chromium.org

[commit-bot: I haz the power, 2015-02-09 17:55:32]

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

[binji, 2015-02-09 18:13:42]

binji@chromium.org changed reviewers:
+ binji@chromium.org

[binji, 2015-02-09 18:13:42]

lgtm

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
File native_client_sdk/src/doc/faq.rst (right):

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
native_client_sdk/src/doc/faq.rst:498: reasons these APIs are only available to
`packaged applications
I believe these are just called Chrome Apps now. It seems that this is still
used in many places, though, so I suppose it's OK to leave it for now

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
native_client_sdk/src/doc/faq.rst:506: new ``.pexe`` files that your existing
``.pexe`` saved in a local
This sentence is clumsy. Split it into two sentences?

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
File native_client_sdk/src/doc/sdk/examples.rst (right):

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
native_client_sdk/src/doc/sdk/examples.rst:216:
<pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or `UDP
bad link

[commit-bot: I haz the power, 2015-02-09 18:22:23]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-02-09 18:23:04]

Patchset 3 (id:??) landed as
https://crrev.com/bd7a27361b8a72157ddbf25733a521022641481c
Cr-Commit-Position: refs/heads/master@{#315345}

[binji, 2015-02-09 18:54:52]

On 2015/02/09 18:23:04, I haz the power (commit-bot) wrote:
> Patchset 3 (id:??) landed as
> https://crrev.com/bd7a27361b8a72157ddbf25733a521022641481c
> Cr-Commit-Position: refs/heads/master@{#315345}

Hm, it looks like I shouldn't have lg'd that so fast. The CQ landed it before
you could fix those nits.

[JF, 2015-02-09 19:00:44]

On 2015/02/09 18:54:52, binji wrote:
> On 2015/02/09 18:23:04, I haz the power (commit-bot) wrote:
> > Patchset 3 (id:??) landed as
> > https://crrev.com/bd7a27361b8a72157ddbf25733a521022641481c
> > Cr-Commit-Position: refs/heads/master@{#315345}
> 
> Hm, it looks like I shouldn't have lg'd that so fast. The CQ landed it before
> you could fix those nits.

I'll fix in another CL.

[JF, 2015-02-09 19:25:40]

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
File native_client_sdk/src/doc/sdk/examples.rst (right):

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
native_client_sdk/src/doc/sdk/examples.rst:216:
<pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or `UDP
On 2015/02/09 18:13:42, binji wrote:
> bad link

Are you sure? This works:

https://developer.chrome.com/native-client/pepper_stable/cpp/classpp_1_1_u_d_...

[binji, 2015-02-09 21:29:51]

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
File native_client_sdk/src/doc/sdk/examples.rst (right):

https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
native_client_sdk/src/doc/sdk/examples.rst:216:
<pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or `UDP
On 2015/02/09 19:25:39, JF wrote:
> On 2015/02/09 18:13:42, binji wrote:
> > bad link
> 
> Are you sure? This works:
> 
>
https://developer.chrome.com/native-client/pepper_stable/cpp/classpp_1_1_u_d_...

I mean it looks like that's a link to udp, not tcp.

[JF, 2015-02-09 22:32:19]

On 2015/02/09 21:29:51, binji wrote:
>
https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
> File native_client_sdk/src/doc/sdk/examples.rst (right):
> 
>
https://codereview.chromium.org/886163005/diff/40001/native_client_sdk/src/do...
> native_client_sdk/src/doc/sdk/examples.rst:216:
> <pepper_stable/cpp/classpp_1_1_u_d_p_socket>`_ or `UDP
> On 2015/02/09 19:25:39, JF wrote:
> > On 2015/02/09 18:13:42, binji wrote:
> > > bad link
> > 
> > Are you sure? This works:
> > 
> >
>
https://developer.chrome.com/native-client/pepper_stable/cpp/classpp_1_1_u_d_...
> 
> I mean it looks like that's a link to udp, not tcp.

ack syn, will fix.