Permalink
Browse files

README: fix typos

  • Loading branch information...
falconindy committed Dec 25, 2012
1 parent 1aa1075 commit 38357d39d73c571b6b947f37602460fd6a17b362
Showing with 8 additions and 8 deletions.
  1. +8 −8 README.md
View
@@ -10,14 +10,14 @@ it with your project and source it from a controlled location.
## How to Use
-Source apron as early as possible, and call `APRON_enable`. This initializes
-a small amount of bookkeeping needed to intercept calls and keep track of
-any mocks which you might register. At this point, any call which cannot
-be resolved by the shell will be caught by Apron as an uninteresting call.
-You can enable Apron with the `-v` to get verbose output as to what Apron
-is doing.
-
-Next, define your mock! Let's call it `badcommand`. Of course, at this point,
+Source apron as early as possible, and call `APRON_enable`. This initializes a
+small amount of bookkeeping needed to intercept calls and keep track of any
+mocks which you might register. At this point, any call which cannot be
+resolved by the shell will be caught by Apron as an uninteresting call. You can
+enable Apron with the `-v` flag to get verbose output as to what Apron is
+doing.
+
+Next, define your mocks! Let's call one `badcommand`. Of course, at this point,
since shell functions take priority over external commands, the function will
always be called. However, you'll also want to register your mock with Apron,
by calling `APRON_register badcommand`. This allows Apron to keep track of

0 comments on commit 38357d3

Please sign in to comment.