diff --git a/docs/en/02_Developer_Guides/01_Templates/03_Requirements.md b/docs/en/02_Developer_Guides/01_Templates/03_Requirements.md
index c579c5b69b1..b6b69b71b82 100644
--- a/docs/en/02_Developer_Guides/01_Templates/03_Requirements.md
+++ b/docs/en/02_Developer_Guides/01_Templates/03_Requirements.md
@@ -240,10 +240,6 @@ You can also use any of the below options in order to tweak this behaviour:
    other systems, it is usually necessary to distinguish combined files from other assets.
  * `Requirements_Backend.combine_in_dev` - By default combined files will not be combined except in test
    or live environments. Turning this on will allow for pre-combining of files in development mode.
- * `Requirements_Backend.resolve_relative_css_refs` - By default combined files will be parsed for relative urls 
-   to image/font assets and those URLs will be changed to absolute to accommodate the fact that the combined 
-   css is placed in a totally different folder than the source css files. Turn this off if you see some 
-   unexpected results.
 
 In some cases it may be necessary to create a new storage backend for combined files, if the default location
 is not appropriate. Normally a single backend is used for all site assets, so a number of objects must be
@@ -258,7 +254,6 @@ SilverStripe\View\Requirements:
   disable_flush_combined: true
 SilverStripe\View\Requirements_Backend:
   combine_in_dev: true
-  resolve_relative_css_refs: true
   combine_hash_querystring: true
   default_combined_files_folder: 'combined'
 SilverStripe\Core\Injector\Injector: