Updated Preparing a Contribution Proposal (markdown)

Preparing-a-Contribution-Proposal.md

@@ -16,6 +16,8 @@ For example if you are planning to start a new model to track students, you coul
 
 ERPNext also has thousands of users, and all these users are going to discover and use the feature you are going to build. The most important thing for these users is that your new feature must *look and behave* in a consistent manner to the existing features, so that the user does not have to learn a new *way* of doing things. This means how things are named, how objects are laid out on the screen etc.
 
+_Example: [#7538 [Feature] Customer and Supplier as one Party](https://github.com/frappe/erpnext/issues/7538)_
+
 ### 4. Start with a GitHub Issue
 
 Summarize your discussion and start with a GitHub Issue. Also post your design with a tag `[Proposal]` on both GitHub and discuss. 
@@ -32,4 +34,3 @@ In your Issue, make sure to mention
 Make sure you get at least some feedback from the maintainers before you start building your feature, since this will help the maintainers when they have to merge the issue.
 
 If your contribution is very significant, don't hesitate to @-tag or ask a maintainer for a call. A good way to select who to call is based on who has worked on similar or adjacent features to the one you are proposing.
-