From 2da0e56c2957f51b1e3fbc898e91523aed9a383e Mon Sep 17 00:00:00 2001 From: njtierney Date: Fri, 15 Mar 2024 14:42:33 +1100 Subject: [PATCH] minor tweaks to README wording --- README.Rmd | 4 ++-- README.md | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.Rmd b/README.Rmd index bd45d7e..dec2c3d 100644 --- a/README.Rmd +++ b/README.Rmd @@ -51,7 +51,7 @@ remotes::install_github("njtierney/geotargets") ## A note on development -`geotargets` is still undergoing development, and we would love for people to use the package to kick the tyres. We are using it in our own work, but feel it is appropriate that users use the package with the understanding the API could change in subtle or breaking ways. +`geotargets` is still undergoing development, and we would love for people to use the package to kick the tyres. We are using it in our own work, but want users to know that the API could change in subtle or breaking ways. # Examples @@ -62,7 +62,7 @@ Below we show two examples of target factories: You would use these in place of `tar_target()` in your targets pipeline, when you are doing work with terra raster or terra vector data. -It is a bit tricky to implement targets workflows in a README, but if you would like to see and download working examples for yourself, see the repo, [demo-geotargets](https://github.com/njtierney/demo-geotargets) +It is a bit tricky to implement targets workflows in a README, but if you would like to see and download working examples for yourself, see the repo, [demo-geotargets](https://github.com/njtierney/demo-geotargets). ## `tar_terra_rast()`: targets with terra rasters diff --git a/README.md b/README.md index 278a2ca..c5c1ef6 100644 --- a/README.md +++ b/README.md @@ -50,8 +50,8 @@ remotes::install_github("njtierney/geotargets") `geotargets` is still undergoing development, and we would love for people to use the package to kick the tyres. We are using it in our own -work, but feel it is appropriate that users use the package with the -understanding the API could change in subtle or breaking ways. +work, but want users to know that the API could change in subtle or +breaking ways. # Examples @@ -66,7 +66,7 @@ when you are doing work with terra raster or terra vector data. It is a bit tricky to implement targets workflows in a README, but if you would like to see and download working examples for yourself, see the repo, -[demo-geotargets](https://github.com/njtierney/demo-geotargets) +[demo-geotargets](https://github.com/njtierney/demo-geotargets). ## `tar_terra_rast()`: targets with terra rasters