From 258bf4a84010eefe325b129a0acc9c51a1ffe25a Mon Sep 17 00:00:00 2001
From: affanshahid <affan.shahid.94@gmail.com>
Date: Sat, 13 Oct 2018 21:18:26 +0500
Subject: [PATCH] Fix incorrect information about the return value

---
 src/app/homepage/pages/controllers/controllers.component.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/app/homepage/pages/controllers/controllers.component.html b/src/app/homepage/pages/controllers/controllers.component.html
index 63e820a9d8..2efc95dfc8 100644
--- a/src/app/homepage/pages/controllers/controllers.component.html
+++ b/src/app/homepage/pages/controllers/controllers.component.html
@@ -35,8 +35,8 @@ <h4>Routing</h4>
     <code>cats</code>), Nest will map every <code>/cats</code> <strong>GET</strong> request to this method.
   </p>
   <p>
-    When a GET request is made to this endpoint, Nest will now return a 200 status code and the serialized <strong>JSON</strong>
-    response, which in this case just an empty array. Why does that happen? Generally, we distinguish <strong>two different
+    When a GET request is made to this endpoint, Nest will now return a 200 status code and the associated
+    response, which in this case is just a string. Why does that happen? Generally, we distinguish <strong>two different
       approaches
     </strong> to manipulate responses:
   </p>