GNOME.org
 

[nautilus-actions] Documentation spelling fixes and improvements

commit 6ff8d845c92ac550b2512b6fb6661d77b9f22c79
Author: Christian Kirbach <christian kirbach googlemail com>
Date:   Sun Jul 3 12:16:15 2011 +0200

    Documentation spelling fixes and improvements
    
    Fix #652664.

 ChangeLog                       |    8 ++++++++
 docs/nact/C/nact-conditions.xml |   34 +++++++++++++++++-----------------
 docs/nact/C/nact-execution.xml  |   26 +++++++++++++-------------
 docs/nact/C/nact-where.xml      |   38 +++++++++++++++++++-------------------
 4 files changed, 57 insertions(+), 49 deletions(-)
---
diff --git a/ChangeLog b/ChangeLog
index e7b2429..3a25f62 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2011-07-03 Pierre Wieser <pwieser trychlos org>
+
+	* docs/nact/C/nact-conditions.xml:
+	* docs/nact/C/nact-execution.xml:
+	* docs/nact/C/nact-where.xml:
+	Fix #652664 - [doc] couple of spelling and improvement suggestions;
+	patch provided by Christian Kirbach.
+
 2011-06-10 Pierre Wieser <pwieser trychlos org>
 
 	* src/core/na-boxed.c (string_to_array):
diff --git a/docs/nact/C/nact-conditions.xml b/docs/nact/C/nact-conditions.xml
index 677d96e..057e630 100644
--- a/docs/nact/C/nact-conditions.xml
+++ b/docs/nact/C/nact-conditions.xml
@@ -47,7 +47,7 @@
     <para>
       In fact, basename-based conditions are built as a list of
       &must_match; and &must_not_match;
-      patterns. In order you action be candidate regarding of these basename-based
+      patterns. In order for your action to be a candidate regarding these basename-based
       conditions, each element of the selection must be valid for all the listed
       conditions: the basename of each element must match at least one of the defined
       &must_match; patterns, and must not match any of
@@ -178,7 +178,7 @@
     <para>
       In fact, mimetype-based conditions are built as a list of
       &must_match; and &must_not_match; patterns.
-      In order you action be candidate regarding of these mimetype-based
+      In order for your action to be a candidate regarding these mimetype-based
       conditions, each element of the selection must be valid for all the listed
       conditions: the mimetype of each element must match at least one of the defined
       &must_match; patterns, and must not match any of
@@ -347,9 +347,9 @@
     <para>
       In fact, folder-based conditions are built as a list of
       &must_match; and &must_not_match; patterns.
-      In order you action be candidate regarding of these folder-based
+      In order for your action to be a candidate regarding these folder-based
       conditions, each element of the selection must be valid for all the
-      listed conditions: each element must located in one of the defined
+      listed conditions: each element must be located in one of the defined
       &must_match; folders, and must not match any of the defined
       &must_not_match; folders.
     </para>
@@ -465,7 +465,7 @@
     <para>
       In fact, scheme-based conditions are built as a list of
       &must_match; and &must_not_match; patterns.
-      In order you action be candidate regarding of these scheme-based
+      In order for your action to be a candidate regarding these scheme-based
       conditions, each element of the selection must be valid for all the
       listed conditions: the scheme of each element must match at least one
       of the defined &must_match; patterns, and must not match any of
@@ -606,7 +606,7 @@
     <para>
       In fact, capability-based conditions are built as a list of
       &laquosp;must match all of&spraquo; and &must_not_match; patterns.
-      In order you action be candidate regarding of these capability-based
+      In order for your action to be a candidate regarding these capability-based
       conditions, each element of the selection must be valid for all the
       listed conditions: the capability of each element must match each
       of the defined &laquosp;must match all of&spraquo; capabilities,
@@ -779,7 +779,7 @@
         <simplelist type="vert">
           <member><literal>&lt;</literal> <termdef>(strictly less than)</termdef></member>
           <member><literal>=</literal> <termdef>(equal to)</termdef></member>
-          <member><literal>&gt;</literal> <termdef>(strictly greather than)</termdef></member>
+          <member><literal>&gt;</literal> <termdef>(strictly greater than)</termdef></member>
         </simplelist>
       </listitem>
       <listitem>
@@ -791,7 +791,7 @@
     <para>
       The selection count defaults to
       &laquosp;<literal>Count > (strictly greater than) 0</literal>&spraquo;,
-      which means that the action will be candidate to be displayed
+      which means that the action will be a candidate to be displayed
       as soon as at least one item is selected in the file manager.
     </para>
   </sect3>
@@ -875,7 +875,7 @@
     <para>
       The targeted desktop environment condition defaults to
       &laquosp;<literal>Always appear</literal>&spraquo;,
-      which means that the action will be candidate to be displayed
+      which means that the action will be a candidate to be displayed
       regarding of the current desktop environment.
     </para>
   </sect3>
@@ -887,7 +887,7 @@
       prerequisite package is installed on your system. This is
       checked here by specifying that a specific file, known or
       at least supposed to be provided by the package, must be
-      present on the filesystem, and executable.
+      present on the file system, and executable.
     </para>
     <para>
       Click on the <guilabel>Environment</guilabel> tab to show the page
@@ -919,7 +919,7 @@
       To define the relevant file, enter its full filename in the
       <guilabel>Appears if the file is executable</guilabel> entry
       box, or click on <guibutton>Browse</guibutton> to select a file
-      on the filesystem.
+      on the file system.
     </para>
     <para>
       Leave the field empty if this condition is not relevant for
@@ -929,7 +929,7 @@
       <para>
         You may embed some parameters in the searched filename.
         These parameters will be dynamically substituted at runtime with values
-        which will depend of currently selected item(s). 
+        which will depend on currently selected item(s). 
       </para>
     </tip>
   </sect3>
@@ -938,7 +938,7 @@
     <title>D-Bus registration condition</title>
     <para>
       You may define that your action will only appear if some given
-      name is registered on D-Bus system at runtime.
+      name is registered on the D-Bus system at runtime.
     </para>
     <para>
       Click on the <guilabel>Environment</guilabel> tab to show the page
@@ -958,7 +958,7 @@
       <para>
         You may embed some parameters in the searched name.
         These parameters will be dynamically substituted at runtime with values
-        which will depend of currently selected item(s). 
+        which will depend on currently selected item(s). 
       </para>
     </tip>
   </sect3>
@@ -993,7 +993,7 @@
       <para>
         You may embed some parameters in the executed filename or its options.
         These parameters will be dynamically substituted at runtime with values
-        which will depend of currently selected item(s). 
+        which will depend on currently selected item(s). 
       </para>
     </tip>
   </sect3>
@@ -1013,7 +1013,7 @@
       To define the binary, enter its name in the
       <guilabel>Appears if the binary is running</guilabel>
       entry box, or click on <guibutton>Browse</guibutton> to select
-      a file on the filesystem.
+      a file on the file system.
     </para>
     <note>
       <para>
@@ -1030,7 +1030,7 @@
       <para>
         You may embed some parameters in the searched name.
         These parameters will be dynamically substituted at runtime with values
-        which will depend of currently selected item(s). 
+        which will depend on currently selected item(s). 
       </para>
     </tip>
   </sect3>
diff --git a/docs/nact/C/nact-execution.xml b/docs/nact/C/nact-execution.xml
index 0c79c7d..1437165 100644
--- a/docs/nact/C/nact-execution.xml
+++ b/docs/nact/C/nact-execution.xml
@@ -1,10 +1,10 @@
 <sect2 id="usage-execution">
-  <title>What the action should it execute ?</title>
+  <title>What action should be executed ?</title>
   <para>
-    You most probably want your action eventually ends up with
+    You most probably want that your action eventually ends up in
     executing something. And, as a matter of fact, having something
     to execute is one of the few conditions which are required
-    in order an action be considered as valid.
+    for an action to be considered as valid.
   </para>
   <para>
     As we have already seen, the command to be executed is configured
@@ -13,7 +13,7 @@
   <para>
     This command may take arguments, which themselves may embed
     parameters. These parameters will be expanded at runtime,
-    with values which will depend of currently selected item(s).
+    with values which will depend on currently selected item(s).
   </para>
 
   <sect3 id="usage-execution-parameters">
@@ -94,23 +94,23 @@
     </para>
     <para>
       In the particular case of the <literal>%d</literal> parameter,
-      which is the &laquosp;<guilabel>first</guilabel>&spraquo; selected item
-      is not very important: we are rather sure that all selected items
+      the &laquosp;<guilabel>first</guilabel>&spraquo; selected item
+      is not very important because it is very likely that all selected items
       are located in the same base directory.
     </para>
   </sect3>
 
   <sect3 id="usage-execution-how">
-    <title>How the action should it be executed ?</title>
+    <title>How should the action be executed ?</title>
     <para>
-      Apart from configuring the conditions the selection must met in
+      Apart from configuring the conditions, the selection must met in
       order your action be displayed in file manager menus, &prodname;
       allows you to configure how exactly your command will be
       executed.
     </para>
     <para>
       Click on the <guilabel>Execution</guilabel> tab to show the page
-      which will permit you to configure the execution of your command.
+      which configures the execution of your command.
     </para>
     <figure id="nact-FIG-execution">
       <title>Configuration of the execution modes</title>
@@ -277,7 +277,7 @@
       </figure>
       <para>
         Enter in the <guilabel>Execute as user</guilabel> entry box the username
-        or the <acronym>UID</acronym> of the user your command must be ran as.
+        or the <acronym>UID</acronym> of the user your command will be run as.
       </para>
       <para>
         If you do not enter anything in this field, then the command will be
@@ -286,14 +286,14 @@
     </sect4>
 
     <sect4 id="usage-execution-how-singular">
-      <title>Multiple execution</title>
+      <title>Multiple executions</title>
       <para>
-        You may want your command be executed once, giving it the list of
+        You may want your command be executed once, providing it the list of
         selected items as argument.
       </para>
       <para>
         Or you may prefer your command be repeated for each selected item,
-        giving to each execution a different item as argument.
+        providing a different item as argument for each execution.
       </para>
       <para>
         Actually, &prodname; automatically handles these two behaviors,
diff --git a/docs/nact/C/nact-where.xml b/docs/nact/C/nact-where.xml
index e4fcb79..2847311 100644
--- a/docs/nact/C/nact-where.xml
+++ b/docs/nact/C/nact-where.xml
@@ -8,7 +8,7 @@
             <imagedata fileref="figures/nact-target-location.png" format="PNG" />
           </imageobject>
           <textobject>
-            <phrase>Shows the three fields which lets you configure the target of your action.</phrase>
+            <phrase>Shows the three fields which let you configure the target of your action.</phrase>
           </textobject>
           <caption>
             <para>Target configuration</para>
@@ -31,8 +31,8 @@
     <title>Targeting the selection context menu</title>
     <para>
       When <guilabel>Display item in selection context menu</guilabel>
-      is checked, then your action will be candidate to be displayed in 
-      &nautilus; context menu as soon as at least one item is selected in 
+      is checked, then your action will be a candidate to be displayed in 
+      &nautilus;' context menu as soon as at least one item is selected in 
       the file manager. Your action will so deal with currently selected
       item(s).In order to be
       actually displayed, all the conditions defined in
@@ -42,8 +42,8 @@
     <tip>
       <para>
         When an action targets the selection context menu, and is actually 
-        displayed in &nautilus; context menu, then it is also displayed
-        in &nautilus; <guimenu>Edit</guimenu> menu.
+        displayed in &nautilus;' context menu, then it is also displayed
+        in &nautilus;' <guimenu>Edit</guimenu> menu.
       </para>
     </tip>
     <para>
@@ -55,8 +55,8 @@
     <title>Targeting the location context menu</title>
     <para>
       When <guilabel>Display item in location context menu</guilabel> checkbox
-      is activated, then your action will be candidate to be displayed in 
-      &nautilus; context menu when the file manager selection is empty.
+      is activated, then your action will be a candidate to be displayed in 
+      &nautilus;' context menu when the file manager selection is empty.
       Your action will so deal with currently displayed location.
       In order to be
       actually displayed, all the conditions defined in
@@ -66,8 +66,8 @@
     <tip>
       <para>
         When an action targets the location context menu, and is actually 
-        displayed in &nautilus; context menu, then it is also displayed
-        in &nautilus; <guimenu>File</guimenu> menu.
+        displayed in &nautilus;' context menu, then it is also displayed
+        in &nautilus;' <guimenu>File</guimenu> menu.
       </para>
     </tip>
   </sect3>
@@ -76,8 +76,8 @@
     <title>Targeting the toolbar</title>
     <para>
       When <guilabel>Display item in the toolbar</guilabel> checkbox
-      is activated, then your action will be candidate to be displayed in 
-      &nautilus; toolbar.
+      is activated, then your action will be a candidate to be displayed in 
+      &nautilus;' toolbar.
     </para>
     <para>
       Actions displayed in the toolbar only deal with the location which
@@ -95,7 +95,7 @@
       <title>If your action is to be displayed in a context menu</title>
       <para>
         Whether it is the selection context menu or the location
-        context menu, and both in &nautilus; context menus and in 
+        context menu, and both in &nautilus;' context menus and in 
         <guimenu>File</guimenu> or <guimenu>Edit</guimenu> menus, it
         will be displayed as
       </para>
@@ -129,7 +129,7 @@
       <para>
         You may embed some parameters in the label, the icon name or the tooltip.
         These parameters will be dynamically substituted at runtime with values
-        which will depend of currently selected item(s). 
+        which will depend on currently selected item(s). 
       </para>
     </tip>
 
@@ -166,26 +166,26 @@
     </note>
     <tip>
       <para>
-        The toolbar label defaults to the same label than
+        The toolbar label defaults to the same label as
         those used in menus. By unchecking the
         <guilabel>Use same label for icon in the toolbar</guilabel>
-        checkbox, then you can define a label specific to the
-        toolbar, usually shorter that those defined for the menus.
+        checkbox you can define a label specific to the
+        toolbar, which is usually shorter that those defined for the menus.
       </para>
     </tip>
     <tip>
       <para>
         You may embed some parameters in the toolbar label, the icon name or the tooltip.
         These parameters will be dynamically substituted at runtime with values
-        which will depend of currently selected item(s). 
+        which will depend on currently selected item(s). 
       </para>
     </tip>
 
     <formalpara>
       <title>Defining several targets</title>
       <para>
-        An action may target both the selection context menu, the location context
-        menu and the toolbar, or one or more among these.
+        An action may target the selection context menu, the location context
+        menu and the toolbar, or one or more of these.
       </para>
     </formalpara>
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]