[Bug 263324] Move/copy reference to virtualization in the installation chapter somewhere more obvious than preinstall step 2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263324

--- Comment #3 from PauAmma <pauamma@gundo.com> ---
Comment on attachment 233331
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=233331
diff to add virtualization to synposis

>diff --git a/documentation/content/en/books/handbook/bsdinstall/_index.adoc b/documentation/content/en/books/handbook/bsdinstall/_index.adoc
>index 625462331d..f06cb706ca 100644
>--- a/documentation/content/en/books/handbook/bsdinstall/_index.adoc
>+++ b/documentation/content/en/books/handbook/bsdinstall/_index.adoc
>@@ -132,6 +132,7 @@ A 32-bit kernel can only use the first 2 GB of RAM.
> == Pre-Installation Tasks
> 
> Once it has been determined that the system meets the minimum hardware requirements for installing FreeBSD, the installation file should be downloaded and the installation media prepared.
>+An alternative is to use virtualization (crossref:virtualization[virtualization,Virtualization]) which allows multiple operating systems to run at the same time without modifying any disk partitions.

I'd merge the repeated "virtualization" into one. Something like: 

An alternative is to use
crossref:virtualization[virtualization,virtualization], which allows...

> Before doing this, check that the system is ready for an installation by verifying the items in this checklist:
> 
> [.procedure]
>@@ -169,7 +170,7 @@ Since the possibility of selecting the wrong partition exists, always backup any
> ====
> +
> Disk partitions containing different operating systems make it possible to install multiple operating systems on one computer.
>-An alternative is to use virtualization (crossref:virtualization[virtualization,Virtualization]) which allows multiple operating systems to run at the same time without modifying any disk partitions.
>+Virtualization (crossref:virtualization[virtualization,Virtualization]) allows multiple operating systems to run at the same time without modifying any disk partitions.

Same here, and I think I'd keep "An alternative...". Or maybe just keep the
added earlier mention and remove this one, not sure.

> . *Collect Network Information*
> +
> Some FreeBSD installation methods require a network connection in order to download the installation files.
>diff --git a/documentation/content/en/books/handbook/zfs/_index.adoc b/documentation/content/en/books/handbook/zfs/_index.adoc
>index 3f9a2a457d..0242b01a6c 100644
>--- a/documentation/content/en/books/handbook/zfs/_index.adoc
>+++ b/documentation/content/en/books/handbook/zfs/_index.adoc
>@@ -488,7 +488,7 @@ The <<zfs-zfs,`zfs`>> utility allows creating, destroying, and managing datasets
> [[zfs-zpool-create]]
> === Creating and Destroying Storage Pools
> 
>-Creating a ZFS storage pool (_zpool_) requires permanent decisions, as the pool structure cannot change after creation.
>+Creating a ZFS storage pool requires permanent decisions, as the pool structure cannot change after creation.
> The most important decision is which types of vdevs to group the physical disks into. 
> See the list of <<zfs-term-vdev,vdev types>> for details about the possible options.
> After creating the pool, most vdev types do not allow adding disks to the vdev.
>@@ -580,7 +580,7 @@ This can cause undefined behavior in applications which had open files on those
> [[zfs-zpool-attach]]
> === Adding and Removing Devices
> 
>-Two ways exist for adding disks to a zpool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
>+Two ways exist for adding disks to a pool: attaching a disk to an existing vdev with `zpool attach`, or adding vdevs to the pool with `zpool add`.
> Some <<zfs-term-vdev,vdev types>> allow adding disks to the vdev after creation.
> 
> A pool created with a single disk lacks redundancy.

-- 
You are receiving this mail because:
You are the assignee for the bug.