Fix typos.

docs/source/Howtos/Beginner-Tutorial/Part1/Beginner-Tutorial-Gamedir-Overview.md

@@ -63,7 +63,7 @@ This holds the server logs. When you do `evennia --log`, the evennia program is
 
 This contains all configuration files of the Evennia server. These are regular Python modules which  means that they must be extended with valid Python. You can also add logic to them if you wanted to.
 
-Common for the settings is that you generally will never them directly via their python-path; instead Evennia knows where they are and will read them to configure itself at startup. 
+Common for the settings is that you generally will never import them directly via their python-path; instead Evennia knows where they are and will read them to configure itself at startup. 
 
 - `settings.py` - this is by far the most important file. It's nearly empty by default, rather you
   are expected to copy&paste the changes you need from [evennia/default_settings.py](../../../Setup/Settings-Default.md). The default settings file is extensively documented. Importing/accessing the values in the settings file is done in a special way, like this: 
@@ -83,7 +83,7 @@ Common for the settings is that you generally will never them directly via their
 - `inlinefuncs.py` - [Inlinefuncs](../../../Concepts/Inline-Functions.md) are optional and limited 'functions' that can be embedded in any strings being  sent to a player. They are written as `$funcname(args)` and are used to customize the output  depending on the user receiving it. For example sending people the text `"Let's meet at $realtime(13:00, GMT)!`  would show every player seeing that string the time given in their own time zone. The functions added to this module will become new inlinefuncs in the game. See also the [FuncParser](../../../Components/FuncParser.md).
 - `inputfucs.py` - When a command like `look` is received by the server, it is handled by an [Inputfunc](InputFuncs) that redirects it to the cmdhandler system. But there could be other inputs coming from the clients, like  button-presses or the request to update a health-bar. While most common cases are already covered, this is  where one adds new functions to process new types of input.
 - `lockfuncs.py` - [Locks](../../../Components/Locks.md) and their component _LockFuncs_ restrict access to things in-game. Lock funcs are used in a mini-language  to defined more complex locks. For example you could have a lockfunc that checks if the user is carrying a given item, is bleeding or has a certain skill value. New functions added in this modules will  become available for use in lock definitions.
-- `mssp.py` - Mud Server Status Protocol is a way for online MUD archives/listings (which you usually have  to sign up for) to track which MUDs are currently online, how many players they have etc. While Evennia handles  the dynamic information automatically, this is were you set up the meta-info about your game, such as its  theme, if player-killing is allowed and so on. This is a more generic form of the Evennia Game directory.
+- `mssp.py` - Mud Server Status Protocol is a way for online MUD archives/listings (which you usually have  to sign up for) to track which MUDs are currently online, how many players they have etc. While Evennia handles  the dynamic information automatically, this is where you set up the meta-info about your game, such as its  theme, if player-killing is allowed and so on. This is a more generic form of the Evennia Game directory.
 - `portal_services_plugins.py` - If you want to add new external connection protocols to Evennia, this is the place  to add them.
 - `server_services_plugins.py` - This allows to override internal server connection protocols.
 - `web_plugins.py` - This allows to add plugins to the Evennia webserver as it starts.