From b5e81577001f04f489e9fb000d4229e7b7cc9733 Mon Sep 17 00:00:00 2001 From: bluikko <14869000+bluikko@users.noreply.github.com> Date: Mon, 1 Nov 2021 20:13:18 +0700 Subject: [PATCH] Fix #7685: Doc image links (#7698) * Fix image link in custom-script.md * Fix image link in cable.md * Fix image link in power.md --- docs/core-functionality/power.md | 2 +- docs/customization/custom-scripts.md | 2 +- docs/models/dcim/cable.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/core-functionality/power.md b/docs/core-functionality/power.md index bdefb2afd..4d7d5f0ab 100644 --- a/docs/core-functionality/power.md +++ b/docs/core-functionality/power.md @@ -5,4 +5,4 @@ # Example Power Topology -![Power distribution model](/media/power_distribution.png) +![Power distribution model](../media/power_distribution.png) diff --git a/docs/customization/custom-scripts.md b/docs/customization/custom-scripts.md index cf052f918..9263f387c 100644 --- a/docs/customization/custom-scripts.md +++ b/docs/customization/custom-scripts.md @@ -240,7 +240,7 @@ An IPv4 or IPv6 network with a mask. Returns a `netaddr.IPNetwork` object. Two a !!! note To run a custom script, a user must be assigned the `extras.run_script` permission. This is achieved by assigning the user (or group) a permission on the Script object and specifying the `run` action in the admin UI as shown below. - ![Adding the run action to a permission](/media/admin_ui_run_permission.png) + ![Adding the run action to a permission](../media/admin_ui_run_permission.png) ### Via the Web UI diff --git a/docs/models/dcim/cable.md b/docs/models/dcim/cable.md index 18ac1002e..87ec68e03 100644 --- a/docs/models/dcim/cable.md +++ b/docs/models/dcim/cable.md @@ -25,7 +25,7 @@ A cable may be traced from either of its endpoints by clicking the "trace" butto In the example below, three individual cables comprise a path between devices A and D: -![Cable path](/media/models/dcim_cable_trace.png) +![Cable path](../media/models/dcim_cable_trace.png) Traced from Interface 1 on Device A, NetBox will show the following path: