Taiga 490: Fix capitalization in Tools > Patron import

[kohadocs.git] / source / tools.rst

diff --git a/source/tools.rst b/source/tools.rst
index 9e0fd78..2ad6c8f 100644 (file)
--- a/source/tools.rst
+++ b/source/tools.rst
@@ -178,7 +178,7 @@ and choosing 'Enrollment' from the 'Actions' button.
 Comments
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
--  *Get there:* More > Tools > Patrons and Circulation > Comments
+-  *Get there:* More > Tools > Patrons and circulation > Comments
 
 All comments added by patrons via the OPAC to bibliographic records
 require moderation by the librarians. If there are comments awaiting
@@ -187,12 +187,12 @@ below the module list:
 
 |image251|
 
-and next to the Comments tool on the Tools Module
+and next to the Comments tool on the Tools page
 
 |image1219|
 
 To moderate comments click on the notification on the main dashboard or
-go directly to the Comments Tool and click 'Approve' or 'Delete' to the
+go directly to the Comments tool and click 'Approve' or 'Delete' to the
 right of the comments awaiting moderation.
 
 |image252|
@@ -266,7 +266,7 @@ with the exception of a few mandatory ones.
        -  Since values can contain spaces, additional doubled-quotes may
           be required:
 
-          -  "INSTID:12345,BASEBALL:Cubs,""BASEBALL:White Sox"""
+          -  "INSTID:12345,BASEBALL:Cubs,""BASEBALL:White Sox""
 
     **Note**
 
@@ -278,7 +278,7 @@ with the exception of a few mandatory ones.
 
 .. _importing-patrons-label:
 
-Importing Patrons
+Importing patrons
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Once you have created your file, you can use the patron import tool to
@@ -297,11 +297,11 @@ bring the data into Koha.
 -  Next you can choose default values to apply to all patrons you are
    importing
 
-   -  ex. If you're importing patrons specific to one branch you can use
+   -  For example, if you're importing patrons specific to one branch you can use
       the field on the import form to apply the branch code to all those
       you are importing.
 
--  Finally you need to decide on what data you want to replace if there
+-  Finally, you need to decide on what data you want to replace if there
    are duplicates.
 
    -  A matching record is found using the field you chose for matching