Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

more small fix/details

  • Loading branch information...
commit f163277f256e53fb58c5a97ab3bd207af20f802a 1 parent a9b32d0
@diegoviola diegoviola authored
View
2  guide/general/controllers.md
@@ -13,7 +13,7 @@ instead it will merely tell the cooks to make the dinner and bring it to you onc
it's done. The waiter is our controller, the cook is our model and our meal can
be seen as the view.
-In a typical application the entire flow of a request is as following::
+In a typical application the entire flow of a request is as following:
Request --> Server (Thin, Unicorn, etc) --> Rack --> Ramaze --> Controller
View
2  guide/general/middlewares.md
@@ -7,7 +7,7 @@ in order to intercept and process sequentially each incoming request and outgoin
response between Rack and Ramaze. You can think of a collection of middlewares
as a stack at whose bottom lies your Ramaze app.
-The flow of a Rack request (including middlewares) looks as following::
+The flow of a Rack request (including middlewares) looks as following:
Request --> Server (Thin, Unicorn, etc) --> Rack --> Middleware(s) -->
Ramaze --> Controller
View
2  guide/general/views.md
@@ -4,7 +4,7 @@
Views are the last step in the process of a request to a MVC framework such as
Ramaze. A controller loads a model, the model processes a certain amount of
data and the controller will then pass this data to a view. The typical flow of
-a MVC framework (or any framework using a view system) looks like the following::
+a MVC framework (or any framework using a view system) looks like the following:
Request --> Controller --> View
^ |
Please sign in to comment.
Something went wrong with that request. Please try again.