---
number: 91
title: Update GETTING_STARTED.md with fenced code blocks
author: steffen
state: MERGED
createdAt: '2019-11-24T12:32:09Z'
updatedAt: '2019-11-24T12:33:13Z'
closedAt: '2019-11-24T12:33:13Z'
mergedAt: '2019-11-24T12:33:13Z'
head: patch-1
base: dev
url: 'https://github.com/neomjs/neo/pull/91'
---
Please make sure to read the Contributing Guidelines:

https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe: Markdown formatting

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch, _not_ the `master` branch
- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**

I recommend using fenced code blocks (and code highlighting) for markdown documentation files, see https://help.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks.
