diff --git a/docs/app/references/troubleshooting.mdx b/docs/app/references/troubleshooting.mdx
index be8482dc6f..373a6e00d1 100644
--- a/docs/app/references/troubleshooting.mdx
+++ b/docs/app/references/troubleshooting.mdx
@@ -434,7 +434,7 @@ For the current list, see
 [packages/launcher](https://github.com/cypress-io/cypress/blob/develop/packages/launcher/lib/darwin/index.ts)
 files.
 
-**Note:** `chrome-for-testing` and `chromium` typically require the downloaded application file to be manually moved to the `/Applications` folder.
+**Note:** `chrome-for-testing` and `chromium` typically require the downloaded application file to be manually moved to the `/Applications` folder to be auto-detected.
 
 #### Linux
 
@@ -461,14 +461,13 @@ These binary names should work for most Linux distributions. If your
 distribution packages browsers under a different binary name, you can add a
 symlink using the expected binary name so that Cypress can detect it.
 
-For example, if your distribution packages Google Chrome as `chrome`, you could
-add a symlink to `google-chrome` like this:
+For example, to create a symlink for the `chrome-for-testing` browser:
 
 ```shell
-sudo ln `which chrome` /usr/local/bin/google-chrome
+sudo ln -s /path/to/binary/chrome /usr/local/bin/chrome
 ```
 
-**Note:** `chrome-for-testing` and `chromium` typically require the binary to be manually added to the `PATH` to be auto-detected.
+**Note:** `chrome-for-testing` and `chromium` typically require the binary to be manually added to the `PATH` or a symlink created to be auto-detected.
 
 #### Windows
 
@@ -497,9 +496,13 @@ To make a browser installed at a different path be auto-detected, create a
 symlink using `mklink` in the location that Cypress expects to find your
 browser.
 
-[Read more about creating symbolic links on Windows](https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/)
+For example, to create a symlink for the `chrome-for-testing` browser:
 
-**Note:** `chrome-for-testing` and `chromium` typically require the downloaded folder to either be moved and renamed to the location mentioned above or a symlink created as described above.
+```shell
+mklink /d "C:\Program Files\Google\Chrome for Testing" "C:\path\to\chrome\executable\folder"
+```
+
+**Note:** `chrome-for-testing` and `chromium` typically require the downloaded folder to either be moved and renamed to the location mentioned above or a symlink created as described above to be auto-detected.
 
 Occasionally Cypress will have issues detecting the type of browser in Windows
 environments. To manually detect the browser type, append the browser type to