From f5d31373cbcff53ae2308732955ca37fc93f32be Mon Sep 17 00:00:00 2001 From: Jesse Peterson Date: Tue, 7 Jan 2025 12:12:05 -0800 Subject: [PATCH] Fix syntax --- docs/operations-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/operations-guide.md b/docs/operations-guide.md index dbc8b71..04e4159 100644 --- a/docs/operations-guide.md +++ b/docs/operations-guide.md @@ -574,10 +574,10 @@ In "keypair generation" mode (that is, without specifying the `-token` switch) i In "decrypt and decode tokens" mode (that is, by specifying the path to the downloaded tokens file with the `-token` switch) it will attempt to use the certificate and key on disk (specified by `-cert` and `-key` switches, respectively, with an optional password for an encrypted private key specified with `-password`) to decrypt the tokens and display them. They can then be stored in `depserver` by using the "raw" token API (documented above). > [!NOTE] -> `deptokens` is **not required** to use NanoDEP: `depserver` contains this functionality built-in using the tools/scripts (or via the API) directly. See above documentation.** +> `deptokens` is **not required** to use NanoDEP: `depserver` contains this functionality built-in using the tools/scripts (or via the API) directly. See above documentation. > [!WARNING] -> `deptokens` is discouraged for use with NanoDEP's `depserver`. The private key and certificate for the PKI exchange is not preserved when only uploading OAuth tokens. Some modern DEP functionality will not be possible. See the note above regarding the Tokens API.** +> `deptokens` is discouraged for use with NanoDEP's `depserver`. The private key and certificate for the PKI exchange is not preserved when only uploading OAuth tokens. Some modern DEP functionality will not be possible. See the note above regarding the Tokens API. ### Switches