From 9d1cf5310795bb0dfb12aeb45f62765e8bdba38b Mon Sep 17 00:00:00 2001 From: Pedram Navid <1045990+PedramNavid@users.noreply.github.com> Date: Sun, 11 Aug 2024 11:43:22 -0700 Subject: [PATCH] fix all vale errors --- docs/.vale.ini | 3 +++ docs/docs-next/docs/how-to/asset-management.md | 2 +- docs/docs-next/docs/intro.md | 2 +- docs/docs-next/docs/tutorial/quick-start.md | 14 +++++++------- .../styles/config/vocabularies/Dagster/accept.txt | 3 +++ 5 files changed, 15 insertions(+), 9 deletions(-) diff --git a/docs/.vale.ini b/docs/.vale.ini index 9e62abffa7a27..57fa9b375bbdb 100644 --- a/docs/.vale.ini +++ b/docs/.vale.ini @@ -28,6 +28,9 @@ Microsoft.Vocab = NO Google.Will = NO Google.WordList = NO +; Exclamation is fine +Google.Exclamation = NO + ; Passive is a bit too noisy Google.Passive = NO diff --git a/docs/docs-next/docs/how-to/asset-management.md b/docs/docs-next/docs/how-to/asset-management.md index 696af55511733..4184a148cc369 100644 --- a/docs/docs-next/docs/how-to/asset-management.md +++ b/docs/docs-next/docs/how-to/asset-management.md @@ -6,7 +6,7 @@ last_update: author: Pedram Navid --- -In Dagster, assets are the building blocks of data pipelines. They represent the data that is being processed by the pipeline. +In Dagster, assets are the building blocks of data pipelines. They represent the data that's being processed by the pipeline. An asset can represent a table in a database, a file in a file system, or even a machine learning model or notebook. diff --git a/docs/docs-next/docs/intro.md b/docs/docs-next/docs/intro.md index f26b51f847d1e..cbfb65747693e 100644 --- a/docs/docs-next/docs/intro.md +++ b/docs/docs-next/docs/intro.md @@ -5,4 +5,4 @@ slug: / # Dagster Documentation -Welcome to Dagster's documentation! \ No newline at end of file +Welcome to Dagster's documentation. \ No newline at end of file diff --git a/docs/docs-next/docs/tutorial/quick-start.md b/docs/docs-next/docs/tutorial/quick-start.md index a745279eac8f4..055ff4f6f3f69 100644 --- a/docs/docs-next/docs/tutorial/quick-start.md +++ b/docs/docs-next/docs/tutorial/quick-start.md @@ -48,14 +48,14 @@ First, set up a new Dagster project. ## Step 2: Create Your Dagster Project Structure -Let's set up a basic project structure: +Set up a basic project structure: :::warning -The file structure here is simplified to get started quickly. Once you've -completed this tutorial, consider completing the [ETL Pipeline Tutorial](/tutorial/tutorial-etl) -to learn how to build a more complex ETL pipeline with best practices when it comes -to file organization. +The file structure here is simplified to get quickly started. + +Once you've completed this tutorial, consider the [ETL Pipeline Tutorial](/tutorial/tutorial-etl) to learn +how to build more complex pipelines with best practices. ::: @@ -118,7 +118,7 @@ defs = Definitions(assets=[extract_data, transform_data, load_data]) This code defines three assets: - `extract_data`: Reads data from the CSV file -- `transform_data`: Adds an 'age_group' column based on the 'age' +- `transform_data`: Adds an `age_group` column based on the `age` - `load_data`: Saves the processed data to a CSV file The `Definitions` object serves as the central configuration point for a Dagster project. In this code, a `Definitions` @@ -160,7 +160,7 @@ To verify that your pipeline worked correctly: cat data/processed_data.csv ``` -You should see your transformed data, including the new 'age_group' column. +You should see your transformed data, including the new `age_group` column. ## What You've Learned diff --git a/docs/vale/styles/config/vocabularies/Dagster/accept.txt b/docs/vale/styles/config/vocabularies/Dagster/accept.txt index cf90c76b258ae..99cc5969713db 100644 --- a/docs/vale/styles/config/vocabularies/Dagster/accept.txt +++ b/docs/vale/styles/config/vocabularies/Dagster/accept.txt @@ -4,3 +4,6 @@ Dagster ETL SDAs SDA +Extract +Transform +Load