summaryrefslogtreecommitdiff
path: root/doc/devblog
diff options
context:
space:
mode:
authorGravatar Richard Hartmann <richih@debian.org>2013-11-25 21:40:19 +0100
committerGravatar Richard Hartmann <richih@debian.org>2013-11-25 21:40:19 +0100
commitb8e9e2a1d2556ce0628e451717af665d59a204ef (patch)
treeff76b245774bac3fcc654284b3f26e12b75370a2 /doc/devblog
parent59f2984911e5761c3d7cc6b2c9ed3deb58a62a74 (diff)
doc: perl -p -i -e s/certianly/certainly/
Diffstat (limited to 'doc/devblog')
-rw-r--r--doc/devblog/day_-4__forgetting.mdwn2
-rw-r--r--doc/devblog/day_48__direct_mode_guard_design.mdwn2
-rw-r--r--doc/devblog/day_65__wrapping_up_upgrades.mdwn2
-rw-r--r--doc/devblog/day_9__Friday_the_13th.mdwn2
4 files changed, 4 insertions, 4 deletions
diff --git a/doc/devblog/day_-4__forgetting.mdwn b/doc/devblog/day_-4__forgetting.mdwn
index 9cec51475..a37b32e33 100644
--- a/doc/devblog/day_-4__forgetting.mdwn
+++ b/doc/devblog/day_-4__forgetting.mdwn
@@ -72,7 +72,7 @@ feature.
to handle this case, too..
* For some reason the automatic transitioning code triggers
- a "(recovery from race)" commit. This is certianly a bug somewhere,
+ a "(recovery from race)" commit. This is certainly a bug somewhere,
because you can't have a race with only 1 participant.
----
diff --git a/doc/devblog/day_48__direct_mode_guard_design.mdwn b/doc/devblog/day_48__direct_mode_guard_design.mdwn
index bc2dbe316..c047e7f75 100644
--- a/doc/devblog/day_48__direct_mode_guard_design.mdwn
+++ b/doc/devblog/day_48__direct_mode_guard_design.mdwn
@@ -3,7 +3,7 @@ Preventing a stray `git commit -a` or `git add` doing bad things in a
direct mode repository seems increasingly important.
First, considered moving `.git`, so git won't know it's a git repository.
-This doesn't seem *too* hard to do, but there will certianly be unexpected
+This doesn't seem *too* hard to do, but there will certainly be unexpected
places that assume `.git` is the directory name.
I dislike it more and more as I think about it though, because it moves
diff --git a/doc/devblog/day_65__wrapping_up_upgrades.mdwn b/doc/devblog/day_65__wrapping_up_upgrades.mdwn
index b5bb62d6d..2c3816f0a 100644
--- a/doc/devblog/day_65__wrapping_up_upgrades.mdwn
+++ b/doc/devblog/day_65__wrapping_up_upgrades.mdwn
@@ -1,5 +1,5 @@
[[!img assistant/upgradecomplete.png]]
Upgrades are fully working on Linux. OSX code is written but intested and I
-thought of one bug it certianly has on my evening walk. Probably another
+thought of one bug it certainly has on my evening walk. Probably another
hour's work left later this evening to finsh it off.
diff --git a/doc/devblog/day_9__Friday_the_13th.mdwn b/doc/devblog/day_9__Friday_the_13th.mdwn
index b8fe4bc19..77d9039eb 100644
--- a/doc/devblog/day_9__Friday_the_13th.mdwn
+++ b/doc/devblog/day_9__Friday_the_13th.mdwn
@@ -10,7 +10,7 @@ But, I got distracted chasing down some bugs on Windows. These were
quite ugly; more direct mode mapping breakage which resulted in
files not being accessible. Also fsck on Windows failed to detect and fix
the problem. All fixed now. (If you use git-annex on Windows, you should
-certianly upgrade and run `git annex fsck`.)
+certainly upgrade and run `git annex fsck`.)
As with most bugs in the Windows port, the underlying cause turned out to
be stupid: `isSymlink` always returned False on Windows. Which makes sense