Adding topics from the BNE Fedora Docs Day, missing images and fixing several asciibinder warnings

_topic_map.yml

@@ -63,6 +63,8 @@ Topics:
         File: build-custom-kernel
   - Name: Managing keyboard shortcuts for running an application in GNOME
     File: managing-keyboard-shortcuts-for-running-app-in-gnome
+  - Name: Setting a key shortcut to run an application in GNOME
+    File: proc_setting-key-shortcut
   - Name: Disabling the GNOME automatic screen locking
     File: disabling-automatic-screenlock
   - Name: Viewing logs in Fedora
@@ -73,6 +75,8 @@ Topics:
     File: installing-and-running-vlc
   - Name: Configuring networking with NetworkManager CLI (nmcli)
     File: configuring-ip-networking-with-nmcli
+  - Name: Creating disk partitions
+    File: creating-a-disk-partition-in-linux
   - Name: NVIDIA Optimus Bumblebee
     File: bumblebee
   - Name: Raspberry Pi
@@ -121,8 +125,8 @@ Topics:
     File: configuring-x-window-system-using-the-xorg-conf-file
   - Name: Configuring X.org as the default GNOME session
     File: configuring-xorg-as-default-gnome-session
-  - Name: Identifying Wayland problems
-    File: debug-wayland-problems
+#  - Name: (FIX ME!) Identifying Wayland problems
+#    File: debug-wayland-problems
 # - Name: (CHECK) GRUB 2
 #   File: grub2
 # - Name: (FIX ME!) How to debug Dracut problems

en-US/create-gpg-keys.adoc

@@ -55,7 +55,7 @@ There are several options available on the market, for example the https://www.y
 Look for a token which advertises OpenPGP support.
 See https://blog.josefsson.org/2014/06/23/offline-gnupg-master-key-and-subkeys-on-yubikey-neo-smartcard/[this blog entry] for how to create a key with offline backups, and use the token for online access.
 
-include::en-US/modules/proc_revoking-gpg-keys.adoc[]
+include::en-US/modules/proc_revoking-gpg-keys.adoc[leveloffset=+1]
 
 = Additional resources
 

en-US/creating-a-disk-partition-in-linux.adoc

@@ -0,0 +1,13 @@
+:experimental:
+
+:parent-context: {context}
+
+[id='disk-partition-in-linux-{context}']
+= Creating a disk partition in Linux
+:context: using-parted
+
+include::en-US/modules/con_disk-partition-linux.adoc[leveloffset=+1]
+include::en-US/modules/proc_creating-a-disk-partition-in-linux.adoc[leveloffset=+1]
+include::en-US/modules/ref_help-mkpart.adoc[leveloffset=+1]
+
+:context: {parent-context}

en-US/firewalld.adoc

@@ -1,166 +1,29 @@
-[[ch-FirewallD]]
-= FirewallD
+:experimental:
+:imagesdir: ./images
 
-[[sect-what-is-firewalld]]
-== What is FirewallD?
+[[using-firewalld]]
+= Using firewalld
 
-FirewallD allows users to control which network ports they want opened, or closed, to keep their system secure from unauthorized access.
-FirewallD is integrated with SystemD and NetworkManager, and supports IPv4, IPv6 and ethernet bridges.
-It also supports an interface for services and applications to add firewall rules directly.
-These settings can be controlled from the command-line, or with the `firewall-config` graphic-user-interface.
+:leveloffset: +1
 
-[[sect-do-i-have-firewalld-on-my-system]]
-== Do I have FirewallD on my system?
-FirewallD is the default firewall service for current releases of Fedora and is enabled by default.
-To check if your system has FirewallD enabled, at the command-line, type:
+include::en-US/modules/con_firewalld.adoc[]
 
-[source,bash]
+include::en-US/modules/proc_checking_firewalld.adoc[]
 
-----
+include::en-US/modules/proc_installing_firewalld.adoc[]
 
-sudo firewall-cmd --state
+include::en-US/modules/proc_starting_firewalld.adoc[]
 
-----
+include::en-US/modules/proc_stopping_firewalld.adoc[]
 
-This command will show if it is `running` or `not running`
+include::en-US/modules/con_runtime_and_permanent_firewalld.adoc[]
 
-If FirewallD is `not running`, type:
+include::en-US/modules/proc_changing_runtime_firewalld.adoc[]
 
-[source,bash]
+include::en-US/modules/con_controlling_ports_firewalld.adoc[]
 
-----
+include::en-US/modules/proc_opening_ports_firewalld.adoc[]
 
-sudo systemctl enable --now firewalld
+include::en-US/modules/proc_closing_ports_firewalld.adoc[]
 
-----
-
-This will enable the FirewallD service when booting the system, and immediately start the service.
-
-If these commands do not work, FirewallD may not be installed. To install it, type:
-
-[source,bash]
-
-----
-
-sudo dnf install firewalld
-
-----
-
-To install the FirewallD graphical-user-interface application and open it from the command-line, type:
-
-[source,bash]
-
-----
-
-sudo dnf install firewall-config
-
-sudo firewall-config
-
-----
-
-[[sect-opening-and-closing-ports-with-firewalld]]
-== Opening and closing ports with FirewallD
-
-Opening ports with FirewallD can be executed from the command-line without the need to edit configuration files.
-Ports can be opened using either the service name, or the port number.
-For example, to allow access to the SSH service, type:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --add-service ssh
-
-----
-
-If allowing access by the port number, it needs to be followed by the protocol whether it is TCP or UDP.
-To open SSH by its port, type:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --add-port=22/tcp
-
-----
-
-This will open the SSH port in runtime mode.
-Runtime mode means it will run the change temporarily and will revert back to its original state after reloading the FirewallD service, or after a system reboot.
-To keep the SSH port opened after a FirewallD service restart, or system reboot, include the `--permanent` option, type:
-
-[source,bash]
-----
-
-sudo firewall-cmd --permanent --add-service ssh
-
-----
-
-or by port number:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --permanent --add-port=22/tcp
-
-----
-
-To save the changes:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --reload
-
-----
-
-To block access to the SSH service:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --remove-service ssh
-
-----
-
-To block access by port number:
-
-----
-
-sudo firewall-cmd --remove-port=22/tcp
-
-----
-
-Again, add the `--permanent` option to make it persistent, and don't forget to do `firewall-cmd --reload` to save the changes.
-
-[[sect-how-can-i-see-the-services-recognized-by-firewalld]]
-== How can I see the services recognized by FirewallD?
-
-To see a list of all the services recognized by FirewallD, type:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --get-services
-
-----
-
-To view a list of services "turned-on" in FirewallD, type:
-
-[source,bash]
-
-----
-
-sudo firewall-cmd --list-services
-
-----
-
-[[sect-additional-resources]]
-== Additional Resources
-
-For more information about configuring FirewallD, such as how to list and change zones, port forwarding, and other system administrative tasks, refer to the FirewallD documentation at link:++http://www.firewalld.org/++[firewalld.org], the link:++https://fedoraproject.org/wiki/Firewalld++[Fedora Wiki: FirewallD].
-
-You can also find local documentation by using `firewall-cmd --help` or the man pages: `man firewalld`
+:leveloffset: 0

en-US/managing-keyboard-shortcuts-for-running-app-in-gnome.adoc

@@ -4,7 +4,6 @@
 = Managing keyboard shortcuts for running an application in GNOME
 
 :md: en-US/modules
-:imagesdir: ./images
 
 :leveloffset: +1
 

en-US/modules/con_controlling_ports_firewalld.adoc

@@ -0,0 +1,13 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+
+[id='controlling-ports-firewalld-fedora']
+
+= Controlling ports using firewalld
+
+== What are ports?
+Ports are logical devices that enable an operating system to receive and distinguish network traffic and forward it accordingly to system services. These are usually represented by a daemon that listens on the port, that is it waits for any traffic coming to this port.
+
+Normally, system services listen on standard ports that are reserved for them. The httpd daemon, for example, listens on port 80. However, system administrators may configure daemons to listen on different ports to enhance security.

en-US/modules/con_disk-partition-linux.adoc

@@ -0,0 +1,9 @@
+// Module included in the following assemblies:
+//
+// creating-a-disk-partition-in-linux-using-the-parted-command.adoc
+:experimental:
+
+[#{context}-disk-partition-linux]
+= Disk Partitioning in Linux
+
+Creating and deleting partitions in Linux is a regular practice because storage devices (such as hard drives and USB drives) must be structured in some way before they can be used. In most cases, large storage devices are divided into separate sections called partitions. Partitioning also allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems.

en-US/modules/con_firewalld.adoc

@@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+[id='concept-firewalld-fedora']
+= Using firewalld
+
+== What is firewalld?
+
+A _firewall_ is a way to protect machines from any unwanted traffic from outside. It enables users to control incoming network traffic on host machines by defining a set of _firewall rules_. These rules are used to sort the incoming traffic and either block it or allow through.
+
+`firewalld` is a firewall service daemon that provides a dynamic customizable host-based firewall with a `D-Bus` interface. Being dynamic, it enables creating, changing, and deleting the rules without the necessity to restart the firewall daemon each time the rules are changed.
+
+`firewalld` uses the concepts of _zones_ and _services_, that simplify the traffic management.
+
+`_Zones_` are predefined sets of rules. Network interfaces and sources can be assigned to a zone. The traffic allowed depends on the network your computer is connected to and the security level this network is assigned. Firewall services are predefined rules that cover all necessary settings to allow incoming traffic for a specific service and they apply within a zone.
+
+`_Services_` use one or more ports or addresses for network communication. Firewalls filter communication based on ports. To allow network traffic for a service, its ports must be open. `firewalld` blocks all traffic on ports that are not explicitly set as open. Some zones, such as trusted, allow all traffic by default.
+
+.Additional resources
+
+For more information about using firewalld and configuring zones and services, see link:https://firewalld.org/documentation/[firewalld documentation] or link:https://fedoraproject.org/wiki/Firewalld[Fedora wiki:firewalld]

en-US/modules/con_runtime_and_permanent_firewalld.adoc

@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+[id='concept-runtime-and-permanent-firewalld-fedora']
+
+= Runtime and permanent settings
+
+Any changes made while firewalld is running will be lost when firewalld is restarted. When firewalld is restarted, the settings revert to their permanent values.
+
+These changes are said to be made in _runtime mode_.
+
+To make the changes persistent across reboots, apply them again using the `--permanent` option. Alternatively, to make changes persistent while firewalld is running, use the `--runtime-to-permanent _firewall-cmd_` option.
+
+If you make changes while firewalld is running using only the `--permanent` option, they do not become effective until firewalld is restarted. However, restarting firewalld briefly stops the networking traffic, causing disruption to your system.

en-US/modules/proc_adding-new-certificates.adoc

@@ -1,8 +1,6 @@
 [id='proc_adding-new-certificates']
 = Adding New Certificates
 
-.Procedure
-
 To add a certificate in the simple PEM or DER file formats to the list of CAs trusted on the system, copy the certificate file to the `/usr/share/pki/ca-trust-source/anchors/` or `/etc/pki/ca-trust/source/anchors/` directory, for example:
 
 [subs="+quotes,macros"]

en-US/modules/proc_adding-repositories.adoc

@@ -3,9 +3,6 @@
 
 This section describes how to add software repositories with the `dnf config-manger` command.
 
-[discrete]
-== Procedure
-
 Use the following commands as the `root` user or under the `sudo` utility.
 
 . Define a new repository by adding a new file with the `.repo` suffix to the [filename]`/etc/yum.repos.d/` directory. For details about various options to use in the `.repo` file, see the link:https://docs-old.fedoraproject.org/en-US/Fedora/26/html/System_Administrators_Guide/sec-Setting_repository_Options.html[Setting [repository\] Options] section in the System Administrator's Guide

en-US/modules/proc_changing_runtime_firewalld.adoc

@@ -0,0 +1,50 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+[id='changing_runtime_firewalld_fedora']
+
+= Changing settings in runtime and permanent configuration using CLI
+
+Using the CLI, you can only modify either runtime or permanent mode. To modify the firewall settings in permanent mode, use the `--permanent` option with the `firewall-cmd` command.
+
+----
+$ sudo firewall-cmd --permanent <other options>
+----
+
+Without this option, the command modifies runtime mode.
+To change settings in both modes, you can use two methods:
+
+* Change runtime settings and then make them permanent as follows:
+
+. Change the runtime settings:
++
+`firewall-cmd <other options>`
++
+. Use `--runtime-to-permanent` to make the changes permanent.
++
+`firewall-cmd --runtime-to-permanent`
+
+* Set permanent settings and reload the settings into runtime mode:
+
+. Make the changes in permanent mode:
++
+`firewall-cmd --permanent <other options>`
++
+. Reload the settings:
++
+`firewall-cmd --reload`
+
+The first method allows you to test the settings before you apply them to permanent mode.
+
+[NOTE]
+====
+It is possible that an incorrect setting will result in a user locking themselves out of a machine. To prevent this, use the `--timeout` option. Using this option means that after a specified amount of time, any change reverts to its previous state.
+You can not use the `--permanent` option with the `--timeout` option.
+
+For example, to add the SSH service for 15 minutes use this command:
+----
+$ sudo firewall-cmd --add-service=ssh --timeout 15m
+----
+The SSH service will be available until access is removed after 15 minutes.
+====

en-US/modules/proc_checking_firewalld.adoc

@@ -0,0 +1,130 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+// Base the file name and the ID on the module title. For example:
+// * file name: doing-procedure-a.adoc
+// * ID: [id='doing-procedure-a']
+// * Title: = Doing procedure A
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id=checking-firewalld-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Checking the firewalld status
+
+== Viewing the current status of `firewalld`
+
+The firewall service, `firewalld`, is installed on the system by default. Use the `firewalld` CLI interface to check that the service is running.
+
+To see the status of the service:
+
+----
+$ sudo firewall-cmd --state
+----
+
+For more information about the service status, use the [command]`systemctl status` sub-command:
+
+----
+$ sudo systemctl status firewalld
+firewalld.service - firewalld - dynamic firewall daemon
+   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor pr
+   Active: active (running) since Mon 2017-12-18 16:05:15 CET; 50min ago
+     Docs: man:firewalld(1)
+ Main PID: 705 (firewalld)
+    Tasks: 2 (limit: 4915)
+   CGroup: /system.slice/firewalld.service
+           └─705 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork --nopid
+----
+
+Furthermore, it is important to know how `firewalld` is set up and which rules are in force before you try to edit the settings. To display the firewall settings, see <<sec-Viewing_Current_firewalld_Settings>>
+
+[[sec-Viewing_Current_firewalld_Settings]]
+== Viewing current firewalld settings
+
+[[sec-Viewing_Allowed_Services_Using_GUI]]
+=== Viewing allowed services using GUI
+
+To view the list of services using the graphical [application]*firewall-config* tool, press the kbd:[Super] key to enter the Activities Overview, type [command]`firewall`, and press kbd:[Enter]. The [application]*firewall-config* tool appears. You can now view the list of services under the `Services` tab.
+
+Alternatively, to start the graphical firewall configuration tool using the command-line, enter the following command:
+
+[subs="quotes, macros"]
+----
+$ [command]`firewall-config`
+----
+
+The `Firewall Configuration` window opens. Note that this command can be run as a normal user, but you are prompted for an administrator password occasionally.
+////
+[[exam-firewall_config_services]]
+.The Services tab in firewall-config
+
+image::images/firewall-config-services.png[A screenshot of the firewall configuration tool - the Services tab]
+////
+[[sec-Viewing_firewalld_Settings_Using_CLI]]
+=== Viewing firewalld settings using CLI
+
+With the CLI client, it is possible to get different views of the current firewall settings. The [option]`--list-all` option shows a complete overview of the `firewalld` settings.
+
+`firewalld` uses zones to manage the traffic. If a zone is not specified by the [option]`--zone` option, the command is effective in the default zone assigned to the active network interface and connection.
+
+To list all the relevant information for the default zone:
+
+----
+$ firewall-cmd --list-all
+public
+  target: default
+  icmp-block-inversion: no
+  interfaces:
+  sources:
+  services: ssh dhcpv6-client
+  ports:
+  protocols:
+  masquerade: no
+  forward-ports:
+  source-ports:
+  icmp-blocks:
+  rich rules:
+----
+
+[NOTE]
+====
+To specify the zone for which to display the settings, add the [option]`--zone=pass:attributes[{blank}]_zone-name_pass:attributes[{blank}]` argument to the [command]`firewall-cmd --list-all` command, for example:
+----
+~]# firewall-cmd --list-all --zone=home
+home
+  target: default
+  icmp-block-inversion: no
+  interfaces:
+  sources:
+  services: ssh mdns samba-client dhcpv6-client
+... [output truncated]
+
+----
+====
+
+To see the settings for particular information, such as services or ports, use a specific option. See the `firewalld` manual pages or get a list of the options using the command help:
+
+----
+$ firewall-cmd --help
+
+Usage: firewall-cmd [OPTIONS...]
+
+General Options
+  -h, --help           Prints a short help text and exists
+  -V, --version        Print the version string of firewalld
+  -q, --quiet          Do not print status messages
+
+Status Options
+  --state              Return and print firewalld state
+  --reload             Reload firewall and keep state information
+... [output truncated]
+----
+
+For example, to see which services are allowed in the current zone:
+
+----
+$ firewall-cmd --list-services
+samba-client ssh dhcpv6-client
+----
+
+Listing the settings for a certain subpart using the CLI tool can sometimes be difficult to interpret. For example, you allow the `SSH` service and `firewalld` opens the necessary port (22) for the service. Later, if you list the allowed services, the list shows the `SSH` service, but if you list open ports, it does not show any. Therefore, it is recommended to use the [option]`--list-all` option to make sure you receive a complete information.

en-US/modules/proc_closing_ports_firewalld.adoc

@@ -0,0 +1,42 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+// Base the file name and the ID on the module title. For example:
+// * file name: doing-procedure-a.adoc
+// * ID: [id='doing-procedure-a']
+// * Title: = Doing procedure A
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id=closing-ports-firewalld-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Closing a port
+
+When an open port is no longer needed, close that port in firewalld. It is highly recommended to close all unnecessary ports as soon as they are not used because leaving a port open represents a security risk.
+
+.Closing a port using the command line
+
+To close a port, remove it from the list of allowed ports:
+
+. List all allowed ports:
++
+----
+$ firewall-cmd --list-ports
+----
++
+[WARNING]
+====
+This command will only give you a list of ports that have been opened as ports. You will not be able to see any open ports that have been opened as a service. Therefore, you should consider using the --list-all option instead of --list-ports.
+====
++
+. Remove the port from the allowed ports to close it for the incoming traffic:
++
+----
+$ sudo firewall-cmd --remove-port=port-number/port-type
+----
++
+. Make the new settings persistent:
++
+----
+$ sudo firewall-cmd --runtime-to-permanent
+----

en-US/modules/proc_configuring-xorg-as-default-gnome-session.adoc

@@ -0,0 +1,15 @@
+[id='configuring-xorg-as-default-gnome-session']
+= Configuring Xorg as the default GNOME session
+
+To run GNOME in X11, click the gear icon on the Fedora log in screen and select *GNOME on Xorg*, or complete the following steps:
+
+[discrete]
+== Procedure
+
+. Open `/etc/gdm/custom.conf` and uncomment `WaylandEnable=false`.
+
+. Add the following line to the `[daemon]` section:
+
+  DefaultSession=gnome-xorg.desktop
+
+. Save the `custom.conf` file.

en-US/modules/proc_configuring_firewalld.adoc

@@ -0,0 +1,43 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+[id='configuring_firewalld_fedora']
+
+= Modifying Settings in runtime and permanent configuration using CLI
+
+Using the CLI, you do not modify the firewall settings in both modes at the same time. You only modify either runtime or permanent mode. To modify the firewall settings in the permanent mode, use the --permanent option with the firewall-cmd command.
+
+----
+$ sudo firewall-cmd --permanent <other options>
+----
+
+Without this option, the command modifies runtime mode.
+To change settings in both modes, you can use two methods:
+
+Change runtime settings and then make them permanent as follows:
+----
+$ sudo firewall-cmd <other options>
+$ sudo firewall-cmd --runtime-to-permanent
+----
+
+Set permanent settings and reload the settings into runtime mode:
+
+----
+$ sudo firewall-cmd --permanent <other options>
+$ sudo firewall-cmd --reload
+----
+
+The first method allows you to test the settings before you apply them to the permanent mode.
+
+[Note]
+====
+
+It is possible, especially on remote systems, that an incorrect setting results in a user locking themselves out of a machine. To prevent such situations, use the `--timeout` option. After a specified amount of time, any change reverts to its previous state. Using this options excludes the --permanent option.
+For example, to add the SSH service for 15 minutes:
+
+----
+$ sudo firewall-cmd --add-service=ssh --timeout 15m
+----
+
+====

en-US/modules/proc_creating-a-disk-partition-in-linux.adoc

@@ -0,0 +1,105 @@
+// Module included in the following assemblies:
+//
+// <List assemblies here, each on a new line>
+
+// Base the file name and the ID on the module title. For example:
+// * file name: proc_creating-a-disk-partition-in-linux.adoc
+// * ID: [id='creating-a-disk-partition-in-linux']
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id='creating-a-disk-partition-in-linux_{context}']
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Creating a Disk Partition in Linux
+// Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.
+
+This procedure describes how to partition a storage disk in Linux using the `parted` command.
+
+.Procedure
+
+. List the partitions using the `parted -l` command to identify the storage device you want to partition. Typically, the first hard disk (`/dev/sda` or `/dev/vda`) will contain the operating system, so look for another disk to find the one you want. For example:
++
+----
+$ sudo parted -l
+[sudo] password for user:
+Model: ATA RevuAhn_850X1TU5 (scsi)
+Disk /dev/vdc: 512GB
+Sector size (logical/physical): 512B/512B
+Partition Table: msdos
+Disk Flags:
+
+Number  Start   End    Size   Type     File system  Flags
+ 1      1049kB  525MB  524MB  primary  ext4         boot
+ 2      525MB   512GB  512GB  primary               lvm
+----
++
+. Open the storage device. Use the `parted` command to begin working with the selected storage device. For example:
++
+----
+$ sudo parted /dev/vdc
+GNU Parted 3.2
+Using /dev/vdc
+Welcome to GNU Parted! Type 'help' to view a list of commands.
+(parted)
+----
++
+[IMPORTANT]
+====
+Be sure to indicate the specific device you want to partition. If you just enter `parted` without a device name, it will randomly select a storage device to modify.
+====
++
+. Set the partition table type to `gpt`, then enter `Yes` to accept it.
++
+----
+(parted) mklabel gpt
+Warning: the existing disk label on /dev/vdc will be destroyed
+and all data on this disk will be lost. Do you want to continue?
+Yes/No? Yes
+----
++
+[NOTE]
+====
+The `mklabel` and `mktable` commands are both used for making a partition table on a storage device. At time of writing, the supported partition tables are: `aix`, `amiga`, `bsd`, `dvh`, `gpt`, `mac`, `ms-dos`, `pc98`, `sun`, and `loop`. Remember `mklabel` will not make a partition, rather it will make a partition table.
+====
+. Review the partition table of the storage device.
++
+----
+(parted) print
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdc: 1396MB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+Number Start End Size File system Name Flags
+----
++
+. Create a new partition using the following command. For example, 1396 MB on partition 0:
++
+----
+(parted) mkpart primary 0 1396MB
+
+Warning: The resulting partition is not properly aligned for best performance
+Ignore/Cancel? I
+
+(parted) print
+Model: Virtio Block Device (virtblk)
+Disk /dev/vdc: 1396MB
+Sector size (logical/physical): 512B/512B
+Partition Table: gpt
+Disk Flags:
+Number Start   End     Size    File system Name Flags
+1      17.4kB  1396MB  1396MB  primary
+----
++
+[NOTE]
+====
+Providing a partition name under GPT is a must; in the above example, primary is the name, not the partition type. In a GPT partition table, the partition type is used as partition name. 
+====
++
+. Quit using the `quit` command. Changes are automatically saved when you quit `parted`.
++
+----
+(parted) quit
+Information: You may need to update /etc/fstab. 
+$
+----
++

en-US/modules/proc_creating_xorg_conf.adoc

@@ -14,3 +14,5 @@ Next, copy the file to the correct location:
 ----
 
 Now you may edit the file according to your needs.
+
+See the `xorg.conf(5)` man page for more information.

en-US/modules/proc_enabling-shortcut-custom-app-gnome.adoc

@@ -3,9 +3,6 @@
 
 This section describes how to enable a keyboard shortcut for starting a custom application in GNOME.
 
-[discrete]
-== Procedure
-
 . Open *Settings* and choose the *Devices* entry from the list:
 +
 image::shortcuts-settings-devices.png[]
@@ -39,4 +36,3 @@ As soon as you release the key combination, the window for entering the shortcut
 image::shortcuts-enabling-entered.png[]
 
 . Close the shortcut editing window.
-

en-US/modules/proc_enabling-third-party-repository.adoc

@@ -1,15 +1,14 @@
 [id='enabling-third-party-repository']
-= Enabling Third party repositories 
+= Enabling Third party repositories
 
 Once you have downloaded the rpm, you can enable the repository.
 
 == To enable repo:
 
 . Login as root:
-`#su`
+`$ su`
 
 . Create a file in */etc/yum.repos.d/* directory to enable third party repository. This file must end with *.repo* . The repository file contains the URL of the the repository, a name, enabled, gpgcheck.
 
 . To enable repo, use the following command:
-`#dnf --enablerepo=<reponame>`
-
+`# dnf --enablerepo=<reponame>`

en-US/modules/proc_enabling_firewalld.adoc

@@ -0,0 +1,81 @@
+// Module included in the following assemblies:
+//
+// <List assemblies here, each on a new line>
+
+// Base the file name and the ID on the module title. For example:
+// * file name: doing-procedure-a.adoc
+// * ID: [id='doing-procedure-a']
+// * Title: = Doing procedure A
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id='doing-one-procedure_{context}']
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Doing one procedure
+// Start the title of a procedure module with a verb, such as Creating or Create. See also _Wording of headings_ in _The IBM Style Guide_.
+
+This paragraph is the procedure module introduction: a short description of the procedure.
+
+.Prerequisites
+
+* A bulleted list of conditions that must be satisfied before the user starts following this assembly.
+* You can also link to other modules or assemblies the user must follow before starting this assembly.
+* Delete the section title and bullets if the assembly has no prerequisites.
+
+.Procedure
+
+. Start each step with an active verb.
+
+. Include one command or action per step.
+
+. Use an unnumbered bullet (*) if the procedure includes only one step.
+
+.Additional resources
+
+* A bulleted list of links to other material closely related to the contents of the procedure module.
+* For more details on writing procedure modules, see the link:https://github.com/redhat-documentation/modular-docs#modular-documentation-reference-guide[Modular Documentation Reference Guide].
+* Use a consistent system for file names, IDs, and titles. For tips, see _Anchor Names and File Names_ in link:https://github.com/redhat-documentation/modular-docs#modular-documentation-reference-guide[Modular Documentation Reference Guide].
+
+
+== Do I have FirewallD on my system?
+
+FirewallD is the default firewall service for current releases of Fedora and is enabled by default.
+If you are not sure whether FirewallD is on your Fedora installation use the following commands to check.  
+
+
+. Check if your system has FirewallD enabled.
+Enter the folowing on the command line:
+ 
+[source,bash]
+
+----
+
+sudo firewall-cmd --state
+
+----
+
+You will see `running` if FirewallD is on your system. 
+
+If you see `not running`, then FirewallD is not on your system. Use these commands to install it:
+
+
+. Install FirewallD:
+
+[source,bash]
+
+----
+
+sudo dnf install firewalld
+
+----
+
+. Install the FirewallD graphical-user-interface application and open it from the command-line, type:
+
+[source,bash]
+
+----
+
+sudo dnf install firewall-config
+
+sudo firewall-config
+
+----

en-US/modules/proc_install_firewalld_gui.adoc

@@ -0,0 +1,18 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+
+[id=installing-firewalld-gui-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Installing the [application]*firewall-config* GUI configuration tool
+
+To use the [application]*firewall-config* GUI configuration tool, install the [package]*firewall-config* package as `root`:
+
+----
+$ sudo dnf install firewall-config
+----
+
+Alternatively, in [application]*GNOME*, use the kbd:[Super] key and type `Software` to launch the [application]*Software Sources* application. Type `firewall` to the search box, which appears after selecting the search button in the top-right corner. Select the `Firewall` item from the search results, and click on the btn:[Install] button.
+
+To run [application]*firewall-config*, use either the [command]`firewall-config` command or press the kbd:[Super] key to enter the `Activities Overview`, type `firewall`, and press kbd:[Enter].

en-US/modules/proc_installing_firewalld.adoc

@@ -0,0 +1,25 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+// Base the file name and the ID on the module title. For example:
+// * file name: doing-procedure-a.adoc
+// * ID: [id='doing-procedure-a']
+// * Title: = Doing procedure A
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id=installing-firewalld-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Installing firewalld
+
+.Install firewalld:
+
+. Run this command on the command line:
+
+[source,bash]
+
+----
+
+sudo dnf install firewalld
+
+----

en-US/modules/proc_managing-trusted-system-certificates.adoc

@@ -1,8 +1,6 @@
 [id='proc_managing-trusted-system-certificates']
 = Managing Trusted System Certificates
 
-.Procedure
-
 To list, extract, add, remove, or change trust anchors, use the [command]`trust` command. To see the built-in help for this command, enter it without any arguments or with the [option]`--help` directive:
 
 [subs="quotes, macros"]

en-US/modules/proc_opening_ports_firewalld.adoc

@@ -0,0 +1,37 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+// Base the file name and the ID on the module title. For example:
+// * file name: doing-procedure-a.adoc
+// * ID: [id='doing-procedure-a']
+// * Title: = Doing procedure A
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id=opening-ports-firewalld-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Opening a port
+
+Through open ports, the system is accessible from the outside, which represents a security risk. Generally, keep ports closed and only open them if they are required for certain services.
+
+.Opening a port using the command line
+
+. Get a list of allowed ports in the current zone:
++
+----
+$ firewall-cmd --list-ports
+----
++
+. Add a port to the allowed ports to open it for incoming traffic:
++
+----
+$ sudo firewall-cmd --add-port=port-number/port-type
+----
++
+. Make the new settings persistent:
++
+----
+$ sudo firewall-cmd --runtime-to-permanent
+----
+
+The port types are either tcp, udp, sctp, or dccp. The type must match the type of network communication.

en-US/modules/proc_starting_firewalld.adoc

@@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+//
+// firewalld.adoc
+
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id=starting-firewalld-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Starting firewalld
+
+Start firewalld, by entering the following commands:
+
+----
+$ sudo systemctl unmask firewalld
+$ sudo systemctl start firewalld
+----
+
+To make firewalld start automatically at system start:
+
+----
+$ sudo systemctl enable firewalld
+----

en-US/modules/proc_stopping_firewalld.adoc

@@ -0,0 +1,29 @@
+// Module included in the following assemblies:
+//
+//firewalld.adoc
+
+// Base the file name and the ID on the module title. For example:
+// * file name: doing-procedure-a.adoc
+// * ID: [id='doing-procedure-a']
+// * Title: = Doing procedure A
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id=stopping-firewalld-fedora]
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Stopping firewalld
+
+
+To stop firewalld, enter the following command as root:
+----
+$ sudo systemctl stop firewalld
+----
+
+Prevent firewalld from starting automatically at system start, enter the following command as root:
+----
+$ sudo systemctl disable firewalld
+----
+
+Make sure firewalld is not started by accessing the firewalld D-Bus interface and also if other services require firewalld, enter the following command as root:
+----
+$ sudo systemctl mask firewalld
+----

en-US/modules/ref_help-mkpart.adoc

@@ -0,0 +1,37 @@
+// Module included in the following assemblies:
+//
+// <List assemblies here, each on a new line>
+
+// Base the file name and the ID on the module title. For example:
+// * file name: help-mkpart.adoc
+// * ID: [id='help-mkpart']
+
+// The ID is used as an anchor for linking to the module. Avoid changing it after the module has been published to ensure existing links are not broken.
+[id='help-mkpart_{context}']
+// The `context` attribute enables module reuse. Every module's ID includes {context}, which ensures that the module has a unique ID even if it is reused multiple times in a guide.
+= Help command for creating a new partition
+
+To get help on how to make a new partition, type: `help mkpart`.
+
+----
+(parted) help mkpart
+  mkpart PART-TYPE [FS-TYPE] START END     make a partition
+
+        PART-TYPE is one of: primary, logical, extended
+        FS-TYPE is one of: btrfs, nilfs2, ext4, ext3, ext2, fat32, fat16, hfsx, hfs+, hfs, jfs, swsusp,
+        linux-swap(v1), linux-swap(v0), ntfs, reiserfs, hp-ufs, sun-ufs, xfs, apfs2, apfs1, asfs, amufs5,
+        amufs4, amufs3, amufs2, amufs1, amufs0, amufs, affs7, affs6, affs5, affs4, affs3, affs2, affs1,
+        affs0, linux-swap, linux-swap(new), linux-swap(old)
+        START and END are disk locations, such as 4GB or 10%.  Negative values count from the end of the
+        disk.  For example, -1s specifies exactly the last sector.
+       
+        'mkpart' makes a partition without creating a new file system on the partition.  FS-TYPE may be
+        specified to set an appropriate partition ID.
+----
+
+[NOTE]
+====
+* Filesystem type (fstype) will not create an ext4 filesystem on /dev/vdc1. 
+* A DOS partition table's partition types are primary, logical, and extended. 
+* Providing a partition name under GPT is a must. In a GPT partition table, the partition type is used as the partition name.
+====

en-US/proc_setting-key-shortcut.adoc

@@ -0,0 +1,23 @@
+[id='setting-key-shortcut_{context}']
+= Setting a key shortcut to run an application in GNOME
+
+If you frequently use a certain application, you can set a keyboard shortcut to quickly launch that application on GNOME.
+
+This example shows how to set a key shortcut to launch the terminal.
+
+To set a key shortcut to run an application:
+
+. Navigate to menu:Settings[Keyboard] to open the *Keyboard Shortcuts* list.
+. Click `+` at the bottom of the list to create a new shortcut.
+. Enter the following details in the *Add Custom Shortcut* window:
+* Add a `Name` for your shortcut, for example, `Terminal`.
+* Enter the command that launches the application. For example, `gnome-terminal`.
+. Click *Set Shortcut* to open the *Set Custom Shortcut* window.
+. Type a keyboard shortcut, for example `Ctrl-Alt-T`.
+. Click *Add*.
+
+Your shortcut appears under *Custom Shortcuts* and is ready to use.
+
+image:custom_shortcut.png[]
+
+To edit or remove your shortcut, click the shortcut to open its details.