diff --git a/docs/configuration.md b/docs/configuration.md
index 70011cc0..3f77059f 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -219,6 +219,8 @@ By default, Catch does not stringify some types from the standard library. This
 
 ## Disabling exceptions
 
+> Introduced in Catch 2.4.0.
+
 By default, Catch2 uses exceptions to signal errors and to abort tests
 when an assertion from the `REQUIRE` family of assertions fails. We also
 provide an experimental support for disabling exceptions. Catch2 should
diff --git a/docs/test-cases-and-sections.md b/docs/test-cases-and-sections.md
index 5f524320..53f9e150 100644
--- a/docs/test-cases-and-sections.md
+++ b/docs/test-cases-and-sections.md
@@ -90,6 +90,8 @@ These macros map onto ```SECTION```s except that the section names are the _some
 
 Similar to ```GIVEN```, ```WHEN``` and ```THEN``` except that the prefixes start with "and ". These are used to chain ```GIVEN```s, ```WHEN```s and ```THEN```s together.
 
+> `AND_GIVEN` was [introduced](https://github.com/catchorg/Catch2/issues/1360) in Catch 2.4.0.
+
 When any of these macros are used the console reporter recognises them and formats the test case header such that the Givens, Whens and Thens are aligned to aid readability.
 
 Other than the additional prefixes and the formatting in the console reporter these macros behave exactly as ```TEST_CASE```s and ```SECTION```s. As such there is nothing enforcing the correct sequencing of these macros - that's up to the programmer!