Update to latest (#3486)

docs/wiki/Fetching latest changes - Scenario 1 Consume library.md

@@ -34,3 +34,4 @@ If your copy deviates from the upstream version due to customizations you applie
 
 To test and publish updated modules, follow the best option for your scenario in [Test and publish modules](./Getting%20started%20-%20Scenario%201%20Consume%20library#3-test-and-publish-modules)
 
+> **Note:** It may be the case that names of modules changed. While this won't have an effect on any existing solution you may have based on the library, it will mean that for new module versions you will need to adopt the new module names.

docs/wiki/Fetching latest changes - Scenario 2 Module library and CI environment.md

@@ -23,7 +23,7 @@ Rename your local repository. Assuming the local repository location is `'D:\Res
 
 You have a public fork of public CARML source repository in your target organization.
 
-1. Keep your fork synced to the fork upstream repository, on the GitHub web UI or through the GitHub CLI or the command-line, as explaind in [Syncing a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) documentation.
+1. Keep your fork synced to the fork upstream repository, on the GitHub web UI or through the GitHub CLI or the command-line, as explained in [Syncing a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) documentation.
 1. Sync your local copy of the fork taking care of eventual customizations you can have in place.
 
 </details>