docs: fix typos

docs/ALTSVC.md

@@ -27,7 +27,7 @@ space separated fields.
 4. The ALPN id for the destination host
 5. The host name for the destination host
 6. The host number for the destination host
-7. The expiration date and time of this entry withing double quotes. The date format is "YYYYMMDD HH:MM:SS" and the time zone is GMT.
+7. The expiration date and time of this entry within double quotes. The date format is "YYYYMMDD HH:MM:SS" and the time zone is GMT.
 8. Boolean (1 or 0) if "persist" was set for this entry
 9. Integer priority value (not currently used)
 

docs/INSTALL.md

@@ -307,7 +307,7 @@ for `aarch64` and API level 29:
     export RANLIB=$TOOLCHAIN/bin/aarch64-linux-android-ranlib
     export STRIP=$TOOLCHAIN/bin/aarch64-linux-android-strip
 
-When building on Linux or targetting other API levels or architectures, you need
+When building on Linux or targeting other API levels or architectures, you need
 to adjust those variables accordingly. After that you can build curl like this:
 
     ./configure --host aarch64-linux-android --with-pic --disable-shared

docs/KNOWN_BUGS

@@ -339,7 +339,7 @@ problems may have been fixed or changed somewhat since this was written!
 
 5.1 USE_UNIX_SOCKETS on Windows
 
- Due to incorrect CMake checks for the presense of the feature, it will never
+ Due to incorrect CMake checks for the presence of the feature, it will never
  be enabled for windows in a cmake build.
 
  See https://github.com/curl/curl/issues/4040

docs/PARALLEL-TRANSFERS.md

@@ -18,7 +18,7 @@ completely different than the regular one used for each single transfer.
 
  o percent download (if known, which means *all* transfers need to have a
    known size)
- o precent upload (if known, with the same caveat as for download)
+ o percent upload (if known, with the same caveat as for download)
  o total amount of downloaded data
  o total amount of uploaded data
  o number of transfers to perform

docs/TODO

@@ -813,7 +813,7 @@ that doesn't exist on the server, just like --ftp-create-dirs.
 
  The SFTP code in libcurl checks the file size *before* a transfer starts and
  then proceeds to transfer exactly that amount of data. If the remote file
- grows while the tranfer is in progress libcurl won't notice and will not
+ grows while the transfer is in progress libcurl won't notice and will not
  adapt. The OpenSSH SFTP command line tool does and libcurl could also just
  attempt to download more to see if there is more to get...