Change to MyST parser

docs/source/Coding/Quirks.md

@@ -4,7 +4,7 @@
 This is a list of various quirks or common stumbling blocks that people often ask about or report
 when using (or trying to use) Evennia. They are not bugs.
 
-### Forgetting to use @reload to see changes to your typeclasses
+## Forgetting to use @reload to see changes to your typeclasses
 
 Firstly: Reloading the server is a safe and usually quick operation which will *not* disconnect any
 accounts.
@@ -13,7 +13,7 @@ New users tend to forget this step. When editing source code (such as when tweak
 commands or adding new commands to command sets) you need to either use the in-game `@reload`
 command or, from the command line do `python evennia.py reload` before you see your changes.
 
-### Web admin to create new Account
+## Web admin to create new Account
 
 If you use the default login system and are trying to use the Web admin to create a new Player
 account, you need to consider which `MULTIACCOUNT_MODE` you are in. If you are in
@@ -28,12 +28,12 @@ the "account" property on the Character and the "character" property on the Acco
 other. You must also set the lockstring of the Character to allow the Account to "puppet" this
 particular character.
 
-### Mutable attributes and their connection to the database
+## Mutable attributes and their connection to the database
 
 When storing a mutable object (usually a list or a dictionary) in an Attribute
 
 ```python
-     object.db.mylist = [1,2,3] 
+     object.db.mylist = [1,2,3]
 ```
 
 you should know that the connection to the database is retained also if you later extract that
@@ -62,16 +62,16 @@ use of `evennia.utils.dbserialize.deserialize`:
 The property `blist` is now `[1,2,3,4]` whereas `object.db.mylist` remains unchanged. If you want to
 update the database you'd need to explicitly re-assign the updated data to the `mylist` Attribute.
 
-### Commands are matched by name *or* alias
+## Commands are matched by name *or* alias
 
-When merging [command sets](../Components/Commands) it's important to remember that command objects are identified
+When merging [command sets](../Components/Commands.md) it's important to remember that command objects are identified
 *both* by key *or* alias. So if you have a command with a key `look` and an alias `ls`, introducing
 another command with a key `ls` will be assumed by the system to be *identical* to the first one.
 This usually means merging cmdsets will overload one of them depending on priority. Whereas this is
 logical once you know how command objects are handled, it may be confusing if you are just looking
 at the command strings thinking they are parsed as-is.
 
-### Objects turning to `DefaultObject`
+## Objects turning to `DefaultObject`
 
 A common confusing error for new developers is finding that one or more objects in-game are suddenly
 of the type `DefaultObject` rather than the typeclass you wanted it to be. This happens when you
@@ -82,7 +82,7 @@ back to the safe `DefaultObject` until you fix the problem and reload. Most erro
 be caught by any good text editors. Keep an eye on the terminal/console during a reload to catch
 such errors - you may have to scroll up if your window is small.
 
-### Overriding of magic methods
+## Overriding of magic methods
 
 Python implements a system of [magic
 methods](https://docs.python.org/3/reference/datamodel.html#emulating-container-types), usually
@@ -104,17 +104,17 @@ can result in very inconsistent and hard-to-diagnose errors.
 The moral of the story-- it can be dangerous to tinker with magic methods on typeclassed objects.
 Try to avoid doing so.
 
-### Known upstream bugs
+## Known upstream bugs
 
 - There is currently (Autumn 2017) a bug in the `zope.interface` installer on some Linux Ubuntu
 distributions (notably Ubuntu 16.04 LTS). Zope is a dependency of Twisted. The error manifests in
 the server not starting with an error that `zope.interface` is not found even though `pip list`
 shows it's installed. The reason is a missing empty `__init__.py` file at the root of the zope
-package. If the virtualenv is named "evenv" as suggested in the [Setup Quickstart](../Setup/Setup-Quickstart)
+package. If the virtualenv is named "evenv" as suggested in the [Setup Quickstart](../Setup/Setup-Quickstart.md)
 instructions, use the following command to fix it:
 
     ```shell
     touch evenv/local/lib/python2.7/site-packages/zope/__init__.py
     ```
 
-    This will create the missing file and things should henceforth work correctly.
+    This will create the missing file and things should henceforth work correctly.