A couple of fixes based on in-product rendering limitations.

release-notes/v1_8.md

@@ -11,7 +11,7 @@ MetaSocialImage: 1_8_release-highlights.png
 Welcome to the November release of Visual Studio Code. There are a number of significant updates in this version that we hope you will like, some of the key highlights include:
 
 * **[Hot Exit](#hot-exit)** - Switch context quickly and never lose your changes.
-* **[Focus on Your Code](#focus-on-your-code)** - Enhancements like [Zen Mode](#zen-mode), [Configurable Activity Bar](#configurable-activity-bar), and more.
+* **[Focus on Your Code](#focus-on-your-code)** - Enhancements like Zen Mode, configurable Activity Bar, and more.
 * **[Settings improvements](#settings)** - New experience for configuring VS Code.
 * **[New Selection menu](#selection-menu)** - Easily discover and use the editor selection commands.
 * **[Faster Text Search ](#text-search-performance)** - Find the code you're looking for fast no matter how large your project.
@@ -71,7 +71,7 @@ This release we've added features to help you focus on your highest priority, yo
 
 ### Zen Mode
 
-Per [user requests](https://github.com/Microsoft/vscode/issues/12940), we have added Zen Mode to VS Code. Zen Mode lets you focus on your code by hiding all UI except the editor (no Activity Bar, Status Bar, Sidebar and Panel) and going to full screen. Zen mode can be toggled using the **View** menu, **Command Palette** or by the shortcut `kb(workbench.action.toggleZenMode)`. If you prefer not to transition to full screen, that can be disabled via `workbench.fullScreenZenMode`. Double `kbstyle(Esc)` exits Zen Mode.
+Per [user requests](https://github.com/Microsoft/vscode/issues/12940), we have added Zen Mode to VS Code. Zen Mode lets you focus on your code by hiding all UI except the editor (no Activity Bar, Status Bar, Sidebar and Panel) and going to full screen. Zen mode can be toggled using the **View** menu, **Command Palette** or by the shortcut `kb(workbench.action.toggleZenMode)`. If you prefer not to transition to full screen, that can be disabled via `workbench.fullScreenZenMode`. Double `kbstyle(Escape)` exits Zen Mode.
 
 ### Configurable Activity Bar
 
@@ -355,7 +355,7 @@ Use the 'old' debugger `node` when debugging Node.js versions < 6.3 and the new
 
 >**Note:** If you are using ES6 Proxy in your Node.js app, a Node.js v7.x runtime might even crash when being debugged by the old debugger. This does not happen with `node2`. This issue is tracked in [Microsoft/vscode#12749](https://github.com/Microsoft/vscode/issues/12749).
 
-### Just My Code (`node` and `node2`)
+### Just My Code (node and node2)
 
 We have added a feature to avoid code that you don't want to step through. This feature can be enabled with the `skipFiles` setting in your launch configuration. `skipFiles` is an array of glob patterns for script paths to skip.
 
@@ -391,7 +391,7 @@ In the following example all but a 'math' module is skipped:
 
 >**Note:** The old debugger (`node`) has to emulate the _Just My Code_ feature because the _V8 Debugger Protocol_ does not support it natively. This might result in slow stepping performance.
 
-### Load environment variables from external file (`node`)
+### Load environment variables from external file (node)
 
 The VS Code Node debugger now supports to load environment variables from a file and passes them to the node runtime.
 To use this feature add an attribute `envFile` to your launch config and specify the absolute path to the file containing the environment variables:
@@ -420,7 +420,7 @@ lines="foo\nbar"
 
 ```
 
-### Diagnostics for Source Map Problems (`node2`)
+### Diagnostics for Source Map Problems (node2)
 
 When debugging a Node.js app, you may have seen breakpoints turn gray with the message "Source map problem?". The new `node2` debug adapter has two new features which make it easier to understand these issues.
 
@@ -428,7 +428,7 @@ Typing `.scripts` in the debug console during a debugging session will cause the
 
 And the `sourceMapPathOverrides` option in the launch config allows you to rewrite paths in your sourcemap file to enable sourcemaps in cases where the sourcemap file doesn't  include enough information for the debug adapter to find the correct source files on disk. See more information about both of these features [in the `node2` README](https://github.com/Microsoft/vscode-node-debug2#the-scripts-command).
 
-### Back in time Debugging (`node`)
+### Back in time Debugging (node)
 
 This UI appears automatically for Chakra based Node.js runtimes. For details see this [blog](https://blogs.windows.com/msedgedev/2016/11/29/node-chakracore-vm-neutrality/#cr7wJLzUhp37TVcI.97).