refactor: bincraftR -> bincraft

README.md

@@ -9,14 +9,14 @@ This project offers a framework for creating R package binaries on Linux across
 
 It achieves this through the integration of several components:
 
-- **R package `bincraftR`**
+- **R package `bincraft`**
 - **Containerfiles** that define the build toolchain for each distribution
 - **S3 storage** for storing the compiled binaries
 - **PostgreSQL database** for recording build logs
 
 ## R Package
 
-The R package [`bincraftR`](https://gitlab.com/devxy/r-package-binaries/bincraftr) powers everything.
+The R package [`bincraft`](https://gitlab.com/devxy/r-package-binaries/bincraft) powers everything.
 It provides the following functionality:
 
 - build binaries
@@ -25,7 +25,7 @@ It provides the following functionality:
 - update the package index files (`PACKAGES*`)
 - store build metadata, including error logs, in a PostgreSQL database
 
-See the function reference on the [pkgdown site](https://devxy.gitlab.io/r-package-binaries/bincraftr/) for a full overview.
+See the function reference on the [pkgdown site](https://devxy.gitlab.io/r-package-binaries/bincraft/) for a full overview.
 
 The focus of the R package is on usability rather than minimizing dependencies.
 The individual containerfiles include the package along with its dependencies.
@@ -68,7 +68,7 @@ Currently, the {cranlike} and {desc} packages only work with files on a local fi
 This is infeasible if the goal is to store binaries in S3.
 Storing binaries permanently on a disk-based file system would incur significantly higher costs, especially when operating in the cloud.
 
-Hence, [{cranlike}](https://devxy.gitlab.io/r-package-binaries/bincraftr/) and [{desc}](https://github.com/pat-s/desc/tree/description-from-remote) were forked to handle files in S3 (through {s3fs}).
+Hence, [{cranlike}](https://devxy.gitlab.io/r-package-binaries/bincraft/) and [{desc}](https://github.com/pat-s/desc/tree/description-from-remote) were forked to handle files in S3 (through {s3fs}).
 
 ### Resources