From f4d43cdfdd739e324d229fc193cb2d75bafc8c6e Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Tue, 16 Feb 2021 13:15:34 -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 1945894..8c1b774 100644 --- a/developing-with-nats/tutorials/jwt.md +++ b/developing-with-nats/tutorials/jwt.md @@ -574,7 +574,7 @@ A deeper understanding of accounts will help you to best setup NATS JWT based se Our official suggestion is to scope accounts by application/service offered. This is very fine grain and will require some configuration. This is why some users gravitate to accounts per team. One account for all Applications of a team. - It is possible to start out with less granular accounts and as applications grow in importance or scale become more fine grain. + It is possible to start out with less granular accounts and as applications grow in importance or scale become more fine grained. * Compared to file based config, Imports and Exports change slightly. To control who gets to import an export, activation tokens are introduced. These are JWTs that an importer can embed.