Git commit 328499c354a8992935343b4e5d825584f0422a45 by Stephane MANKOWSKI.
Committed on 30/10/2019 at 19:43.
Pushed by smankowski into branch 'master'.

BUG:D24973

M  +9    -12   doc/index.docbook

https://commits.kde.org/skrooge/328499c354a8992935343b4e5d825584f0422a45

diff --git a/doc/index.docbook b/doc/index.docbook
index d8e1d2fc7..48daff581 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -129,45 +129,42 @@
       
       <sect2 id="terminology-operation">
        <title>Operation</title>
-       <para>An operation is either a credit or a debt on one of your 
accounts. By affecting a <link linkend="terminology-category">category</link> 
to an operation, you are able to analyze how you spend your money.
-       </para>
+       <para>An operation is either a credit or debit to one of your accounts. 
 If you assign a <link linkend="terminology-category">category</link> or <link 
linkend="trackers">tracker</link> to operations, you can analyze how you spend 
your money.</para>
        
        <sect3 id="terminology_standard_operation">
          <title>Standard Operation</title>
-         <para>A standard operation is the basic operation in &skrooge;. Like 
"Today, spent 20€ in credit card for groceries".</para>
+         <para>A standard operation is the basic operation in &skrooge;. For 
example, "Today, spent 20€ in credit card for groceries".</para>
          <para></para>
        </sect3>
        
        <sect3 id="terminology_split_operation">
          <title>Split Operation</title>
-         <para>A split operation is an operation for which the total amount is 
split over several <link linkend="terminology-category">categories</link>, 
dates and/or <link linkend="trackers">trackers</link>.</para>
-         <para>For example, "Yesterday, spent 100€ at the supermarket, of 
which 60€ were for food, and 40€ for clothes".</para>
+         <para>A split operation is an operation for which the total amount is 
split over several <link linkend="terminology-category">categories</link>, 
dates and/or <link linkend="trackers">trackers</link>. For example, "Yesterday, 
spent 100€ at the supermarket, of which 60€ were for food, and 40€ for 
clothes".</para>
        </sect3>
        
        <sect3 id="terminology_transfer">
          <title>Transfer</title>
-         <para>A transfer in &skrooge; is equivalent to moving a quantity of 
money from one of your &skrooge; accounts to another of your &skrooge; 
accounts.</para>
-         <para>This must not be confused with the payment mode chosen: if you 
made a transfer, for example using your bank's website, to someone else's 
account, this is not a transfer operation, because &skrooge; doesn't know about 
that other person's account. It is a <link 
linkend="terminology_standard_operation">standard operation</link> made with 
transfer as a payment mode.</para>
-         <para>Read the <link linkend="transfer">dedicated chapter</link> if 
things are still unclear</para>
+         <para>A transfer in &skrooge; records moving a quantity of money from 
one of your &skrooge; accounts to another.</para>
+         <para>This must not be confused with the payment mode chosen: if you 
made a transfer, for example using your bank's website, to someone else's 
account, this is not a transfer operation, because &skrooge; doesn't know about 
that other person's account. It is a <link 
linkend="terminology_standard_operation">standard operation</link> with 
transfer as its payment mode.</para>
+         <para>Read the <link linkend="transfer">transfer section</link> if 
things are still unclear</para>
        </sect3>
        
        <sect3 id="terminology_validated_operation">
          <title>Validated Operation</title>
-         <para>When <link linkend="import">Importing</link> operations, they 
are not considered valid right away. You need first to manually validate them 
before. A validated operation is this, an imported operation that has been 
validated.</para>
+         <para>When you <link linkend="import">import</link> operations from 
your financial instution into &skrooge;, they are not considered valid right 
away and appear in blue. You need to manually validate them. Such validated 
operations no longer appear blue.</para>
          <para>Note that it is possible to automatically validate operations 
on import, by turning on the corresponding option in the <!--TODO: put a link 
to the settings here-->settings.</para>
        </sect3>
        
        <sect3 id="terminology_pointed_operation">
          <title>Pointed Operation</title>
-         <para>During the <link linkend="reconciliation">reconciliation 
process</link>, you point in &skrooge; all operations that appear in the 
corresponding account position. A pointed operation is one of these operations. 
It is not <link linkend="terminology_checked_operation">Checked</link> until 
the reconciliation is completed.</para>
+         <para>During the <link linkend="reconciliation">reconciliation 
process</link>, you point in &skrooge; all operations that appear in the 
corresponding account position. Such pointed operations display a half-filled 
square in the Status column of an operations view. A pointed operation is not 
<link linkend="terminology_checked_operation">Checked</link> until you complete 
reconciliation.</para>
        </sect3>
        
        <sect3 id="terminology_checked_operation">
          <title>Checked Operation</title>
-         <para>When all operations on your account's position have been 
pointed in &skrooge;, you can complete the reconciliation process. All <link 
linkend="terminology_pointed_operation">Pointed</link> operation are then 
turned into Checked Operations.</para>
+         <para>When all operations on your account's position have been 
pointed in &skrooge;, you can complete the reconciliation process. &skrooge; 
then turns all <link linkend="terminology_pointed_operation">Pointed</link> 
operations into Checked Operations, which display a filled square in the Status 
column of an operations view.</para>
        </sect3>
        
-       
       </sect2>
       
       <sect2 id="terminology-category">

Reply via email to