PR feedback updates

Author: jaydeluca

CONTRIBUTING.md

@@ -6,9 +6,34 @@ Before submitting new features or changes to current functionality, it is recomm
 [open an issue](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/new)
 and discuss your ideas or propose the changes you wish to make.
 
-**Breaking Changes**: If your PR introduces a breaking change, please add the `breaking change` label.
-This will trigger automation to help you document the change properly.
-See [Breaking Changes Automation](RELEASING.md#breaking-changes-and-deprecations-automation) for more details.
+
+## Breaking Changes
+
+When your PR introduces a breaking change:
+
+* Add the `breaking change` label to your PR
+* Provide migration notes in the PR description:
+  - What is changing and why
+  - How users should update their code/configuration
+  - Code examples showing before/after usage (if applicable)
+
+**When to Use:**
+
+* API changes that break backward compatibility
+* Configuration changes that require user action
+* Behavioral changes that might affect existing users
+* Removal of deprecated features
+
+## Deprecations
+
+When your PR deprecates functionality:
+
+* Add the `deprecation` label to your PR
+* Provide deprecation details in the PR description:
+  - What is being deprecated and why
+  - What should be used instead (if applicable)
+  - Timeline for removal (if known)
+  - Any migration guidance
 
 ## Building
 

RELEASING.md

@@ -74,62 +74,6 @@ and deadlocks.
     (note that if this is not a patch release then the change log on main may already be up-to-date,
     in which case no pull request will be created).
 
-## Breaking Changes and Deprecations Automation
-
-This project includes automation to help track and communicate breaking changes and deprecations to users.
-
-### For Contributors
-
-#### Breaking Changes
-When your PR introduces a breaking change:
-
-1. **Apply the Label**: Add the `breaking change` label to your PR
-2. **Respond to Automation**: A bot will comment with guidance on documenting the breaking change
-3. **Provide Migration Notes**: Add detailed migration notes to your PR description or as a comment, including:
-   - What is changing and why
-   - How users should update their code/configuration
-   - Code examples showing before/after usage (if applicable)
-
-#### Deprecations
-When your PR deprecates functionality:
-
-1. **Apply the Label**: Add the `deprecation` label to your PR
-2. **Respond to Automation**: A bot will comment with guidance on documenting the deprecation
-3. **Provide Deprecation Details**: Add details to your PR description or as a comment, including:
-   - What is being deprecated and why
-   - What should be used instead (if applicable)
-   - Timeline for removal (if known)
-   - Any migration guidance
-
-### For Maintainers
-
-During PR review, ensure:
-- Migration notes are clear
-- The breaking change is properly categorized
-- The impact is well understood
-
-### Automation Details
-
-The breaking changes automation includes:
-
-- **PR Comment Bot** (`.github/workflows/breaking-change-pr-comment.yml`): Automatically comments on PRs with the `breaking change` label, providing guidance and a checklist for the author
-- **Changelog Integration** (`.github/scripts/extract-breaking-changes.sh`): Extracts PRs with breaking change labels and includes them in the changelog template
-- **Release Notes Enhancement** (`.github/workflows/release.yml`): Highlights breaking changes prominently in GitHub release notes
-
-Breaking changes are automatically:
-- Included in the "Breaking Changes" section of the changelog template generated by `draft-change-log-entries.sh`
-- Highlighted at the top of GitHub release notes with links to the original PRs
-- Linked to migration notes provided by contributors
-
-### Label Requirements
-
-- **Label Name**: `breaking change` (exact match, case sensitive)
-- **When to Use**:
-  - API changes that break backward compatibility
-  - Configuration changes that require user action
-  - Behavioral changes that might affect existing users
-  - Removal of deprecated features
-
 ## Credentials
 
 Same as the core repo, see [opentelemetry-java/RELEASING.md#credentials](https://github.com/open-telemetry/opentelemetry-java/blob/main/RELEASING.md#credentials).