Merge pull request #741 from xebia/manage-innersource-program

more clear messaging on readme priority

Author: barneschism

learn-pr/github/manage-innersource-program-github/includes/2-manage-innersource-program.md

@@ -60,7 +60,10 @@ A README file communicates expectations for your project and helps you manage co
 - Include references to the projects on which you depend. These references are a good way to promote the work of others.
 - Use Markdown to guide readers through properly formatted content.
 
-If you put your README file in your repository's root directory, or in the hidden `.github` or `docs` directory, GitHub recognizes and automatically surfaces your README to repository visitors. If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
+If you put your README file in your repository's root directory, or in the hidden `.github` or `docs` directory, GitHub recognizes and automatically surfaces your README to repository visitors. If a repository contains more than one README file, then the file shown is chosen from locations in the following order: 
+1. The `.github` directory  
+2. The repository's root directory  
+3. The `docs` directory  
 
 Check out some [Awesome README examples](https://github.com/matiassingers/awesome-readme?azure-portal=true).