doc: perl -p -i -e s/certianly/certainly/

5 files changed, 5 insertions, 5 deletions

diff --git a/doc/design/assistant/blog/day_114__xmpp/comment_2_d14375dfb5791615802dab3c5438f8e2._comment b/doc/design/assistant/blog/day_114__xmpp/comment_2_d14375dfb5791615802dab3c5438f8e2._comment
index a18fa95e3..716f7d99a 100644
--- a/doc/design/assistant/blog/day_114__xmpp/comment_2_d14375dfb5791615802dab3c5438f8e2._comment
+++ b/doc/design/assistant/blog/day_114__xmpp/comment_2_d14375dfb5791615802dab3c5438f8e2._comment
@@ -4,5 +4,5 @@
  subject="comment 2"
  date="2012-11-09T21:55:42Z"
  content="""
-It does try to mark itself as extended away, but yes, I think this is a potential concern. If you find the assistant interacts badly with your other clients, you can certianly give it its own XMPP account.
+It does try to mark itself as extended away, but yes, I think this is a potential concern. If you find the assistant interacts badly with your other clients, you can certainly give it its own XMPP account.
 """]]
diff --git a/doc/design/assistant/blog/day_140__release_monday.mdwn b/doc/design/assistant/blog/day_140__release_monday.mdwn
index 5d732aef1..9c9ccd166 100644
--- a/doc/design/assistant/blog/day_140__release_monday.mdwn
+++ b/doc/design/assistant/blog/day_140__release_monday.mdwn
@@ -19,7 +19,7 @@ Still working on getting the standalone builds for this release done,
 should be done by the end of today.
 
 Also found a real stinker of a bug in `dirContentsRecursive`, which was
-just completely broken, apparently since day 1. Fixing that has certianly
+just completely broken, apparently since day 1. Fixing that has certainly
 fixed buggy behavior of `git annex import`. It seems that the other
 user of it, the transfer log code, luckily avoided the deep directory
 trees that triggered the bug.
diff --git a/doc/design/assistant/blog/day_76__pairing/comment_2_8e1b2233579bc26bfd758bbf6b3bdc07._comment b/doc/design/assistant/blog/day_76__pairing/comment_2_8e1b2233579bc26bfd758bbf6b3bdc07._comment
index 1ebc78627..a2e64671f 100644
--- a/doc/design/assistant/blog/day_76__pairing/comment_2_8e1b2233579bc26bfd758bbf6b3bdc07._comment
+++ b/doc/design/assistant/blog/day_76__pairing/comment_2_8e1b2233579bc26bfd758bbf6b3bdc07._comment
@@ -6,5 +6,5 @@
  content="""
 The [[bugs]] page is the place to put bug reports like this so I won't forget them.
 
-This should certianly not be happening. There are actually two git-annex processes running in the situation you describe; I'd be most curious to know whether the `git annex transfer` process was the one that blew up, or if the `git annex assistant` blew up. Also, it's not clear to me if you enabled the chunksize parameter when setting up the special remote, which could well be a significant detail.
+This should certainly not be happening. There are actually two git-annex processes running in the situation you describe; I'd be most curious to know whether the `git annex transfer` process was the one that blew up, or if the `git annex assistant` blew up. Also, it's not clear to me if you enabled the chunksize parameter when setting up the special remote, which could well be a significant detail.
 """]]
diff --git a/doc/design/assistant/blog/day_83__3-way.mdwn b/doc/design/assistant/blog/day_83__3-way.mdwn
index d58ec9fe5..9411c4c1c 100644
--- a/doc/design/assistant/blog/day_83__3-way.mdwn
+++ b/doc/design/assistant/blog/day_83__3-way.mdwn
@@ -68,6 +68,6 @@ still possible with other network topologies (ie, if D is connected to both
 B and C, there would be an upload loop 'B -> C -> D -> B`). So unless I can
 find a better event to hook into, this idea is doomed.
 
-I do have another idea to fix the same problem. C could certianly remember
+I do have another idea to fix the same problem. C could certainly remember
 that it saw a file and didn't know where to get the content from, and then
 when it receives a git push of a git-annex branch, try again.
diff --git a/doc/design/assistant/gpgkeys.mdwn b/doc/design/assistant/gpgkeys.mdwn
index e3f2a3a93..647d65083 100644
--- a/doc/design/assistant/gpgkeys.mdwn
+++ b/doc/design/assistant/gpgkeys.mdwn
@@ -7,7 +7,7 @@ To support using gpg keys in the assistant, we need some things:
 1. Help user set up a gpg key if they don't have one. This could be a
    special-purpose key dedicated to being used by git-annex. It might be
    nice to leave the user with a securely set up general purpose key,
-   but that would certianly preclude prompting for its password in the
+   but that would certainly preclude prompting for its password in the
    webapp. Indeed, the password prompt is the main problem here.
    Best solution would be to get gpg agent working on all supported 
    platforms.