fixed pdoc linking issues in documentation

Author: ThomasSteinbach

gcip/__init__.py

@@ -10,9 +10,9 @@
 * addons
 
 The **core** folder contains, as the name implies, all the core components that represent Gitlab CI objects in Python.
-You need to know that all class names from all Python modules within the _core_ folder are mapped to the gcip
-root module. This is done within the `__init__.py` of the gcip folder. Instead of _import gcip.core.job.Job_
-you should _import gcip.Job_. You should import all classes of the _core_ folder the same way.
+You need to know that all class names from all Python modules within the ```core``` folder are mapped to the gcip
+root module. This is done within the ```__init__.py``` of the gcip folder. Instead of ```import gcip.core.job.Job```
+you should ```import gcip.Job```. You should import all classes of the ```core``` folder the same way.
 
 Always remember:
 
@@ -30,13 +30,13 @@
 pipeline = pipeline.Pipeline()
 ```
 
-The **lib** folder contains all higher level objects which are derived from the _core_ objects. For example: `gcip.Rule`
-from _gcip.core.rule_ is the general Gitlab CI Rule representation, whereas _core.rules_ contains some convenient
-predefined Rule instances like `on_main()` or `on_tags()`.
+The **lib** folder contains all higher level objects which are derived from the ```core``` objects. For example: `gcip.Rule`
+from _gcip.core.rule_ is the general Gitlab CI Rule representation, whereas ```core.rules``` contains some convenient
+predefined Rule instances like ```on_main()``` or ```on_tags()```.
 
 The **tools** folder contains all code which is used by the library code but does not represent any Gitlab CI specific
 functionality. This directory also contains scripts which could be run on their own and are supposed to be called
-by Gitlab CI jobs during the pipeline execution. For example _gcip.tools.url.is_valid_url(str)_ which, as the name implies,
+by Gitlab CI jobs during the pipeline execution. For example ```gcip.tools.url.is_valid_url(str)``` which, as the name implies,
 checks if `str` is a valid url.
 
 The **addons** folder also contains code which extends the core components in form of higher level objects that provide
@@ -49,10 +49,10 @@
 
 We also use a following naming conventions throughout the library:
 
-* Files called _job_scripts.py_ hold functions that return strings, which could be used as command within
+* Files called ```_job_scripts.py``` hold functions that return strings, which could be used as command within
 Gitlab CI jobs.
 * Directories called _tools_ hold Python scripts which could be called by Gitlab CI jobs during the pipeline
-execution. They will be called directly from the Gitlab CI Python library, e.g. `python3 -m gcip.path.to.script`.
+execution. They will be called directly from the Gitlab CI Python library, e.g. ```python3 -m gcip.path.to.script```.
 """
 
 from pkg_resources import (