Adding a couple of trivial doc bug fixes.

native_client_sdk/src/doc/sdk/examples.rst

 .. _sdk-examples-2:
 
 Running the SDK Examples
 ========================
 
 Every Native Client SDK bundle comes with a folder of example applications.
 Each example demonstrates one or two key Native Client programming concepts.
 After you've :doc:`downloaded the SDK <download>`, follow the instructions
 on this page to build and run the examples.
 
@@ skipping 199 matching lines @@
 ``TOOLCHAIN`` and ``CONFIG`` parameters to make::
 
   $ make run TOOLCHAIN=pnacl CONFIG=Debug
 
 .. _run_sdk_examples_as_packaged:
 
 Run the SDK examples as packaged apps
 -------------------------------------
 
 Each example can also be launched as a packaged app. For more information about
-using Native Client for packaged apps, see :ref:`Packaged appliction
+using Native Client for packaged apps, see :ref:`Packaged application
 <distributing_packaged>`.  For general information about packaged apps, see the
 `Chrome apps documentation </apps/about_apps>`_.
 
 Some Pepper features, such as TCP/UDP socket access, are only allowed in
 packaged apps. The examples that use these features must be run as packaged
 apps, by using the ``make run_package`` command::
 
   $ make run_package
 
 You can use ``TOOLCHAIN`` and ``CONFIG`` parameters as above to run with a
@@ skipping 27 matching lines @@
 
 At this point, you can use the standard GDB commands to debug your NaCl module.
 The most common commands you will use to debug are ``continue``, ``step``,
 ``next``, ``break`` and ``backtrace``. See :doc:`Debugging
 <../devguide/devcycle/debugging>` for more information about debugging a Native Client
 application.
 
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |gear-icon| image:: /images/gear-icon.png