aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/Truncated_file_transferred_via_S3
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/bugs/Truncated_file_transferred_via_S3
parent59f2984911e5761c3d7cc6b2c9ed3deb58a62a74 (diff)
doc: perl -p -i -e s/certianly/certainly/
Diffstat (limited to 'doc/bugs/Truncated_file_transferred_via_S3')
-rw-r--r--doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment
index 6a05b9750..f3583d31b 100644
--- a/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment
+++ b/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment
@@ -6,5 +6,5 @@
content="""
Did you get a chance to run `git annex fsck` on the file? I'd hope it would detect this problem.
-It's certianly possible for data to get corrupted somehow in transit. git-annex does not check that it got the expected contents until a fsck happens.
+It's certainly possible for data to get corrupted somehow in transit. git-annex does not check that it got the expected contents until a fsck happens.
"""]]