diff --git a/docs/faq.rst b/docs/faq.rst
index 8c88125ca..ef6ca6619 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -165,6 +165,8 @@ Yes, if you want to detect accidental data damage (like bit rot), use the
 If you want to be able to detect malicious tampering also, use a encrypted
 repo. It will then be able to check using CRCs and HMACs.
 
+.. _a_status_oddity:
+
 I am seeing 'A' (added) status for a unchanged file!?
 -----------------------------------------------------
 
diff --git a/docs/usage.rst b/docs/usage.rst
index 5bba83904..1db3bc594 100644
--- a/docs/usage.rst
+++ b/docs/usage.rst
@@ -444,7 +444,7 @@ A uppercase character represents the status of a regular file relative to the
 is not used). Metadata is stored in any case and for 'A' and 'M' also new data
 chunks are stored. For 'U' all data chunks refer to already existing chunks.
 
-- 'A' = regular file, added
+- 'A' = regular file, added (see also :ref:`a_status_oddity` in the FAQ)
 - 'M' = regular file, modified
 - 'U' = regular file, unchanged
 - 'E' = regular file, an error happened while accessing/reading *this* file