Version: (using KDE Devel) Installed from: Compiled sources No real typo this time, but a style question: In index.docbook:101, 124, 136, 164, "the user" is used whereas the rest of the documentation refers to "you". I'd like to see this changed to have "you" consistently over KDE.
SVN commit 498709 by mhunter: Fix consistency: the user -> you CCBUG=120148 M +15 -15 index.docbook --- trunk/KDE/kdebase/doc/kcontrol/kcmaccess/index.docbook #498708:498709 @@ -100,7 +100,7 @@ <term><guilabel>Use Sticky Keys</guilabel></term> <listitem> <para> -If this option is enabled, the user can press and release the &Shift;, +If this option is enabled, you can press and release the &Shift;, &Alt; or &Ctrl; keys, and then press another key to get a key combo (example: <keycombo action="simul">&Ctrl; &Alt; <keycap>Del</keycap></keycombo> could be done with &Ctrl; then &Alt; @@ -110,8 +110,8 @@ <para> Also in this section is a check box labeled <guilabel>Lock Sticky Keys</guilabel>. If this check box is enabled, the &Alt;, &Ctrl; -and &Shift; keys stay <quote>selected</quote> until they are -<quote>de-selected</quote> by the user. +and &Shift; keys stay <quote>selected</quote> until you +<quote>de-selected</quote> them. </para> <para> @@ -121,10 +121,10 @@ <varlistentry> <term>With <guilabel>Lock Sticky Keys</guilabel> disabled:</term> <listitem> -<para>The user presses the &Shift; key, then presses the -<keycap>F</keycap> key. The computer translates this into <keycombo -action="simul">&Shift;<keycap>F</keycap></keycombo>. Now if the user -types a <keycap>p</keycap>, the computer interprets this as the letter p +<para>If you press the &Shift; key then press the +<keycap>F</keycap> key, the computer interprets this as <keycombo +action="simul">&Shift;<keycap>F</keycap></keycombo>. Now if you +type a <keycap>p</keycap>, the computer interprets this as the letter p (no shift). </para> </listitem> @@ -134,10 +134,10 @@ <term>With <guilabel>Lock Sticky Keys</guilabel> enabled:</term> <listitem> <para> -The user presses the &Shift; key <emphasis>twice</emphasis>, then presses the <keycap>F</keycap> key. -The computer translates this into <keycombo -action="simul">&Shift;<keycap>F</keycap></keycombo>. Now if the user -types a <keycap>p</keycap>, the computer interprets this as the letter P +If you press the &Shift; key <emphasis>twice</emphasis> then press the <keycap>F</keycap> key, +the computer interprets this as <keycombo +action="simul">&Shift;<keycap>F</keycap></keycombo>. Now if you +type a <keycap>p</keycap>, the computer interprets this as the letter P (<keycombo action="simul">&Shift;<keycap>P</keycap></keycombo>). To de-select the &Shift; key, press it again. </para> @@ -151,8 +151,8 @@ <term><guilabel>Slow keys</guilabel></term> <listitem> <para> -If this option is enabled, the user must hold the key down for a -specified period of time (adjustable with the slider) before the +If this option is enabled, you must hold the key down for a +specified length of time (adjustable with the slider) before the keystroke will be accepted. This helps prevent accidental key strokes. </para> </listitem> @@ -162,9 +162,9 @@ <term><guilabel>Bounce keys</guilabel></term> <listitem> <para> -If this option is enabled, the user must wait a specified delay +If this option is enabled, you must wait for a specified length of time (configurable with the slider) before the next key press can be -accepted. This prevents accidental multiple key strokes. +accepted. This prevents accidental multiple key strokes. </para> </listitem> </varlistentry>
looks like malcolm fixed this bug but didn't close the bug report.