summaryrefslogtreecommitdiffstats
path: root/doc/kmail/using-kmail.docbook
diff options
context:
space:
mode:
authorMavridis Philippe <mavridisf@gmail.com>2022-07-18 14:58:59 +0300
committerMavridis Philippe <mavridisf@gmail.com>2022-07-18 14:58:59 +0300
commitb4a0d3cc1eacfb1e59e0fcd7831a7561ef04a646 (patch)
tree8f92236b9669f0c8cfc661dddf49b752d9bdf6f8 /doc/kmail/using-kmail.docbook
parent3b2bf711dacdeecaf8b244caa873216c7d245091 (diff)
downloadtdepim-b4a0d3cc1eacfb1e59e0fcd7831a7561ef04a646.tar.gz
tdepim-b4a0d3cc1eacfb1e59e0fcd7831a7561ef04a646.zip
Gender-neutral language
Related to TDE/tde#93. Signed-off-by: Mavridis Philippe <mavridisf@gmail.com>
Diffstat (limited to 'doc/kmail/using-kmail.docbook')
-rw-r--r--doc/kmail/using-kmail.docbook4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/kmail/using-kmail.docbook b/doc/kmail/using-kmail.docbook
index 999bd6d96..8609f2e6a 100644
--- a/doc/kmail/using-kmail.docbook
+++ b/doc/kmail/using-kmail.docbook
@@ -344,7 +344,7 @@ choose from the list of common &MIME; types. You can also select an encoding
method for your file from the list of encoding options (normally, the default
value works fine). Check the <guilabel>Suggest automatic display</guilabel> option
if you want to suggest to the recipient the automatic (inline) display of this attachment. Whether this works or not depends on the recipient's email client
-and on his settings.</para>
+and on their settings.</para>
<para>You can also attach public keys to the message by using the appropriate options in the
<menuchoice><guimenu>Attach</guimenu></menuchoice> menu. <application>PGP</application>
@@ -2014,7 +2014,7 @@ defined for the current identity to the message. Now you can send the message.</
that the receiver will get the correct key: there can be a man-in-the-middle
attack, as somebody can change the key and sign the message with that other
key. That is why the recipient should verify the attached key by checking the
-key's fingerprint against the one he received in a secure way from you; have a look
+key's fingerprint against the one they received in a secure way from you; have a look
at the <application>PGP</application> documentation for further details.</para>
</sect2>