Merge branch 'release/1.0.1'

* release/1.0.1:
  Raise version number to 1.0.1
  [BUGFIX] fix typo in composer.json #1
  Fix formatting in Documentation

README.rst

@@ -131,10 +131,10 @@ statement.
    :alt: DatabasePane
 
 Info: The extension uses the *connectToDB* hook to
-inject `Doctrine\DBAL\Logging\DebugStack` as a logger to the
+inject ``Doctrine\DBAL\Logging\DebugStack`` as a logger to the
 connection. At the end of the rendering process it retrieves the Logger
 and shows the logged queries. Its important to understand, that the
-extension adds `Doctrine\DBAL\Logging\DebugStack` in any case, even if
+extension adds ``Doctrine\DBAL\Logging\DebugStack`` in any case, even if
 its not shown in the frontend. This is due to log *all* queries from the
 very beginning ... but at that point the BE User is not initialized yet
 and its unclear if the DebugBar is enabled or not. Classical
@@ -144,7 +144,7 @@ VarDump
 --------
 
 Everybody knows the output of DebugUtility::var_dump() ... and everybody knows that it breaks the layout. Lets move the output
-to the TYPO3 Debugbar. Use `Konafets\TYPO3DebugBar\Overrides\DebuggerUtility::var_dump($variable)` and get an output like this:
+to the TYPO3 Debugbar. Use ``Konafets\TYPO3DebugBar\Overrides\DebuggerUtility::var_dump($variable)`` and get an output like this:
 
 .. figure:: https://raw.githubusercontent.com/konafets/typo3_debugbar/develop/Documentation/Images/VarDumpPane.png
    :alt: VarDumpPane

composer.json

@@ -16,7 +16,7 @@
     "maximebf/debugbar": "^1.15"
   },
   "replace": {
-    "typo_debugbar": "self.version"
+    "typo3_debugbar": "self.version"
   },
   "autoload": {
     "psr-4": {

ext_emconf.php

@@ -10,7 +10,7 @@
     'uploadfolder' => '0',
     'createDirs' => '',
     'clearCacheOnLoad' => 1,
-    'version' => '1.0.0',
+    'version' => '1.0.1',
     'constraints' => [
         'depends' => [
             'typo3' => '7.6.0-8.7.99',