diff options
| -rw-r--r-- | docs/configuration/service/https.rst | 2 | ||||
| -rw-r--r-- | docs/configuration/service/snmp.rst | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/docs/configuration/service/https.rst b/docs/configuration/service/https.rst index 4569e867..c44fffd9 100644 --- a/docs/configuration/service/https.rst +++ b/docs/configuration/service/https.rst @@ -78,7 +78,7 @@ Set an API-KEY is the minimal configuration to get a working API Endpoint. set service https api keys id MY-HTTPS-API-ID key MY-HTTPS-API-PLAINTEXT-KEY -To use this full configuration we asume a publice accessable hostname. +To use this full configuration we asume a public accessible hostname. .. code-block:: none diff --git a/docs/configuration/service/snmp.rst b/docs/configuration/service/snmp.rst index 36dc1787..d4b340c1 100644 --- a/docs/configuration/service/snmp.rst +++ b/docs/configuration/service/snmp.rst @@ -129,7 +129,7 @@ sent in clear text between a manager and agent. Each SNMPv3 message contains security parameters which are encoded as an octet string. The meaning of these security parameters depends on the security model being used. -The securityapproach in v3 targets: +The security approach in SNMPv3 targets: * Confidentiality – Encryption of packets to prevent snooping by an unauthorized source. @@ -163,7 +163,7 @@ Example set service snmp v3 view default oid 1 After commit the plaintext passwords will be hashed and stored in your -configuration. The resulting LCI config will look like: +configuration. The resulting CLI config will look like: .. code-block:: none |