send v0.2 to CRAN

Author: pachadotdev

.github/CONTRIBUTING.md

@@ -12,7 +12,7 @@ You can find the `.R` file that generates the `.Rd` by reading the comment in th
 
 ## Bigger changes
 
-If you want to make a bigger change, it's a good idea to first file an issue and make sure someone from the team agrees that it’s needed. 
+If you want to make a bigger change, it's a good idea to first file an issue and make sure someone from the team agrees that it's needed. 
 If you’ve found a bug, please file an issue that illustrates the bug with a minimal 
 [reprex](https://www.tidyverse.org/help/#reprex) (this will also help you write a unit test, if needed).
 

.github/SUPPORT.md

@@ -29,7 +29,7 @@ For example, you'd simply remove `is:open` to search _all_ issues in the repo, o
 ## What happens next?
 
 To be as efficient as possible, development of tidyverse packages tends to be very bursty, so you shouldn't worry if you don't get an immediate response.
-Typically we don't look at a repo until a sufficient quantity of issues accumulates, then there’s a burst of intense activity as we focus our efforts. 
+Typically we don't look at a repo until a sufficient quantity of issues accumulates, then there's a burst of intense activity as we focus our efforts. 
 That makes development more efficient because it avoids expensive context switching between problems, at the cost of taking longer to get back to you. 
 This process makes a good reprex particularly important because it might be multiple months between your initial report and when we start working on it. 
 If we can’t reproduce the bug, we can’t fix it!

CRAN-SUBMISSION

@@ -1,3 +1,3 @@
-Version: 0.1.0
-Date: 2025-10-06 11:22:23 UTC
-SHA: c3501c11bf20bf000e5054c3e35259f501857aba
+Version: 0.2.0
+Date: 2025-10-07 19:06:29 UTC
+SHA: c05c5a8f838146c90d93e3f07c878466eea6c553

README.Rmd

@@ -67,7 +67,7 @@ cpp4r is a header only library with no hard dependencies and does not use a shar
 
 ## Vendoring
 
-You can [vendor](https://cpp4r.org/articles/motivations.html#vendoring) the current installed version of cpp4r headers into your package with `cpp4r::vendor()`.
+You can [vendor](https://cpp4r.org/articles/01-motivations.html) the current installed version of cpp4r headers into your package with `cpp4r::vendor()`.
 
 The [cpp4rvendor](https://github.com/pachadotdev/cpp4r/tree/main/cpp4rtest) package shows an example of vendoring cpp4r headers.
 
@@ -80,7 +80,7 @@ Please open an issue or email me. I will do my best to respond before 48 hours.
 
 ## Contributing
 
-Contributions are welcome! Please see the [internals vignette](https://cpp4r.org/articles/14-internals.html) for details about design choices and coding style.
+Contributions are welcome! Please see the [internals vignette](https://cpp4r.org/articles/15-internals.html) for details about design choices and coding style.
 
 ## Code of Conduct
 

README.md

@@ -72,13 +72,19 @@ packages without fear of compile-time and run-time mismatches.
 
 ## Vendoring
 
-You can
-[vendor](https://cpp4r.org/articles/00-motivations.html#vendoring) the
+You can [vendor](https://cpp4r.org/articles/01-motivations.html) the
 current installed version of cpp4r headers into your package with
 `cpp4r::vendor()`.
 
-This ensures the headers will remain unchanged until you explicitly
-update them.
+The
+[cpp4rvendor](https://github.com/pachadotdev/cpp4r/tree/main/cpp4rtest)
+package shows an example of vendoring cpp4r headers.
+
+Vendoring ensures the headers will remain unchanged until you explicitly
+update them. The advantage is that your package will not break if there
+are breaking changes in future versions of cpp4r. The disadvantage is
+that you will not get bug fixes and new features unless you update the
+vendored headers.
 
 ## Getting help
 
@@ -88,7 +94,7 @@ hours.
 ## Contributing
 
 Contributions are welcome! Please see the [internals
-vignette](https://cpp4r.org/articles/14-internals.html) for details
+vignette](https://cpp4r.org/articles/15-internals.html) for details
 about design choices and coding style.
 
 ## Code of Conduct

cpp4rols/README.md

@@ -10,7 +10,7 @@
 The goal of cpp4rdummyols is to show how to use cpp4r and solve a
 specific Linear Algebra problem, which is to obtain the OLS estimator,
 in the most naive way Use this only for elemental examples, not for
-actual estimation. There is a good explanation about why R’s lm()
+actual estimation. There is a good explanation about why R's lm()
 function uses a QR decomposition instead of a naive computation of the
 form (X’X)-1(X’Y) as I did here. See
 <http://madrury.github.io/jekyll/update/statistics/2016/07/20/lm-in-R.html>.
@@ -43,7 +43,7 @@ naive_ols(X, Y)
 #> [2,] -5.344472
 ```
 
-Now let’s compare with the `lm()` function from R:
+Now let's compare with the `lm()` function from R:
 
 ``` r
 coef(lm(mpg ~ wt, data = mtcars))

cran-comments.md

@@ -1 +1,23 @@
-This is a new package submission.
+Dear CRAN Team:
+
+I have fixed these noted in your last email:
+
+  Possibly misspelled words in DESCRIPTION:
+    ABI (19:71)
+    ALTREP (18:5)
+    Roxygen (21:41)
+    nullable (22:29, 23:25)
+    vendoring (20:24)
+
+  Found the following (possibly) invalid URLs:
+    URL: https://cpp4r.org/articles/00-motivations.html#vendoring
+      From: README.md
+      Status: 404
+      Message: Not Found
+    URL: https://cpp4r.org/articles/14-internals.html
+      From: README.md
+      Status: 404
+      Message: Not Found
+
+Best,
+MVS

dev/config_attachment.yaml

@@ -0,0 +1 @@
+spelling::update_wordlist()