docs(overview): update overview pages for v2.2.3

- drop Qt5 builds for 2.2.x and explain nightly downloads
- add language list, update notes and smart card label to FAQ
- mention startup window and update check in getting started
- add short notes on new features to the glance page

4 files changed, 112 insertions, 26 deletions

diff --git a/src/content/docs/overview/downloads.mdx b/src/content/docs/overview/downloads.mdx
index 47a380b..837c47f 100644
--- a/src/content/docs/overview/downloads.mdx
+++ b/src/content/docs/overview/downloads.mdx
@@ -24,7 +24,7 @@ almost everyone.
 
 Other options, for special cases only:
 
-- [**Older Version (v2.1.x)**][github-v2-1-x]: only if you specifically need the GnuPG-only build.
+- [**Older Version (v2.1.x)**][github-v2-1-x]: only if you specifically need the GnuPG-only build, or a Qt5 build for an older system such as Windows 7.
 - [**Nightly Builds**][github-nightly]: early test builds for testers and contributors, not for everyday use.
 - [**Mirror Site**][ftp-gpgfrontend]: the same files from another source, with no tracking or sign-in.
 
@@ -55,15 +55,29 @@ Use this table to find the right file for your system.
 | `-linux-<arch>.AppImage`       | Standalone Linux app. Make it executable, then run it.           |
 | `-portable`                    | Marks the portable version of a build.                           |
 | `*.sig`                        | Signature file. Always use it to check the download is genuine.  |
-| `-qt5-`                        | Older system build (e.g., Windows 7, Ubuntu 20.04).              |
 
-<Aside type="note" title="Qt5 builds moved to the Mirror Site">
-  Starting with **v2.2.1**, the Qt5 (`-qt5-`) builds are no longer on the GitHub
-  releases page. They now live only on the [Mirror
-  Site][ftp-gpgfrontend]. These builds are for older systems
-  only. If your system is current, use the standard build instead.
+<Aside type="note" title="Changed in v2.2.3">
+  There are no Qt5 (`-qt5-`) builds of v2.2.x any more. Qt5 builds exist only
+  for the older v2.1.x line. If your system needs one, for example Windows 7,
+  download a [v2.1.x release][github-v2-1-x].
 </Aside>
 
+### About Nightly Builds
+
+[Nightly builds][github-nightly] are made automatically from the newest code.
+They are less tested, so do not use them for anything you cannot afford to
+lose.
+
+- Like stable releases, they come as **installed** or **portable**. There is
+  no portable build for macOS.
+- For macOS there is only a `.dmg` file. Apple has checked it (it is
+  notarized).
+- The downloads are larger than stable ones, because they include extra
+  information for finding bugs. The app runs just as fast.
+- They are not GPG-signed, so there are no `.sig` files. Use the
+  `SHA256SUMS.txt` file instead. See
+  [Checking a Nightly Build](/appendix/code-binary-verify/#checking-a-nightly-build).
+
 ## Package Managers and App Stores
 
 Install GpgFrontend through trusted package managers and official app stores.
diff --git a/src/content/docs/overview/faq.mdx b/src/content/docs/overview/faq.mdx
index e4e47b8..4bccc48 100644
--- a/src/content/docs/overview/faq.mdx
+++ b/src/content/docs/overview/faq.mdx
@@ -42,6 +42,39 @@ yourself; see the [Version Numbering Policy](/appendix/version-policy/).
 
 </details>
 
+<details>
+<summary>How does GpgFrontend tell me about a new version?</summary>
+
+Only if you allow it. The update check is off unless you turn it on, either on
+the last page of the first-run welcome window or in **Settings** >
+**Updates**.
+
+When it is on, GpgFrontend checks quietly in the background when it starts, at
+most once a day. It never pops up a window. If a newer version exists, a small
+badge appears on **Help** > **Check for Updates**. Click it to see what is new
+and to download it.
+
+The check only asks GitHub Releases. See
+[Finding Your Settings](/guides/settings/#the-updates-page).
+
+<Aside type="note" title="Changed in v2.2.3">
+
+The check now runs in the background and shows a badge instead of a window.
+The **Check for Updates** window was redesigned.
+
+</Aside>
+
+</details>
+
+<details>
+<summary>Is there still a Qt5 build?</summary>
+
+Not for v2.2.x. The Qt5 builds were only made for the older v2.1.x line. If
+your system cannot run Qt6, for example Windows 7, you need a v2.1.x release.
+See [System Requirements](/appendix/system-requirement/).
+
+</details>
+
 ## OpenPGP and the Engines
 
 <details>
@@ -348,8 +381,9 @@ interface to protect or unlock files.
 <details>
 <summary>Does GpgFrontend support OpenPGP smart cards or tokens?</summary>
 
-Yes, if your GnuPG supports smart cards. Manage your smart cards directly in the
-SmartCard Controller. Smart card support needs the **GnuPG engine**; the rPGP
+Yes, if your GnuPG supports smart cards. To manage them, click **Advanced** >
+**Open Smart Card Controller**. This opens the **Smart Card Controller**
+window. Smart card support needs the **GnuPG engine**; the rPGP
 engine does not support smart cards or tokens.
 
 </details>
@@ -357,9 +391,21 @@ engine does not support smart cards or tokens.
 <details>
 <summary>Is GpgFrontend available in my language?</summary>
 
-GpgFrontend supports many languages. Open **Settings**, choose **General**, and
-pick your language. Want to help translate? See the [contribution
-guide](/appendix/translate-interface) on GitHub!
+GpgFrontend comes in these languages:
+
+- English
+- Chinese (Simplified)
+- Chinese (Traditional)
+- French
+- German
+- Italian
+- Spanish
+- Russian
+- Polish
+- Turkish
+
+Open **Settings**, choose **General**, and pick your language. Want to help
+translate? See the [translation guide](/appendix/translate-interface)!
 
 </details>
 
@@ -406,6 +452,9 @@ file. See [Profiles](/advanced/profiles/).
 Normal encrypted text is a big block that chat apps often break. **IM Encrypt**
 turns your message into one short line that pastes cleanly into any messenger.
 
+You find it in the **Operations** menu, while a text tab is open. There are no
+toolbar buttons for it.
+
 The other person just presses **Decrypt** as usual. See [Instant
 Messaging](/guides/instant-messaging/).
 
@@ -426,9 +475,9 @@ those keys back in it. See [Key Categories](/guides/key-categories/).
 <details>
 <summary>Why can I no longer generate a DSA key?</summary>
 
-On the rPGP engine, DSA and RSA keys below 2048 bits are no longer offered
-for new keys. The current OpenPGP standard (RFC 9580) says they are no longer
-safe enough.
+On the rPGP engine, DSA keys and RSA keys below 3072 bits are not offered for
+new keys. The current OpenPGP standard (RFC 9580) says new keys of these kinds
+must not be made.
 
 Existing keys of these types still import and still work. The GnuPG engine
 still offers both if you really need one.
@@ -452,8 +501,15 @@ Verify](/appendix/code-binary-verify/).
 
 These are auto-generated test builds with new features and fixes still being
 tested. They are less stable than official releases, may include breaking
-changes, and are not GPG-signed. They are not recommended for production. Always
-check the SHA256 checksum. Please report feedback and issues on GitHub.
+changes, and are not GPG-signed. They are not recommended for production.
+
+Each nightly comes with a `SHA256SUMS.txt` file. Always use it to check your
+download. You can also check that GitHub built the files for this project. See
+[Checking a Nightly Build](/appendix/code-binary-verify/#checking-a-nightly-build).
+
+Nightly downloads are larger than official ones, because they include
+information for finding bugs. The app runs just as fast. Please report
+feedback and issues on GitHub.
 
 For how stable, beta and nightly builds relate, see [Stable, Beta, and
 Nightly](/appendix/version-policy/#stable-beta-and-nightly) in the Version
@@ -505,8 +561,8 @@ decrypt your messages.
 <summary>What data does GpgFrontend collect?</summary>
 
 GpgFrontend does not collect or send any personal or usage data. All encryption
-runs locally. Update checks can be turned off, and there is no tracking or
-analytics built in.
+runs locally. Update checks are off unless you turn them on, and there is no
+tracking or analytics built in.
 
 There is also no AI feature in the app, and nothing you do is ever sent to an
 AI service. See the [AI Policy](/appendix/ai-policy/).
diff --git a/src/content/docs/overview/getting-started.mdx b/src/content/docs/overview/getting-started.mdx
index f98924a..3edb14e 100644
--- a/src/content/docs/overview/getting-started.mdx
+++ b/src/content/docs/overview/getting-started.mdx
@@ -27,8 +27,9 @@ system in the table below to see which engine is best for you:
 | **Linux**        | **GnuPG**           | Pre-installed in most distros. Check with `gpg --version`. |
 | **BSD**          | **GnuPG**           | Must be installed manually via ports/pkg.                  |
 
-> **Note:** If GnuPG is missing (v2.2.0+), GpgFrontend will automatically switch
-> to the built-in **rPGP** engine to keep the basics working.
+> **Note:** GpgFrontend needs GnuPG 2.2.0 or newer. If GnuPG is missing, or
+> older than 2.1.0, GpgFrontend does not use it. It switches to the built-in
+> **rPGP** engine instead, so the basics keep working.
 
 ## Step 2: Install GpgFrontend
 
@@ -83,12 +84,22 @@ Pick your operating system to see the recommended steps. For other methods
 
 ## Step 3: The First Time You Open It
 
-A short welcome window appears the first time GpgFrontend runs, and only that
-time.
+When GpgFrontend starts, a small **Starting GpgFrontend** window may appear. It
+shows a progress bar while your keys and modules load. Wait for it to finish.
+The main window then opens.
 
-The first page has a **Language** setting. Pick yours there and the window
-switches to it straight away, so you do not have to read the rest in English.
-The rest of the welcome offers links to the basics.
+A short **Welcome to GpgFrontend** window appears the first time GpgFrontend
+runs, and only that time.
+
+1. The first page has a **Language:** setting. Pick yours there and the window
+   switches to it straight away, so you do not have to read the rest in
+   English.
+2. The next page offers links to the basics.
+3. The last page, **Ready to use**, has a **Check for updates on startup**
+   checkbox. It is off unless you tick it. If you tick it, GpgFrontend quietly
+   checks for a new version at most once a day. See
+   [Settings](/guides/settings/#the-updates-page). Sandboxed builds, such as
+   Flatpak, do not show this checkbox.
 
 Nothing in it is permanent. You can close it at any point, and everything it
 sets can be changed later in **Settings**.
diff --git a/src/content/docs/overview/glance.mdx b/src/content/docs/overview/glance.mdx
index 076bbab..7add4a5 100644
--- a/src/content/docs/overview/glance.mdx
+++ b/src/content/docs/overview/glance.mdx
@@ -22,6 +22,11 @@ proven **GnuPG** and a modern, memory-safe Rust **rPGP** backend. Everything run
 - **Cross-platform**: native support for Windows, macOS, and Linux.
 - **Portable**: run straight from a USB drive and carry your keys with you.
 - **Profiles**: keep separate sets of keys and settings, and switch between them.
+  A temporary profile leaves nothing behind when you close it.
+- **Email**: write, sign, encrypt and send email, and read it from your mail
+  server.
+- **Modules**: extra features come as modules. A module you add yourself must
+  be signed, and you decide which publishers to trust.
 - **Flexible**: keep keys apart in multiple, separate key databases.
 - **Dual-engine**: switch freely between the mature GnuPG and the Rust rPGP
   backend.