[sling-org-apache-sling-pipes] 24/31: typo

[ro...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rombert pushed a commit to annotated tag org.apache.sling.pipes-0.0.10
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-pipes.git

commit 088c4f8357d3294c906a4ae7d685cc3d55dc617f
Author: Oliver Lietz <ol...@apache.org>
AuthorDate: Sun Oct 2 12:18:10 2016 +0000

    typo
    
    git-svn-id: https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/sling-pipes@1763058 13f79535-47bb-0310-9956-ffa450edef68
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index fba116b..a32bb4a 100644
--- a/README.md
+++ b/README.md
@@ -18,7 +18,7 @@ getInput  +---+---+   getOutput
 A sling pipe is essentially a sling resource stream:
 * it provides an output as a sling resource iterator
 * it gets its input either from a configured path, either, if its chained (see container pipes below), from another pipe's output
-* each pipe can have additional dynamic inputs using other's bindings, and outputing its own bindings
+* each pipe can have additional dynamic inputs using other's bindings, and outputting its own bindings
  
 At the moment, there are 3 types of pipes to consider:
 * "reader" pipes, that will just output a set of resource depending on the input

-- 
To stop receiving notification emails like this one, please contact
"commits@sling.apache.org" <co...@sling.apache.org>.