From 9bbf1d8ab61ded769f15fb73e2ca526402fd3a97 Mon Sep 17 00:00:00 2001
From: Pranav Wadhwa <25285598+Pranav-Wadhwa@users.noreply.github.com>
Date: Fri, 23 Aug 2024 17:41:05 -0400
Subject: [PATCH] Clarify documentation for asfreq (#59589)

---
 pandas/core/generic.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pandas/core/generic.py b/pandas/core/generic.py
index 8e2524c21d31e2..cdc8642c9c70e0 100644
--- a/pandas/core/generic.py
+++ b/pandas/core/generic.py
@@ -8452,8 +8452,8 @@ def asfreq(
         will map one-to-one to the new index).
 
         Otherwise, the new index will be equivalent to ``pd.date_range(start, end,
-        freq=freq)`` where ``start`` and ``end`` are, respectively, the first and
-        last entries in the original index (see :func:`pandas.date_range`). The
+        freq=freq)`` where ``start`` and ``end`` are, respectively, the min and
+        max entries in the original index (see :func:`pandas.date_range`). The
         values corresponding to any timesteps in the new index which were not present
         in the original index will be null (``NaN``), unless a method for filling
         such unknowns is provided (see the ``method`` parameter below).
@@ -8471,7 +8471,7 @@ def asfreq(
             does not fill NaNs that already were present):
 
             * 'pad' / 'ffill': propagate last valid observation forward to next
-              valid
+              valid based on the order of the index
             * 'backfill' / 'bfill': use NEXT valid observation to fill.
         how : {{'start', 'end'}}, default end
             For PeriodIndex only (see PeriodIndex.asfreq).