From 1152cfbda5cf68e250a43a924714c3b13f09a457 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9ment?=
 <48858570+clementlize@users.noreply.github.com>
Date: Tue, 29 Oct 2024 19:02:03 +0100
Subject: [PATCH] =?UTF-8?q?doc:=20replaced=20'<URL=20to=20your=20PWA>'=20b?=
 =?UTF-8?q?y=20'<Host=20URL=20of=20your=20PWA>'=20in=20andr=E2=80=A6=20(#4?=
 =?UTF-8?q?833)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

fixes #4832
<!-- Link to relevant issue (for ex: "fixes #1234") which will
automatically close the issue once the PR is merged -->

## PR Type
<!-- Please uncomment one ore more that apply to this PR -->

<!-- - Bugfix -->
<!-- - Feature -->
<!-- - Code style update (formatting) -->
<!-- - Refactoring (no functional changes, no api changes) -->
<!-- - Build or CI related changes -->
- Documentation content changes
<!-- - Sample app changes -->
<!-- - Other... Please describe: -->


## Describe the current behavior?
<!-- Please describe the current behavior that is being modified or link
to a relevant issue. -->

> To properly deploy this file, upload it to your server at
`https://<URL to your PWA>/.well-known/assetlinks.json`.

## Describe the new behavior?

> To properly deploy this file, upload it to your server at
`https://<Host URL of your PWA>/.well-known/assetlinks.json`.

## PR Checklist

- [ ] Test: run `npm run test` and ensure that all tests pass
- [ ] Target main branch (or an appropriate release branch if
appropriate for a bug fix)
- [ ] Ensure that your contribution follows [standard accessibility
guidelines](https://docs.microsoft.com/en-us/microsoft-edge/accessibility/design).
Use tools like https://webhint.io/ to validate your changes.


## Additional Information

Co-authored-by: Justin Willis <jgw9617@gmail.com>
---
 docs/builder/android.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/builder/android.md b/docs/builder/android.md
index 55b99bbaf..31870f397 100644
--- a/docs/builder/android.md
+++ b/docs/builder/android.md
@@ -83,10 +83,11 @@ There are a few steps to take before your PWA is ready to be published. All the
 #### 1. Deploy the assetlinks.json file
 Your zip file contains assetlinks.json. This is a digital asset links file that proves ownership of your PWA. 
 
-To properly deploy this file, upload it to your server at `https://<URL to your PWA>/.well-known/assetlinks.json`. 
+To properly deploy this file, upload it to your server at `<Host URL of your PWA>/.well-known/assetlinks.json`.
 
-?> **Note** Digital asset links are required for your PWA on Android. If you’re seeing a browser address bar in your app on Android, or if your app is crashing on launch, it means your assetlinks.json file is missing, inaccessible, or incorrect. See our asset links helper to fix this.
+?> **Note** To find out the Host URL of your PWA, please refer to the values you provided at the [Configuration options](/builder/android?id=configuration-options) step. Example: if the URL of your PWA is `https://foo.example.co/my/app`, upload the file at `https://foo.example.com/.well-known/assetlinks.json`.
 
+!> Digital asset links are required for your PWA on Android. If you’re seeing a browser address bar in your app on Android, or if your app is crashing on launch, it means your assetlinks.json file is missing, inaccessible, or incorrect. See our [asset links helper](/builder/asset-links-faq) to fix this.
 #### 2. Upload your app to the Google Play Store
 
 Next, you'll upload your app package to the Google Play Console: