aboutsummaryrefslogtreecommitdiff
path: root/doc/doc.RPKI.RP.rcynic
diff options
context:
space:
mode:
authorRPKI Documentation Robot <docbot@rpki.net>2016-03-27 18:00:58 +0000
committerRPKI Documentation Robot <docbot@rpki.net>2016-03-27 18:00:58 +0000
commitb0bafd42f83c29e8f8fb51388810637e0488c2e2 (patch)
treeb40162081c2b832e12812c6e0c21c30bbda2aa7b /doc/doc.RPKI.RP.rcynic
parent774a6d9502e20400745fd8c245e062d0e63503e2 (diff)
Automatic pull of documentation from Wiki.
svn path=/trunk/; revision=6331
Diffstat (limited to 'doc/doc.RPKI.RP.rcynic')
-rw-r--r--doc/doc.RPKI.RP.rcynic2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/doc.RPKI.RP.rcynic b/doc/doc.RPKI.RP.rcynic
index 4bd95ae1..f3ba5e4c 100644
--- a/doc/doc.RPKI.RP.rcynic
+++ b/doc/doc.RPKI.RP.rcynic
@@ -447,7 +447,7 @@ except when building complex topologies where rcynic running on one set of
machines acts as aggregators for another set of validators. A large ISP might
want to build such a topology so that they could have a local validation cache
in each POP while minimizing load on the global repository system and
-maintaining some degree of internal consistancy between POPs. In such cases,
+maintaining some degree of internal consistency between POPs. In such cases,
one might want the rcynic instances in the POPs to validate data fetched from
the aggregators via an external process, without the POP rcynic instances
attempting to fetch anything themselves.