docs(guides): improve wording across guides

- clarify temporary file behavior to explain safe write use
- rephrase instant-messaging sentences to avoid awkward phrasing
- update key-categories wording for right-click options
- improve key-management wording about prefilled search box
- reword openpgp trust guide to clarify certify methods
- adjust settings table entries for General and Instant Messaging
- tweak interface guide phrasing for counts and row clarity

7 files changed, 18 insertions, 18 deletions

diff --git a/src/content/docs/guides/file-operations.md b/src/content/docs/guides/file-operations.md
index 913d855..8b8febc 100644
--- a/src/content/docs/guides/file-operations.md
+++ b/src/content/docs/guides/file-operations.md
@@ -193,9 +193,9 @@ This is a faster way to switch output modes without opening the main settings.
 
 ![](https://image.cdn.bktus.com/i/2025/04/09/ea2c8b52-2a49-ee18-5897-5cf3d72115a5.webp)
 
-## If Something Goes Wrong Part Way
+## If an Operation Is Interrupted
 
-Since v2.2.2, GpgFrontend writes its result somewhere out of the way first and
+Since v2.2.2, GpgFrontend writes its result to a temporary file first and
 only puts it in place once it is complete.
 
 If an operation fails or is interrupted, you get no output file at all, rather
diff --git a/src/content/docs/guides/instant-messaging.mdx b/src/content/docs/guides/instant-messaging.mdx
index 254c12a..d80055a 100644
--- a/src/content/docs/guides/instant-messaging.mdx
+++ b/src/content/docs/guides/instant-messaging.mdx
@@ -59,8 +59,8 @@ There is no separate button for reading one. If the sender signed it, use
 
 ## Share a Secret Phrase
 
-Out of the box, your messages still look like nothing in particular to most
-people. But anyone who knows GpgFrontend can recognise them for what they are.
+Out of the box, your messages do not stand out to most people. But anyone who
+knows GpgFrontend can recognise them for what they are.
 
 To stop that, you and the person you write to can share a **secret phrase**.
 Once you both have the same one, your messages look like plain random text to
diff --git a/src/content/docs/guides/key-categories.mdx b/src/content/docs/guides/key-categories.mdx
index bf2e6cf..6f4472d 100644
--- a/src/content/docs/guides/key-categories.mdx
+++ b/src/content/docs/guides/key-categories.mdx
@@ -91,8 +91,8 @@ A key can be in as many categories as you like.
 
 ## Rename, Recolour, Reorder
 
-Right-click a category you made for **Rename Category**, **Set Colour**, and
-**Reset Colour**.
+Right-click one of your own categories to find **Rename Category**, **Set
+Colour**, and **Reset Colour**.
 
 To change the order, drag a category up or down the list. The order is
 remembered.
diff --git a/src/content/docs/guides/key-management.mdx b/src/content/docs/guides/key-management.mdx
index 803bede..55337df 100644
--- a/src/content/docs/guides/key-management.mdx
+++ b/src/content/docs/guides/key-management.mdx
@@ -92,8 +92,8 @@ send it anywhere.
 
 ### Key servers
 
-- **Search Keyserver...**: look someone up online. Started from a key you have
-  selected, the search is already filled in for you.
+- **Search Keyserver...**: look someone up online. If you start it with a key
+  selected, the search box is already filled in for you.
 - **Publish Key to Keyserver...**: upload your public key so others can find
   it.
 - **Refresh Selected from Keyserver**: fetch the latest copy of a key, in case
diff --git a/src/content/docs/guides/openpgp-trust-manage.md b/src/content/docs/guides/openpgp-trust-manage.md
index be05281..185cde1 100644
--- a/src/content/docs/guides/openpgp-trust-manage.md
+++ b/src/content/docs/guides/openpgp-trust-manage.md
@@ -109,9 +109,9 @@ a person.
 
 :::
 
-If you do need to sign one, there are two ways in. Open the key's details and
-use the **UID** tab, or right-click the key in the **Manage Keys** window and
-choose **Certify Key...**. The second one is new in v2.2.2.
+If you do need to sign one, there are two ways to do it. Open the key's
+details and use the **UID** tab, or right-click the key in the **Manage Keys**
+window and choose **Certify Key...**. The second way is new in v2.2.2.
 
 You cannot certify your own key, and GpgFrontend greys the action out to say
 so.
diff --git a/src/content/docs/guides/settings.md b/src/content/docs/guides/settings.md
index e4c74e8..9680282 100644
--- a/src/content/docs/guides/settings.md
+++ b/src/content/docs/guides/settings.md
@@ -35,14 +35,14 @@ If you would rather browse, the pages are sorted into four groups:
 
 | Page                  | Group          | What you change there                                                     |
 | --------------------- | -------------- | ------------------------------------------------------------------------- |
-| **General**           | Application    | Language, which engine to use, what the file panel opens at, expiry warnings |
-| **Appearance**        | Application    | Theme, icon size, which buttons appear on the toolbar, fonts               |
+| **General**           | Application    | Language, which engine to use, file panel start folder, expiry warnings   |
+| **Appearance**        | Application    | Theme, icon size, which buttons appear on the toolbar, fonts              |
 | **Network**           | Application    | Proxy settings                                                            |
 | **Key Databases**     | Keys & Engines | Add, edit and remove key databases                                        |
 | **GnuPG**             | Keys & Engines | Point at your own GnuPG, clear the password cache, restart GnuPG          |
 | **rPGP**              | Keys & Engines | How long the rPGP engine remembers a passphrase                           |
 | **Key Servers**       | Keys & Engines | The list of key servers, and which one is the default                     |
-| **Instant Messaging** | Features       | Your shared secret phrase for [instant messaging](/guides/instant-messaging/) |
+| **Instant Messaging** | Features       | Your phrase for [instant messaging](/guides/instant-messaging/)           |
 | **Advanced**          | System         | How the program protects its own key, and how much it writes to the log   |
 
 Some pages only show up when they apply to you. **GnuPG** and **rPGP** appear
diff --git a/src/content/docs/guides/understand-interface.mdx b/src/content/docs/guides/understand-interface.mdx
index e6774c2..a0275a0 100644
--- a/src/content/docs/guides/understand-interface.mdx
+++ b/src/content/docs/guides/understand-interface.mdx
@@ -150,8 +150,8 @@ rather than just pick them. See [Manage Your Keys](/guides/key-management/).
 - **Refresh**: read your keys again from disk.
 - **Sync Public Key**: fetch updates for your keys from the key server.
 - **Check All** and **Uncheck All**: tick or untick every key in the current
-  category. The uncheck button carries a small number showing how many keys
-  are ticked right now.
+  category. The uncheck button shows a small count of how many keys are
+  ticked right now.
 - **Columns**: choose which columns to show, and reset their widths.
 - **New Key Group**: make a group from the keys you have ticked.
 - **Key database**: switch between key databases. The button shows the name of
@@ -186,8 +186,8 @@ aren't obvious at first. Here is what they mean.
   - `Expiring Soon`: still works, but runs out shortly.
   - `Expired`, `Revoked`, `Disabled`: cannot be used.
 
-Rows are tinted to match the Status column, so a problem key stands out
-without reading it.
+Rows are tinted to match the Status column, so a problem key stands out at a
+glance.
 
 Use the **Columns** button to show or hide columns such as **Expire Date** and
 **Status**. Each key list remembers its own choice, so you can keep the Key