From 4bad4d76551c176b6be7cb16502cca02d60fcadf Mon Sep 17 00:00:00 2001 From: Weng Shiwei Date: Tue, 25 Jul 2017 11:29:20 -0400 Subject: [PATCH] should be "requiring" module invokes the function Before this line, it says the function flows from providing module to requiring module. After this line, it says the argument travels back from requiring moduleo to providing module. I believe that argument supplying and function invoking should happen at requiring module, rather than providing module. --- .../scribblings/guide/contracts/new-combinators.scrbl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pkgs/racket-doc/scribblings/guide/contracts/new-combinators.scrbl b/pkgs/racket-doc/scribblings/guide/contracts/new-combinators.scrbl index 49027f5dae..d3316ecf1e 100644 --- a/pkgs/racket-doc/scribblings/guide/contracts/new-combinators.scrbl +++ b/pkgs/racket-doc/scribblings/guide/contracts/new-combinators.scrbl @@ -120,7 +120,7 @@ imagine the flow of values in a program between two modules. First, one module (the server) defines a function, and then that module is required by another (the client). So far, the function itself has to go from the original, providing module to the -requiring module. Now, imagine that the providing module +requiring module. Now, imagine that the requiring module invokes the function, supplying it an argument. At this point, the flow of values reverses. The argument is traveling back from the requiring module to the providing