From 281c33ce67a8063b22055e26f68de2e8a9bbfa51 Mon Sep 17 00:00:00 2001 From: David Dooling Date: Thu, 29 Oct 2020 16:26:59 -0500 Subject: [PATCH] Fix admonition format [changelog:fixed] --- docs/developer/local-quick-start.md | 4 ++-- docs/developer/sdm-concepts.md | 6 +++--- docs/getting-started.md | 7 ++++--- docs/user/admin/integrations/supported-integrations.md | 9 +++++---- 4 files changed, 14 insertions(+), 12 deletions(-) diff --git a/docs/developer/local-quick-start.md b/docs/developer/local-quick-start.md index 0433a53cf..13a1ff235 100644 --- a/docs/developer/local-quick-start.md +++ b/docs/developer/local-quick-start.md @@ -41,8 +41,8 @@ bash support). npm install -g @atomist/cli !!! Note - If you already have an SDM in your organization, you can skip step 2, - and instead clone the repository containing your SDM. + If you already have an SDM in your organization, you can skip step 2, + and instead clone the repository containing your SDM. 2. Create a local software delivery machine (SDM). This is going to create a new project in the Atomist projects directory (which diff --git a/docs/developer/sdm-concepts.md b/docs/developer/sdm-concepts.md index ccaa63e2a..77980a799 100644 --- a/docs/developer/sdm-concepts.md +++ b/docs/developer/sdm-concepts.md @@ -92,9 +92,9 @@ If you want the same events to be sent to multiple SDMs, just make sure the SDMs have different names. !!! note "Custom Ingestion" -Any custom ingestion types can only be registered once within an -Atomist workspace. Therefore it is recommended to register these -in a dedicated API client. + Any custom ingestion types can only be registered once within an + Atomist workspace. Therefore it is recommended to register these + in a dedicated API client. ## Event handling diff --git a/docs/getting-started.md b/docs/getting-started.md index 7bb9961bb..10c13b807 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -38,9 +38,10 @@ skills][catalog]. We're going to enable the GitHub Notifications Skill. Now you will get Slack notifications for all pushed commits, pull requests, and issues. -!!! tip "Note" You control which channels will receive notifications, so you may -want to start with just one repository linked to one Slack channel until you're -ready to add more. +!!! Tip + You control which channels will receive notifications, so you may + want to start with just one repository linked to one Slack channel until you're + ready to add more. [catalog]: https://go.atomist.com/catalog "Atomist Catalog of Skills" diff --git a/docs/user/admin/integrations/supported-integrations.md b/docs/user/admin/integrations/supported-integrations.md index 45866fcf7..7bd4bba5e 100644 --- a/docs/user/admin/integrations/supported-integrations.md +++ b/docs/user/admin/integrations/supported-integrations.md @@ -55,10 +55,11 @@ One of the tools you are most likely to integrate is Continuous Integration You can integrate Atomist with a custom CI tool by invoking Atomist hooks to send events around build and artifact creation. -!!! note CI tools are great for building and generating artifacts, but they're -often abused as a PaaS for `bash`. If you find your CI usage has you programming -in `bash` or YML, consider whether invoking such operations from Atomist event -handlers might be a better model. +!!! Note + CI tools are great for building and generating artifacts, but they're + often abused as a PaaS for `bash`. If you find your CI usage has you programming + in `bash` or YML, consider whether invoking such operations from Atomist event + handlers might be a better model. You can also use Atomist generators to create pre-defined CI files, and Atomist editors to keep them in synch, minimizing inconsistency across all your