git: de1af21205 - main - handbook/containers: Avoid single sentence paragraphs

The branch main has been updated by bcr:

URL: https://cgit.FreeBSD.org/doc/commit/?id=de1af21205f6892186163c357829d0036590d889

commit de1af21205f6892186163c357829d0036590d889
Author:     Benedict Reuschling <bcr@FreeBSD.org>
AuthorDate: 2026-06-20 14:32:31 +0000
Commit:     Benedict Reuschling <bcr@FreeBSD.org>
CommitDate: 2026-06-20 14:32:31 +0000

    handbook/containers: Avoid single sentence paragraphs
    
    Combine single sentence paragraphs together to form actual paragraphs.
    No content changes.
    
    Event:  BSDCan 2026
---
 .../content/en/books/handbook/containers/_index.adoc       | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/documentation/content/en/books/handbook/containers/_index.adoc b/documentation/content/en/books/handbook/containers/_index.adoc
index d23ce96aed..62c4d516a6 100644
--- a/documentation/content/en/books/handbook/containers/_index.adoc
+++ b/documentation/content/en/books/handbook/containers/_index.adoc
@@ -52,11 +52,8 @@ endif::[]
 == Synopsis
 
 The https://opencontainers.org/[Open Container Initiative], commonly referred to as `+OCI+`, provides a vendor and OS-agnostic way to describe, distribute, and run containers.
-
 The OCI specifications provide these in a way that can be used on many different operating systems, including FreeBSD.
-
 The underlying virtualization technology is still FreeBSD jails, with the same feature set, but OCI tooling enables additional ways of working, and constructing, container-based workloads.
-
 https://www.freebsd.org/releases/14.3R/announce/[14.3-RELEASE] and upwards, including https://download.freebsd.org/snapshots/OCI-IMAGES/[snapshots], now include OCI-compatible images, and the https://podman.io/[Podman] toolkit on FreeBSD is ready to use them, on both amd64 and arm64 architectures.
 
 For FreeBSD users familiar with jails, there is a loose analogy:
@@ -66,7 +63,6 @@ For FreeBSD users familiar with jails, there is a loose analogy:
 * use the `+jail ..+` command to run a container, given a filesystem path, with the `+podman+` suite of tools.
 
 By importing this container stack, FreeBSD users both benefit from common tooling, but also enjoy wide support across public and private container registries, and container-specific tooling and services.
-
 In the https://download.freebsd.org/releases/OCI-IMAGES/{rel-latest}-RELEASE/aarch64/Latest/[aarch64] and https://download.freebsd.org/releases/OCI-IMAGES/{rel-latest}-RELEASE/amd64/Latest/[amd64] download directories, you'll see official OCI-format images.
 The naming may be a little confusing at first, but should make sense once you start using them.
 
@@ -92,9 +88,7 @@ FreeBSD-{rel-latest}-RELEASE-amd64-container-image-toolchain.txz
 === Introduction
 
 FreeBSD's official container images are built from base system packages, themselves built during the FreeBSD release process, and published to public registries.
-
 This guide explains how images are named and tagged, helping you choose the right image for your needs, and ensuring you understand the implications of each choice, as new images are published, and in some cases, mutable tags are amended.
-
 This naming convention aligns with the new base system package naming scheme, giving clear provenance between container images and the corresponding FreeBSD releases.
 
 [[containers-image-types]]
@@ -114,16 +108,13 @@ The static image is intended as a base image, for a workload which is entirely s
 
 Note that it has, by design, a lean footprint, to make a security compromise of the container less useful to the attacker.
 There's no UNIX shell, no command-line tools, no dynamic libraries, nor package manager.
-
 It is the smallest image provided by the FreeBSD project.
 
 [[containers-freebsd-dynamic]]
 ==== `+freebsd-dynamic+`
 
 The dynamic image uses the static image as a parent layer, and supports using shared libraries, including `+libc+`.
-
 Most FreeBSD software should run without issue with this image, with minor changes.
-
 It doesn't have a shell, rc system, nor a package manager.
 These limitations are additional security, making it awkward for attackers in a compromised container to move laterally, or make use of tools that were never installed.
 
@@ -131,10 +122,8 @@ These limitations are additional security, making it awkward for attackers in a
 ==== `+freebsd-runtime+`
 
 Again, runtime builds on the preceding dynamic layer, and finally adds the minimum that a user would expect - a UNIX shell, rc system, and the package manager.
-
 It is the ideal base image for porting existing applications with a minimum of changes.
 Users will need to include additional FreeBSD base system libraries, as well as additional packages from the Ports tree.
-
 This is the closest to a typical FreeBSD system, including the man:pkg[8] tool, allowing users to install, or do, almost anything, similar to a non-containerised system.
 
 [[containers-freebsd-notoolchain]]
@@ -147,7 +136,6 @@ This base image contains almost all tools one would expect on a typical FreeBSD
 
 The Toolchain base image is the sum of all preceding images, including a full compiler and toolchain.
 It is generally possible to compile almost any software for FreeBSD in the same way as a normal non-jailed FreeBSD system.
-
 All images follow a consistent naming pattern, derived from the FreeBSD release they are based upon.
 
 [[containers-tag-structure]]
@@ -157,10 +145,8 @@ All images follow a consistent naming pattern, derived from the FreeBSD release
 ==== Immutable Tags
 
 Immutable tags never change and are ideal for production systems where you need stability and predictability.
-
 These are the most common tags used by the release process.
 They will not change, even after FreeBSD security patches, or errata notices.
-
 They are ideal for base images for software deployments where a high degree of reproducibility is expected, even as a trade-off against more pro-active security patching.
 
 * `+major.minor+` (e.g., `+14.4+`): Points to a specific FreeBSD RELEASE version