*: update info string in config fences

This will allow the blocks to render correctly on both GitHub and
coreos.com.

Author: crawford

coreupdate/configure-machines.md

@@ -24,7 +24,7 @@ For example, here is what the Alpha group looks like in CoreUpdate:
 
 Here's the Container Linux Config to use:
 
-```container-linux-config
+```yaml container-linux-config
 update:
   group:  alpha
   server: https://customer.update.core-os.net/v1/update/
@@ -40,7 +40,7 @@ For example, here is what "NYC Production" looks like in CoreUpdate:
 
 Here's the Container Linux Config to use:
 
-```container-linux-config
+```yaml container-linux-config
 update:
   group:  0a809ab1-c01c-4a6b-8ac8-6b17cb9bae09
   server: https://customer.update.core-os.net/v1/update/

etcd/etcd-live-cluster-reconfiguration.md

@@ -6,7 +6,7 @@ This document describes the reconfiguration or recovery of an etcd cluster runni
 
 When [a Container Linux Config][cl-configs] is used to configure an etcd member on a Container Linux node, it compiles a special `/etc/systemd/system/etcd-member.service.d/20-clct-etcd-member.conf` [drop-in unit file][drop-in]. That is, the Container Linux Config below:
 
-```container-linux-config
+```yaml container-linux-config
 etcd:
   advertise_client_urls: http://<PEER_ADDRESS>:2379
   initial_advertise_peer_urls: http://<PEER_ADDRESS>:2380
@@ -76,7 +76,7 @@ This section provides instructions on how to recover a failed etcd member. It is
 
 In this example, we use a 3-member etcd cluster with one failed node, that is still running and has maintained [quorum][majority]. An etcd member node might fail for several reasons: out of disk space, an incorrect reboot, or issues on the underlying system. Note that this example assumes you used [a Container Linux Config][cl-configs] with an etcd [discovery URL][etcd-discovery] to bootstrap your cluster, with the following default options:
 
-```container-linux-config
+```yaml container-linux-config
 etcd:
   advertise_client_urls: http://<PEER_ADDRESS>:2379
   initial_advertise_peer_urls: http://<PEER_ADDRESS>:2380

etcd/getting-started-with-etcd.md

@@ -18,7 +18,7 @@ To upgrade an existing etcd v2 cluster rather than deploy a new one, start with
 
 A Container Linux Config can be used to set any etcd option, like in this example:
 
-```container-linux-config
+```yaml container-linux-config
 etcd:
   name:                        my-etcd-1
   listen_client_urls:          https://10.240.0.1:2379

etcd/tls-etcd-clients.md

@@ -14,7 +14,7 @@ This document assumes three Container Linux nodes will be booted and will be run
 
 Flannel options can be specified in a Container Linux Config. For an example, this is a config that sets the etcd endpoints flannel will use and specifies tls resources to encrypt the connection:
 
-```container-linux-config
+```yaml container-linux-config
 flannel:
   etcd_endpoints: "https://172.16.0.101:2379,https://172.16.0.102:2379,https://172.16.0.103:2379"
   etcd_cafile:    /etc/ssl/etcd/ca.pem
@@ -28,7 +28,7 @@ Suppose you're using `/etc/etcd/ssl` instead, you will need to adjust the flanne
 
 A complete example would look like:
 
-```container-linux-config
+```yaml container-linux-config
 flannel:
   etcd_endpoints: "https://172.16.0.101:2379,https://172.16.0.102:2379,https://172.16.0.103:2379"
   etcd_cafile:    /etc/ssl/etcd/ca.pem
@@ -47,7 +47,7 @@ systemd:
 
 Due to the [deprecation of fleet][fleet-deprecation], Container Linux Configs don't have a convenient syntax for configuring fleet like for flannel. Fleet can still be easily configured however with the use of a systemd drop-in.
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: fleet.service
@@ -67,7 +67,7 @@ systemd:
 
 Example Container Linux Config excerpt for Locksmith configuration:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: locksmithd.service

flannel/flannel-config.md

@@ -26,7 +26,7 @@ $ etcdctl set /coreos.com/network/config '{ "Network": "10.1.0.0/16" }'
 
 You can put this into a drop-in for flanneld.service via a Container Linux Config:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: flanneld.service
@@ -47,7 +47,7 @@ flannel uses UDP port 8285 for sending encapsulated IP packets. Make sure to ena
 
 The last step is to enable `flanneld.service` by creating the `flannel` section in our Container Linux Config. Options for flannel can be specified in this section.
 
-```container-linux-config
+```yaml container-linux-config
 flannel:
 ```
 
@@ -57,7 +57,7 @@ flannel:
 
 Flannel requires SSL certificates to communicate with a secure etcd cluster. By default, flannel looks for these certificates in `/etc/ssl/etcd`. To use different certificates, add `Environment=ETCD_SSL_DIR` to a drop-in file for `flanneld.service`. Use the following configuration snippet to achieve this:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: flanneld.service

fleet/launching-containers-fleet.md

@@ -297,7 +297,7 @@ MachineMetadata=region=east
 
 On Container Linux, only fleet 0.11.x is available under /usr/bin. That one might be obsolete for users who want to try out more recent versions. In that case, users should define their own custom Container Linux Config to be able to run any version of fleet as they want. For example:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   files:
     - path: /opt/bin/fleet-wrapper

os/adding-swap.md

@@ -81,7 +81,7 @@ The block device mounted at `/var/`, `/dev/sdXN`, is the correct filesystem type
 
 The following config sets up a 1GiB swapfile located at `/var/vm/swapfile1`.
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: swap.service

os/adding-users.md

@@ -6,7 +6,7 @@ You can create user accounts on a CoreOS Container Linux machine manually with `
 
 In your Container Linux Config, you can specify many [different parameters](https://github.com/coreos/container-linux-config-transpiler/blob/master/doc/configuration.md) for each user. Here's an example:
 
-```container-linux-config
+```yaml container-linux-config
 passwd:
   users:
     - name: core

os/booting-on-azure.md

@@ -42,7 +42,7 @@ You can provide a raw Ignition config (produced from a Container Linux Config) t
 
 As an example, this config will configure and start etcd:
 
-```container-linux-config:azure
+```yaml container-linux-config:azure
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.

os/booting-on-digitalocean.md

@@ -78,7 +78,7 @@ You can provide a raw Ignition config to Container Linux via the DigitalOcean we
 
 As an example, this config will configure and start etcd:
 
-```container-linux-config:digitalocean
+```yaml container-linux-config:digitalocean
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.

os/booting-on-ec2.md

@@ -122,7 +122,7 @@ You can provide a raw Ignition config to Container Linux via the Amazon web cons
 
 As an example, this Container Linux Config will configure and start etcd:
 
-```container-linux-config:ec2
+```yaml container-linux-config:ec2
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.
@@ -146,7 +146,7 @@ etcd:
 
 Ephemeral disks and additional EBS volumes attached to instances can be mounted with a `.mount` unit. Amazon's block storage devices are attached differently [depending on the instance type](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#InstanceStoreDeviceNames). Here's the Container Linux Config to format and mount the first ephemeral disk, `xvdb`, on most instance types:
 
-```container-linux-config:ec2
+```yaml container-linux-config:ec2
 storage:
   filesystems:
     - mount:
@@ -258,7 +258,7 @@ First we need to create a security group to allow Container Linux instances to c
         </li>
         <li>
           Use <a href="provisioning.md">ct</a> to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field.
-          ```container-linux-config:ec2
+          ```yaml container-linux-config:ec2
           etcd:
             # All options get passed as command line flags to etcd.
             # Any information inside curly braces comes from the machine at boot time.
@@ -332,7 +332,7 @@ First we need to create a security group to allow Container Linux instances to c
         </li>
         <li>
           Use <a href="provisioning.md">ct</a> to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field.
-          ```container-linux-config:ec2
+          ```yaml container-linux-config:ec2
           etcd:
             # All options get passed as command line flags to etcd.
             # Any information inside curly braces comes from the machine at boot time.
@@ -406,7 +406,7 @@ First we need to create a security group to allow Container Linux instances to c
         </li>
         <li>
           Use <a href="provisioning.md">ct</a> to convert the following configuration into an Ignition config, and back in the EC2 dashboard, paste it into the "User Data" field.
-          ```container-linux-config:ec2
+          ```yaml container-linux-config:ec2
           etcd:
             # All options get passed as command line flags to etcd.
             # Any information inside curly braces comes from the machine at boot time.

os/booting-on-ecs.md

@@ -10,7 +10,7 @@ When booting your [Container Linux Machines on EC2](booting-on-ec2.md), configur
 
 Be sure to change `ECS_CLUSTER` to the cluster name you've configured via the ECS CLI or leave it empty for the default. Here's a full config example:
 
-```container-linux-config:ec2
+```yaml container-linux-config:ec2
 systemd:
  units:
    - name: amazon-ecs-agent.service

os/booting-on-google-compute-engine.md

@@ -16,7 +16,7 @@ You can provide a raw Ignition config to Container Linux via the Google Cloud co
 
 As an example, this config will configure and start etcd:
 
-```container-linux-config:gce
+```yaml container-linux-config:gce
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.
@@ -67,7 +67,7 @@ Create 3 instances from the image above using our Ignition from `example.ign`:
 
 Additional disks attached to instances can be mounted with a `.mount` unit. Each disk can be accessed via `/dev/disk/by-id/google-<disk-name>`. Here's the Container Linux Config to format and mount a disk called `database-backup`:
 
-```container-linux-config:gce
+```yaml container-linux-config:gce
 storage:
   filesystems:
     - mount:

os/booting-on-openstack.md

@@ -80,7 +80,7 @@ Container Linux allows you to configure machine parameters, launch systemd units
 
 A common Container Linux Config for OpenStack looks like:
 
-```container-linux-config:openstack-metadata
+```yaml container-linux-config:openstack-metadata
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.

os/booting-on-packet.md

@@ -39,7 +39,7 @@ You can provide a raw Ignition config to Container Linux via Packet's userdata f
 
 As an example, this config will configure and start etcd:
 
-```container-linux-config:packet
+```yaml container-linux-config:packet
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.

os/booting-on-vmware.md

@@ -76,7 +76,7 @@ You can provide a raw Ignition config to Container Linux via VMware's [Guestinfo
 
 As an example, this config will start etcd:
 
-```container-linux-config
+```yaml container-linux-config
 etcd:
   # All options get passed as command line flags to etcd.
   # Any information inside curly braces comes from the machine at boot time.

os/booting-with-pxe.md

@@ -44,7 +44,7 @@ label coreos
 
 Here's a common config example which should be located at the URL from above:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: etcd2.service
@@ -147,7 +147,7 @@ If you plan on using Docker we recommend using a local ext4 filesystem with over
 
 For example, to setup an ext4 root filesystem on `/dev/sda`:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   disks:
   - device: /dev/sda
@@ -167,7 +167,7 @@ And add `root=/dev/sda1` or `root=LABEL=ROOT` to the kernel options as documente
 
 Similarly, to setup a btrfs root filesystem on `/dev/sda`:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   disks:
   - device: /dev/sda

os/cluster-discovery.md

@@ -15,7 +15,7 @@ The discovery URL can be provided to each Container Linux machine via [Container
 
 Boot each one of the machines with identical Container Linux Config and they should be automatically clustered:
 
-```container-linux-config:ec2
+```yaml container-linux-config:ec2
 etcd:
   # generate a new token for each unique cluster from https://discovery.etcd.io/new?size=3
   # specify the initial size of your cluster with ?size=X

os/configuring-date-and-timezone.md

@@ -121,7 +121,7 @@ $ sudo systemctl restart systemd-networkd
 
 NTP time sources can be set in `timesyncd.conf` with a [Container Linux Config][cl-configs] snippet like:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   files:
     - path: /etc/systemd/timesyncd.conf
@@ -147,7 +147,7 @@ $ sudo systemctl start ntpd
 
 or with this Container Linux Config snippet:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: systemd-timesyncd.service
@@ -179,7 +179,7 @@ $ sudo systemctl reload ntpd
 
 Or, in a [Container Linux Config][cl-configs]:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   files:
     - path: /etc/ntp.conf

os/configuring-dns.md

@@ -8,7 +8,7 @@ By default, DNS resolution on Container Linux is handled through `/etc/resolv.co
 
 Here is an example [Container Linux Config][cl-configs] snippet to do that:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   files:
     - path: /etc/nsswitch.conf

os/customize-etcd-unit.md

@@ -8,7 +8,7 @@ etcd supports client certificates as a way to provide secure communication betwe
 
 Please follow the [instruction](generate-self-signed-certificates.md) to know how to create self-signed certificates and private keys.
 
-```container-linux-config
+```yaml container-linux-config
 etcd:
   # More settings are needed here for a functioning etcd daemon
   ca_file:        /path/to/CA.pem

os/customizing-docker.md

@@ -38,7 +38,7 @@ docker -H tcp://127.0.0.1:2375 ps
 
 To enable the remote API on every Container Linux machine in a cluster, use a [Container Linux Config][cl-configs]. We need to provide the new socket file and Docker's socket activation support will automatically start using the socket:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: docker-tcp.socket
@@ -162,7 +162,7 @@ docker images
 
 A Container Linux Config for Docker TLS authentication will look like:
 
-```container-linux-config
+```yaml container-linux-config
 storage:
   files:
     - path: /etc/docker/ca.pem
@@ -249,7 +249,7 @@ journalctl -u docker
 
 If you need to modify a flag across many machines, you can add the flag with a Container Linux Config:
 
-```container-linux-config
+```yaml container-linux-config
 docker:
   flags:
     - --debug
@@ -283,7 +283,7 @@ Proxy environment variables can also be set [system-wide][systemd-env-vars].
 
 The easiest way to use this proxy on all of your machines is via a Container Linux Config:
 
-```container-linux-config
+```yaml container-linux-config
 systemd:
   units:
     - name: docker.service
@@ -321,7 +321,7 @@ systemctl restart docker
 
 The easiest way to use these new ulimits on all of your machines is via a Container Linux Config:
 
-```container-linux-configs
+```yaml container-linux-configs
 systemd:
   units:
     - name: docker.service