Formatting issues in Employee Open Source Engagement guide

[alice-sowerby]

A few things have not rendered correctly due to Markdown errors:

Start with listening and learning about the project, its people and its culture. There usually is a lot of documentation and public archives of communication which will give you a very good idea of how the community works. Make use of this opportunity. Don’t introduce yourself to a project as somebody who knows it all.

This paragraph is supposed to be italicised. The asterisks are not supposed to be visible.

Don’t withdraw resources suddenly. Instead, give proper notification and share an exit plan. Provide clear documentation that will allow the community to pick up projects when your company decides to withdraw its support.*

This paragraph is supposed to be italicised. The asterisks are not supposed to be visible. There is not supposed to be a bullet point at the start.