diff --git a/react/modules/tasks/nextjs-ssr-ssg.md b/react/modules/tasks/nextjs-ssr-ssg.md
index 60f1590a7..bc53212ad 100644
--- a/react/modules/tasks/nextjs-ssr-ssg.md
+++ b/react/modules/tasks/nextjs-ssr-ssg.md
@@ -153,22 +153,22 @@ Note: You may also use the experimental `vinext` framework for this task. It is
 - Initial load of the search results page (with current page and query parameters) is rendered on the server. [8 points]
 - The search results list and layout (including the container for the details panel) are implemented using server components. [7 points]
 
-### Feature 10: Server Actions for Search, Filtering, and Detail Selection (**10 points**)
+### Feature 10: Server Actions for Search and Detail Selection (**10 points**)
 
 **As a** user
-**I want** my interactions on the search results page (search, filter, select item) to be handled on the server
+**I want** my interactions on the search results page (search, select item) to be handled on the server
 **So that** I always see up-to-date data with minimal client-side logic
 
 **Scenario:** Server-Driven Interactions on Search Page
 
 - **Given** I am on the search results page
-- **When** I submit a search or filter form
+- **When** I submit a search form
 - **Then** a Next.js server action (e.g., using `useActionState` or form actions) handles the request and returns updated server-rendered results
 - **And** when I select an item, the server-driven details panel component receives the selected ID and fetches data on the server
 
 **Acceptance Criteria:**
 
-- Search and filter submissions are wired through server actions or server functions, not ad-hoc client-only fetch calls. [5 points]
+- Search submissions are wired through server actions or server functions, not ad-hoc client-only fetch calls. [5 points]
 - Selecting an item for the details panel triggers server-side data fetching for that item (via server component or server function). [5 points]
 
 ### Penalties