[docs] Fix typo onYearPicker to onYearChange (#5954)

mui · Aug 30, 2022 · 656cf1a · 656cf1a
1 parent e59e909
commit 656cf1a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -585,7 +585,7 @@ We'd like to offer a big thanks to the 15 contributors who made this release pos
 
   **MonthPicker**: The prop `onMonthChange` has been removed, you can use `onChange` instead since every change is a month change
 
-  **YearPicker**: The prop `onYearPicker` has been removed, you can use `onChange` instead since every change is a year change
+  **YearPicker**: The prop `onYearChange` has been removed, you can use `onChange` instead since every change is a year change
 
   **DayPicker**: The prop `isDateDisabled` has been removed, you can now use the same validation props as for the other components (`maxDate`, `minDate`, `shouldDisableDate`, `disableFuture` and `disablePast`)
 

diff --git a/docs/data/date-pickers/migration-lab/migration-lab.md b/docs/data/date-pickers/migration-lab/migration-lab.md
@@ -106,7 +106,7 @@ The default behavior remains the same (close after the last step on desktop but
 The props of `MonthPicker`, `YearPicker` and `DayPicker` have been reworked to make them more consistent for a standalone usage.
 
 - **MonthPicker**: The prop `onMonthChange` has been removed, you can use `onChange` instead since every change is a month change.
-- **YearPicker**: The prop `onYearPicker` has been removed, you can use `onChange` instead since every change is a year change.
+- **YearPicker**: The prop `onYearChange` has been removed, you can use `onChange` instead since every change is a year change.
 - **DayPicker**: The prop `isDateDisabled` has been removed, you can now use the same validation props as for the other components (`maxDate`, `minDate`, `shouldDisableDate`, `disableFuture` and `disablePast`).
 
 #### Translation