correct spelling mistakes

3 files changed, 3 insertions, 3 deletions

diff --git a/doc/todo/Add_confirmation_dialog_to_the_restart_option/comment_1_00da59dc2d9b86a51eb462c481ab665d._comment b/doc/todo/Add_confirmation_dialog_to_the_restart_option/comment_1_00da59dc2d9b86a51eb462c481ab665d._comment
index ca60ec5fd..0732b7dde 100644
--- a/doc/todo/Add_confirmation_dialog_to_the_restart_option/comment_1_00da59dc2d9b86a51eb462c481ab665d._comment
+++ b/doc/todo/Add_confirmation_dialog_to_the_restart_option/comment_1_00da59dc2d9b86a51eb462c481ab665d._comment
@@ -6,7 +6,7 @@
 Restarting the daemon should just take a second and the web browser should
 redirect to the new instance. I guess it does move away from the current
 page to the dashboard, and in a way that the back button can't undo, but I
-see no other harm in accidentially restarting the daemon.
+see no other harm in accidentally restarting the daemon.
 
 So, I think I'll just add a spacer to separate the repository part of that
 menu from the daemon part.
diff --git a/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment b/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment
index ba8526a34..6d4f9b026 100644
--- a/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment
+++ b/doc/todo/be_able_to_specify_custom_commit_message_for_git-annex_branch_commit/comment_1_c8836a164c8c1efedd5467233237bfd0._comment
@@ -10,7 +10,7 @@ out of the user's view, because it's a complication that should not
 need to worry about.
 
 Keeping it in an env var does avoid complicating the discoverable
-interface with some parameter to specifiy the commit message. Another
+interface with some parameter to specify the commit message. Another
 way would be to make the commit message configurable in git config.
 Then it could be overridden with -c. Seems like the user of this 
 feature is likely going to also use annex.alwayscommit=false sometimes
diff --git a/doc/todo/wishlist__58___make_partial_files_available_during_transfer/comment_3_1304a721da6f5133fdfa1dac507f1ecb._comment b/doc/todo/wishlist__58___make_partial_files_available_during_transfer/comment_3_1304a721da6f5133fdfa1dac507f1ecb._comment
index 8e955fd48..2907dafc3 100644
--- a/doc/todo/wishlist__58___make_partial_files_available_during_transfer/comment_3_1304a721da6f5133fdfa1dac507f1ecb._comment
+++ b/doc/todo/wishlist__58___make_partial_files_available_during_transfer/comment_3_1304a721da6f5133fdfa1dac507f1ecb._comment
@@ -4,7 +4,7 @@
  subject="comment 3"
  date="2012-11-04T19:58:28Z"
  content="""
-I'm not at all comfortable with either idea. Temporarily repointing the symlink could lead to accidentially git committing a bad symlink. Or the user accidentially doing something with a partially transferred file. Running rsync in place would break lots of things that assume that, once the file is present, it can be assumed to be the full and correct file. (Obviously fsck doesn't assume that, but checks made by `git annex drop` do, for example.)
+I'm not at all comfortable with either idea. Temporarily repointing the symlink could lead to accidentally git committing a bad symlink. Or the user accidentally doing something with a partially transferred file. Running rsync in place would break lots of things that assume that, once the file is present, it can be assumed to be the full and correct file. (Obviously fsck doesn't assume that, but checks made by `git annex drop` do, for example.)
 
 However, you can access partially transferred files by key in `.git/annex/tmp`. It would be easy to write some hack that looks at the symlink to get the key, and then spits out the name of the partial file in `.git/annex/tmp.`.
 """]]