Merge lp:~chuckw20/widelands/assorted_grammar_corrections into lp:widelands

[Chuck Wilder]

Reviewed the files of the doc and txts folders and edited for grammar and usage.

[Raul Ferriz (raul.ferriz)]

review: Approve

=== modified file 'doc/README.development'
--- doc/README.development	2007-06-12 21:28:15 +0000
+++ doc/README.development	2010-04-28 21:36:32 +0000
@@ -41,7 +41,7 @@
 
 A word about triggers and events
 --------------------------------
-Here i'll talk very shortly about triggers and events and how they are implemented.
+Here I'll talk very shortly about triggers and events and how they are implemented.
 
 Triggers are exactly what they sound like: Simple triggers (switches) which can 
 either be on or off. Triggers are checked periodically in the cmdqueue if they
@@ -51,21 +51,21 @@
 really gets set after 20-21 seconds; same: it could take up to 1 seconds before
 an event occurs that should be tackled by one trigger; even worse: it could take
 up to number_of_triggers_the_event_needs_to_be_set seconds. So the way triggers are
-checked may change in the future when this proofs as to slow.
+checked may change in the future when this proves to be too slow.
 
 If you want to implement a new trigger, here is what to do. First, make sure
 that: 
   1) if your trigger sets/unsets itself in the check function, make sure that it 
      stays set/unset, even if it's condition changes again until it is reset by 
-     some event. Than it behave on a check like expected
+     some event. Then it behaves on a check like expected.
   2) if your trigger triggers only once through the whole game, make sure that
-     your reset function assert(0)s and that it's check function never ever
+     your reset function assert(0)s and that its check function never ever
      changes the state again after this first time.
 
 Ok, now the steps to implement a new Trigger:
   1) Add its id in src/trigger_ids.h (TRIGGER_<YOUR_TRIGGER_NAME>)
   2) Add its description, name and id into TRIGGER_DESCRIPTIONS[] in
-      src/trigger_factor.cc, update also the functions ther
+      src/trigger_factor.cc, update also the functions there
   3) Derive a class Trigger_<Your_Trigger_Name> from Trigger (own header and
      source file, trigger_<your_name_here>.[h|cc]
   4) Create the Menu class as a modal window (no move, no other actions allowed
@@ -76,9 +76,9 @@
 order (especially ID and TRIGGER_VERSION of your trigger)
 
 Events are also what they sound like: Something happens in the game. Events can
-be nearly everything you can imagine (and programm 8) ): change of terrain, new
+be nearly everything you can imagine (and program 8) ): change of terrain, new
 land conquered, unhide areas, warp some wares/workers, let the computer attack
-or show a message box to the interactive user are just some possibilitys.
+or show a message box to the interactive user are just some possibilities.
 Events depend on triggers, each event can have one or more triggers attached to
 it, whenever a trigger gets set, all events look at their triggers, and if all
 are in the state the event needs, the event runs itself. If the event can't rerun
@@ -91,13 +91,13 @@
       there.
    3) Derive a class Event_<Your Event Name> from class Event (own header
       and source file)
-      make sure that you proper handle your resources,
+      make sure that you properly handle your resources,
         memory stuff should be freed in destructor
         trigger should be released in cleanup and reinitialized/freed
-        in reinitialize_own(). if all triggers are already released in 
+        in reinitialize_own(). If all triggers are already released in 
         reinitialize own, cleanup must detect this and not release them 
-        again
+        again.
    4) Create the Option-Menu class as a modal window in
          src/editor/ui_menus/event_<event name here>.[h|cc]
-And that's all. Orientat yourself on the already implemented classes.
+And that's all. Orientate yourself on the already implemented classes.
 

=== modified file 'doc/hidden_features.txt'
--- doc/hidden_features.txt	2010-03-16 22:06:20 +0000
+++ doc/hidden_features.txt	2010-04-28 21:36:32 +0000
@@ -7,18 +7,18 @@
 	
 	RETREAT WHEN INJURED
 	--------------------
-		Retreat when injured, or simply retreat. When a soldier's hit points downs
-		below to this percentage value, soldier then will try to go to safety of 
+		Retreat when injured, or simply retreat. When a soldier's hit points drops
+		below this percentage value, soldier then will try to go to safety of 
 		home.
 		
 		[allow_retreat_change]
-			If this section exist on config file of tribe, then player is allowed
+			If this section exists on config file of tribe, then player is allowed
 		to change value of retreat in-game. This may be present on files like
 		castle_village and headquarters_medium to activate this feature.
 	
 
 		[retreat_change]
-			This section encapsulates next two varibles. This section should exist
+			This section encapsulates next two variables. This section should exist
 		on main tribe conf file.
 		
 		retreat_change=value
@@ -26,7 +26,7 @@
 		This variable should exist on main tribes conf file.
 		
 		retreat_interval=min-max
-			Sets valid interval of retreating for tribe that player is allowed to
+			Sets valid interval of retreating for tribe that the player is allowed to
 		set. This interval only is shown in game when player is allowed to modify
 		retreat. 
 

=== modified file 'doc/productionsite_program_reference.xhtml'
--- doc/productionsite_program_reference.xhtml	2009-08-04 07:57:50 +0000
+++ doc/productionsite_program_reference.xhtml	2010-04-28 21:36:32 +0000
@@ -62,7 +62,7 @@
 Aborts the execution of the program and sets a return value. Updates the productionsite's statistics depending on the return value.
 </p>
 <p>
-Note: If the execution reaches the end of the program. the return value is implicitly set to Completed.
+Note: If the execution reaches the end of the program, the return value is implicitly set to Completed.
 </p>
 <h3 id="call">call</h3>
 <p>Calls a program of the productionsite.</p>
@@ -162,7 +162,7 @@
 <p>Takes resources from the ground. This command type is subject to change.</p>
 <h3 id="check_soldier">check_soldier</h3>
 <p>
-Returns failure unless there are a specified amout of soldiers with specified level of specified properties. This command type is subject to change.
+Returns failure unless there are a specified amount of soldiers with specified level of specified properties. This command type is subject to change.
 </p>
 <h3 id="train">train</h3>
 <p>
@@ -174,7 +174,7 @@
 <pre>  parameters&nbsp;::= <i>soundFX</i> [<i>priority</i>]</pre>
 <p>Parameter semantics:</p>
 <pre>  <i>soundFX</i>:
-     The filename of an soundFX (relative to the productionsite's
+     The filename of a soundFX (relative to the productionsite's
      directory).
   <i>priority</i>:
      An integer. If omitted, 127 is used.</pre>

=== modified file 'txts/README'
--- txts/README	2010-04-24 15:23:56 +0000
+++ txts/README	2010-04-28 21:36:32 +0000
@@ -10,7 +10,7 @@
 "</p>"
 "<p line-spacing=3 font-size=12>"
 "<br><br>"
-_"Widelands is a strategy game aiming for gameplay similar to Settlers II by BlueByte.<br>In this game, you start out on a small piece of land with nothing more than a few of useful resources. Using those, you can build yourself an empire with many thousands of inhabitants. On your way towards this goal, you will have to build up an economic infrastructure, explore the lands around you and face enemies who are trying to rule the world just like you do."
+_"Widelands is a strategy game aiming for gameplay similar to Settlers II by BlueByte.<br>In this game, you start out on a small piece of land with nothing more than a few useful resources. Using those, you can build yourself an empire with many thousands of inhabitants. On your way towards this goal, you will have to build up an economic infrastructure, explore the lands around you and face enemies who are trying to rule the world just like you."
 "<br>"
 "<br>"
 _"Check out the Widelands project homepage:"

=== modified file 'txts/tips/editor.tip'
--- txts/tips/editor.tip	2010-04-05 21:52:27 +0000
+++ txts/tips/editor.tip	2010-04-28 21:36:32 +0000
@@ -11,7 +11,7 @@
 sec=6
 
 [Tip 4]
-text=_"Holding down SHIFT switches first alternative tool on. This tool is in most cases the complete difference of the normal tool (for example deletion of an object instead of placing one)."
+text=_"Holding down SHIFT switches first alternative tool on. This tool is in most cases the complete opposite of the normal tool (for example deletion of an object instead of placing one)."
 sec=7
 
 [Tip 5]

=== modified file 'txts/tips/multiplayer.tip'
--- txts/tips/multiplayer.tip	2010-03-02 17:53:06 +0000
+++ txts/tips/multiplayer.tip	2010-04-28 21:36:32 +0000
@@ -1,5 +1,5 @@
 [Tip 1]
-text=_"You can use 'Page up' and 'Page down' keys to adjust your wished speed - the real speed is than democratically set."
+text=_"You can use 'Page up' and 'Page down' keys to adjust your wished speed - the real speed is then democratically set."
 sec=5
 
 [Tip 2]