diff --git a/cursor-vs-copilot-python/README.md b/cursor-vs-copilot-python/README.md
index a47aa5f4e2..00ce5f49eb 100644
--- a/cursor-vs-copilot-python/README.md
+++ b/cursor-vs-copilot-python/README.md
@@ -1,3 +1,3 @@
-# Cursor vs GitHub Copilot: Which AI Editor Is Better for Python?
+# Cursor vs Copilot: Which AI Editor Is Better for Python?
 
-This folder provides the prompts used in the Real Python tutorial [Cursor vs GitHub Copilot: Which AI Editor Is Better for Python?](https://realpython.com/cursor-vs-github-copilot-python/)
+This folder provides the prompts used in the Real Python tutorial [Cursor vs Copilot: Which AI Editor Is Better for Python?](https://realpython.com/cursor-vs-copilot/)
diff --git a/cursor-vs-copilot-python/cursor/pyproject.toml b/cursor-vs-copilot-python/cursor/pyproject.toml
index 9cba48884e..714d81dfa2 100644
--- a/cursor-vs-copilot-python/cursor/pyproject.toml
+++ b/cursor-vs-copilot-python/cursor/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 name = "notes-manager-cursor-test"
 version = "0.1.0"
 description = ""
-requires-python = ">=3.9"
+requires-python = ">=3.10"
 dependencies = [
     "pyyaml==6.0.2",
     "pytest==9.0.3",
diff --git a/cursor-vs-copilot-python/github-copilot/pyproject.toml b/cursor-vs-copilot-python/github-copilot/pyproject.toml
index 74b7d88390..8f1bdfde1d 100644
--- a/cursor-vs-copilot-python/github-copilot/pyproject.toml
+++ b/cursor-vs-copilot-python/github-copilot/pyproject.toml
@@ -5,7 +5,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "notes-manager-copilot-test"
 version = "0.1.0"
-requires-python = ">=3.9"
+requires-python = ">=3.10"
 dependencies = [
     "pyyaml==6.0.2",
 ]
diff --git a/cursor-vs-copilot-python/prompts.md b/cursor-vs-copilot-python/prompts.md
index 45427780b6..08accb8c27 100644
--- a/cursor-vs-copilot-python/prompts.md
+++ b/cursor-vs-copilot-python/prompts.md
@@ -18,7 +18,7 @@ packaging conventions:
 
 ## Implementing the Application
 
-Use this prompt in **Agent** mode after setting up the project. It defines the requirements for the command-line Markdown note manager, including Markdown storage, YAML frontmatter, the note data model, SQLite persistence, and the command-line interface. :contentReference[oaicite:1]{index=1}
+Use this prompt in **Agent** mode after setting up the project. It defines the requirements for the command-line Markdown note manager, including Markdown storage, YAML frontmatter, the note data model, SQLite persistence, and the command-line interface.
 
 ```text
 Build a command-line Markdown note manager for this project.
@@ -37,7 +37,7 @@ Requirements:
 
 ## Testing and Debugging
 
-Use this prompt in **Agent** mode after deliberately removing the `self._conn.commit()` call from `NoteStore.add_note()`. It asks the editor to run the existing tests, investigate any failures, fix the underlying problem, and verify the fix by running the complete test suite again. :contentReference[oaicite:2]{index=2}
+Use this prompt in **Agent** mode after deliberately removing the `self._conn.commit()` call from `NoteStore.add_note()`. It asks the editor to run the existing tests, investigate any failures, fix the underlying problem, and verify the fix by running the complete test suite again.
 
 ```text
 Run the existing pytest test suite.
@@ -48,7 +48,7 @@ and rerun the tests until the entire suite passes.
 
 ## Planning the Archiving Feature
 
-Use this prompt in **Plan** mode to compare how Cursor and GitHub Copilot plan a multi-file change before modifying the project. The feature adds support for archiving notes while keeping archived notes out of normal searches and listings unless explicitly requested. :contentReference[oaicite:3]{index=3}
+Use this prompt in **Plan** mode to compare how Cursor and GitHub Copilot plan a multi-file change before modifying the project. The feature adds support for archiving notes while keeping archived notes out of normal searches and listings unless explicitly requested.
 
 ```text
 Create a plan to add support for archiving notes.
@@ -62,7 +62,7 @@ Create a plan to add support for archiving notes.
 
 ## Reviewing the Database Layer
 
-Use this prompt in **Ask** mode after deliberately replacing the parameterized search query with an interpolated SQL query. It asks the editor to inspect the database layer for correctness, SQL safety, and code quality without changing the implementation. :contentReference[oaicite:4]{index=4}
+Use this prompt in **Ask** mode after deliberately replacing the parameterized search query with an interpolated SQL query. It asks the editor to inspect the database layer for correctness, SQL safety, and code quality without changing the implementation.
 
 ```text
 Review the database layer for correctness, SQL safety,
@@ -72,7 +72,7 @@ Identify any issues and suggest improvements without modifying the code.
 
 ## Reviewing Pending Changes in Cursor
 
-Use the `/review` command in Cursor after introducing the SQL injection vulnerability. Unlike the broader review in Ask mode, `/review` focuses on the changes in the current diff and identifies issues introduced by those changes. :contentReference[oaicite:5]{index=5}
+Use the `/review` command in Cursor after introducing the SQL injection vulnerability. Unlike the broader review in Ask mode, `/review` focuses on the changes in the current diff and identifies issues introduced by those changes.
 
 ```text
 /review