Prep for CRAN release

DESCRIPTION

@@ -1,13 +1,14 @@
 Package: otpr
 Title: An R Wrapper for the 'OpenTripPlanner' REST API
-Version: 0.2.0.9000
+Version: 0.3.0
 Authors@R: c(
     person("Marcus", "Young", email = "M.A.Young@soton.ac.uk", role = c("aut", "cre"))
     )
 Description: A wrapper for the 'OpenTripPlanner' <http://www.opentripplanner.org/>
     REST API. Queries are submitted to the relevant 'OpenTripPlanner' API resource, the response
     is parsed and useful R objects are returned.
 License: MIT + file LICENSE
+Language: en-GB
 Encoding: UTF-8
 LazyData: true
 Imports:

NEWS.md

@@ -1,14 +1,16 @@
-# otpr 0.2.0.9000
+# otpr 0.3.0.9000
+
+# otpr 0.3.0
 
 ## New features
 
 * Added option to request information about each of the legs in a returned 
 transit itinerary. There is a new parameter available for `otp_get_times()` called 
 `includeLegs`. If this is set to TRUE (default is FALSE) and `detail` is also set
 to TRUE and `mode` includes a transit mode, then the list returned by the
-function will contain a third dataframe called `legs`. This contains a row for each
-leg of the trip. Information provided includes `departureWait` which is the
-length of time in minutes required to wait for start of the leg.
+function will contain a third dataframe called `legs`. This consists of a row for
+each leg of the trip. Information provided includes `departureWait` which is the
+length of time in minutes required to wait for the start of a leg.
 
 * Added support for time zones (#7). The OTP API returns itinerary start and end
 times as EPOCH values. otpr converts these to hh:mm:ss format using the `as.POSIXct()`
@@ -24,7 +26,7 @@ is set to the local system's time zone. If the router's graph is in a different
 time zone the user can specify it (for example, "Europe/Berlin").
     * The dataframe returned by `otp_get_times()` when the `detail` argument is set to
 TRUE now includes an additional 'time zone' column. This shows the time zone of 
-the returned itinerary start and end times. This makes explit what time zone
+the returned itinerary start and end times. This makes explicit what time zone
 these times are expressed in.