Bug 962568 - Replace all "Caution" with "Warning" and all "Tip" with "Note". r=LpSolit, a=glob.

docs/en/rst/about.rst

@@ -148,14 +148,10 @@ Document Conventions
 
 This document uses the following conventions:
 
-.. caution:: This is a caution. Make sure to read this to not be in trouble!
-
-.. tip:: This is a hint or tip, especially about some configuration tweaks.
+.. warning:: This is a warning - something you should be aware of.
 
 .. note:: This is just a note, for your information.
 
-.. warning:: This is a warning, something you should take care of.
-
 A filename or a path to a filename is displayed like this:
 :file:`/path/to/filename.ext`
 
@@ -177,7 +173,7 @@ A sample of code is illustrated like this:
     Second Line of Code
     ...
 
-This documentation is maintained in ReStructured Text format.
+This documentation is maintained in reStructured Text format.
 Changes are best submitted as diffs, attached
 to a bug filed in the `Bugzilla Documentation <https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla;component=Documentation>`_
 component.

docs/en/rst/administration.rst

@@ -327,7 +327,7 @@ authentication, all other user-related tasks are still handled by email
 address, not LDAP username. For example, bugs are still assigned by
 email address and users are still queried by email address.
 
-.. caution:: Because the Bugzilla account is not created until the first time
+.. warning:: Because the Bugzilla account is not created until the first time
    a user logs in, a user who has not yet logged is unknown to Bugzilla.
    This means they cannot be used as an assignee or QA contact (default or
    otherwise), added to any CC list, or any other such operation. One
@@ -360,7 +360,7 @@ LDAPserver
     the URI, the default is either 389 or 636 for 'LDAP' and 'LDAPS'
     schemes respectively.
 
-    .. tip:: In order to use SSL with LDAP, specify a URI with "ldaps://".
+    .. note:: In order to use SSL with LDAP, specify a URI with "ldaps://".
        This will force the use of SSL over port 636.
        For example, normal LDAP:
        ``ldap://ldap.company.com``, LDAP over SSL:
@@ -577,7 +577,7 @@ password for this "super user". If for some reason you delete
 the "super user" account, re-running checksetup.pl will again prompt
 you for this username and password.
 
-.. tip:: If you wish to add more administrative users, add them to
+.. note:: If you wish to add more administrative users, add them to
    the "admin" group and, optionally, edit the tweakparams, editusers,
    creategroups, editcomponents, and editkeywords groups to add the
    entire admin group to those groups (which is the case by default).
@@ -1645,7 +1645,7 @@ adding too many fields can make the user interface more complicated and
 harder to use. Custom Fields should be added only when necessary and with
 careful consideration.
 
-.. tip:: Before adding a Custom Field, make sure that Bugzilla cannot already
+.. note:: Before adding a Custom Field, make sure that Bugzilla cannot already
    do the desired behavior. Many Bugzilla options are not enabled by
    default, and many times Administrators find that simply enabling
    certain options that already exist is sufficient.

docs/en/rst/installation.rst

@@ -176,7 +176,7 @@ Good locations are either directly in the web server's document directories or
 in :file:`/usr/local` with a symbolic link to the web server's
 document directories or an alias in the web server's configuration.
 
-.. caution:: The default Bugzilla distribution is NOT designed to be placed
+.. warning:: The default Bugzilla distribution is NOT designed to be placed
    in a :file:`cgi-bin` directory. This
    includes any directory which is configured using the
    ``ScriptAlias`` directive of Apache.
@@ -228,7 +228,7 @@ you invoke :file:`install-module.pl` as follows:
 
     bash# perl install-module.pl <modulename>
 
-.. tip:: Many people complain that Perl modules will not install for
+.. note:: Many people complain that Perl modules will not install for
    them. Most times, the error messages complain that they are missing a
    file in
    ``@INC``.
@@ -435,7 +435,7 @@ hosting account), you will need to leave
 that :file:`checksetup.pl` will subsequently display
 every time it is run.
 
-.. caution:: If you are using suexec, you should use your own primary group
+.. warning:: If you are using suexec, you should use your own primary group
    for *webservergroup* rather than leaving it
    empty, and see the additional directions in the suexec section :ref:`suexec`.
 
@@ -471,7 +471,7 @@ see what has changed.
 MySQL
 -----
 
-.. caution:: MySQL's default configuration is insecure.
+.. warning:: MySQL's default configuration is insecure.
    We highly recommend to run :file:`mysql_secure_installation`
    on Linux or the MySQL installer on Windows, and follow the instructions.
    Important points to note are:
@@ -706,7 +706,7 @@ When this is done, restart your web server.
 SQLite
 ------
 
-.. caution:: Due to SQLite's `concurrency
+.. warning:: Due to SQLite's `concurrency
    limitations <http://sqlite.org/faq.html#q5>`_ we recommend SQLite only for small and development
    Bugzilla installations.
 
@@ -1214,7 +1214,7 @@ the ActiveState repository.
    provided when you run :command:`checksetup.pl` as it will
    tell you what package you'll need to install.
 
-.. tip:: If you are behind a corporate firewall, you will need to let the
+.. note:: If you are behind a corporate firewall, you will need to let the
    ActiveState PPM utility know how to get through it to access
    the repositories by setting the HTTP_proxy system environmental
    variable. For more information on setting that variable, see
@@ -1712,7 +1712,7 @@ using Bzr.
     ...
     All changes applied successfully.
 
-.. caution:: If a line in the output from :command:`bzr up` mentions
+.. warning:: If a line in the output from :command:`bzr up` mentions
    a conflict, then that represents a file with local changes that
    Bzr was unable to properly merge. You need to resolve these
    conflicts manually before Bugzilla (or at least the portion using
@@ -1754,7 +1754,7 @@ omit the first three lines of the example.
    is a very important detail--it means that the destination
    directory is the current working directory.
 
-.. caution:: If you have some extensions installed, you will have to copy them
+.. warning:: If you have some extensions installed, you will have to copy them
    to the new bugzilla directory too. Extensions are located in :file:`bugzilla/extensions/`.
    Only copy those you
    installed, not those managed by the Bugzilla team.
@@ -1831,7 +1831,7 @@ steps to complete your upgrade.
       command :command:`./checksetup.pl` is important and cannot
       be omitted.
 
-   .. caution:: If this is a major upgrade (say, 3.6 to 4.2 or similar),
+   .. warning:: If this is a major upgrade (say, 3.6 to 4.2 or similar),
       running :command:`checksetup.pl` on a large
       installation (75,000 or more bugs) can take a long time,
       possibly several hours.

docs/en/rst/security.rst

@@ -93,7 +93,7 @@ be accessible is rather complicated. A quick way is to run
 Bugzilla files as expected. If not, you may want to follow the few
 steps below.
 
-.. tip:: Bugzilla ships with the ability to create :file:`.htaccess`
+.. note:: Bugzilla ships with the ability to create :file:`.htaccess`
    files that enforce these rules. Instructions for enabling these
    directives in Apache can be found in :ref:`http-apache`
 
@@ -134,7 +134,7 @@ or
 `Bugtraq ID 6501 <http://online.securityfocus.com/bid/6501>`_.
 To test, simply run :file:`testserver.pl`, as said above.
 
-.. tip:: Be sure to check :ref:`http` for instructions
+.. note:: Be sure to check :ref:`http` for instructions
    specific to the web server you use.
 
 .. _security-bugzilla: