Update raft api docs (#10893)

* Update raft api docs

* Update website/content/api-docs/system/storage/raft.mdx

Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com>

* Update website/content/api-docs/system/storage/raft.mdx

Co-authored-by: Brian Kassouf <briankassouf@users.noreply.github.com>

* Update website/content/api-docs/system/storage/raft.mdx

Co-authored-by: Brian Kassouf <briankassouf@users.noreply.github.com>

Co-authored-by: Nick Cabatoff <ncabatoff@hashicorp.com>
Co-authored-by: Brian Kassouf <briankassouf@users.noreply.github.com>

website/content/api-docs/system/storage/raft.mdx

@@ -38,6 +38,19 @@ leader node.
 
 - `leader_client_key` `(string: "")` - Client key used to communicate with
   Raft's leader node.
+- `leader_tls_servername` `(string: "")` - TLS servername to use when connecting with HTTPS.  Should match one of the names in the DNS SANs of the remote server certificate. 
+- `auto_join` `(string: "")` - Defines any cloud auto-join metadata. If
+ supplied, Vault will attempt to automatically discover peers in addition to what
+ can be provided via 'leader_api_addr'.
+
+- `auto_join_scheme` `(string: "https")` - URI scheme to be used for `auto_join`.
+
+- `auto_join_port` `(int: 8200)` - Port to be used for `auto_join`.
+
+- `non_voter` `(bool: false) (enterprise)` - If set, will make the server not
+ participate in the Raft quorum, and have it only receive the data replication
+ stream. This can be used to add read scalability to a cluster in cases where a
+ high volume of reads to servers are needed. The default is false.
 
 Additionally, the following options are allowed in Vault open-source, but
 relevant functionality is only supported in Vault Enterprise: