Commits

Anonymous committed 3ad418b

fixed misc typos and spelling in introduction

  • Participants
  • Parent commits 6f0bdeb

Comments (0)

Files changed (1)

File source/introduction.txt

    maintain it for their users, i.e. system administrators. Thus, We have to be
    sure to explain the basics at some point: sys.path and PYTHONPATH at least.
 
-.. This section was mostly extracted from the install documenation
+.. This section was mostly extracted from the install documentation
    at: <http://docs.python.org/install/index.html>
 
 .. topic:: Abstract
 contains paths to the directories where the extra packages are
 installed.
 
-.. note:: For details on the ``.pth`` file, please refer to `modyfing python's search path <http://docs.python.org/install/index.html#inst-search-path>`_. In short, when a new package is installed using :mod:`distutils` or `one of its extenders <installation>`_, the contents of the package are dropped into the ``site-packages`` directory and then the name of the new package directory is added to a ``.pth`` file. This allows Python upon the next startup to see the new package. 
+.. note:: For details on the ``.pth`` file, please refer to `modifying Python's search path <http://docs.python.org/install/index.html#inst-search-path>`_. In short, when a new package is installed using :mod:`distutils` or `one of its extenders <installation>`_, the contents of the package are dropped into the ``site-packages`` directory and then the name of the new package directory is added to a ``.pth`` file. This allows Python upon the next startup to see the new package. 
 
 Benefits of packaging
 =====================
 - Accounting
       Package managers can maintain lists of things installed and other metadata like the version installed etc. which makes is easy for the user to know what are the things his system has. (see :ref:`pip_info`)
 
-- Unistall
+- Uninstall
       Package managers can give you push button ways of removing a package from your environment. (see :ref:`pip_info`)
 
 - Search
 
 The :mod:`distutils` module is provides the basics for packaging Python. Unfortunately, the :mod:`distutils` module is riddled with a few problems, which is why a small group of python developers is working on :mod:`distutils2`. However, until :mod:`distutils2` is complete, it is recommended that the :term:`Developer` either use pure :mod:`distutils` or the `Distribute package <distribute_info_>`_ for packaging Python software.
 
-.. seealso:: For more information about the :mod:`distutils2` package, you can take a look at the :doc:`future` document.
+.. see also:: For more information about the :mod:`distutils2` package, you can take a look at the :doc:`future` document.
 
-In the mean time, if a package requires the ``setuptools`` package, it is our recommendation that you install the `Distribute`, which provides a more up to date version of ``setuptools`` than does the `orignal Setuptools package <http://pypi.python.org/pypi/setuptools/>`_.
+In the mean time, if a package requires the ``setuptools`` package, it is our recommendation that you install the `Distribute` package, which provides a more up to date version of ``setuptools`` than does the `original Setuptools package <http://pypi.python.org/pypi/setuptools/>`_.
 
 In the :doc:`future <future>` :mod:`distutils2` will replace :mod:`setuptools` and :mod:`distutils`, which will also remove the need for :ref:`Distribute <distribute_info>`. And as stated before :mod:`distutils` will be removed from the :term:`standard library`. For more information, please refer to the :doc:`future`.
 
 Creating a Micro-Ecosystem with :mod:`virtualenv`
 =================================================
 
-Here we have a small digression to briefly discuss :doc:`Virtual Environments <virtualenv>`, which will be covered later in this guide. In most situations, the ``site-packages`` directory is part of the system Python installation and not writable by unprivileged users. Also, it's useful to have a solid reliable installation of the language which we can use. Experimental packages shouldn't be mixed with the stable ones if we want to keep this quality. In order to achieve this, most Python developers use the :doc:`virtualenv </virtualenv>` package which allows people to create a *virtual* installation of Python. This replicates the ``site-packages`` directory in an user writeable area. The ``site-packages`` directory located in the :doc:`virtualenv` is in addition to the global one. While orthogonal to the whole package installation process, it's an extremely useful and natural way to work and so the whole thing will be mentioned again.  The installation and usage of ``virtualenv`` is covered in :doc:`virtualenv` document.
+Here we have a small digression to briefly discuss :doc:`Virtual Environments <virtualenv>`, which will be covered later in this guide. In most situations, the ``site-packages`` directory is part of the system Python installation and not writable by unprivileged users. Also, it's useful to have a solid reliable installation of the language which we can use. Experimental packages shouldn't be mixed with the stable ones if we want to keep this quality. In order to achieve this, most Python developers use the :doc:`virtualenv </virtualenv>` package which allows people to create a *virtual* installation of Python. This replicates the ``site-packages`` directory in an user writable area. The ``site-packages`` directory located in the :doc:`virtualenv` is in addition to the global one. While orthogonal to the whole package installation process, it's an extremely useful and natural way to work and so the whole thing will be mentioned again.  The installation and usage of ``virtualenv`` is covered in :doc:`virtualenv` document.