diff --git a/help/alter-exposed-filter.html b/help/alter-exposed-filter.html
index 5bddb6e..65b6522 100644
--- a/help/alter-exposed-filter.html
+++ b/help/alter-exposed-filter.html
@@ -1,31 +1,31 @@
-Modifying default values of a views exposed form is tricky, because FAPI was not designed to work with GET forms. One consequence is that it often can't tell if textfields (there are others) were submitted or not.
-
-As a consequence, it *always* thinks the value was submitted, even if it was not. To fix that, Views modifies $form_state['input'][$identifier] with the default value if $form_state['input'][$identifier] was not set. In order to modify the default value in an alter, you need to do this:
-
-<pre>
-&lt;?php
-if (empty($form_state['view']->exposed_input[$identifier])) . 
-		{ $form_state['input'][$identifier] = $default_value; }
-?&gt;
-</pre>
-
-where $identifier is the particular filter for which you want to change the default value, and $default_value is the new default value you want to set.
-
-If you use a hook_form_FORM_ID_alter or hook_form_alter, you can modify exposed filters on the fly based on information that is external to Views. For example, I modified the exposed filter of a form to set a taxonomy term ID based on the user's GeoIP.
-
-To do this, I used the following function, where geoip_redirect_get_tid() loads the relevant term id based on the user's current ip_address():
-
-<pre>
-&lt;?php
-function MODULENAME_form_views_exposed_form_alter(&$form, $form_state) {
-  if(strpos($form['#id'], 'volunteer-directory') !== FALSE) {   
-    $city_tid = geoip_redirect_get_tid();
-    if(is_numeric($city_tid) && $city_tid != 7660) {
-      if (empty($form_state['view']->exposed_input['tid']))  {
-        $form_state['input']['tid'] = $city_tid;
-      }
-    }
-  }   
-}
-?&gt;
+Modifying default values of a views exposed form is tricky, because FAPI was not designed to work with GET forms. One consequence is that it often can't tell if textfields (there are others) were submitted or not.
+
+As a consequence, it *always* thinks the value was submitted, even if it was not. To fix that, Views modifies $form_state['input'][$identifier] with the default value if $form_state['input'][$identifier] was not set. In order to modify the default value in an alter, you need to do this:
+
+<pre>
+&lt;?php
+if (empty($form_state['view']->exposed_input[$identifier])) . 
+		{ $form_state['input'][$identifier] = $default_value; }
+?&gt;
+</pre>
+
+where $identifier is the particular filter for which you want to change the default value, and $default_value is the new default value you want to set.
+
+If you use a hook_form_FORM_ID_alter or hook_form_alter, you can modify exposed filters on the fly based on information that is external to Views. For example, I modified the exposed filter of a form to set a taxonomy term ID based on the user's GeoIP.
+
+To do this, I used the following function, where geoip_redirect_get_tid() loads the relevant term id based on the user's current ip_address():
+
+<pre>
+&lt;?php
+function MODULENAME_form_views_exposed_form_alter(&$form, $form_state) {
+  if(strpos($form['#id'], 'volunteer-directory') !== FALSE) {   
+    $city_tid = geoip_redirect_get_tid();
+    if(is_numeric($city_tid) && $city_tid != 7660) {
+      if (empty($form_state['view']->exposed_input['tid']))  {
+        $form_state['input']['tid'] = $city_tid;
+      }
+    }
+  }   
+}
+?&gt;
 </pre>
\ No newline at end of file
diff --git a/help/drush.html b/help/drush.html
index 61f2330..7eb309a 100644
--- a/help/drush.html
+++ b/help/drush.html
@@ -1,13 +1,13 @@
-There are some Drush commands available for Views, initially added in <a href="http://drupal.org/node/1079178">Drush command to revert views</a>:
-
-<ul>
-<li>views-dev (vd) -  Setup the views settings to a more developer oriented value</li>
-<li>views-revert (vr) - Revert overriden views to their default state. Make backups first!</li>
-</ol>
-
-Examples:
-drush views-revert
-[prompts the user with a list of overridden views to choose from, or to revert all]
-
-drush views-revert archive myview2
+There are some Drush commands available for Views, initially added in <a href="http://drupal.org/node/1079178">Drush command to revert views</a>:
+
+<ul>
+<li>views-dev (vd) -  Setup the views settings to a more developer oriented value</li>
+<li>views-revert (vr) - Revert overriden views to their default state. Make backups first!</li>
+</ol>
+
+Examples:
+drush views-revert
+[prompts the user with a list of overridden views to choose from, or to revert all]
+
+drush views-revert archive myview2
 [reverts the two specified views]
\ No newline at end of file
diff --git a/help/get-total-rows.html b/help/get-total-rows.html
index 3e74fd9..b40d198 100644
--- a/help/get-total-rows.html
+++ b/help/get-total-rows.html
@@ -1,16 +1,16 @@
-The flag $view->get_total_rows is used to force the query of the view to calculate the total number of results of the set.
-
-This parameter is TRUE by default in views that get all the results (no limit) or those which have a pager, so you always have the $view->total_rows variable populated in those cases.
-But when you have a view that gets only a given number of results and no pager, the count query is not executed by default so you have to force it, i.e. in the hook_views_pre_execute so you have $view->total_rows populated for later use.
-
-This code will help you do that.
-
-<pre>
-&lt;?php
-function my_module_views_pre_execute(&$view) {
-  if ($view->name == 'my_view' && $view->current_display == 'my_display') {
-    $view->get_total_rows = TRUE;
-  }
-}
-?&gt;
+The flag $view->get_total_rows is used to force the query of the view to calculate the total number of results of the set.
+
+This parameter is TRUE by default in views that get all the results (no limit) or those which have a pager, so you always have the $view->total_rows variable populated in those cases.
+But when you have a view that gets only a given number of results and no pager, the count query is not executed by default so you have to force it, i.e. in the hook_views_pre_execute so you have $view->total_rows populated for later use.
+
+This code will help you do that.
+
+<pre>
+&lt;?php
+function my_module_views_pre_execute(&$view) {
+  if ($view->name == 'my_view' && $view->current_display == 'my_display') {
+    $view->get_total_rows = TRUE;
+  }
+}
+?&gt;
 </pre>
\ No newline at end of file
diff --git a/help/other-help.html b/help/other-help.html
index 65d93e2..43c6e5e 100644
--- a/help/other-help.html
+++ b/help/other-help.html
@@ -1,10 +1,10 @@
-There are many tutorials, podcasts, and a few books on Views that you can turn to for further help.
-
-Books:
-<a href="http://www.drupal-building-blocks.com">Drupal Building Blocks</a> is the Views' author book; check <a href="http://www.drupal.org/books">the Drupal.org books page</a> for a fairly comprehensive list.
-
-Videos:
-See <a href="topic:views/demo-video">this page.</a>
-
-Google. Many Drupal shops put together helpful tutorials and publish them to Drupal Planet, not to mention the countless users of Views who do it for the community.
-
+There are many tutorials, podcasts, and a few books on Views that you can turn to for further help.
+
+Books:
+<a href="http://www.drupal-building-blocks.com">Drupal Building Blocks</a> is the Views' author book; check <a href="http://www.drupal.org/books">the Drupal.org books page</a> for a fairly comprehensive list.
+
+Videos:
+See <a href="topic:views/demo-video">this page.</a>
+
+Google. Many Drupal shops put together helpful tutorials and publish them to Drupal Planet, not to mention the countless users of Views who do it for the community.
+
diff --git a/help/select-multple-nids-contextual-filters.html b/help/select-multple-nids-contextual-filters.html
index e2a860c..e623541 100644
--- a/help/select-multple-nids-contextual-filters.html
+++ b/help/select-multple-nids-contextual-filters.html
@@ -1,29 +1,29 @@
-We assume that you have a properly configured view at this point. You should have a page or block display with fields/node to be displayed in it. 
-
-<ol>
-<li>In the views administration screen add a new 'contextual filter' using 'add'.  You will see a configuration screen appear as a modal.</li> 
-
-<li>In the 'Filter' jump menu that you now see select 'Content'. A list will appear below the jump menu.</li>
-
-<li>In the list look for 'Content: Nid', and check it. </li>
-
-<li>Press the 'Add and configure contextual filters' button.  You will now get the configuration screen for 'Content: Nid'.</li>
-
-<li>Under 'When the filter value is NOT in the URL' select 'Provide default argument', and leave it set at 'Fixed value'.</li>
-
-<li>In the field 'Fixed value' add the Nids of the nodes separated by a '+' that you want to show by default.</li>
-
-<li>In 'When the filter value IS in the URL or a default is provided' choose 'Specify validation criteria'. Now select the content types you want, or leave blank for all nodes.</li>
-
-<li>Check the 'Validate user has access to the node'. This will check if a user has permission to view nodes, that are going to be displayed</li> 
-
-<li>For the 'Filter value format' select 'Node IDs separated by , or +'.</li> 
-
-<li>Select the MORE link.</li>
-
-<li>Check 'Allow Multiple Terms per Argument' and press 'Apply (all displays
-)' (or choose a particular display in the dropdown at the top and Apply (this display)). </li>
-</ol>
-
-Preview should now show nodes, that you selected as "default argument". You can now pass arguments to your view, to select custom node IDs. If you provide no argument, default will be used. Save the view when ready. 
-
+We assume that you have a properly configured view at this point. You should have a page or block display with fields/node to be displayed in it. 
+
+<ol>
+<li>In the views administration screen add a new 'contextual filter' using 'add'.  You will see a configuration screen appear as a modal.</li> 
+
+<li>In the 'Filter' jump menu that you now see select 'Content'. A list will appear below the jump menu.</li>
+
+<li>In the list look for 'Content: Nid', and check it. </li>
+
+<li>Press the 'Add and configure contextual filters' button.  You will now get the configuration screen for 'Content: Nid'.</li>
+
+<li>Under 'When the filter value is NOT in the URL' select 'Provide default argument', and leave it set at 'Fixed value'.</li>
+
+<li>In the field 'Fixed value' add the Nids of the nodes separated by a '+' that you want to show by default.</li>
+
+<li>In 'When the filter value IS in the URL or a default is provided' choose 'Specify validation criteria'. Now select the content types you want, or leave blank for all nodes.</li>
+
+<li>Check the 'Validate user has access to the node'. This will check if a user has permission to view nodes, that are going to be displayed</li> 
+
+<li>For the 'Filter value format' select 'Node IDs separated by , or +'.</li> 
+
+<li>Select the MORE link.</li>
+
+<li>Check 'Allow Multiple Terms per Argument' and press 'Apply (all displays
+)' (or choose a particular display in the dropdown at the top and Apply (this display)). </li>
+</ol>
+
+Preview should now show nodes, that you selected as "default argument". You can now pass arguments to your view, to select custom node IDs. If you provide no argument, default will be used. Save the view when ready. 
+
diff --git a/help/semantic-views.html b/help/semantic-views.html
index 8cbf830..258e568 100644
--- a/help/semantic-views.html
+++ b/help/semantic-views.html
@@ -1,18 +1,18 @@
-The <a href="http://drupal.org/project/semanticviews">Semantic Views</a> module has been mostly incorporated into Views 3.x. Semantic Views is still around for people who need it, though. For some details on how the original module is different from the Views implementation, please see <a href="http://drupal.org/node/1013876">this issue</a>.
-
-Semantic views help you insert markup of your own from the Views UI, so that you can fairly easily override the default markup without having to restyle via templates. 
-
-As a usage example,
-
-In a view with a field:
-<ol>
-<li>Configure the field. (Click on the field.)</li>
-
-<li>In the modal that opens, scroll down to <strong>Style Settings</strong>.</li>
-
-<li>Choose one or more of the three <i>Customize</i> options. This will reveal a dropdown menu where you can choose from one or more HTML tags to use on that field and allow you to add a CSS class specific to that field should you desire.</li>
-
-<li>Decide if you want to keep the Views default classes. Unchecking this box means your markup is *it*.</li>
-</ol>
-
+The <a href="http://drupal.org/project/semanticviews">Semantic Views</a> module has been mostly incorporated into Views 3.x. Semantic Views is still around for people who need it, though. For some details on how the original module is different from the Views implementation, please see <a href="http://drupal.org/node/1013876">this issue</a>.
+
+Semantic views help you insert markup of your own from the Views UI, so that you can fairly easily override the default markup without having to restyle via templates. 
+
+As a usage example,
+
+In a view with a field:
+<ol>
+<li>Configure the field. (Click on the field.)</li>
+
+<li>In the modal that opens, scroll down to <strong>Style Settings</strong>.</li>
+
+<li>Choose one or more of the three <i>Customize</i> options. This will reveal a dropdown menu where you can choose from one or more HTML tags to use on that field and allow you to add a CSS class specific to that field should you desire.</li>
+
+<li>Decide if you want to keep the Views default classes. Unchecking this box means your markup is *it*.</li>
+</ol>
+
 <a href="path:images/views3-semanticviews.png"><img src="path:images/views3-semanticviews.png" />
\ No newline at end of file
diff --git a/help/taxonomy-page-override.html b/help/taxonomy-page-override.html
index c83be63..25afe9a 100644
--- a/help/taxonomy-page-override.html
+++ b/help/taxonomy-page-override.html
@@ -1,41 +1,41 @@
-NOTE: This page has not been updated for 7.x-3.x
-Views 2 provides a way to override the taxonomy pages of any term. The view is included by default but is disabled. This page covers three minor aspects that some users could use to control the aspect of their taxonomy pages.
-
-<h3>Background</h3>
-The Taxonomy module provides a way to organize content through the site. It also presents a page with nodes that belong to some term. The style can't be changed easily and taxonomy only displays node teasers.
-
-<h3>Force All</h3>
-When using vocabularies with multiple term levels, a top level won't include the nodes that belongs to the levels inside. Let's clarify this with an example, let's assume the site have this vocabulary:
-
-<code>
-Vocab
- - Term 1
-   -- Term 2
-   -- Term 3
- - Term 4
-   -- Term 5
-   -- Term 6
-</code>
-
-If you go to taxonomy/term/1, then you see all nodes in Term 1 listed, but not nodes in Term 2 and Term 3. If you want to see all nodes in Term 1, Term 2 and Term 3 in a single page, you have to go to 
-
-<code>
-taxonomy/term/1/all
-</code>
-
-Views 2 allows you to show all terms inside another term.
-
-<h3>Step 1. Enabling taxonomy_term</h3>
-The first step we need to do is to enable the "taxonomy term" view that views provides for us. After we've done that we need to edit it.
-
-<h3>Step 2. Changing minor aspects</h3>
-On the Display: Page, we can change the Style to any of the styles that views provides for us, it could be a table or a list. If we do this it's necessary to add some fields to the view.
-
-The most important thing we're going to change it's the argument <strong>Taxonomy: Term ID: (with depth)</strong>. At the bottom of the screen, you'll have 2 options, the first one to change it's the <strong>depth</strong>, if we want to do what the <a href="http://drupal.org/project/taxonomy_forceall" target="_blank">Taxonomy Force All</a> modules does, you'll have to set it up for at least 1.
-
-The next thing you have to do it's check the <strong>Set the breadcrumb for the term parents</strong> option. This will allow your view to show  the breadcrumb with all the term levels in your taxonomy.
-
-Save the changes and try. Next you could do whatever you want, like adding fields, theming, exposing filters, sorting or adding feeds.
-
-<h3>Theme every vocabulary/term independently</h3>
-Using <a href="http://drupal.org/project/tvi">TVI: Taxonomy Views Integrator</a>  it's possible to theme every vocabulary or term with it's own view. All you have to do is clone the view in Step 1 and set it as the TVI active view in the vocab or term edit pages.
+NOTE: This page has not been updated for 7.x-3.x
+Views 2 provides a way to override the taxonomy pages of any term. The view is included by default but is disabled. This page covers three minor aspects that some users could use to control the aspect of their taxonomy pages.
+
+<h3>Background</h3>
+The Taxonomy module provides a way to organize content through the site. It also presents a page with nodes that belong to some term. The style can't be changed easily and taxonomy only displays node teasers.
+
+<h3>Force All</h3>
+When using vocabularies with multiple term levels, a top level won't include the nodes that belongs to the levels inside. Let's clarify this with an example, let's assume the site have this vocabulary:
+
+<code>
+Vocab
+ - Term 1
+   -- Term 2
+   -- Term 3
+ - Term 4
+   -- Term 5
+   -- Term 6
+</code>
+
+If you go to taxonomy/term/1, then you see all nodes in Term 1 listed, but not nodes in Term 2 and Term 3. If you want to see all nodes in Term 1, Term 2 and Term 3 in a single page, you have to go to 
+
+<code>
+taxonomy/term/1/all
+</code>
+
+Views 2 allows you to show all terms inside another term.
+
+<h3>Step 1. Enabling taxonomy_term</h3>
+The first step we need to do is to enable the "taxonomy term" view that views provides for us. After we've done that we need to edit it.
+
+<h3>Step 2. Changing minor aspects</h3>
+On the Display: Page, we can change the Style to any of the styles that views provides for us, it could be a table or a list. If we do this it's necessary to add some fields to the view.
+
+The most important thing we're going to change it's the argument <strong>Taxonomy: Term ID: (with depth)</strong>. At the bottom of the screen, you'll have 2 options, the first one to change it's the <strong>depth</strong>, if we want to do what the <a href="http://drupal.org/project/taxonomy_forceall" target="_blank">Taxonomy Force All</a> modules does, you'll have to set it up for at least 1.
+
+The next thing you have to do it's check the <strong>Set the breadcrumb for the term parents</strong> option. This will allow your view to show  the breadcrumb with all the term levels in your taxonomy.
+
+Save the changes and try. Next you could do whatever you want, like adding fields, theming, exposing filters, sorting or adding feeds.
+
+<h3>Theme every vocabulary/term independently</h3>
+Using <a href="http://drupal.org/project/tvi">TVI: Taxonomy Views Integrator</a>  it's possible to theme every vocabulary or term with it's own view. All you have to do is clone the view in Step 1 and set it as the TVI active view in the vocab or term edit pages.
diff --git a/help/top-pager.html b/help/top-pager.html
index da291ef..68247af 100644
--- a/help/top-pager.html
+++ b/help/top-pager.html
@@ -1,18 +1,18 @@
-Copy the views-view.tpl.php from the /views/theme directory to themes/yourtheme/theme directory. Find the following code...
-
-
-<pre>
-  &lt;?php if ($attachment_before): ?&gt;
-    &lt;div class="attachment-before"&gt;
-      &lt;?php print $attachment_before; ?&gt;
-    &lt;/div&gt;
-  &lt;?php endif; ?&gt;
-</pre>
-
-Insert the following code after it (this is copied directly from the same code at the bottom of the tpl):
-
-<pre>
-  &lt;?php if ($pager): ?&gt;
-    &lt;?php print $pager; ?&gt;
-  &lt;?php endif; ?&gt;
-  </pre>
+Copy the views-view.tpl.php from the /views/theme directory to themes/yourtheme/theme directory. Find the following code...
+
+
+<pre>
+  &lt;?php if ($attachment_before): ?&gt;
+    &lt;div class="attachment-before"&gt;
+      &lt;?php print $attachment_before; ?&gt;
+    &lt;/div&gt;
+  &lt;?php endif; ?&gt;
+</pre>
+
+Insert the following code after it (this is copied directly from the same code at the bottom of the tpl):
+
+<pre>
+  &lt;?php if ($pager): ?&gt;
+    &lt;?php print $pager; ?&gt;
+  &lt;?php endif; ?&gt;
+  </pre>
diff --git a/help/ui-crashes.html b/help/ui-crashes.html
index 14c4aea..4e8a389 100644
--- a/help/ui-crashes.html
+++ b/help/ui-crashes.html
@@ -1,25 +1,25 @@
-<h2>Troubleshooting UI crashes</h2>
-
-There are a number of reasons why the Views UI may crash; the most common state or result of a crash is either a white screen (everyone's favorite WSOD), or a screen of what looks like garbage text. This is generally a javascript crash of some fashion.
-
-To get the most timely and accurate help in the issue queue, please try to gather this information:
-
-Check your javascript console. In Firefox, you can hit ctrl-shift-j or use firebug. Copy this information into the issue, or attach it as a text file. Really - this is the single biggest thing you can do to help figure out where the crash is coming from.
-
-
-<h3>JSON prepends data with jQuery, causing editing and preview problems.</h3>
-This section originally stems from <a href="http://drupal.org/node/346662">this issue.</a>
-
-Some modules may add PHP improperly, disrupting normal jQuery operation. Errors may look like
-
-<code>
-<? session_module_name("files"); ?>{ "default": "default" }
-</code>
-
-This can also be a server configuration issue. In one case, this was solved by commenting out
-
-auto_prepend_file = c:\wamp\www\php.ini.prepend
-
-in the php.ini.
-
-Another page to look at is the drupal.org page on <a href="http://drupal.org/node/158043">White screens</a>
+<h2>Troubleshooting UI crashes</h2>
+
+There are a number of reasons why the Views UI may crash; the most common state or result of a crash is either a white screen (everyone's favorite WSOD), or a screen of what looks like garbage text. This is generally a javascript crash of some fashion.
+
+To get the most timely and accurate help in the issue queue, please try to gather this information:
+
+Check your javascript console. In Firefox, you can hit ctrl-shift-j or use firebug. Copy this information into the issue, or attach it as a text file. Really - this is the single biggest thing you can do to help figure out where the crash is coming from.
+
+
+<h3>JSON prepends data with jQuery, causing editing and preview problems.</h3>
+This section originally stems from <a href="http://drupal.org/node/346662">this issue.</a>
+
+Some modules may add PHP improperly, disrupting normal jQuery operation. Errors may look like
+
+<code>
+<? session_module_name("files"); ?>{ "default": "default" }
+</code>
+
+This can also be a server configuration issue. In one case, this was solved by commenting out
+
+auto_prepend_file = c:\wamp\www\php.ini.prepend
+
+in the php.ini.
+
+Another page to look at is the drupal.org page on <a href="http://drupal.org/node/158043">White screens</a>
