Fix incorrect artifact names in docs

Fixes #1523
square · Aug 2, 2019 · dc0d2b5 · pyricau · Aug 2, 2019 · dc0d2b5
1 parent 29ee622
commit dc0d2b5
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/docs/fundamentals.md b/docs/fundamentals.md
@@ -11,7 +11,7 @@ For example, an Android activity instance is no longer needed after its `onDestr
 Most memory leaks are caused by bugs related to the lifecycle of objects. Here are a few common Android mistakes:
 
 * Storing an Activity context as a field in an object that survives activity recreation due to configuration changes.
-* Registering a listener, broadcast receiver or RxJava subscription which references an object with lifecycle, and forgetting to unregister when the lifecycle reaches its end.
+* Registering a listener, broadcast receiver or RxJava subscription which references an object with lifecycle, and forgetting to unregister whe	n the lifecycle reaches its end.
 * Storing a view in a static field, and not clearing that field when the view is detached.
 
 ## Why should I use LeakCanary?
@@ -216,11 +216,11 @@ LeakCanary is released as several libraries:
 * ObjectWatcher
     * Used to watch retained objects and check if they become weakly reachable.
     * Suitable for release builds.
-    * Artifact id: `com.squareup.leakcanary:object-watcher`.
+    * Artifact id: `com.squareup.leakcanary:leakcanary-object-watcher`.
 * ObjectWatcher Android
     * Automatically detects retained destroyed activities and fragments.
     * Suitable for release builds.
-    * Artifact id: `com.squareup.leakcanary:object-watcher-android`.
+    * Artifact id: `com.squareup.leakcanary:leakcanary-object-watcher-android`.
 * LeakCanary
     * Dumps the heap and analyzes it.
     * Currently only suitable for debug builds.

diff --git a/docs/recipes.md b/docs/recipes.md
@@ -61,13 +61,13 @@ Sometimes it's necessary to disable LeakCanary temporarily, for example for a pr
 
 ## Counting retained instances in production
 
-`com.squareup.leakcanary:leakcanary-android` should only be used in debug builds. It depends on `com.squareup.leakcanary:object-watcher-android` which you can use in production to track and count retained instances.
+`com.squareup.leakcanary:leakcanary-android` should only be used in debug builds. It depends on `com.squareup.leakcanary:leakcanary-object-watcher-android` which you can use in production to track and count retained instances.
 
 In your `build.gradle`:
 
 ```gradle
 dependencies {
-  implementation 'com.squareup.leakcanary:object-watcher-android:2.0-beta-2'
+  implementation 'com.squareup.leakcanary:leakcanary-object-watcher-android:2.0-beta-2'
 }
 ```
 

diff --git a/docs/upgrading-to-leakcanary-2.0.md b/docs/upgrading-to-leakcanary-2.0.md
@@ -85,7 +85,7 @@ If you were using `RefWatcher` in non debug code, you now get a compile error be
 
 ```groovy
 dependencies {
-  implementation 'com.squareup.leakcanary:object-watcher-android:2.0-beta-2'
+  implementation 'com.squareup.leakcanary:leakcanary-object-watcher-android:2.0-beta-2'
 }
 ```