From cc0b169931c0402282904cd662db4b29ce987f4e Mon Sep 17 00:00:00 2001
From: Leo HC Li <36619969+Leo6Leo@users.noreply.github.com>
Date: Sun, 7 Apr 2024 22:52:40 -0400
Subject: [PATCH] Fix the review comment

---
 code-samples/eventing/bookstore-sample-app/db/README.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/code-samples/eventing/bookstore-sample-app/db/README.md b/code-samples/eventing/bookstore-sample-app/db/README.md
index be1d4c774e..26a8de577d 100644
--- a/code-samples/eventing/bookstore-sample-app/db/README.md
+++ b/code-samples/eventing/bookstore-sample-app/db/README.md
@@ -5,9 +5,6 @@ In this tutorial, we'll embark on creating a PostgreSQL database using Kubernete
 
 You might wonder, "Why not leverage Knative Serving to dynamically scale the database service in response to traffic demands?" We'll delve into the optimal scenarios for employing Knative Serving and when it's advantageous for our database service.
 
-## What Knative features will we learn about?
-- Appropriate Use Cases for Knative Service
-
 ## What does the final deliverable look like?
 Our goal is to deploy a PostgreSQL pod within Kubernetes, loaded with the sample data outlined in the accompanying SQL file. This pod will serve as the foundational database service for our bookstore application.