Update docs/guides/modules/integration/pages/using-the-circleci-github-app-in-an-oauth-org.adoc

Co-authored-by: Rosie Yohannan <[email protected]>

Author: BeFunes

docs/guides/modules/integration/pages/using-the-circleci-github-app-in-an-oauth-org.adoc

@@ -184,12 +184,12 @@ If you run into an issue while attempting to authorize, submit a request through
 Dual integration provides the following benefits:
 
 * Access to new GitHub App features while maintaining existing OAuth pipelines. Key functionality enabled through the GitHub App integration includes the following:
-    ** The option to have **multiple pipelines in the same project**, each defined in its own YAML file.
-    ** The possibility to set up your pipelines so that the **config file and the application code are stored in different repositories**. Refer to the link:https://circleci.com/changelog/unlocking-any-cross-repo-pipeline-and-trigger-setups-including-central/[changelog entry] for more information.
-    ** A **more flexible trigger system**, with each pipeline having any number of VCS or non-VCS triggers. This includes:
-       *** **Non-repo based triggers**: xref:orchestrate:custom-webhooks.adoc[Custom webhooks] enable triggering builds from any system that can emit webhook events. Refer to our link:https://discuss.circleci.com/t/product-update-trigger-pipelines-from-anywhere-custom-webhooks/49864[community forum] for an example and known limitations.
-       *** **Cross-repo triggers**: Events in one repository can trigger builds on one or many other repositories.
-       *** **More GitHub events as triggers**: Pipelines can be set up to run on events other than "push", including pull request events, with more powerful customization of trigger conditions. For full details, see the xref:orchestrate:github-trigger-event-options.adoc[GitHub trigger event options] page.
+** The option to have *multiple pipelines in the same project*, each defined in its own YAML file.
+** The possibility to set up your pipelines so that the *config file and the application code are stored in different repositories*. Refer to the link:https://circleci.com/changelog/unlocking-any-cross-repo-pipeline-and-trigger-setups-including-central/[changelog entry] for more information.
+** A *more flexible trigger system*, with each pipeline having any number of VCS or non-VCS triggers. This includes:
+*** *Non-repo based triggers*: xref:orchestrate:custom-webhooks.adoc[Custom webhooks] enable triggering builds from any system that can emit webhook events. Refer to our link:https://discuss.circleci.com/t/product-update-trigger-pipelines-from-anywhere-custom-webhooks/49864[community forum] for an example and known limitations.
+*** *Cross-repo triggers*: Events in one repository can trigger builds on one or many other repositories.
+*** *More GitHub events as triggers*: Pipelines can be set up to run on events other than "push", including pull request events, with more powerful customization of trigger conditions. For full details, see the xref:orchestrate:github-trigger-event-options.adoc[GitHub trigger event options] page.
 * Gradual migration path for complex projects
 * New trigger options without disrupting current pipelines