1 files changed, 4 insertions, 3 deletions

diff --git a/website/content/en/status/_index.adoc b/website/content/en/status/_index.adoc
index 45a7e8b3e0..f52b4ece23 100644
--- a/website/content/en/status/_index.adoc
+++ b/website/content/en/status/_index.adoc
@@ -5,15 +5,15 @@ sidenav: about
 
 = FreeBSD Status Reports
 
-== Next Quarterly Status Report submissions (October - December) due: December 31st, 2022
+== Next Quarterly Status Report submissions (January - March) due: March 31st, 2023
 
-Submit your entries as Pull Requests from your fork of link:https://github.com/freebsd/freebsd-quarterly[FreeBSD Status Report GitHub repo] or submit them via e-mail to quarterly-submissions@FreeBSD.org, using the link:https://github.com/freebsd/freebsd-quarterly/blob/master/report-sample.adoc[report-sample.adoc template].
+Submit your entries as Pull Requests from your fork of link:https://github.com/freebsd/freebsd-quarterly[FreeBSD Status Report GitHub repo] or submit them via e-mail to status-submissions@FreeBSD.org, using the link:https://github.com/freebsd/freebsd-quarterly/blob/master/report-sample.adoc[report-sample.adoc template].
 
 '''''
 
 One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree.
 
-The FreeBSD Development Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.
+The FreeBSD Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.
 
 For more exact guidelines on how to write good status reports, please consult link:howto/[our recommendations].
 
@@ -23,6 +23,7 @@ These status reports may be reproduced in whole or in part, as long as the sourc
 
 == 2022
 
+* link:report-2022-10-2022-12/[October, 2022 - December, 2022]
 * link:report-2022-07-2022-09/[July, 2022 - September, 2022]
 * link:report-2022-04-2022-06/[April, 2022 - June, 2022]
 * link:report-2022-01-2022-03/[January, 2022 - March, 2022]