Translate Mar13 situation report into Dutch

Happy weekend @roanvanscheppingen, @Van-Doorslaer, @pleunipennings, @JSHuisman, @JiscaH !

The situation report from March 13 is ready to be translated to Dutch. A branch exists at sit-rep_nl where this can be done, and the file to translate is ncov_sit-rep_nl_2020-03-13.md under the narratives folder: https://github.com/nextstrain/ncov/blob/sit-rep_nl/narratives/ncov_sit-rep_2020-03-13.md.

You can translate directly in this file, but please remember to push often as other people may be working on the translation! You should have access to push to the sit-rep_nl, so there’s no need to create a pull request. Please make sure you’ve accepted an invitation from me to join the ncov repo.

Note that this file is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.)

Comments to help with translation are noted in comment symbols like <! -- Comment -->.

After pushing changes, you can preview them here: https://nextstrain.org/community/narratives/nextstrain/ncov@sit-rep_nl/sit-rep/nl/2020-03-13

Please add your name in parentheses to the end of the author list, so we can credit your work!

After the report is translated and proofread, we’ll publish it to https://nextstrain.org/ and post on Twitter. Please share the report with your Dutch-speaking colleagues, so we can get the information out there!

Note: You may know of other great resources available in Dutch; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Because Nextstrain team members only speak so many languages, this is our best system for doing so. Thanks for understanding.

Please coordinate amongst yourselves on how to best complete the translations. You can trade off weeks; you can use an online editor like hackmd to translate together, whatever works best for you. But when finished, please push it to GitHub for proofreading and review.

@Van-Doorslaer, @pleunipennings, @JSHuisman, since you have backgrounds in phylogenetics, I won’t send it live without a review from one of you. This is to ensure we provide accurate information.

Thank you so very much for your hard work; you all are amazing!

[roanvanscheppingen]

Guys. We are getting too effective! Good job all and especially the Nextstrain team for their around the clock work

[JiscaH]

@cassiawag it’s good to go!

I’ve merged in @rvosa 's proposed edits, just swapped “the Washington monsters are in-between the the monsters of the GP cruiseship” the other way around.

Resolving the conflicts between @pleunipennings patch-1 and the main branch was unambiguous.