aboutsummaryrefslogtreecommitdiff
path: root/content/pipelines.article
diff options
context:
space:
mode:
authorSameer Ajmani <sameer@golang.org>2014-03-13 11:57:42 -0400
committerSameer Ajmani <sameer@golang.org>2014-03-13 11:57:42 -0400
commit50f8651743a96af446eb1a21b9816a3bdeaf1a92 (patch)
tree3ed87ff7234207d3de4fa33321ca0268ad475305 /content/pipelines.article
parent9aa2e1143c55cfa6a0b8651067b34c61da8d5646 (diff)
add missing "of"
LGTM=rsc R=rsc, adg CC=golang-codereviews https://golang.org/cl/75450043
Diffstat (limited to 'content/pipelines.article')
-rw-r--r--content/pipelines.article4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/pipelines.article b/content/pipelines.article
index ab5d1ce..bfa24fc 100644
--- a/content/pipelines.article
+++ b/content/pipelines.article
@@ -8,8 +8,8 @@ Sameer Ajmani
Go's concurrency primitives make it easy to construct streaming data pipelines
that make efficient use of I/O and multiple CPUs. This article presents
-examples such pipelines, highlights subtleties that arise when operations fail,
-and introduces techniques for dealing with failures cleanly.
+examples of such pipelines, highlights subtleties that arise when operations
+fail, and introduces techniques for dealing with failures cleanly.
* What is a pipeline?