diff --git a/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md b/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md
index 632597cbb..f834e4d24 100644
--- a/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md
+++ b/docs/en/02_Developer_Guides/02_Controllers/05_Middlewares.md
@@ -6,8 +6,11 @@ summary: Create objects for modifying request and response objects across contro
 # HTTP Middlewares
 
 HTTP Middlewares allow you to put code that will run before or after. These might be used for
-authentication, logging, caching, request processing, and many other purposes. Note this interface
-replaces the SilverStripe 3 interface [RequestFilter](api:SilverStripe\Control\RequestFilter), which still works but is deprecated.
+authentication, logging, caching, request processing, and many other purposes. 
+
+[notice]
+Note this interface replaces the SilverStripe 3 interface [RequestFilter](api:SilverStripe\Control\RequestFilter), which still works but is deprecated.
+[/notice]
 
 To create a middleware class, implement `SilverStripe\Control\Middleware\HTTPMiddleware` and define the
 `process(HTTPRequest $request, callable $delegate)` method. You can do anything you like in this