Merge pull request nats-io#631 from jw4/jw4/minor-fix

Fix link to valid subject tokens

nats-concepts/jetstream/key-value-store/readme.md

@@ -15,14 +15,15 @@ You can use KV buckets to perform the typical operations you would expect from a
 * keys: get a copy of all the keys (with a value or operation associated to it)
 
 You can set limits for your buckets, such as:
+
 * the maximum size of the bucket
 * the maximum size for any single value
 * a TTL: how long the store will keep values for
 
 Finally, you can even do things that typically can not be done with a Key/Value Store:
 
 * watch: watch for changes happening for a key, which is similar to subscribing (in the publish/subscribe sense) to the key: the watcher receives updates due to put or delete operations on the key pushed to it in real-time as they happen
-* watch all: watch for all the changes happening on all the keys in the bucket 
+* watch all: watch for all the changes happening on all the keys in the bucket
 * history: retrieve a history of the values (and delete operations) associated with each key over time (by default the history of buckets is set to 1, meaning that only the latest value/operation is stored)
 
-The key must be in the same format as a NATS subject, i.e. it can be a dot separated list of tokens (which means that you can then use wildcards to match hierarchies of keys when watching a bucket), and can only contain [valid characters](../../../nats-concepts/subjects#characters-allowed-for-subject-names). The value can be any byte array
+The key must be in the same format as a NATS subject, i.e. it can be a dot separated list of tokens (which means that you can then use wildcards to match hierarchies of keys when watching a bucket), and can only contain [valid characters](../../../nats-concepts/subjects.md#characters-allowed-for-subject-names). The value can be any byte array

using-nats/developing-with-nats/js/kv.md

@@ -2,7 +2,7 @@
 
 As the Key Value Store is built on top of the JetStream persistence layer you obtain a KeyValueManager object from your JetStream [context](context.md).
 
-The key must be in the same format as a NATS subject, i.e. it can be a dot separated list of tokens (which means that you can then use wildcards to match hierarchies of keys when watching a bucket), and can only contain [valid characters](../../../nats-concepts/subjects#characters-allowed-for-subject-names). The value can be any byte array.
+The key must be in the same format as a NATS subject, i.e. it can be a dot separated list of tokens (which means that you can then use wildcards to match hierarchies of keys when watching a bucket), and can only contain [valid characters](../../../nats-concepts/subjects.md#characters-allowed-for-subject-names). The value can be any byte array.
 
 ### Creating, and deleting KV buckets