diff options
| author | John Bampton <jbampton@gmail.com> | 2021-02-17 01:48:21 +0000 |
|---|---|---|
| committer | Emmanuel Odeke <emmanuel@orijtech.com> | 2021-02-24 04:11:43 +0000 |
| commit | 6ba4a300d894b33fd8bf076dec08a5e3245d3a2c (patch) | |
| tree | 08b44d533c3f2cc4245f9eb3c9459f66d3760eea /src/internal | |
| parent | 43652dc46f770253b3603f47165b1568b439b0b5 (diff) | |
| download | go-6ba4a300d894b33fd8bf076dec08a5e3245d3a2c.tar.gz go-6ba4a300d894b33fd8bf076dec08a5e3245d3a2c.zip | |
docs: fix spelling
Change-Id: Ib689e5793d9cb372e759c4f34af71f004010c822
GitHub-Last-Rev: d63798388e5dcccb984689b0ae39b87453b97393
GitHub-Pull-Request: golang/go#44259
Reviewed-on: https://go-review.googlesource.com/c/go/+/291949
Reviewed-by: Emmanuel Odeke <emmanuel@orijtech.com>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Trust: Matthew Dempsky <mdempsky@google.com>
Trust: Robert Griesemer <gri@golang.org>
Diffstat (limited to 'src/internal')
| -rw-r--r-- | src/internal/poll/copy_file_range_linux.go | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/internal/poll/copy_file_range_linux.go b/src/internal/poll/copy_file_range_linux.go index 01b242a4ea..5b9e5d4020 100644 --- a/src/internal/poll/copy_file_range_linux.go +++ b/src/internal/poll/copy_file_range_linux.go @@ -78,7 +78,7 @@ func CopyFileRange(dst, src *FD, remain int64) (written int64, handled bool, err // Go supports Linux >= 2.6.33, so the system call // may not be present. // - // If we see ENOSYS, we have certainly not transfered + // If we see ENOSYS, we have certainly not transferred // any data, so we can tell the caller that we // couldn't handle the transfer and let them fall // back to more generic code. @@ -91,13 +91,13 @@ func CopyFileRange(dst, src *FD, remain int64) (written int64, handled bool, err // Prior to Linux 5.3, it was not possible to // copy_file_range across file systems. Similarly to // the ENOSYS case above, if we see EXDEV, we have - // not transfered any data, and we can let the caller + // not transferred any data, and we can let the caller // fall back to generic code. // // As for EINVAL, that is what we see if, for example, // dst or src refer to a pipe rather than a regular // file. This is another case where no data has been - // transfered, so we consider it unhandled. + // transferred, so we consider it unhandled. // // If src and dst are on CIFS, we can see EIO. // See issue #42334. |