Merge pull request #3164 from DMBuce/doc-update

Doc update

docsite/latest/rst/examples.rst

@@ -135,8 +135,9 @@ Ensure a package is not installed::
 
     $ ansible webservers -m yum -a "name=acme state=removed"
 
-Currently Ansible only has modules for managing packages with yum and apt.  You can install
-for other packages for now using the command module or (better!) contribute a module
+Ansible has modules for managing packages under many platforms.  If your package manager
+does not have a module available for it, you can install
+for other packages using the command module or (better!) contribute a module
 for other package managers.  Stop by the mailing list for info/details.
 
 Users and Groups

docsite/latest/rst/gettingstarted.rst

@@ -45,7 +45,7 @@ also need:
    Ansible) are not
    switching over yet.  However, some Linux distributions (Gentoo, Arch) may not have a 
    Python 2.X interpreter installed by default.  On those systems, you should install one, and set
-   the 'ansible_python_interpreter' variable in inventory to point at your 2.X python.  Distributions
+   the 'ansible_python_interpreter' variable in inventory (see :doc:`patterns`) to point at your 2.X python.  Distributions
    like Red Hat Enterprise Linux, CentOS, Fedora, and Ubuntu all have a 2.X interpreter installed
    by default and this does not apply to those distributions.  This is also true of nearly all
    Unix systems.  If you need to bootstrap these remote systems by installing Python 2.X, 
@@ -236,7 +236,7 @@ If you have python3 installed on Arch, you probably want to symlink python to py
 
     $ sudo ln -sf /usr/bin/python2 /usr/bin/python
 
-You should also set a 'ansible_python_interpreter' inventory variable for hosts that have python 
+You should also set a 'ansible_python_interpreter' inventory variable (see :doc:`patterns`) for hosts that have python 
 pointing to python3, so the right python can be found on the managed nodes.
 
 Tagged Releases