Fix spelling in documentation

In some cases a little work on some grammar.

Author: puck

bin/rt-crontool.in

@@ -391,11 +391,11 @@ as cron.
 
 Security:
 
-This tool allows the user to run arbitrary perl modules from within RT. If
+This tool allows the user to run arbitrary Perl modules from within RT. If
 this tool were setgid, a hostile local user could use this tool to gain
-administrative access to RT. It is incredibly important that nonprivileged
+administrative access to RT. It is incredibly important that non-privileged
 users not be allowed to run this tool. It is suggested that you create a
-non-privileged unix user with the correct group membership and RT access to
+non-privileged Unix user with the correct group membership and RT access to
 run this tool.
 
 

bin/rt-mailgate.in

@@ -328,7 +328,7 @@ Usual invocation (from MTA):
 
 =item C<--action>
 
-Specifies what happens to email sent to this alias.  The avaliable basic
+Specifies what happens to email sent to this alias.  The available basic
 actions are: C<correspond>, C<comment>.  Additional actions, such as
 C<take> or C<resolve>, may be available depending on your local
 C<@MailPlugins> configuration.
@@ -372,7 +372,7 @@ This flag tells the mail gateway to trust all SSL certificates,
 regardless of if their hostname matches the certificate, and regardless
 of CA.  This is required if you have a self-signed certificate, or some
 other certificate which is not traceable back to an certificate your
-system ultimitely trusts.
+system ultimately trusts.
 
 =item C<--extension> OPTIONAL
 

devel/tools/rt-apache

@@ -248,7 +248,7 @@ of that list which exists will be used.  See also L</--modules>.
 
 =item --port B<number>, -p
 
-Choses the port to listen on.  By default, this is parsed from the
+Chooses the port to listen on.  By default, this is parsed from the
 F<RT_SiteConfig.pm>, and falling back to 8888.
 
 =item --ssl [B<number>]

docs/UPGRADING-3.6

@@ -3,7 +3,7 @@
 As there are a large number of code changes, it is highly recommended that you
 install RT into a fresh directory, and then reinstall your customizations.
 
-The database schema has changed significantly for mysql 4.1 and above; please
+The database schema has changed significantly for MySQL 4.1 and above; please
 read UPGRADING.mysql for more details.
 
 The configuration format has been made stricter. All options MUST be set using

docs/UPGRADING-4.0

@@ -54,8 +54,8 @@ lists.
 
 =head2 Upgrading sessions on MySQL
 
-In 4.0.0rc2, RT began shipping an updated schema for the sesions table that
-specificies a character set as well as making the table InnoDB.  As part of
+In 4.0.0rc2, RT began shipping an updated schema for the sessions table that
+specifies a character set as well as making the table InnoDB.  As part of
 the upgrade process, your sessions table will be dropped and recreated with
 the new schema.
 
@@ -80,7 +80,7 @@ You can run this as
 
   /opt/rt5/etc/upgrade/upgrade-articles
 
-It will ouput a lot of data about what it is changing.  You should review this
+It will output a lot of data about what it is changing.  You should review this
 for errors.
 
 If you are running RTFM 2.0 with a release of RT, there isn't currently an
@@ -119,7 +119,7 @@ with duplicate names.  Running
 will report duplicate group names, and running it with --resolve will fix
 duplicates by appending the group id to the name.
 
-Nota Bene: As a result of differing indexes in the schema files, Postgres and
+Nota Bene: As a result of differing indexes in the schema files, PostgreSQL and
 SQLite RT databases have enforced group name uniqueness for many years at the
 database level.
 
@@ -173,7 +173,7 @@ The 3.9.2 upgrade step removed all enabled Personal Groups, but missed
 any disabled groups. We catch and clean up the disabled Personal groups
 during the 4.0.9 upgrade step.
 
-=head2 Javascript Changes
+=head2 JavaScript Changes
 
 If you have set a custom @JSFiles in RT_SiteConfig.pm, you will need to
 amend this to include the new jquery.cookie.js file added to

docs/UPGRADING-4.2

@@ -322,7 +322,7 @@ issues with blank outgoing emails.
 =head1 UPGRADING FROM 4.2.10 AND EARLIER
 
 The C<$DatabaseRequireSSL> option has never affected whether the
-database connection was performed using SSL, even under Postgres; the
+database connection was performed using SSL, even under PostgreSQL; the
 functionality can now be implemented via C<%DatabaseExtraDSN>.
 C<$DatabaseRequireSSL> has been removed, and setting it will trigger an
 informational message that setting it is ineffective.

docs/UPGRADING-5.0

@@ -54,7 +54,7 @@ change touches large RT tables like Transactions and Attachments, this
 upgrade step may take a while to run.
 
 You also will need free disk space equal to the size of these tables
-while running because MySQL, MariaDB, and Postgres will create a
+while running because MySQL, MariaDB, and PostgreSQL will create a
 temporary copy of the table while running. If you don't have sufficient
 space, it can cause this step to fail.
 
@@ -147,7 +147,7 @@ configuration option. This may also help other areas of RT in addition to
 searches.
 
 We are investigating options to improve the underlying queries. Some users have
-reported improved performance with the following indexes, at least on Postgres:
+reported improved performance with the following indexes, at least on PostgreSQL:
 
    CREATE INDEX ACL2 ON acl (objecttype, objectid);
    CREATE INDEX ACL3 ON acl (principalid, rightname, principaltype);
@@ -239,7 +239,7 @@ will migrate your existing tokens to the new core RT tables.
 =item *
 
 The extension C<RT::Extension::FormattedTransaction> was added to core. This
-adds a new RT dependency on the perl module L<Text::WordDiff>, so you will be
+adds a new RT dependency on the Perl module L<Text::WordDiff>, so you will be
 prompted to install this new module if your system doesn't have it.
 
 =item *
@@ -406,7 +406,7 @@ so batch runs only once for the outermost updates. All transactions
 performed for that batch are available from the C<TransactionBatch> method
 as expected.
 
-=item * Ambigious Owner order by option in search replaced with Owner.Name
+=item * Ambiguous Owner order by option in search replaced with Owner.Name
 
 RT 4.4.5 adds a bunch of new order by and format options for users and roles
 to the Query Builder. For example, you can order by user fields on a user
@@ -510,7 +510,7 @@ we have added the new option C<$EmailDashboardInlineCSS> to inline the
 CSS. We have found this reduces the size of the dashboard emails
 significantly and can help with rendering in some email clients.
 
-To use this new feature, you must install the optional perl module
+To use this new feature, you must install the optional Perl module
 L<CSS::Inliner>, version 4018 or later, then enable the feature in
 your RT configuration.
 

docs/authentication.pod

@@ -86,7 +86,7 @@ the matched user.
 It is often used to provide single sign-on (SSO) support via Apache modules
 such as C<mod_auth_kerb> (to talk to Active Directory).  C<$WebRemoteUserAuth> is
 widely used by organizations with existing authentication standards for web
-services that leverge web server modules for central authentication services.
+services that leverage web server modules for central authentication services.
 The flexibility of RT's C<$WebRemoteUserAuth> support means that it can be setup
 with almost any authentication system.
 

docs/charts.pod

@@ -15,7 +15,7 @@ when we converted the web chart library to Chart.js.
 =head2 C<$EnableJSChart>
 
 Starting in RT 5.0, by default charts are rendered by Chart.js,
-a javascript charting library. If you'd like to disable javascript
+a JavaScript charting library. If you'd like to disable JavaScript
 rendered charts, you can set this configuration value to false. To use
 GD charts instead of JS charts, set the C<--enable-gd> option
 when running the configure script to install RT.

docs/customizing/lifecycles.pod

@@ -16,7 +16,7 @@ The web interface allows for easy visualization and editing of lifecycles.
 =head2 Editing statuses, transitions and categories
 
 Instructions for interacting with the web UI lifecycle builder can be found on the main "modify" page.
-The modify page allows for create and deleting statuses, adding transistions between statuses with
+The modify page allows for create and deleting statuses, adding transitions between statuses with
 drag and drop arrows and changing the categories of a status (initial, active and inactive).
 
 =for html <img alt="Lifecycle UI Modify" src="../images/lifecycle-ui-modify.png">