Merge branch 'freebsd:main' into docs/handbook/boot

documentation/content/en/articles/building-products/_index.adoc

@@ -111,7 +111,7 @@ FreeBSD makes an excellent foundation on which to build products:
 * The project offers exceptional transparency into its workings, allowing organizations using its code to plan effectively for the future.
 * The culture of the FreeBSD project, carried over from the Computer Science
   Research Group at The University of California, Berkeley
-  crossref:building-products[McKu1999-1,"Why you should use a BSD style license for your Open Source Project"], fosters high-quality work. Some features in FreeBSD define the state of the art.
+  crossref:building-products[McKu1999-1,"Twenty Years of Berkeley Unix: From AT&T-Owned to Freely Redistributable"], fosters high-quality work. Some features in FreeBSD define the state of the art.
 
 crossref:building-products[GoldGab2005,"Innovation Happens Elsewhere: Open Source as Business Strategy"] examines the business reasons for using open-source in greater detail.
 For organizations, the benefits of using FreeBSD components in their products include a shorter time to market, lower development costs and lower development risks. 
@@ -163,7 +163,7 @@ FreeBSD's in-kernel Netgraph (man:netgraph[4]) framework allows kernel networkin
 +
 FreeBSD supports a number of filesystems, and its native UFS2 filesystem
 supports soft updates, snapshots and very large filesystem sizes (16TB per
-		filesystem) crossref:building-products[McKu1999,"Why you should use a BSD style license for your Open Source Project"].
+		filesystem) crossref:building-products[McKu1999,"Soft Updates: A Technique for Eliminating Most Synchronous Writes in the Fast Filesystem"].
 +
 FreeBSD's in-kernel GEOM (man:geom[4]) framework allows kernel storage modules to be composed in flexible ways.
 * Over {numports} ported applications, both commercial and open-source, managed via the FreeBSD ports collection.

documentation/content/en/books/handbook/kernelconfig/_index.adoc

@@ -89,6 +89,13 @@ This has a number of benefits, such as:
 * Lower memory usage. A custom kernel often uses less memory than the [.filename]#GENERIC# kernel by omitting unused features and device drivers. This is important because the kernel code remains resident in physical memory at all times, preventing that memory from being used by applications. For this reason, a custom kernel is useful on a system with a small amount of RAM.
 * Additional hardware support. A custom kernel can add support for devices which are not present in the [.filename]#GENERIC# kernel.
 
+[WARNING]
+====
+When building a custom kernel, it is important to note that non-default configurations are less thoroughly tested than the GENERIC configuration.
+While customizing the kernel can provide specific benefits it also increases the risk of encountering build or runtime issues.
+Custom kernel configurations are recommended only for advanced users who have a specific reason for making changes and are willing to engage in the debugging process if necessary.
+====
+
 Before building a custom kernel, consider the reason for doing so.
 If there is a need for specific hardware support, it may already exist as a module.
 

documentation/content/en/books/handbook/preface/_index.adoc

@@ -259,7 +259,7 @@ An _italic_ font is used for filenames, URLs, emphasized text, and the first usa
 `Monospace`::
 A `monospaced` font is used for error messages, commands, environment variables, names of ports, hostnames, user names, group names, device names, variables, and code fragments.
 
-Bold::
+*Bold*::
 A *bold* font is used for applications, commands, and keys.
 
 [[preface-conv-commands]]