style: Add bullet points before prerequisites

antoineco · antoineco · commit 9efee25e4adf · 2021-04-19T18:43:03.000+02:00
diff --git a/docs/sources/awscodecommit.md b/docs/sources/awscodecommit.md
@@ -5,6 +5,10 @@ as a new commit or the creation of a pull request, happens in this repository.
 
 ## Prerequisites
 
+* CodeCommit Repository and Branch
+* Amazon Resource Name (ARN)
+* API Credentials
+
 ### CodeCommit Repository and Branch
 
 If you don't already have an AWS CodeCommit repository, create one by following the instructions at [Create an AWS
diff --git a/docs/sources/awscognitouserpool.md b/docs/sources/awscognitouserpool.md
@@ -5,6 +5,10 @@ creation of a new user, happens in the user identity pool.
 
 ## Prerequisites
 
+* AWS Cognito User Pool
+* Amazon Resource Name (ARN)
+* API Credentials
+
 ### AWS Cognito User Pool
 
 If you don't already have an AWS Cognito User Pool, create one by following the instructions in the [Getting started
diff --git a/docs/sources/awsdynamodb.md b/docs/sources/awsdynamodb.md
@@ -5,6 +5,10 @@ sequence of item-level modifications from a [DynamoDB Stream][ddb-streams].
 
 ## Prerequisites
 
+* DynamoDB Table and Stream
+* Amazon Resource Name (ARN)
+* API Credentials
+
 ### DynamoDB Table and Stream
 
 If you don't already have an AWS DynamoDB Table, create one by following the instructions at [Getting Started with
diff --git a/docs/sources/awskinesis.md b/docs/sources/awskinesis.md
@@ -5,6 +5,10 @@ after wrapping them in a [CloudEvent][ce] envelope.
 
 ## Prerequisites
 
+* Kinesis Data Stream
+* Amazon Resource Name (ARN)
+* API Credentials
+
 ### Kinesis Data Stream
 
 If you don't already have an AWS Kinesis Data Stream, create one by following the instructions at [Creating and Updating
diff --git a/docs/sources/awss3.md b/docs/sources/awss3.md
@@ -5,6 +5,11 @@ an [Amazon SQS queue][sqs-docs] in order to be consumable by the event source.
 
 ## Prerequisites
 
+* S3 Bucket
+* Amazon Resource Name (ARN)
+* API Credentials
+* SQS Queue _(optional)_
+
 ### S3 Bucket
 
 If you didn't already do so, create a S3 bucket by following the instructions at [Create your first S3
diff --git a/docs/sources/awssns.md b/docs/sources/awssns.md
@@ -5,6 +5,10 @@ sink.
 
 ## Prerequisites
 
+* SNS Topic (standard)
+* Amazon Resource Name (ARN)
+* API Credentials
+
 ### SNS Topic (standard)
 
 If you don't already have an AWS SNS standard topic, create one by following the instructions in the [Getting started
diff --git a/docs/sources/awssqs.md b/docs/sources/awssqs.md
@@ -4,6 +4,10 @@ The event source captures messages sent to a [AWS SQS queue][sqs-docs] and sends
 
 ## Prerequisites
 
+* SQS Queue
+* Amazon Resource Name (ARN)
+* API Credentials
+
 ### SQS Queue
 
 If you don't already have an AWS SQS queue, create one by following the instructions in the [Getting started with Amazon
diff --git a/docs/sources/azureactivitylogs.md b/docs/sources/azureactivitylogs.md
@@ -6,6 +6,11 @@ selected set of log categories to a dedicated Event Hub, then subscribing to the
 
 ## Prerequisites
 
+* Service Principal
+* Event Hubs Namespace
+* Event Hubs Instance _(optional)_
+* Shared Access Policy / Shared Access Signature (SAS)
+
 ### Service Principal
 
 A [Service Principal][sp] is required in order to authenticate the event source against the Azure tenant that has
diff --git a/docs/sources/azureblobstorage.md b/docs/sources/azureblobstorage.md
@@ -6,6 +6,11 @@ in this setup.
 
 ## Prerequisites
 
+* Storage Account
+* Service Principal
+* Event Hubs Namespace
+* Event Hubs Instance _(optional)_
+
 ### Storage Account
 
 If you didn't already do so, create a [Storage Account][storage-acc] of one of the following supported types:
diff --git a/docs/sources/googlecloudpubsub.md b/docs/sources/googlecloudpubsub.md
@@ -4,6 +4,10 @@ This event source subscribes to messages sent to a [Google Cloud Pub/Sub][gc-pub
 
 ## Prerequisites
 
+* Service Account
+* Pub/Sub Topic
+* Pub/Sub Subscription _(optional)_
+
 ### Service Account
 
 A [Service Account][gc-pubsub-svcacc] is required to authenticate the event source and allow it to interact with Google
diff --git a/docs/sources/googlecloudstorage.md b/docs/sources/googlecloudstorage.md
@@ -5,6 +5,11 @@ to a [Google Cloud Pub/Sub][gc-storage-events] topic.
 
 ## Prerequisites
 
+* Storage Bucket
+* Pub/Sub Topic and Subscription
+* Notification Configuration
+* Service Account
+
 ### Storage Bucket
 
 The storage bucket is expected to exist prior to running this event source. If you haven't already done so, create a
diff --git a/docs/sources/salesforce.md b/docs/sources/salesforce.md
@@ -5,18 +5,22 @@ after wrapping them in a [CloudEvent][ce] envelope.
 
 ## Prerequisites
 
+* Salesforce Account
+* Salesforce Stream Channel
+* Certificate Key Secret
+
 ### Salesforce Account
 
 Salesforce source uses [OAuth JWT credentials][salesforce-oauth-jwt] for service authentication.
 
 1. First, you will need to generate an X509 certificate for signing and verifying requests.
 We will be using `OpenSSL` but any other certificate generation tool should work.
 
-```sh
-openssl req -x509 -sha256 -nodes -days 36500 -newkey rsa:2048 -keyout tm-sf.key -out tm-sf.crt
-```
+    ```sh
+    openssl req -x509 -sha256 -nodes -days 36500 -newkey rsa:2048 -keyout tm-sf.key -out tm-sf.crt
+    ```
 
-2. At Salesforce site select `Setup > Apps > App Manager`, click on `New Connected App`.
+1. At Salesforce site select `Setup > Apps > App Manager`, click on `New Connected App`.
 
     - Fill in mandatory fields, then click `Enable OAuth Settings`.
     - A callback URL is mandatory but can be filled with any HTTPS data.
@@ -38,7 +42,7 @@ openssl req -x509 -sha256 -nodes -days 36500 -newkey rsa:2048 -keyout tm-sf.key
     - Add permissions on the data this user will have access to.
     - Save.
 
-3. Retrieve OAuth data to configure Triggermesh Source.
+1. Retrieve OAuth data to configure Triggermesh Source.
 
    - Select the Connected App from the list and at the click on `View`.
    - Copy `Consumer Key`
