Merge pull request #7297 from JimHagan/jhagan_fix_issue_7238

Added line breaks

src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-optimizing.mdx

@@ -1096,9 +1096,15 @@ The different approaches:
   pattern: WARN|ERROR
 ```
 
-        If you have pre-written Fluentd configurations for Fluentbit that do valuable filtering or parsing, you can import them into our New Relic logging config. To do this, use the `config_file` and `parsers` parameters.
+        If you have pre-written Fluentd configurations for Fluentbit that do valuable filtering or parsing, you can import them into our New Relic logging config. To do this, use the `config_file` and `parsers` parameters in any `.yaml` file in your `logging.d` folder.
+
+
         `config_file`: path to an existing Fluent Bit configuration file. Any overlapping source results in duplicate messages in New Relic's log management.
-        `parsers_file`: path to an existing Fluent Bit parsers file. The following parser names are reserved: `rfc3164`, `rfc3164-local` and `rfc5424`.
+
+        `parsers_file`: path to an existing Fluent Bit parsers file. 
+
+
+        The following parser names are reserved: `rfc3164`, `rfc3164-local` and `rfc5424`.
         Learning how to inject attributes (or tags) into your logs in your data pipeline and to perform transformations can help with downstream features dropping using New Relic drop rules. By augmenting your logs with metadata about the source, we can make centralized and easily reversible decisions about what to drop on the backend.  At a minimum, make sure the following attributes are present in your logs in some form:
 
         * Team