docs(turn,livekit): Add troubleshooting steps for incorrect IPs

docs/deploying/generic.mdx

@@ -29,19 +29,12 @@ we can't cross-build static binaries - contributions are welcome here.
 
 #### Performance-optimised builds
 
-For x86_64 systems with CPUs from the last ~15 years, use the
-`-haswell-` optimised binaries for best performance. These
-binaries enable hardware-accelerated CRC32 checksumming in
-RocksDB, which significantly improves database performance.
-The haswell instruction set provides an excellent balance of
-compatibility and speed.
+Continuwuity provides `*-maxperf` tagged binaries, which uses the `release-max-perf` build profile with [link-time optimisation (LTO)][lto-rust-docs]. For the x86_64 architecture, these binaries specifically target the Haswell architecture (hence the `-haswell-` name extension), and enables hardware-accelerated CRC32 checksumming in
+RocksDB which significantly improves database performance. If you're using an x86_64 system with CPUs from the last ~15 years, consider using these images for best performance.
 
 If you're using Docker instead, equivalent performance-optimised
 images are available with the `-maxperf` suffix (e.g.
 `forgejo.ellis.link/continuwuation/continuwuity:latest-maxperf`).
-These images use the `release-max-perf` build profile with
-[link-time optimisation (LTO)][lto-rust-docs]
-and, for amd64, target the haswell CPU architecture.
 
 [lto-rust-docs]: https://doc.rust-lang.org/cargo/reference/profiles.html#lto
 
@@ -59,28 +52,7 @@ If you wish to generate a static binary, you can do so using Nix: `nix build git
 
 ### Compiling
 
-Alternatively, you may compile the binary yourself.
-
-#### Using Docker
-
-See the [Building Docker Images](../development/index.mdx#building-docker-images)
-section in the development documentation.
-
-#### Manual
-
-##### Dependencies
-
-- Run `nix develop` to get a devshell with everything you need
-- Or, install the following:
-    - (On linux) `liburing-dev` on the compiling machine, and `liburing` on the target host
-    - (On linux) `pkg-config` on the compiling machine to allow finding `liburing`
-    - A C++ compiler and (on linux) `libclang` for RocksDB
-
-##### Build
-
-You can now build Continuwuity using `cargo build --release`.
-
-Continuwuity supports various optional features that can be enabled during compilation. Please see the Cargo.toml file for a comprehensive list, or ask in our rooms.
+Alternatively, you may compile the binary yourself. See the [Appendix subsection](#compiling-continuwuity) for more details.
 
 ## Adding a Continuwuity user
 
@@ -207,7 +179,7 @@ For more granular controls, you will need to proxy everything under these follow
 
   - `/_matrix/client` - core Client-Server APIs. These should be available on port :443
 
-- `/_continuwuity/` - Continuwuity's integrated account management interface for OAuth-compatible clients
+- `/_continuwuity/` - Continuwuity's integrated account management interface and authentication path for OAuth-compatible clients
 
 You can optionally reverse proxy the following individual routes:
 
@@ -215,7 +187,7 @@ You can optionally reverse proxy the following individual routes:
   Continuwuity to perform delegation (see the `[global.well_known]` config section)
 - `/.well-known/matrix/support` if using Continuwuity to send the homeserver admin
   [contact and support page][well-known-support]
-- `/` and `/_continuwuity/logo.svg` if you would like to see the Continuwuity landing page
+- `/` and `/_continuwuity/resources` if you would like to see the Continuwuity landing page
 
 Refer to the respective software's documentation and online guides on how to do so.
 
@@ -286,10 +258,10 @@ and verify that your federation endpoints are opened and forwarded correctly.
 As a quick health check, you can also use these cURL commands:
 
 ```bash
-curl https://example.com/_conduwuit/server_version
+curl https://example.com/_continuwuity/server_version
 
 # If using port 8448
-curl https://example.com:8448/_conduwuit/server_version
+curl https://example.com:8448/_continuwuity/server_version
 
 # If federation is enabled
 curl https://example.com:8448/_matrix/federation/v1/version
@@ -305,3 +277,28 @@ curl https://example.com/_matrix/client/versions
 - For Audio/Video call functionality see the [**Calls**](../calls.md) page.
 - Consult the [Maintenance](../maintenance.mdx) page for guidance on maintaining your homeserver.
 - If you want to set up an appservice, take a look at the [**Appservice Guide**](../appservices.md).
+
+## Appendix
+
+### Compiling Continuwuity
+
+#### Using Docker
+
+See the [Building Docker Images](../development/index.mdx#building-docker-images)
+section in the development documentation.
+
+#### Manual
+
+##### DEPENDENCIES
+
+- Run `nix develop` to get a devshell with everything you need
+- Or, install the following:
+    - (On linux) `liburing-dev` on the compiling machine, and `liburing` on the target host
+    - (On linux) `pkg-config` on the compiling machine to allow finding `liburing`
+    - A C++ compiler and (on linux) `libclang` for RocksDB
+
+##### BUILD
+
+You can now build Continuwuity using `cargo build --release`.
+
+Continuwuity supports various optional features that can be enabled during compilation. Please see the Cargo.toml file for a comprehensive list, or ask in our rooms.