remove accordions that won't expand

content/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/_index.md

@@ -15,15 +15,15 @@ In this installation scenario, you'll install Docker on a single Linux host, and
 > **Want to use an external load balancer?**
 > See [Docker Install with an External Load Balancer]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/single-node-install-external-lb) instead.
 
-## Requirements for OS, Docker, Hardware, and Networking
+# Requirements for OS, Docker, Hardware, and Networking
 
 Make sure that your node fulfills the general [installation requirements.]({{<baseurl>}}/rancher/v2.x/en/installation/requirements/)
 
-## 1. Provision Linux Host
+# 1. Provision Linux Host
 
 Provision a single Linux host according to our [Requirements]({{<baseurl>}}/rancher/v2.x/en/installation/requirements) to launch your Rancher server.
 
-## 2. Choose an SSL Option and Install Rancher
+# 2. Choose an SSL Option and Install Rancher
 
 For security purposes, SSL (Secure Sockets Layer) is required when using Rancher. SSL secures all Rancher network communication, like when you login or interact with a cluster.
 
@@ -36,19 +36,19 @@ For security purposes, SSL (Secure Sockets Layer) is required when using Rancher
 
 Choose from the following options:
 
-{{% accordion id="option-a" label="Option A-Default Self-Signed Certificate" %}}
+### Option A: Default Rancher-generated Self-signed Certificate
 
 If you are installing Rancher in a development or testing environment where identity verification isn't a concern, install Rancher using the self-signed certificate that it generates. This installation option omits the hassle of generating a certificate yourself.
 
 Log into your Linux host, and then run the minimum installation command below.
 
-```
+```bash
 docker run -d --restart=unless-stopped \
 	-p 80:80 -p 443:443 \
 	rancher/rancher:latest
 ```
-{{% /accordion %}}
+
-{{% accordion id="option-b" label="Option B-Bring Your Own Certificate: Self-Signed" %}}
+### Option B: Bring Your Own Certificate, Self-signed
 In development or testing environments where your team will access your Rancher server, create a self-signed certificate for use with your install so that your team can verify they're connecting to your instance of Rancher.
 
 > **Prerequisites:**
@@ -59,14 +59,14 @@ In development or testing environments where your team will access your Rancher
 
 After creating your certificate, run the Docker command below to install Rancher. Use the `-v` flag and provide the path to your certificates to mount them in your container.
 
-| Placeholder         | Description                                                  |
+| Placeholder         | Description     |
-| ------------------- | ------------------------------------------------------------ |
+| ------------------- | --------------------- |
 | `<CERT_DIRECTORY>`  | The path to the directory containing your certificate files. |
 | `<FULL_CHAIN.pem>`  | The path to your full certificate chain.                     |
 | `<PRIVATE_KEY.pem>` | The path to the private key for your certificate.            |
 | `<CA_CERTS>`        | The path to the certificate authority's certificate.         |
 
-```
+```bash
 docker run -d --restart=unless-stopped \
 	-p 80:80 -p 443:443 \
 	-v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
@@ -75,8 +75,7 @@ docker run -d --restart=unless-stopped \
 	rancher/rancher:latest
 ```
 
-{{% /accordion %}}
+### Option C: Bring Your Own Certificate, Signed by a Recognized CA
-{{% accordion id="option-c" label="Option C-Bring Your Own Certificate: Signed by Recognized CA" %}}
 
 In production environments where you're exposing an app publicly, use a certificate signed by a recognized CA so that your user base doesn't encounter security warnings.
 
@@ -90,13 +89,13 @@ After obtaining your certificate, run the Docker command below.
 - Use the `-v` flag and provide the path to your certificates to mount them in your container. Because your certificate is signed by a recognized CA, mounting an additional CA certificate file is unnecessary.
 - Use the `--no-cacerts` as argument to the container to disable the default CA certificate generated by Rancher.
 
-| Placeholder         | Description                                                  |
+| Placeholder         | Description    |
-| ------------------- | ------------------------------------------------------------ |
+| ------------------- | ----------------------------- |
 | `<CERT_DIRECTORY>`  | The path to the directory containing your certificate files. |
 | `<FULL_CHAIN.pem>`  | The path to your full certificate chain.                     |
 | `<PRIVATE_KEY.pem>` | The path to the private key for your certificate. |
 
-```
+```bash
 docker run -d --restart=unless-stopped \
 	-p 80:80 -p 443:443 \
 	-v /<CERT_DIRECTORY>/<FULL_CHAIN.pem>:/etc/rancher/ssl/cert.pem \
@@ -105,8 +104,7 @@ docker run -d --restart=unless-stopped \
 	--no-cacerts
 ```
 
-{{% /accordion %}}
+### Option D: Let's Encrypt Certificate
-{{% accordion id="option-d" label="Option D-Let's Encrypt Certificate" %}}
 
 > **Remember:** Let's Encrypt provides rate limits for requesting new certificates. Therefore, limit how often you create or destroy the container. For more information, see [Let's Encrypt documentation on rate limits](https://letsencrypt.org/docs/rate-limits/).
 
@@ -130,7 +128,6 @@ docker run -d --restart=unless-stopped \
 	rancher/rancher:latest \
 	--acme-domain <YOUR.DNS.NAME>
 ```
-{{% /accordion %}}
 
 ## Advanced Options