From 69a44c461f063fdf74a6f1f15e93b3866f448dcd Mon Sep 17 00:00:00 2001
From: Cody Peterson <54814569+lostmygithubaccount@users.noreply.github.com>
Date: Mon, 26 Aug 2024 09:17:09 -0400
Subject: [PATCH] docs(blog): minor edits to pandas blog (#9920)

---
 docs/posts/farewell-pandas/index.qmd | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/posts/farewell-pandas/index.qmd b/docs/posts/farewell-pandas/index.qmd
index 1c5d5df0221a..4e91b1fe0263 100644
--- a/docs/posts/farewell-pandas/index.qmd
+++ b/docs/posts/farewell-pandas/index.qmd
@@ -1,7 +1,7 @@
 ---
-title: Farewell Pandas, and thanks for all the fish.
+title: Farewell pandas, and thanks for all the fish.
 author: Gil Forsyth
-date: 2024-08-22
+date: 2024-08-26
 categories:
     - blog
     - pandas
@@ -13,11 +13,11 @@ removing them in version 10.0.
 
 There is no feature gap between the `pandas` backend and our default DuckDB
 backend, and DuckDB is _much_ more performant.  `pandas` DataFrames will still
-be available as _format_ for getting data from Ibis, we just won't support using
-`pandas` to execute queries.
+be available as _format_ for getting data to and from Ibis, we just won't
+support using `pandas` to execute queries.
 
 Most of the rationale below applies to the Dask backend since it has so much in
-common with Pandas. Dask is a great project and people should continue to use
+common with pandas. Dask is a great project and people should continue to use
 it outside the Ibis context.
 
 ## Why `pandas`? And a bit of Ibis history