Delete doc/content/integrations/other-integrations/lora-cloud directory

doc/content/integrations/cloud-integrations/azure-iot-central/device-twin.md

@@ -87,7 +87,7 @@ An example of this property as unmodeled data would look as follows:
 
 > `frm-payload` is the service name for the service which derives the end device location from the decoded payload.
 
-- `serviceData` - Object mapping between the service (name) and the service data reported by that service. Used by integrations such as [LoRa Cloud]({{< ref "/integrations/other-integrations/lora-cloud" >}}).
+- `serviceData` - Object mapping between the service (name) and the service data reported by that service. Used by third-party integrations.
 - `decodedPayload` - Decoded payload of the uplink messages, which is generated using the [Payload Formatters]({{< ref "/integrations/payload-formatters" >}}).
 
 An example of this property as unmodeled data would look as follows:

doc/content/integrations/cloud-integrations/ttnmapper/_index.md

@@ -21,8 +21,6 @@ Your end device can be sending its GPS coordinates in an uplink message as part
 - If your end device is sending data in Cayenne LPP format, choose [Cayenne LPP payload formatter](({{< ref "/integrations/payload-formatters/cayenne" >}})) in your device's settings on {{% tts %}}.
 - Otherwise, create a custom [JavaScript payload formatter]({{< ref "/integrations/payload-formatters/javascript" >}}). This formatter will have to contain fields `latitude`, `longitude` and `altitude`. If possible, `hdop`, `accuracy` or `sats` fields should also be contained.
 
-<!--- Some devices, for example [LoRa Edge LR1110](https://www.semtech.com/products/wireless-rf/lora-edge/), obtain their location from [LoRa Cloud](https://www.loracloud.com/) platform using {{% tts %}} [LoRa Cloud integration]({{< ref "/integrations/other-integrations/lora-cloud" >}}). As a result, device location solution is contained in the `location` field of the location solved message. In this case, there is no need to set up a payload formatter. --->
-
 The next step is to instantiate the **TTN Mapper** [Webhook template]({{< ref "/integrations/webhooks/webhook-templates" >}}).
 
 <!--- {{< note >}} Both uplink and location solved message types are enabled by default in TTN Mapper webhook template. {{</ note >}} --->