diff --git a/website/content/docs/concepts/transparent-sessions.mdx b/website/content/docs/concepts/transparent-sessions.mdx
index 43f7549720..87b579230e 100644
--- a/website/content/docs/concepts/transparent-sessions.mdx
+++ b/website/content/docs/concepts/transparent-sessions.mdx
@@ -27,7 +27,6 @@ Refer to the following table for known issues:
| Issue | Description |
| ----- | ----------- |
-| Connection is reset when trying to reconnect | If you use an SSH transparent session and then cancel the connection, you may have trouble reconnecting until Boundary cleans up the session. |
| SSH connection fails with man-in-the-middle warning | On Linux systems, the initial transparent session may be successful, but any subsequent connections prompt a warning that you may be experiencing a man-in-the-middle attack.
For more information, refer to [WARNING! Remote host indentification has changed! It is possible that someone is doing something nasty!](/boundary/docs/api-clients/client-agent#warning-remote-host-indentification-has-changed-it-is-possible-that-someone-is-doing-something-nasty) in the **Common error messages** section.|
| Boundary Client Agent authentication does not persist across restarts | When you reboot, you are required to re-authenticate to the Client Agent before you can use transparent sessions. |
| Windows installer prompts for restart | When you install Boundary, the Windows installer occasionally prompts you to restart your computer, however it is not necessary. |
@@ -36,7 +35,6 @@ Refer to the following table for known issues:
| Windows installer does not support partial installations | The Windows installer fails to start the Client Agent if the Desktop client is not installed at the same time. |
| Alias connection failures inside containers/VMs | Using transparent sessions rely on network access to the local network of the computer the Client Agent is running on. Network enclaves such as those created by Docker containers and VMs cannot reach this network. |
| DNS lookup is broken on MacOS 15.1 and 15.2 | MacOS 15.1 and 15.2 may incorrectly block DNS lookups for the Client Agent. This issue is resolved in MacOS 15.3 and later. |
-| DNS resolution may fail after switching network interfaces | If you switch network interfaces while the Client Agent is running, DNS resolution can fail and you may lose connectivity for some applications. This failure can occur when you switch from an ethernet connection to a wireless network, for example. |
## More information
diff --git a/website/content/docs/configuration/target-aliases/interoperability-matrix.mdx b/website/content/docs/configuration/target-aliases/interoperability-matrix.mdx
index eb4d29dc8c..55ff2dec16 100644
--- a/website/content/docs/configuration/target-aliases/interoperability-matrix.mdx
+++ b/website/content/docs/configuration/target-aliases/interoperability-matrix.mdx
@@ -46,10 +46,10 @@ Any patches or updates will be reflected in the minor number.
Windows version: 2025.2.600.0