From a40e468c5ad747d6ce5e1e7cc8b328c015ddf156 Mon Sep 17 00:00:00 2001
From: Jan Kuparinen <copper_fin@hotmail.com>
Date: Mar 09 2021 09:51:06 +0000
Subject: Fixed typos, changed British spelling to American


---

diff --git a/docs/modules/ROOT/assets/images/Logo_server2.png b/docs/modules/ROOT/assets/images/Logo_server2.png
new file mode 100644
index 0000000..eeaad84
Binary files /dev/null and b/docs/modules/ROOT/assets/images/Logo_server2.png differ
diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
index 0da6fe1..72824cf 100644
--- a/docs/modules/ROOT/nav.adoc
+++ b/docs/modules/ROOT/nav.adoc
@@ -1,9 +1,9 @@
 * xref:index.adoc[Welcome]
 * xref:serverAdministration.adoc[Server Administration]
-* xref:serverVirtualisation.adoc[Virtualisation]
-** xref:virtualisationInstall.adoc[Add Virtualisation Support]
-** xref:virtualisationVMInstall.adoc[VM Installation Using Cockpit]
-** xref:virtualisationVMCloud.adoc[VM Installation Using Cloud Image]
+* xref:serverVirtualization.adoc[Virtualization]
+** xref:virtualizationInstall.adoc[Add Virtualization Support]
+** xref:virtualizationVMInstall.adoc[VM Installation Using Cockpit]
+** xref:virtualizationVMCloud.adoc[VM Installation Using Cloud Image]
 * xref:serverContainers.adoc[Containers]
 ** xref:containerNspawn.adoc[Container systemd-nspawn]
 * xref:serverUseCases.adoc[Example Use Cases]
diff --git a/docs/modules/ROOT/pages/containerNspawn.adoc b/docs/modules/ROOT/pages/containerNspawn.adoc
index 3f3367f..a62cc21 100644
--- a/docs/modules/ROOT/pages/containerNspawn.adoc
+++ b/docs/modules/ROOT/pages/containerNspawn.adoc
@@ -8,7 +8,7 @@ Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedor
 ****
 [NOTE]
 ====
-Work in Progress. Comming soon
+Work in progress. Coming soon
 ==== 
 
 
diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
index 317742b..11f0769 100644
--- a/docs/modules/ROOT/pages/index.adoc
+++ b/docs/modules/ROOT/pages/index.adoc
@@ -2,7 +2,8 @@
 Peter Boy; Jan Kuparinen
 :page-authors: {author}, {author_2}
 
-image::Logo_server.png[Server] 
+image::Logo_server2.png[Server] 
+
 
 [sidebar]
 ****
@@ -33,7 +34,7 @@ Currently, we work on several projects
 
 - We are preparing Fedora Server 34
 - We are working on improving Server's documentation (you currently get a first glimpse)
-- We are exploring opportunities of aligning cloud images and server installation more closely with each other and further harmonising technical details.
+- We are exploring opportunities of aligning cloud images and server installation more closely with each other and further harmonizing technical details.
 - Technically we are revisiting defaults ... filesystem / partitioning
 
 Stay tuned. The results will soon be visible.
@@ -56,4 +57,4 @@ Stay tuned. The results will soon be visible.
 
 - System Administration Guide
 - Wiki pages
-- General ogoing work / change requests?
\ No newline at end of file
+- General ongoing work / change requests?
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverCommunicating.adoc b/docs/modules/ROOT/pages/serverCommunicating.adoc
index 9c7ee29..f73dad3 100644
--- a/docs/modules/ROOT/pages/serverCommunicating.adoc
+++ b/docs/modules/ROOT/pages/serverCommunicating.adoc
@@ -4,7 +4,7 @@ Peter Boy; Jan Kuparinen
 
 [sidebar]
 ****
-Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): All
 ****
 [NOTE]
 ====
@@ -18,7 +18,7 @@ For general troubleshooting help related to Fedora, please refer to link:https:/
 If you found a bug, report it!
 * link:https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to file a bug].
 	
-* Issues about server can be filed at link:https://pagure.io/fedora-server/issues[ticketing repository on Pagure].
+* Issues about a server can be filed at link:https://pagure.io/fedora-server/issues[ticketing repository on Pagure].
 	
 * You can chat with us at link:https://webchat.freenode.net/?channels=#fedora-server[#fedora-server on irc.freenode.net].
 
diff --git a/docs/modules/ROOT/pages/serverCommunity.adoc b/docs/modules/ROOT/pages/serverCommunity.adoc
index ccd8f6a..0747a80 100644
--- a/docs/modules/ROOT/pages/serverCommunity.adoc
+++ b/docs/modules/ROOT/pages/serverCommunity.adoc
@@ -4,7 +4,7 @@ Peter Boy; Jan Kuparinen
 
 [sidebar]
 ****
-Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
 ****
 [NOTE]
 ====
@@ -19,5 +19,5 @@ First Collection of Ideas! Please comment on server mailing list
      2  WG / Link to WG Wiki
          2.1  Members of WG incl. Tasks / area of commitment
              2.1.1  Governance Charter
-     3  Product Requirement Document
+     3  Product Requirements Document
      4  Various other suitable contents of the Fedora Server Wiki pages
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverContainers.adoc b/docs/modules/ROOT/pages/serverContainers.adoc
index 2ca1511..9fc82a2 100644
--- a/docs/modules/ROOT/pages/serverContainers.adoc
+++ b/docs/modules/ROOT/pages/serverContainers.adoc
@@ -1,4 +1,4 @@
-= Containerisation
+= Containerization
 Peter Boy; Jan Kuparinen
 :page-authors: {author}, {author_2}
 
@@ -8,7 +8,7 @@ Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedor
 ****
 [NOTE]
 ====
-Work in Progress. Comming soon
+Work in progress. Coming soon
 ==== 
 
 
diff --git a/docs/modules/ROOT/pages/serverFaq.adoc b/docs/modules/ROOT/pages/serverFaq.adoc
index 0686aba..aca6a19 100644
--- a/docs/modules/ROOT/pages/serverFaq.adoc
+++ b/docs/modules/ROOT/pages/serverFaq.adoc
@@ -4,7 +4,7 @@ Peter Boy; Jan Kuparinen
 
 [sidebar]
 ****
-Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): All
 ****
 [NOTE]
 ====
diff --git a/docs/modules/ROOT/pages/serverTroubleshooting.adoc b/docs/modules/ROOT/pages/serverTroubleshooting.adoc
index eb86bd8..c0edae2 100644
--- a/docs/modules/ROOT/pages/serverTroubleshooting.adoc
+++ b/docs/modules/ROOT/pages/serverTroubleshooting.adoc
@@ -4,7 +4,7 @@ Peter Boy; Jan Kuparinen
 
 [sidebar]
 ****
-Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+Author: Jan Kuparinen (copperi) | Creation Date: 2021-03-09 | Last update: N/A | Related Fedora Version(s): 33
 ****
 [NOTE]
 ====
@@ -12,7 +12,7 @@ First Collection of Ideas! Please comment on server mailing list
 ==== 
 	
 
-Some examples from latest discussions
+Some examples from the latest discussions
 
 1. The well known BIOSboot partition issue
 2. systemnd-oomd and httpd / jBoss/wildfly 
@@ -25,7 +25,7 @@ If you found a bug, report it!
 
 * link:https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/[How to file a bug].
 	
-* Issues about server can be filed at link:https://pagure.io/fedora-server/issues[ticketing repository on Pagure].
+* Issues about a server can be filed at link:https://pagure.io/fedora-server/issues[ticketing repository on Pagure].
 	
 * You can chat with us at link:https://webchat.freenode.net/?channels=#fedora-server[#fedora-server on irc.freenode.net].
 
diff --git a/docs/modules/ROOT/pages/serverTutorials.adoc b/docs/modules/ROOT/pages/serverTutorials.adoc
index bd08d97..ad1dd6f 100644
--- a/docs/modules/ROOT/pages/serverTutorials.adoc
+++ b/docs/modules/ROOT/pages/serverTutorials.adoc
@@ -4,7 +4,7 @@ Peter Boy; Jan Kuparinen
 
 [sidebar]
 ****
-Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
 ****
 [NOTE]
 ====
diff --git a/docs/modules/ROOT/pages/serverUseCases.adoc b/docs/modules/ROOT/pages/serverUseCases.adoc
index 61d00f2..0777080 100644
--- a/docs/modules/ROOT/pages/serverUseCases.adoc
+++ b/docs/modules/ROOT/pages/serverUseCases.adoc
@@ -4,23 +4,23 @@ Peter Boy; Jan Kuparinen
 
 [sidebar]
 ****
-Author: N/A | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
 ****
 [NOTE]
 ====
 First Collection of Ideas! Please comment on server mailing list
 ==== 
 	
-     1  Setup a Fedora Local Home Server, including
+     1  Setting up a Fedora Local Home Server, including
          1.1  Security considerations
          1.2  Considerations organizing storage
          1.3  Configuring local network
          1.4  file services Windows. Apple, Fedora Workstation
          1.5  media server 
-         1.6  (personal web server, perhaps rather a bit off the mark )
-         1.7  Again, propably providing a configurable / adaptable Ansible playbook
-     2  Setup a Home Server Mail Service
-(items according above)
+         1.6  (personal web server, perhaps rather a bit off the mark)
+         1.7  Again, probably providing a configurable / adaptable Ansible playbook
+     2  Set up a Home Server Mail Service
+        (items according to above)
      3  More to come (hopefully)
 
 
diff --git a/docs/modules/ROOT/pages/serverVirtualisation.adoc b/docs/modules/ROOT/pages/serverVirtualisation.adoc
deleted file mode 100644
index d1ee52c..0000000
--- a/docs/modules/ROOT/pages/serverVirtualisation.adoc
+++ /dev/null
@@ -1,46 +0,0 @@
-# Virtualisation
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-First Draft! Please comment on server mailing list
-==== 
-
-
-Todays Hardware is pretty much powerful enough to run not only one server but many of them.
-
-Virtualisation means that several complete and probably different operating systems run on one and the same hardware - as far as possible independently and isolated from each other.
-
-Containers are an alternative. Here, several containers use the kernel of the host system simultaneously. The mutual isolation is lower, but the performance overhead is also lower.
-
-Fedora Server uses KVM and the libvirt libraries for virtualisation. Another alternative that is often used is XEN.
-
-System software required for virtualisation is not automatically installed. It can be added as an option during installation. However, a more targeted installation is a subsequent, precisely fitting installation.
-
-After Fedora Server is enabled for virtualisation, one or more virtual machines can be installed. This can also be Fedora Server, or any other distribution.
-
-## Adding Virtualisation
-
-This step includes an installation of the libvirt software and further configuration steps. For example, external connectivity must be set up for virtual machines, e.g. through a virtual bridge. Often, an internal network is also required for protected communication between the virtual machines or with the host system.
-
-## Adding Virtual Maschines
-
-There are two common ways to install virtual machines:
-
-- Use of the distribution-specific installation programme with the help of specialised utilities
-- Installation of cloud (base) images, a variant of the operating system optimised for virtualisation.
-
-### Distributionsspezifische Installation
-
-To do this, the standard ISO file is copied to the server and then executed via a utility. The web-based administration tool Cockpit is currently recommended for Fedora Server. An alternative is Virt-Manager, a graphical utility. However, it must be installed on the local workstation (Linux only) and then works via an ssh connection. Execution on the server itself is not supported, as Fedora Server is designed to be "headless", i.e. without a graphical user interface.
-
-Experienced administrators can also initialise an installation via the command line using VNC and virt-install. However, this is comparatively time-consuming  and error-prone.
-
-### Cloud Base Images
-
-A special feature of cloud images is a configuration for a specific runtime environment and purpose with the help of a special programme, cloud-init. The necessary information is provided by the cloud system, e.g. Open Stack. These are not readily available on an autonomous server. With Fedora 33 and version 3 of the virt-install programme, the installation and use of cloud images and cloud-init has been greatly simplified. 
-
-Installation is now accomplished with a single and simple invocation of the virt-install CLI programme. Currently, no support is available through a graphical or web-based programme. 
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/serverVirtualization.adoc b/docs/modules/ROOT/pages/serverVirtualization.adoc
new file mode 100644
index 0000000..8b36ace
--- /dev/null
+++ b/docs/modules/ROOT/pages/serverVirtualization.adoc
@@ -0,0 +1,46 @@
+# Virtualization
+
+[sidebar]
+****
+Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Related Fedora Version(s): 33
+****
+[NOTE]
+====
+First Draft! Please comment on server mailing list
+==== 
+
+
+Today's Hardware is pretty much powerful enough to run not only one server but many of them.
+
+Virtualization means that several complete and probably different operating systems run on one and the same hardware - as far as possible independently and isolated from each other.
+
+Containers are an alternative. Here, several containers use the kernel of the host system simultaneously. The mutual isolation is lower, but the performance overhead is also lower.
+
+Fedora Server uses KVM and the libvirt libraries for virtualization. Another alternative that is often used is XEN.
+
+System software required for virtualization is not automatically installed. It can be added as an option during installation. However, a more targeted installation is a subsequent, precisely fitting installation.
+
+After Fedora Server is enabled for virtualization, one or more virtual machines can be installed. This can also be Fedora Server, or any other distribution.
+
+## Adding Virtualization
+
+This step includes an installation of the libvirt software and further configuration steps. For example, external connectivity must be set up for virtual machines, e.g. through a virtual bridge. Often, an internal network is also required for protected communication between the virtual machines or with the host system.
+
+## Adding Virtual Machines
+
+There are two common ways to install virtual machines:
+
+- Use of the distribution-specific installation program with the help of specialized utilities
+- Installation of cloud (base) images, a variant of the operating system optimized for virtualization.
+
+### Distribution specific installation
+
+To do this, the standard ISO file is copied to the server and then executed via a utility. The web-based administration tool Cockpit is currently recommended for Fedora Server. An alternative is Virt-Manager, a graphical utility. However, it must be installed on the local workstation (Linux only) and then works via a ssh connection. Execution on the server itself is not supported, as Fedora Server is designed to be "headless", i.e. without a graphical user interface.
+
+Experienced administrators can also initialize an installation via the command line using VNC and virt-install. However, this is comparatively time-consuming and error-prone.
+
+### Cloud Base Images
+
+A special feature of cloud images is a configuration for a specific runtime environment and purpose with the help of a special program, cloud-init. The necessary information is provided by the cloud system, e.g. Open Stack. These are not readily available on an autonomous server. With Fedora 33 and version 3 of the virt-install program, the installation and use of cloud images and cloud-init has been greatly simplified. 
+
+Installation is now accomplished with a single and simple invocation of the virt-install CLI program. Currently, no support is available through a graphical or web-based program. 
\ No newline at end of file
diff --git a/docs/modules/ROOT/pages/virtualisationInstall.adoc b/docs/modules/ROOT/pages/virtualisationInstall.adoc
deleted file mode 100644
index 5858b43..0000000
--- a/docs/modules/ROOT/pages/virtualisationInstall.adoc
+++ /dev/null
@@ -1,116 +0,0 @@
-= Adding Virtualisation Support
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Affected Fedora Version(s): 33
-****
-[NOTE]
-====
-First Draft! Please comment on server mailing list
-====
-Libvirt is the standard virtualisation method in Fedora and provides a management toolkit for KVM / QEMU. This includes a local virtual network for protected communication between the virtual guest systems with each other and with the host. 
-
-== Preparation
-
-Libvirt stores its data including the image files of the virtual hard disk(s) for the guest systems in /var/lib/libvirt. If you adhere to the default partitioning concept, the libvirt application data is stored in its own logical volume in the default volume group (fedora_fedora).
-
-Before starting the installation, a logical partition must be created. The easiest way is to use Cockpit to create a logical volume, e.g. named libvirt, format it with XFS and mount it at the position /var/lib/libvirt. Cockpit creates this directory automatically. 
-
-== Installing libvirt Virtualisation Software
-
-Installing the software is quite simple.
-[source,]
-----
-[…]# dnf install qemu-kvm libvirt virt-install cockpit-machines libguestfs-tools
-----
-
-Package libguestfs-tools provides various useful tools to maintain virtual disks. It is recommended not to install the group @virtualisation onto a Fedora Server. It includes various graphical programs and libraries that are not usable on headless servers.
-
-Next check the SELinux labels
-[source,]
-----
-[…]# ls -alZ /var/lib/libvirt
-----
-
-Usually, the installation adjusts the labels accordingly. Otherwise, an adjustment must be made manually.
-[source,]
-----
-[…]# /sbin/restorecon -R -vF /var/lib/libvirt
-----
-If everything is correct, libvirtd must be activated and started.
-[source,]
-----
-[…]# systemctl enable libvirtd  --now
-----
-
-By default, libvirt creates a bridge with an interface virbr0, the IP 192.168.122.1 and the internal name default. In addition, a separate firewall zone libvirt is set up. Check if everything is running as expected.
-[source,]
-----
-[…]# ip a
-[…]# firewall-cmd –get-active-zones
-----
-
-== Adjusting libvirt Configuration
-
-The internal network should be used for the internal, protected communication of the VMs with each other and with the host. For this purpose, it is advantageous to set up a DNS for the internal network so that the VMs can be addressed by their names.
-
-The first step is to decide about a domain name. A top-level ".local" is explicitly not recommended, nor taking one if the official top-level names. But for example, you can take the official domain name and replace the top-level domain with 'lan' or 'internal'. The example domain example.com then becomes example.lan. We use that one throughout this tutorial. The host gets the name  host.example.lan.
-
-Modify libvirt default network:
-[source,]
-----
-[…]# virsh  net-edit  default
-<network>
-  <name>default</name>
-  <uuid>aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee</uuid>
-  <bridge name='virbr0' stp='on' delay='0'/>
-  <mac address='52:54:00:xx:yy:zz'/>
-  <forward mode='nat'/>
-  <mtu size='8000'/>
-  <domain name='example.lan'/>
-  <dns forwardPlainNames='no'>
-    <forwarder domain='example.lan' />
-    <forwarder addr='213.133.98.98'/>
-    <forwarder addr='213.133.99.99'/>
-    <host ip='192.168.122.1'>
-      <hostname>host</hostname>
-      <hostname>host.example.lan</hostname>
-    </host>
-  </dns>
-  <ip address='192.168.122.1' netmask='255.255.255.0'>
-    <dhcp>
-      <range start='192.168.122.2' end='192.168.122.254'/>
-    </dhcp>
-  </ip>
-</network>
-----
-
-Activate the modified configuration 
-[source,]
-----
-[…]# virsh net-destroy default 
-[…]# virsh net-start default 
-----
-
-== Converting the Hosts DNS Configuration
-[IMPORTANT]
-====
-Wait, systemd project is currently working to fix the resolved split-DNS bug
-====
-
-== Final Test
-
-Check the functionality of the name resolution with internal and external addresses.[source,]
-----
-[…]# ping host
-[…]# ping host.example.lan
-[…]# ping host.example.com
-[…]# ping guardian.co.uk
-----
-
-
-
-
-
diff --git a/docs/modules/ROOT/pages/virtualisationVMCloud.adoc b/docs/modules/ROOT/pages/virtualisationVMCloud.adoc
deleted file mode 100644
index a211126..0000000
--- a/docs/modules/ROOT/pages/virtualisationVMCloud.adoc
+++ /dev/null
@@ -1,14 +0,0 @@
-= Virtual Machines based on Cloud Images
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-Work in Progress. Comming soon
-==== 
-
-
diff --git a/docs/modules/ROOT/pages/virtualisationVMInstall.adoc b/docs/modules/ROOT/pages/virtualisationVMInstall.adoc
deleted file mode 100644
index 574f5fd..0000000
--- a/docs/modules/ROOT/pages/virtualisationVMInstall.adoc
+++ /dev/null
@@ -1,16 +0,0 @@
-= Installing Virtual Machines using Cockpit
-Peter Boy; Jan Kuparinen
-:page-authors: {author}, {author_2}
-
-[sidebar]
-****
-Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
-****
-[NOTE]
-====
-Work in Progress. Comming soon
-==== 
-
-
-
-
diff --git a/docs/modules/ROOT/pages/virtualizationInstall.adoc b/docs/modules/ROOT/pages/virtualizationInstall.adoc
new file mode 100644
index 0000000..161377b
--- /dev/null
+++ b/docs/modules/ROOT/pages/virtualizationInstall.adoc
@@ -0,0 +1,116 @@
+= Adding Virtualization Support
+Peter Boy; Jan Kuparinen
+:page-authors: {author}, {author_2}
+
+[sidebar]
+****
+Author: Peter Boy (pboy) | Creation Date: 2021-03-10 | Last update: N/A | Affected Fedora Version(s): 33
+****
+[NOTE]
+====
+First Draft! Please comment on server mailing list
+====
+Libvirt is the standard virtualization method in Fedora and provides a management toolkit for KVM / QEMU. This includes a local virtual network for protected communication between the virtual guest systems with each other and with the host. 
+
+== Preparation
+
+Libvirt stores its data including the image files of the virtual hard disk(s) for the guest systems in /var/lib/libvirt. If you adhere to the default partitioning concept, the libvirt application data is stored in its own logical volume in the default volume group (fedora_fedora).
+
+Before starting the installation, a logical partition must be created. The easiest way is to use Cockpit to create a logical volume, e.g. named libvirt, format it with XFS and mount it at the position /var/lib/libvirt. Cockpit creates this directory automatically. 
+
+== Installing libvirt Virtualization Software
+
+Installing the software is quite simple.
+[source,]
+----
+[…]# dnf install qemu-kvm libvirt virt-install cockpit-machines libguestfs-tools
+----
+
+Package libguestfs-tools provides various useful tools to maintain virtual disks. It is recommended not to install the group @virtualization onto a Fedora Server. It includes various graphical programs and libraries that are not usable on headless servers.
+
+Next check the SELinux labels
+[source,]
+----
+[…]# ls -alZ /var/lib/libvirt
+----
+
+Usually, the installation adjusts the labels accordingly. Otherwise, an adjustment must be made manually.
+[source,]
+----
+[…]# /sbin/restorecon -R -vF /var/lib/libvirt
+----
+If everything is correct, libvirtd must be activated and started.
+[source,]
+----
+[…]# systemctl enable libvirtd  --now
+----
+
+By default, libvirt creates a bridge with an interface virbr0, the IP 192.168.122.1 and the internal name default. In addition, a separate firewall zone libvirt is set up. Check if everything is running as expected.
+[source,]
+----
+[…]# ip a
+[…]# firewall-cmd –get-active-zones
+----
+
+== Adjusting libvirt Configuration
+
+The internal network should be used for the internal, protected communication of the VMs with each other and with the host. For this purpose, it is advantageous to set up a DNS for the internal network so that the VMs can be addressed by their names.
+
+The first step is to decide about a domain name. A top-level ".local" is explicitly not recommended, nor taking one if the official top-level names. But for example, you can take the official domain name and replace the top-level domain with 'lan' or 'internal'. The example domain example.com then becomes example.lan. We use that one throughout this tutorial. The host gets the name  host.example.lan.
+
+Modify libvirt default network
+[source,]
+----
+[…]# virsh  net-edit  default
+<network>
+  <name>default</name>
+  <uuid>aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee</uuid>
+  <bridge name='virbr0' stp='on' delay='0'/>
+  <mac address='52:54:00:xx:yy:zz'/>
+  <forward mode='nat'/>
+  <mtu size='8000'/>
+  <domain name='example.lan'/>
+  <dns forwardPlainNames='no'>
+    <forwarder domain='example.lan' />
+    <forwarder addr='213.133.98.98'/>
+    <forwarder addr='213.133.99.99'/>
+    <host ip='192.168.122.1'>
+      <hostname>host</hostname>
+      <hostname>host.example.lan</hostname>
+    </host>
+  </dns>
+  <ip address='192.168.122.1' netmask='255.255.255.0'>
+    <dhcp>
+      <range start='192.168.122.2' end='192.168.122.254'/>
+    </dhcp>
+  </ip>
+</network>
+----
+
+Activate the modified configuration 
+[source,]
+----
+[…]# virsh net-destroy default 
+[…]# virsh net-start default 
+----
+
+== Converting the Hosts DNS Configuration
+[IMPORTANT]
+====
+Wait, systemd project is currently working to fix the resolved split-DNS bug
+====
+
+== Final Test
+
+Check the functionality of the name resolution with internal and external addresses.[source,]
+----
+[…]# ping host
+[…]# ping host.example.lan
+[…]# ping host.example.com
+[…]# ping guardian.co.uk
+----
+
+
+
+
+
diff --git a/docs/modules/ROOT/pages/virtualizationVMCloud.adoc b/docs/modules/ROOT/pages/virtualizationVMCloud.adoc
new file mode 100644
index 0000000..63c7cec
--- /dev/null
+++ b/docs/modules/ROOT/pages/virtualizationVMCloud.adoc
@@ -0,0 +1,14 @@
+= Virtual Machines based on Cloud Images
+Peter Boy; Jan Kuparinen
+:page-authors: {author}, {author_2}
+
+[sidebar]
+****
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+****
+[NOTE]
+====
+Work in progress. Coming soon
+==== 
+
+
diff --git a/docs/modules/ROOT/pages/virtualizationVMInstall.adoc b/docs/modules/ROOT/pages/virtualizationVMInstall.adoc
new file mode 100644
index 0000000..a8b62c0
--- /dev/null
+++ b/docs/modules/ROOT/pages/virtualizationVMInstall.adoc
@@ -0,0 +1,16 @@
+= Installing Virtual Machines using Cockpit
+Peter Boy; Jan Kuparinen
+:page-authors: {author}, {author_2}
+
+[sidebar]
+****
+Author: Peter Boy (pboy) | Creation Date: N/A | Last update: N/A | Related Fedora Version(s): 33
+****
+[NOTE]
+====
+Work in progress. Coming soon
+==== 
+
+
+
+

