[Rt-commit] rt branch, 4.0/upgrading-docs, updated. rt-4.0.0rc6-46-g55402b1

[Kevin Falcone]

The branch, 4.0/upgrading-docs has been updated
       via  55402b1992b8078dee812af9e36e0d9564b23ad2 (commit)
       via  853e5c649aa54d0564ab2c71d576d8e72c167506 (commit)
       via  9fe44871fef10c9600c337f728232c823be019a6 (commit)
      from  f990c0c66464c989dd7a12f8bcfbd2c542ca6fee (commit)

Summary of changes:
 README             |    7 ++++---
 docs/UPGRADING-4.0 |    2 +-
 2 files changed, 5 insertions(+), 4 deletions(-)

- Log -----------------------------------------------------------------
commit 9fe44871fef10c9600c337f728232c823be019a6
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Mar 17 14:16:50 2011 -0400

    small wording tweaks

diff --git a/README b/README
index 971bbe1..3f58a7f 100644
--- a/README
+++ b/README
@@ -125,7 +125,7 @@ GENERAL INSTALLATION
 
       and follow the instructions.  Once completed, you should now have a
       working RT instance running with the standalone rt-server.  Press
-      Ctrl-C to stop it, and proceed to Step 7 to configure recommended
+      Ctrl-C to stop it, and proceed to Step 7 to configure a recommended
       deployment environment for production.
 
       To configure RT manually, you must setup etc/RT_SiteConfig.pm in
diff --git a/docs/UPGRADING-4.0 b/docs/UPGRADING-4.0
index b1cba9a..e030d4c 100644
--- a/docs/UPGRADING-4.0
+++ b/docs/UPGRADING-4.0
@@ -4,7 +4,7 @@ RT now defaults to a database name of rt4 and an installation root of /opt/rt4.
 
 If you are upgrading, you will likely want to specify that your database
 is still named rt3 (or import a backup of your database as rt4 so that
-can feel more confident making the upgrade).
+you can feel more confident making the upgrade).
 
 If you choose to force RT to install into /opt/rt3, or another existing RT 3.x
 install location, you will encounter issues because we removed the _Overlay

commit 853e5c649aa54d0564ab2c71d576d8e72c167506
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Mar 17 14:17:06 2011 -0400

    refer people to our security webpage

diff --git a/README b/README
index 3f58a7f..5010695 100644
--- a/README
+++ b/README
@@ -263,7 +263,8 @@ SECURITY
 If you believe you've discovered a security issue in RT, please send an
 email to <security at bestpractical.com> with a detailed description of the
 issue, and a secure means to respond to you (such as your PGP public
-key).
+key).  You can find our PGP key and fingerprint at
+http://bestpractical.com/security/
 
 
 BUGS

commit 55402b1992b8078dee812af9e36e0d9564b23ad2
Author: Kevin Falcone <falcone at bestpractical.com>
Date:   Thu Mar 17 14:17:19 2011 -0400

    prefer bestpractical.com over fsck.com

diff --git a/README b/README
index 5010695..f4f847c 100644
--- a/README
+++ b/README
@@ -276,7 +276,7 @@ into on the rt-users mailinglist (or pick up a commercial support
 contract from Best Practical). But, sometimes people do run into
 bugs. In the exceedingly unlikely event that you hit a bug in RT, please
 report it! We'd love to hear about problems you have with RT, so we can
-fix them.  To report a bug, send email to <rt-bugs at fsck.com>.
+fix them.  To report a bug, send email to <rt-bugs at bestpractical.com>.
 
 
 # BEGIN BPS TAGGED BLOCK {{{

-----------------------------------------------------------------------