diff --git a/docs/reference/edot-android/automatic-instrumentation.md b/docs/reference/edot-android/automatic-instrumentation.md
index d7793a24d..cbf98d6bd 100644
--- a/docs/reference/edot-android/automatic-instrumentation.md
+++ b/docs/reference/edot-android/automatic-instrumentation.md
@@ -154,3 +154,15 @@ dependencies {
 ```
 
 1. Will only install the instrumentation for the `release` build type of the app, avoiding to increase the compilation time for other types, such as `debug`, for example.
+## Understanding auto-instrumentation scope
+
+Auto-instrumentation automatically captures telemetry for the frameworks and libraries listed on this page. However, it cannot instrument:
+
+- Custom or proprietary frameworks and libraries
+- Closed-source components without instrumentation support
+- Application-specific business logic
+
+If your application uses technologies not covered by auto-instrumentation, you have two options:
+
+1. **Native OpenTelemetry support** — Some frameworks and libraries include built-in OpenTelemetry instrumentation provided by the vendor.
+2. **Manual instrumentation** — Use the [OpenTelemetry API](manual-instrumentation.md) to add custom spans, metrics, and logs for unsupported components.
\ No newline at end of file
diff --git a/docs/reference/edot-android/configuration.md b/docs/reference/edot-android/configuration.md
index 67b1887c7..da5754722 100644
--- a/docs/reference/edot-android/configuration.md
+++ b/docs/reference/edot-android/configuration.md
@@ -73,6 +73,14 @@ class MyApp : android.app.Application {
 To provide these values from outside of your code, using an environment variable or a properties file for example, refer to [Provide config values outside of your code](configuration.md#provide-config-values-from-outside-of-your-code).
 :::
 
+### TLS connections
+
+EDOT Android supports TLS connections to OTLP endpoints and OpAMP (central configuration) endpoints when the server uses a TLS certificate signed by a trusted Certificate Authority (CA).
+
+:::{warning}
+Self-signed certificates are **not supported**. If your endpoint uses a self-signed certificate, EDOT Android will not be able to establish a secure connection. Ensure your server uses a certificate issued by a publicly trusted CA or an internal CA that is trusted by the device.
+:::
+
 ### Intercept export request headers
 
 You can provide an interceptor for the signals' export request headers, where you can read or modify them if needed.