Update the instruction order in contributing file and release file

Author: Mansi-mParticle

CONTRIBUTING.md

@@ -6,10 +6,28 @@ Thanks for contributing! Please read this document to follow our conventions for
 ## Setting Up
 
 1. Fork the repository and then clone down your fork
-2. Commit your code per the conventions below, and PR into the mParticle SDK master branch
+2. Commit your code per the conventions below, and PR into the mParticle SDK main branch
 3. Your PR title will be checked automatically against the below convention (view the commit history to see examples of a proper commit/PR title). If it fails, you must update your title
 4. Our engineers will work with you to get your code change implemented once a PR is up
 
+
+## Development Process
+
+1. Fork the repo and create your branch from `main`
+2. Make your changes
+3. Add tests for any new functionality
+4. Run the test suite to ensure tests (both new and old) all pass
+6. Update the documentation
+7. Create a Pull Request
+
+
+### Pull Requests
+
+* Fill in the required template
+* Follow the [Android style guide](https://developer.android.com/kotlin/style-guide)
+* Include screenshots and animated GIFs in your pull request whenever possible
+* End all files with a newline
+
 ### PR Title and Commit Convention
 
 PR titles should follow conventional commit standards. This helps automate the release process.
@@ -38,42 +56,6 @@ The following lists the different types allowed in the commit message:
 - **revert**: Revert commit
 - **build**: Changes that affect the build system or other dependencies
 
-
-
-### Reporting Bugs
-
-This section guides you through submitting a bug report for the mParticle Android SDK. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
-
-Before creating bug reports, please check [existing issues](https://github.com/mParticle/mparticle-android-sdk/issues) as you might find out that you don't need to create one.
-
-**When you are creating a bug report, please include as many details as possible:**
-
-* Use a clear and descriptive title
-* Describe the exact steps which reproduce the problem
-* Provide specific examples to demonstrate the steps
-* Describe the behavior you observed after following the steps
-* Explain which behavior you expected to see instead and why
-* Include logcat output and stack traces if applicable
-* Include your SDK version and Android OS version
-
-
-### Pull Requests
-
-* Fill in the required template
-* Follow the [Android style guide](https://developer.android.com/kotlin/style-guide)
-* Include screenshots and animated GIFs in your pull request whenever possible
-* End all files with a newline
-
-## Development Process
-
-1. Fork the repo and create your branch from `main`
-2. Run the tests to ensure they all pass
-3. Add tests for any new functionality
-4. Make your changes
-5. Run the test suite to ensure tests still pass
-6. Update the documentation
-7. Create a Pull Request
-
 ### Testing
 
 We use JUnit and Mockito for our testing framework. Please write tests for new code you create. Before submitting your PR, ensure all tests pass by running:
@@ -95,6 +77,24 @@ We use JUnit and Mockito for our testing framework. Please write tests for new c
 
 Make sure all tests pass successfully before submitting your PR. If you encounter any test failures, investigate and fix the issues before proceeding.
 
+
+### Reporting Bugs
+
+This section guides you through submitting a bug report for the mParticle Android SDK. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
+
+To notify our team about an issue, please submit a ticket through our [mParticles support page](https://support.mparticle.com/hc/en-us/requests/new).
+
+**When you are creating a ticket, please include as many details as possible:**
+
+* Use a clear and descriptive title
+* Describe the exact steps which reproduce the problem
+* Provide specific examples to demonstrate the steps
+* Describe the behavior you observed after following the steps
+* Explain which behavior you expected to see instead and why
+* Include logcat output and stack traces if applicable
+* Include your SDK version and Android OS version
+
+
 ## License
 
 By contributing to the mParticle Android SDK, you agree that your contributions will be licensed under its [Apache License 2.0](LICENSE).

RELEASE.md

@@ -4,14 +4,13 @@ This document outlines the process for releasing the mParticle Android SDK and i
 
 ## Step 1: Preparing the SDK for Release
 
-The Android SDK and kits are released through the [public repository](https://github.com/mParticle/mparticle-android-sdk) using GitHub Actions. The SDK and kits are currently coupled together in the release process.
+The Android SDK and kits are released using GitHub Actions. The SDK and kits are currently coupled together in the release process.
 
 ### Pre-release Checklist
-- Ensure all commits are in the public development branch
-- Verify linear history between development and main branches
+- Ensure all commits are in the public main branch
 - Review `release.yml` in the repo for specific workflow details
-- The release job deploys the most current snapshot of development branch to main branch
-  > Note: We rarely merge anything to development branch that isn't ready for immediate release.
+- The release job deploys the most current snapshot of main branch release tag to main branch
+
 
 ## Step 2: Release via GitHub Actions
 
@@ -52,9 +51,10 @@ The Android SDK and kits are released through the [public repository](https://gi
 
 1. Navigate to the Actions tab
 2. Select "release SDK"
-3. Run the workflow from main branch
-4. Select "not dry run" 
-   > Note: Dry run performs steps up to semantic release only
+3. Run the workflow from main branch with "dry run" option first
+   > Important: Always start with a dry run to validate the release process. This will perform all steps up to semantic release without actually publishing, helping catch potential issues early.
+4. If the dry run succeeds, run the workflow again with "not dry run" option to perform the actual release
+   > Note: Only proceed with the actual release after confirming a successful dry run
 
 ### Important Notes
 
@@ -71,7 +71,7 @@ The Android SDK and kits are released through the [public repository](https://gi
 
 After a successful build through GitHub Actions, verify:
 1. Public repo has a new semantic release tag
-2. New artifact is present in Sonatype
+2. New artifact is present in [Sonatype](https://central.sonatype.com/publishing) 
 
 ## Troubleshooting