doc: Add ttn.org LoRaWAN links (TheThingsIndustries#631)

nejraselimovic · web-flow · commit 6fe0bd373404 · 2021-10-27T13:00:10.000+02:00
diff --git a/doc/content/devices/abp-vs-otaa/_index.md b/doc/content/devices/abp-vs-otaa/_index.md
@@ -8,11 +8,13 @@ This section can help you understand the differences between ABP and OTAA activa
 
 <!--more-->
 
+{{< note >}} Learn more about device activation in general and details about OTAA and ABP flow in [The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/end-device-activation/). {{</ note >}}
+
 A `DevEUI` is a 64-bit unique ID assigned to an end device by the manufacturer. This value is linked to the hardware and it cannot be altered.
 
 Unlike `DevEUI`, which identifies an end device globally, a 32-bit `DevAddr` identifies the end device within the current network and all communication after joining the network is done with it. A `DevAddr` value consists of `NwkAddr` (end device address within network) prefixed by a `NwkID` (network identifier).
 
-**Note:** `DevAddr` is not unique - multiple devices can have the same `DevAddr`. 
+{{< note >}} `DevAddr` is not unique - multiple devices can have the same `DevAddr`. {{</ note >}} 
 
 A `DevAddr` and session keys are assigned to an end device during a procedure called **activation**. LoRaWAN supports two modes of activating an end device: **ABP (Activation By Personalization)** and **OTAA (Over-The-Air Activation)**.
 
@@ -44,6 +46,8 @@ ABP's drawbacks are arising as consequences of its main characteristics.
 
   Unlike ABP, OTAA end devices re-negotiate frame counters and session keys at establishing each new session. Hence, the lifetime of an OTAA device is not conditioned by the width of the frame counter.
 
+  Read more about LoRaWAN security in [The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/security/).
+  
   For enhancing security, you can use a dedicated [Join Server](https://www.thethingsindustries.com/docs/reference/components/join-server/) to handle the join flow, Network Server and Application Server authentication, store root keys and generate session keys. Using a dedicated Join Server also prevents the vendor lock-in. Another option is using Hardware Secured Elements (see [ATECC608A](https://www.thethingsindustries.com/docs/devices/claim-atecc608a/)) which prevent the exposure of keys to software, firmware, manufacturing sites, and other third parties. 
 
 3. **ABP end devices use fixed network parameters.**
diff --git a/doc/content/devices/best-practices/_index.md b/doc/content/devices/best-practices/_index.md
@@ -36,7 +36,7 @@ The duty cycle of radio devices is often regulated by government. If this is the
 
 For example, in Europe, duty cycles are regulated by section 7.2.3 of the ETSI EN300.220 standard.
 
-Additionally, the LoRaWAN specification dictates duty cycles for the join frequencies, the frequencies devices of all LoRaWAN-compliant devices use for over-the-air activation (OTAA). In most regions this duty cycle is set to 1%.
+Additionally, the LoRaWAN specification dictates duty cycles for the join frequencies, the frequencies devices of all LoRaWAN-compliant devices use for over-the-air activation (OTAA). In most regions this duty cycle is set to 1%. Learn more about duty cycles in [The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/duty-cycle/).
 
 ## Expect Packet Loss
 
@@ -80,7 +80,7 @@ For devices that don't move, the LoRaWAN specification recommends allowing the N
 
 For moving devices, ADR should not be used since RF conditions will likely change, but since many moving devices are temporarily stationary, it is possible to save additional power by requesting ADR only during the time a device is stationary. ([LoRaWAN Specification 1.0.3, line 438](https://lora-alliance.org/sites/default/files/2018-07/lorawan1.0.3.pdf)).
 
-You may also use application specific knowledge to predict when ADR is appropriate. A tracking device can detect when it is moving, for example. A parked car sensor can detect when a parked car will affect RF conditions, and should fall back to another strategy. 
+You may also use application specific knowledge to predict when ADR is appropriate. A tracking device can detect when it is moving, for example. A parked car sensor can detect when a parked car will affect RF conditions, and should fall back to another strategy. [Learn more about how ADR is implemented in {{% tts %}}]({{< ref "/reference/adr" >}}).
 
 ## Use OTAA
 
@@ -94,7 +94,7 @@ Devices should also randomize initial power on delay (i.e. Join). See [Synchroni
 
 ## Frame Counters
 
-Devices must increment the frame counter after each uplink and downlink. Devices should use 32 bit counters for FCntUp and FCntDwn to prevent replay attacks.
+Devices must increment the frame counter after each uplink and downlink. Devices should use 32 bit counters for FCntUp and FCntDwn to prevent replay attacks. [Learn more about frame counters in The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/security/#frame-counters).
 
 ## Ack
 
diff --git a/doc/content/devices/class-b/index.md b/doc/content/devices/class-b/index.md
@@ -8,6 +8,8 @@ Class B end devices listen for downlink messages during ping slots. This allows
 
 <!--more-->
 
+Read more about device classes in [The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/classes/).
+
 ## Enabling and Disabling Class B
 
 In order to send Class B downlink messages to a single device, enable Class B support for the end device when creating or updating it with the `--supports-class-b` flag.
diff --git a/doc/content/devices/class-c/_index.md b/doc/content/devices/class-c/_index.md
@@ -10,6 +10,8 @@ This guide shows how to enable or disable Class C for an and device, and how to
 
 <!--more-->
 
+Read more about device classes in [The Things Network LoRaWAN documentation]](https://www.thethingsnetwork.org/docs/lorawan/classes/).
+
 ## Enabling and Disabling Class C
 
 In order to send Class C downlink messages to a single device, enable Class C support for the end device when creating or updating it with the `--supports-class-c` flag.
diff --git a/doc/content/getting-started/migrating/major-changes.md b/doc/content/getting-started/migrating/major-changes.md
@@ -30,7 +30,7 @@ See the [MAC settings guide]({{< ref "/devices/mac-settings" >}}) for more infor
 
 {{% tts %}} expects that all end devices comply with the LoRaWAN specification by default, which means that the end devices should respond to Network Server MAC command requests accordingly. If a device fails to answer a MAC Command in a timely manner, there may be disruptions to the device uplink or downlink traffic. As mentioned in the LoRaWAN specification, the Network Server of {{% tts %}} will always prioritize MAC commands over application payloads on downlink.
 
-In case a device is not fully compliant with the LORaWAN specification, it can still work on {{% tts %}}, but it may require custom MAC settings configuration.
+In case a device is not fully compliant with the LORaWAN specification, it can still work on {{% tts %}}, but it may require custom [MAC settings configuration]({{< ref "/devices/mac-settings" >}}).
 
 ### DevStatusReq
 
diff --git a/doc/content/getting-started/packet-broker/connect.md b/doc/content/getting-started/packet-broker/connect.md
@@ -34,6 +34,8 @@ If you own a NetID, enter your NetID to obtain your DevAddr prefix:
 
 Your DevAddr prefix is: <code><span data-content="dev-addr-prefix"></span></code>
 
+{{< note >}} See a full list of NetIDs, DevAddr Prefix assignments, operators, and regions they are allocated to in [The Things Network LoRaWAN documentation]](https://www.thethingsnetwork.org/docs/lorawan/prefix-assignments/). {{</ note >}}
+
 {{< note >}} This guide uses The Things Network NetID `000013` as example, which has DevAddr prefix `26000000/7`. {{</ note >}}
 
 ## Configure Packet Broker Agent
diff --git a/doc/content/getting-started/quick-start/index.md b/doc/content/getting-started/quick-start/index.md
@@ -16,6 +16,14 @@ First off, it's a good idea to understand what {{% tts %}} is. Learn that, and l
 
 In case you skipped the previous section, here is a quick summary: {{% tts %}} is a network server which implements the LoRaWAN protocol. To learn more about LoRaWAN, check out the [Learn section](https://thethingsnetwork.org/docs/lorawan) of The Things Network, or read up at the [LoRa Alliance](https://lora-alliance.org).
 
+Here is a video of Johan Stokking, the tech lead of The Things Industries and one of the core developers of {{% tts %}}, explaining LoRaWAN:
+
+{{< youtube "ZsVhYiX4_6o" >}}
+
+{{< note >}} Some common [use cases](https://www.thethingsnetwork.org/docs/lorawan/what-is-lorawan/#lorawan-use-cases) are explained in the video above, but there are certain limitations that make LoRaWAN not suitable for every use-case. Read about [LoRaWAN limitations in The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/limitations/). {{</ note >}}
+
+Make sure to get familiar about [LoRaWAN architecture](https://www.thethingsnetwork.org/docs/lorawan/architecture/) and [components]({{< ref "/reference/components" >}}), to understand how {{% tts %}} works.
+
 ## Start Using {{% tts %}}
 
 To get started with {{% tts %}}, you can simply [create an account](https://console.cloud.thethings.network) on The Things Network to start using [The Things Stack Community Edition]({{< ref "getting-started/ttn" >}}) for free.
@@ -40,6 +48,16 @@ Once you've added a device and it's connected to a gateway and to {{% tts %}}, s
 
 When you're ready to start running your LoRaWAN solution commercially, get in touch with us at [The Things Industries](https://thethingsindustries.com) for an affordable, scalable, deployment which is SLA backed.
 
+## Learn and Get Certified
+
+The Things Network certification program allows you to officially certify your LoRaWAN knowledge and skills.
+
+Visit [The Things Network Learn hub](https://www.thethingsnetwork.org/docs/lorawan/) or [The Things Academy on Udemy](https://www.udemy.com/course/lorawan-fundamentals/) to learn all about LoRa and LoRaWAN, and get prepared for [The Things Fundamentals certification](https://www.thethingsnetwork.org/achievements/a/the-things-certified-fundamentals/).
+
+Check all available certifications on [The Things Certification site](https://www.thethingsnetwork.org/achievements/certificates/).
+
+A lot of academic research around LoRaWAN is being conducted nowadays. [Read some LoRaWAN-related academic papers and publications](https://www.thethingsnetwork.org/docs/lorawan/academic/).
+
 ## Useful Links
 
 - Learn more about LoRaWAN and our global, crowdsourced LoRaWAN network at [The Things Network Learn](https://thethingsnetwork.org/docs)
diff --git a/doc/content/getting-started/ttn/_index.md b/doc/content/getting-started/ttn/_index.md
@@ -6,7 +6,7 @@ distributions: "Community"
 
 {{< figure src="logo_TTN.svg" class="float plain" width="150px" >}}
 
-The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
+[The Things Network](https://www.thethingsnetwork.org/) is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
 
 The Things Network runs {{% tts %}} Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
 
diff --git a/doc/content/reference/adr/_index.md b/doc/content/reference/adr/_index.md
@@ -17,8 +17,7 @@ The ADR mechanism controls the following transmission parameters of an end devic
 - Bandwidth
 - Transmission power
 
-See [The Things Network Learn](https://www.thethingsnetwork.org/docs/lorawan/adaptive-data-rate/) for a general description of ADR.
-
+See [The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/adaptive-data-rate/) for a general description of ADR. See the [Spreading Factors](https://www.thethingsnetwork.org/docs/lorawan/spreading-factors/) section to learn how spreading factor influence data rate, range and battery life.
 
 ## The Things Stack ADR Algorithm
 
diff --git a/doc/content/reference/data-formats/_index.md b/doc/content/reference/data-formats/_index.md
@@ -8,6 +8,8 @@ The streaming data integrations provide multiple formats for the delivery of app
 
 <!--more-->
 
+{{< note >}} Read about LoRaWAN message types in [The Things Network documentation](https://www.thethingsnetwork.org/docs/lorawan/message-types/). {{</ note >}}
+
 ## JSON
 
 The JSON message format is described in the sections below.
diff --git a/doc/content/reference/frequency-plans/_index.md b/doc/content/reference/frequency-plans/_index.md
@@ -9,6 +9,8 @@ Deployments may also have custom frequency plans configured.
 
 <!--more-->
 
+Read more about [Frequency Plans](https://www.thethingsnetwork.org/docs/lorawan/frequency-plans/) and see a list of [Frequency Plans by Country](https://www.thethingsnetwork.org/docs/lorawan/frequencies-by-country/).
+
 <!-- terms come from /data/frequency-plans. -->
 
 {{< frequency-plans >}}
diff --git a/doc/content/reference/spec-regional-parameters/index.md b/doc/content/reference/spec-regional-parameters/index.md
@@ -28,6 +28,6 @@ The LoRaWAN specification versions are available from the [LoRa Alliance resourc
 - LoRaWAN Regional Parameters 1.1 Rev A
 - LoRaWAN Regional Parameters 1.1 Rev B
 
-The LoRaWAN Regional Parameters specification versions are available from the [LoRa Alliance resource hub](https://lora-alliance.org/resource-hub/).
+The LoRaWAN Regional Parameters specification versions are available from the [LoRa Alliance resource hub](https://lora-alliance.org/resource-hub/). More information is also available in [The Things Network LoRaWAN documentation](https://www.thethingsnetwork.org/docs/lorawan/regional-parameters/).
 
 In addition, {{% tts %}} supports Class A, B, C, and multicast group devices. See the [Class B]({{< ref "devices/class-b" >}}), [Class C]({{< ref "devices/class-c" >}}), and [Multicast]({{< ref "devices/multicast" >}}) references for special instructions when using these device classes.
