# Release PR documentation

### Make following changes in plugin’s main file ( i.e. content-approval-workflow.php):
1. Update Version number in header comments and make changes if any.
2. Update constant CONTENT_APPROVAL_WORKFLOW_VERSION in code.

### Make following changes in README.txt file and README.md:
1. Update configurations like stable tag, tested up to, requires at least, release date.
2. Add new features if any.
3. Add benefits if any.
4. Update installation process if any changes.
5. Update frequently asked questions if any.
6. Update changelog.
7. Update bug fixes.
8. Update how it works if any.

**Go through the documentation.md file and make changes if needed.**

# Follow while reviewing peer’s PR
### Here are some things to consider when reviewing a PR for a WordPress site:
**1. Code Quality:**
- Code Consistency.
- WordPress coding standard.
- Readability: Ensure variable names, functions, and comments are clear.
- Check if the code is well-documented and easy to understand.
- Check translation in the code.

**2. Functionality:**
- Check the task result in the browser.
- Check compatibility with existing functionality.
- Check compatibility with the current version of WordPress.

**3. Security:**
- Check Sanitization and Validation.
- Check proper user capabilities and permissions are considered.
- Ensure that no sensitive information, such as API keys or credentials, is exposed in the code.

**4. Performance:**
- Check Queries and Database Interactions for efficiency.
- Make sure there are no unnecessary queries.

**5. Testing:**
- Check for responsiveness on different devices.
- Test the changes in various browsers to ensure cross-browser compatibility.

**6. Documentation:**
- Ensure that the code is well-commented, explaining complex or critical sections.
- Check block documentation of the code.

By considering these aspects during your pull request review, you can help maintain a high standard of code quality and ensure the stability and security of the WordPress site.