fix README.md

Author: egarciajulia

README.md

@@ -24,7 +24,7 @@ Your work will be organized into three separate pull requests within your own re
 
 *   **`main`**: The initial state of the codebase. You will branch from here.
 *   **`fix-bug-666`**: A simulated PR from a junior developer. This branch contains their work for you to review.
-*   **`fix/haunted-codebase`**: The branch you will create from `main` to fix the existing technical debt (the N+1 and re-render bugs).
+*   **`fix/haunted-codebase`**: The branch you will create from `main` to fix the existing technical debt.
 *   **`feature/transaction-tags-grid`**: The branch you will create from `fix/haunted-codebase` for the new feature (database migration and data grid).
 
 
@@ -108,7 +108,7 @@ With the codebase stabilized, you can now build the new feature. This PR will be
 The final deliverable is **a link to your forked repository.** When you submit it, we expect to see the following:
 
 *   **PR #1 (Code Review):** A **closed** pull request from `fix-bug-666` to `main`, containing your review comments.
-*   **PR #2 (Bug Fixes):** An **open** pull request from `fix/haunted-codebase` to `main`, containing the fixes for the N+1 and re-render bugs.
+*   **PR #2 (Bug Fixes):** An **open** pull request from `fix/haunted-codebase` to `main`, containing the fixes.
 *   **PR #3 (New Feature):** An **open** pull request from `feature/transaction-tags-grid` to `main`, containing the database migration and the new data grid feature. This PR will implicitly include the commits from PR #2 as its base.
 
 ### PR Description Template for PRs #2 and #3