docs(perf): Grammar/wording edits from feedback

Also combined the introductory paragraphs into one

docs/advanced/performance.mdx

@@ -1,8 +1,6 @@
 # Performance tuning
 
-While Continuwuity's default config parameters are generally optimised, additional modifications can be made to better utilise your server resources. This is especially helpful for homeservers with many users and/or are joined in many large federated rooms, and will increasingly be the case as the Matrix network expands.
-
-This page aims to outline various performance tweaks for Continuwuity and their effects. As always, your mileage may vary according to your setup's specifics. If you have further discussions or recommendations, please share them in the community rooms.
+This page aims to outline various performance tweaks for Continuwuity and their effects. These adjustments are especially helpful for homeservers that are in many large federated rooms or have many users, and it will become increasingly necessary as the Matrix network expands. As always, your mileage may vary according to your setup's specifics. If you have further discussions or recommendations, please share them in the community rooms.
 
 ## DNS tuning (recommended)
 
@@ -10,9 +8,9 @@ Please see the dedicated [DNS tuning guide](./dns.mdx).
 
 ## Cache capacities
 
-If you have unused memory to spare, consider increasing the `cache_capacity_modifier` value to a larger number, as to allow more data to be stored in hot memory. This *significantly* speed up many intensive operations such as state resolutions, and also results in decreased CPU usage and disk I/O. Start with a baseline of `cache_capacity_modifier = 2.0` and tune up until you find a satisfactory RAM usage.
+If you have unused memory to spare, consider increasing the `cache_capacity_modifier` value to a larger number to allow more data to be stored in hot memory. This *significantly* speed up many intensive operations (such as state resolutions) and decreases CPU usage and disk I/O. Start with a baseline of `cache_capacity_modifier = 2.0` and tune up until you are satisfied with RAM usage.
 
-On the other hand, if your system doesn't have a lot of RAM, consider decreasing the cache capacity modifier to something smaller than `1.0` to avoid low-memory issues (at the cost of higher load on disk/CPU). The recommendation also works if your system has very little RAM compared to the number of CPU cores, as cache capacities tend to scale according to number of cores.
+On the other hand, if your system doesn't have a lot of RAM, consider decreasing the cache capacity modifier to something smaller than `1.0` to avoid low-memory issues (at the cost of higher load on disk/CPU). This recommendation also works if your system has very little RAM compared to the number of CPU cores, as cache capacities tend to scale according to number of cores.
 
 ## Disabling some features
 
@@ -68,11 +66,11 @@ rocksdb_compression_algo = "lz4"
 rocksdb_wal_compression = "none"
 ```
 
-The tweak can especially be helpful if you have an older or less performant CPU (e.g. a Raspberry Pi) and disk space to spare.
+This tweak can especially be helpful if you have an older or less performant CPU (e.g. a Raspberry Pi) and disk space to spare.
 
 ### Increasing bottommost layer compression (`zstd` only)
 
-The bottommost layer of the database usually contains old and read-only data, and hence is a suitable place for further compression. In Continuwuity, this is possible by setting `rocksdb_bottommost_compression = true` and tuning `rocksdb_bottommost_compression_level` to a more compact level than the default one used in `rocksdb_compression_level`. The tweak comes at a cost of some increased CPU usage, but would prevent your database from growing too large especially in the long run.
+The bottommost layer of the database usually contains old and read-only data, so it is a suitable place for further compression. In Continuwuity, this is possible by setting `rocksdb_bottommost_compression = true` and tuning `rocksdb_bottommost_compression_level` to a more compact level than the default one used in `rocksdb_compression_level`. This tweak comes at a cost of increased CPU usage, but may prevent your database from growing too large in the long run.
 
 For those using `zstd` compression, the compression level ranges from 1 to 22. An example like this could apply:
 
@@ -86,7 +84,7 @@ rocksdb_bottommost_compression_level = 9 # level 9 on zstd
 
 For `lz4` users, the default level (`-1`) is already the most compact. You can only further decrease it to favor compression speed over ratio.
 
-Consult these documentations for more information on compression tuning and levels:
+Consult these documents for more information on compression tuning and levels:
 
 - [Rocksdb compression documentation][rocksdb-compression]
 - [Rocksdb default compression levels][rocksdb-compression-defaults]
@@ -102,7 +100,7 @@ Consult these documentations for more information on compression tuning and leve
 
 ### Using UNIX sockets
 
-If your homeserver and reverse proxy lives on the same machine, you may wish to expose Continuwuity on a UNIX socket instead of a port. This reduces TCP overhead between the two programs.
+If your homeserver and reverse proxy live on the same machine, you may wish to expose Continuwuity on a UNIX socket instead of a port. This reduces TCP overhead between the two programs.
 
 <details>
 
@@ -131,7 +129,7 @@ https://matrix.example.com {
 
 ### Tuning your trusted servers
 
-Trusted servers are queried sequentially starting from the first entry of `trusted_servers`. If you have multiple notaries configured, put the faster ones first:
+Trusted servers are queried sequentially in the order they are listed. If you have multiple notaries configured, put the faster ones first:
 
 ```toml
 trusted_servers = ["fastest.example.com","faster.example.com","matrix.org"]
@@ -139,7 +137,7 @@ trusted_servers = ["fastest.example.com","faster.example.com","matrix.org"]
 
 Avoid using `matrix.org` as your primary notary, as it tends to be quite slow. If you need suggestions for trusted servers, ask in the Continuwuity main room.
 
-Furthermore, consider increasing `trusted_server_batch_size` to something higher than the default `1024`, as this could help with faster joins for huge rooms. Start with doubling to `2048` until you find a suitable value.
+Some users have also reported that increasing `trusted_server_batch_size` has helped with faster joins for huge rooms. Start with doubling the default to `2048` until you find a suitable value.
 
 ### Serving .well-knowns manually