From 69b67b3b4b9c4be435125e1a526e938ef5a25109 Mon Sep 17 00:00:00 2001 From: Jocelyn Fiat Date: Tue, 7 Jan 2014 05:11:40 -0800 Subject: [PATCH] Updated Documentation (markdown) --- Documentation.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation.md b/Documentation.md index b50d51b7..ad1d2494 100644 --- a/Documentation.md +++ b/Documentation.md @@ -26,7 +26,7 @@ This is the low level of the framework, at this point, `req` provides access to The response `res` is the interface to send data back to the client. For convenience, the framework provides richer service interface that handles the most common needs (filter, router, ...). -[Learn more about service](Documentation__Service) +> [Learn more about service](Documentation__Service) # Request and Response @@ -63,7 +63,7 @@ Currently 3 main connectors are available: At compilation time, you can use a default connector (by using the associated default lib), but you can also use a mixed of them and choose which one to execute at runtime. It is fairly easy to add new connector, it just has to follow the EWSGI interface -[Learn more about connector](Documentation__Connector) +> [Learn more about connector](Documentation__Connector) # Router or Request Dispatcher: @@ -109,7 +109,7 @@ How we do that in EWF? : Router with (or without context). Related code: wsf_router, wsf_router_context Examples -[Learn more about router](Documentation__Router) +> [Learn more about router](Documentation__Router) # EWF components ## URI Handler: