Spacing between paragraphs and list elements is very tight vertically

[rmloveland]

Not sure if this is possibly related to what is mentioned in #9430 or #9436.

Screenshot:

HTML for the screenshotted region:

   <p>This page has high-level information about how to configure a <a href="multiregion-overview.html">multi-region cluster&#39;s</a> <a href="multiregion-overview.html#survival-goals">survival goals</a> and <a href="multiregion-overview.html#table-locality">table locality</a>.</p>

<p>The options for configuring your multi-region cluster include:</p>

<ul>
<li><p><em>Change nothing</em>: Using the <a href="multiregion-overview.html#default-settings">default settings</a>, you get zone survival, low-latency single-region writes, and multi-region stale reads.</p></li>
<li><p><em>Change only <a href="multiregion-overview.html#survival-goals">survival goals</a></em>: In this configuration, you move from availability zone (AZ) to get region survival, single-region writes, and multi-region stale reads. This configuration is useful for single-region apps that need higher levels of survival.</p></li>
<li><p><em>Change only <a href="multiregion-overview.html#table-locality">table locality</a></em>: In this configuration, you accept the default zone survival, and optimize for low-latency multi-region reads and writes. This is useful for multi-region apps that require different read/write latency guarantees for different tables in the database, and are not concerned with surviving a region failure.</p></li>
<li><p><em>Change both <a href="multiregion-overview.html#survival-goals">survival goals</a> and <a href="multiregion-overview.html#table-locality">table locality</a></em>: In this configuration, you upgrade from zone to region survival, and optimize for low-latency multi-region reads.  Multi-region writes are higher-latency because they have to move across the network. This is useful for multi-region apps that want a high level of survival.</p></li>
</ul>

<p>The table below offers another view of how the configuration options described above map to:</p>

<ul>
<li>The performance characteristics of specific survival goal/table locality combinations.</li>
<li>The types of applications that can benefit from each combination.</li>
</ul>

[ericharmeling]

+10000

There is absolutely no padding between any paragraphs, unless you explicitly add a <br>, which was not the case before the redesign. This makes reading prose in our docs very difficult.

For example:

This is three separate paragraphs.

[jseldess]

100% agree. Already tracking this in #9849.