doc: move blocking Operation to its own file

src/main/docs/guide/httpServer/serverConfiguration/threadPools.adoc

@@ -29,19 +29,3 @@ NOTE: The default value for the number of threads is the value of the system pro
 See the following table for configuring event loops:
 
 include::{includedir}configurationProperties/io.micronaut.http.netty.channel.DefaultEventLoopGroupConfiguration.adoc[]
-
-==== Blocking Operations
-
-When dealing with blocking operations, Micronaut shifts the blocking operations to an unbound, caching I/O thread pool by default. You can configure the I/O thread pool using the api:scheduling.executor.ExecutorConfiguration[] named `io`. For example:
-
-.Configuring the Server I/O Thread Pool
-[source,yaml]
-----
-micronaut:
-  executors:
-    io:
-      type: fixed
-      nThreads: 75
-----
-
-The above configuration creates a fixed thread pool with 75 threads.

src/main/docs/guide/httpServer/serverConfiguration/threadPools/blockingOperations.adoc

@@ -0,0 +1,13 @@
+When dealing with blocking operations, Micronaut shifts the blocking operations to an unbound, caching I/O thread pool by default. You can configure the I/O thread pool using the api:scheduling.executor.ExecutorConfiguration[] named `io`. For example:
+
+.Configuring the Server I/O Thread Pool
+[source,yaml]
+----
+micronaut:
+  executors:
+    io:
+      type: fixed
+      nThreads: 75
+----
+
+The above configuration creates a fixed thread pool with 75 threads.

src/main/docs/guide/toc.yml

@@ -118,7 +118,9 @@ httpServer:
   serverEvents: Server Events
   serverConfiguration:
     title: Configuring the HTTP Server
-    threadPools: Configuring Server Thread Pools
+    threadPools:
+      title: Configuring Server Thread Pools
+      blockingOperations: Blocking Operations
     nettyPipeline: Configuring the Netty Pipeline
     cors: Configuring CORS
     https: Securing the Server with HTTPS