fixup! Lead Resource Type documentation

content/en/docs/configuration/resource-aggregate.md

@@ -77,7 +77,7 @@ plgd hub uses NATS messaging system as a event bus.
 | `clients.eventBus.nats.jetstream`| bool | `If true, events will be published to jetstream.` | `false` |
 | `clients.eventBus.nats.leadResourceType.enabled` | bool | `If true, publish events to NATS with lead resource type subject token included.` | `false` |
 | `clients.eventBus.nats.leadResourceType.regexFilter` | []string | `List of regex expressions used to find resouce type that will be used as the lead resource type subject for resource-level events. The expressions are iterated in order and the first matched resource type of the resource associated with the event is used in the NATS subject.` | `[]` |
-| `clients.eventBus.nats.leadResourceType.filter` | string | `Can contain values "first", "last" or be kept empty (""). If "first" is used, then the first resource type of the resource associated with the event will be used as the lead resource type in the NATS subject. If "last" is used, then the last resource type is used in the NATS subject. If both "regexFilter" and "filter" properties are set then "regexFilter" takes precedence and "filter" is only examined if no resource type is matched by "regexFilter".` | `""` |
+`clients.eventBus.nats.leadResourceType.filter` | string | `Can contain values "first", "last" or be kept empty (""). If "first" is used, the first resource type of the resource associated with the event will be used as the lead resource type in the NATS subject. If "last" is used, the last resource type is used in the NATS subject. If both "regexFilter" and "filter" properties are set, "regexFilter" takes precedence and "filter" is only examined if no resource type is matched by "regexFilter". If neither are set, the NATS subject will not have a lead resource type, but it will just have the "leadrt" token if the feature is enabled.` | `""` |
 | `clients.eventBus.nats.leadResourceType.useUUID` | bool | `If true then do not use the selected resource type as a token directly, but encode it into a UUID string.` | `false` |
 
 ### Event Store

content/en/docs/features/control-plane/nats.md

@@ -150,7 +150,7 @@ Each event is encoded in protobuf [event envelope](https://github.com/plgd-dev/h
 
 ### Consumer subscriptions options
 
-For the consumers of events you can subscribe to:
+For the consumers of events, you can subscribe to:
 
 - `plgd.owners.>` retrieves all events of the hub.
 - `plgd.owners.{ownerId}.>` retrieves all events of the owner with the `ownerId`.