summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-08-27 06:10:47 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-08-27 06:10:47 +0000
commit1056202b48255c39e08a1af815cac44f3be5fa09 (patch)
tree30c434c4baa36599ff4a871776e2b0f8f2cdb7bb
parent709de3d6217bdd470ce1e1840375fe7f7bdeb2d4 (diff)
downloadcurl-1056202b48255c39e08a1af815cac44f3be5fa09.tar.gz
spell! (most of it fixed by Tor Arntsen)
-rw-r--r--lib/README.curl_off_t8
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/README.curl_off_t b/lib/README.curl_off_t
index 52eb12bfd..923b2774c 100644
--- a/lib/README.curl_off_t
+++ b/lib/README.curl_off_t
@@ -12,7 +12,7 @@ Transition from < 7.19.0 to >= 7.19.0
Applications that used libcurl before 7.19.0 that are rebuilt with a libcurl
that is 7.19.0 or later may or may not have to worry about anything of
this. We have made a significant effort to make the transition really seamless
-and transparant.
+and transparent.
You have have to take notice if you are in one of the following situations:
@@ -33,15 +33,15 @@ Benefits
This new way has several benefits:
o Platforms without LFS support can still use libcurl to do >32 bit file
- transfers and range operations etc as long as they have >32 bit datatypes
+ transfers and range operations etc as long as they have >32 bit data-types
supported.
o Applications will no longer easily build with the curl_off_t size
mismatched, which has been a very frequent (and annoying) problem with
libcurl <= 7.18.2
-Historicly
-----------
+Historically
+------------
Previously, before 7.19.0, the curl_off_t type would be rather strongly
connected to the size of the system off_t type, where currently curl_off_t is