Fix doc config files and dead links

[policy/parent.git] / docs / drools / feature_controllerlogging.rst

diff --git a/docs/drools/feature_controllerlogging.rst b/docs/drools/feature_controllerlogging.rst
index 0677030..fc8d6da 100644 (file)
--- a/docs/drools/feature_controllerlogging.rst
+++ b/docs/drools/feature_controllerlogging.rst
@@ -2,6 +2,8 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 
+.. _feature_controllerlogging-label:
+
 ***************************
 Feature: Controller Logging
 ***************************
@@ -9,13 +11,8 @@ Feature: Controller Logging
 .. contents::
     :depth: 3
 
-Summary
-^^^^^^^
 The controller logging feature provides a way to log network topic messages to a separate controller log file for each controller. This allows a clear separation of network traffic between all of the controllers.
 
-Enabling Controller Logging
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
 Type "features enable controller-logging". The feature will now display as "enabled".
 
     .. image:: ctrlog_enablefeature.png
@@ -42,7 +39,8 @@ Once a logger for the controller is configured, start the drools-pdp and navigat
 
     .. image:: ctrlog_view.png
 
-The original network log remains and will append traffic information from all topics regardless of which controller it is for. To abbreviate and customize messages for the network log, refer to the `Feature MDC Filters <feature_mdcfilters.html>`_ documentation.
+The original network log remains and will append traffic information from all topics regardless of which controller it is for. To abbreviate and customize messages for the network log, refer to the
+:ref:`Feature MDC Filters <feature_mdcfilters-label>` documentation.
 
 
 End of Document