diff --git a/docs/en/04_Changelogs/4.7.0.md b/docs/en/04_Changelogs/4.7.0.md
index c2a6b6df542..34035f9c695 100644
--- a/docs/en/04_Changelogs/4.7.0.md
+++ b/docs/en/04_Changelogs/4.7.0.md
@@ -2,6 +2,7 @@
 
 ## Overview
 
+- [Updated file usage table](#updated-file-usage-table)
 - [Experimental support for PHP 8](#experimental-support-for-php-8)
 - [Support for Symfony 4 Components](#support-for-symfony-4-components)
 - [Default MySQL collation updated](#default-mysql-collation-updated)
@@ -10,6 +11,24 @@
 
 ## New features
 
+### Updated file usage table
+
+CMS users can view where a file is used by accessing the Used on tab in the Files section. This feature allows them to
+identify what DataObjects depend on the file.
+
+The following changes have been made to the Used on table:
+- Data is now sourced from `has_one` and `many_many` relations instead of the ownership API
+- This means more data relationships should be shown than before
+- Uses the new `RelatedDataService` API in the framework module which can also be used for other non-file use cases
+- Support for linking ancestor relationships in the same table row, for instance showing the Page a Content Block is on
+- Ability to click on a row and navigate to the most relevant `CMSEditLink()`
+- Removal of draft badges
+- Styling tweaks such as reduced padding
+
+Your project specific DataObjects will automatically be displayed on this Used on tab. This may not always be desirable,
+especially when working with background DataObjects the user can not interact with directly. It is recommended you view
+the CMS Developer Guide for more information on this change, see the [File Usage section](docs/en/02_Developer_Guides/14_Files/07_File_Usage).
+
 ### Experimental support for PHP 8
 
 You can now run Silverstripe CMS on PHP 8, which is due for release in November 2020. PHP 8 includes
diff --git a/docs/en/04_Changelogs/beta/4.7.0-beta1.md b/docs/en/04_Changelogs/beta/4.7.0-beta1.md
index e3c12a9f671..30e101aceaa 100644
--- a/docs/en/04_Changelogs/beta/4.7.0-beta1.md
+++ b/docs/en/04_Changelogs/beta/4.7.0-beta1.md
@@ -2,6 +2,7 @@
 
 ## Overview
 
+- [Updated file usage table](#updated-file-usage-table)
 - [Experimental support for PHP 8](#experimental-support-for-php-8)
 - [Support for Symfony 4 Components](#support-for-symfony-4-components)
 - [Default MySQL collation updated](#default-mysql-collation-updated)
@@ -12,18 +13,22 @@
 
 ### Updated file usage table
 
-CMS users can view where a file is used by accessing the Used on tab in the Files section. This feature allows them to identify what DataObjects depend on the file.
+CMS users can view where a file is used by accessing the Used on tab in the Files section. This feature allows them to
+identify what DataObjects depend on the file.
 
 The following changes have been made to the Used on table:
-- Data is now sourced from has_one and many_many relations instead of the ownership API
+- Data is now sourced from `has_one` and `many_many` relations instead of the ownership API
 - This means more data relationships should be shown than before
-- Uses the new RelatedDataService API in the framework module which can also be used for other non-file use cases
+- Uses the new `RelatedDataService` API in the framework module which can also be used for other non-file use cases
 - Support for linking ancestor relationships in the same table row, for instance showing the Page a Content Block is on
+- Usage data is lazy-loaded when the Used on tab is selected to minimise its performance impact
 - Ability to click on a row and navigate to the most relevant `CMSEditLink()`
 - Removal of draft badges
 - Styling tweaks such as reduced padding
 
-Your project specific DataObjects will automatically be displayed on this Used on tab. This may not always be desirable, especially when working with background DataObjects the user can not interact with directly. It is recommended you view the CMS Developer Guide for more information on this change, see the [File Usage section](docs/en/02_Developer_Guides/14_Files/07_File_Usage).
+Your project specific DataObjects will automatically be displayed on this Used on tab. This may not always be desirable,
+especially when working with background DataObjects the user can not interact with directly. It is recommended you view
+the CMS Developer Guide for more information on this change, see the [File Usage section](docs/en/02_Developer_Guides/14_Files/07_File_Usage).
 
 ### Experimental support for PHP 8