make intro copy more concise, fix toc links, add tk to workflows article

Signed-off-by: nikki everett <[email protected]>
flyteorg · Dec 1, 2023 · 059cba9 · 059cba9
1 parent 798ef85
commit 059cba9
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 6 deletions.
diff --git a/docs/getting_started/getting_started_with_workflow_development.md b/docs/getting_started/getting_started_with_workflow_development.md
@@ -8,18 +8,18 @@ prev-page-title: Quickstart guide
 
 # Getting started with workflow development
 
-At the heart of machine learning, data engineering, and data analytics is the directed acyclic graph (DAG) of processes that consume, transform, and output data. Flyte enables you to develop and test your DAGs locally in a production-like environment by creating a Flyte project to contain the task and workflow code that defines your DAG, as well as the configuration files needed to package your code to run on a local or remote Flyte cluster.
+Machine learning engineers, data engineers, and data analysts represent the processes that consume, transform, and output data with directed acyclic graphs (DAGs). In this section, you will learn how to create a Flyte project to contain the workflow code that implements your DAG, as well as the configuration files needed to package the code to run on a local or remote Flyte cluster.
 
 ```{list-table}
 :header-rows: 0
 :widths: 20 30
 
-* - {doc}`Installing development tools <getting_started_installing_development_tools>`
+* - {doc}`Installing development tools <installing_development_tools>`
   - Install the tools needed to create Flyte projects and run workflows and tasks.
-* - {doc}`Creating a Flyte project <getting_started_creating_a_flyte_project>`
-  - Create a Flyte project that contains workflow code and configuration files needed to package the code to run on a local or remote Flyte cluster.
-* - {doc}`Running workflows locally <getting_started_running_workflows_locally>`
-  - Execute workflows locally both on a local cluster and not.
+* - {doc}`Creating a Flyte project <creating_a_flyte_project>`
+  - Create a Flyte project that contains workflow code and necessary configuration files.
+* - {doc}`Running workflows locally <running_workflows_locally>`
+  - Execute workflows locally both on a local cluster and not. TK - need better language here
 ```
 
 ```{toctree}

diff --git a/docs/getting_started/running_workflows_locally.md b/docs/getting_started/running_workflows_locally.md
@@ -10,6 +10,8 @@ jupytext:
 
 # Running workflows locally
 
+TK - "Creating a Flyte project" emphasizes that projects enable you to package code to run on a Flyte cluster, so you would expect this article to mention packaging code (and workflow registration), but it doesn't. We should probably mention those things at least briefly.
+
 ## Running a workflow locally (not in a local cluster)
 
 [TK - why run locally + not in a local cluster]