GH username

Author: maelle

maintenance_curation.Rmd

@@ -79,7 +79,7 @@ packages that fall out of scope for peer review.
 - Archived packages can be unarchived when the old or a new maintainer
   is willing to address the problems and wants to revive the
   package. For that please [contact rOpenSci](https://ropensci.org/contact/).
-  They are transferred to the rOpenSci Labs organization.
+  They are transferred to the ropenscilabs organization.
 
 ## Peer-reviewed packages {#peer-reviewed-packages}
 
@@ -89,7 +89,7 @@ community and have passed through peer review. They need to be
 at the time of submission to be reviewed.
 
 - Upon acceptance, these peer-reviewed packages are transferred from
-  the author's GitHub to the rOpenSci GitHub organization 
+  the author's GitHub to the "ropensci" GitHub organization 
   or alternatively tracked by adding them to a [JSON file](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json).
 
 - Peer-reviewed packages will be in the registry tagged as
@@ -174,10 +174,10 @@ at unconferences
 - Biannually or annually, rOpenSci will contact incubator maintainers
   about repositories at least three months old, inquiring about
   development status and author preferences for migration to
-  peer-review, rOpenSci-archive, or to author organizations. Based
+  peer-review, ropensci-archive, or to author organizations. Based
   on the response, the package will be migrated immediately, peer review
   will be initiated, or migration will be deferred to the next
-  review. Incubator packages will be migrated to the ROpenSci-archive by
+  review. Incubator packages will be migrated to the ropensci-archive by
   default after one year, following [transfer guidance](#archivalguidance).
 
 - Archived incubator packages will gain the "archived" type.

softwarereview_editor.Rmd

@@ -31,7 +31,7 @@ If you're a guest editor, thanks for helping! Please contact the editor who invi
 
 ### Upon submission: {#upon-submission}
 
-- Submission will automatically generate package check output from the rOpenSci-review-bot. The check results should be examined for any outstanding issues (most exceptions will need to be justified by the author in the particular context of their package). Checks can be re-run after any package change with the comment `@ropensci-review-bot check package`.
+- Submission will automatically generate package check output from the ropensci-review-bot. The check results should be examined for any outstanding issues (most exceptions will need to be justified by the author in the particular context of their package). Checks can be re-run after any package change with the comment `@ropensci-review-bot check package`.
 - For statistical submissions (identifiable as "Submission Type: Stats" in issue template), add the "stats" label to the issue (if not already added).
 - Check that the issue template has been properly filled out. Most common oversights and omissions should be caught and noted by the bot, but a manual check always helps. Editors can edit templates directly for minor fixes, or may direct authors to fill any mandatory template fields that may be missing.
 - The checking system is rebuilt every Tuesday at 00:01 UTC, and can take a couple of hours. If automatic checks fail around that time, wait a few hours and try again.
@@ -112,7 +112,7 @@ Each submission should be reviewed by *two* package reviewers. Although it is fi
 ### After review: {#after-review}
 
 - `@ropensci-review-bot approve <package-name>`
-- *If the original repository wishes to keep the package in their own GitHub organization rather than transfer to yOpenSci, add a line with the repository URL to [this repos list](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) to ensure the package gets included in rOpenSci package registry.*
+- *If the original repository wishes to keep the package in their own GitHub organization rather than transfer to ropensci, add a line with the repository URL to [this repos list](https://github.com/ropensci/roregistry/blob/gh-pages/info/not_transferred.json) to ensure the package gets included in rOpenSci package registry.*
 - Nominate a package to be featured in an rOpenSci blog post or tech note if you think it might be of high interest. Please note in the software review issue one or two things the author could highlight, and tag `@ropensci/blog-editors` for follow-up.
 - If authors maintain a gitbook that is at least partly about their
   package, contact [an rOpenSci staff member](https://ropensci.org/about/#team) so they might contact the authors