Fixed all errors in doc building

This commit is contained in:
Griatch 2020-07-11 00:14:13 +02:00
parent 9fbfc8f8d0
commit 76761825d0
80 changed files with 766 additions and 767 deletions

View file

@ -8,21 +8,21 @@ to you, but some things may still be useful.
## Find your way
- [Directory-Overview](../Howto/Starting/Part1/Gamedir-Overview)
- [Quirks of Evennia](Quirks)
- [Quirks of Evennia](./Quirks)
## Setting up a workflow
- [Setting up PyCharm](Setting-up-PyCharm)
- [Using Version-Control](Version-Control)
- [Updating Evennia sources](Updating-Your-Game)
- [Setting up PyCharm](./Setting-up-PyCharm)
- [Using Version-Control](./Version-Control)
- [Updating Evennia sources](./Updating-Your-Game)
## Coding away
- [Ways to Debug](Debugging)
- [Adding unit-tests](Unit-Testing)
- [Ways to Debug](./Debugging)
- [Adding unit-tests](./Unit-Testing)
## Advanced concepts
- [Continuous Integration](Continuous-Integration)
- [Using Travis](Using-Travis)
- [Profiling](Profiling)
- [Continuous Integration](./Continuous-Integration)
- [Using Travis](./Using-Travis)
- [Profiling](./Profiling)

View file

@ -27,7 +27,7 @@ Among those you will need:
* A Continuous Integration Environment.
* I recommend [TeamCity](https://www.jetbrains.com/teamcity/) which has an in-depth [Setup
Guide](https://confluence.jetbrains.com/display/TCD8/Installing+and+Configuring+the+TeamCity+Server)
* [Source Control](Version-Control)
* [Source Control](./Version-Control)
* This could be Git or SVN or any other available SC.
## Linux TeamCity Setup

View file

@ -324,7 +324,7 @@ developer mailing list or IRC chat to see beforehand if your feature is deemed s
as a core feature in the engine. When it comes to bug-fixes, other developers may also have good
input on how to go about resolving the issue.
To contribute you need to have [forked Evennia](Version-Control#forking-evennia) first. As described
To contribute you need to have [forked Evennia](./Version-Control#forking-evennia) first. As described
above you should do your modification in a separate local branch (not in the master branch). This
branch is what you then present to us (as a *Pull request*, PR, see below). We can then merge your
change into the upstream master and you then do `git pull` to update master usual. Now that the