[patch] packaging guide

[Jordan Mantha]

Dean,
    Thanks for the contribution. I have applied your patch.

-Jordan Mantha

dean wrote:
> Hi,
> I've attached a small patch that just fixes some typos in
> introduction.xml and scenarios.xml in the packaging guide, hopefully
> it'll be of some use.
> 
> Dean 
> 
> 
> ------------------------------------------------------------------------
> 
> Index: introduction.xml
> ===================================================================
> --- introduction.xml	(revision 2360)
> +++ introduction.xml	(working copy)
> @@ -27,14 +27,14 @@
>  		<para>There are several reasons why you might want to learn how to package for
>  			Ubuntu. First, building and fixing &ubuntu; packages is a great way to
>  			contribute to the &ubuntu; community. It is also a good way to learn how
> -			&ubuntu; and the applications you have installed work. Or maybe, you want to
> +			&ubuntu; and the applications you have installed work, or maybe, you want to
>  			install a package that is not in the &ubuntu; repositories. Hopefully after you
>  			have completed this guide you will have the tools and knowledge you need to do
>  			all of these.</para>
>  	
>  		<para>This guide assumes that the reader has a reasonable knowledge of general
> -			linux tools and installation of linux software in &ubuntu;.  Baicaly, you should
> -			be able to use the terminal with ease ad be familiar with apt tools (for
> +			linux tools and installation of linux software in &ubuntu;.  Basically, you should
> +			be able to use the terminal with ease and be familiar with apt tools (for
>  			example, apt-get, aptitude or synaptic).</para>
>  		
>  		<para>Besides this guide, there are many resources available to people trying to
> Index: scenarios.xml
> ===================================================================
> --- scenarios.xml	(revision 2360)
> +++ scenarios.xml	(working copy)
> @@ -65,9 +65,9 @@
>  		<para>Now let's go into the source directory that we just unpacked:</para>
>  		<para><screen>cd hello-2.1.1/</screen></para>
>  
> -		<para>We see that this directory look like a typical source directory and if we
> -			where to compare this directory with one made from downloading the source
> -			tarball and unpacking it would be that we now have a new directory called
> +		<para>We see that this directory looks like a typical source directory and if we
> +			were to compare this directory with one made from downloading the source
> +			tarball and unpacking, it would be that we now have a new directory called
>  			debian in our source directory. This is the customary directory
>  			that holds all of the changes made by the packager. This allows for a
>  			separation of the packaging from the actual source code. Since the actual
> @@ -179,7 +179,7 @@
>  						version of the version of the <ulink
>  					url="http://www.debian.org/doc/debian-policy/">Debian Policy</ulink>
>  				that the package adheres to (in this case version
> -				3.6.1). and easy way to find the current version is <emphasis>dpkg -l
> +				3.6.1). an easy way to find the current version is <emphasis>dpkg -l
>  debian-policy</emphasis>.</para></listitem>
>  
>  				<listitem><para><emphasis role="bold">Build-Depends:</emphasis> One of the
> @@ -256,11 +256,11 @@
>  				
>  				<listitem><para><emphasis role="bold">Conflicts:</emphasis> Used for
>  						packages that will conflict with this package. Both cannot be
> -						installed a the same time. If one is being installed, the other
> +						installed at the same time. If one is being installed, the other
>  						will be removed.</para></listitem>
>  
>  				<listitem><para><emphasis role="bold">Description:</emphasis> Both a short
> -						and long description are used by package mangers. The format
> +						and long description are used by package managers. The format
>  						is:<screen>Description: <single line synopsis>
>   <extended description over several lines></screen> Note that there is one space at
>   the beginning of each line in the long description.</para></listitem>
> @@ -272,7 +272,7 @@
>  		<sect2>
>  			<title>copyright</title>
>  
> -			<para>This file give the copyright information. Generally copyright information
> +			<para>This file gives the copyright information. Generally copyright information
>  				is found in the <filename>COPYING</filename> file in the programs source
>  				directory. Information that should be included should be the names of the
>  				author and the packager, the URL for which the source came from, a
> @@ -510,9 +510,9 @@
>  			process of package building. With those scripts, building a Debian package
>  			become quite simple.  </para>
>  
> -		<para>In this scenario, we will build again the GNU Hello package, but this
> +		<para>In this scenario, we will again build the GNU Hello package, but this
>  			time we will be using the <application>debhelper</application> package. First,
> -			created a directory where your development files will be stored: </para>
> +			create a directory where your development files will be stored: </para>
>  
>  		<para><screen>mkdir hello-debhelper</screen></para>
>  
> @@ -528,12 +528,12 @@
>  			</screen>
>  		</para>
>  
> -		<para>Replace SOMEKEY by your GNUPG key. When the program finished, look in your
> +		<para>Replace SOMEKEY with your GNUPG key. When the program is finished, look in your
>  			directory, you have now created a .deb file! The debuild command is actually
> -			just a call of the ``make'' program. Instead of using a makefile, it use the
> +			just a call of the ``make'' program. Instead of using a makefile, it uses the
>  			``rules'' file located in the debian/ directory.</para>
>  		
> -		<para> Here the content of the debian/rules file.</para>
> +		<para> Here is the content of the debian/rules file.</para>
>  
>  		<para><screen> #!/usr/bin/make -f
>  
>