Skip to content

Commit cf856bf

Browse files
authored
fix markdown in blog post v7.0.0 (#994)
1 parent 9e68065 commit cf856bf

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

locale/en/blog/release/v7.0.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ As an odd numbered release, in accordance with our [Long Term Support plan](http
1616

1717
The general rule for deciding which version of Node.js to use is:
1818

19-
* Stay on Node.js v4 or upgrade to Node.js v6 if you need *stability and have a complex production environment, e.g. you are a medium or large enterprise.
19+
* Stay on Node.js v4 or upgrade to Node.js v6 if you need *stability* and have a complex production environment, e.g. you are a medium or large enterprise.
2020
* Upgrade to Node.js v7 if you have the ability to upgrade versions quickly and easily without disrupting your environment and want to play with the latest features as they arrive.
2121

2222
The release notes below are annotated with the main breaking changes. Note that because this new version of Node.js is shipping with a new version of V8, existing native addons will need to be recompiled or runtime errors will occur when trying to load them. Use `npm rebuild` or simply remove your `node_modules` and `npm install` from scratch.

0 commit comments

Comments
 (0)