On Thu, 29 Jun 2006 13:40:02 +0200
Paolo Ornati <[email protected]> wrote:
> Remove every (hopefully) duplicated word under Documentation/.
>
> Examples:
> "and and" --> "and"
> "in in" --> "in"
> ...
I've re-read the whole thing and found these, please comment:
--------
diff --git a/Documentation/DocBook/videobook.tmpl b/Documentation/DocBook/videobook.tmpl
index fdff984..d19ccee 100644
--- a/Documentation/DocBook/videobook.tmpl
+++ b/Documentation/DocBook/videobook.tmpl
@@ -322,7 +322,7 @@ static int radio_ioctl(struct video_devi
</entry>
</row><row>
<entry>type</entry><entry>This reports the capabilities of the device, and
- matches the field we filled in in the struct
+ matches the field we filled in the struct
video_device when registering.</entry>
------------
I'm not 100% sure of this.
-----------------
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 0d189c9..9adc500 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -106,7 +106,7 @@ Do not modify the syntax of boot loader
need or coordination with <Documentation/i386/boot.txt>.
Note that ALL kernel parameters listed below are CASE SENSITIVE, and that
-a trailing = on the name of any parameter states that that parameter will
+a trailing = on the name of any parameter states that parameter will
be entered as an environment variable, whereas its absence indicates that
it will appear as a kernel argument readable via /proc/cmdline by programs
running once the system is up.
-------------------------------
The old one looks correct.
---------------------------------------------
Life isn't quite as simple as it may appear above, however: for while the
-caches are expected to be coherent, there's no guarantee that that coherency
+caches are expected to be coherent, there's no guarantee that coherency
will be ordered. This means that whilst changes made on one CPU will
eventually become visible on all CPUs, there's no guarantee that they will
become apparent in the same order on those other CPUs.
---------------------------------------------------
Not sure.
-----------------------------------------
--- a/Documentation/networking/pt.txt
+++ b/Documentation/networking/pt.txt
@@ -25,7 +25,7 @@ recompile it.
The driver is not real good at the moment for finding the card. You can
'help' it by changing the order of the potential addresses in the structure
-found in the pt_init() function so the address of where the card is is put
+found in the pt_init() function so the address of where the card is put
first.
------------------------------------------
The old one looks correct.
--
Paolo Ornati
Linux 2.6.17.1 on x86_64
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
