X-Git-Url: http://git.nikiroo.be/?p=gofetch.git;a=blobdiff_plain;f=test%2Fexpected%2FLWN%2F0000764057.header;fp=test%2Fexpected%2FLWN%2F0000764057.header;h=5b71d2756b2ad6bf1a71c2f834fac7b8f61943f6;hp=eb103f9c34b9d7db609b0ac58a4ebf66806c5ee1;hb=3367f6256b5143b7cba2a61de36e74f389a5f379;hpb=b389651b0012a7ba1ff30d164958e155688ac216

diff --git a/test/expected/LWN/0000764057.header b/test/expected/LWN/0000764057.header
index eb103f9..5b71d27 100644
--- a/test/expected/LWN/0000764057.header
+++ b/test/expected/LWN/0000764057.header
@@ -3,7 +3,7 @@ i  [Kernel] Sep 4, 2018 0:15 UTC (Tue) (corbet)
 i
 i    It  is  common  for kernel code to generate unique integers for
 i    identifiers.  When  one plugs in a flash drive, it will show up
-i    as  /dev/sdN;  that  N (a letter derived from a number) must be
+i    as  /dev/sdN  ; that N (a letter derived from a number) must be
 i    generated  in  the  kernel, and it should not already be in use
 i    for  another  drive or unpleasant things will happen. One might
 i    think  that  generating  such  numbers would not be a difficult