Edit pass

Author: ntrogh

release-notes/v1_96.md

@@ -129,15 +129,15 @@ Additionally, there is a new, experimental, setting to make an Inline Chat hint
 
 ### Terminal Chat
 
-Terminal inline chat has a fresh coat of paint that brings the look and feel much closer to editor inline chat:
+Terminal Inline Chat has a fresh coat of paint that brings the look and feel much closer to editor Inline Chat:
 
 ![Terminal inline chat looks a lot like editor chat now](images/1_96/copilot-terminal-chat.png)
 
 Here are some other improvements of note that were made:
 
-- The layout and positioning of the widget is improved and generally behaves better
-- There's a model picker
-- The buttons on the bottom are now more consistent
+* The layout and positioning of the widget is improved and generally behaves better
+* There's a model picker
+* The buttons on the bottom are now more consistent
 
 ### Performance improvements for `@workspace`
 
@@ -698,10 +698,10 @@ We are excited to announce that we have started work on enabling GPU acceleratio
 
 This is still early and not ready to test out, but we wanted to share some details about the progress that has been made:
 
-- The GPU renderer is using WebGPU behind the scenes.
-- We're focusing currently on feature parity and correctness over performance.
-- There's a fallback mechanism when GPU acceleration is enabled that allows lines to "fallback" to DOM rendering when it's not fully supported. This means that we can self-host early on and currently incompatible lines will show using the DOM approach instead. Some examples of lines that currently fallback lines over 200 characters, lines with certain monaco decorations (eg. fading unused variables), lines that wrap, and so on.
-- Monaco's inline decorations which allow styling the actual elements containing the charatcers posed a big challenge for this feature as they are styled using CSS. The approach we're using to support most inline decorations without breaking or changing API is to detect the CSS attached to these decorations and then support a subset of common CSS properties, falling back if not all styles are supported.
+* The GPU renderer is using WebGPU behind the scenes.
+* We're focusing currently on feature parity and correctness over performance.
+* There's a fallback mechanism when GPU acceleration is enabled that allows lines to "fallback" to DOM rendering when it's not fully supported. This means that we can self-host early on and currently incompatible lines will show using the DOM approach instead. Some examples of lines that currently fallback lines over 200 characters, lines with certain monaco decorations (eg. fading unused variables), lines that wrap, and so on.
+* Monaco's inline decorations which allow styling the actual elements containing the characters posed a big challenge for this feature as they are styled using CSS. The approach we're using to support most inline decorations without breaking or changing API is to detect the CSS attached to these decorations and then support a subset of common CSS properties, falling back if not all styles are supported.
 
 Here's a screenshot of the feature in action, note the yellow line in the gutter tells us what lines are using fallback rendering. This particular case uses fallback rendering due to the `dontShow` parameter having an inline decoration as it's unused: