diff --git a/modules/system/assets/ui/docs/inspector.md b/modules/system/assets/ui/docs/inspector.md
index 353924332..73d62d666 100644
--- a/modules/system/assets/ui/docs/inspector.md
+++ b/modules/system/assets/ui/docs/inspector.md
@@ -14,7 +14,7 @@ Clicking an inspectable element displays Inspector for that element. Any HTML el
 
 * `data-inspectable` - indicates that Inspector should be created when the element is clicked.
 * `data-inspector-title` - sets the Inspector popup title.
-* `data-inspector-config` - contains the Inspector configuration JSON string. If this attribute is not specified, the configuration is loaded from the server, see the [Dynamic configuration and dynamic items](#) section below.
+* `data-inspector-config` - contains the Inspector configuration JSON string. If this attribute is not specified, the configuration is loaded from the server, see the [Dynamic configuration and dynamic items](#dynamic-configuration-and-dynamic-items) section below.
 
 Inspectable elements should also contain a hidden input element used by Inspector for reading and writing values. The input element should be marked with the `data-inspector-values` data attribute.
 
@@ -185,7 +185,7 @@ This editor works like the `string` editor, but includes the autocomplete featur
         "items": {"start": "Start", "end": "End"}
     }
 
-The items are specified as a key-value object. The `items` parameter is optional, if it's not provided, the items will be loaded from the server - see [Dynamic configuration and dynamic items](#) section above.
+The items are specified as a key-value object. The `items` parameter is optional, if it's not provided, the items will be loaded from the server - see [Dynamic configuration and dynamic items](#dynamic-configuration-and-dynamic-items) section above.
 
 Values generated by the editor are strings. Example:
 
@@ -225,7 +225,7 @@ Displays a drop-down list. Options for the drop-down list can be specified stati
         }
     }
 
-The `options` attribute should be a key-value object. If the attribute is not specified, Inspector will try to load options from the server - see [Dynamic configuration and dynamic items](#) section above.
+The `options` attribute should be a key-value object. If the attribute is not specified, Inspector will try to load options from the server - see [Dynamic configuration and dynamic items](#dynamic-configuration-and-dynamic-items) section above.
 
 The editor generates a string value corresponding to the selected option, for example: 
 
@@ -246,7 +246,7 @@ The editor generates an object value, for example:
 
     {"options":{"option1":"Option 1","option2":"Option 2"}}
 
-The dictionary editor supports validation for the entire set (`required` and `length` validators) and for keys and values separately. See the validation description further in this document. The `validationKey` and `validationValue` define validation for keys and values, for example:
+The dictionary editor supports validation for the entire set (`required` and `length` validators) and for keys and values separately. See the [validation description](#defining-the-validation-rules) further in this document. The `validationKey` and `validationValue` define validation for keys and values, for example:
 
     {
         "property": "options",
@@ -435,7 +435,7 @@ The set editor allows users to select multiple predefined options with checkboxe
         "default": ["create", "update"]
     }
 
-The `items` attribute should be a key-value object. If the attribute is not specified, Inspector will try to load options from the server - see [Dynamic configuration and dynamic items](#) section above.
+The `items` attribute should be a key-value object. If the attribute is not specified, Inspector will try to load options from the server - see [Dynamic configuration and dynamic items](#dynamic-configuration-and-dynamic-items) section above.
 
 The `default` parameter, if specified, should be an array listing item keys selected by default.