Update README.md (#35004)

sdk/monitor/azure-monitor-opentelemetry/README.md

@@ -64,7 +64,8 @@ You can use `configure_azure_monitor` to set up instrumentation for your app to
 | `instrumentation_options` | A nested dictionary that determines which instrumentations to enable or disable. Instrumentations are referred to by their [Library Names](#officially-supported-instrumentations). For example, `{"azure_sdk": {"enabled": False}, "flask": {"enabled": False}, "django": {"enabled": True}}` will disable Azure Core Tracing and the Flask instrumentation but leave Django and the other default instrumentations enabled. The `OTEL_PYTHON_DISABLED_INSTRUMENTATIONS` environment variable explained below can also be used to disable instrumentations. | `N/A` |
 | `span_processors` | A list of [span processors][ot_span_processor] that will perform processing on each of your spans before they are exported. Useful for filtering/modifying telemetry. | `N/A` |
 
-You can configure further with [OpenTelemetry environment variables][ot_env_vars] such as:
+You can configure further with [OpenTelemetry environment variables][ot_env_vars].
+
 | Environment Variable | Description |
 |-------------|----------------------|
 | [OTEL_SERVICE_NAME][ot_spec_service_name], [OTEL_RESOURCE_ATTRIBUTES][ot_spec_resource_attributes] | Specifies the OpenTelemetry [Resource][ot_spec_resource] associated with your application. |