From f949f23f6c5687d20b6736474bfb201f71fd63b9 Mon Sep 17 00:00:00 2001 From: jeremystretch Date: Mon, 19 Jul 2021 14:00:31 -0400 Subject: [PATCH] Clean up errant links --- docs/models/ipam/iprange.md | 2 +- mkdocs.yml | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/models/ipam/iprange.md b/docs/models/ipam/iprange.md index 9d64ed964..ab712e5b2 100644 --- a/docs/models/ipam/iprange.md +++ b/docs/models/ipam/iprange.md @@ -2,7 +2,7 @@ This model represents an arbitrary range of individual IPv4 or IPv6 addresses, inclusive of its starting and ending addresses. For instance, the range 192.0.2.10 to 192.0.2.20 has eleven members. (The total member count is available as the `size` property on an IPRange instance.) Like prefixes and IP addresses, each IP range may optionally be assigned to a VRF and/or tenant. -IP also ranges share the same [functional roles](role.md) as prefixes and VLANs, although the assignment of a role is optional. Each IP range must be assigned an operational status, which is one of the following: +IP also ranges share the same functional roles as prefixes and VLANs, although the assignment of a role is optional. Each IP range must be assigned an operational status, which is one of the following: * Active - Provisioned and in use * Reserved - Designated for future use diff --git a/mkdocs.yml b/mkdocs.yml index 47b10a284..29c60caf2 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -68,7 +68,6 @@ nav: - Custom Scripts: 'customization/custom-scripts.md' - Reports: 'customization/reports.md' - Additional Features: - - Caching: 'additional-features/caching.md' - Change Logging: 'additional-features/change-logging.md' - Context Data: 'models/extras/configcontext.md' - Journaling: 'additional-features/journaling.md'