diff --git a/content/blogposts/apex-23-2-workflows-first-look/index.mdx b/content/blogposts/apex-23-2-workflows-first-look/index.mdx
index da424e8..0fd5fb3 100644
--- a/content/blogposts/apex-23-2-workflows-first-look/index.mdx
+++ b/content/blogposts/apex-23-2-workflows-first-look/index.mdx
@@ -15,7 +15,7 @@
   ghCommentsIssueId: 95
 ---
 
-## The big question mark: Flows vs. Workflows
+## The big question mark: Flows for APEX vs. Workflows
 
 I have used and learned to love the APEX extension, [Flows for APEX](https://flowsforapex.org/). It is a process modeling engine tightly integrated into APEX. You basically design a model in the BPMN notation, which is an international standard that is heavily used in almost any big company.
 
@@ -200,6 +200,6 @@ I currently have these questions that I can't answer yet?
 - How can we wait for user input? There are waiting activities, but I did not find a way to set variables for an existing workflow instance. There is an API for that, but it is only meant to be used by admins to resolve issues.
 - How does the integration with "Approval Tasks" work? Can I set a variable in the workflow instance from there?
 - In the "Participants" section, we can define roles, but only "Workflow Administrator" and "Workflow Owner" are available types. Can I fit roles like department X into this somehow?
-- What are the plans to reduce the visual complexity of huge workflows? BPMN has swimlanes and subflows to group and hide details. Are there plans to add this?
+- What are the plans to reduce the visual complexity of huge workflows? BPMN has swimlanes and call activities to group and hide details. Are there plans to add this?
 
 I guess this is the next step in a long-term feature set that will have a big impact on how we can build apps with APEX. So I think the workflow feature is not final as it is but will get many upgrades over time. Approval components definitely make more sense to me as they integrate with workflows. I am looking forward to seeing how it evolves.