diff --git a/README.md b/README.md
index 5905bbd647f..01776b048ad 100644
--- a/README.md
+++ b/README.md
@@ -176,7 +176,7 @@ The list below contains the functionality that contributors are planning to deve
   * [ ] Cassandra
 * **Streaming**
   * [x] [Custom streaming ingestion job support](https://docs.feast.dev/how-to-guides/creating-a-custom-provider)
-  * [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push.md)
+  * [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push)
   * [ ] Streaming ingestion on AWS
   * [ ] Streaming ingestion on GCP
 * **Feature Engineering**
@@ -207,7 +207,7 @@ The list below contains the functionality that contributors are planning to deve
   * [x] CLI for browsing feature registry
   * [x] Model-centric feature tracking (feature services)
   * [x] Amundsen integration (see [Feast extractor](https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/feast_extractor.py))
-  * [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui.md))
+  * [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui))
   * [ ] REST API for browsing feature registry
   * [ ] Feature versioning
 
diff --git a/docs/getting-started/architecture-and-components/online-store.md b/docs/getting-started/architecture-and-components/online-store.md
index 4f2e44c92ce..21b4dbcb9c7 100644
--- a/docs/getting-started/architecture-and-components/online-store.md
+++ b/docs/getting-started/architecture-and-components/online-store.md
@@ -12,4 +12,4 @@ Once the above data source is materialized into Feast \(using `feast materialize
 
 ![](../../.gitbook/assets/image%20%285%29.png)
 
-Features can also be written to the online store via [push sources](https://docs.feast.dev/reference/data-sources/push) 
\ No newline at end of file
+Features can also be written to the online store via [push sources](../../reference/data-sources/push.md) 
\ No newline at end of file
diff --git a/docs/getting-started/architecture-and-components/overview.md b/docs/getting-started/architecture-and-components/overview.md
index bf5c12dcc20..0c47fb2753d 100644
--- a/docs/getting-started/architecture-and-components/overview.md
+++ b/docs/getting-started/architecture-and-components/overview.md
@@ -23,7 +23,7 @@ A complete Feast deployment contains the following components:
   * Materialize (load) feature values into the online store.
   * Build and retrieve training datasets from the offline store.
   * Retrieve online features.
-* **Online Store:** The online store is a database that stores only the latest feature values for each entity. The online store is populated by materialization jobs and from [stream ingestion](../../reference/alpha-stream-ingestion.md).
+* **Online Store:** The online store is a database that stores only the latest feature values for each entity. The online store is populated by materialization jobs and from [stream ingestion](../../reference/data-sources/push.md).
 * **Offline Store:** The offline store persists batch data that has been ingested into Feast. This data is used for producing training datasets. Feast does not manage the offline store directly, but runs queries against it.
 
 {% hint style="info" %}
diff --git a/docs/getting-started/quickstart.md b/docs/getting-started/quickstart.md
index 41449b77e39..1684c720632 100644
--- a/docs/getting-started/quickstart.md
+++ b/docs/getting-started/quickstart.md
@@ -367,7 +367,7 @@ pprint(feature_vector)
 
 ## Step 7: Using a feature service to fetch online features instead.
 
-You can also use feature services to manage multiple features, and decouple feature view definitions and the features needed by end applications. The feature store can also be used to fetch either online or historical features using the same api below. More information can be found [here](https://docs.feast.dev/getting-started/concepts/feature-service).
+You can also use feature services to manage multiple features, and decouple feature view definitions and the features needed by end applications. The feature store can also be used to fetch either online or historical features using the same api below. More information can be found [here](https://docs.feast.dev/getting-started/concepts/feature-retrieval).
 
 {% tabs %}
 {% tab title="Python" %}
diff --git a/docs/roadmap.md b/docs/roadmap.md
index c2f5511f1ed..d893814aafd 100644
--- a/docs/roadmap.md
+++ b/docs/roadmap.md
@@ -41,7 +41,7 @@ The list below contains the functionality that contributors are planning to deve
   * [ ] Cassandra
 * **Streaming**
   * [x] [Custom streaming ingestion job support](https://docs.feast.dev/how-to-guides/creating-a-custom-provider)
-  * [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push.md)
+  * [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push)
   * [ ] Streaming ingestion on AWS
   * [ ] Streaming ingestion on GCP
 * **Feature Engineering**
@@ -72,6 +72,6 @@ The list below contains the functionality that contributors are planning to deve
   * [x] CLI for browsing feature registry
   * [x] Model-centric feature tracking (feature services)
   * [x] Amundsen integration (see [Feast extractor](https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/feast_extractor.py))
-  * [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui.md))
+  * [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui))
   * [ ] REST API for browsing feature registry
   * [ ] Feature versioning