From 55655ada3b5d38d6357648cfde72017f1f2ca9cb Mon Sep 17 00:00:00 2001 From: Patrick Huber Date: Fri, 28 Nov 2014 09:20:11 +0100 Subject: [PATCH] typos --- Documentation/Books/Users/Foxx/HandlingRequest.mdpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/Books/Users/Foxx/HandlingRequest.mdpp b/Documentation/Books/Users/Foxx/HandlingRequest.mdpp index 957ec0d596..05e29c8aa3 100644 --- a/Documentation/Books/Users/Foxx/HandlingRequest.mdpp +++ b/Documentation/Books/Users/Foxx/HandlingRequest.mdpp @@ -78,7 +78,7 @@ like any other collection with the db object, e.g. ``` Of course you still use any collection directly with the db object even -from Foxx. To access an collection called "movies" this could be one solution: +from Foxx. To access a collection called "movies" this could be one solution: ```js app.get("/all", function(req, res) { @@ -95,7 +95,7 @@ Then there are Foxx repositories. These are objects that you can create to hide the internals of the database access from the application so that the application will just use the repository but not the database. -A repository is an object that wrap access to a collection (or multiple +A repository is an object that wraps access to a collection (or multiple collections if you want), whereas controller.collection returns the collection itself. That's the main difference.