diff --git a/SUMMARY.md b/SUMMARY.md
index 04ea8fe..09b7485 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -102,7 +102,7 @@
     * [Configuration](nats-server/configuration/mqtt/mqtt_config.md)
   * [System Events](nats-server/configuration/sys_accounts/README.md)
     * [System Events & Decentralized JWT Tutorial](nats-server/configuration/sys_accounts/sys_accounts.md)
-  * [Websocket](nats-server/configuration/websocket.md)
+  * [WebSocket](nats-server/configuration/websocket.md)
 * [Managing A NATS Server](nats-server/nats_admin/README.md)
   * [Upgrading a Cluster](nats-server/nats_admin/upgrading_cluster.md)
   * [Slow Consumers](nats-server/nats_admin/slow_consumers.md)
diff --git a/nats-server/configuration/websocket.md b/nats-server/configuration/websocket.md
index 8f133c4..43a1531 100644
--- a/nats-server/configuration/websocket.md
+++ b/nats-server/configuration/websocket.md
@@ -1,11 +1,11 @@
-# Websocket
+# WebSocket
 
 _Supported since NATS Server version 2.2_
 
-Websocket support can be enabled in the server and may be used alongside the traditional TCP socket connections. TLS, compression and Origin Header checking are supported.
+WebSocket support can be enabled in the server and may be used alongside the traditional TCP socket connections. TLS, compression and Origin Header checking are supported.
 
 **Important**
 
-* NATS Supports only Websocket data frames in Binary, not Text format \([https://tools.ietf.org/html/rfc6455\#section-5.6](https://tools.ietf.org/html/rfc6455#section-5.6)\). The server will always send in Binary and your clients MUST send in Binary too.
-* For writers of client libraries: a Websocket frame is not guaranteed to contain a full NATS protocol \(actually will generally not\). Any data from a frame must be going through a parser that can handle partial protocols. See the protocol description [here](../../nats-protocol/nats-protocol/).
+* NATS Supports only WebSocket data frames in Binary, not Text format \([https://tools.ietf.org/html/rfc6455\#section-5.6](https://tools.ietf.org/html/rfc6455#section-5.6)\). The server will always send in Binary and your clients MUST send in Binary too.
+* For writers of client libraries: a WebSocket frame is not guaranteed to contain a full NATS protocol \(actually will generally not\). Any data from a frame must be going through a parser that can handle partial protocols. See the protocol description [here](../../nats-protocol/nats-protocol/).