Merge pull request #227 from slabstone/fix-typos

Fix a bunch of typos in file formats

Author: lynxlynxlynx

file_formats/general.htm

@@ -12,7 +12,7 @@
 
     <div class="fileHeader">General</div>
     <div class="indent1">
-      All versions of the Infinity Engine, except that used in Planescape: Torment, make some internal of the <a href="http://www.lua.org/" class="offsite">Lua</a> programming language, as developed by TeCGraf at the Pontifical Catholic University of Rio de Janeiro in Brazil. In the Infinity Engine, LUA is primarily used for the cheats/debugging console. The debug console actually allows complete LUA programs to be entered and run, though these programs can only have a very limited affect on the game and the engine. The LUA <a href="http://www.lua.org/docs.html" class="offsite">documentation</a> is available online, though knowledge of LUA is of limited use in IE modding. It should be mentionned, that unlike other engines where LUA is used, the Infinity Engine AI scripts have nothing to do with LUA.<br />
+      All versions of the Infinity Engine, except that used in Planescape: Torment, make some internal use of the <a href="http://www.lua.org/" class="offsite">Lua</a> programming language, as developed by TeCGraf at the Pontifical Catholic University of Rio de Janeiro in Brazil. In the Infinity Engine, LUA is primarily used for the cheats/debugging console. The debug console actually allows complete LUA programs to be entered and run, though these programs can only have a very limited effect on the game and the engine. The LUA <a href="http://www.lua.org/docs.html" class="offsite">documentation</a> is available online, though knowledge of LUA is of limited use in IE modding. It should be mentioned, that unlike other engines where LUA is used, the Infinity Engine AI scripts have nothing to do with LUA.<br />
       <br />
       The data types used to describe the file formats used by the Infinity Engine are:<br />
       <br />
@@ -99,7 +99,7 @@
               <td><code>.key</code></td>
               <td>'<code>KEY </code>'</td>
               <td>&nbsp;</td>
-              <td>A directory of resources, resource locations and resource types. Each game generally have one KEY file, located in the main game directory.</td>
+              <td>A directory of resources, resource locations and resource types. Each game generally has one KEY file, located in the main game directory.</td>
             </tr>
             <tr>
               <td>N/A</td>
@@ -113,7 +113,7 @@
               <td><code>.cbf</code></td>
               <td>'<code>BIF </code>'</td>
               <td>&nbsp;</td>
-              <td>zlib compressed BIF file; index by the KEY file.</td>
+              <td>zlib compressed BIF file; indexed by the KEY file.</td>
             </tr>
             <tr>
               <td>N/A</td>

file_formats/ie_formats/2da.htm

@@ -18,7 +18,7 @@
     <br />
     2DA files should always contain at least four rows;<br />
     <div class="indent1">
-      The first row contains the file signature, &quot;2DA V1.0&quot;, which may be preceeded by white space.<br />
+      The first row contains the file signature, &quot;2DA V1.0&quot;, which may be preceded by white space.<br />
       The second row contains the &quot;default value&quot; for the file.<br />
       The third row contains column headings.<br />
       Subsequent rows consist of row data.<br />

file_formats/ie_formats/_dlg_v1.htm

@@ -53,7 +53,7 @@
     be associated with a transition, which can be used, for instance, to start a
     store. And a transition has a "DLG" resource associated with it, for
     conversations which involve multiple people. (i.e. You talk to somebody and then
-    a 3rd part interrupts you, etc.) That takes care of the preliminary details.
+    a 3rd party interrupts you, etc.) That takes care of the preliminary details.
     Now, on to the format.<br />
     </div>
     <br />

file_formats/ie_formats/acm.htm

@@ -8,15 +8,15 @@
 
     <div class="fileHeader">General Description</div>
     <div class="indent1">
-    The ACM format is a properity copyrighted format, used by Interplay.<br />
+    The ACM format is a proprietary copyrighted format, used by Interplay.<br />
     <br />
     ACM files are used for ambients, area music and game shell music. The ACM files in the game are located in the \music folder, under the main game directory. Each ambient is stored under its own subfolder, for example the ambient of area 1 could be stored under music\AR1, while the ambient of area 2 could be under music\AR2.<br />
     <br />
     The ACM files under the subdirectories are named in the following format:<br />
     <div class="indent1">Subdirectory Name+File Tag+(Number)</div>
     For example, the files under the BC1 can be BC1A1 or BC1ZA.<br />
     <br />
-    Music is usually made up of many smaller files as opposed to one larger file - this allows music to have a smooth progression when conditions change (ie. end of combat, end of ambient sound) rather than a sharp interuption. This smooth progression is controlled via MUS files, which act as ACM playlists. All MUS files are in the \music folder, and are attached to areas or romances through 2da files.<br />
+    Music is usually made up of many smaller files as opposed to one larger file - this allows music to have a smooth progression when conditions change (ie. end of combat, end of ambient sound) rather than a sharp interruption. This smooth progression is controlled via MUS files, which act as ACM playlists. All MUS files are in the \music folder, and are attached to areas or romances through 2da files.<br />
     </div>
     <br />
 

file_formats/ie_formats/are_v1.htm

@@ -2473,7 +2473,7 @@
     <div class="fileHeader">V1.0 <a name="formAREAV1_0_Rest_Interruptions">Rest Interruptions</a></div>
     <div class="indent1">
       <br />
-      This section determines the creatures that interupt party resting (e.g. soldiers in Athkatla that prevent rest when inside the city).<br />
+      This section determines the creatures that interrupt party resting (e.g. soldiers in Athkatla that prevent rest when inside the city).<br />
       The section is E4h bytes in length.<br />
       <br />
       <table border="1" width="98%">

file_formats/ie_formats/are_v9.1.htm

@@ -2129,7 +2129,7 @@
     <div class="fileHeader">V9.1 <a name="formAREAV9_1_Rest_Interruptions">Rest Interruptions</a></div>
     <div class="indent1">
       <br />
-      This section determines the creatures that interupt party resting (e.g. soldiers in Athkatla that prevent rest when inside the city).<br />
+      This section determines the creatures that interrupt party resting (e.g. soldiers in Athkatla that prevent rest when inside the city).<br />
       The section is E4h bytes in length.<br />
       <br />
       <table border="1" width="98%">

file_formats/ie_formats/bam_v1.htm

@@ -84,7 +84,7 @@
             <td>1 (unsigned byte)</td>
             <td>The compressed colour index for RLE encoded bams (ie. this is the colour that is compressed)<br />
               <br />
-              The transparency index is set to the first occurence of RGB(0,255,0). If RGB(0,255,0) does not exist in the palette then transparency index is set to 0</td>
+              The transparency index is set to the first occurrence of RGB(0,255,0). If RGB(0,255,0) does not exist in the palette then transparency index is set to 0</td>
           </tr>
           <tr>
             <td>0x000c</td>

file_formats/ie_formats/bcs.htm

@@ -8,7 +8,7 @@
     <br />
 
     <div class="fileHeader">General Description</div>
-    <div class="indent1">These files represent scripted actions. <code>.bcs</code> files are scripts attached to anything other than the player characters.&nbsp; <code>.bs</code> files are scripts which drive a characters actions automatically (AI scripts) based on criteria in the environment.<br />
+    <div class="indent1">These files represent scripted actions. <code>.bcs</code> files are scripts attached to anything other than the player characters.&nbsp; <code>.bs</code> files are scripts which drive a character's actions automatically (AI scripts) based on criteria in the environment.<br />
     Just as the files from which they are compiled, these script files make use of the concept of &quot;triggers&quot; and &quot;responses&quot;. A trigger is a condition which causes a response with a certain probability. A response is one or more calls to functions they have exposed to the script. I believe this to be the difference between <code>.bcs</code> and <code>.bs</code> files. (They are assigned different resource types in the resource management code, too.)<br />
     </div>
     <br />
@@ -19,7 +19,7 @@
     The format will be given in a top-down sense: i.e. I will describe the formatting of top-level blocks, and then I will describe the contents of the blocks. The process will proceed recursively until the whole format is described. The top-level block is the <a href="#pFILE">script file</a>.<br />
     <br />
     <div class="fileHeader"><a name="pPARAM">Parameters</a></div>
-    First, a brief word on &quot;function parameters&quot;. Both <a href="#pTRIGGER">triggers</a> and <a href="#pACTION">actions</a> are essentially calls to functions inside the Infinity Engine. Triggers can take up to 7 arguments, and actions can take up to 10 arguments. There are three allowable forms of arguments: strings, integers, and objects. The different function calls are defined in TRIGGER.IDS and ACTION.IDS. There are also functions defined in SVTRIOBJ.IDS, which are a {sub|super} set of of the function calls defined in TRIGGER.IDS. They are probably used for {insert spiel here}. String arguments are simply quoted strings (i.e. ASCII strings delimited by the double quote character &quot;). The format of these descriptions is given below, by way of an example (from BG's TRIGGER.IDS):<br />
+    First, a brief word on &quot;function parameters&quot;. Both <a href="#pTRIGGER">triggers</a> and <a href="#pACTION">actions</a> are essentially calls to functions inside the Infinity Engine. Triggers can take up to 7 arguments, and actions can take up to 10 arguments. There are three allowable forms of arguments: strings, integers, and objects. The different function calls are defined in TRIGGER.IDS and ACTION.IDS. There are also functions defined in SVTRIOBJ.IDS, which are a {sub|super} set of the function calls defined in TRIGGER.IDS. They are probably used for {insert spiel here}. String arguments are simply quoted strings (i.e. ASCII strings delimited by the double quote character &quot;). The format of these descriptions is given below, by way of an example (from BG's TRIGGER.IDS):<br />
     <pre>0x401D Specifics(O:Object*,I:Specifics*Specific)</pre>
     The first thing on the line is the ID (in hex. IDs in scripts are typically in decimal). Next is the name of the function. Inside the parentheses, similarly to C/C++, is a comma-delimited list of argument type and argument name. The argument types are:<br />
     <div class="indent1">
@@ -93,7 +93,7 @@
 
     <div class="fileHeader"><a name="pRESPSET">Response set</a></div>
     <div class="indent1">
-    Each response in a reponse set has a certain weight associated with it. Usually, this is 100%, but if not, then the response is only played with a certain probability. To find the chance of a particular response being chosen, sum the probabilities of all the responses in the response set. Each response Rnhas a probability <code>Pn/Sum(P)</code> of being chosen, if the response set is to be played.<br />
+    Each response in a response set has a certain weight associated with it. Usually, this is 100%, but if not, then the response is only played with a certain probability. To find the chance of a particular response being chosen, sum the probabilities of all the responses in the response set. Each response Rn has a probability <code>Pn/Sum(P)</code> of being chosen, if the response set is to be played.<br />
     <div class="indent1">
       <li><code>RS</code> (newline)
       <li><a href="#pRESPONSE">Response</a>

file_formats/ie_formats/cre_v1.2.htm

@@ -1011,7 +1011,7 @@
     <div class="fileHeader"><a name="CREV1_2_Overlay">CRE V1.2 Overlays</a></div>
     <div class="indent1">
       <br />
-      This section details visual effects applied to the creature by opcode 201 (the specific effect applied is controled by paramter 2). Each entry is 40 bytes.<br />
+      This section details visual effects applied to the creature by opcode 201 (the specific effect applied is controlled by parameter 2). Each entry is 40 bytes.<br />
       <div class="indent1">
         0 - SPWI304 - Cloak of Warding - absorbs 3d4+level damage then removed, or level*5 seconds expired<br />
         1 - SPWI111 - Shield - AC = 3, +1 to saving throws, removed after level*25 seconds<br />

file_formats/ie_formats/eff_v2.htm

@@ -32,7 +32,7 @@
     {% assign offset_header_name = "effv2_Body" %}
     {% assign offset_header_display_name = "EFF V2.0 Body" %}
     {% assign offsets = site.data.file_formats.eff_v2.body %}
-    {% assign offset_header_desc = "When an effect is called via an eff, several of the fields (including duration and timing mode) are overriden by the calling SPL/ITM. Other fields are copied directly from the calling SPL/ITEM and overwrite the values defined in the EFF." %}
+    {% assign offset_header_desc = "When an effect is called via an eff, several of the fields (including duration and timing mode) are overridden by the calling SPL/ITM. Other fields are copied directly from the calling SPL/ITEM and overwrite the values defined in the EFF." %}
     {% assign offset_start = 8 %}
     {% include offset_table.html %}