Fix typos

doc/devdocs/IOFdata203/IOFdata.dtd

@@ -34,7 +34,7 @@
 
 	 Authors:
 	 	Stefan Nordmark, SWE
-	 	Kell Sønnichsen, DEN
+	 	Kell Sønnichsen, DEN
 	 	Finn Arildsen, DEN
 	 	
 	 Date:
@@ -227,7 +227,7 @@
 	 - classes
 	 - races (i.e. event "days")
 	 - entry data (where to deliver entries)
-	 - services (e.g. accomodation)
+	 - services (e.g. accommodation)
 	 - web site information
 	 - accounts for fees
 -->
@@ -262,7 +262,7 @@
 
 <!-- Event Class
 	 A Class extended with event specific information, e.g. whether
-	 the class is transfered to another class due to lack of entries.
+	 the class is transferred to another class due to lack of entries.
 -->
 
 <!ELEMENT EventClass ((ClassId|Class), (((ClassRaceInfo,
@@ -932,7 +932,7 @@
 	 ##########
 	 
 	 The following elements are used for non-orienteering purposes,
-	 i.e. accomodation, payment, addresses, press, dates etc.
+	 i.e. accommodation, payment, addresses, press, dates etc.
 	 
 	 Also different "general purpose" elements, e.g. date and time.
 	 
@@ -1019,7 +1019,7 @@
 
 
 <!-- Service
-	 A general purpose service request, e.g. for accomodation.
+	 A general purpose service request, e.g. for accommodation.
 -->
 
 <!ELEMENT Service (ServiceId, Name, Amount, Comment?, MaxNumber?,

doc/devdocs/IOFdata30/CourseData_Relay_Step4.xml

@@ -170,7 +170,7 @@
         <CourseName>A</CourseName>
         <CourseFamily>Open long</CourseFamily>
       </TeamMemberCourseAssignment>
-      <!-- Team members on leg 2 (which is run by three parallel team memebrs) are assigned the course C of course family Open short -->
+      <!-- Team members on leg 2 (which is run by three parallel team members) are assigned the course C of course family Open short -->
       <TeamMemberCourseAssignment>
         <Leg>2</Leg>
         <LegOrder>1</LegOrder>

doc/devdocs/IOFdata30/iof.xsd

@@ -760,7 +760,7 @@
       <xsd:element name="Service" type="Service" minOccurs="0" maxOccurs="unbounded">
         <xsd:annotation>
           <xsd:documentation>
-            The services available for the event, e.g. accomodation and transport.
+            The services available for the event, e.g. accommodation and transport.
           </xsd:documentation>
         </xsd:annotation>
       </xsd:element>
@@ -940,7 +940,7 @@
       <xsd:element name="Service" type="Service" minOccurs="0" maxOccurs="unbounded">
         <xsd:annotation>
           <xsd:documentation>
-            The services available for the race, e.g. accomodation and transport.
+            The services available for the race, e.g. accommodation and transport.
           </xsd:documentation>
         </xsd:annotation>
       </xsd:element>
@@ -1411,7 +1411,7 @@
       <xsd:element name="Status" type="RaceClassStatus" minOccurs="0">
         <xsd:annotation>
           <xsd:documentation>
-            The status of the race, e.g. if results should be considered invalid due to misplaced constrols.
+            The status of the race, e.g. if results should be considered invalid due to misplaced controls.
           </xsd:documentation>
         </xsd:annotation>
       </xsd:element>
@@ -1741,7 +1741,7 @@
       <xsd:element name="AssignedFee" type="AssignedFee" minOccurs="0" maxOccurs="unbounded">
         <xsd:annotation>
           <xsd:documentation>
-            The fees that the team as a whole has to pay when entering the event. In a multi-race event, there is usually one element for each race. If there are differentated fees for the team members, specify them in the TeamEntryPerson elements.
+            The fees that the team as a whole has to pay when entering the event. In a multi-race event, there is usually one element for each race. If there are differentiated fees for the team members, specify them in the TeamEntryPerson elements.
           </xsd:documentation>
         </xsd:annotation>
       </xsd:element>
@@ -2715,7 +2715,7 @@
                     <xsd:enumeration value="Leg">
                       <xsd:annotation>
                         <xsd:documentation>
-                          The time behind refers to the best time of the competitors that are taking part on the same leg as this team member, independly of the course assigned.
+                          The time behind refers to the best time of the competitors that are taking part on the same leg as this team member, independently of the course assigned.
                         </xsd:documentation>
                       </xsd:annotation>
                     </xsd:enumeration>
@@ -2748,7 +2748,7 @@
                     <xsd:enumeration value="Leg">
                       <xsd:annotation>
                         <xsd:documentation>
-                          The position refers to all competitors that are taking part on the same leg as this team member, independly of the course assigned.
+                          The position refers to all competitors that are taking part on the same leg as this team member, independently of the course assigned.
                         </xsd:documentation>
                       </xsd:annotation>
                     </xsd:enumeration>
@@ -3093,7 +3093,7 @@
           <xsd:enumeration value="OK">
             <xsd:annotation>
               <xsd:documentation>
-                Control belongs to the course and has been punched (either by electronical punching or pin punching). If the time is not available or invalid, omit the Time element.
+                Control belongs to the course and has been punched (either by electronic punching or pin punching). If the time is not available or invalid, omit the Time element.
               </xsd:documentation>
             </xsd:annotation>
           </xsd:enumeration>
@@ -3157,7 +3157,7 @@
 
         Seconds delta storage mode
         --------------------------
-        The following byte is an unsigned 8-bit integer defining the waypoint's time as the number of seconds to add to the last waypoint's time. This storage mody can only be used when the difference to the last waypoint's time is an integer value.
+        The following byte is an unsigned 8-bit integer defining the waypoint's time as the number of seconds to add to the last waypoint's time. This storage mode can only be used when the difference to the last waypoint's time is an integer value.
 
         Consequently:
         - seconds delta storage mode is used when the waypoint's time is less than 256 seconds later than the last waypoint's time, and the difference between the times is an integer value.
@@ -4005,7 +4005,7 @@
   <xsd:complexType name="Service">
     <xsd:annotation>
       <xsd:documentation>
-        Defines a general purpose service request, e.g. for rental card or accomodation.
+        Defines a general purpose service request, e.g. for rental card or accommodation.
       </xsd:documentation>
     </xsd:annotation>
     <xsd:sequence>

doc/devdocs/OCAD10Format.txt

@@ -634,7 +634,7 @@ Objects are stored as a TElement structure.
                                         // graphic object: color number
 					// image object: CYMK color of object
     LineWidth: SmallInt;                // line with for image and graphic object
-    DiamFlags: SmallInt;                // flages: LineStyle by lines
+    DiamFlags: SmallInt;                // flags: LineStyle by lines
     Res2: double;                       // not used
 
     Mark: Byte;                         // Internal used
@@ -700,7 +700,7 @@ si_CoursePar = 1031
   // b = background for control descriptions
   // c = numbering (0=number, 1=number and code, 2=code only)
   // d = control descriptions for all controls
-  // e = event titel
+  // e = event title
   // f = control frequencies (0 = number and frequencies, 1 = frequencies only)
   // i = maximum rows in control description [integer]
   // l = distance to connection line
@@ -910,7 +910,7 @@ si_OimPar = 1025 (OCAD Internet Maps )
   // i = Overview height
   // m = Do not create tiles
   // r = Zoom range
-  // s = Select lable
+  // s = Select label
   // v = Overview width
   // w = Width
   // z = Zoom levels
@@ -1012,7 +1012,7 @@ si_SpotColor[list] = 10 (spot colors)
   // y = yellow
   // k = black
 
-si_FileInfo[list] = 11 (file informations)
+si_FileInfo[list] = 11 (file information)
 ------------------------------------------
   // First = text
 
@@ -1121,7 +1121,7 @@ si_ScalePar = 1039 (scales settings)
   // b = additional local horizontal offset in m
   // c = additional local vertical offset in m
   // d = grid distance for real world  in m
-  // g = grid distance for paper coordiantes in mm
+  // g = grid distance for paper coordinates in mm
   // i = grid and zone
   // m = map scale
   // r = real world cord (0=paper, 1=real world)

doc/devdocs/OCAD9Format.txt

@@ -793,7 +793,7 @@ si_DataSet[list] = 4 (dataset)
   // l = length unit
   // a = area unit
   // c = decimals
-  // h = horizontal coordiante
+  // h = horizontal coordinate
   // v = vertical coordinate
 
 si_DbObject[list] = 5 (object linked to a database)
@@ -847,7 +847,7 @@ si_OimPar = 1025 (OCAD Internet Maps )
   // i = Overview height
   // m = Do not create tiles
   // r = Zoom range
-  // s = Select lable
+  // s = Select label
   // v = Overview width
   // w = Width
   // z = Zoom levels
@@ -901,7 +901,7 @@ si_TilesPar = 1033
 
 Parameter Strings - Misc
 =============================================================================================
-si_FileInfo[list] = 11 (file informations)
+si_FileInfo[list] = 11 (file information)
 ------------------------------------------
   // First = text
 
@@ -964,7 +964,7 @@ si_ScalePar = 1039 (scales settings)
 ------------------------------------
   // a = real world angle
   // d = grid distance for real world  in m
-  // g = grid distance for paper coordiantes in mm
+  // g = grid distance for paper coordinates in mm
   // i = grid and zone
   // m = map scale
   // r = real world cord (0=paper, 1=real world)

doc/devdocs/fileformat.txt

@@ -2,7 +2,7 @@ MapEdit file format specification.
 
 geode - top node of the document
   Attributes:
-    format: (int) full version of the format. Changes in this are totally uncompatible
+    format: (int) full version of the format. Changes in this are totally incompatible
     revision: (int) revision of the format. Indicates the version of nodes and attributes 
               in the file format. When reading a version with a revision > one you
               know, warn the user and ignore stuff you don't understand
@@ -40,7 +40,7 @@ symboldefs: contains all the symbol definitions in the map
 
 symboldef:
   Attributes:
-     id - id of the symbol definiton [required]
+     id - id of the symbol definition [required]
      name - name of the symbol definition [optional: def empty]
      isom-number - number of the symbol for ISOM/OCAD [required]
      type - type is "point", "line", "area", "text" [required]
@@ -92,7 +92,7 @@ dashes:
 
 shorten:
    Attributes:
-     beginning-length - lenght of beginning shortening [required]
+     beginning-length - length of beginning shortening [required]
      end-length - length of end shortening [required]
      pointed-ends - draw pointed ends? [required]
 
@@ -107,7 +107,7 @@ linesymbol:
     Attributes:
       location -(required) where on line glyph appears ("begin", "end", ...)
       number - (optional) number of glyphs at each point [ default: 1]
-      spacing - (optional, if number > 1) spacing of mulptiple glyphs [
+      spacing - (optional, if number > 1) spacing of multiple glyphs [
       spaced-distance - (if location=="spaced") spacing along line
       spaced-end-distance - (if location=="spaced") spacing from end of line
       spaced-minimum - (if location=="spaced") minimum number of symbols [optional, default = 1]

doc/devdocs/format7.txt

@@ -31,7 +31,7 @@ Here is a list of changes:
 - TLTextSym: new variables Tool, FrWidth (reserved in OCAD 6)
 - TAreaSym: new variable Tool (reserved in OCAD 6)
 - TTextSym: new variable FrWidth (reserved in OCAD 6)
-- TStp: new varialbles RealWorldCord, FileName, HatchAreas,
+- TStp: new variables RealWorldCord, FileName, HatchAreas,
     HideTemp, TempMode, TempColor
 
 The OCAD 8 format is still under development. However here are the
@@ -990,7 +990,7 @@ of the file and adjust SetupPos and SetupSize.
                                {Last 8 Zoom magnification for use
                                in the Zoom out command. TZoomRec
                                is explained below.}
-    nZoomHist: longint;        {number of magnificiations in
+    nZoomHist: longint;        {number of magnifications in
                                ZoomHist}
 
                                {OCAD 6: the setup ends here

doc/devdocs/format8.txt

@@ -1013,7 +1013,7 @@ of the file and adjust SetupPos and SetupSize.
                                {Last 8 Zoom magnification for use
                                in the Zoom out command. TZoomRec
                                is explained below.}
-    nZoomHist: longint;        {number of magnificiations in
+    nZoomHist: longint;        {number of magnifications in
                                ZoomHist}
 
                                {OCAD 6: the setup ends here

doc/devdocs/ocadformat.txt

@@ -1013,7 +1013,7 @@ of the file and adjust SetupPos and SetupSize.
                                {Last 8 Zoom magnification for use
                                in the Zoom out command. TZoomRec
                                is explained below.}
-    nZoomHist: longint;        {number of magnificiations in
+    nZoomHist: longint;        {number of magnifications in
                                ZoomHist}
 
                                {OCAD 6: the setup ends here

doc/userdocs/Help/ControlsAutomaticNumbering.htm

@@ -16,8 +16,8 @@ <h1>Event/Automatic Numbering...</h1>
 <p>Purple Pen automatically numbers newly created controls according the settings in this dialog.</p>
 <p><b>Starting code.</b> This is the first code that is used. To meet IOF guidelines, this should be 31 or greater.</p>
 <p><b>Disallow codes that could be read upside-down.</b> If this box is checked, control codes that read as a <I>different</I> control code upside-down are skipped. Example codes that would be skipped are 66, 89, 108, 119. Check this box if control codes could possibly be misread by competitors.</p>
-<p><b>Apply these settings to newly created controls only.</b> If this option is selected, the codes of existing controls are not changed. Any newly created control will receive a unique control code chosed according to the previous options.</p>
-<p><b>Renumber existing controls also.</b> If this option is selected, all the existing controls will receive new control codes, consecutively numbers according to the previous options. Newly created controls will also receive a unique control code chosed according to the previous options.</p>
+<p><b>Apply these settings to newly created controls only.</b> If this option is selected, the codes of existing controls are not changed. Any newly created control will receive a unique control code chosen according to the previous options.</p>
+<p><b>Renumber existing controls also.</b> If this option is selected, all the existing controls will receive new control codes, consecutively numbers according to the previous options. Newly created controls will also receive a unique control code chosen according to the previous options.</p>
 <p>Regardless of the settings in this dialog, you can always change controls to have any desired code (including letters) by using the <a href="ControlsChangeCodes.htm">Controls/Change Codes</a> command.
 <!-- #EndEditable -->
 </BODY>

doc/userdocs/Help/FileCreateRouteGadget.htm

@@ -23,7 +23,7 @@ <h1>File/Create RouteGadget Files...</h1>
 	<li>A .xml file that describes the locations of the controls and the courses</li>
 	<li>A file from the timing program with split times for each competitor</li>
 </ul>
-<p>This command automatically creates the first two (three if geoferenced) files. After the event is 
+<p>This command automatically creates the first two (three if georeferenced) files. After the event is 
 complete, you must obtain the timing program output before posting the event to 
 Route Gadget.</p>
 <p>When creating the image of the map, Purple Pen automatically creates a map 
@@ -33,7 +33,7 @@ <h1>File/Create RouteGadget Files...</h1>
 <img alt="Create RouteGadget Files Dialog" src="CreateRouteGadgetFiles.png"></p>
 <p>This dialog has several options to customize the result.</p>
 <h2>File Name section</h2>
-<p>This section allows settng the file name (without the .xml or .gif extension) 
+<p>This section allows setting the file name (without the .xml or .gif extension) 
 for the two files that are created. The default name is the name of the event.</p>
 <h2>Folder section</h2>
 <p>This section determines in which folder (directory) the RouteGadget files are 

doc/userdocs/Help/GpsCreateGpxFile.htm

@@ -15,7 +15,7 @@ <h1>File/Create GPX File...</h1>
 <p>Creates GPX file with the control locations for use on an portable GPS unit or smart phone.</p>
     <p>A GPX file is a standard file with GPS coordinates (waypoints) in it. The GPX file can be used with a portable GPS unit or smartphone to verify the locations of controls when setting them. Consult the documentation for your GPS unit to learn how to send GPX files to it.</p>
     <p>In order to create a GPX file, the map file must be an OCAD or OpenOrienteering Mapper file, and the file must be georeferenced. Georeferencing a map sets up a mapping between coordinates on the paper, and geographic coordinates on the earth. <a href="http://wiki.ocad.com/en.wiki/index.php?title=Create_a_New_Map#Georeference_the_Map">See more information about setting up a georeferenced map in OCAD</a>. Purple Pen supports most, but not all, coordinate systems that OCAD supports. Purple Pen does not support User Defined coordinate systems.</p>
-    <p><strong>Important</strong>: Do not rely solely on GPS coordinate to place controls in the field! Competitors need to be able to navigate to the control location using only the map and compass, and it is the course setter&#39;s resposibility to ensure that the control is fairly set, that the control site is accurately mapped, and that the control site can be navigated to. GPS locations should be treated only as a double check to prevent errors.</p>
+    <p><strong>Important</strong>: Do not rely solely on GPS coordinate to place controls in the field! Competitors need to be able to navigate to the control location using only the map and compass, and it is the course setter&#39;s responsibility to ensure that the control is fairly set, that the control site is accurately mapped, and that the control site can be navigated to. GPS locations should be treated only as a double check to prevent errors.</p>
 <p>
 <img alt="Create GPX File Dialog" src="CreateGpxFile.png"></p>
 <p>This dialog has a few options to customize how the GPX File is created.</p>

doc/userdocs/Help/Variations.htm

@@ -22,9 +22,9 @@ <h2>Overview of Variations</h2>
 <p>There are two possible ways through the course: A and B. Variation A visits controls 31, 48, 36, 38. Variation B visits controls 31, 40, 43, 38. In 
 a two-person relay, one team can run variation A, then B, while another team runs variation B, then A.
 </p>
-<p>A more complex course can sequence two or more forks. This provides more possible ways throught the course. For example, consider the following course, with two forks:</p>
+<p>A more complex course can sequence two or more forks. This provides more possible ways through the course. For example, consider the following course, with two forks:</p>
 <p><img src="Variation2.png" /></p>
-<p>There are four possible ways throught the course, which are designated by letter pairs of which branches to take. Variation AC 
+<p>There are four possible ways through the course, which are designated by letter pairs of which branches to take. Variation AC 
 visits 31, 48, 36, 38, 50, 39. Variation AD visits 31, 48, 36, 38, 49, 39. Variation BC visits 31, 40, 43, 38, 50, 39. Variation 
 BD visits 31, 40, 43, 38, 49, 39.
 </p>

doc/userdocs/Help/ViewClearAdditionalCourses.htm

@@ -5,7 +5,7 @@
 <meta name="GENERATOR" content="Microsoft&reg; HTML Help Workshop 4.1">
 <link rel=stylesheet href="StyleSheet.css" type="text/css">
 <!-- #BeginEditable "doctitle" -->
-<Title>View/Clear Other Couses</Title>
+<Title>View/Clear Other Courses</Title>
 <!-- #EndEditable -->
 </HEAD>
 <BODY>