From 71bd8d2383237b22fe99d4b46c45f50f438dff66 Mon Sep 17 00:00:00 2001 From: Garth Vander Houwen Date: Sun, 3 Jul 2022 12:02:54 -0700 Subject: [PATCH] Fix links --- docs/faq/channel.mdx | 2 +- docs/software/device/remote-admin.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/faq/channel.mdx b/docs/faq/channel.mdx index 9e286c1b..d6a1e99d 100644 --- a/docs/faq/channel.mdx +++ b/docs/faq/channel.mdx @@ -24,4 +24,4 @@ This is the first channel that's created for you when you initially setup your M ### What is a Secondary Channel? -As this is a new feature, secondary channels work on the device and the Python Script. Support for secondary channels by other clients is pending. [See further details here](/docs/software/device/device-channels#how-to-use-secondary-channels). +As this is a new feature, secondary channels work on the device and the Python Script. Support for secondary channels by other clients is pending. diff --git a/docs/software/device/remote-admin.mdx b/docs/software/device/remote-admin.mdx index 66f2da6f..a8d1254e 100644 --- a/docs/software/device/remote-admin.mdx +++ b/docs/software/device/remote-admin.mdx @@ -53,7 +53,7 @@ Notice that now we have a new secondary channel and the `--info` option prints o ## Sharing the admin channel with other nodes -Creating an "admin" channel automatically generates a preshared key, just like with [Multiple channel support](./device-channels). In order to administer to other nodes remotely, we need to copy the preshared key to the new nodes. +Creating an "admin" channel automatically generates a preshared key. In order to administer to other nodes remotely, we need to copy the preshared key to the new nodes. For this step you need physical access to both the nodes.