fix: add missing blank lines around shortcode alert content

Hugo requires blank lines between alert shortcode tags and their
content. Without them, the alert content is not rendered correctly.

Fixes #1144

Signed-off-by: Nick Nikolakakis <nicknikolakakis@gmail.com>
Signed-off-by: Nick Nikolakakis <nonicked@protonmail.com>

Author: nicknikolakakis

content/en/docs/v3.4/how-to-migrate.md

@@ -13,11 +13,13 @@ etcd v2.Y releases store data in the v2store, which supports the legacy API v2.
 This document focus on how to migrate existing data from the v2store to the v3store. For a detailed guideline of migrating from API v2 to API v3, please refer to [Migrate applications from using API v2 to API v3](https://etcd.io/docs/v3.4/op-guide/v2-migration/).
 
 {{% alert color="warning" %}}
+
 ⚠️ **Deprecated functionality:**
 
 The `etcdctl migrate` command was removed in etcd v3.5.0 ([pull/12971](https://github.com/etcd-io/etcd/pull/12971)). If your etcd cluster is already running v3.5 or higher, you can no longer migrate v2store to v3store using this method.  
 
 You **must use etcdctl v3.4 or earlier** to perform the migration (View note from  [CHANGELOG-3.5](https://github.com/ahrtr/etcd/blob/main/CHANGELOG/CHANGELOG-3.5.md#etcdctl-v3-3)). However please take appropriate precautions when using it, as it is no longer officially supported or tested in recent releases.  
+
 {{% /alert %}}
 
 ## Pre-requisites

content/en/docs/v3.4/op-guide/v2-migration.md

@@ -41,9 +41,11 @@ First, all members in the etcd cluster must converge to the same state. This can
 Second, migrate the v2 keys into v3 with the [migrate][migrate_command] (`ETCDCTL_API=3 etcdctl migrate`) command. The migrate command writes keys in the v2 store to a user-provided transformer program and reads back transformed keys. It then writes transformed keys into the mvcc store. This usually takes at most tens of seconds.
 
 {{% alert title="known issue" color="warning" %}}
+
   The migrate command has a known issue that new members added after the migration do not receive existing data if no .snap file exists.
   The workaround is to perform a snapshot restore after the migration.
   For more information see [GitHub issue](https://github.com/etcd-io/etcd/issues/8804).
+
 {{% /alert %}}
 
 Restart the etcd members and everything should just work.

content/en/docs/v3.5/op-guide/configuration.md

@@ -13,11 +13,13 @@ You can configure etcd through the following:
 - **[Configuration file](#configuration-file)**
 
 {{% alert color="warning" %}}
+
 <i class="fas fa-exclamation-triangle mr-1"></i> **Caution**: If you mix-and-match configuration options, then the following
 rules apply.
 
 - Command-line flags take precedence over environment variables.
 - If you provide a _configuration file_ all command-line flags and environment variables are **ignored**.
+
 {{% /alert %}}
 
 ## Command-line flags
@@ -27,10 +29,12 @@ Flags are presented below using the format `--flag-name DEFAULT_VALUE`.
 The list of flags provided below may not be up-to-date due to ongoing development changes. For the latest available flags, run `etcd --help` or refer to the [etcd help][].
 
 {{% alert color="info" %}}
+
   **Note**: For details concerning new, updated, and deprecated {{< param version >}} flags,
   see [CHANGELOG-{{< psubstr version 1 >}}.md][changelog].
 
   [changelog]: https://github.com/etcd-io/etcd/blob/main/CHANGELOG/CHANGELOG-{{< psubstr version 1 >}}.md
+
 {{% /alert %}}
 
 ### Member
@@ -227,7 +231,9 @@ The list of flags provided below may not be up-to-date due to ongoing developmen
 ### v2 Proxy
 
 {{% alert color="warning" %}}
+
 **<i class="fas fa-exclamation-triangle mr-1"></i> Note**: flags will be deprecated in v3.6.
+
 {{% /alert %}}
 
 
@@ -272,7 +278,9 @@ The list of flags provided below may not be up-to-date due to ongoing developmen
 ### Unsafe features
 
 {{% alert color="warning" %}}
+
 **<i class="fas fa-exclamation-triangle mr-1"></i> Warning**: using unsafe features may break the guarantees given by the consensus protocol!
+
 {{% /alert %}}
 
 ```nocode

content/en/docs/v3.5/op-guide/monitoring.md

@@ -139,7 +139,9 @@ Now Prometheus will scrape etcd metrics every 10 seconds.
 There is a set of [default alerts](https://github.com/etcd-io/etcd/tree/master/contrib/mixin) for etcd v3 clusters for Prometheus.
 
 {{% alert title="Note" color="info" %}}
+
 Note that `job` labels may need to be adjusted to fit a particular need. The rules were written to apply to a single cluster so it is recommended to choose labels unique to a cluster.
+
 {{% /alert %}}
 
 ### Grafana
@@ -164,7 +166,9 @@ Sample dashboard:
 In v3.5 etcd has added support for distributed tracing using [OpenTelemetry](https://github.com/open-telemetry).
 
 {{% alert title="Note" color="info" %}}
+
 This feature is still experimental and can change at any time.
+
 {{% /alert %}}
 
 To enable this experimental feature, pass the `--experimental-enable-distributed-tracing=true` to the etcd server, along with the `--experimental-distributed-tracing-sampling-rate=<number>` flag to choose how many samples to collect per million spans, the default sampling rate is `0`.
@@ -180,7 +184,9 @@ Configure the distributed tracing by starting etcd server with the following opt
 Before enabling the distributed tracing, make sure to have the OpenTelemetry endpoint, if that address differs to the default one, override with the `--experimental-distributed-tracing-address` flag. Due to OpenTelemetry having different ways of running, refer to the [collector documentation](https://opentelemetry.io/docs/collector/getting-started/) to learn more.
 
 {{% alert title="Note" color="info" %}}
+
 There is a resource overhead, as with any observability signal, according to our initial measurements that overhead could be between 2% - 4% CPU overhead.
+
 {{% /alert %}}
 
 [grafana]: http://grafana.org/

content/en/docs/v3.5/op-guide/supported-platform.md

@@ -56,12 +56,14 @@ prints a warning message and exits immediately unless the environment variable
 `ETCD_UNSUPPORTED_ARCH` is set to the target architecture.
 
 {{% alert title="32-bit systems" color="warning" %}}
+
   etcd has **known issues** on 32-bit systems due to a bug in the Go runtime.
   For more information see the [Go issue #599][go-issue] and the [atomic package
   bug note][go-atomic].
 
   [go-atomic]: https://golang.org/pkg/sync/atomic/#pkg-note-BUG
   [go-issue]: https://github.com/golang/go/issues/599
+
 {{% /alert %}}
 
 [etcd maintainers]: https://github.com/etcd-io/etcd/blob/main/OWNERS

content/en/docs/v3.6/benchmarks/etcd-3-watch-memory-benchmark.md

@@ -5,7 +5,9 @@ description: Performance measures for etcd watchers
 ---
 
 {{% alert title="Note" color="info" %}}
+
 The watch features are under active development, and their memory usage may change as that development progresses. We do not expect it to significantly increase beyond the figures stated below.
+
 {{% /alert %}}
 
 A primary goal of etcd is supporting a very large number of watchers doing a massively large amount of watching. etcd aims to support O(10k) clients, O(100K) watch streams (O(10) streams per client) and O(10M) total watchings (O(100) watching per stream). The memory consumed by each individual watching accounts for the largest portion of etcd's overall usage, and is therefore the focus of current and future optimizations.

content/en/docs/v3.6/downgrades/downgrade_3_5.md

@@ -16,7 +16,9 @@ Before [starting a downgrade](#downgrade-procedure), read through the rest of th
 content/en/docs/v3.5/op-guide/authentication/rbac.md
 
 {{% alert title="Note" color="info" %}}
+
 If your cluster enables auth, rolling downgrade from 3.5 isn't supported because 3.5 [changes a format of WAL entries related to auth](https://github.com/etcd-io/etcd/pull/11943). You can follow the [authentification instructions](../../op-guide/authentication/rbac/) to disable auth, and delete all users first.
+
 {{% /alert %}}
 
 Highlighted breaking changes from 3.5 to 3.4:
@@ -26,7 +28,9 @@ Highlighted breaking changes from 3.5 to 3.4:
 If you are using any of the following flags in your 3.5 configurations, make sure to remove, rename, or change the default value when downgrading to 3.4.
 
 {{% alert title="Note" color="info" %}}
+
 The diff is based on version 3.5.14 and v.3.4.33. The actual diff would be dependent on your patch version, check with `diff <(etcd-3.5/bin/etcd -h | grep \\-\\-) <(etcd-3.4/bin/etcd -h | grep \\-\\-)` first.
+
 {{% /alert %}}
 
 ```diff

content/en/docs/v3.6/downgrades/downgrade_3_6.md

@@ -20,7 +20,9 @@ Highlighted breaking changes from v3.6 to v3.5:
 If you are using any of the following flags in your v3.6 configurations, make sure to remove, rename, or change the default value when downgrading to v3.5.
 
 {{% alert title="Note" color="info" %}}
+
 The diff is based on version v3.6.0 and v.3.5.18. The actual diff would be dependent on your patch version, check with `diff <(etcd-3.6/bin/etcd -h | grep \\-\\-) <(etcd-3.5/bin/etcd -h | grep \\-\\-)` first.
+
 {{% /alert %}}
 
 ```diff
@@ -223,7 +225,9 @@ COMMENT
 ```
 
 {{% alert title="Note" color="info" %}}
+
 Once downgrade is enabled, the cluster will remain operating with v3.5 protocol even if all the servers are still running the v3.6 binary, unless the downgrade is canceled with `etcdctl downgrade cancel`
+
 {{% /alert %}}
 
 #### Step 5: stop one existing etcd server
@@ -309,7 +313,9 @@ COMMENT
 ```
 
 {{% alert title="Note" color="info" %}}
+
 You will see the `DOWNGRADE ENABLED` is false for the v3.5 server, because the downgrade info is not implemented in v3.5 status endpoint, downgrade is still enabled for the cluster at this point.
+
 {{% /alert %}}
 
 #### Step 7: repeat *step 5* and *step 6* for rest of the members

content/en/docs/v3.6/feature-gates/index.md

@@ -103,8 +103,10 @@ A *Beta* feature means:
   discovering new hard-to-spot bugs through wider adoption.
 
 {{% alert title="Note" color="info" %}}
+
 Please do try *Beta* features and give feedback on them!
 After they exit beta, it may not be practical for us to make more changes.
+
 {{% /alert %}}
 
 A *General Availability* (GA) feature is also referred to as a *stable* feature. It means:

content/en/docs/v3.6/install.md

@@ -72,7 +72,9 @@ source by following these steps:
 ## Installation via OS packages
 
 {{% alert title="Warning" color="warning" %}}
+
 etcd installations through OS package managers can deliver outdated versions since they are not being automatically maintained nor officially supported by etcd project. Therefore use OS packages with caution.*
+
 {{% /alert %}}
 
 There are various ways of installing etcd on different operating systems and these are just some examples how it can be done.
@@ -97,7 +99,9 @@ $ etcd --version
 ## Linux
 
 {{% alert title="Warning" color="warning" %}}
+
 Although installing etcd through many major Linux distributions' official repositories and package managers is possible, the published versions can be significantly outdated. So, installing this way is strongly discouraged.
+
 {{% /alert %}}
 
 The recommended way to install etcd on Linux is either through [pre-built binaries](#install-pre-built-binaries) or by using Homebrew.