fix documentation after review

core/runtime/src/main/java/io/quarkus/runtime/logging/LogConfig.java

@@ -108,7 +108,7 @@ public final class LogConfig {
     /**
      * Socket handlers.
      * <p>
-     * The named socket handlers configured here can be linked on one or more categories.
+     * The named socket handlers configured here can be linked to one or more categories.
      */
     @ConfigItem(name = "handler.socket")
     @ConfigDocSection

core/runtime/src/main/java/io/quarkus/runtime/logging/SocketConfig.java

@@ -58,7 +58,7 @@ public class SocketConfig {
     Optional<String> filter;
 
     /**
-     * Syslog async logging config
+     * Socket async logging config
      */
     AsyncConfig async;
 }

docs/src/main/asciidoc/centralized-log-management.adoc

@@ -240,10 +240,10 @@ Launch your application, you should see your logs arriving inside the Elastic St
 [[logstash_ecs]]
 == GELF alternative: Send logs to Logstash in the ECS (Elastic Common Schema) format
 
-You can also send your logs to Logstash using a tcp input, using the https://www.elastic.co/guide/en/ecs-logging/overview/current/intro.html[ECS] format.
-To achieve this we'll use the `quarkus-logging-json` extention to format the logs in json format and the socket handler to send them to Logstash.
+You can also send your logs to Logstash using a TCP input in the https://www.elastic.co/guide/en/ecs-logging/overview/current/intro.html[ECS] format.
+To achieve this we will use the `quarkus-logging-json` extension to format the logs in JSON format and the socket handler to send them to Logstash.
 
-For this you can use the same docker compose yml file as above but with a different Logstash pipeline configuration.
+For this you can use the same `docker-compose.yml` file as above but with a different Logstash pipeline configuration.
 
 [source]
 ----
@@ -271,7 +271,7 @@ output {
 }
 ----
 
-Then configure your application to log in json format instead of GELF
+Then configure your application to log in JSON format instead of GELF
 ----
 <dependency>
     <groupId>io.quarkus</groupId>

docs/src/main/asciidoc/logging.adoc

@@ -512,7 +512,7 @@ For details about its configuration, see the xref:#quarkus-core_section_quarkus-
 
 This handler will send the logs to a socket.
 It is disabled by default, so you must first enable it.
-When enabled, it sends all log events to a socket, for instance to a logstash server.
+When enabled, it sends all log events to a socket, for instance to a Logstash server.
 
 This will typically be used in conjunction with the `quarkus-logging-json` extension so send logs in ECS format to an Elasticsearch instance.
 An example configuration can be found in the xref:centralized-log-management.adoc[Centralized log management] guide.