starting to work...

1 files changed, 16 insertions, 17 deletions

diff --git a/rt/README.Oracle b/rt/README.Oracle
index 9835b93e6..e128f7096 100644
--- a/rt/README.Oracle
+++ b/rt/README.Oracle
@@ -1,23 +1,23 @@
-Since RT 3.8.2 RT deployment on Oracle database has been simplified.
+On RT 3.8.2 and later, RT deployment for Oracle databases is very
+straightforward.
 
-You don't need to create anything beforehead. During installation
-an user is created and all RT's objects are created in his schema.
-User is created with the following parameters:
+You don't need to configure Oracle beforehand. During installation
+a user is created and all RT's objects are created in his schema.
+The user is created with the following parameters:
 
     CREATE USER <DatabaseUser> IDENTIFIED BY <DatabasePassword>
         DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
         QUOTA UNLIMITED ON USERS
 
-And as well granted with 'CONNECT' and 'RESOURCE'. It's up to you
-to do decide how to manage users, change quotas, table spaces and
-other.
+And the user is also granted 'CONNECT' and 'RESOURCE'. It's up to you
+to do decide how to manage users, change quotas, table spaces, etc.
 
-RT has option DatabaseName which is used to define SID of
-the Oracle database. You don't have to setup TWO_TASK environment
-variable or other helpers files for connection.
+RT has an option $DatabaseName which is used to define the SID of
+the Oracle database. You don't have to set up the TWO_TASK environment
+variable or any helper files for establishing connections.
 
 Example:
-    
+
     ./configure \
         --with-db-type=Oracle \
         --with-db-database=XE \
@@ -27,15 +27,14 @@ Example:
         --with-db-rt-pass=rtdb1secret \
         ... other configure options ...
 
-This's all specifics of deployment on Oracle you should be aware
-of. To complete installation you must follow general instructions
-in the README file.
+That should be enough to get you started on Oracle, but to complete
+installation you must follow the general instructions in the README file.
 
 As with all databases it is important to analyze the schema and get
-current statistics after any significant dataset change.  Oracle's
+current statistics after every significant dataset change.  Oracle's
 cost-based optimizer can provide particularly bad performance when the
-schema statistics are significantly inaccurate.  To analyze the schema
-of a user called rt, execute the following from within sqlplus:
+schema statistics are inaccurate.  To analyze the schema of the user
+called RT, execute the following from within sqlplus:
 
   execute dbms_utility.analyze_schema( 'RT', 'estimate');