Fix links, formatting and spelling

README.md

@@ -77,8 +77,9 @@ also to define a [`_config.yaml`][config-yaml].
 If you want to test your own setup use the
 [Statement List Generator and Tester][asset-links-generator].
 
-As simple check if the linking works fine check [this link][test-deeplink], if
-that opens in chrome the example app without an intent chooser then this works.
+As simple check if the linking works fine check [this link][test-deeplink] **on
+your Android phone**, if that opens in Chrome the Example App without an Intent
+Chooser then this works correctly.
 
 ### iOS and MacOS
 
@@ -157,7 +158,7 @@ Autologin is not supported yet, since I am not aware of any API for that.
 [App Links]: https://developer.android.com/training/app-links/index.html
 [Kotlin]: https://kotlinlang.org
 [Coroutines]: https://kotlinlang.org/docs/coroutines-guide.html
-[activity-lifecycle]: https://developer.android.com/guide/components/activities/activity-lifecycle
+[Activity Lifecycle]: https://developer.android.com/guide/components/activities/activity-lifecycle
 [Android Jetpack]: https://developer.android.com/jetpack
 [lifecycle-api]: https://developer.android.com/reference/androidx/lifecycle/Lifecycle
 [LifecycleOwner]: https://developer.android.com/reference/androidx/lifecycle/LifecycleOwner

autologin_android/README.md

@@ -12,7 +12,7 @@ This package is [endorsed][endorsed_link], which means you can simply use
 when you do, so you do not need to add it to your pubspec.yaml.
 
 However, if you import this package to use any of its APIs directly, you should
-add it to your pubspec.yaml as usual.
+add it to your `pubspec.yaml` as usual.
 
 # Installation
 
@@ -56,8 +56,9 @@ also to define a [`_config.yaml`][config-yaml].
 If you want to test your own setup use the
 [Statement List Generator and Tester][asset-links-generator].
 
-As simple check if the linking works fine check [this link][test-deeplink], if
-that opens in chrome the example app without an intent chooser then this works.
+As simple check if the linking works fine check [this link][test-deeplink] **on
+your Android phone**, if that opens in Chrome the Example App without an Intent
+Chooser then this works correctly.
 
 
 [endorsed_link]: https://flutter.dev/docs/development/packages-and-plugins/developing-packages#endorsed-federated-plugin
@@ -66,6 +67,7 @@ that opens in chrome the example app without an intent chooser then this works.
 [App Links]: https://developer.android.com/training/app-links/index.html
 [Kotlin]: https://kotlinlang.org
 [Coroutines]: https://kotlinlang.org/docs/coroutines-guide.html
+[Activity Lifecycle]: https://developer.android.com/guide/components/activities/activity-lifecycle
 [Android Jetpack]: https://developer.android.com/jetpack
 [lifecycle-api]: https://developer.android.com/reference/androidx/lifecycle/Lifecycle
 [LifecycleOwner]: https://developer.android.com/reference/androidx/lifecycle/LifecycleOwner

autologin_darwin/README.md

@@ -8,7 +8,7 @@ This package is [endorsed][endorsed_link], which means you can simply use
 when you do, so you do not need to add it to your pubspec.yaml.
 
 However, if you import this package to use any of its APIs directly, you should
-add it to your pubspec.yaml as usual.
+add it to your `pubspec.yaml` as usual.
 
 # Installation
 

autologin_linux/README.md

@@ -1,6 +1,6 @@
 # autologin_linux
 
-The Linux implementation of [`autologin`](https://pub.dev/packages/autologin].
+The Linux implementation of [`autologin`](https://pub.dev/packages/autologin).
 
 ## Usage
 
@@ -9,6 +9,6 @@ This package is [endorsed][endorsed_link], which means you can simply use
 when you do, so you do not need to add it to your pubspec.yaml.
 
 However, if you import this package to use any of its APIs directly, you should
-add it to your pubspec.yaml as usual.
+add it to your `pubspec.yaml` as usual.
 
 [endorsed_link]: https://flutter.dev/docs/development/packages-and-plugins/developing-packages#endorsed-federated-plugin

autologin_web/README.md

@@ -9,6 +9,6 @@ This package is [endorsed][endorsed_link], which means you can simply use
 when you do, so you do not need to add it to your pubspec.yaml.
 
 However, if you import this package to use any of its APIs directly, you should
-add it to your pubspec.yaml as usual.
+add it to your `pubspec.yaml` as usual.
 
 [endorsed_link]: https://flutter.dev/docs/development/packages-and-plugins/developing-packages#endorsed-federated-plugin