diff mbox

usb: Fix typo in documentation

Message ID 20161207123959.4565-1-fziglio@redhat.com
State New
Headers show

Commit Message

Frediano Ziglio Dec. 7, 2016, 12:39 p.m. UTC
Signed-off-by: Frediano Ziglio <fziglio@redhat.com>
---
 docs/usb-storage.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Eric Blake Dec. 7, 2016, 3:53 p.m. UTC | #1
On 12/07/2016 06:39 AM, Frediano Ziglio wrote:
> Signed-off-by: Frediano Ziglio <fziglio@redhat.com>

Mentioning 'simliar' in the commit message would make it easier to pick
out which word is being changed, when not using a colored-by-word diff.

This patch can also go through qemu-trivial (cc'd).

Reviewed-by: Eric Blake <eblake@redhat.com>

> ---
>  docs/usb-storage.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/docs/usb-storage.txt b/docs/usb-storage.txt
> index fbc1f2e..551af6f 100644
> --- a/docs/usb-storage.txt
> +++ b/docs/usb-storage.txt
> @@ -34,7 +34,7 @@ with tree logical units:
>  Number three emulates the classic bulk-only transport protocol too.
>  It's called "usb-bot".  It shares most code with "usb-storage", and
>  the guest will not be able to see the difference.  The qemu command
> -line interface is simliar to usb-uas though, i.e. no automatic scsi
> +line interface is similar to usb-uas though, i.e. no automatic scsi
>  disk creation.  It also features support for up to 16 LUNs.  The LUN
>  numbers must be continuous, i.e. for three devices you must use 0+1+2.
>  The 0+1+5 numbering from the "usb-uas" example isn't going to work
>
diff mbox

Patch

diff --git a/docs/usb-storage.txt b/docs/usb-storage.txt
index fbc1f2e..551af6f 100644
--- a/docs/usb-storage.txt
+++ b/docs/usb-storage.txt
@@ -34,7 +34,7 @@  with tree logical units:
 Number three emulates the classic bulk-only transport protocol too.
 It's called "usb-bot".  It shares most code with "usb-storage", and
 the guest will not be able to see the difference.  The qemu command
-line interface is simliar to usb-uas though, i.e. no automatic scsi
+line interface is similar to usb-uas though, i.e. no automatic scsi
 disk creation.  It also features support for up to 16 LUNs.  The LUN
 numbers must be continuous, i.e. for three devices you must use 0+1+2.
 The 0+1+5 numbering from the "usb-uas" example isn't going to work