Update logging.mdx

Author: joaniekube

vcluster/configure/vcluster-yaml/logging.mdx

@@ -8,21 +8,21 @@ description: Configuration for setting structured logging options for vCluster.
 import InterpolatedCodeBlock from '@site/src/components/InterpolatedCodeBlock'
 import Logging from '../../_partials/config/logging.mdx'
 
-By default, vCluster creates logs in the control plane pod in console format, which is easy to read and preferred for manual log review. However, you can configure the logging in the control plane pod to JSON format. By enabling the JSON format, logs can be sent to external tools to aggregate logs across multiple virtual clusters to help monitor and troubleshoot these virtual clusters. 
+By default, vCluster generates logs in console format. Console format provides human-readable output that is well-suited for manual log review and troubleshooting. Alternatively, you can configure vCluster to output logs in JSON format. JSON format enables integration with external logging systems for centralized log aggregation and automated monitoring across multiple virtual clusters.
 
 ## Log encoding formats
 
 vCluster supports two log encoding formats for the vCluster control plane pod.
 
-- console (_Default_): Human-readable format. Ideal for development and manual log review.
-- JSON: Structured format for log aggregation. Ideal for external monitoring and analysis tools. 
+- [console](#console-format) (_Default_): Human-readable format. Ideal for development and manual log review.
+- [JSON](#json-format): Structured format for log aggregation. Ideal for external monitoring and analysis tools. 
 
 ### Console format
 
-The console format provides human-readable logs with timestamps, log levels, source locations, and contextual information. The console format is best suited for use cases where users will be troubleshooting a single virtual cluster.  Choose this format in environments where human readability is more important than structured log parsing. Example use cases include:
+The console format provides human-readable logs with timestamps, log levels, source locations, and contextual information. This format works well for use cases where users are troubleshooting a single virtual cluster. Choose this format in environments where human readability is more important than structured log parsing. Example use cases include:
 
-* Local development and testing, where developers benefit from quick, readable output
-* Single virtual cluster analysis, where users will manually review logs and debug in a terminal
+- Local development and testing, where developers benefit from quick, readable output
+- Single virtual cluster analysis, where users manually review logs and debug in a terminal
 
 ```text
 2025-06-16 04:43:25	INFO	license	loader/inject.go:52	initializing license...	{"component": "vcluster"}
@@ -32,10 +32,9 @@ The console format provides human-readable logs with timestamps, log levels, sou
 ```
 
 ### JSON format
+The JSON format structures log data for programmatic processing and integration with log management systems. This format is best suited for use cases where external tools monitor and analyze logs for multiple virtual clusters. Log aggregation tools (for example, Elasticsearch or Splunk) can ingest these logs to support automated analysis, alerting, and integration with monitoring platforms (for example, Prometheus and Grafana). Example use cases include:
 
-The JSON format structures log data for programmatic processing and integration with log management systems. The JSON format is best suited for use cases where external tools are used to monitor and analyze logs for multiple virtual clusters. Log aggregation tools (e.g. Elasticsearch or Splunk) can ingest these logs to support automated analysis, alerting, and integration with monitoring platforms (e.g. Prometheus and Grafana).  Examples use cases include:
-
-* Product environments where multiple virtual clusters are being monitored and logs from all of them need to be parsed and processed automatically.
+- Production environments where you monitor multiple virtual clusters and require automatic parsing and processing of logs
 
 ```json
 {"level":"info","ts":1750160027.442782,"logger":"license","caller":"loader/inject.go:52","msg":"initializing license...","component":"vcluster"}
@@ -60,9 +59,7 @@ Additional fields might be displayed based on context and log content.
 
 ## Enable log encoding
 
-Logging is enabled in your `vcluster.yaml` configuration file. 
-
-
+Configure logging in your `vcluster.yaml` configuration file. 
 
 You can enable the JSON format of log encoding.
 
@@ -79,7 +76,7 @@ logging:
 ```
 
 :::note
-When changing between encoding formats, the pod will be restarted and all previous logs will be lost. 
+When changing between encoding formats, the pod restarts and all previous logs are lost. 
 :::
 
 ## Config reference