Update how-to-submit.md

how-to-submit.md

@@ -2,33 +2,44 @@
 
 _This guide walks you through how to submit your methodology onto this WEATS document repository. The way this works in github is it creates a copy of the WEATS repository into your account. You will then make changes to your copy of the WEATS repository, and then submit a Pull Request, which represents a change that you would like to make to the primary WEATS repository._
 
-1. Write up your methodology in whatever text document you are most comfortable with. Our document repository is this Github repository, which renders documents in a format called Markdown, so it would be easiest to write your methodology in that format. However, these instructions include a way to convert any text to markdown if you wrote them in Google Docs or Microsoft Word.
-
-2. To submit your methodology, you will create a Pull Request on our WEATS github repository. The simplest way to do that is to first attempt to create a new file directly on the repository. You can do that by clicking the “+” Sign to the right of the “Go to file” button. Then click “Create new file”, as shown below.
+### 1. Write up your methodology in whatever text document you are most comfortable with. Our document repository is this Github repository, which renders documents in a format called Markdown, so it would be easiest to write your methodology in that format. However, these instructions include a way to convert any text to markdown if you wrote them in Google Docs or Microsoft Word.
+---
+### 2. To submit your methodology, you will create a Pull Request on our WEATS github repository. The simplest way to do that is to first attempt to create a new file directly on the repository. You can do that by clicking the “+” Sign to the right of the “Go to file” button. Then click “Create new file”, as shown below.
 
 ![](https://lh7-us.googleusercontent.com/docsz/AD_4nXdpDybDNdUG2cROGZ4nsXy6eLqg4N5mrkCPoRbJVT2wB7BMnbk2-6WKJoJunsulNDT5IvNPfsKK2oDy17ryknZFoabEit0lVuEhePYukCxAgnp9GdZI0cXtfsQc4OLbhKcgeXWOjkOLULUpd9tvOTR5IUD0?key=aRRrnxOzZnP06EN6jI_DLw)
 
-3. You will end up with a page that allows you to paste in your methodology in markdown. If you wrote your methodology in Microsoft Word or Google Docs, you can use [this website](https://gdoc2md.com/) to convert it to Markdown.
+---
+### 3. A page will come up asking if you want to fork the repository. Click "Fork this repository" to continue.
+
+![](https://lh7-us.googleusercontent.com/docsz/AD_4nXcGe39uDShfX5nv0vVXYbp3weMzhgsVYmgfvqRvH5_Td6wQm4OJlVz8zYzJLNJF3n3pq34R5IGTwpg7KwyXPHatulTStijS0yhQThtnsBOOu4a5kjmv2gP1AiiSozt8tdYW9jSD9NCTrqzYejugp3fG96qY?key=aRRrnxOzZnP06EN6jI_DLw)
+
+---
+### 4. You will end up with a page that allows you to paste in your methodology in markdown. If you wrote your methodology in Microsoft Word or Google Docs, you can use [this website](https://gdoc2md.com/) to convert it to Markdown.
 
-   1. Make sure to fill out the “Name your file” with a file that ends with the suffix “.md”. This will allow you to use the “Edit” and “Preview” button to toggle between the raw Markdown and how it will be rendered on Github.![](https://lh7-us.googleusercontent.com/docsz/AD_4nXdMSswetj5f0tL0g2bveBFTQWYQYV9SdtCCGE2L7XizxDXh6_dRaYsXjhJYlrsB19zB8yXFUBBBeSeVB5UqKrYgMkTPjwAB6_PBbZjD6w7DjlQDMmY3-fFqc5_u1HAaeHPqVHWctKiKr9VO4J5bNCWJmp_V?key=aRRrnxOzZnP06EN6jI_DLw)
+#### Make sure to fill out the “Name your file” with a file that ends with the suffix “.md”. This will allow you to use the “Edit” and “Preview” button to toggle between the raw Markdown and how it will be rendered on Github.![](https://lh7-us.googleusercontent.com/docsz/AD_4nXdMSswetj5f0tL0g2bveBFTQWYQYV9SdtCCGE2L7XizxDXh6_dRaYsXjhJYlrsB19zB8yXFUBBBeSeVB5UqKrYgMkTPjwAB6_PBbZjD6w7DjlQDMmY3-fFqc5_u1HAaeHPqVHWctKiKr9VO4J5bNCWJmp_V?key=aRRrnxOzZnP06EN6jI_DLw)
 
-4. Paste your methodology into the document. When you click Preview, you should see your methodology rendered in a way that resembles what it looked like in the Google Doc.
+#### Paste your methodology into the document. When you click Preview, you should see your methodology rendered in a way that resembles what it looked like in the Google Doc.
 
 ![](https://lh7-us.googleusercontent.com/docsz/AD_4nXfX0ETT1q6niLmBl7ZHSELFaPVAbYyjPmsoIySCzj_l1_aFstAVenPlQwqB-h8LPr7gh2q9wEiBrEpHFsw8uh1Iw3fY_3gsq0J0LfNrF-nMYEZRT10CFnicIl37YG3W2Y6wLo2hk7_Ib3-Im44Wnuo5vC8?key=aRRrnxOzZnP06EN6jI_DLw)
 
-5. When you are done, click the green “Commit Changes…” button and a pop-up will appear. You don’t need to write anything in this description, a later step will provide an opportunity for you to explain your proposed methodology and any additional information you think reviewers might need. When you have completed this, click “Propose changes”
+---
+### 5. When you are done, click the green “Commit Changes…” button and a pop-up will appear. You don’t need to write anything in this description, a later step will provide an opportunity for you to explain your proposed methodology and any additional information you think reviewers might need. When you have completed this, click “Propose changes”
 
 ![](https://lh7-us.googleusercontent.com/docsz/AD_4nXc41Q4YEC5L0BpzGcVIwDkSu4l-TSTRM38lZAJNG1DsjoAvii0qdayAetOy0VXgZgSvhAAo-aheXkyuGlODjwWIDECJ_1xU0acZgAg4xi2i5Asen7cIxz_ybBoXIdq3cD4COW5U6FqoP9Gt6b6DhyYw2tU?key=aRRrnxOzZnP06EN6jI_DLw)
 
-6. You will be redirected to a page that shows a summary of your changes, as well as a page that allows you to Create a pull request. Click the “Create pull request” button.
+---
+### 6. You will be redirected to a page that shows a summary of your changes, as well as a page that allows you to Create a pull request. Click the “Create pull request” button.
 
 ![](https://lh7-us.googleusercontent.com/docsz/AD_4nXdtoXo2hYGrXs49zi08ESMZd1IVl6bfGt7WKJ001TWw1wdNgzIKIkei1SV0wzBWbxzEY7LUpDh5dh6JIIFhz_lYdmJe-HJFjQ03U05Nb40WeOTv74yuGJsySFPYhRmvbmwct30DBDtXwJA3lVDTqs-RgaTs?key=aRRrnxOzZnP06EN6jI_DLw)
 
-7. This will redirect you to a page that will allow you to add information that will be publicly shown alongside the methodology. This is where you can provide a summary of the methodology as well as any additional information you’d want reviewers to see. This can even include supplementary files. When you are done, click the “Create pull request” and a pull request will show up in the WEATS repository for review!
+---
+### 7. This will redirect you to a page that will allow you to add information that will be publicly shown alongside the methodology. This is where you can provide a summary of the methodology as well as any additional information you’d want reviewers to see. This can even include supplementary files. When you are done, click the “Create pull request” and a pull request will show up in the WEATS repository for review!
 
 ![](https://lh7-us.googleusercontent.com/docsz/AD_4nXcjDZ84C83-h-i4HA94k99InZlpXrEZfp0IzTKyZTZrnX8ndZUCusyBY7VaT6MzDF2_kzIEgy9m3-BT4a0aYW9a83SL2ZQSva4XCb_YWuWJXeTFGnz6xhpmnw8e047cDs9vWtHHWtooPo-0U-Zh5x0YcDdN?key=aRRrnxOzZnP06EN6jI_DLw)
 
-8. After clicking the “Create pull request” button, your Pull Request should show up on the WEATS Repository. You should be able to see it by clicking the “Pull Requests Tab”.
+---
+### 8. After clicking the “Create pull request” button, your Pull Request should show up on the WEATS Repository. You should be able to see it by clicking the “Pull Requests Tab”.
 
 ![](https://lh7-us.googleusercontent.com/docsz/AD_4nXfEF_yqz7fCMPrz2Z-AMf4cxHtIphRQLcTAdAAtWJCsE_rC-nHal-7sigLRpJ24g9VspkwYaeCWnqtaynlzvQySuUYRqC6qWb4NGMF3tkdy2YqQkq5LchsCidHYQ-PP0BlL9yL3KIdWWN3yJtNecSDru84?key=aRRrnxOzZnP06EN6jI_DLw)
 
+### Thank you for submitting a methodology to the OpenEAC Alliance! The Steering Committee will reach out with next steps.