From 0d5666f56c01986958f001bbd03e05728cf17317 Mon Sep 17 00:00:00 2001 From: Saranjeet Kaur Date: Tue, 3 Dec 2024 16:24:14 +0000 Subject: [PATCH 1/2] Change Developer -> Dev --- 09-documenting.Rmd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/09-documenting.Rmd b/09-documenting.Rmd index 1ac23d68..4feea58f 100644 --- a/09-documenting.Rmd +++ b/09-documenting.Rmd @@ -166,9 +166,9 @@ While an issue filed on Bugzilla means there is a known issue somewhere, that do If you decide to proofread, read a section of the documentation from start to finish, filing issues in Bugzilla for each major type of problem you find. It is best to avoid filing a single issue for an entire section containing multiple problems; instead, file several issues so that it is easier to break the work up for multiple people and more efficient review. -## Helping with the Developer's Guide +## Helping with the R Dev Guide -The Developer’s Guide (what you are reading now) uses the same process as the main R documentation, except for some small differences. The source lives in a [GitHub repository](https://github.com/r-devel/rdevguide/) and bug reports should be submitted to the [devguide GitHub tracker](https://github.com/r-devel/rdevguide/issues). +The R Dev Guide (what you are reading now) uses the same process as the main R documentation, except for some small differences. The source lives in a [GitHub repository](https://github.com/r-devel/rdevguide/) and bug reports should be submitted to the [devguide GitHub tracker](https://github.com/r-devel/rdevguide/issues). Our dev guide workflow uses continuous integration and deployment so changes to the dev guide are normally published when the pull request is merged. [How to contribute to this guide from the introduction.](#how-to-contribute-to-this-guide) From 1e157dc2f4a60a8fea11841fc957331ccc4c49cc Mon Sep 17 00:00:00 2001 From: Heather Turner Date: Tue, 3 Dec 2024 16:57:59 +0000 Subject: [PATCH 2/2] dev -> development --- 09-documenting.Rmd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/09-documenting.Rmd b/09-documenting.Rmd index 4feea58f..dff11e01 100644 --- a/09-documenting.Rmd +++ b/09-documenting.Rmd @@ -166,11 +166,11 @@ While an issue filed on Bugzilla means there is a known issue somewhere, that do If you decide to proofread, read a section of the documentation from start to finish, filing issues in Bugzilla for each major type of problem you find. It is best to avoid filing a single issue for an entire section containing multiple problems; instead, file several issues so that it is easier to break the work up for multiple people and more efficient review. -## Helping with the R Dev Guide +## Helping with the R Development Guide -The R Dev Guide (what you are reading now) uses the same process as the main R documentation, except for some small differences. The source lives in a [GitHub repository](https://github.com/r-devel/rdevguide/) and bug reports should be submitted to the [devguide GitHub tracker](https://github.com/r-devel/rdevguide/issues). +The R Development Guide (what you are reading now) uses the same process as the main R documentation, except for some small differences. The source lives in a [GitHub repository](https://github.com/r-devel/rdevguide/) and bug reports should be submitted to the [devguide GitHub tracker](https://github.com/r-devel/rdevguide/issues). -Our dev guide workflow uses continuous integration and deployment so changes to the dev guide are normally published when the pull request is merged. [How to contribute to this guide from the introduction.](#how-to-contribute-to-this-guide) +Our development guide workflow uses continuous integration and deployment so changes to the development guide are normally published when the pull request is merged. [How to contribute to this guide from the introduction.](#how-to-contribute-to-this-guide) ## Reporting documentation bugs