Fixed doc generation

+ rollback the (now) unecessary changes

Signed-off-by: Olivier Gambier <olivier@docker.com>

docs/Dockerfile

@@ -19,7 +19,7 @@ RUN find /docs/content/registry -type f -name "*.md" -exec sed -i.old \
     -e '/^<!.*metadata]>/g' \
     -e '/^<!.*end-metadata.*>/g' \
     -e 's/\(\]\)\([(]\)\(\/\)/\1\2\/registry\//g' \
-    -e 's/\(\][(]\)\([A-z].*\)\(\.md\)/\1\/registry\/\2/g' \
+    -e 's/\(\][(]\)\([A-Za-z0-9]*\)\(\.md\)/\1\/registry\/\2/g' \
     -e 's/\([(]\)\(.*\)\(\.md\)/\1\2/g'  \
     -e 's/\(\][(]\)\(\.\/\)/\1\/registry\//g' \
     -e 's/\(\][(]\)\(\.\.\/\.\.\/\)/\1\/registry\//g' \

docs/configuration.md

@@ -279,7 +279,7 @@ Refer to `loglevel` to configure the level of messages printed.
 
 ## loglevel
 
-> **DEPRECATED:** Please use `log` instead.
+> **DEPRECATED:** Please use [log](#logs) instead.
 
 ```yaml
 loglevel: debug
@@ -1255,7 +1255,7 @@ Declare parameters for constructing the redis connections. Registry instances
 may use the Redis instance for several applications. The current purpose is
 caching information about immutable blobs. Most of the options below control
 how the registry connects to redis. You can control the pool's behavior
-with the `pool` subsection.
+with the [pool](#pool) subsection.
 
 <table>
   <tr>

docs/deploying.md

@@ -36,7 +36,7 @@ Then pull it back:
 
 By default, your registry stores its data on the local filesystem, inside the container.
 
-In a production environment, it's highly recommended to use [another storage backend](storagedrivers.md), by [configuring it](/configuration.md).
+In a production environment, it's highly recommended to use [another storage backend](storagedrivers.md), by [configuring it](configuration.md).
 
 If you want to stick with the local posix filesystem, you should store your data outside of the container.
 

docs/notifications.md

@@ -17,7 +17,7 @@ The Registry supports sending webhook notifications in response to events
 happening within the registry. Notifications are sent in response to manifest
 pushes and pulls and layer pushes and pulls. These actions are serialized into
 events. The events are queued into a registry-internal broadcast system which
-queues and dispatches events to endpoints. 
+queues and dispatches events to [_Endpoints_](#endpoints).
 
 ![](../images/notifications.png)
 
@@ -54,7 +54,7 @@ The above would configure the registry with an endpoint to send events to
 5 failures happen consecutively, the registry will backoff for 1 second before
 trying again.
 
-For details on the fields, please see the [configuration documentation](configuration.md).
+For details on the fields, please see the [configuration documentation](configuration.md#notifications).
 
 A properly configured endpoint should lead to a log message from the registry
 upon startup: