instruction clarity

Author: bloombar

instructions.md

@@ -52,11 +52,14 @@ To merge code from a feature branch into the `main` branch, do the following:
 
 Replace the contents of the [README.md](./README.md) file with a beautifully-formatted Markdown file including a plain-language **description** of your project and **clear instructions**, including exact **code examples**, for:
 
-- how a developer who wants to import your project into their own code can do so - include documentation for all functions in your package and a link to an example Python program that uses each of them.
-- how a developer who wants to contribute to your project can set up the virtual environment, install dependencies, and build and test your package for themselves.
-
-Include a [badge](https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge) at the top of the `README.md` file showing the result of the latest build/test workflow run.
+Replace the contents of the [README.md](./README.md) file with a beautifully-formatted Markdown file including
 
-Include the names of all teammates as links to their GitHub profiles in the README.md file.
-
-Include a link to your package's page on the PyPI website.
+- a plain-language **description** of your project, including:
+- a [badge](https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge) at the top of the `README.md` file showing the result of the latest build/test workflow run.
+- a link to your package's page on the PyPI website.
+- how a developer who wants to import your project into their own code can do so - include documentation and code examples for all functions in your package and a link to an example Python program that uses each of them.
+- how a developer who wants to contribute to your project can set up the virtual environment, install dependencies, and build and test your package for themselves.
+- the names of all teammates as links to their GitHub profiles in the `README.md` file.
+- instructions for how to configure and run all parts of your project for any developer on any platform - these instructions must work!
+- instructions for how to set up any environment variables and import any starter data into the database, as necessary, for the system to operate correctly when run.
+- if there are any "secret" configuration files, such as `.env` or similar files, that are not included in the version control repository, exact instructions for how to create them and what their contents should be must be supplied to the course admins by the due date.