From d07cdfbc5e232a45fe93b474fa2c376969c7d6d6 Mon Sep 17 00:00:00 2001
From: TroisSinges <TroisSinges@web>
Date: Tue, 26 Nov 2013 21:59:29 +0000
Subject: [PATCH] typo

---
 .../bugs/direct_mode_sync_should_avoid_git_commit.mdwn          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn b/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
index 74e1d89c92..63c90a0318 100644
--- a/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
+++ b/doc/forum/Actions_very_slow_on_a_direct___40__and_crippled__41___annex_repository/bugs/direct_mode_sync_should_avoid_git_commit.mdwn
@@ -1,3 +1,3 @@
 Per forum post linking to this bug, git commit can be very slow when run in a filesystem without symlink support, and seems to be reading the content of files just in order to show typechanged messages in the status.
 
-So, git annex sync should stop using git commit when in direct mode, and intead manually make its own commit. Git.Branch.commit and Git.Branch.update should be able to easily be used for this.
+So, git annex sync should stop using git commit when in direct mode, and instead manually make its own commit. Git.Branch.commit and Git.Branch.update should be able to easily be used for this.