diff --git a/docs/development.rst b/docs/development.rst
index 365025d92..05719df8f 100644
--- a/docs/development.rst
+++ b/docs/development.rst
@@ -340,7 +340,7 @@ Checklist:
 - announce on:
 
  - Mailing list
- - Twitter (follow @ThomasJWaldmann for these tweets)
+ - Twitter
  - IRC channel (change ``/topic``)
 
 - create a GitHub release, include:
diff --git a/docs/support.rst b/docs/support.rst
index 293264f51..8bd3fcbed 100644
--- a/docs/support.rst
+++ b/docs/support.rst
@@ -38,6 +38,15 @@ unsubscribe and where you can find the archives of the list, see the
 `mailing list homepage
 <https://mail.python.org/mailman/listinfo/borgbackup>`_.
 
+Twitter
+-------
+
+Follow @borgbackup for announcements. You can also add @borgbackup if you
+would like to get retweeted for a borg related tweet.
+
+Please understand that Twitter is not suitable for longer / more complex
+discussions - use one of the other channels for that.
+
 Bounties and Fundraisers
 ------------------------
 
diff --git a/docs/usage/notes.rst b/docs/usage/notes.rst
index 85648382e..c45ef3f8c 100644
--- a/docs/usage/notes.rst
+++ b/docs/usage/notes.rst
@@ -50,6 +50,17 @@ a new repository when changing chunker params.
 For more details, see :ref:`chunker_details`.
 
 
+``--noatime / --noctime``
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can use these ``borg create`` options to not store the respective timestamp
+into the archive, in case you do not really need it.
+
+Besides saving a little space for the not archived timestamp, it might also
+affect metadata stream deduplication: if only this timestamp changes between
+backups and is stored into the metadata stream, the metadata stream chunks
+won't deduplicate just because of that.
+
 ``--umask``
 ~~~~~~~~~~~
 
diff --git a/src/borg/archiver.py b/src/borg/archiver.py
index f081cdcdb..2dd290875 100644
--- a/src/borg/archiver.py
+++ b/src/borg/archiver.py
@@ -2520,6 +2520,11 @@ class Archiver:
         change_passphrase_epilog = process_epilog("""
         The key files used for repository encryption are optionally passphrase
         protected. This command can be used to change this passphrase.
+
+        Please note that this command only changes the passphrase, but not any
+        secret protected by it (like e.g. encryption/MAC keys or chunker seed).
+        Thus, changing the passphrase after passphrase and borg key got compromised
+        does not protect future (nor past) backups to the same repository.
         """)
         subparser = key_parsers.add_parser('change-passphrase', parents=[common_parser], add_help=False,
                                           description=self.do_change_passphrase.__doc__,