| Index: native_client_sdk/src/doc/nacl-and-pnacl.rst
|
| diff --git a/native_client_sdk/src/doc/nacl-and-pnacl.rst b/native_client_sdk/src/doc/nacl-and-pnacl.rst
|
| index 7e9c2942016c9e1ead0066d86f3627d743f265e5..8db78c10a0fb2bb743b95278f837dc5db6385d7e 100644
|
| --- a/native_client_sdk/src/doc/nacl-and-pnacl.rst
|
| +++ b/native_client_sdk/src/doc/nacl-and-pnacl.rst
|
| @@ -16,12 +16,12 @@ Native Client (NaCl)
|
| ====================
|
|
|
| Native Client enables the execution of native code securely inside web
|
| -applications through the use of advanced `Software Fault Isolation (SFI)
|
| -techniques </native-client/community/talks#research>`_. Since its launch in
|
| -2011, Native Client has provided developers with the ability to harness a
|
| -client machine's computational power to a much fuller extent than traditional
|
| -web technologies, by running compiled C and C++ code at near-native speeds and
|
| -taking advantage of multiple cores with shared memory.
|
| +applications through the use of advanced Software Fault Isolation (SFI)
|
| +techniques. Since its launch in 2011, Native Client has provided developers
|
| +with the ability to harness a client machine's computational power to a much
|
| +fuller extent than traditional web technologies, by running compiled C and C++
|
| +code at near-native speeds and taking advantage of multiple cores with shared
|
| +memory.
|
|
|
| While Native Client provides operating system independence, it requires
|
| developers to generate architecture-specific executable
|
|
|