taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

syntax & grammar review

Browse Source
This commit is contained in:
Ginger Collison 2021-05-13 16:56:58 -05:00 committed by GitHub
parent 30514de274
commit 0b1886871c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
jetstream/administration/naming.md
View File

@ -9,11 +9,11 @@ friendly to the file system.
We recommend the following guideline for stream, consumer, and account names: We recommend the following guideline for stream, consumer, and account names:
* Alphanumeric values are recommended. * Alphanumeric values are recommended.
* Spaces, tabs, period \(`.`\), greater than \(`>`\) or asterix \(`*`\) are prohibited. * Spaces, tabs, period \(`.`\), greater than \(`>`\) or asterisk \(`*`\) are prohibited.
* Limit names to 255 characters or less. * Limit names to 255 characters or less.
* Do not use reserved file names like NUL, LPT1, etc. * Do not use reserved file names like NUL, LPT1, etc.
* Be aware that some file systems are case insentitive so do not * Be aware that some file systems are case insentitive so do not
use stream or account names that would collide in a file system. use stream or account names that would collide in a file system.
For example, `Foo` and `foo` would collide on a Windows or Mac OSx System. For example, `Foo` and `foo` would collide on a Windows or Mac OSx System.
We plan to address these limitations in a future release. We plan to address these limitations in a future release.