From f801db7c27bfa71b88bdf066e50f0432caeb923a Mon Sep 17 00:00:00 2001
From: tgmof <31918716+tgmof@users.noreply.github.com>
Date: Mon, 31 Jul 2023 15:32:05 +0200
Subject: [PATCH] Update README.md (#104)

Update the example so that it doesn't mislead the user to think that the end date is included. This also follows the (less misleading even though not clearly stated) example here:
https://github.com/dbt-labs/dbt-utils#date_spine-source
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index e7ed0da..4efd2f0 100644
--- a/README.md
+++ b/README.md
@@ -125,10 +125,10 @@ For example, use `America/New_York` for East Coast Time.
 
 A wrapper around [`dbt_utils.date_spine`](https://github.com/dbt-labs/dbt-utils#date_spine-source) that allows you to specify either `start_date` and `end_date` for your date spine, or specify a number of periods (`n_dateparts`) in the past from today.
 
-Usage:
+Usage to build a daily date dimension for the years 2015 to 2022:
 
 ```sql
-{{ dbt_date.get_base_dates(start_date="2015-01-01", end_date="2022-12-31") }}
+{{ dbt_date.get_base_dates(start_date="2015-01-01", end_date="2023-01-01") }}
 ```
 
 or to build a daily date dimension for the last 3 years: