diff --git a/docs/configure_rum_android_sdk.md b/docs/configure_rum_android_sdk.md
index d7e6373d7c..5fbeb5ae65 100644
--- a/docs/configure_rum_android_sdk.md
+++ b/docs/configure_rum_android_sdk.md
@@ -292,7 +292,7 @@ For instance, to set each fragment as a distinct view, use the following configu
    
 For `ActivityViewTrackingStrategy`, `FragmentViewTrackingStrategy`, or `MixedViewTrackingStrategy`, you can filter which `Fragment` or `Activity` is tracked as a RUM View by providing a `ComponentPredicate` implementation in the constructor.
    
-**Note**: By default, the library does not track any views. If you decide not to provide a view tracking strategy, you must manually send the views by calling the `startView` and `stopView` methods yourself.
+**Note**: By default, the library is using `ActivityViewTrackingStrategy`. If you decide not to provide a view tracking strategy, you must manually send the views by calling the `startView` and `stopView` methods yourself.
 
 
 ### Automatically track network requests
diff --git a/docs/mobile_data_collected.md b/docs/mobile_data_collected.md
index 3f08052aa7..2d9b6932e3 100644
--- a/docs/mobile_data_collected.md
+++ b/docs/mobile_data_collected.md
@@ -124,7 +124,6 @@ RUM action, error, resource, and long task events contain information about the
 | Metric                              | Type        | Description                                                                                          |
 |----------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `view.time_spent`                             | number (ns) | Time spent on this view.                                    |
-| `view.loading_time`                             | number (ns) | Loading time for this view.                                   |
 | `view.long_task.count`        | number      | Count of all long tasks collected for this view.                                |
 | `view.error.count`            | number      | Count of all errors collected for this view.                                    |
 | `view.resource.count`         | number      | Count of all resources collected for this view.                                 |
diff --git a/docs/rum_getting_started.md b/docs/rum_getting_started.md
index ca541a5fa8..1ccd78bb28 100644
--- a/docs/rum_getting_started.md
+++ b/docs/rum_getting_started.md
@@ -285,7 +285,9 @@ public class SampleApplication extends Application {
 {{< /tabs >}}
 {{< /site-region >}}
 
-The credentials for initialization require your application's variant name and uses the value of `BuildConfig.FLAVOR` or an empty string if you don't have variants. This enables the correct ProGuard `mapping.txt` file to automatically upload at build time so you can view de-obfuscated RUM error stack traces. For more information, see the [guide to uploading Android source mapping files][8].
+The initialization credentials require your application's variant name and uses the value of `BuildConfig.FLAVOR`. With the variant, RUM can match the errors reported from your application with the mapping files uploaded by the Gradle plugin. If you do not have variants, the credentials use an empty string. 
+
+The Gradle plugin automatically uploads the appropriate ProGuard `mapping.txt` file at build time so you can view deobfuscated RUM error stack traces. For more information, see the [Track Android Errors][8].
 
 ### Initialize the RUM Monitor and Interceptor
 
@@ -300,8 +302,8 @@ GlobalRum.registerIfAbsent(monitor)
 {{% /tab %}}
 {{% tab "Java" %}}
 ```java
-    final RumMonitor monitor = new RumMonitor.Builder().build();
-    GlobalRum.registerIfAbsent(monitor);
+final RumMonitor monitor = new RumMonitor.Builder().build();
+GlobalRum.registerIfAbsent(monitor);
 ```
 {{% /tab %}}
 {{< /tabs >}}
@@ -311,16 +313,16 @@ To track your OkHttp requests as resources, add the provided [Interceptor][9]:
 {{< tabs >}}
 {{% tab "Kotlin" %}}
 ```kotlin
-    val okHttpClient =  OkHttpClient.Builder()
-        .addInterceptor(DatadogInterceptor())
-        .build()
+val okHttpClient =  OkHttpClient.Builder()
+    .addInterceptor(DatadogInterceptor())
+    .build()
 ```
 {{% /tab %}}
 {{% tab "Java" %}}
 ```java
-    final OkHttpClient okHttpClient =  new OkHttpClient.Builder()
-        .addInterceptor(new DatadogInterceptor())
-        .build();
+final OkHttpClient okHttpClient =  new OkHttpClient.Builder()
+    .addInterceptor(new DatadogInterceptor())
+    .build();
 ```
 {{% /tab %}}
 {{< /tabs >}}
@@ -337,17 +339,16 @@ You can track events such as crashes and network requests when your application
 
 Add the following snippet during initialization in your Datadog configuration:
 
- {{< tabs >}}
+{{< tabs >}}
 {{% tab "Kotlin" %}}
-   ```kotlin
-        .trackBackgroundRumEvents(true)
-   ```
+```kotlin
+.trackBackgroundRumEvents(true)
+```
 {{% /tab %}}
- {{% tab "Java" %}}
- ```java
- .trackBackgroundRumEvents(true)
-
- ```
+{{% tab "Java" %}}
+```java
+.trackBackgroundRumEvents(true)
+```
 {{% /tab %}}
 {{< /tabs >}}
 <div class="alert alert-info"><p>Tracking background events may lead to additional sessions, which can impact billing. For questions, <a href="https://docs.datadoghq.com/help/">contact Datadog support.</a></p>
@@ -371,4 +372,4 @@ Add the following snippet during initialization in your Datadog configuration:
 [11]: https://docs.datadoghq.com/real_user_monitoring/android/advanced_configuration/#automatically-track-network-requests
 [12]: https://github.com/DataDog/dd-sdk-android-gradle-plugin
 [13]: https://docs.datadoghq.com/real_user_monitoring/android/web_view_tracking/
-[14]: https://docs.datadoghq.com/getting_started/tagging/using_tags/#rum--session-replay
\ No newline at end of file
+[14]: https://docs.datadoghq.com/getting_started/tagging/using_tags/#rum--session-replay