[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-trivial] [Qemu-devel] [PATCH] slirp: Fix spelling in comment (
From: |
Eric Blake |
Subject: |
Re: [Qemu-trivial] [Qemu-devel] [PATCH] slirp: Fix spelling in comment (enought -> enough, insure -> ensure) |
Date: |
Thu, 27 Sep 2012 13:13:10 -0600 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 |
On 09/27/2012 12:57 PM, Stefan Weil wrote:
> Signed-off-by: Stefan Weil <address@hidden>
> ---
>
> As a non native speaker, I feel that 'ensure' is better here than 'insure'.
> Could a native speaker please confirm that?
As a US speaker, I've seen both words used interchangeably. I also
checked dictionary.com, where both words imply a guarantee, but 'insure'
has a connotation of a guarantee against loss (think insurance policy)
while 'ensure' tends to be used in most other situations. That is, I am
in favor of this spelling change for connotation reasons. But as Peter
pointed out, the sentence has more problems than just a spelling choice.
> - * For the error advice packets must first insure that the
> - * packet is large enought to contain the returned ip header.
> + * For the error advice packets must first ensure that the
> + * packet is large enough to contain the returned ip header.
> * Only then can we do the check to see if 64 bits of packet
> * data have been returned, since we need to check the returned
> * ip header length.
>
--
Eric Blake address@hidden +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature