Fix sources-triggers typos

Author: jverce

docs-v2/pages/connect/api.mdx

@@ -966,7 +966,7 @@ GET /{component_type}
 
 `component_type` **string**
 
-Either `sources`, `actions`, or `components`.
+Either `triggers`, `actions`, or `components`.
 
 ##### Query parameters
 
@@ -1103,7 +1103,7 @@ GET /{component_type}/{component_key}
 
 `component_type` **string**
 
-Either `sources`, `actions`, or `components`.
+Either `triggers`, `actions`, or `components`.
 
 ---
 
@@ -1234,7 +1234,7 @@ GET /{component_type}/configure
 
 `component_type` **string**
 
-Either `sources`, `actions`, or `components`.
+Either `triggers`, `actions`, or `components`.
 
 ##### Body Parameters
 
@@ -1434,7 +1434,7 @@ GET /{component_type}/props
 
 `component_type` **string**
 
-Either `sources`, `actions`, or `components`.
+Either `triggers`, `actions`, or `components`.
 
 ##### Body Parameters
 

docs-v2/pages/connect/components.mdx

@@ -320,7 +320,7 @@ To illustrate, the response for the request above would look like this:
 
 Once all the props have been configured, the component can be invoked. Pipedream
 supports two types of components: [actions](/components#actions) and
-[sources](/components#sources).
+[sources](/components#sources) (a.k.a. triggers).
 
 Actions are components that perform a task by taking an input either during
 [configuration](#configuration) and/or during invocation (usually both), and