Fix wordo

lifecycle.Rmd

@@ -335,7 +335,7 @@ This supports a lifestyle where a user's default package library is managed in t
 But any project that has a specific, higher requirement for reproducibility is managed with renv.
 This keeps package updates triggered by work in project A from breaking the code in project B and also helps with collaboration and deployment.
 
-We suspect that package-specific libraries and tools like renv are currently under-utilized in the R world.
+We suspect that project-specific libraries and tools like renv are currently under-utilized in the R world.
 That is, lots of R users still use just one package library.
 Therefore, package maintainers still need to exercise considerable caution and care when they introduce breaking changes, regardless of what's happening with the version number.
 In @sec-lifecycle-stages-and-package, we describe how tidyverse packages approach this, supported by tools in the lifecycle package.