NaCl docs: fix clumsy sentence

native_client_sdk/doc_generated/faq.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="frequently-asked-questions">
 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#what-is-native-client-good-for" id="id1">What is Native Client Good For?</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#why-did-google-build-native-client" id="id2">Why did Google build Native Client?</a></li>
 <li><a class="reference internal" href="#when-should-i-use-portable-native-client-instead-of-native-client" id="id3">When should I use Portable Native Client instead of Native Client?</a></li>
@@ skipping 409 matching lines @@
 <p>The following kinds of code may be more challenging to port:</p>
 <ul class="small-gap">
 <li>Code that does direct <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">TCP</a> or
 <a class="reference external" href="pepper_stable/cpp/classpp_1_1_u_d_p_socket">UDP</a> networking. For security
 reasons these APIs are only available to <a class="reference external" href="/apps/about_apps">packaged applications</a> after asking for the appropriate permissions, not on the
 open web. Native Client is otherwise restricted to the networking APIs
 available in the browser. You may want to use to <a class="reference external" href="nacl_io">nacl_io library</a>
 to use POSIX-like sockets.</li>
 <li>Code that creates processes, including UNIX <code>fork</code>, won&#8217;t function
 as-is. However, threads are supported. You can nonetheless create new
-<code>&lt;embed&gt;</code> tags in your HTML page to launch new PNaCl processes, even using
-new <code>.pexe</code> files that your existing <code>.pexe</code> saved in a local
+<code>&lt;embed&gt;</code> tags in your HTML page to launch new PNaCl processes. You can even
+use new <code>.pexe</code> files that your existing <code>.pexe</code> saved in a local
 filesystem. This is somewhat akin to <code>execve</code>, but the process management
 has to go through <code>postMessage</code> to JavaScript in order to create the new
 <code>&lt;embed&gt;</code>.</li>
 <li>Code that needs to do local file I/O. Native Client is restricted to accessing
 URLs and to local storage in the browser (the Pepper <a class="reference internal" href="/native-client/devguide/coding/file-io.html"><em>File IO API</em></a> has access to the same per-application storage that
 JavaScript has via Local Storage). HTML5 File System can be used, among
 others. For POSIX compatabiliy the Native Client SDK includes a library called
 nacl_io which allows the application to interact with all these types of files
 via standard POSIX I/O functions (e.g. <code>open</code> / <code>fopen</code> / <code>read</code> /
 <code>write</code> / ...). See <a class="reference internal" href="/native-client/devguide/coding/nacl_io.html"><em>Using NaCl I/O</em></a> for more
@@ skipping 43 matching lines @@
 you&#8217;re loading the correct <code>.nexe</code> file by building a separate
 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest file to
 let the browser select the correct <code>.nexe</code> file. Note: the need to
 select a processor-specific <code>.nexe</code> goes away with Portable Native
 Client.</li>
 <li>If things still aren&#8217;t working, <a class="reference internal" href="/native-client/help.html"><em>ask for help</em></a>!</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}