Fix various typos

docs/source/Components/MonitorHandler.md

@@ -5,7 +5,7 @@ The *MonitorHandler* is a system for watching changes in properties or Attribute
 monitor can be thought of as a sort of trigger that responds to change.
 
 The main use for the MonitorHandler is to report changes to the client; for example the client
-Session may ask Evennia to monitor the value of the Characer's `health` attribute and report
+Session may ask Evennia to monitor the value of the Character's `health` attribute and report
 whenever it changes. This way the client could for example update its health bar graphic as needed.
 
 ## Using the MonitorHandler

docs/source/Components/Objects.md

@@ -34,7 +34,7 @@ An Evennia Object is, by definition, a Python class that includes  [evennia.obje
 
 Here, arrows indicate inheritance and point from-child-to-parent.
 
-So, for example `DefaultObjet` is a child of `DefaultCharacter` (in the Evennia library), which is a parent of `Character` (in the game dir). The class in the game-dir is the one you should modify for your game.
+So, for example `DefaultObject` is a child of `DefaultCharacter` (in the Evennia library), which is a parent of `Character` (in the game dir). The class in the game-dir is the one you should modify for your game.
 
 > Note the `ObjectParent` class. This is an empty mix-in that all classes in the game-dir inherits from. It's where you put things you want _all_ these classes to have. 
 

docs/source/Components/Scripts.md

@@ -11,7 +11,7 @@ If you ever consider creating an [Object](./Objects.md) with a `None`-location j
 - Scripts can _attach_ to Objects and Accounts via e.g. `obj.scripts.add/remove`. In the script you can then access the object/account as `self.obj` or `self.account`. This can be used to dynamically extend other typeclasses but also to use the timer component to affect the parent object in various ways. For historical reasons, a Script _not_ attached to an object is referred to as a _Global_ Script.
 
 ```{versionchanged} 1.0
-   In previus Evennia versions, stopping the Script's timer also meant deleting the Script object.
+   In previous Evennia versions, stopping the Script's timer also meant deleting the Script object.
    Starting with this version, the timer can be start/stopped separately and `.delete()` must be called
    on the Script explicitly to delete it.
 
@@ -333,7 +333,7 @@ GLOBAL_SCRIPTS.weather.db.current_weather = "Cloudy"
 ```
 
 ```{warning}
-Note that global scripts appear as properties on `GLOBAL_SCRIPTS` based on their `key`. If you were to create two global scripts with the same `key` (even with different typeclasses), the `GLOBAL_SCRIPTS` container will only return one of them (which one depends on order in the database). Best is to organize your scripts so that this does not happen. Otherwise, use `evennia.search_scripts` to get exactly the script you want.
+Note that global scripts appear as properties on `GLOBAL_SCRIPTS` based on their `key`. If you were to create two global scripts with the same `key` (even with different typeclasses), the `GLOBAL_SCRIPTS` container will only return one of them (which one depends on order in the database). Best is to organize your scripts so that this does not happen. Otherwise, use `evennia.search_script` to get exactly the script you want.
 ```
 
 There are two ways to make a script appear as a property on `GLOBAL_SCRIPTS`: