diff --git a/docs/images/templates/coder-session-token.png b/docs/images/templates/coder-session-token.png
index 571c28ccd0568..2e042fd67e454 100644
Binary files a/docs/images/templates/coder-session-token.png and b/docs/images/templates/coder-session-token.png differ
diff --git a/docs/images/user-guides/desktop/coder-desktop-workspaces.png b/docs/images/user-guides/desktop/coder-desktop-workspaces.png
index c621c7e541094..da1b36ea5ed67 100644
Binary files a/docs/images/user-guides/desktop/coder-desktop-workspaces.png and b/docs/images/user-guides/desktop/coder-desktop-workspaces.png differ
diff --git a/docs/user-guides/desktop/desktop-connect-sync.md b/docs/user-guides/desktop/desktop-connect-sync.md
index 1a09c9b7c5f5d..f6a45a598477f 100644
--- a/docs/user-guides/desktop/desktop-connect-sync.md
+++ b/docs/user-guides/desktop/desktop-connect-sync.md
@@ -11,7 +11,7 @@ While active, Coder Connect will list the workspaces you own and will configure

-To copy the `.coder` hostname of a workspace agent, you can click the copy icon beside it.
+To copy the `.coder` hostname of a workspace agent, select the copy icon beside it.
You can also connect to the SSH server in your workspace using any SSH client, such as OpenSSH or PuTTY:
@@ -88,19 +88,17 @@ You can hover your mouse over the status for the list of conflicts:
If you encounter a synchronization conflict, delete the conflicting file that contains changes you don't want to keep.
-## Accessing web apps in a secure browser context
+## Troubleshooting
+
+### Accessing web apps in a secure browser context
Some web applications require a [secure context](https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts) to function correctly.
A browser typically considers an origin secure if the connection is to `localhost`, or over `HTTPS`.
-As Coder Connect uses its own hostnames and does not provide TLS to the browser, Google Chrome and Firefox will not allow any web APIs that require a secure context.
-
-> [!NOTE]
-> Despite the browser showing an insecure connection without `HTTPS`, the underlying tunnel is encrypted with WireGuard in the same fashion as other Coder workspace connections (e.g. `coder port-forward`).
-
-If you require secure context web APIs, you will need to mark the workspace hostnames as secure in your browser settings.
+Because Coder Connect uses its own hostnames and does not provide TLS to the browser, Google Chrome and Firefox will not allow any web APIs that require a secure context.
+Even though the browser displays a warning about an insecure connection without `HTTPS`, the underlying tunnel is encrypted with WireGuard in the same fashion as other Coder workspace connections (e.g. `coder port-forward`).
-We are planning some changes to Coder Desktop that will make accessing secure context web apps easier. Stay tuned for updates.
+If you require secure context web APIs, identify the workspace hostnames as secure in your browser settings.