git: e5597fb515 - main - Whitespace fixes at the end of some lines

The branch main has been updated by bcr:

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

commit e5597fb515148898aeb0b0419a2419af2a1be76c
Author:     Benedict Reuschling <bcr@FreeBSD.org>
AuthorDate: 2023-12-29 12:16:26 +0000
Commit:     Benedict Reuschling <bcr@FreeBSD.org>
CommitDate: 2023-12-29 12:16:26 +0000

    Whitespace fixes at the end of some lines
---
 documentation/content/en/articles/releng/_index.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/documentation/content/en/articles/releng/_index.adoc b/documentation/content/en/articles/releng/_index.adoc
index a6f48da97a..9a48f7ee22 100644
--- a/documentation/content/en/articles/releng/_index.adoc
+++ b/documentation/content/en/articles/releng/_index.adoc
@@ -64,7 +64,7 @@ The development of FreeBSD is a very open process.
 FreeBSD is comprised of contributions from thousands of people around the world.
 The FreeBSD Project provides Subversion footnote:[Subversion, http://subversion.apache.org] access to the general public so that others can have access to log messages, diffs (patches) between development branches, and other productivity enhancements that formal source code management provides.
 This has been a huge help in attracting more talented developers to FreeBSD.
-However, I think everyone would agree that chaos would soon manifest if write access to the main repository was opened up to everyone on the Internet. 
+However, I think everyone would agree that chaos would soon manifest if write access to the main repository was opened up to everyone on the Internet.
 Therefore only a "select" group of nearly 300 people are given write access to the Subversion repository.
 These extref:{contributors}[FreeBSD committers, staff-committers]footnote:[extref:{contributors}[FreeBSD committers, staff-committers]] are usually the people who do the bulk of FreeBSD development.
 An elected link:https://www.FreeBSD.org/administration/#t-core[Core Team]footnote:[link:https://www.FreeBSD.org/administration/#t-core[FreeBSD Core Team]] of developers provide some level of direction over the project.
@@ -323,7 +323,7 @@ The `{portmgr}` is responsible for maintaining a consistent ports tree that can
 === Release ISOs
 
 Starting with FreeBSD 4.4, the FreeBSD Project decided to release all four ISO images that were previously sold on the _BSDi/Wind River Systems/FreeBSD Mall_ "official" CDROM distributions.
-Each of the four discs must contain a [.filename]#README.TXT# file that explains the contents of the disc, a [.filename]#CDROM.INF# file that provides meta-data for the disc so that man:bsdinstall[8] can validate and use the contents, and a [.filename]#filename.txt# file that provides a manifest for the disc. 
+Each of the four discs must contain a [.filename]#README.TXT# file that explains the contents of the disc, a [.filename]#CDROM.INF# file that provides meta-data for the disc so that man:bsdinstall[8] can validate and use the contents, and a [.filename]#filename.txt# file that provides a manifest for the disc.
 This _manifest_ can be created with a simple command:
 
 [source,shell]
@@ -355,7 +355,7 @@ This disc should be bootable and should also contain a compressed copy of the CV
 
 Sysinstall supports multiple volume package installations.
 This requires that each disc have an [.filename]#INDEX# file containing all of the packages on all volumes of a set, along with an extra field that indicates which volume that particular package is on.
-Each volume in the set must also have the `CD_VOLUME` variable set in the [.filename]#cdrom.inf# file so that bsdinstall can tell which volume is which. 
+Each volume in the set must also have the `CD_VOLUME` variable set in the [.filename]#cdrom.inf# file so that bsdinstall can tell which volume is which.
 When a user attempts to install a package that is not on the current disc, bsdinstall will prompt the user to insert the appropriate one.
 
 [[distribution]]
@@ -403,7 +403,7 @@ Coming soon: Tips for sending FreeBSD ISOs to a replicator and quality assurance
 [[extensibility]]
 == Extensibility
 
-Although FreeBSD forms a complete operating system, there is nothing that forces you to use the system exactly as we have packaged it up for distribution. 
+Although FreeBSD forms a complete operating system, there is nothing that forces you to use the system exactly as we have packaged it up for distribution.
 We have tried to design the system to be as extensible as possible so that it can serve as a platform that other commercial products can be built on top of.
 The only "rule" we have about this is that if you are going to distribute FreeBSD with non-trivial changes, we encourage you to document your enhancements!
 The FreeBSD community can only help support users of the software we provide.
@@ -424,7 +424,7 @@ The security officer was very involved in the last week of the process as severa
 A total of over _500_ emails were sent to the `{re}` in little over a month.
 
 Our user community has made it very clear that the security and stability of a FreeBSD release should not be sacrificed for any self-imposed deadlines or target release dates.
-The FreeBSD Project has grown tremendously over its lifetime and the need for standardized release engineering procedures has never been more apparent. 
+The FreeBSD Project has grown tremendously over its lifetime and the need for standardized release engineering procedures has never been more apparent.
 This will become even more important as FreeBSD is ported to new platforms.
 
 [[future]]