Closes #24 broken links to admiraldev

.github/CONTRIBUTING.md

@@ -3,7 +3,7 @@
 This outlines how to propose a change to the aok package. For more detailed info
 about contributing to {oak}, and other [pharmaverse
 packages](https://pharmaverse.org/), please see the [development process
-guide](https://pharmaverse.github.io/admiraldev/main/articles/development_process.html)
+guide](https://pharmaverse.github.io/admiraldev/articles/development_process.html)
 as well as other Developer Guides in the Articles section of the [{admiral}
 website](https://pharmaverse.github.io/admiral/cran-release/index.html)
 
@@ -23,7 +23,7 @@ feedback. Since we are not a 100% fully resourced software development team it
 might be that some issues will take longer to respond to depending on the amount
 of overall issues.
 
- * Familiarize yourself with our [programming strategy](https://pharmaverse.github.io/admiraldev/main/articles/programming_strategy.html), guidance for [GitHub usage](https://pharmaverse.github.io/admiraldev/main/articles/git_usage.html) and [unit testing](https://pharmaverse.github.io/admiraldev/main/articles/unit_test_guidance.html).
+ * Familiarize yourself with our [programming strategy](https://pharmaverse.github.io/admiraldev/articles/programming_strategy.html), guidance for [GitHub usage](https://pharmaverse.github.io/admiraldev/articles/git_usage.html) and [unit testing](https://pharmaverse.github.io/admiraldev/articles/unit_test_guidance.html).
 
  * All newly [created issues](https://github.com/pharmaverse/oak/issues) will be
 reviewed within the next backlog meeting and the creator will receive an

.github/pull_request_template.md

@@ -1,6 +1,6 @@
 Thank you for your Pull Request! We have developed this task checklist from the
 [Development Process
-Guide](https://pharmaverse.github.io/admiraldev/devel/articles/development_process.html)
+Guide](https://pharmaverse.github.io/admiraldev/articles/development_process.html)
 to help with the final steps of the process. Completing the below tasks helps to
 ensure our reviewers can maximize their time on your code as well as making sure
 the oak codebase remains robust and consistent.
@@ -18,13 +18,13 @@ Request Title (Use Edit button in top-right if you need to update)
 - [ ] Updated relevant unit tests or have written new unit tests, which should
 consider realistic data scenarios and edge cases, e.g. empty datasets, errors,
 boundary cases etc. - See 
-[Unit Test Guide](https://pharmaverse.github.io/admiraldev/devel/articles/unit_test_guidance.html#tests-should-be-robust-to-cover-realistic-data-scenarios)
+[Unit Test Guide](https://pharmaverse.github.io/admiraldev/articles/unit_test_guidance.html#tests-should-be-robust-to-cover-realistic-data-scenarios)
 - [ ] If you removed/replaced any function and/or function parameters, did you 
 fully follow the 
-[deprecation guidance](https://pharmaverse.github.io/admiraldev/devel/articles/programming_strategy.html#deprecation)?
+[deprecation guidance](https://pharmaverse.github.io/admiraldev/articles/programming_strategy.html#deprecation)?
 - [ ] Update to all relevant roxygen headers and examples, including keywords
 and families. Refer to the 
-[categorization of functions](https://pharmaverse.github.io/admiraldev/devel/articles/programming_strategy.html#categorization-of-functions) to tag appropriate keyword/family.
+[categorization of functions](https://pharmaverse.github.io/admiraldev/articles/programming_strategy.html#categorization-of-functions) to tag appropriate keyword/family.
 - [ ] Run `devtools::document()` so all `.Rd` files in the `man` folder and the
 `NAMESPACE` file in the project root are updated appropriately
 - [ ] Address any updates needed for vignettes and/or templates