fix fmt

Signed-off-by: ChrsMark <chrismarkou92@gmail.com>

Author: ChrsMark

internal/pkg/otel/templates/README.md.tmpl

@@ -19,6 +19,12 @@ To validate OTel configuration run `otel validate` subcommand:
 ./elastic-agent otel validate --config otel.yml
 ```
 
+Use the components command to get the list of components included in the binary:
+
+```bash
+./elastic-agent otel components
+```
+
 [feature gates](https://github.com/open-telemetry/opentelemetry-collector/blob/main/featuregate/README.md#controlling-gates) are supported using `--feature-gates` flag.
 
 ## Components
@@ -78,9 +84,9 @@ This section provides a summary of components included in the Elastic Distributi
 
 ## Persistence in OpenTelemetry Collector
 
-By default, the OpenTelemetry Collector is stateless, which means it doesn't store offsets on disk while reading files. As a result, if you restart the collector, it won't retain the last read offset, potentially leading to data duplication or loss. However, we have configured persistence in the settings provided with the Elastic Agent package. 
+By default, the OpenTelemetry Collector is stateless, which means it doesn't store offsets on disk while reading files. As a result, if you restart the collector, it won't retain the last read offset, potentially leading to data duplication or loss. However, we have configured persistence in the settings provided with the Elastic Agent package.
 
-To enable persistence for the `filelogreceiver`, we add the `file_storage` extension and activate it for `filelog`. 
+To enable persistence for the `filelogreceiver`, we add the `file_storage` extension and activate it for `filelog`.
 Execute `export STATE_PATH=/path/to/store/otel/offsets` and use the following configuration to enable persistence:
 
 ```yaml
@@ -106,10 +112,10 @@ service:
       exporters: [...]
 ```
 
-> [!WARNING]  
+> [!WARNING]
 Removing the storage key from the filelog section will disable persistence, which will lead to data duplication or loss when the collector restarts.
 
-> [!IMPORTANT]  
+> [!IMPORTANT]
 If you remove the `create_directory: true` option, you'll need to manually create a directory to store the data. You can ignore this option if the directory already exists.
 
 ### Persistence in standalone Docker mode