Develop: Correct typo from 'pare' to 'parse' in documentation (#16860)

Author: lucas-zimerman

develop-docs/engineering-practices/commit-messages.mdx

@@ -16,7 +16,7 @@ sidebar_order: 10
 
 ### Merge vs Rebase
 
-Sentry uses a rebase workflow. That means that every commit on its own should be a clear, functional, and stable change. This means that when you’re building a new feature, you should try to pare it down into functional steps, and when that’s not reasonable, the end patch should be a single commit. This is counter to having a Pull Request which may include “fix [unmerged] behavior”. Those commits should be squashed, and the final patch when landed should be rebased.
+Sentry uses a rebase workflow. That means that every commit on its own should be a clear, functional, and stable change. This means that when you’re building a new feature, you should try to parse it down into functional steps, and when that’s not reasonable, the end patch should be a single commit. This is counter to having a Pull Request which may include “fix [unmerged] behavior”. Those commits should be squashed, and the final patch when landed should be rebased.
 
 Remember: each commit should follow the commit message format and be stable (green build).