fix not building

docs/components/firmware/app-nrf91-origin/index.md

@@ -24,21 +24,21 @@ or by domain names. There can be a port number specified; without one it will de
 for MQTT and 8883 for MQTTs. A username and password can be added, optionally. No topic must be
 added to the host entry. The format is
 
-    mqtt://[username:password@]host[:port]
-    mqtts://[username:password@]host[:port]
+    `mqtt://[username:password@]host[:port]`
+    `mqtts://[username:password@]host[:port]`
 
 If username or password contain special characters, they must be URL-encoded. 
 
 
 ### MQTT topics
 The device will only publish on topics that conform to this syntax:
 
-    LOB/<DevEUI>/up/<message-type>
-    LOB/<DevEUI>/req/<message-type>
+    `LOB/<DevEUI>/up/<message-type>`
+    `LOB/<DevEUI>/req/<message-type>`
 
 and will only subscribe to topics that conform to this syntax:
 
-    LOB/<DevEUI>/down/<message-type>
+    `LOB/<DevEUI>/down/<message-type>`
 
 where `<DevEUI>` is the device's EUI in urn form, e.g. `urn:dev:mac:70b3d5e05001c6f3`, and 
 `<message-type>` is a string that describes the message type. 
@@ -59,13 +59,13 @@ its own thing using Let's Encrypt and not covered here.
 ### Self-signed Certificates
 Devices can create a self-signed certificate. This is done over the Shell, using the command
 
-    cert self-signed <subject>
+    `cert self-signed <subject>`
 
 The CN is automatically set using the DevEUI in urn form, e.g. `urn:dev:mac:70b3d5e05001c6f3`.
 The DevEUI urn will also be used as Subject Alternative Name (SAN) in the certificate.
-Any fields added as <subject> will be appended to the subject (not the SAN), so you can use something like
+Any fields added as `<subject>` will be appended to the subject (not the SAN), so you can use something like
 
-    cert self-signed C=DE,O=Lobaro,L=Hamburg
+    `cert self-signed C=DE,O=Lobaro,L=Hamburg`
 
 Subject must be comma separated (without blanks) and not be surrounded by quotes (see example).
 When the cert creation is successful, the certificate will be stored in the device's flash memory and 
@@ -77,7 +77,7 @@ generated during boot, if it is missing).
 ### Certificate Signing Requests
 Devices can create a Certificate Signing Request (CSR) to be signed by a CA. This is done over the Shell, using the command
 
-    cert csr <subject>
+    `cert csr <subject>`
 
 It works the same as `self-signed`, but the certificate is not created, only the CSR. The CSR will be printed to the console.
 It must be signed by the provisioning computer that runs the shell (or by hand), using an intermediate CA that is in 
@@ -86,7 +86,7 @@ turn signed by our Device Root CA.
 ### Writing Certificates from CSR
 After the CSR has been signed externally, the certificate can be written to the device using the command
 
-    cert own
+    `cert own`
 
 It is a multi-input command, where you input the certificate in PEM format, one line at a time ('\n' terminated).
 You need to include `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` lines in the input. You must also 
@@ -100,7 +100,7 @@ the both, the device's certificate chain and the trusted CA certificates togethe
 The device can store multiple trusted server CA certificates or server certificates directly. Those are entered 
 using the shell command
 
-    cert ca
+    `cert ca`
 
 The handling is the same as with `cert own`, only that you do not provide a chain, but a list of trusted CA 
 certificates. Size is limited by a shared 4 kiB space with the device's certificate chain (in DER format).