diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 40b3872..ed246d2 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,5 @@
 blank_issues_enabled: true
 contact_links:
   - name: Questions and contribution help
-    url: https://github.com/yusufipk/OpenFrame/blob/main/CONTRIBUTING.md
+    url: https://github.com/yusufipk/OpenFrame/blob/master/CONTRIBUTING.md
     about: Use issues for actionable tasks; for questions, include context and expected outcome.
diff --git a/CODEOWNERS b/CODEOWNERS
index ffe83da..cfaab40 100644
--- a/CODEOWNERS
+++ b/CODEOWNERS
@@ -1,10 +1,2 @@
 # Global default owners
 * @yusufipk
-
-# Critical security and access control areas
-
-/lib/auth.ts @yusufipk
-/lib/route-access.ts @yusufipk
-/app/api/auth/ @yusufipk
-/app/api/stripe/ @yusufipk
-/prisma/ @yusufipk
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 51226e5..09384be 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -62,7 +62,7 @@ bun run db:seed
 
 ## Contribution Workflow
 
-1. Fork and create a branch from `main`.
+1. Fork and create a branch from `master`.
 2. Keep changes focused on one logical concern.
 3. Follow coding and architecture conventions in this guide.
 4. Run required validation locally.
@@ -179,43 +179,6 @@ When changing data model behavior:
 - For technical changes, document behavior in the most relevant existing file or PR notes.
 - Keep docs practical and update them in the same PR when behavior changes.
 
-## Pull Request Checklist
-
-Before submitting, confirm:
-
-- [ ] My branch is focused on one concern.
-- [ ] I followed project conventions in this guide.
-- [ ] I ran `bun run check`.
-- [ ] I ran `bun run db:generate` if schema changed.
-- [ ] I updated docs for user-visible or architectural changes.
-- [ ] I added screenshots or request/response examples when useful.
-- [ ] My PR description explains what changed and why.
-
-## PR Description Template (Recommended)
-
-```markdown
-## Summary
-
-Short description of what changed.
-
-## Why
-
-What problem this solves.
-
-## Changes
-
-- Key change 1
-- Key change 2
-
-## Validation
-
-- bun run check
-- Manual test notes
-
-## Notes
-
-Any migration, compatibility, or follow-up notes.
-```
 
 ## Review Expectations
 
diff --git a/SECURITY.md b/SECURITY.md
index 51c3d7c..54f432a 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -3,7 +3,7 @@
 ## Supported Versions
 
 OpenFrame is under active development.
-Security fixes are prioritized for the latest code on `main` and recent release tags (if available).
+Security fixes are prioritized for the latest code on `master` and recent release tags (if available).
 
 ## Reporting a Vulnerability