Fix release issues

README.Rmd

@@ -127,7 +127,7 @@ date-time object. However:
   the date which failed to parse and reports the considered date: making it much
   easier to figure out which dates supplied failed to parse and why. 
 2.  When imputing a missing day or month, there is no user-control over this
-  behaviour. For example, when imputing a missing month, the user may wish to
+  behavior. For example, when imputing a missing month, the user may wish to
   impute July,  the middle of the year, instead of January. However, January will
   always be imputed in `{lubridate}`. In `datefixR`, this behaviour can be
   controlled by the `month.impute` argument.
@@ -159,10 +159,10 @@ consistently being over 3 times slower (testing up to 10,000 dates).
 of time faster than `datefixR` and `lubridate::parse_date_time2()`, which is
 written in C but only allows numeric dates, is even faster. If you are don't mind
 not having control over imputation, do not expect to have to deal with many
-unparsed dates, are confident you will specify all potential formats the
-supplied dates will be in, and you have many many dates to standardise (hundreds
-of thousands or more), `{lubridate}`'s functions may be a better option than
-`datefixR`. 
+dates which fail to parse, are confident you will specify all potential formats
+the supplied dates will be in, and you have many many dates to standardize
+(hundreds of thousands or more), `{lubridate}`'s functions may be a better
+option than `datefixR`. 
 
 ### Not actively maintained alternatives
 

README.md

@@ -131,7 +131,7 @@ date-time object. However:
     reports the considered date: making it much easier to figure out
     which dates supplied failed to parse and why.
 2.  When imputing a missing day or month, there is no user-control over
-    this behaviour. For example, when imputing a missing month, the user
+    this behavior. For example, when imputing a missing month, the user
     may wish to impute July, the middle of the year, instead of January.
     However, January will always be imputed in `{lubridate}`. In
     `datefixR`, this behaviour can be controlled by the `month.impute`
@@ -165,11 +165,11 @@ than `datefixR`: consistently being over 3 times slower (testing up to
 an order of magnitude of time faster than `datefixR` and
 `lubridate::parse_date_time2()`, which is written in C but only allows
 numeric dates, is even faster. If you are don’t mind not having control
-over imputation, do not expect to have to deal with many unparsed dates,
-are confident you will specify all potential formats the supplied dates
-will be in, and you have many many dates to standardise (hundreds of
-thousands or more), `{lubridate}`’s functions may be a better option
-than `datefixR`.
+over imputation, do not expect to have to deal with many dates which
+fail to parse, are confident you will specify all potential formats the
+supplied dates will be in, and you have many many dates to standardize
+(hundreds of thousands or more), `{lubridate}`’s functions may be a
+better option than `datefixR`.
 
 ### Not actively maintained alternatives
 

codemeta.json

@@ -8,13 +8,13 @@
   "codeRepository": "https://github.com/nathansam/datefixR",
   "issueTracker": "https://github.com/nathansam/datefixR/issues",
   "license": "https://spdx.org/licenses/GPL-3.0",
-  "version": "0.1.4.9000",
+  "version": "0.1.5",
   "programmingLanguage": {
     "@type": "ComputerLanguage",
     "name": "R",
     "url": "https://r-project.org"
   },
-  "runtimePlatform": "R version 4.1.3 (2022-03-10)",
+  "runtimePlatform": "R version 4.2.0 (2022-04-22)",
   "provider": {
     "@id": "https://cran.r-project.org",
     "@type": "Organization",
@@ -86,18 +86,6 @@
       "version": ">= 4.0.0"
     },
     "2": {
-      "@type": "SoftwareApplication",
-      "identifier": "lifecycle",
-      "name": "lifecycle",
-      "provider": {
-        "@id": "https://cran.r-project.org",
-        "@type": "Organization",
-        "name": "Comprehensive R Archive Network (CRAN)",
-        "url": "https://cran.r-project.org"
-      },
-      "sameAs": "https://CRAN.R-project.org/package=lifecycle"
-    },
-    "3": {
       "@type": "SoftwareApplication",
       "identifier": "stringr",
       "name": "stringr",
@@ -111,7 +99,7 @@
     },
     "SystemRequirements": null
   },
-  "fileSize": "515.975KB",
+  "fileSize": "512.052KB",
   "citation": [
     {
       "@type": "SoftwareSourceCode",
@@ -125,7 +113,7 @@
       "name": "{datefixR}: Fix Really Messy Dates in {R}",
       "identifier": "10.5281/zenodo.5655311",
       "url": "https://CRAN.R-project.org/package=datefixR",
-      "description": "R package version 0.1.4.9000",
+      "description": "R package version 0.1.5",
       "@id": "https://doi.org/10.5281/zenodo.5655311",
       "sameAs": "https://doi.org/10.5281/zenodo.5655311"
     }