hand merged remaining unresolved files following the backout of 648b42a75739, which was a NON-trivial whitespace commit

16 files changed, 55 insertions, 55 deletions

diff --git a/user_guide/installation/index.html b/user_guide/installation/index.html
index f62aadb5e..87da5189f 100644
--- a/user_guide/installation/index.html
+++ b/user_guide/installation/index.html
@@ -61,24 +61,24 @@ Installation Instructions
 
 <ol>
 <li>Unzip the package.</li>
-<li>Upload the CodeIgniter folders and files to your server. Normally the index.php file will be at your root.</li>
-<li>Open the <dfn>application/config/config.php</dfn> file with a text editor and set your base URL. If you intend to use encryption or sessions, set your encryption key.</li>
+<li>Upload the CodeIgniter folders and files to your server.  Normally the index.php file will be at your root.</li>
+<li>Open the <dfn>application/config/config.php</dfn> file with a text editor and set your base URL.  If you intend to use encryption or sessions, set your encryption key.</li>
 <li>If you intend to use a database, open the <dfn>application/config/database.php</dfn> file with a text editor and set your database settings.</li>
 </ol>
 
 <p>If you wish to increase security by hiding the location of your CodeIgniter files you can rename the <dfn>system</dfn> and <dfn>application</dfn> folders
-to something more private. If you do rename them, you must open your main <kbd>index.php</kbd> file and set the <samp>$system_folder</samp> and <samp>$application_folder</samp>
+to something more private.  If you do rename them, you must open your main <kbd>index.php</kbd> file and set the <samp>$system_folder</samp> and <samp>$application_folder</samp>
 variables at the top of the file with the new name you've chosen.</p>
 
-<p>For the best security, both the <dfn>system</dfn> and any <dfn>application</dfn> folders should be placed above web root so that they are not directly accessible via a browser. By default, .htaccess files are included in each folder to help prevent direct access, but it is best to remove them from public access entirely in case the web server configuration changes or doesn't abide by the .htaccess.</p>
+<p>For the best security, both the <dfn>system</dfn> and any <dfn>application</dfn> folders should be placed above web root so that they are not directly accessible via a browser.  By default, .htaccess files are included in each folder to help prevent direct access, but it is best to remove them from public access entirely in case the web server configuration changes or doesn't abide by the .htaccess.</p>
 
 <p>After moving them, open your main <kdb>index.php</kbd> file and set the <samp>$system_folder</samp> and <samp>$application_folder</samp> variables, preferably with a full path, e.g. '<dfn>/www/MyUser/system</dfn>'.</p>
 
 <p>
-  One additional measure to take in production environments is to disable
-  PHP error reporting and any other development-only functionality. In CodeIgniter,
-  this can be done by setting the <kbd>ENVIRONMENT</kbd> constant, which is
-  more fully described on the <a href="../general/security.html">security page</a>.
+    One additional measure to take in production environments is to disable
+    PHP error reporting and any other development-only functionality. In CodeIgniter,
+    this can be done by setting the <kbd>ENVIRONMENT</kbd> constant, which is
+    more fully described on the <a href="../general/security.html">security page</a>.
 </p>
 
 <p>That's it!</p>
diff --git a/user_guide/installation/troubleshooting.html b/user_guide/installation/troubleshooting.html
index f99fc0a32..2a50b8dbf 100644
--- a/user_guide/installation/troubleshooting.html
+++ b/user_guide/installation/troubleshooting.html
@@ -61,8 +61,8 @@ Trouble Shooting
 does not support the PATH_INFO variable needed to serve search-engine friendly URLs.
 
 As a first step, open your <dfn>application/config/config.php</dfn> file and look for the <kbd>URI Protocol</kbd>
-information. It will recommend that you try a couple alternate settings. If it still doesn't work after you've tried this you'll need
-to force CodeIgniter to add a question mark to your URLs. To do this open your <kbd>application/config/config.php</kbd> file and change this:</p>
+information. It will recommend that you try a couple alternate settings.  If it still doesn't work after you've tried this you'll need
+to force CodeIgniter to add a question mark to your URLs.  To do this open your <kbd>application/config/config.php</kbd> file and change this:</p>
 
 <code>$config['index_page'] = "index.php";</code>
 
diff --git a/user_guide/installation/upgrade_130.html b/user_guide/installation/upgrade_130.html
index e6bb9480e..f7ffac74e 100644
--- a/user_guide/installation/upgrade_130.html
+++ b/user_guide/installation/upgrade_130.html
@@ -57,7 +57,7 @@ Upgrading from 1.2 to 1.3
 
 <h1>Upgrading from 1.2 to 1.3</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.2. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.2.  If you
 have not upgraded to that version please do so first.</p>
 
 
@@ -72,8 +72,8 @@ with a static one.</p>
 <p class="important"><strong>Note:</strong> If you have any custom developed files in these folders please make copies of them first.</p>
 
 <ul>
-<li>application/<strong>models</strong>/&nbsp;&nbsp; (new for 1.3)</li>
-<li>codeigniter&nbsp;&nbsp;  (new for 1.3)</li>
+<li>application/<strong>models</strong>/&nbsp;&nbsp;  (new for 1.3)</li>
+<li>codeigniter&nbsp;&nbsp;   (new for 1.3)</li>
 <li>drivers</li>
 <li>helpers</li>
 <li>init</li>
@@ -109,7 +109,7 @@ replace this folder:</p>
 
 <h2>Step 3: Update your index.php file</h2>
 
-<p>Please open your main <dfn>index.php</dfn> file (located at your root). At the very bottom of the file, change this:</p>
+<p>Please open your main <dfn>index.php</dfn> file (located at your root).  At the very bottom of the file, change this:</p>
 
 <code>require_once BASEPATH.'libraries/Front_controller'.EXT;</code>
 
diff --git a/user_guide/installation/upgrade_131.html b/user_guide/installation/upgrade_131.html
index a7025f2a7..7541a83ec 100644
--- a/user_guide/installation/upgrade_131.html
+++ b/user_guide/installation/upgrade_131.html
@@ -57,7 +57,7 @@ Upgrading from 1.3 to 1.3.1
 
 <h1>Upgrading from 1.3 to 1.3.1</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
diff --git a/user_guide/installation/upgrade_132.html b/user_guide/installation/upgrade_132.html
index 3b71594dc..4fcbb46b9 100644
--- a/user_guide/installation/upgrade_132.html
+++ b/user_guide/installation/upgrade_132.html
@@ -57,7 +57,7 @@ Upgrading from 1.3.1 to 1.3.2
 
 <h1>Upgrading from 1.3.1 to 1.3.2</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.1. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.1.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
diff --git a/user_guide/installation/upgrade_133.html b/user_guide/installation/upgrade_133.html
index a81f67bf5..c63465955 100644
--- a/user_guide/installation/upgrade_133.html
+++ b/user_guide/installation/upgrade_133.html
@@ -57,7 +57,7 @@ Upgrading from 1.3.2 to 1.3.3
 
 <h1>Upgrading from 1.3.2 to 1.3.3</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.2. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.2.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
@@ -83,9 +83,9 @@ have not upgraded to that version please do so first.</p>
 
 <p>If you are <strong>NOT</strong> using CodeIgniter's <a href="../general/models.html">Models</a> feature disregard this step.</p>
 
-<p>As of version 1.3.3, CodeIgniter does <strong>not</strong> connect automatically to your database when a model is loaded. This
-allows you greater flexibility in determining which databases you would like used with your models. If your application is not connecting
-to your database prior to a model being loaded you will have to update your code. There are several options for connecting,
+<p>As of version 1.3.3, CodeIgniter does <strong>not</strong> connect automatically to your database when a model is loaded.  This
+allows you greater flexibility in determining which databases you would like used with your models.  If your application is not connecting
+to your database prior to a model being loaded you will have to update your code.  There are several options for connecting,
 <a href="../general/models.html">as described here</a>.</p>
 
 
diff --git a/user_guide/installation/upgrade_140.html b/user_guide/installation/upgrade_140.html
index 234e2f5b3..2049628a6 100644
--- a/user_guide/installation/upgrade_140.html
+++ b/user_guide/installation/upgrade_140.html
@@ -57,7 +57,7 @@ Upgrading from 1.3.3 to 1.4.0
 
 <h1>Upgrading from 1.3.3 to 1.4.0</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.3. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.3.3.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
@@ -95,7 +95,7 @@ have not upgraded to that version please do so first.</p>
 |--------------------------------------------------------------------------
 |
 | If you would like to use the "hooks" feature you must enable it by
-| setting this variable to TRUE (boolean). See the user guide for details.
+| setting this variable to TRUE (boolean).  See the user guide for details.
 |
 */
 $config['enable_hooks'] = FALSE;
@@ -111,7 +111,7 @@ $config['enable_hooks'] = FALSE;
 | get a warning message.
 |
 | As a security measure you are STRONGLY encouraged to restrict URLs to
-| as few characters as possible. By default only these are allowed: a-z 0-9~%.:_-
+| as few characters as possible.  By default only these are allowed: a-z 0-9~%.:_-
 |
 | Leave blank to allow all characters -- but only if you are insane.
 |
diff --git a/user_guide/installation/upgrade_141.html b/user_guide/installation/upgrade_141.html
index 79e51e4ab..c19143c64 100644
--- a/user_guide/installation/upgrade_141.html
+++ b/user_guide/installation/upgrade_141.html
@@ -56,7 +56,7 @@ Upgrading from 1.4.0 to 1.4.1 </td>
 
 <h1>Upgrading from 1.4.0 to 1.4.1</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.4.0. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.4.0.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
@@ -88,16 +88,16 @@ have not upgraded to that version please do so first.</p>
 | Output Compression
 |--------------------------------------------------------------------------
 |
-| Enables Gzip output compression for faster page loads. When enabled,
+| Enables Gzip output compression for faster page loads.  When enabled,
 | the output class will test whether your server supports Gzip.
 | Even if it does, however, not all browsers support compression
 | so enable only if you are reasonably sure your visitors can handle it.
 |
-| VERY IMPORTANT: If you are getting a blank page when compression is enabled it
+| VERY IMPORTANT:  If you are getting a blank page when compression is enabled it
 | means you are prematurely outputting something to your browser. It could
-| even be a line of whitespace at the end of one of your scripts. For
+| even be a line of whitespace at the end of one of your scripts.  For
 | compression to work, nothing can be sent before the output buffer is called
-| by the output class. Do not "echo" any values with compression enabled.
+| by the output class.  Do not "echo" any values with compression enabled.
 |
 */
 $config['compress_output'] = FALSE;
diff --git a/user_guide/installation/upgrade_150.html b/user_guide/installation/upgrade_150.html
index 9cd0089c0..342d486df 100644
--- a/user_guide/installation/upgrade_150.html
+++ b/user_guide/installation/upgrade_150.html
@@ -57,7 +57,7 @@ Upgrading from 1.4.1 to 1.5.0
 
 <h1>Upgrading from 1.4.1 to 1.5.0</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.4.1. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.4.1.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
@@ -105,7 +105,7 @@ $db['default']['cachedir'] = '';
 |--------------------------------------------------------------------------
 |
 | This item allows you to set the filename/classname prefix when extending
-| native libraries. For more information please see the user guide:
+| native libraries.  For more information please see the user guide:
 |
 | http://codeigniter.com/user_guide/general/core_classes.html
 | http://codeigniter.com/user_guide/general/creating_libraries.html
@@ -120,7 +120,7 @@ $config['subclass_prefix'] = 'MY_';
 |
 | If your PHP installation does not have short tag support enabled CI
 | can rewrite the tags on-the-fly, enabling you to utilize that syntax
-| in your view files. Options are TRUE or FALSE (boolean)
+| in your view files.  Options are TRUE or FALSE (boolean)
 |
 */
 $config['rewrite_short_tags'] = FALSE;
@@ -136,7 +136,7 @@ $config['rewrite_short_tags'] = FALSE;
 |--------------------------------------------------------------------------
 |
 | If you would like errors or debug messages logged set this variable to
-| TRUE (boolean). Note: You must set the file permissions on the "logs" folder
+| TRUE (boolean).  Note: You must set the file permissions on the "logs" folder
 | such that it is writable.
 |
 */
diff --git a/user_guide/installation/upgrade_152.html b/user_guide/installation/upgrade_152.html
index 136e3090b..f601a252e 100644
--- a/user_guide/installation/upgrade_152.html
+++ b/user_guide/installation/upgrade_152.html
@@ -57,7 +57,7 @@ Upgrading from 1.5.0 to 1.5.2
 
 <h1>Upgrading from 1.5.0 to 1.5.2</h1>
 
-<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.5.0 or 1.5.1. If you
+<p class="important"><strong>Note:</strong> The instructions on this page assume you are running version 1.5.0 or 1.5.1.  If you
 have not upgraded to that version please do so first.</p>
 
 <p>Before performing an update you should take your site offline by replacing the index.php file with a static one.</p>
diff --git a/user_guide/installation/upgrade_160.html b/user_guide/installation/upgrade_160.html
index 2adeff379..d06f58ec9 100644
--- a/user_guide/installation/upgrade_160.html
+++ b/user_guide/installation/upgrade_160.html
@@ -84,16 +84,16 @@ Upgrading from 1.5.4 to 1.6.0
 <p>Add the following to application/config/autoload.php</p>
 <p><code> /*<br />
 	| -------------------------------------------------------------------<br />
-	| Auto-load Model files<br />
+	|  Auto-load Model files<br />
 	| -------------------------------------------------------------------<br />
 	| Prototype:<br />
 	|<br />
-	| $autoload['model'] = array('my_model');<br />
+	|  $autoload['model'] = array('my_model');<br />
 	|<br />
 	*/<br />
 	<br />
 	$autoload['model'] = array();</code></p>
-<h2>Step 4: Add to your database.php </h2>
+<h2>Step 4: Add  to your database.php </h2>
 <p>Make the following changes to your application/config/database.php file:</p>
 <p>Add the following variable above the database configuration options, with <dfn>$active_group</dfn></p>
 <p><code>$active_record = TRUE;</code></p>
diff --git a/user_guide/installation/upgrade_170.html b/user_guide/installation/upgrade_170.html
index 6fd92f52a..01597a416 100644
--- a/user_guide/installation/upgrade_170.html
+++ b/user_guide/installation/upgrade_170.html
@@ -88,14 +88,14 @@ Here is an example of what this column might look like for MySQL:</p>
 
 <code>ALTER TABLE `ci_sessions` ADD `user_data` text NOT NULL</code>
 
-<p>You'll find more information regarding the new Session functionality in the <a href="../libraries/sessions.html">Session class</a> page.</p>
+<p>You'll find more information regarding the new Session functionality in the  <a href="../libraries/sessions.html">Session class</a> page.</p>
 
 
 <h2>Step 3: Update your Validation Syntax</h2>
 
-<p>This is an <strong>optional</strong>, but recommended step, for people currently using the Validation class. CI 1.7 introduces a new <a href="../libraries/form_validation.html">Form Validation class</a>, which
-deprecates the old Validation library. We have left the old one in place so that existing applications that use it will not break, but you are encouraged to
-migrate to the new version as soon as possible. Please read the user guide carefully as the new library works a little differently, and has several new features.</p>
+<p>This is an <strong>optional</strong>, but recommended step, for people currently using the Validation class.  CI 1.7 introduces a new  <a href="../libraries/form_validation.html">Form Validation class</a>, which
+deprecates the old Validation library.  We have left the old one in place so that existing applications that use it will not break, but you are encouraged to
+migrate to the new version as soon as possible.  Please read the user guide carefully as the new library works a little differently, and has several new features.</p>
 
 
 
diff --git a/user_guide/installation/upgrade_200.html b/user_guide/installation/upgrade_200.html
index cd39d924d..0b24079ef 100644
--- a/user_guide/installation/upgrade_200.html
+++ b/user_guide/installation/upgrade_200.html
@@ -69,8 +69,8 @@ Upgrading from 1.7.2 to 2.0.0
 
 <h2>Step 2: Adjust get_dir_file_info() where necessary</h2>
 
-<p>Version 2.0.0 brings a non-backwards compatible change to <kbd>get_dir_file_info()</kbd> in the <a href="../helpers/file_helper.html">File Helper</a>. Non-backwards compatible changes are extremely rare
-	in CodeIgniter, but this one we feel was warranted due to how easy it was to create serious server performance issues. If you <em>need</em>
+<p>Version 2.0.0 brings a non-backwards compatible change to <kbd>get_dir_file_info()</kbd> in the <a href="../helpers/file_helper.html">File Helper</a>.  Non-backwards compatible changes are extremely rare
+	in CodeIgniter, but this one we feel was warranted due to how easy it was to create serious server performance issues.  If you <em>need</em>
 	recursiveness where you are using this helper function, change such instances, setting the second parameter, <kbd>$top_level_only</kbd> to FALSE:</p>
 
 <code>get_dir_file_info('/path/to/directory', <kbd>FALSE</kbd>);</code>
@@ -79,7 +79,7 @@ Upgrading from 1.7.2 to 2.0.0
 
 <h2>Step 3: Convert your Plugins to Helpers</h2>
 
-<p>2.0.0 gets rid of the "Plugin" system as their functionality was identical to Helpers, but non-extensible. You will need to rename your plugin files from <var>filename_pi.php</var> to <var>filename_helper.php</var>, move them to your <kbd>helpers</kbd> folder, and change all instances of:
+<p>2.0.0 gets rid of the "Plugin" system as their functionality was identical to Helpers, but non-extensible.  You will need to rename your plugin files from <var>filename_pi.php</var> to <var>filename_helper.php</var>, move them to your <kbd>helpers</kbd> folder, and change all instances of:
 
 	<code>$this->load->plugin('foo');</code>
 
@@ -94,7 +94,7 @@ to
 <p class="important"><strong>Note:</strong> If your application does not use the Encryption library, does not store Encrypted data permanently, or is on an environment that does not support Mcrypt, you may skip this step.</p>
 
 <p>The Encryption library has had a number of improvements, some for encryption strength and some for performance, that has an unavoidable consequence of
-	making it no longer possible to decode encrypted data produced by the original version of this library. To help with the transition, a new method has
+	making it no longer possible to decode encrypted data produced by the original version of this library.  To help with the transition, a new method has
 	been added, <kbd>encode_from_legacy()</kbd> that will decode the data with the original algorithm and return a re-encoded string using the improved methods.
 	This will enable you to easily replace stale encrypted data with fresh in your applications, either on the fly or en masse.</p>
 
@@ -104,7 +104,7 @@ to
 <p>The compatibility helper has been removed from the CodeIgniter core. All methods in it should be natively available in supported PHP versions.</p>
 
 <h2>Step 6: Update Class extension</h2>
-<p>All core classes are now prefixed with <kbd>CI_</kbd>. Update Models and Controllers to extend CI_Model and CI_Controller, respectively.</p>
+<p>All core classes are now prefixed with <kbd>CI_</kbd>.  Update Models and Controllers to extend CI_Model and CI_Controller, respectively.</p> 
 
 <h2>Step 7: Update Parent Constructor calls</h2>
 <p>All native CodeIgniter classes now use the PHP 5 <kbd>__construct()</kbd> convention. Please update extended libraries to call <kbd>parent::__construct()</kbd>.</p>
diff --git a/user_guide/installation/upgrade_202.html b/user_guide/installation/upgrade_202.html
index 93c537227..d457d8bbb 100644
--- a/user_guide/installation/upgrade_202.html
+++ b/user_guide/installation/upgrade_202.html
@@ -76,7 +76,7 @@ Upgrading from 2.0.1 to 2.0.2
 
 <p>If you are overriding or extending the Security library, you will need to move it to <kbd>application/core</kbd>.</p>
 
-<p><samp>csrf_token_name</samp> and <samp>csrf_hash</samp> have changed to protected class properties. Please use <samp>security->get_csrf_hash()</samp> and <samp>security->get_csrf_token_name()</samp> to access those values.</p>
+<p><samp>csrf_token_name</samp> and <samp>csrf_hash</samp> have changed to protected class properties.  Please use <samp>security->get_csrf_hash()</samp> and <samp>security->get_csrf_token_name()</samp> to access those values.</p>
 
 </div>
 <!-- END CONTENT -->
diff --git a/user_guide/installation/upgrade_203.html b/user_guide/installation/upgrade_203.html
index d1c9a940f..7dbc907ea 100644
--- a/user_guide/installation/upgrade_203.html
+++ b/user_guide/installation/upgrade_203.html
@@ -69,7 +69,7 @@ Upgrading from 2.0.2 to 2.0.3
 <h2>Step 2: Update CodeIgniter files</h2>
 
 <p>Replace the files and directories in your "system" folder with the new versions:</p>
-
+	
 <h2>Step 3: Update your main index.php file</h2>
 
 <p>If you are running a stock <dfn>index.php</dfn> file simply replace your version with the new one.</p>
@@ -81,7 +81,7 @@ Upgrading from 2.0.2 to 2.0.3
 <p>This config file has been updated to contain more user agent types, please copy it to <kbd>application/config/user_agents.php</kbd>.</p>
 
 <h2>Step 5: Change references of the EXT constant to ".php"</h2>
-<p class="important"><strong>Note:</strong> The EXT Constant has been marked as deprecated, but has not been removed from the application. You are encouraged to make the changes sooner rather than later.</p>
+<p class="important"><strong>Note:</strong> The EXT Constant has been marked as deprecated, but has not been removed from the application.  You are encouraged to make the changes sooner rather than later.</p>
 
 <h2>Step 6: Remove APPPATH.'third_party' from autoload.php</h2>
 
@@ -101,10 +101,10 @@ Upgrading from 2.0.2 to 2.0.3
 <code>
 	CREATE INDEX last_activity_idx ON ci_sessions(last_activity);
 	ALTER TABLE ci_sessions MODIFY user_agent VARCHAR(120);
-</code>
-
-
-
+</code>	
+	
+	
+	
 
 </div>
 <!-- END CONTENT -->
diff --git a/user_guide/installation/upgrade_b11.html b/user_guide/installation/upgrade_b11.html
index d2fc20d18..add7228c8 100644
--- a/user_guide/installation/upgrade_b11.html
+++ b/user_guide/installation/upgrade_b11.html
@@ -61,7 +61,7 @@ Upgrading from Beta 1.0 to Beta 1.1
 
 <h2>Step 1: Replace your index file</h2>
 
-<p>Replace your main <kbd>index.php</kbd> file with the new index.php file. Note: If you have renamed your "system" folder you will need to edit this info in the new file.</p>
+<p>Replace your main <kbd>index.php</kbd> file with the new index.php file. Note:  If you have renamed your "system" folder you will need to edit this info in the new file.</p>
 
 <h2>Step 2: Relocate your config folder</h2>
 
@@ -91,7 +91,7 @@ the following item to your version: <dfn>language/english/calendar_lang.php</dfn
 
 <h2>Step 5: Edit your config file</h2>
 
-<p>The original <kbd>application/config/config.php</kbd> file has a typo in it Open the file and look for the items related to cookies:</p>
+<p>The original <kbd>application/config/config.php</kbd> file has a typo in it  Open the file and look for the items related to cookies:</p>
 
 <code>$conf['cookie_prefix']	= "";<br />
 $conf['cookie_domain']	= "";<br />
@@ -112,7 +112,7 @@ $config['cookie_path']	= "/";</code>
 |------------------------------------------------<br />
 |<br />
 | This item determines which server global <br />
-| should be used to retrieve the URI string. The <br />
+| should be used to retrieve the URI string.  The <br />
 | default setting of "auto" works for most servers.<br />
 | If your links do not seem to work, try one of <br />
 | the other delicious flavors:<br />