Spellchecked

Signed-off-by: Ben Ostrowsky <sylvar@gmail.com>

diff --git a/docs/reports/reporter_add_data_source.txt b/docs/reports/reporter_add_data_source.txt
index df97c45..4368506 100644 (file)
--- a/docs/reports/reporter_add_data_source.txt
+++ b/docs/reports/reporter_add_data_source.txt
@@ -23,7 +23,7 @@ data source.
 . Add a new class to _fm_IDL.xml_ for your data source.
 . Restart the affected services to see the new data source in Reporter.
 
-There are two possbile sources for new data sources:
+There are two possible sources for new data sources:
 
 indexterm:[PostgreSQL]
 
@@ -32,7 +32,7 @@ indexterm:[SQL]
 * An SQL query built directly into the class definition in _fm_IDL.xml_. You can 
 use this method if you are only going to access this data source through the 
 Evergreen reporter and/or cstore code that you write.
-* A new table or view in the Evergreen PostgresSQL database on which a class 
+* A new table or view in the Evergreen PostgreSQL database on which a class 
 definition in _fm_IDL.xml_. You can use this method if you want to be able to 
 access this data source through directly through SQL or using other reporting tool.
 
@@ -56,7 +56,7 @@ need to use a table to store the results of a query for performance reasons.
 
 To develop and test queries, views, and tables, you will need
 
-* Access to the Evergree PostgreSQL database at the command line. This is 
+* Access to the Evergreen PostgreSQL database at the command line. This is 
 normally the psql application. You 
 can access the Postgres documentation at the 
 http://http://www.postgresql.org/docs/[Official Postgres documentation] for 
@@ -72,7 +72,7 @@ for contribution to the core Evergreen code, create the Views and Tables in the
 extend_reporter schema. This schema is intended to be used for local 
 customizations and will not be modified during upgrades to the Evergreen system.
 
-You should make that you have an appropriate version control pocess for the SQL 
+You should make that you have an appropriate version control process for the SQL 
 used to create you data sources.
 
 Here's an example of a view created to incorporate some locally defined user 

diff --git a/docs/reports/reporter_create_templates.txt b/docs/reports/reporter_create_templates.txt
index 25fdbee..e741e1a 100644 (file)
--- a/docs/reports/reporter_create_templates.txt
+++ b/docs/reports/reporter_create_templates.txt
@@ -21,7 +21,7 @@ add all fields from the table at the highest source level. Run a report and chec
 to see that you get results that seem reasonable. Then clone the report, add any 
 filters on fields at that level and run another report. Then drill down to the 
 next table and add any required fields. Run another report. Add any filters at 
-that level. Run another report. Continue until you’ve drilled down to all the 
+that level. Run another report. Continue until you've drilled down to all the 
 fields you need and added all the filters. This might seem time consuming and 
 you will end up cloning your initial report several times. However, it will help 
 you to check the correctness of your results, and will help to debug if you run 
@@ -160,7 +160,7 @@ Selected Fields_
 image::media/create-template-20.png[create-template-20]
 +
 . _Check Out Date/Time_ will appear in the _Displayed Fields_ pane. In the report 
-it will appear as a year and month _(YYYY-MM)_ corresponding to the selected tranform.
+it will appear as a year and month _(YYYY-MM)_ corresponding to the selected transform.
 +
 image::media/create-template-21.png[create-template-21]
 +

diff --git a/docs/reports/reporter_daemon.txt b/docs/reports/reporter_daemon.txt
index d7d0af8..96223ec 100644 (file)
--- a/docs/reports/reporter_daemon.txt
+++ b/docs/reports/reporter_daemon.txt
@@ -30,7 +30,7 @@ run; defaults to 10
 /tmp/reporter-LOCK
 * *concurrency=integer*: number of reporter daemon processes to run; defaults to 
 1
-* *boostrap=filename*: OpenSRF bootstrap configuration file; defaults to 
+* *bootstrap=filename*: OpenSRF bootstrap configuration file; defaults to 
 /openils/conf/opensrf_core.xml
 
 
@@ -41,7 +41,7 @@ the reporter daemon can be started.
 
 Remember that if the server is restarted, the reporter daemon will need to be 
 restarted before you can view reports unless you have configured your server to 
-start the daemonautomatically at start up time. 
+start the daemon automatically at startup time. 
 ==============
 
 Stopping the Reporter Daemon