diff --git a/docs/introduction/notsupported.rst b/docs/introduction/notsupported.rst
index 3a5ffa42..ea23ab40 100644
--- a/docs/introduction/notsupported.rst
+++ b/docs/introduction/notsupported.rst
@@ -8,9 +8,9 @@ Ocelot does not support...
 * Forwarding a host header - The host header that you send to Ocelot will not be forwarded to the downstream service. Obviously this would break everything :(
 
 * Swagger - I have looked multiple times at building swagger.json out of the Ocelot ocelot.json but it doesnt fit into the vision 
-I have for Ocelot. If you would like to have Swagger in Ocelot then you must roll your own swagger.json and do the following in your 
-Startup.cs or Program.cs. The code sample below registers a piece of middleware that loads your hand rolled swagger.json and returns 
-it on /swagger/v1/swagger.json. It then registers the SwaggerUI middleware from Swashbuckle.AspNetCore
+  I have for Ocelot. If you would like to have Swagger in Ocelot then you must roll your own swagger.json and do the following in your 
+  Startup.cs or Program.cs. The code sample below registers a piece of middleware that loads your hand rolled swagger.json and returns 
+  it on /swagger/v1/swagger.json. It then registers the SwaggerUI middleware from Swashbuckle.AspNetCore
 
 .. code-block:: csharp
 
@@ -40,4 +40,4 @@ package doesnt reload swagger.json if it changes during runtime. Ocelot's config
 information would not match. Unless I rolled my own Swagger implementation.
 
 If the user wants something to easily test against the Ocelot API then I suggest using Postman as a simple way to do this. It might 
-even be possible to write something that maps ocelot.json to the postman json spec. However I don't intend to do this.
\ No newline at end of file
+even be possible to write something that maps ocelot.json to the postman json spec. However I don't intend to do this.