[kde-doc-english] [kate/KDE/4.12] doc/kate: Correcting typos and grammar, making use of hyphens more consistent, improving the meaning of sentences, using entities, and improving punctuation.
Burkhard Lück
lueck at hube-lueck.de
Tue Dec 24 10:07:26 UTC 2013
Git commit 3596241e4846261bbd3084ccdccf40f5e00a1b12 by Burkhard Lück, on behalf of David Palser.
Committed on 27/11/2013 at 16:54.
Pushed by lueck into branch 'KDE/4.12'.
Correcting typos and grammar, making use of hyphens more consistent, improving the meaning of sentences, using entities, and improving punctuation.
(cherry picked from commit 0b0e7f6f81ad3a166910a9fa35a52aee6a537e18)
backport to 4.12.1
M +27 -27 doc/kate/configuring.docbook
M +43 -43 doc/kate/highlighting.docbook
http://commits.kde.org/kate/3596241e4846261bbd3084ccdccf40f5e00a1b12
diff --git a/doc/kate/configuring.docbook b/doc/kate/configuring.docbook
index 7196721..2ce621c 100644
--- a/doc/kate/configuring.docbook
+++ b/doc/kate/configuring.docbook
@@ -44,8 +44,8 @@ document.</para></listitem>
</varlistentry>
</variablelist>
-<para>The embedded terminal is using the configuration defined in the
-&systemsettings;, and may be configured by clicking the
+<para>The embedded terminal uses the configuration defined in the
+&systemsettings;, and may also be configured by clicking the
<mousebutton>right</mousebutton> mouse button to display a context menu.</para>
</sect1>
@@ -98,7 +98,7 @@ the right.</para>
from outside the application whenever the main window receives input focus.
You will be able to deal with several modified files at once, you
can reload, save or discard changed files in groups.</para>
-<para>If not enabled, &kate; will prompt you for action when a externally
+<para>If not enabled, &kate; will prompt you for action when an externally
modified file receives focus within the application.</para>
</listitem>
</varlistentry>
@@ -125,7 +125,7 @@ will be used if the document is unchanged when reopened.</para></listitem>
<term><anchor id="config-general-delete-meta-information-after"/>
<guilabel>Delete unused meta information after</guilabel></term>
<listitem><para>Set the maximum number of days to keep meta information
-for unopen files. This helps keeping the database of meta information
+for previously opened files. This helps keeping the database of meta information
reasonably sized.</para></listitem>
</varlistentry>
@@ -170,7 +170,7 @@ linkend="command-line-options">command line</link>.</para>
<varlistentry>
<term><guilabel>Start new session</guilabel></term>
<listitem><para>With this option, &kate; will start a new, unnamed session
-when you start it.</para></listitem>
+when you start the application.</para></listitem>
</varlistentry>
<varlistentry>
<term><guilabel>Load last-used session</guilabel></term>
@@ -190,7 +190,7 @@ frequently.</para></listitem>
</varlistentry><!-- /startup behavior -->
</variablelist>
-<para>The changes to the session data (opened files and if enabled,
+<para>Any changes to the session data (opened files and, if enabled,
window configuration) will always be saved.</para>
</sect2>
@@ -199,11 +199,11 @@ window configuration) will always be saved.</para>
<title>Plugins</title>
<para>This page provides a list of installed plugins for the &kate;
-application. Each plug-in is represented with its name and a short description.
-You can check the checkbox with an item to enable the plug-in it represents.
+application. Each plugin is represented with its name and a short description.
+You can check the checkbox with an item to enable the plugin it represents.
</para>
-<para>If a plug-in provides configuration options, a section to access those
+<para>If a plugin provides configuration options, a section to access those
will appear as a child of this page.</para>
<para>For more information about the available plugins, see
@@ -287,7 +287,7 @@ so the calling program is aware you have finished editing the file.</para></list
<title>Configuring With Document Variables</title>
<para>&kappname; variables is katepart's implementation of document variables, similar
-to emacs and vi modelines. In katepart, the lines have the following format:
+to &Emacs; and vi modelines. In katepart, the lines have the following format:
<userinput>kate: VARIABLENAME VALUE; [ VARIABLENAME VALUE; ... ]</userinput>
@@ -330,7 +330,7 @@ the plugin's documentation.</para>
<listitem><para>Settings made during editing from menu or command line.</para></listitem>
</itemizedlist>
-As you see, document variables are only overriden by changes made at runtime.
+As you can see, document variables are only overridden by changes made at runtime.
Whenever a document is saved, the document variables are reread, and will
overwrite changes made using menu items or the command line.</para>
@@ -387,9 +387,9 @@ on or off.</para></listitem>
<varlistentry id="variable-byte-order-marker">
<term><cmdsynopsis><command>bom | byte-order-marker</command><arg>BOOL</arg></cmdsynopsis></term>
-<listitem><para>Enable/disable the byte order marker when saving files in unicode format
+<listitem><para>Enable/disable the byte order marker when saving files in Unicode format
(utf8, utf16, utf32).</para>
-<para>Since: Kate 3.4 (KDE 4.4)</para></listitem>
+<para>Since: &kate; 3.4 (&kde; 4.4)</para></listitem>
</varlistentry>
<varlistentry id="variable-encoding">
@@ -397,7 +397,7 @@ on or off.</para></listitem>
<listitem><para>Set the encoding used for loading or saving the file.
As the variables in the document will be read after loading, this impacts only the saving.
If you place it in a <filename>.kateconfig</filename> file, it will have an effect for the loading, too.</para>
-<para>Since: Kate 3.10 (KDE 4.10)</para></listitem>
+<para>Since: &kate; 3.10 (&kde; 4.10)</para></listitem>
</varlistentry>
<varlistentry id="variable-bracket-highlight-color">
@@ -410,14 +410,14 @@ something that can be evaluated to a valid color, for example <userinput>#ff0000
<varlistentry id="variable-current-line-color">
<term><cmdsynopsis><command>current-line-color</command><arg>STRING</arg></cmdsynopsis></term>
<listitem><para>Set the color for the current line. The value must be
-something that can be evaluated to a valid color, for example <userinput>#ff0000</userinput>
+something that can be evaluated to a valid color, for example <userinput>#ff0000</userinput>.
</para></listitem>
</varlistentry>
<varlistentry id="variable-default-dictionary">
<term><cmdsynopsis><command>default-dictionary</command><arg>STRING</arg></cmdsynopsis></term>
-<listitem><para>Sets the default dictionary used for spell checking.</para>
-<para>Since: Kate 3.4 (KDE 4.4)</para></listitem>
+<listitem><para>Sets the default dictionary used for spellchecking.</para>
+<para>Since: &kate; 3.4 (&kde; 4.4)</para></listitem>
</varlistentry>
<varlistentry id="variable-dynamic-word-wrap">
@@ -429,7 +429,7 @@ off.</para></listitem>
<varlistentry id="variable-end-of-line">
<term><cmdsynopsis><command>eol | end-of-line</command><arg>STRING</arg></cmdsynopsis></term>
<listitem><para>Set the end of line mode. Valid settings are
-<userinput>unix</userinput>, <userinput>mac</userinput> and <userinput>dos</userinput></para></listitem>
+<userinput>unix</userinput>, <userinput>mac</userinput> and <userinput>dos</userinput>.</para></listitem>
</varlistentry>
<varlistentry id="variable-folding-markers">
@@ -480,7 +480,7 @@ be evaluated to a valid color, for example <userinput>#ff0000</userinput>.</para
<varlistentry id="variable-indent-pasted-text">
<term><cmdsynopsis><command>indent-pasted-text</command><arg>BOOL</arg></cmdsynopsis></term>
<listitem><para>Enable/disable adjusting indentation of text pasted from the clipboard.</para>
-<para>Since: Kate 3.11 (KDE 4.11)</para></listitem>
+<para>Since: &kate; 3.11 (&kde; 4.11)</para></listitem>
</varlistentry>
<varlistentry id="variable-indent-width">
@@ -500,14 +500,14 @@ be evaluated to a valid color, for example <userinput>#ff0000</userinput>.</para
<varlistentry id="variable-mixed-indent">
<term><cmdsynopsis><command>mixed-indent</command><arg>BOOL</arg></cmdsynopsis></term>
-<listitem><para>Set mixed indentation ala Emacs on or off.</para>
-<para>Note: Deprecated since Kate 3 in KDE4. This variable is ignored, set <command>replace-tabs on;</command> instead for the future.</para></listitem>
+<listitem><para>Set mixed indentation, as with &Emacs;, on or off.</para>
+<para>Note: Deprecated since &kate; 3 in &kde;4. This variable is ignored, set <command>replace-tabs on;</command> instead for the future.</para></listitem>
</varlistentry>
<varlistentry id="variable-newline-at-eof">
<term><cmdsynopsis><command>newline-at-eof</command><arg>BOOL</arg></cmdsynopsis></term>
<listitem><para>Add an empty line at the end of the file (EOF) when saving the document.</para>
-<para>Since: &kate; 3.9 (KDE 4.9)</para></listitem>
+<para>Since: &kate; 3.9 (&kde; 4.9)</para></listitem>
</varlistentry>
<varlistentry id="variable-overwrite-mode">
@@ -524,7 +524,7 @@ on or off.</para></listitem>
<varlistentry id="variable-remove-trailing-space">
<term><cmdsynopsis><command>remove-trailing-space</command><arg>BOOL</arg></cmdsynopsis></term>
<listitem><para>Set dynamic end of line cleanup on or off.</para>
-<para>Note: Deprecated since KDE 4.10. Please use <link linkend="variable-remove-trailing-spaces">
+<para>Note: Deprecated since &kde; 4.10. Please use <link linkend="variable-remove-trailing-spaces">
remove-trailing-spaces</link> with the desired choice instead.
</para></listitem>
</varlistentry>
@@ -538,7 +538,7 @@ remove-trailing-spaces</link> with the desired choice instead.
modified lines. The modified lines are marked by the line modification system.</para></listitem>
<listitem><para><userinput>all</userinput>, <userinput>*</userinput> or <userinput>2</userinput>: remove trailing spaces in the entire document.</para></listitem>
</itemizedlist>
-<para>Since: KDE 4.10. This deprecates the options <userinput>remove-trailing-space</userinput> and <userinput>replace-trailing-space-save</userinput>.
+<para>Since: &kde; 4.10. This deprecates the options <userinput>remove-trailing-space</userinput> and <userinput>replace-trailing-space-save</userinput>.
</para></listitem>
</varlistentry>
@@ -555,7 +555,7 @@ modified lines. The modified lines are marked by the line modification system.</
<varlistentry id="variable-replace-trailing-space-save">
<term><cmdsynopsis><command>replace-trailing-space-save</command><arg>BOOL</arg></cmdsynopsis></term>
<listitem><para>Set end of line cleanup on save on or off.</para>
-<para>Note: Deprecated since KDE 4.10. Please use <link linkend="variable-remove-trailing-spaces">
+<para>Note: Deprecated since &kde; 4.10. Please use <link linkend="variable-remove-trailing-spaces">
remove-trailing-spaces</link> with the desired choice instead.
</para></listitem>
</varlistentry>
@@ -586,7 +586,7 @@ on or off.</para></listitem>
<varlistentry id="variable-space-indent">
<term><cmdsynopsis><command>space-indent</command><arg>BOOL</arg></cmdsynopsis></term>
<listitem><para>Set indentation with spaces on or off.</para>
-<para>Note: Deprecated since Kate 3 in KDE4. Mixed indentation is the default behavior.
+<para>Note: Deprecated since &kate; 3 in &kde;4. Mixed indentation is the default behavior.
Set <command>replace-tabs on;</command> to achieve space-only indentation.</para></listitem>
</varlistentry>
@@ -603,7 +603,7 @@ Set <command>replace-tabs on;</command> to achieve space-only indentation.</para
<varlistentry id="variable-undo-steps">
<term><cmdsynopsis><command>undo-steps</command><arg>INT</arg></cmdsynopsis></term>
<listitem><para>Set the number of undo steps to remember.</para>
-<para>Note: Deprecated since Kate 3 in KDE4. This variable is ignored. The maximal count of undo steps is unlimited.</para></listitem>
+<para>Note: Deprecated since &kate; 3 in &kde;4. This variable is ignored. The maximal count of undo steps is unlimited.</para></listitem>
</varlistentry>
<varlistentry id="variable-word-wrap-column">
diff --git a/doc/kate/highlighting.docbook b/doc/kate/highlighting.docbook
index 94b51e3..7706887 100644
--- a/doc/kate/highlighting.docbook
+++ b/doc/kate/highlighting.docbook
@@ -145,7 +145,7 @@ specific data in rules.</para>
<title>Context Styles and Keywords</title>
<para>In some programming languages, integer numbers are treated
-differently than floating point ones by the compiler (the program that
+differently from floating point ones by the compiler (the program that
converts the source code to a binary executable), and there may be
characters having a special meaning within a quoted string. In such
cases, it makes sense to render them differently from the surroundings
@@ -158,8 +158,8 @@ different rendering.</para>
cover the concepts of the format it is used for.</para>
<para>In many formats, there are lists of words that represent a
-specific concept. For example in programming languages, the control
-statements is one concept, data type names another, and built in
+specific concept. For example, in programming languages, control
+statements are one concept, data type names another, and built in
functions of the language a third. The &kappname; Syntax Highlighting
System can use such lists to detect and mark words in the text to
emphasize concepts of the text formats.</para>
@@ -177,17 +177,17 @@ for special treatment, the colors used are the same. This is because
the individual syntax definitions.</para>
<para>This makes it easy to recognize similar concepts in different
-text formats. For example comments are present in almost any
+text formats. For example, comments are present in almost any
programming, scripting or markup language, and when they are rendered
using the same style in all languages, you do not have to stop and
think to identify them within the text.</para>
<tip>
<para>All styles in a syntax definition use one of the default
-styles. A few syntax definitions use more styles that there are
+styles. A few syntax definitions use more styles than there are
defaults, so if you use a format often, it may be worth launching the
-configuration dialog to see if some concepts are using the same
-style. For example there is only one default style for strings, but as
+configuration dialog to see if some concepts use the same
+style. For example, there is only one default style for strings, but as
the Perl programming language operates with two types of strings, you
can enhance the highlighting by configuring those to be slightly
different. All <link linkend="kate-highlight-default-styles">available default styles</link>
@@ -209,7 +209,7 @@ format. Based on a small example it will describe the main components
and their meaning and usage. The next section will go into detail with
the highlight detection rules.</para>
-<para>The formal definition, aka the <acronym>DTD</acronym> is stored
+<para>The formal definition, also known as the <acronym>DTD</acronym>, is stored
in the file <filename>language.dtd</filename> which should be
installed on your system in the folder
<filename>$<envar>KDEDIR</envar>/share/apps/katepart/syntax</filename>.
@@ -236,17 +236,17 @@ Available attributes are:</term>
<para>Required attributes:</para>
<para><userinput>name</userinput> sets the name of the language. It appears in the menus and dialogs afterwards.</para>
<para><userinput>section</userinput> specifies the category.</para>
-<para><userinput>extensions</userinput> defines file extensions, like "*.cpp;*.h"</para>
+<para><userinput>extensions</userinput> defines file extensions, such as "*.cpp;*.h"</para>
<para>Optional attributes:</para>
-<para><userinput>mimetype</userinput> associates files &MIME; Type based.</para>
+<para><userinput>mimetype</userinput> associates files &MIME; type.</para>
<para><userinput>version</userinput> specifies the current version of the definition file.</para>
<para><userinput>kateversion</userinput> specifies the latest supported &kappname; version.</para>
<para><userinput>casesensitive</userinput> defines, whether the keywords are case sensitive or not.</para>
<para><userinput>priority</userinput> is necessary if another highlight definition file uses the same extensions. The higher priority will win.</para>
<para><userinput>author</userinput> contains the name of the author and his email-address.</para>
-<para><userinput>license</userinput> contains the license, usually LGPL, Artistic, GPL and others.</para>
-<para><userinput>hidden</userinput> defines, whether the name should appear in &kappname;'s menus.</para>
+<para><userinput>license</userinput> contains the license, usually LGPL, Artistic, GPL or others.</para>
+<para><userinput>hidden</userinput> defines whether the name should appear in &kappname;'s menus.</para>
<para>So the next line may look like this:</para>
<programlisting>
<language name="C++" version="1.00" kateversion="2.4" section="Sources" extensions="*.cpp;*.h" />
@@ -307,11 +307,11 @@ about keywords, code folding, comments and indentation.</term>
<listitem>
<para>The <userinput>comment</userinput> section defines with what
string a single line comment is introduced. You also can define a
-multiline comments using <emphasis>multiLine</emphasis> with the
+multiline comment using <emphasis>multiLine</emphasis> with the
additional attribute <emphasis>end</emphasis>. This is used if the
user presses the corresponding shortcut for <emphasis>comment/uncomment</emphasis>.</para>
<para>The <userinput>keywords</userinput> section defines whether
-keyword lists are casesensitive or not. Other attributes will be
+keyword lists are case sensitive or not. Other attributes will be
explained later.</para>
<programlisting>
<general>
@@ -337,19 +337,19 @@ itemDatas, keywords, comments, code folding and indentation.</para>
<variablelist>
<varlistentry>
-<term>The element <userinput>context</userinput> belongs into the group
+<term>The element <userinput>context</userinput> belongs in the group
<userinput>contexts</userinput>. A context itself defines context specific
-rules like what should happen if the highlight system reaches the end of a
+rules such as what should happen if the highlight system reaches the end of a
line. Available attributes are:</term>
<listitem>
-<para><userinput>name</userinput> the context name. Rules will use this name
+<para><userinput>name</userinput> states the context name. Rules will use this name
to specify the context to switch to if the rule matches.</para>
<para><userinput>lineEndContext</userinput> defines the context the highlight
system switches to if it reaches the end of a line. This may either be a name
of another context, <userinput>#stay</userinput> to not switch the context
-(⪚. do nothing) or <userinput>#pop</userinput> which will cause to leave this
+(⪚. do nothing) or <userinput>#pop</userinput> which will cause it to leave this
context. It is possible to use for example <userinput>#pop#pop#pop</userinput>
to pop three times, or even <userinput>#pop#pop!OtherContext</userinput> to pop
two times and switch to the context named <userinput>OtherContext</userinput>.</para>
@@ -370,12 +370,12 @@ documents for example. Default: <emphasis>false</emphasis>.</para>
<varlistentry>
<term>The element <userinput>itemData</userinput> is in the group
<userinput>itemDatas</userinput>. It defines the font style and colors.
-So it is possible to define your own styles and colors, however we
-recommend to stick to the default styles if possible so that the user
+So it is possible to define your own styles and colors. However, we
+recommend you stick to the default styles if possible so that the user
will always see the same colors used in different languages. Though,
sometimes there is no other way and it is necessary to change color
and font attributes. The attributes name and defStyleNum are required,
-the other optional. Available attributes are:</term>
+the others are optional. Available attributes are:</term>
<listitem>
<para><userinput>name</userinput> sets the name of the itemData.
@@ -389,8 +389,8 @@ Available default styles are explained in detail later.</para>
<para><userinput>italic</userinput> if <emphasis>true</emphasis>, the text will be italic.</para>
<para><userinput>bold</userinput> if <emphasis>true</emphasis>, the text will be bold.</para>
<para><userinput>underline</userinput> if <emphasis>true</emphasis>, the text will be underlined.</para>
-<para><userinput>strikeout</userinput> if <emphasis>true</emphasis>, the text will be stroked out.</para>
-<para><userinput>spellChecking</userinput> if <emphasis>true</emphasis>, the text will be spell checked, otherwise it will be ignored during spell check.</para>
+<para><userinput>strikeout</userinput> if <emphasis>true</emphasis>, the text will be struck out.</para>
+<para><userinput>spellChecking</userinput> if <emphasis>true</emphasis>, the text will be spellchecked.</para>
</listitem>
</varlistentry>
@@ -402,9 +402,9 @@ Available default styles are explained in detail later.</para>
<listitem>
<para><userinput>casesensitive</userinput> may be <emphasis>true</emphasis>
or <emphasis>false</emphasis>. If <emphasis>true</emphasis>, all keywords
-are matched casesensitive</para>
+are matched case sensitively.</para>
<para><userinput>weakDeliminator</userinput> is a list of characters that
-do not act as word delimiters. For example the dot <userinput>'.'</userinput>
+do not act as word delimiters. For example, the dot <userinput>'.'</userinput>
is a word delimiter. Assume a keyword in a <userinput>list</userinput> contains
a dot, it will only match if you specify the dot as a weak delimiter.</para>
<para><userinput>additionalDeliminator</userinput> defines additional delimiters.</para>
@@ -450,7 +450,7 @@ Available attributes are:</term>
<listitem>
<para><userinput>indentationsensitive</userinput> if <emphasis>true</emphasis>, the code folding markers
-will be added indentation based, like in the scripting language Python. Usually you
+will be added indentation based, as in the scripting language Python. Usually you
do not need to set it, as it defaults to <emphasis>false</emphasis>.</para>
</listitem>
</varlistentry>
@@ -458,8 +458,8 @@ do not need to set it, as it defaults to <emphasis>false</emphasis>.</para>
<varlistentry>
<term>The element <userinput>indentation</userinput> in the group
-<userinput>general</userinput> defines which indenter will be used, however we strongly
-recommend to omit this element, as the indenter usually will be set by either defining
+<userinput>general</userinput> defines which indenter will be used. However, we strongly
+recommend you omit this element, as the indenter usually will be set by either defining
a File Type or by adding a mode line to the text file. If you specify an indenter though,
you will force a specific indentation on the user, which he might not like at all.
Available attributes are:</term>
@@ -483,7 +483,7 @@ and <emphasis>xml</emphasis>.</para>
as a short summary: Default styles are predefined font and color styles.</para>
<variablelist>
<varlistentry>
-<term>So here only the list of available default styles:</term>
+<term>So here are only the list of available default styles:</term>
<listitem>
<para><userinput>dsNormal</userinput>, used for normal text.</para>
<para><userinput>dsKeyword</userinput>, used for keywords.</para>
@@ -513,7 +513,7 @@ as a short summary: Default styles are predefined font and color styles.</para>
<para>This section describes the syntax detection rules.</para>
<para>Each rule can match zero or more characters at the beginning of
-the string they are test against. If the rule matches, the matching
+the string they are tested against. If the rule matches, the matching
characters are assigned the style or <emphasis>attribute</emphasis>
defined by the rule, and a rule may ask that the current context is
switched.</para>
@@ -673,7 +673,7 @@ comparing is used.</para>
<term>WordDetect</term>
<listitem>
<para>Detect an exact string but additionally require word boundaries
-like a dot <userinput>'.'</userinput> or a whitespace on the beginning
+such as a dot <userinput>'.'</userinput> or a whitespace on the beginning
and the end of the word. Think of <userinput>\b<string>\b</userinput>
in terms of a regular expression, but it is faster than the rule <userinput>RegExpr</userinput>.</para>
<programlisting><WordDetect String="(string)" [insensitive="true|false"] (common attributes) (dynamic) /></programlisting>
@@ -717,13 +717,13 @@ for more information on those.</para>
keyword list by name. A list with that name must exist.</para>
<para>The highlighting system processes keyword rules in a very optimized way.
This makes it an absolute necessity that any keywords to be matched need to be
-surrounded by defined deliminators, either implied (the default deliminators),
+surrounded by defined delimiters, either implied (the default delimiters),
or explicitly specified within the <emphasis>additionalDeliminator</emphasis>
property of the <emphasis>keywords</emphasis> tag.</para>
-<para>If a keyword to be matched shall contain a deliminator character, this
+<para>If a keyword to be matched shall contain a delimiter character, this
respective character must be added to the <emphasis>weakDeliminator</emphasis>
property of the <emphasis>keywords</emphasis> tag. This character will then
-loose its deliminator property in all <emphasis>keyword</emphasis> rules.</para>
+loose its delimiter property in all <emphasis>keyword</emphasis> rules.</para>
</listitem>
</varlistentry>
@@ -753,7 +753,7 @@ the <acronym>DTD</acronym> only allows the child rule <userinput>StringDetect</u
<para>Detect a floating point number.</para>
<para><programlisting><Float (common attributes) /></programlisting></para>
<para>This rule has no specific attributes. <userinput>AnyChar</userinput> is
-allowed as a child rules and typically used to detect combinations, see rule
+allowed as a child rule and typically used to detect combinations, see rule
<userinput>Int</userinput> for reference.</para>
</listitem>
</varlistentry>
@@ -790,7 +790,7 @@ program code, for example <userinput>\n</userinput>
<para>The following characters will match if they follow a backslash
(<literal>\</literal>):
<userinput>abefnrtv"'?\</userinput>. Additionally, escaped
-hexadecimal numbers like for example <userinput>\xff</userinput> and
+hexadecimal numbers such as for example <userinput>\xff</userinput> and
escaped octal numbers, for example <userinput>\033</userinput> will
match.</para>
@@ -805,7 +805,7 @@ match.</para>
<para>This rule has no specific attributes.</para>
<para>It matches C characters enclosed in a tick (Example: <userinput>'c'</userinput>).
-So in the ticks may be a simple character or an escaped character.
+The ticks may be a simple character or an escaped character.
See HlCStringChar for matched escaped character sequences.</para>
</listitem>
@@ -855,8 +855,8 @@ would include the context <emphasis>String</emphasis> from the <emphasis>C++</em
highlighting definition.</para>
<para>If <userinput>includeAttrib</userinput> attribute is
<emphasis>true</emphasis>, change the destination attribute to the one of
-the source. This is required to make for example commenting work, if text
-matched by the included context is a different highlight than the host
+the source. This is required to make, for example, commenting work, if text
+matched by the included context is a different highlight from the host
context.
</para>
</listitem>
@@ -870,9 +870,9 @@ context.
<programlisting><DetectSpaces (common attributes) /></programlisting>
<para>This rule has no specific attributes.</para>
-<para>Use this rule if you know that there can several whitespaces ahead,
+<para>Use this rule if you know that there can be several whitespaces ahead,
for example in the beginning of indented lines. This rule will skip all
-whitespace at once, instead of testing multiple rules and skipping one at the
+whitespace at once, instead of testing multiple rules and skipping one at a
time due to no match.</para>
</listitem>
</varlistentry>
@@ -886,7 +886,7 @@ time due to no match.</para>
<para>This rule has no specific attributes.</para>
<para>Use this rule to skip a string of word characters at once, rather than
-testing with multiple rules and skipping one at the time due to no match.</para>
+testing with multiple rules and skipping one at a time due to no match.</para>
</listitem>
</varlistentry>
@@ -919,7 +919,7 @@ You can achieve the same much faster in using:
<programlisting><DetectChar attribute="Macro" context="macro" char="#" firstNonSpace="true" /></programlisting>
If you want to match the regular expression <userinput>'^#'</userinput> you
can still use <userinput>DetectChar</userinput> with the attribute <userinput>column="0"</userinput>.
-The attribute <userinput>column</userinput> counts character based, so a tabulator still is only one character.
+The attribute <userinput>column</userinput> counts characters, so a tabulator is only one character.
</para>
</listitem>
<listitem>
More information about the kde-doc-english
mailing list