feat(iot): reviews 12/11

scaleway · Nov 13, 2024 · b64b51a · b64b51a
1 parent 5a12c00
commit b64b51a
Show file tree

Hide file tree

Showing 8 changed files with 12 additions and 12 deletions.
diff --git a/managed-services/iot-hub/how-to/enable-auto-provisioning.mdx b/managed-services/iot-hub/how-to/enable-auto-provisioning.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to enable device auto-provisioning
 tags: iot iot-hub auto-provisioning
 dates:
-  validation: 2024-04-30
+  validation: 2024-11-13
   posted: 2019-09-01
 categories:
   - managed-services

diff --git a/managed-services/iot-hub/reference-content/certificate.mdx b/managed-services/iot-hub/reference-content/certificate.mdx
@@ -1,12 +1,12 @@
 ---
 meta:
-  title: Updating your Endpoint's Certificate Authority 
+  title: Updating your Endpoint's Certificate Authority
   description: This page provides important information about the Scaleway IoT Hub Certificate Authority.
 content:
   h1: Certificate Authority update
   paragraph: This page provides important information about the Scaleway IoT Hub Certificate Authority.
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2023-04-27
 categories:
   - managed-services
@@ -39,7 +39,7 @@ On **30 January 2024**, the migration endpoint will be deactivated. You will onl
 
 Taking this timeline into account and depending on what your device allows, two options are available to you.
 
-## Your device can use a CA bundle 
+## Your device can use a CA bundle
 
 The first option is to use a CA bundle. In this case, the transition will be smoother because no further action will be required from you once you are done configuring it.
 

diff --git a/managed-services/iot-hub/reference-content/devices.mdx b/managed-services/iot-hub/reference-content/devices.mdx
@@ -6,7 +6,7 @@ content:
   h1: Devices
   paragraph: This page provides detailed information about Scaleway IoT Hub Devices.
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2021-08-31
 categories:
   - managed-services
@@ -50,7 +50,7 @@ When you **allow** insecure connections, all three options are available for the
 
 ## Authentication
 
-Device authentication ensures that only authorized Devices can connect to a Hub. A Device can authenticate itself to a Hub in 2 ways:  
+Device authentication ensures that only authorized Devices can connect to a Hub. A Device can authenticate itself to a Hub in 2 ways:
 
 - with a **certificate**, the certificate can be either signed by the Hub certificate authority or associated with the Device.
 - with the **MQTT username**, matched to a **Device ID** (device is configured to allow insecure connections).

diff --git a/managed-services/iot-hub/reference-content/hubs.mdx b/managed-services/iot-hub/reference-content/hubs.mdx
@@ -10,7 +10,7 @@ excerpt: |
 totalTime: PT5M
 tags: iot iot-hub certificate-authority auto-provisioning metrics events
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2021-08-31
 categories:
   - managed-services

diff --git a/managed-services/iot-hub/reference-content/networks.mdx b/managed-services/iot-hub/reference-content/networks.mdx
@@ -10,7 +10,7 @@ excerpt: |
 totalTime: PT5M
 tags: iot iot-hub network mqtt websocket tls
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2021-08-31
 categories:
   - managed-services

diff --git a/managed-services/iot-hub/reference-content/overview.mdx b/managed-services/iot-hub/reference-content/overview.mdx
@@ -10,7 +10,7 @@ excerpt: |
 totalTime: PT5M
 tags: iot iot-hub networks routes
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2021-08-31
 categories:
   - managed-services

diff --git a/managed-services/iot-hub/reference-content/routes.mdx b/managed-services/iot-hub/reference-content/routes.mdx
@@ -10,7 +10,7 @@ excerpt: |
 totalTime: PT5M
 tags: iot iot-hub route amazon-s3 database postgres postgresql mysql rest api inference
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2021-08-31
 categories:
   - managed-services
@@ -69,7 +69,7 @@ Depending on the strategy the message payload will be written:
 - **Per topic**: s3://`my-bucket`/`my/prefix`/`my/topic`
 - **Per message**: s3://`my-bucket`/`my/prefix`/`my/topic`/`timestamp`
 
-Timestamp example: 
+Timestamp example:
 
 ```
 2006-01-02T15:04:05.999999999Z

diff --git a/...ces/transactional-email/reference-content/protecting-your-domain-reputation.mdx b/...ces/transactional-email/reference-content/protecting-your-domain-reputation.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This section provides information about how we protect your domain's reputation with progressive emailing
 tags: transactional-email domain-reputation email-deliverability
 dates:
-  validation: 2024-05-06
+  validation: 2024-11-13
   posted: 2023-04-27
 categories:
   - managed-services