Further input from Mark re: hyphenation.

diff --git a/docs/en/rst/installing/installing-end.inc.rst b/docs/en/rst/installing/installing-end.inc.rst
index a259e53fcadcf34eecfab982235f7556284061d0..6e34395acb9aaf3f2fb2779658b99bad24f67c44 100644 (file)
--- a/docs/en/rst/installing/installing-end.inc.rst
+++ b/docs/en/rst/installing/installing-end.inc.rst
@@ -15,7 +15,7 @@ Load this file in your editor. You will need to check/change ``$db_driver``
 and ``$db_pass``, which are respectively the type of the database you are
 using and the password for the ``bugs`` database user you have created.
 ``$db_driver`` can be either ``mysql``, ``Pg`` (PostgreSQL), ``Oracle`` or
-``Sqlite``. All values are case-sensitive.
+``Sqlite``. All values are case sensitive.
 
 Set the value of ``$webservergroup`` to the group your web server runs as.
 

diff --git a/docs/en/rst/using/finding.rst b/docs/en/rst/using/finding.rst
index 32e73a8f1df372a30cec8236a1908f4f8a5e6a67..9acbd460bd7b196235221675c49b504167cf4c9f 100644 (file)
--- a/docs/en/rst/using/finding.rst
+++ b/docs/en/rst/using/finding.rst
@@ -7,7 +7,7 @@ Bugzilla has a number of different search options.
 
 .. note:: Bugzilla queries are case-insensitive and accent-insensitive when
     used with either MySQL or Oracle databases. When using Bugzilla with
-    PostgreSQL, however, some queries are case-sensitive. This is due to
+    PostgreSQL, however, some queries are case sensitive. This is due to
     the way PostgreSQL handles case and accent sensitivity.
 
 .. _quicksearch:

diff --git a/docs/en/rst/using/understanding.rst b/docs/en/rst/using/understanding.rst
index 39db5c9e94d0434205c172d85820d6bac330c779..014abefd6a7065a02ebd573b19b920d15afa8c58 100644 (file)
--- a/docs/en/rst/using/understanding.rst
+++ b/docs/en/rst/using/understanding.rst
@@ -14,7 +14,7 @@ installation of Bugzilla.
    the bug number.
 
 *Status (and Resolution):*
-   These define exactly what state the bug is in - from not even
+   These define exactly what state the bug is in—from not even
    being confirmed as a bug, through to being fixed and the fix
    confirmed by Quality Assurance. The different possible values for
    Status and Resolution on your installation should be documented in the
@@ -43,7 +43,7 @@ installation of Bugzilla.
    manager. It's a good idea not to change this on other people's bugs. The
    default values are P1 to P5.
 
-   The Severity field indicates how severe the problem is - from blocker
+   The Severity field indicates how severe the problem is—from blocker
    ("application unusable") to trivial ("minor cosmetic issue"). You
    can also use this field to indicate whether a bug is an enhancement
    request.
@@ -52,7 +52,7 @@ installation of Bugzilla.
    A future version by which the bug is to
    be fixed. e.g. The Bugzilla Project's milestones for future
    Bugzilla versions are 4.4, 5.0, 6.0, etc. Milestones are not
-   restricted to numbers, though - you can use any text strings, such
+   restricted to numbers, though—you can use any text strings, such
    as dates.
 
 *Assigned To:*
@@ -69,7 +69,7 @@ installation of Bugzilla.
 
 *Keywords:*
    The administrator can define keywords which you can use to tag and
-   categorise bugs - e.g. ``crash`` or ``regression``.
+   categorise bugs—e.g. ``crash`` or ``regression``.
 
 *Personal Tags:*
    Unlike Keywords which are global and visible by all users, Personal Tags