manual: described pm catching better...

github_docs/de-Benutzeroberflaeche.md

@@ -56,7 +56,9 @@ Beide Hinweise blinken ungefähr zwölf Sekunden und verschwinden anschließend
 
 Das PM-Fenster zeigt die an die eigenen Chat-Logins gerichteten Privatnachrichten und die zugehörigen ausgehenden Antworten.
 
-Öffentliche Nachrichten erscheinen dort zusätzlich, wenn ihr Text ohne Beachtung der Groß- und Kleinschreibung das konfigurierte eigene Login-Rufzeichen enthält. Dieses PM-Catching – flapsig auch **„Lästererkennung“** – verändert weder den öffentlichen Empfänger `ALL` noch Nachrichtentext, Chat-Kategorie oder Routing.
+Nicht selbst gesendete Nachrichten erscheinen dort zusätzlich, wenn ihr Text ohne Beachtung der Groß- und Kleinschreibung das konfigurierte eigene Login-Rufzeichen enthält. Das gilt für öffentliche Nachrichten an `ALL` ebenso wie für gerichtete Nachrichten zwischen anderen Chatteilnehmern. Gerade im zweiten Fall lässt sich dieses PM-Catching flapsig als **„Lästererkennung“** bezeichnen.
+
+Der tatsächliche Empfänger, der Nachrichtentext, die Chat-Kategorie und das Routing bleiben unverändert. Die Nachricht erhält lediglich eine zusätzliche Darstellung im PM-Fenster.
 
 Ist das [QSO-Monitoring](de-Funktionen#qso-monitoring-ab-v131) aktiviert, erscheinen dort zusätzlich die erfassten Nachrichten der überwachten Basisrufzeichen. Diese Einträge erhalten eine `Sniffed:`-Kennzeichnung mit dem vollständigen sichtbaren Absender und Empfänger.
 

github_docs/de-Funktionen.md

@@ -271,9 +271,11 @@ Manche Nutzer senden Direktnachrichten versehentlich öffentlich, z. B.:
 (DM5M) pse ur qrg
 ```
 
-KST4Contest sucht im Nachrichtentext ohne Beachtung der Groß- und Kleinschreibung nach dem konfigurierten eigenen Login-Rufzeichen. Enthält eine öffentliche Nachricht diesen Text, erscheint sie zusätzlich in der **Privatnachrichten-Tabelle**. Etwas flapsig lässt sich das als **„Lästererkennung“** bezeichnen. Das ist eine Nebenbezeichnung, kein formaler Funktionsname.
+KST4Contest sucht im Text aller nicht selbst gesendeten Nachrichten ohne Beachtung der Groß- und Kleinschreibung nach dem konfigurierten eigenen Login-Rufzeichen. Ein Treffer erscheint zusätzlich in der **Privatnachrichten-Tabelle**. Das gilt sowohl für öffentliche Nachrichten an `ALL` als auch für gerichtete Nachrichten zwischen anderen Chatteilnehmern.
 
-Die ursprüngliche Nachricht bleibt unverändert: Sie ist weiterhin öffentlich, behält ihren Empfänger `ALL`, ihren Text und ihre Chat-Kategorie. PM-Catching ergänzt nur eine weitere Ansicht derselben Nachricht.
+Gerade bei einer fremden gerichteten Nachricht wirkt das etwas wie **„Lästererkennung“**. Das ist eine flapsige Nebenbezeichnung, kein formaler Funktionsname.
+
+Die ursprüngliche Nachricht bleibt unverändert: Der tatsächliche Empfänger bleibt `ALL` beziehungsweise der andere Chatteilnehmer; auch Text, Chat-Kategorie und Routing bleiben erhalten. PM-Catching ergänzt nur eine weitere Ansicht derselben Nachricht.
 
 Die Textsuche versteht keine Absicht. Ein Schreibfehler oder ein verkürztes Rufzeichen wird nicht erkannt. Umgekehrt kann eine bloße Erwähnung des vollständig geschriebenen Rufzeichens einen Treffer erzeugen, obwohl keine Antwort erwartet wird.
 

github_docs/en-Configuration.md

@@ -373,13 +373,15 @@ AirScout setup, aircraft display and the meaning of the returned AP information
 
 ![Notifications, DX cluster output and QSO monitoring](client_settings_window_notification.png)
 
-Three notification types are available:
+The three audio functions work independently:
 
-1. **Simple sounds**: TADA sound for incoming messages, tick for sked direction detection, etc.
+1. **Simple sounds**: Plays short cues for new private messages, detected directional opportunities, sked reminders and `BAND+` hints.
-2. **CW announcement**: The callsign of a station sending a private message is output as a CW signal.
+2. **CW announcement**: Spells the sender's callsign in CW for a new private message.
-3. **Phonetic announcement**: The callsign is pronounced phonetically.
+3. **Phonetic announcement**: Speaks the sender's callsign phonetically for a new private message.
 
-PM-related audio output is triggered only by messages actually directed to the local login callsign. Public messages shown additionally through PM Catching and messages added through QSO Monitoring remain silent.
+Each function can be enabled separately. CW and phonetic output can also be active at the same time.
+
+PM-related audio output is triggered only by messages actually directed to the local login callsign. Messages shown additionally through PM Catching and messages added through QSO Monitoring remain silent.
 
 ### Fallback Band for Relative QRG Detection
 

github_docs/en-Features.md

@@ -270,9 +270,11 @@ Some users accidentally post direct messages publicly, e.g.:
 (DM5M) pse ur qrg
 ```
 
-KST4Contest searches the message text for the configured local login callsign without distinguishing upper- and lower-case letters. When a public message contains that text, it also appears in the **private messages table**. A slightly flippant description is **“gossip detection”**. This is a nickname, not the formal name of the function.
+KST4Contest searches the text of every message not sent by the local station for the configured local login callsign without distinguishing upper- and lower-case letters. A match also appears in the **private messages table**. This applies to public messages addressed to `ALL` and to directed messages between other chat participants.
 
-The original message remains unchanged: it is still public and retains its `ALL` receiver, text and chat category. PM Catching merely adds another view of the same message.
+A directed message between two other stations is where the slightly flippant description **“gossip detection”** fits best. It is a nickname, not the formal name of the function.
+
+The original message remains unchanged: its actual receiver remains `ALL` or the other chat participant; its text, chat category and routing are retained as well. PM Catching merely adds another view of the same message.
 
 The text search cannot infer intention. A typing error or shortened callsign is not recognised. Conversely, a simple mention of the complete callsign can produce a match even when no reply was expected.
 

github_docs/en-User-Interface.md

@@ -56,7 +56,9 @@ Both indicators flash for approximately twelve seconds and then disappear. Their
 
 The PM window shows private messages addressed to the local chat logins and the corresponding outgoing replies.
 
-Public messages are also shown when their text contains the configured local login callsign, ignoring letter case. This PM Catching mechanism – informally, **“gossip detection”** – changes neither the public `ALL` receiver nor the message text, chat category or routing.
+Messages not sent by the local station are also shown when their text contains the configured local login callsign, ignoring letter case. This applies to public messages addressed to `ALL` and to directed messages between other chat participants. The informal description **“gossip detection”** is particularly apt for the latter case.
+
+The actual receiver, message text, chat category and routing remain unchanged. The message merely gains an additional representation in the PM window.
 
 If [QSO Monitoring](en-Features#qso-sniffer-from-v131) is enabled, it additionally shows captured messages involving the monitored base callsigns. These entries receive a `Sniffed:` prefix containing the complete visible sender and receiver callsigns.
 

website/src/features/private-message-handling.md

@@ -3,8 +3,8 @@ title: Private Message Handling
 icon: ✉️
 category: ON4KST Chat
 since: "1.1"
-summary: Catch public mentions of the configured login callsign in the PM table and use six green age levels to keep recent messages visible without changing their routing.
+summary: Catch mentions of the configured login callsign from public or directed chat traffic and use six green age levels without changing the original message routing.
-description: KST4Contest combines PM Catching, age-based row highlighting and reply preparation so that direct messages and relevant public mentions remain practical to handle during a busy contest.
+description: KST4Contest combines PM Catching, age-based row highlighting and reply preparation for direct messages and callsign mentions across the visible chat traffic.
 tagsList:
   - ON4KST
   - private messages
@@ -21,15 +21,15 @@ related:
 
 ## Why catch more than direct PMs?
 
-Not every message intended for one station is sent as a directed ON4KST message. An operator may accidentally post something like this publicly:
+Not every message which concerns the local station is addressed to it directly. An operator may accidentally post something like this publicly:
 
 ```text
 (DM5M) pse ur qrg
 ```
 
-Without an additional view, that line remains among CQ calls, beacons and the rest of the public chat. KST4Contest therefore also shows a public message in the PM table when its text contains the configured local login callsign.
+The callsign may also appear in a directed message between two other chat participants. KST4Contest therefore also shows every message not sent by the local station in the PM table when its text contains the configured local login callsign. This covers public messages addressed to `ALL` and directed traffic between other stations.
 
-PM Catching has existed since version 1.1. A slightly flippant description is **“gossip detection”**. It is a nickname, not the formal name of the function.
+PM Catching has existed since version 1.1. For directed messages between other stations, a slightly flippant description is **“gossip detection”**. It is a nickname, not the formal name of the function.
 
 ## How is a mention recognised?
 
@@ -46,7 +46,7 @@ In plain terms: PM Catching finds visible callsign text. It cannot know what the
 
 ## The original message remains unchanged
 
-Catching adds the message to the PM view. It does not turn the public line into a private message, change its receiver, rewrite its text or move it to another chat category.
+Catching adds the message to the PM view. It does not turn it into a private message to the local station. The actual receiver remains `ALL` or the other chat participant; message text, chat category and routing remain unchanged as well.
 
 The same principle applies to [QSO Monitoring](/features/qso-monitoring/): a monitored message may be shown additionally in the PM table, but its original routing remains intact. The two mechanisms use different criteria:
 
@@ -79,7 +79,7 @@ After five minutes, the row returns to the normal table colour. Messages sent by
 
 ## What produces a PM notification sound?
 
-PM audio is reserved for messages actually directed to the local login. A public message shown through PM Catching does not trigger the simple PM sound, CW callsign output or phonetic callsign output.
+PM audio is reserved for messages actually directed to the local login. A message shown through PM Catching does not trigger the simple PM sound, CW callsign output or phonetic callsign output.
 
 Messages added through QSO Monitoring likewise remain silent. Their appearance in the PM table is a visual aid, not evidence that the local station received a new private message.