docs: update PR title instructions

Author: raisedadead

src/content/docs/how-to-open-a-pull-request.mdx

@@ -38,7 +38,7 @@ We use [conventional title and messages](https://www.conventionalcommits.org/) f
 >
 > For example:
 >
-> `fix(learn): tests for the do...while loop challenge`
+> `fix(curriculum): tests for the do...while loop challenge`
 
 Whenever you open a Pull Request (PR), you can use the below to determine the type, scope (optional), and description.
 
@@ -49,15 +49,13 @@ Whenever you open a Pull Request (PR), you can use the below to determine the ty
 | fix      | Bug fixes - when you repair something that wasn't working correctly        |
 | feat     | New features - when you add new functionality that didn't exist before     |
 | refactor | Code cleanup - reorganizing code without changes to logic                  |
-| chore    | Maintenance tasks - updating dependencies, build configs, or project setup |
 | docs     | Documentation - updating README files, comments, or help documentation     |
 
 **Scope:**
 
 `Scope` is optional but it helps reviewers understand which areas of the project are impacted. Common scopes include:
 
 - **curriculum**: Lessons, challenges, projects, and learning content
-- **ui**: User interface and user experience improvements
 - **a11y**: Accessibility improvements and fixes
 - **i18n**: Internationalization and language translations
 - **api**: Backend API and server-side code