Part 3: workflows - two small editorial fixes

extensions/workflows/sections/clause_13_openeo_workflows.adoc

@@ -17,7 +17,7 @@ is already covered by a conformance class of Part 2.
 
 include::../requirements/requirements_class_openeo-workflows.adoc[]
 
-The following requirements describe the ability of an implementation to execute a CWL workflow in an ad-hoc manner and return its output, without requiring a prior deployment.
+The following requirements describe the ability of an implementation to execute an openEO process graph workflow in an ad-hoc manner and return its output, without requiring a prior deployment.
 
 ==== Ad-hoc OpenEO Workflow Execution
 

extensions/workflows/sections/clause_6_overview.adoc

@@ -129,7 +129,7 @@ This negotiation happens at each hop along a workflow chain, and the end-user cl
 For example, some hops may operate better using DGGS zone IDs, while other using subset requests, and yet others using tiles; or some hops may support and work best with some format or API,
 while others work best with another.
 
-When setting up a new workflow for collection output our asynchronous execution, if possible, the API should fully validate the immediate process and all nested inputs prior to returning a result.
+When setting up a new workflow for collection output or asynchronous execution, if possible, the API should fully validate the immediate process and all nested inputs prior to returning a result.
 A successful result indicates a fully validated workflow which should normally succeed for requests within the range for which data is produced.
 It is expected that clients may make a large number of requests for the same workflow e.g., using subset or tiles or DGGS zone ID to trigger processing of a specific Area of Interest or resolution,
 as a client pans and zooms around a map.