diff --git a/ships/0031-shipwright-trigger.md b/ships/0031-shipwright-trigger.md
index a2e75f4..dd0580d 100644
--- a/ships/0031-shipwright-trigger.md
+++ b/ships/0031-shipwright-trigger.md
@@ -5,7 +5,11 @@ Shipwright Trigger
 
 Shipwright's project goal is to automate and greatly simplify the container image building process, and currently, users can only initiate the build process by issuing a new `BuildRun` object.
 
-This enhancement proposal describes how Shipwright will react upon WebHook events coming from Git service providers like GitHub, how it will be incorporated into Tekton Pipelines via Custom Task, and how it will react upon Tekton Pipelines resources.
+This enhancement proposal describes how Shipwright will react to:
+- WebHooks: Handles WebHook requests from Git service providers, like GitHub, in order to activate a Build 
+-  Tekton Pipelines: Integration between Tekton Pipelines and Shipwright, Builds will be triggered when a given Pipeline has reach the desired status
+- Tekton [Custom-Tasks](https://github.com/tektoncd/community/blob/main/teps/0002-custom-tasks.md) (Run): A new Custom Task will allow users to call out Shipwright Builds directly from Pipelines
+Images: Integration with the new Shipwright [Image project](https://github.com/shipwright-io/image), changes to any Images managed by that project that serve as input into a Shipwright Build will initiate new BuildRuns when any of those images change.
 
 # Motivation