diff --git a/docs/signed-apk-android.md b/docs/signed-apk-android.md
index 61768f318763c6..308b2a340c7851 100644
--- a/docs/signed-apk-android.md
+++ b/docs/signed-apk-android.md
@@ -141,4 +141,4 @@ def enableProguardInReleaseBuilds = true
 
 ### Migrating old Android React Native apps to use App Signing by Google Play
 
-If you are migrating from previous version of React Native chances are your app does not use App Signing by Google Play feature. We recommend you enable that in order to take adventage from things like automatic app splitting. In order to migrate from the old way of signing you need to start by [generating new upload key](#generating-a-signing-key) and then replacing release signing config in `android/app/build.gradle` to use the upload key instead of the release one (see section about [adding signing config to gradle](#adding-signing-config-to-your-app-s-gradle-config)). Once that's done you should follow the [instructions from Google Play Help website](https://support.google.com/googleplay/android-developer/answer/7384423) in order to send your original release key to Google Play.
+If you are migrating from previous version of React Native chances are your app does not use App Signing by Google Play feature. We recommend you enable that in order to take advantage from things like automatic app splitting. In order to migrate from the old way of signing you need to start by [generating new upload key](#generating-a-signing-key) and then replacing release signing config in `android/app/build.gradle` to use the upload key instead of the release one (see section about [adding signing config to gradle](#adding-signing-config-to-your-app-s-gradle-config)). Once that's done you should follow the [instructions from Google Play Help website](https://support.google.com/googleplay/android-developer/answer/7384423) in order to send your original release key to Google Play.