Apply suggestions from code review

Co-authored-by: Michael Zalimeni <michael.zalimeni@hashicorp.com>
Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>

.changelog/21700.txt

@@ -1,4 +1,4 @@
 ```release-note:enhancement
-  use raft-wal as a default raft log store.
+raft: use raft-wal as the default raft log store.
 ```
 

website/content/docs/agent/wal-logstore/enable.mdx

@@ -5,7 +5,7 @@ description: >-
   Learn how to safely configure and test the experimental WAL backend in your Consul deployment.
 ---
 
-# Enable the experimental WAL LogStore backend
+# Enable the WAL LogStore backend
 
 WAL LogStore is now enabled by default
 

website/content/docs/agent/wal-logstore/index.mdx

@@ -2,13 +2,13 @@
 layout: docs
 page_title: WAL LogStore Backend Overview
 description: >-
-  The experimental WAL (write-ahead log) LogStore backend shipped in Consul 1.15 is intended to replace the BoltDB backend, improving performance and log storage issues.
+  The write-ahead log (WAL) LogStore is the default backend for Consul. Learn about the WAL backend and how it is different from the BoltDB backend.
 ---
 
-# WAL LogStore backend overview
+# Write-ahead Log (WAL) LogStore backend overview
 
 This topic provides an overview of the WAL (write-ahead log) LogStore backend.
-The WAL backend is now the default Consul LogStore when a boltdb database is not already in place. Refer to
+The WAL backend is now the default Consul LogStore when a BoltDB database is not already in place. Refer to
 [Requirements](/consul/docs/agent/wal-logstore/enable#requirements) for
 supported environments and known issues.
 

website/content/docs/agent/wal-logstore/monitoring.mdx

@@ -7,7 +7,7 @@ description: >-
 
 # Monitor Raft metrics and logs for WAL
 
-This topic describes how to monitor Raft metrics and logs if you are testing the WAL backend. We strongly recommend monitoring the Consul cluster, especially the target server, for evidence that the WAL backend is not functioning correctly.
+This topic describes how to monitor Raft metrics and logs for the WAL backend. We strongly recommend monitoring the Consul cluster, especially the target server, for evidence that the WAL backend is not functioning correctly.
 
 ## Monitor for checksum failures