quarto fixes + wording

_quarto.yml

@@ -23,8 +23,7 @@ website:
             url: https://github.com/r-releases/help
       - icon: rocket-takeoff
         href: https://r-releases.r-universe.dev/
-  body-footer: |
-    <br />&copy; 2024 the R-releases project.
+  page-footer: "&copy; 2024 the R-releases project."
 
 format:
   html:

index.qmd

@@ -8,4 +8,4 @@ R-releases is a community-curated, maintainer-driven repository of R package rel
 
 Anyone can contribute packages in the GitHub repository at <https://github.com/r-releases/contributions>. Once a package is registered, [R-universe](https://r-universe.dev/) automatically builds and checks every new release and makes it available to install from <https://r-releases.r-universe.dev/>. Package maintainers have complete control over deployment.
 
-The R-releases initiative originated from the [R Consortium Repositories Working Group](https://github.com/RConsortium/r-repositories-wg).
+The R-releases project originated from the [R Consortium Repositories Working Group](https://github.com/RConsortium/r-repositories-wg).

users.qmd

@@ -10,7 +10,7 @@ Simply add R-releases to your repository settings:
 options(repos = c("https://r-releases.r-universe.dev", getOption("repos")))
 ```
 
-R natively supports multiple repositories as a core language feature, and the above only needs to be set once per session. We recommend adding it to your `.Rprofile` so that it is always available.
+R supports multiple repositories as a core language feature, and the above only needs to be set once per session. We recommend adding it to your `.Rprofile` so that it is always available.
 
 Alternatively, to prioritize CRAN over R-releases:
 
@@ -28,20 +28,20 @@ By [contributing](contributors.html) a package to R-releases, you may convenient
 
 ## A guarantee of package availability
 
-R-releases is designed to work seamlessly alongside CRAN. By prioritizing CRAN in the settings above, you can choose to still get your packages from CRAN, only using R-releases as a fall-back.
+R-releases is designed to work seamlessly alongside CRAN. By prioritizing CRAN in the settings above, you can continue to get your packages from CRAN, only using R-releases as a fall-back.
 
 A package may become unavailable on CRAN at any time due to its strict archival policy.
 
-- Sometimes due to the archival of a dependency, and outside the direct control of the maintainer.
+- Sometimes due to the archival of a dependency, and outside the maintainer's direct control.
 - Situations can be temporary, but may take an extended time to resolve.
 
 By [contributing](contributors.html) a package that you rely on, you can ensure that it remains available for your critical workflows.
 
 ## A direct distribution channel from maintainers
 
-Maintainers may choose to use R-releases as a faster release channel, especially for packages under intensive development. 
+Maintainers may use R-releases as a faster release channel, especially for packages under intensive development. 
 
-CRAN is first and foremost an archival network, and its policy restricts the frequency of package updates. R-releases allows the timely dissemination of newer package versions containing critical updates or bug fixes.
+CRAN is first and foremost an archival network, and its policy restricts the frequency of package updates. R-releases allows timely dissemination of newer package versions containing critical updates or bug fixes.
 
-If a package maintainer recommends you to install a package from R-releases, please prioritize R-releases in front of CRAN in the repository settings above.
+If a package maintainer recommends that you install a package from R-releases, please prioritize R-releases in front of CRAN in the repository settings above.