summaryrefslogtreecommitdiff
path: root/src/table
diff options
context:
space:
mode:
authorJMcKiern <jmckiern@tcd.ie>2019-09-29 21:27:32 +0100
committerCharles Pigott <charlespigott@googlemail.com>2019-09-29 21:27:32 +0100
commit04f659e768486da4fc73a97a633f140d9733bf78 (patch)
tree7d1ecef7d6a39891d2485ae8a0ef8f12673d2b93 /src/table
parent316e4e94171d8d269b80dd9e329fc1fe610fbfe2 (diff)
downloadopenttd-04f659e768486da4fc73a97a633f140d9733bf78.tar.xz
Fix: Some typos found using codespell
Diffstat (limited to 'src/table')
-rw-r--r--src/table/elrail_data.h2
-rw-r--r--src/table/gameopt_settings.ini2
-rw-r--r--src/table/settings.h.preamble2
-rw-r--r--src/table/settings.ini4
-rw-r--r--src/table/sprites.h4
5 files changed, 7 insertions, 7 deletions
diff --git a/src/table/elrail_data.h b/src/table/elrail_data.h
index 691536003..df5788fa8 100644
--- a/src/table/elrail_data.h
+++ b/src/table/elrail_data.h
@@ -412,7 +412,7 @@ static const SortableSpriteStruct RailCatenarySpriteData_Tunnel[] = {
* Identifiers for Wires:
* <ol><li>Direction of the wire</li>
* <li>Slope of the tile for diagonals, placement inside the track for horiz/vertical pieces</li>
- * <li>Place where a pylon shoule be</li></ol>
+ * <li>Place where a pylon should be</li></ol>
* Identifiers for Pylons:
* <ol><li>Direction of the wire</li>
* <li>Slope of the tile</li>
diff --git a/src/table/gameopt_settings.ini b/src/table/gameopt_settings.ini
index 9bacb80c7..b18ed9d75 100644
--- a/src/table/gameopt_settings.ini
+++ b/src/table/gameopt_settings.ini
@@ -12,7 +12,7 @@ static uint16 _old_diff_custom[GAME_DIFFICULTY_NUM];
uint8 _old_diff_level; ///< Old difficulty level from old savegames
uint8 _old_units; ///< Old units from old savegames
-/* Most of these strings are used both for gameopt-backward compatability
+/* Most of these strings are used both for gameopt-backward compatibility
* and the settings tables. The rest is here for consistency. */
static const char *_locale_currencies = "GBP|USD|EUR|YEN|ATS|BEF|CHF|CZK|DEM|DKK|ESP|FIM|FRF|GRD|HUF|ISK|ITL|NLG|NOK|PLN|RON|RUR|SIT|SEK|YTL|SKK|BRL|EEK|custom";
static const char *_locale_units = "imperial|metric|si";
diff --git a/src/table/settings.h.preamble b/src/table/settings.h.preamble
index 08380cbf1..65fc489fa 100644
--- a/src/table/settings.h.preamble
+++ b/src/table/settings.h.preamble
@@ -33,7 +33,7 @@ static size_t ConvertLandscape(const char *value);
* Thse are for members in the struct described by the current
* #SettingDesc list / .ini file. Here, 'base' specifies type of the
* struct while 'var' points out the member of the struct (the actual
- * struct to store it in is implicitely defined by the #SettingDesc
+ * struct to store it in is implicitly defined by the #SettingDesc
* list / .ini file preamble the entry is in).
*
* The something part defines the type of variable to store. There are a
diff --git a/src/table/settings.ini b/src/table/settings.ini
index 800d6f79c..714a8c86c 100644
--- a/src/table/settings.ini
+++ b/src/table/settings.ini
@@ -95,7 +95,7 @@ cat = SC_ADVANCED
; Saved settings variables.
-; Do not ADD or REMOVE something in this "difficulty.XXX" table or before it. It breaks savegame compatability.
+; Do not ADD or REMOVE something in this "difficulty.XXX" table or before it. It breaks savegame compatibility.
[SDT_VAR]
base = GameSettings
var = difficulty.max_no_competitors
@@ -3947,7 +3947,7 @@ cat = SC_EXPERT
; Since the network code (CmdChangeSetting and friends) use the index in this array to decide
; which setting the server is talking about all conditional compilation of this array must be at the
; end. This isn't really the best solution, the settings the server can tell the client about should
-; either use a seperate array or some other form of identifier.
+; either use a separate array or some other form of identifier.
;
; We might need to emulate a right mouse button on mac
diff --git a/src/table/sprites.h b/src/table/sprites.h
index 5f5aa4705..a0e068f8f 100644
--- a/src/table/sprites.h
+++ b/src/table/sprites.h
@@ -27,10 +27,10 @@
* All sprites which are described here are referenced only one to a handful of times
* throughout the code. When introducing new sprite enums, use meaningful names.
* Don't be lazy and typing, and only use abbreviations when their meaning is clear or
- * the length of the enum would get out of hand. In that case EXPLAIN THE ABBREVATION
+ * the length of the enum would get out of hand. In that case EXPLAIN THE ABBREVIATION
* IN THIS FILE, and perhaps add some comments in the code where it is used.
* Now, don't whine about this being too much typing work if the enums are like
- * 30 characters in length. If your editor doen't help you simplifying your work,
+ * 30 characters in length. If your editor doesn't help you simplifying your work,
* get a proper editor. If your Operating Systems don't have any decent editors,
* get a proper Operating System.
*