From ff840d36062301d9f0e48093e3547a4ee46ac70c Mon Sep 17 00:00:00 2001
From: Perkles <otaviocha@gmail.com>
Date: Fri, 4 Jun 2021 17:15:43 -0300
Subject: [PATCH] Add title naming convention to reusables

---
 data/reusables/actions/actions-group-concurrency.md  | 4 ++--
 data/reusables/github-actions/actions-on-examples.md | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/data/reusables/actions/actions-group-concurrency.md b/data/reusables/actions/actions-group-concurrency.md
index 493e81cb45..e24fd257b7 100644
--- a/data/reusables/actions/actions-group-concurrency.md
+++ b/data/reusables/actions/actions-group-concurrency.md
@@ -1,6 +1,6 @@
 When a concurrent job or workflow is queued, if another job or workflow using the same concurrency group in the repository is in progress, the queued job or workflow will be `pending`. Any previously pending job or workflow in the concurrency group will be canceled. To also cancel any currently running job or workflow in the same concurrency group, specify `cancel-in-progress: true`.
 
-##### Examples using concurrency and the default behavior
+##### Examples: Using concurrency and the default behavior
 
 {% raw %}
 ```yaml
@@ -14,7 +14,7 @@ concurrency: ci-${{ github.ref }}
 ```
 {% endraw %}
 
-##### Example using concurrency to cancel any in-progress job or run
+##### Example: Using concurrency to cancel any in-progress job or run
 
 {% raw %}
 ```yaml
diff --git a/data/reusables/github-actions/actions-on-examples.md b/data/reusables/github-actions/actions-on-examples.md
index 06efe2e4ea..1d16cbd839 100644
--- a/data/reusables/github-actions/actions-on-examples.md
+++ b/data/reusables/github-actions/actions-on-examples.md
@@ -1,18 +1,18 @@
-##### Example using a single event
+##### Example: Using a single event
 
 ```yaml
 # Triggered when code is pushed to any branch in a repository
 on: push
 ```
 
-##### Example using a list of events
+##### Example: Using a list of events
 
 ```yaml
 # Triggers the workflow on push or pull request events
 on: [push, pull_request]
 ```
 
-##### Example using multiple events with activity types or configuration
+##### Example: Using multiple events with activity types or configuration
 
 If you need to specify activity types or configuration for an event, you must configure each event separately. You must append a colon (`:`) to all events, including events without configuration.