openmrs · denniskigen · Dec 8, 2023 · Dec 7, 2023
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -1,10 +1,13 @@
-## Requirements
-- [ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a [conventional commit](https://o3-dev.docs.openmrs.org/#/getting_started/contributing?id=your-pr-title-should-indicate-the-type-of-change-it-is) label. See existing PR titles for inspiration.
+# Requirements
 
-#### For changes to apps
-- [ ]  My work conforms to the [**OpenMRS 3.0 Styleguide**](https://om.rs/styleguide) and **design documentation**.
+- [ ] This PR has a title that briefly describes the work done including the ticket number. Ensure your PR title includes a [conventional commit](https://o3-docs.openmrs.org/docs/frontend-modules/contributing#contributing-guidelines) label (such as `feat`, `fix`, or `chore`, among others). See existing PR titles for inspiration.
+
+## For changes to apps
+
+- [ ] My work conforms to the [**O3 Styleguide**](https://om.rs/styleguide) and [**design documentation**](https://om.rs/o3ui).
+
+## If applicable
 
-#### If applicable
 - [ ] My work includes tests or is validated by existing tests.
 - [ ] I have updated the [esm-framework mock](https://github.com/openmrs/openmrs-esm-core/blob/main/packages/framework/esm-framework/mock.tsx) to reflect any API changes I have made.
 

diff --git a/README.md b/README.md
@@ -158,8 +158,7 @@ yarn link path/to/openmrs-esm-core/packages/framework/esm-api
 ```
 
 This satisfies the build tooling, but we must do one more step to get the frontend
-to load these dependencies at runtime
-(see docs on [Runtime Dependencies](https://o3-dev.docs.openmrs.org/#/main/deps)).
+to load these dependencies at runtime.
 
 Here, there are two options:
 
@@ -175,9 +174,6 @@ Then run your patient chart dev server as usual, with `yarn start`.
 
 #### Method 2: Using import map overrides
 
-Read the [dev documentation](https://o3-dev.docs.openmrs.org/#/getting_started/setup?id=import-map-overrides)
-about import map overrides if you have not already.
-
 In `esm-core`, start the app shell with `yarn run:shell`. Then, in the patient chart repository, `cd` into whatever packages you are working on and run `yarn serve` from there. Then use the import map override tool in the browser to tell the frontend to load your local patient chart packages.
 
 #### Once it's working

diff --git a/docs/.nojekyll b/docs/.nojekyll
diff --git a/docs/CNAME b/docs/CNAME
diff --git a/docs/README.md b/docs/README.md
diff --git a/docs/_sidebar.md b/docs/_sidebar.md
diff --git a/docs/getting_started/contributing.md b/docs/getting_started/contributing.md
diff --git a/docs/getting_started/prerequisites.md b/docs/getting_started/prerequisites.md
diff --git a/docs/getting_started/release_and_deployment.md b/docs/getting_started/release_and_deployment.md