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

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_4_d0e55585f1612148163039d157253258._comment b/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_4_d0e55585f1612148163039d157253258._comment
index dccc5cd6a..1e2a8fe24 100644
--- a/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_4_d0e55585f1612148163039d157253258._comment
+++ b/doc/bugs/non-repos_in_repositories_list___40__+_other_weird_output__41___from_git_annex_status/comment_4_d0e55585f1612148163039d157253258._comment
@@ -4,7 +4,7 @@
  subject="comment 4"
  date="2013-07-26T16:52:26Z"
  content="""
-The 4201 dangling blobs is a little bit strange, although it could certianly happen in some normal scenarios.
+The 4201 dangling blobs is a little bit strange, although it could certainly happen in some normal scenarios.
 Overall, your repository seems to be ok except for this weird data in the one file. I do not anticipate the extra garbage causing any problems at all.
 
 To track this down, we need to find the commit that added the garbage. One way, assuming you're using indirect mode, is to `git checkout git-annex; git blame uuid.log` and `git show` the commit that added the garbage. If you're using direct mode, you should first `git clone` the repository and do that in the clone.