fix formatting

Author: cyrille-leclerc

content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md

@@ -46,7 +46,6 @@ This blog post shows how to set up this solution step by step.
   ingest the logs.
 - Finally, we'll show a Kubernetes-specific setup to handle container logs.
 
-
 ![OTLP/JSON Architecture](otlpjson-architecture.png)
 
 ## Configure Java application to output OTLP/JSON logs
@@ -118,91 +117,90 @@ OTLP/JSON format, with a JSON object per line. The log records are nested in the
 
 ```json
 {
-  "resourceLogs":[
+  "resourceLogs": [
     {
-      "resource":{
-        "attributes":[
+      "resource": {
+        "attributes": [
           {
-            "key":"deployment.environment.name",
-            "value":{
-              "stringValue":"staging"
+            "key": "deployment.environment.name",
+            "value": {
+              "stringValue": "staging"
             }
           },
           {
-            "key":"service.instance.id",
-            "value":{
-              "stringValue":"6ad88e10-238c-4fb7-bf97-38df19053366"
+            "key": "service.instance.id",
+            "value": {
+              "stringValue": "6ad88e10-238c-4fb7-bf97-38df19053366"
             }
           },
           {
-            "key":"service.name",
-            "value":{
-              "stringValue":"checkout"
+            "key": "service.name",
+            "value": {
+              "stringValue": "checkout"
             }
           },
           {
-            "key":"service.namespace",
-            "value":{
-              "stringValue":"shop"
+            "key": "service.namespace",
+            "value": {
+              "stringValue": "shop"
             }
           },
           {
-            "key":"service.version",
-            "value":{
-              "stringValue":"1.1"
+            "key": "service.version",
+            "value": {
+              "stringValue": "1.1"
             }
           }
         ]
       },
-      "scopeLogs":[
+      "scopeLogs": [
         {
-          "scope":{
-            "name":"com.mycompany.checkout.CheckoutServiceServer$CheckoutServiceImpl",
-            "attributes":[
-              
-            ]
+          "scope": {
+            "name": "com.mycompany.checkout.CheckoutServiceServer$CheckoutServiceImpl",
+            "attributes": []
           },
-          "logRecords":[
+          "logRecords": [
             {
-              "timeUnixNano":"1730435085776869000",
-              "observedTimeUnixNano":"1730435085776944000",
-              "severityNumber":9,
-              "severityText":"INFO",
-              "body":{
-                "stringValue":"Order order-12035 successfully placed"
+              "timeUnixNano": "1730435085776869000",
+              "observedTimeUnixNano": "1730435085776944000",
+              "severityNumber": 9,
+              "severityText": "INFO",
+              "body": {
+                "stringValue": "Order order-12035 successfully placed"
               },
-              "attributes":[
+              "attributes": [
                 {
-                  "key":"customerId",
-                  "value":{
-                    "stringValue":"customer-49"
+                  "key": "customerId",
+                  "value": {
+                    "stringValue": "customer-49"
                   }
                 },
                 {
-                  "key":"thread.id",
-                  "value":{
-                    "intValue":"44"
+                  "key": "thread.id",
+                  "value": {
+                    "intValue": "44"
                   }
                 },
                 {
-                  "key":"thread.name",
-                  "value":{
-                    "stringValue":"grpc-default-executor-1"
+                  "key": "thread.name",
+                  "value": {
+                    "stringValue": "grpc-default-executor-1"
                   }
                 }
               ],
-              "flags":1,
-              "traceId":"42de1f0dd124e27619a9f3c10bccac1c",
-              "spanId":"270984d03e94bb8b"
+              "flags": 1,
+              "traceId": "42de1f0dd124e27619a9f3c10bccac1c",
+              "spanId": "270984d03e94bb8b"
             }
           ]
         }
       ],
-      "schemaUrl":"https://opentelemetry.io/schemas/1.24.0"
+      "schemaUrl": "https://opentelemetry.io/schemas/1.24.0"
     }
   ]
 }
 ```
+
 </details>
 
 ## Configure the Collector to ingest the OTLP/JSON logs
@@ -313,8 +311,8 @@ After the pipeline works end-to-end, ensure production readiness:
 
 ## Configure an OpenTelemetry Collector in Kubernetes to handle container logs
 
-To support Kubernetes and container specifics, add the built-in 
-[`container`](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/docs/operators/container.md) 
+To support Kubernetes and container specifics, add the built-in
+[`container`](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/docs/operators/container.md)
 parsing step in the pipeline without needing specific mapping configuration.
 
 Replace `<<namespace>>`, `<<pod_name>>`, and `<<container_name>>` with the