Merge pull request #21523 from plskz/patch-1

Update community exchange requirements

Author: cmwilson21

content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md

@@ -30,11 +30,14 @@ For a submission with a purpose of `Learn`, your repository must have:
 - A description.
 - A LEARN.md file to provide step-by-step instructions, with text and/or media, on how you built your project. Ideally, your LEARN.md file will deconstruct your project into small components and provide thorough details of each step, so that other students can code their project by following your instructions.
 - A README.md file to provide a detailed description of your project.
+- A License so others are aware of what they can and cannot do with your source code.
 
 For a submission with a purpose of `Collaborate`, your repository must have:
 - A description.
 - A README.md file to provide a detailed description of your project.
+- A License so others are aware of what they can and cannot do with your source code.
 - One or more issues for collaborators to work on.
+- CONTRIBUTING.md file to communicate how to contribute to your project.
 
 A good repository submission for both `Learn` and `Collaborate` purposes, is a repository that follows community standards. For more information, see "[About community profiles for public repositories](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)."