From 43f595f80e1a195738e4ecbd50f7778c18c56a85 Mon Sep 17 00:00:00 2001
From: Jupiter <4177229+jupiterhub@users.noreply.github.com>
Date: Mon, 19 Oct 2020 20:39:32 +0900
Subject: [PATCH] Wording changes. Fixed typo 'CorsConfiguraiton'

---
 src/docs/asciidoc/web/webflux-websocket.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docs/asciidoc/web/webflux-websocket.adoc b/src/docs/asciidoc/web/webflux-websocket.adoc
index 033751bed2..0e08d972d5 100644
--- a/src/docs/asciidoc/web/webflux-websocket.adoc
+++ b/src/docs/asciidoc/web/webflux-websocket.adoc
@@ -412,7 +412,7 @@ only Tomcat and Jetty expose such options.
 
 The easiest way to configure CORS and restrict access to a WebSocket endpoint is to
 have your `WebSocketHandler` implement `CorsConfigurationSource` and return a
-`CorsConfiguraiton` with allowed origins, headers, and other details. If you cannot do
+`CorsConfiguration` with allowed origins, headers, and other details. If you cannot do
 that, you can also set the `corsConfigurations` property on the `SimpleUrlHandler` to
 specify CORS settings by URL pattern. If both are specified, they are combined by using the
 `combine` method on `CorsConfiguration`.