diff --git a/nats-streaming-concepts/monitoring/endpoints.md b/nats-streaming-concepts/monitoring/endpoints.md
index 9ff9684..31f06d4 100644
--- a/nats-streaming-concepts/monitoring/endpoints.md
+++ b/nats-streaming-concepts/monitoring/endpoints.md
@@ -98,7 +98,8 @@ You can control these via URL arguments \(limit and offset\). For example: [http
   "clients": [
     {
       "id": "benchmark-sub-0",
-      "hb_inbox": "_INBOX.jAHSY3hcL5EGFQGYmfayQK"
+      "hb_inbox": "_INBOX.jAHSY3hcL5EGFQGYmfayQK",
+      "subs_count": 1
     }
   ]
 }
@@ -119,6 +120,7 @@ You can also report detailed subscription information on a per client basis usin
     {
       "id": "benchmark-sub-0",
       "hb_inbox": "_INBOX.jAHSY3hcL5EGFQGYmfayQK",
+      "subs_count": 1,
       "subscriptions": {
         "foo": [
           {
@@ -146,6 +148,7 @@ You can select a specific client based on its client ID with `client=<id>`, and
 {
   "id": "me",
   "hb_inbox": "_INBOX.HG0uDuNtAPxJQ1lVjIC2sr",
+  "subs_count": 1,
   "subscriptions": {
     "foo": [
       {
@@ -222,6 +225,7 @@ You can also get the list of subscriptions with `subs=1`. For example: [http://l
       "bytes": 0,
       "first_seq": 0,
       "last_seq": 0,
+      "subs_count": 1,
       "subscriptions": [
         {
           "client_id": "me",
@@ -249,7 +253,8 @@ You can select a specific channel based on its name with `channel=name`. For exa
   "msgs": 649234,
   "bytes": 97368590,
   "first_seq": 1,
-  "last_seq": 649234
+  "last_seq": 649234,
+  "subs_count": 1
 }
 ```
 
@@ -262,6 +267,7 @@ And again, you can get detailed subscriptions with `subs=1`. For example: [http:
   "bytes": 105698990,
   "first_seq": 1,
   "last_seq": 704770,
+  "subs_count": 10,
   "subscriptions": [
     {
       "client_id": "me",
@@ -301,6 +307,7 @@ For durables that are currently running, the `is_offline` field is set to `false
   "bytes": 0,
   "first_seq": 0,
   "last_seq": 0,
+  "subs_count": 1,
   "subscriptions": [
     {
       "client_id": "me",
@@ -328,6 +335,7 @@ When that same durable goes offline, `is_offline` is be set to `true`. Although
   "bytes": 0,
   "first_seq": 0,
   "last_seq": 0,
+  "subs_count": 1,
   "subscriptions": [
     {
       "client_id": "me",
diff --git a/nats-streaming-server/configuring/cfgfile.md b/nats-streaming-server/configuring/cfgfile.md
index 746ba28..3648f35 100644
--- a/nats-streaming-server/configuring/cfgfile.md
+++ b/nats-streaming-server/configuring/cfgfile.md
@@ -197,6 +197,9 @@ For a given channel, the possible parameters are:
 | raft\_commit\_timeout | Specifies the time without an Apply\(\) operation before sending an heartbeat to ensure timely commit. Due to random staggering, may be delayed as much as 2x this value | Duration | `raft_commit_timeout: "100ms"` | `100ms` | v0.11.2 |
 | proceed\_on\_restore\_failure | Allow a non leader node to proceed with restore failures, do not use unless you understand the risks! | `true` or `false` | `proceed_on_restore_failure: true` | `false` | v0.17.0 |
 | allow_add_remove_node| Enable the ability to send NATS requests to the leader to add/remove cluster nodes | `true` or `false` | `allow_add_remove_node: true` | `false` | v0.19.0 |
+| bolt_free_list_sync | Causes the RAFT log to synchronize the free list on write operations. Reduces performance at runtime, but makes the recovery faster | `true` or `false` | `bolt_free_list_sync: true` | `false` | v0.21.0 |
+| bolt_free_list_map | Sets the backend freelist type to use a map instead of the default array type. Improves performance for large RAFT logs, with fragmented free list | `true` or `false` | `bolt_free_list_map: true` | `false` | v0.21.0 |
+| nodes_connections | Enable creation of dedicated NATS connections to communicate with other nodes | `true` or `false` | `nodes_connections: true` | `false` | v0.21.0 |
 
 ## SQL Options Configuration