Consistent use of tabs for sample code in the reference documentation

src/docs/asciidoc/web/webflux-websocket.adoc

@@ -28,17 +28,16 @@ Creating a WebSocket server is as simple as implementing `WebSocketHandler`:
 [source,java,indent=0]
 [subs="verbatim,quotes"]
 ----
-import org.springframework.web.reactive.socket.WebSocketHandler;
-import org.springframework.web.reactive.socket.WebSocketSession;
+	import org.springframework.web.reactive.socket.WebSocketHandler;
+	import org.springframework.web.reactive.socket.WebSocketSession;
 
-public class MyWebSocketHandler implements WebSocketHandler {
+	public class MyWebSocketHandler implements WebSocketHandler {
 
-	@Override
-	public Mono<Void> handle(WebSocketSession session) {
-		// ...
+		@Override
+		public Mono<Void> handle(WebSocketSession session) {
+			// ...
+		}
 	}
-
-}
 ----
 
 Spring WebFlux provides a `WebSocketHandlerAdapter` that can adapt WebSocket
@@ -49,26 +48,25 @@ adapter is registered as a bean, you can map requests to your handler, for examp
 [source,java,indent=0]
 [subs="verbatim,quotes"]
 ----
-@Configuration
-static class WebConfig {
+	@Configuration
+	static class WebConfig {
 
-	@Bean
-	public HandlerMapping handlerMapping() {
-		Map<String, WebSocketHandler> map = new HashMap<>();
-		map.put("/path", new MyWebSocketHandler());
+		@Bean
+		public HandlerMapping handlerMapping() {
+			Map<String, WebSocketHandler> map = new HashMap<>();
+			map.put("/path", new MyWebSocketHandler());
 
-		SimpleUrlHandlerMapping mapping = new SimpleUrlHandlerMapping();
-		mapping.setUrlMap(map);
-		mapping.setOrder(-1); // before annotated controllers
-		return mapping;
+			SimpleUrlHandlerMapping mapping = new SimpleUrlHandlerMapping();
+			mapping.setUrlMap(map);
+			mapping.setOrder(-1); // before annotated controllers
+			return mapping;
+		}
+
+		@Bean
+		public WebSocketHandlerAdapter handlerAdapter() {
+			return new WebSocketHandlerAdapter();
+		}
 	}
-
-	@Bean
-	public WebSocketHandlerAdapter handlerAdapter() {
-		return new WebSocketHandlerAdapter();
-	}
-
-}
 ----
 
 
@@ -98,22 +96,21 @@ WebSocket options when running on Tomcat:
 [source,java,indent=0]
 [subs="verbatim,quotes"]
 ----
-@Configuration
-static class WebConfig {
+	@Configuration
+	static class WebConfig {
 
-    @Bean
-    public WebSocketHandlerAdapter handlerAdapter() {
-        return new WebSocketHandlerAdapter(webSocketService());
-    }
+		@Bean
+		public WebSocketHandlerAdapter handlerAdapter() {
+			return new WebSocketHandlerAdapter(webSocketService());
+		}
 
-    @Bean
-    public WebSocketService webSocketService() {
-        TomcatRequestUpgradeStrategy strategy = new TomcatRequestUpgradeStrategy();
-        strategy.setMaxSessionIdleTimeout(0L);
-        return new HandshakeWebSocketService(strategy);
-    }
-
-}
+		@Bean
+		public WebSocketService webSocketService() {
+			TomcatRequestUpgradeStrategy strategy = new TomcatRequestUpgradeStrategy();
+			strategy.setMaxSessionIdleTimeout(0L);
+			return new HandshakeWebSocketService(strategy);
+		}
+	}
 ----
 
 Check the upgrade strategy for your server to see what options are available. Currently
@@ -157,9 +154,9 @@ WebSocketClient client = new ReactorNettyWebSocketClient();
 
 URI url = new URI("ws://localhost:8080/path");
 client.execute(url, session ->
-        session.receive()
-                .doOnNext(System.out::println)
-                .then());
+		session.receive()
+				.doOnNext(System.out::println)
+				.then());
 ----
 
 Some clients, e.g. Jetty, implement `Lifecycle` and need to be started in stopped