docs: fix links on Long Range page (#6790)

zwave-js · Apr 25, 2024 · 1dda6c2 · 1dda6c2
1 parent 742e787
commit 1dda6c2
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/docs/getting-started/long-range.md b/docs/getting-started/long-range.md
@@ -5,7 +5,7 @@ Z-Wave Long Range (ZWLR) is an addition to Z-Wave, that allows for a massively i
 There are a few things applications need to be aware of to support Long Range using Z-Wave JS.
 
 1. ZWLR node IDs start at 256. This can be used to distinguish between ZWLR and classic Z-Wave nodes.
-1. ZWLR has only two security classes, S2 Access Control and S2 Authenticated. Both must use a different security key than their Z-Wave Classic counterparts. To configure them, use the `securityKeysLongRange` property of the [`ZWaveOptions`](../api/driver#zwaveoptions)
-1. ZWLR inclusion works exclusively through [Smart Start](../getting-started/security-s2#smartstart).\
-   ZWLR nodes advertise support for Long Range in the `supportedProtocols` field of the `QRProvisioningInformation` object (see [here](../api/utils#other-qr-codes)). When this field is present, the user **MUST** have the choice between the advertised protocols. Currently this means deciding between including the node via Z-Wave Classic (mesh) or Z-Wave Long Range (no mesh).\
-   To include a node via ZWLR, set the `protocol` field of the `PlannedProvisioningEntry` to `Protocols.ZWaveLongRange` when [provisioning the node](../api/controller#provisionsmartstartnode).
+1. ZWLR has only two security classes, S2 Access Control and S2 Authenticated. Both must use a different security key than their Z-Wave Classic counterparts. To configure them, use the `securityKeysLongRange` property of the [`ZWaveOptions`](api/driver#zwaveoptions)
+1. ZWLR inclusion works exclusively through [Smart Start](getting-started/security-s2#smartstart).\
+   ZWLR nodes advertise support for Long Range in the `supportedProtocols` field of the `QRProvisioningInformation` object (see [here](api/utils#other-qr-codes)). When this field is present, the user **MUST** have the choice between the advertised protocols. Currently this means deciding between including the node via Z-Wave Classic (mesh) or Z-Wave Long Range (no mesh).\
+   To include a node via ZWLR, set the `protocol` field of the `PlannedProvisioningEntry` to `Protocols.ZWaveLongRange` when [provisioning the node](api/controller#provisionsmartstartnode).