README: Markdown lint fixes

Signed-off-by: Micah Abbott <miabbott@redhat.com>

README.md

@@ -15,7 +15,7 @@ The current default user experience is to build *layered* images on top of the o
 binary base images produced and tested by this project. See the documentation[5] for more info.
 
 You can build custom base images by forking this repository; however,
-https://gitlab.com/fedora/bootc/tracker/-/issues/32 tracks a more supportable
+<https://gitlab.com/fedora/bootc/tracker/-/issues/32> tracks a more supportable
 mechanism that is not simply forking. For more information see[6].
 
 ## Build process
@@ -25,7 +25,7 @@ note the build process uses a special podman-ecosystem specific mechanism
 to create fully custom images while inside a `Containerfile`.
 You need to enable some privileges as nested containerization is required.
 
-```
+```bash
 podman build --security-opt=label=disable --cap-add=all \
   --device /dev/fuse -t localhost/fedora-bootc .
 ```
@@ -38,7 +38,7 @@ By default, the base images are built for Fedora rawhide. To build against a
 different Fedora version, you can override the `FROM` image used to obtain the
 Fedora repos and dnf variables. E.g.:
 
-```
+```bash
 podman build --from quay.io/fedora/fedora:41 ...
 ```
 
@@ -59,9 +59,9 @@ to support smaller custom images. For more on this, see
 [this tracker issue](https://gitlab.com/fedora/bootc/tracker/-/issues/32).
 
 - **standard**: This image is the default, what is published as
-  https://quay.io/repository/fedora/fedora-bootc
+  <https://quay.io/repository/fedora/fedora-bootc>
 - **minimal**: This content set is more of a convenient centralization point for CI
-  and curation around a package set that is intended as a starting point fror
+  and curation around a package set that is intended as a starting point for
   a container base image.
 - **minimal-plus**: This content set is intended to be the shared base used by all image-based
   Fedora variants (IoT, Atomic Desktops, and CoreOS).