From 78b1fdd722a77898855c7d17dfbbd555ea6153e9 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Tue, 16 Feb 2021 13:14:29 -0500 Subject: [PATCH] Update developing-with-nats/tutorials/jwt.md Co-authored-by: Colin Sullivan --- developing-with-nats/tutorials/jwt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/tutorials/jwt.md b/developing-with-nats/tutorials/jwt.md index f0a4554..e145ebe 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -582,7 +582,7 @@ JWT feature accounts pretty heavily, thus a few thing need to be clarified. Due to the use of a token the exporting account's JWT does not have to be modified. * Updates of JWT are applied as `nats-server` discover them. * How this is done depends on the resolver. - * `mem-resolver` require `nats-server --signal reload` to re-read all configured account JWT. + * `mem-resolver` require `nats-server --signal reload` to re-read all configured account JWTs. * `url-resolver` and `nats-resolver` listen on a dedicated update subject of the system account and applied if the file is valid. * `nats-resolver` will also also update the corresponding JWT file and compensate in case the update message was not received due to temporary disconnect. * User JWTs do only depend on the issuing Account NKEY only, they do NOT depend on a particular version of an Account JWT.