diff --git a/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
index 83f0e04f..0e412cd7 100644
--- a/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE/PULL_REQUEST_TEMPLATE.md
@@ -2,7 +2,7 @@
 Before submitting your pull request, ensure the following:
 
 ### Pull Request Title Standard
-- [ ] The pull request title follows the standard: [Pull Request Naming Conventions](https://github.com/gelecekbilimde/gelecekbilimde-backend/blob/main/CONTRIBUTING.md#pull-request-title-standard).    
+- [ ] The pull request title follows the standard: [Pull Request Naming Conventions](https://github.com/gelecekbilimde/backend/blob/main/CONTRIBUTING.md#pull-request-naming-conventions)).    
 
 ### Local Testing
 - [ ] I have tested my changes locally on Postman, and they are working as expected.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e056d22d..76e820e2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -226,9 +226,6 @@ To maintain a consistent commit history, start your commit messages with a keywo
 - `#2 | imp: Added timestamp to API responses`
 - `#3 | fix: Resolved permission error when editing user's comment`
 
- ### Pull Request Title Standard
-- For pull requests, include the issue number and a brief description of the change:
-- Use #<issue_number> | prefix followed by the commit type and a concise description.
 
 ## API Response Examples
 
diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 44bd9aa6..00000000
--- a/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,21 +0,0 @@
-## Pull Request Checklist
-Before submitting your pull request, ensure the following:
-
-###  Title and Branch Naming Conventions:
-* The pull request title follows the standard: Pull Request Naming Conventions.
-* The branch name follows one of the conventions outlined in the Branch Naming Conventions.
-
-###  Local Testing:
- * I have tested my changes locally using Postman, and they are working as expected.
-
-###  Code Quality:
-* The code is formatted according to the project's coding guidelines and style.
-* The code has been reviewed to ensure its quality.
-* The code does not contain any issues flagged by SonarLint.
-
-###  Documentation:
-* Necessary documentation has been added or existing documentation has been updated, specifically detailing changes made in Postman.
-
-### Reviewers and Assignees:
-* Default reviewers have been assigned to this pull request.
-* Assignees have been added if necessary.