Minor, markdown fixes

Signed-off-by: Joachim Wiberg <[email protected]>

Author: troglobit

_posts/2024-03-08-containers.md

@@ -8,22 +8,20 @@ tags: [container, containers, docker, podman]
 
 ![Docker whale](/assets/img/docker.webp){: width="200" .right}
 
-A network operating system for switches and routers, that runs Docker?
+An operating system for switches, routers, and end devices that runs Docker?
 
 Yes, as of Infix v24.02 support for running containers using [podman][1]
-is supported.  Because networking is a first class citizen in Infix, you
-can set up quite advanced *virtual topologies* with containers.  This
-blog post is the first in a series of posts that aims to show this.
-
-> This post assumes knowledge and familiarity with the [Infix Network
-> Operating System](https://kernelkit.github.io/).  Ensure you have
-> either a network connection or console access to your Infix system and
-> can log in to it using SSH.  Recommended reading includes the
-> [networking documentation][0].
+is supported. Because networking is a first class citizen in Infix, you
+can set up quite advanced virtual topologies with containers. This blog
+post is the first in a series that aims to show this.
+
+> This post assumes knowledge and familiarity with [Infix][4].  Ensure
+> you have either a network connection or console access to your Infix
+> system and can log in to it using SSH. Recommended reading includes
+> the [networking documentation][0].
 {: .prompt-info }
 
-
-----
+---
 
 ## Introduction
 
@@ -42,7 +40,6 @@ Notice the slight change in the prompt.  Return to the Bash shell using
 the `exit` command, or Ctrl-D, from the "admin-exec" top level of the
 CLI.
 
-
 ## Networking Basics
 
 ![Dataplane overview](/assets/img/dataplane.svg){: width="430" .right}
@@ -51,8 +48,8 @@ In Infix all network access has to be set up explicitly, so there is no
 default container networking setup (it's a security thing).  There are
 two types available to choose from:
 
- - `host`: Ethernet interface
- - `bridge`: Masquerading bridge
+- `host`: Ethernet interface
+- `bridge`: Masquerading bridge
 
 The first can be any physical port/interface which is handed over to the
 container or, more commonly, one end of a *VETH pair*.
@@ -73,7 +70,6 @@ admin@infix:/config/interface/docker0> set container-network
 admin@infix:/config/interface/docker0> leave
 ```
 
-
 ## Web Server Container
 
 ![nginx](/assets/img/nginx.png){: width="60" .left}
@@ -119,7 +115,6 @@ host's IP address.
 ![](/assets/img/nginx-welcome.png)
 _Nginx default landing page._
 
-
 > See the [end of this post](#container-content-in-device-configuration)
 > for how to store container file content in the Infix configuration!
 > Meaning custom(er) builds of Infix can bundle a built-in container's
@@ -154,10 +149,9 @@ d95ce9f7674d:/# vi /usr/share/nginx/html/
 50x.html    index.html
 d95ce9f7674d:/# vi /usr/share/nginx/html/index.html
 ... edit, save & exit from vi ...
-d95ce9f7674d:/# 
+d95ce9f7674d:/#
 ```
 
-
 ## Container Content in Device Configuration
 
 Save the best for last?  A neat feature is that container content can be
@@ -224,7 +218,6 @@ admin@infix:/config/container/web/mount/index.html/> leave
 
 Reload your browser to see the change.
 
-
 ## Fin
 
 That's the end of the first post about containers in Infix.  Remember to
@@ -240,3 +233,4 @@ Take care! 🧡
 [1]: https://podman.io
 [2]: https://www.docker.com/resources/what-container/
 [3]: https://github.com/kernelkit/infix/blob/main/doc/cli/text-editor.md
+[4]: https://kernelkit.org/

_posts/2024-10-15-basic-container.md

@@ -26,8 +26,7 @@ See the [first post][1] for a background and networking basics.
 > [networking documentation][0].
 {: .prompt-info }
 
-----
-
+---
 
 ## Introduction
 
@@ -41,7 +40,6 @@ which is usually hidden from users.
  2. In Qemu you need to activate separate `/var`, at least 256 MiB: `./qemu.sh -c`
  3. Start Infix: `./qemu.sh`
 
-
 ## Configuration
 
 The Infix configuration consists of two parts: networking setup and the
@@ -52,7 +50,6 @@ be handed over to the container.
 Notice the *DHCP client* on interface `e1`, it is required since we need
 Internet access to download the container image below.
 
-
 ```console
 admin@infix:/> configure
 admin@infix:/config/> set dhcp-client client-if e1
@@ -82,7 +79,6 @@ admin@infix:/config/container/system/> leave
 > just as easily kept going all through the new configuration.
 {: .prompt-info }
 
-
 ## The Result
 
 We should now have a running container.
@@ -104,7 +100,7 @@ lo        Link encap:Local Loopback
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000 
+          collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
 eth0      Link encap:Ethernet  HWaddr D2:A3:70:0D:50:00
@@ -113,11 +109,11 @@ eth0      Link encap:Ethernet  HWaddr D2:A3:70:0D:50:00
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:63 errors:0 dropped:9 overruns:0 frame:0
           TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
-          collisions:0 txqueuelen:1000 
+          collisions:0 txqueuelen:1000
           RX bytes:12867 (12.5 KiB)  TX bytes:3064 (2.9 KiB)
 
 root@sys101:~$ exit
-admin@infix:/> 
+admin@infix:/>
 ```
 
 ## Fin
@@ -131,7 +127,7 @@ admin@infix:/> copy running-config startup-config
 
 Take care! 🧡
 
-----
+---
 
 [0]: https://github.com/kernelkit/infix/blob/main/doc/networking.md
 [1]: /posts/containers/