diff --git a/src/cdk/scrolling/scrolling.md b/src/cdk/scrolling/scrolling.md
index eb875979e2ae..3729a76ec903 100644
--- a/src/cdk/scrolling/scrolling.md
+++ b/src/cdk/scrolling/scrolling.md
@@ -27,11 +27,7 @@ rest.
same API as [`*ngFor`](https://angular.io/api/common/NgForOf). The simplest usage just specifies the
list of items:
-```html
-
-
{{item}}
-
-```
+
`*cdkVirtualFor` makes the following context variables available to the template:
@@ -47,15 +43,7 @@ list of items:
All of these apply to the index of the item in the data source, not the index in the rendered
portion of the data.
-```html
-
-
- {{item}} ({{index}} of {{count}})
-
-
-```
+
A `trackBy` function can be specified and works the same as the `*ngFor` `trackBy`. The `index`
passed to the tracking function will be the index in the data source, not the index in the rendered
@@ -68,11 +56,7 @@ is reused instead. The size of the view cache can be adjusted via the `templateC
property; setting this size to `0` disables caching. If your templates are expensive in terms of
memory you may wish to reduce this number to avoid spending too much memory on the template cache.
-```html
-
-
{{item}}
-
-```
+
##### Specifying data
`*cdkVirtualFor` accepts data from an `Array`, `Observable`, or `DataSource`. The
@@ -83,17 +67,13 @@ data array that should be rendered. The viewport will call `disconnect` when the
destroyed, which may be the right time to clean up any subscriptions that were registered during the
connect process.
+
+
#### Scrolling over fixed size items
When all items are the same fixed size, you can use the `FixedSizeVirtualScrollStrategy`. This can
be easily added to your viewport using the `itemSize` directive. The advantage of this constraint is
that it allows for better performance, since items do not need to be measured as they are rendered.
-```html
-
- ...
-
-```
-
The fixed size strategy also supports setting a couple of buffer parameters that determine how much
extra content is rendered beyond what is visible in the viewport. The first of these parameters is
`minBufferPx`. The `minBufferPx` is the minimum amount of content buffer (in pixels) that the
@@ -108,11 +88,7 @@ remaining. Since this is below `minBufferPx` the viewport must render more buffe
least enough buffer to get back to `maxBufferPx`. In this case, it renders 4 items (an additional
`200px`) to bring the total buffer size to `290px`, back above `maxBufferPx`.
-```html
-
- ...
-
-```
+
Other virtual scrolling strategies can be implemented by extending `VirtualScrollStrategy`. An
autosize strategy that works on elements of differing sizes is currently being developed in
@@ -125,11 +101,7 @@ out horizontally via CSS. To do this you may want to target CSS at
`.cdk-virtual-scroll-content-wrapper` which is the wrapper element that contains the rendered
content.
-```html
-
- ...
-
-```
+
### Elements with parent tag requirements
Some HTML elements such as `
` and `
` have limitations on the kinds of parent elements they
@@ -138,13 +110,4 @@ their proper parent, and then wrap the whole thing in a `cdk-virtual-scroll-view
that the parent does not introduce additional space (e.g. via `margin` or `padding`) as it will
interfere with the scrolling.
-```html
-
-