fix errors

text/0225-configuration.md

@@ -276,7 +276,8 @@ Configuration files *MUST* support environment variable expansion. While this ac
 The syntax for environment variable expansion mirrors the [collector](https://opentelemetry.io/docs/collector/configuration/#configuration-environment-variables).
 
 For example, given an environment where `API_KEY=1234`, the configuration file contents:
-```
+
+```yaml
 scheme_version: 0.1
 sdk:
   tracer_provider:
@@ -288,7 +289,8 @@ sdk:
 ```
 
 Result in the following after substitution:
-```
+
+```yaml
 scheme_version: 0.1
 sdk:
   tracer_provider:
@@ -339,10 +341,6 @@ Configuration files provide an opportunity for misconfiguration. A way to mitiga
 
 The working group looked to the OpenTelemetry Collector and OpenTelemetry Operator for inspiration and guidance.
 
-## Configuration through environment variables supports runtime replacement of variables, would file based configuration require users to hardcode potentially sensitive values?
-
-Hardcoding secrets in files is never a good idea. To address this 
-
 ### Alternative schema languages
 
 In choosing to recommend JSON schema, the working group looked at the following options: