From 67af6769a77a81086a21d9d4bc48c11ecc446c8e Mon Sep 17 00:00:00 2001
From: Tim Otten <totten@civicrm.org>
Date: Tue, 22 Sep 2020 02:35:59 -0700
Subject: [PATCH] Partially normalize special headings in D8/D9 pages
---
docs/drupal8/index.md | 6 +++---
docs/drupal9/index.md | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/drupal8/index.md b/docs/drupal8/index.md
index b017895..30ec179 100644
--- a/docs/drupal8/index.md
+++ b/docs/drupal8/index.md
@@ -29,7 +29,7 @@ To download CiviCRM on a Drupal 8 site we'll need to ask [Composer](https://www.
Best practice is to use `composer require` locally or in dev/test and then deploy your `composer.lock` to staging and use `composer install` which requires less memory and implements the changes you've tested and committed to your repo!
<!-- markdownlint-enable MD046 -->
-### Expert Mode - Just the command
+### Expert mode - Just the command
To require the CiviCRM libraries on a Drupal 8 site you can use the following one-line command:
@@ -38,7 +38,7 @@ To require the CiviCRM libraries on a Drupal 8 site you can use the following on
* `composer require civicrm/civicrm-asset-plugin:'~1.0.0' civicrm/civicrm-{core,packages,drupal-8}:'~5.29'`
-### Guided Mode - More context and information
+### Guided mode - More context and information
!!! tip "Location, Location... Location"
You should always run `composer` commands from the top-level folder above the web and vendor folders, where in the same place as your `composer.json` file.
@@ -280,7 +280,7 @@ See [TLS for MySQL](/general/mysql_tls/) for introductory concepts and the setti
),
```
-### D8 <-> CiviCRM Integration modules {:#integration-modules}
+### Integration modules {:#integration-modules}
__Webform CiviCRM module__
diff --git a/docs/drupal9/index.md b/docs/drupal9/index.md
index 8683ebf..e896f3b 100644
--- a/docs/drupal9/index.md
+++ b/docs/drupal9/index.md
@@ -37,7 +37,7 @@ To download CiviCRM on a Drupal 9 site we'll need to ask [Composer](https://www.
Best practice is to use `composer require` locally or in dev/test and then deploy your `composer.lock` to staging and use `composer install` which requires less memory and implements the changes you've tested and committed to your repo!
<!-- markdownlint-enable MD046 -->
-### Expert Mode - Just the command
+### Expert mode - Just the command
To require the CiviCRM libraries on a Drupal 9 site you can use the following one-line command:
@@ -46,7 +46,7 @@ To require the CiviCRM libraries on a Drupal 9 site you can use the following on
* `composer require civicrm/civicrm-asset-plugin:'~1.0.0' civicrm/civicrm-{core,packages,drupal-8}:'~5.28'`
-### Guided Mode - More context and information
+### Guided mode - More context and information
!!! tip "Location, Location... Location"
You should always run `composer` commands from the top-level folder above the web and vendor folders, where in the same place as your `composer.json` file.
@@ -275,7 +275,7 @@ See [TLS for MySQL](/general/mysql_tls/) for introductory concepts and the setti
),
```
-### D8 <-> CiviCRM Integration modules {:#integration-modules}
+### Integration modules {:#integration-modules}
__Webform CiviCRM module__
--
GitLab