Update java/observability.md

Co-authored-by: René Jeglinsky <[email protected]>

java/observability.md

@@ -75,7 +75,7 @@ A `ServiceException` thrown in handler code and indicating a server error (that
 To set up a logging system, a concrete logging framework has to be chosen and, if necessary, corresponding SLF4j adapters.
 In case your application runs on Spring Boot and you use the Spring starter packages, **you most likely don't have to add any explicit dependency**, as the bundle `spring-boot-starter-logging` is part of all Spring Boot starters. It provides `logback` as default logging framework and in addition adapters for the most common logging frameworks (`log4j` and `jul`).
 
-Similarly, no specific log output configuration is required for local development, as per default, log messages are written to the console in human-readable form, which contains timestamp, thread, and logger component information. To customize the log output, for instance to add some application-specific information, you can create corresponding configuration files (such as `logback-spring.xml` for logback) to the classpath and Spring picks it automatically. Consult the documentation of the dedicated logging framework to learn about the configuration file format.
+Similarly, no specific log output configuration is required for local development, as per default, log messages are written to the console in human-readable form, which contains timestamp, thread, and logger component information. To customize the log output, for instance to add some application-specific information, you can create corresponding configuration files (such as `logback-spring.xml` for logback). Add them to the classpath and Spring picks them automatically. Consult the documentation of the dedicated logging framework to learn about the configuration file format.
 
 All logs are written which have a log level greater or equal the configured log level of the corresponding logger object.
 The following log levels are available: