diff --git a/docs/architecture/modern-web-apps-azure/work-with-data-in-asp-net-core-apps.md b/docs/architecture/modern-web-apps-azure/work-with-data-in-asp-net-core-apps.md
index 9c9ddf7c1ac3b..16d9b043d029f 100644
--- a/docs/architecture/modern-web-apps-azure/work-with-data-in-asp-net-core-apps.md
+++ b/docs/architecture/modern-web-apps-azure/work-with-data-in-asp-net-core-apps.md
@@ -379,10 +379,9 @@ When implementing caching, it's important to keep in mind separation of concerns
 ASP.NET Core supports two levels of response caching. The first level does not cache anything on the server, but adds HTTP headers that instruct clients and proxy servers to cache responses. This is implemented by adding the ResponseCache attribute to individual controllers or actions:
 
 ```csharp
-    [ResponseCache(Duration = 60)]
-    public IActionResult Contact()
-    { }
-
+[ResponseCache(Duration = 60)]
+public IActionResult Contact()
+{
     ViewData["Message"] = "Your contact page.";
     return View();
 }