Add 'unverified' banner on top of each file and review instructions to readme

README.md

@@ -1,6 +1,6 @@
 # Fedora Quick Docs
 
-This is the content repository for the Fedora Quick Docs
+This is the content repository for the Fedora Quick Docs.
 
 Please report Issues and submit Pull Requests for **Content Fixes** here.
 Never done a pull request (or "PR")? Here's the [Pagure documentation for
@@ -10,6 +10,17 @@ Pull Requests](https://docs.pagure.org/pagure/usage/pull_requests.html).
 General appearance issues and publishing issues should be reported against
 the [publishing software](https://pagure.io/fedora-docs/docs-fp-o).
 
+## Rewievers needed!
+
+As discussed in [issue #107](https://pagure.io/fedora-docs/quick-docs/issue/107),
+a lot of pages in this repository are in need of a technical review. Pages which need
+one are marked by a disclaimer on the top of the file, right below the top level heading.
+Any reviews are greatly appreciated. If you want to help, pick one of the pages, check it
+for accuracy, and then:
+
+* If you find that all information on the page is correct, either open a pull request which states that you found no problems and which removes the disclaimer from the top (the `include::`) statement at the top, or open an issue against this repository stating which page you reviewed and found no errors in so we can remove it
+* If you find errors, then either open a pull request fixing them and removing the disclaimer from the top, or open an issue and describe the errors you found, and how to fix them if you know a fix
+
 ## How to edit these documents
 
 All of this is written in AsciiDoc. It's a simple mostly-plain-text

modules/ROOT/pages/_partials/unreviewed-message.adoc

@@ -0,0 +1,17 @@
+////
+
+This message needs to be included on any document that has been converted from the Wiki but not reviewed for technical accuracy.
+Add the following line verbatim to the top of any such document - below the top level heading:
+
+include::{partialsdir}/unreviewed-message.adoc[]
+
+Please do not change this message without consultation. Thanks!
+
+////
+
+[CAUTION]
+====
+This page has been converted from the Fedora Project Wiki and cleaned up for publishing here on the Fedora Docs Portal, but it has not yet been reviewed for technical accuracy.
+This means any information on this page may be outdated or inaccurate.
+Reviews for technical accuracy are greatly appreciated. If you want to help, see the link:https://pagure.io/fedora-docs/quick-docs/blob/master/f/README.md[README] file in the source repository for instructions.
+====

modules/ROOT/pages/adding-new-fonts-fedora.adoc

@@ -2,14 +2,15 @@
 ifdef::context[:parent-context: {context}]
 :context: adding-new-fonts-fedora
 
-
 [[adding-new-fonts-fedora]]
 = Adding new fonts in Fedora
 
-The default installation of the Fedora Linux (Fedora) includes several basic fonts. If you plan to use Fedora for activities such as typesetting and graphic design, you may wish to add additional fonts. 
+include::{partialsdir}/unreviewed-message.adoc[]
+
+The default installation of the Fedora Linux (Fedora) includes several basic fonts. If you plan to use Fedora for activities such as typesetting and graphic design, you may wish to add additional fonts.
 
 include::{partialsdir}/proc_adding-new-fonts-as-superuser.adoc[leveloffset=+1]
 
-include::{partialsdir}/proc_adding-new-fonts-as-user.adoc[leveloffset=+1] 
+include::{partialsdir}/proc_adding-new-fonts-as-user.adoc[leveloffset=+1]
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]

modules/ROOT/pages/adding-or-removing-software-repositories-in-fedora.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 [id='adding-or-removing-software-repositories-in-fedora']
 = Adding or removing software repositories in Fedora
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This section describes how to add, enable, or disable a software repository with the DNF application.
 
 include::{partialsdir}/proc_adding-repositories.adoc[leveloffset=+1]

modules/ROOT/pages/adding_user_to_sudoers_file.adoc

@@ -4,6 +4,8 @@ ifdef::context[:parent-context: {context}]
 = Adding a user to sudoers
 [id=adding_user_to_sudoers_{context}]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 One of the most common operations that administrators want to accomplish when managing `sudo` permissions is to grant a new user general `sudo` access. This is helpful if you want to give an account full administrative access to the system.
 
 [discrete]

modules/ROOT/pages/anaconda/anaconda.adoc

@@ -1,5 +1,7 @@
 = Anaconda
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 [caption="Entering Anaconda, Montana. A city probably named after this installation program. David Cantrell took this picture in 2011. His grey VW Jetta is parked in the background."]
 image::DSC_3217.JPG[Anaconda,400]
 
@@ -85,7 +87,7 @@ More are in the works:
 * If you want to work on Anaconda, you should start with the Anaconda/SourceOverview[Source Overview], which contains a high level discussion of the source files and what they do.
 
 Then look at the https://anaconda-installer.readthedocs.io/en/latest/[online documentation] for information on how to test, debug, and develop anaconda.
- 
+
 Familiarize yourself with the tools that Anaconda uses.
 Check out the following external reference documents:
 

modules/ROOT/pages/anaconda/anaconda_logging.adoc

@@ -1,5 +1,7 @@
 = Anaconda Logging
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 == Introduction
 Anaconda tracks all of its activities in logs.
 This includes:
@@ -187,14 +189,14 @@ To avoid name clashes with other log files there, the anaconda logs are renamed:
 
 [%header,cols=2*]
 |====
-| Name during installation | Name on the target system 
-| `/tmp/anaconda.log` | `/var/log/anaconda.log` 
-| `/tmp/syslog` | `/var/log/anaconda.syslog` 
-| `/tmp/X.log` | `/var/log/anaconda.xlog` 
-| `/tmp/program.log` | `/var/log/anaconda.program.log` 
-| `/tmp/storage.log` | `/var/log/anaconda.storage.log` 
-| `/tmp/yum.log` | `/var/log/anaconda.yum.log` 
-| `/tmp/ifcfg.log` (new in F14) | not copied 
+| Name during installation | Name on the target system
+| `/tmp/anaconda.log` | `/var/log/anaconda.log`
+| `/tmp/syslog` | `/var/log/anaconda.syslog`
+| `/tmp/X.log` | `/var/log/anaconda.xlog`
+| `/tmp/program.log` | `/var/log/anaconda.program.log`
+| `/tmp/storage.log` | `/var/log/anaconda.storage.log`
+| `/tmp/yum.log` | `/var/log/anaconda.yum.log`
+| `/tmp/ifcfg.log` (new in F14) | not copied
 |====
 
 Starting with Fedora 15 (or post F14 Rawhide), the logs go to `/var/log/anaconda` directory on the target system, including ifcfg.log inroduced in F14.

modules/ROOT/pages/anaconda/anaconda_product_image.adoc

@@ -1,5 +1,7 @@
 = Creating a Product image
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Anaconda supports several ways to load new code at runtime.
 Passing `inst.updates=<url>` is one way to do this and is documented on the xref:anaconda/anaconda_updates.adoc[updates] page.
 Another is to include a product.img in the install tree, inside the `/images/` directory.

modules/ROOT/pages/anaconda/anaconda_updates.adoc

@@ -1,5 +1,7 @@
 = Anaconda Updates
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Anaconda has the capability to incorporate updates at runtime to fix any bugs or issues with the installer.
 These updates are generally distributed as a disk image file (referred to as `updates.img` from here on out)
 The `updates.img` can be used in a few different ways.
@@ -92,7 +94,7 @@ If you need finer control over this process (like creating an image from an even
 $ scripts/makeupdates
 ----
 
-by hand.  
+by hand.
 The help screen documents the several options that can be used.
 
 An `updates.img` can include more than just files from anaconda, though.

modules/ROOT/pages/assembly_installing-plugins-for-playing-movies-and-music.adoc

@@ -37,6 +37,8 @@ ifdef::context[:parent-context: {context}]
 [id='assembly_installing-plugins-for-playing-movies-and-music_{context}']
 = Installing plugins for playing movies and music
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 As a Fedora user and system administrator, you can use these steps to install additional multimedia plugins that enable you to play various video and audio types.
 
 WARNING: If you live in a country where software patents apply, such as in the United States or in Japan, you need to obtain multimedia codecs from a source that legally distributes patented software in your country. For example, see the Fluendo Codec Pack: link:https://fluendo.com/en/products/enterprise/fluendo-codec-pack/[].

modules/ROOT/pages/autoupdates.adoc

@@ -30,6 +30,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 [[automatic-updates]]
 Automatic Updates

modules/ROOT/pages/bootloading-with-grub2.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='bootloading-with-grub2']
 = Bootloading with GRUB2
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 *GRUB2* is the latest version of *GNU GRUB*, the _GRand Unified Bootloader_. A bootloader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the operating system kernel. In Fedora, the kernel is Linux. The kernel then initializes the rest of the operating system.
 
 *GRUB2* is the follower of the previous version *GRUB* (version 0.9x). The original version is available under the name *GRUB Legacy*.

modules/ROOT/pages/bumblebee.adoc

@@ -4,6 +4,8 @@ include::{partialsdir}/attributes.adoc[]
 
 include::{partialsdir}/3rdparty-message.adoc[]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 [[description]]
 == Description
 

modules/ROOT/pages/changing-selinux-states-and-modes.adoc

@@ -10,6 +10,8 @@ ifdef::context[:parent-context: {context}]
 
 :md: en-US/modules
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/con_permanent-changes-in-selinux-states-and-modes.adoc[leveloffset=+1]
 include::{partialsdir}/proc_enabling-selinux.adoc[leveloffset=+1]
 include::{partialsdir}/proc_changing-to-permissive-mode.adoc[leveloffset=+2]

modules/ROOT/pages/configuring-ip-networking-with-nmcli.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='Configuring-networking-with-nmcli']
 = Configuring IP networking with nmcli
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 How to configure networking using the [application]*nmcli* (NetworkManager Command Line Interface) command-line utility.
 
 include::{partialsdir}/con_Getting-started-with-nmcli.adoc[leveloffset=+1]

modules/ROOT/pages/configuring-x-window-system-using-the-xorg-conf-file.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='configuring-x-window-system-using-the-xorg-conf-file']
 = Configuring X Window System using the xorg.conf file
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/con_xorg-conf.adoc[leveloffset=+1]
 
 include::{partialsdir}/proc_creating_xorg_conf.adoc[leveloffset=+1]

modules/ROOT/pages/configuring-xorg-as-default-gnome-session.adoc

@@ -4,6 +4,8 @@ ifdef::context[:parent-context: {context}]
 [id='configuring-xorg-as-default-gnome-session']
 = Configuring Xorg as the default GNOME session
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Wayland is the default GNOME display server. If GNOME freezes, or some applications do not function correctly in Wayland, you can choose to run GNOME in X11.
 
 

modules/ROOT/pages/create-gpg-keys.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 = Creating GPG Keys
 :experimental:
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This document explains in detail how to obtain a GPG key using common Fedora utilities.
 It also provides information on managing your key as a Fedora contributor.
 

modules/ROOT/pages/create-hello-world-rpm.adoc

@@ -2,6 +2,8 @@ include::{partialsdir}/attributes.adoc[]
 
 = How to Create a GNU Hello World RPM Package
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This is a short hands-on tutorial on writing RPM files, showing how to quickly step up to create simple source and binary software packages.
 It assumes some familiarity with using pre-made RPM packages, and with the FOSS building process.
 
@@ -256,10 +258,10 @@ $ mock --verbose ../SRPMS/hello-2.10-1.fc25.src.rpm
 
 == History
 
-Przemek Klosowski wrote this tutorial when he worked through link:Building_RPM_packages_%2820090405%29[Christoph Wickert's IRC session on building RPMs] using Rahul Sundaram suggestion of GNU "Hello World" as a test case. 
-After he wrote up his experience, he found out about the excellent and extensive link:How_to_create_an_RPM_package[How to create an RPM package] page on this wiki, as well as the link:http://www.absolutepanic.org/blog/2009/07/building-a-gnu-hello-world-rpm[Christian Lyder Jacobsen's website]. 
-However, Christian isn't planning to update his site, and it seemed that a 5-minute 'fast food' alternative to the more extensive article might suit some people. 
+Przemek Klosowski wrote this tutorial when he worked through link:Building_RPM_packages_%2820090405%29[Christoph Wickert's IRC session on building RPMs] using Rahul Sundaram suggestion of GNU "Hello World" as a test case.
+After he wrote up his experience, he found out about the excellent and extensive link:How_to_create_an_RPM_package[How to create an RPM package] page on this wiki, as well as the link:http://www.absolutepanic.org/blog/2009/07/building-a-gnu-hello-world-rpm[Christian Lyder Jacobsen's website].
+However, Christian isn't planning to update his site, and it seemed that a 5-minute 'fast food' alternative to the more extensive article might suit some people.
 More in-depth information on using and building RPM packages is available from link:Yum[other sources].
 
-See a typo, something missing or out of date, or anything else which can be improved? 
+See a typo, something missing or out of date, or anything else which can be improved?
 Edit this document at https://pagure.io/fedora-docs/quick-docs.

modules/ROOT/pages/creating-a-disk-partition-in-linux.adoc

@@ -4,6 +4,8 @@ ifdef::context[:parent-context: {context}]
 [id='disk-partition-in-linux-{context}']
 = Creating a disk partition in Linux
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/con_disk-partition-linux.adoc[leveloffset=+1]
 include::{partialsdir}/proc_creating-a-disk-partition-in-linux.adoc[leveloffset=+1]
 include::{partialsdir}/ref_help-mkpart.adoc[leveloffset=+1]

modules/ROOT/pages/creating-and-using-a-live-installation-image.adoc

@@ -2,6 +2,8 @@ ifdef::context[:parent-context: {context}]
 :context: creating-an-using-a-live-installation-image
 = Creating and using a live installation image
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/proc_downloading-fedora.adoc[leveloffset=+1]
 
 include::{partialsdir}/proc_creating-and-using-live-usb.adoc[leveloffset=+1]

modules/ROOT/pages/creating-rpm-packages.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='creating-rpm-packages']
 = Creating RPM packages
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Learn the basics of RPM packaging.
 
 include::{partialsdir}/con_rpm_packaging_overview.adoc[leveloffset=+1]

modules/ROOT/pages/creating-windows-virtual-machines-using-virtio-drivers.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='creating-windows-virtual-machines-using-virtio-drivers']
 = Creating Windows virtual machines using virtIO drivers
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This document describes how to obtain virtIO drivers  and additional software agents for Windows virtual machines running on kernel-based virtual machines (KVM). https://www.linux-kvm.org/page/Virtio[virtIO] is a virtualization standard for network and disk device drivers.
 
 Fedora cannot ship Windows virtIO drivers because they cannot be built automatically as part of Fedora’s build system: the only way to build Windows virtIO drivers is on a machine running Windows.  In addition, shipping pre-compiled sources is generally against Fedora policies.  Microsoft does not provide virtIO drivers, you must download them yourself in order to make virtIO drivers available for Windows VMs running on Fedora hosts.

modules/ROOT/pages/debug-dracut-problems.adoc

@@ -30,6 +30,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 *Foreword*
 
@@ -183,7 +184,7 @@ serial --unit=0 --speed=9600
 terminal --timeout=5 serial console
 title Fedora (2.6.29.5-191.fc11.x86_64)
         root (hd0,0)
-        kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 rd.shell 
+        kernel /vmlinuz-2.6.29.5-191.fc11.x86_64 ro root=/dev/mapper/vg_uc1-lv_root console=tty0 rd.shell
         initrd /dracut-2.6.29.5-191.fc11.x86_64.img
 ....
 
@@ -195,7 +196,7 @@ No root device found
 Dropping to debug shell.
 
 sh: can't access tty; job control turned off
-# 
+#
 ....
 
 Use this shell prompt to gather the information requested above (see
@@ -247,11 +248,11 @@ activate any logical volumes
 +
 ....
 # blkid
-/dev/sda1: UUID="3de247f3-5de4-4a44-afc5-1fe179750cf7" TYPE="ext4" 
-/dev/sda2: UUID="Ek4dQw-cOtq-5MJu-OGRF-xz5k-O2l8-wdDj0I" TYPE="LVM2_member" 
-/dev/mapper/linux-root: UUID="def0269e-424b-4752-acf3-1077bf96ad2c" TYPE="crypto_LUKS" 
-/dev/mapper/linux-home: UUID="c69127c1-f153-4ea2-b58e-4cbfa9257c5e" TYPE="ext3" 
-/dev/mapper/linux-swap: UUID="47b4d329-975c-4c08-b218-f9c9bf3635f1" TYPE="swap" 
+/dev/sda1: UUID="3de247f3-5de4-4a44-afc5-1fe179750cf7" TYPE="ext4"
+/dev/sda2: UUID="Ek4dQw-cOtq-5MJu-OGRF-xz5k-O2l8-wdDj0I" TYPE="LVM2_member"
+/dev/mapper/linux-root: UUID="def0269e-424b-4752-acf3-1077bf96ad2c" TYPE="crypto_LUKS"
+/dev/mapper/linux-home: UUID="c69127c1-f153-4ea2-b58e-4cbfa9257c5e" TYPE="ext3"
+/dev/mapper/linux-swap: UUID="47b4d329-975c-4c08-b218-f9c9bf3635f1" TYPE="swap"
 ....
 4.  From the output above, you recall that your root volume exists on an
 encrypted block device. Following the guidance disk encryption guidance
@@ -263,7 +264,7 @@ Installation Guide], you unlock your encrypted root volume.
 UUID=$(cryptsetup luksUUID /dev/mapper/linux-root)
 cryptsetup luksOpen /dev/mapper/linux-root luks-$UUID
 Enter passphrase for /dev/mapper/linux-root:
-Key slot 0 unlocked. 
+Key slot 0 unlocked.
 ....
 5.  Next, make a symbolic link to the unlocked root volume
 +

modules/ROOT/pages/debug-systemd-problems.adoc

@@ -30,6 +30,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 *Foreword*
 

modules/ROOT/pages/debug-wayland-problems.adoc

@@ -30,6 +30,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 https://en.wikipedia.org/wiki/Wayland_%28display_server_protocol%29[Wayland]
 is intended as a simpler replacement for

modules/ROOT/pages/disabling-automatic-screenlock.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 
 = Disabling the GNOME automatic screen locking
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/proc_disabling-gnome-screenlock.adoc[leveloffset=+1]
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]

modules/ROOT/pages/displaying_user_prompt_on_gnome_login_screen.adoc

@@ -4,6 +4,8 @@ ifdef::context[:parent-context: {context}]
 
 = Displaying a user prompt on the GNOME login screen
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/proc_displaying_user_prompt_on_gnome_login_screen.adoc[leveloffset=+1]
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]

modules/ROOT/pages/dnf-system-upgrade.adoc

@@ -1,6 +1,8 @@
 [[chap-dnf-system-upgrade]]
 = DNF System Upgrade
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 link:++https://github.com/rpm-software-management/dnf-plugin-system-upgrade++[`dnf-plugin-system-upgrade`] is a plugin for the link:++dnf.html++[DNF] package manager and is used to upgrade your system to the current release of Fedora.
 For Atomic Host, which uses rpm-ostree, you may refer to link:++https://rpm-ostree.readthedocs.io/en/latest/manual/administrator-handbook/++[Read The Docs: rpm-ostree] for details.
 
@@ -21,7 +23,7 @@ This is the recommended command-line upgrade method for Fedora 21 and later and
 *Back up your data* before performing a system-wide upgrade as every system upgrade is potentially risky.
 As a precaution, download the link:++https://getfedora.org/en/workstation/download/++[Fedora Workstation Live image] in the event something goes wrong.
 
-==== 
+====
 
 . To update your Fedora release from the command-line do:
 +
@@ -45,7 +47,7 @@ sudo dnf install dnf-plugin-system-upgrade
 
 ----
 
-. Download the updated packages (replace N with the release version): 
+. Download the updated packages (replace N with the release version):
 +
 [source,bash]
 
@@ -154,7 +156,7 @@ sudo dnf remove $(dnf repoquery --extras --exclude=kernel,kernel-\*)
 
 ----
 
-[NOTE] 
+[NOTE]
 
 ====
 
@@ -239,7 +241,7 @@ sudo dnf distro-sync --allowerasing
 [[sect-relabel-files-with-the-latest-selinux-policy]]
 === Relabel Files With The Latest SELinux Policy
 
-If you encounter any warnings regarding policies with SELinux, some files may have incorrect SELinux permissions. 
+If you encounter any warnings regarding policies with SELinux, some files may have incorrect SELinux permissions.
 This may happen if SELinux was disabled at some point in the past.
 To relabel the entire system run:
 
@@ -325,4 +327,4 @@ Refer to the link:++https://getfedora.org/keys/faq/++[getfedora.org FAQ on Keys]
 [[sect-can-i-use-dnf-system-upgrade-to-upgrade-to-a-pre-release]]
 === Can I Use DNF System Upgrade To Upgrade To A Pre-Release (e.g. a Beta)?
 
-Yes, but this is subject to temporary breakage as with any other aspect of a pre-release.
+Yes, but this is subject to temporary breakage as with any other aspect of a pre-release.

modules/ROOT/pages/dnf.adoc

@@ -1,6 +1,8 @@
 [[chap-dnf]]
 = Using the DNF software package manager
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 DNF is a software package manager that installs, updates, and removes packages on Fedora and is the successor to YUM (Yellow-Dog Updater Modified).
 DNF makes it easy to maintain packages by automatically checking for dependencies and determines the actions required to install packages.
 This method eliminates the need to manually install or update the package, and its dependencies, using the `rpm` command.

modules/ROOT/pages/edit-iptables-rules.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 In this how-to, we will illustrate three ways to edit iptables Rules :
 
@@ -73,17 +74,17 @@ or related, icmp requests, all local traffic, and ssh communication:
 ....
 [root@server ~]# iptables -L
 Chain INPUT (policy DROP)
-target     prot opt source               destination         
+target     prot opt source               destination
 ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
-ACCEPT     icmp --  anywhere             anywhere            
-ACCEPT     all  --  anywhere             anywhere            
+ACCEPT     icmp --  anywhere             anywhere
+ACCEPT     all  --  anywhere             anywhere
 ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
 
 Chain FORWARD (policy ACCEPT)
-target     prot opt source               destination         
+target     prot opt source               destination
 
 Chain OUTPUT (policy ACCEPT)
-target     prot opt source               destination 
+target     prot opt source               destination
 ....
 
 Note that Rules are applied in order of appearance, and the inspection
@@ -101,18 +102,18 @@ The following adds a Rule at the end of the specified chain of iptables:
 [root@server ~]# iptables -A INPUT -p tcp --dport 80 -j ACCEPT
 [root@server ~]# iptables -L
 Chain INPUT (policy DROP)
-target     prot opt source               destination         
+target     prot opt source               destination
 ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
-ACCEPT     icmp --  anywhere             anywhere            
-ACCEPT     all  --  anywhere             anywhere            
+ACCEPT     icmp --  anywhere             anywhere
+ACCEPT     all  --  anywhere             anywhere
 ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
 ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http
 
 Chain FORWARD (policy ACCEPT)
-target     prot opt source               destination         
+target     prot opt source               destination
 
 Chain OUTPUT (policy ACCEPT)
-target     prot opt source               destination 
+target     prot opt source               destination
 ....
 
 Notice the last line in chain INPUT. There are now five Rules in that
@@ -129,17 +130,17 @@ the fifth position:
 [root@server ~]# iptables -D INPUT 5
 [root@server ~]# iptables -L
 Chain INPUT (policy DROP)
-target     prot opt source               destination         
+target     prot opt source               destination
 ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
-ACCEPT     icmp --  anywhere             anywhere            
-ACCEPT     all  --  anywhere             anywhere            
+ACCEPT     icmp --  anywhere             anywhere
+ACCEPT     all  --  anywhere             anywhere
 ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
 
 Chain FORWARD (policy ACCEPT)
-target     prot opt source               destination         
+target     prot opt source               destination
 
 Chain OUTPUT (policy ACCEPT)
-target     prot opt source               destination 
+target     prot opt source               destination
 ....
 
 [[inserting-rules]]
@@ -151,18 +152,18 @@ Create a Rule at the top (first) position:
 [root@server ~]# iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
 [root@server ~]# iptables -L
 Chain INPUT (policy DROP)
-target     prot opt source               destination         
+target     prot opt source               destination
 ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http
 ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
-ACCEPT     icmp --  anywhere             anywhere            
-ACCEPT     all  --  anywhere             anywhere            
+ACCEPT     icmp --  anywhere             anywhere
+ACCEPT     all  --  anywhere             anywhere
 ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
 
 Chain FORWARD (policy ACCEPT)
-target     prot opt source               destination         
+target     prot opt source               destination
 
 Chain OUTPUT (policy ACCEPT)
-target     prot opt source               destination 
+target     prot opt source               destination
 ....
 
 The number given after the chain name indicates the position *before* an
@@ -184,18 +185,18 @@ from the network address range 192.168.0.0/24:
 [root@server ~]# iptables -R INPUT 1 -p tcp -s 192.168.0.0/24 --dport 80 -j ACCEPT
 [root@server ~]# iptables -L
 Chain INPUT (policy DROP)
-target     prot opt source               destination         
+target     prot opt source               destination
 ACCEPT     tcp  --  192.168.0.0/24       anywhere             tcp dpt:http
 ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
-ACCEPT     icmp --  anywhere             anywhere            
-ACCEPT     all  --  anywhere             anywhere            
+ACCEPT     icmp --  anywhere             anywhere
+ACCEPT     all  --  anywhere             anywhere
 ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
 
 Chain FORWARD (policy ACCEPT)
-target     prot opt source               destination         
+target     prot opt source               destination
 
 Chain OUTPUT (policy ACCEPT)
-target     prot opt source               destination 
+target     prot opt source               destination
 ....
 
 [[flushing-rules]]
@@ -227,8 +228,8 @@ reboot. However, iptables comes with two useful utilities:
 These may be redirected to a file:
 
 ....
-[root@server ~]# iptables-save > iptables.dump 
-[root@server ~]# cat iptables.dump 
+[root@server ~]# iptables-save > iptables.dump
+[root@server ~]# cat iptables.dump
 # Generated by iptables-save v1.4.12 on Wed Dec  7 20:10:49 2011
 *filter
 :INPUT DROP [45:2307]
@@ -245,17 +246,17 @@ COMMIT
 * iptables-restore : restore a dump of rules made by iptables-save.
 
 ....
-[root@server ~]# iptables-restore < iptables.dump 
+[root@server ~]# iptables-restore < iptables.dump
 [root@server ~]# iptables -L
 Chain INPUT (policy DROP)
-target     prot opt source               destination         
+target     prot opt source               destination
 ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
-ACCEPT     icmp --  anywhere             anywhere            
-ACCEPT     all  --  anywhere             anywhere            
+ACCEPT     icmp --  anywhere             anywhere
+ACCEPT     all  --  anywhere             anywhere
 ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:ssh
 
 Chain FORWARD (policy ACCEPT)
-target     prot opt source               destination         
+target     prot opt source               destination
 
 Chain OUTPUT (policy ACCEPT)
 target     prot opt source               destination

modules/ROOT/pages/enable-touchpad-click.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 [[scope]]
 == Scope

modules/ROOT/pages/encrypting-drives-using-LUKS.adoc

@@ -4,6 +4,8 @@ ifdef::context[:parent-context: {context}]
 [id='encrypting-drives-using-luks']
 = Encrypting drives using LUKS
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 As a system administrator, you can encrypt a block device. This section gives a brief introduction to block encryption, describes Linux Unified Key Setup (LUKS), and lists the steps to create an encrypted block device.
 
 :leveloffset: +1

modules/ROOT/pages/fedora-and-red-hat-enterprise-linux.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='fedora-and-red-hat-enterprise-linux']
 = Fedora and Red Hat Enterprise Linux
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 What is the difference between Fedora and Red Hat Enterprise Linux?
 
 include::{partialsdir}/con_relation-between-fedora-and-red-hat-enterprise-linux.adoc[leveloffset=+1]

modules/ROOT/pages/fedora-life-cycle.adoc

@@ -1,5 +1,7 @@
 = Fedora Release Life Cycle
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 ////
 The Fedora Project releases a new version of Fedora approximately every 6 months and provides updated packages (maintenance) to these releases for approximately 13 months. This allows users to "skip a release" while still being able to always have a system that is still receiving updates.
 

modules/ROOT/pages/finding-and-installing-linux-applications.adoc

@@ -5,18 +5,20 @@ ifdef::context[:parent-context: {context}]
 [[finding-and-installing-linux-applications]]
 = Finding and installing Linux applications
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Many powerful software applications are available on the Linux operating system. You can find alternatives to most of the popular applications used on other systems.
 
 You can use the Fedora package management system to install applications. Many applications are available from the repository provided by the Fedora project. You can enable other repositories to get additional applications.
 
 include::{partialsdir}/con_package-management-in-fedora.adoc[leveloffset=+1]
 
-include::{partialsdir}/proc_package-searching-web-apps.adoc[leveloffset=+1] 
+include::{partialsdir}/proc_package-searching-web-apps.adoc[leveloffset=+1]
 
-include::{partialsdir}/proc_package-browsing-installing-software.adoc[leveloffset=+1] 
+include::{partialsdir}/proc_package-browsing-installing-software.adoc[leveloffset=+1]
 
-include::{partialsdir}/proc_package-install-command-line.adoc[leveloffset=+1] 
+include::{partialsdir}/proc_package-install-command-line.adoc[leveloffset=+1]
 
-include::{partialsdir}/proc_package-enabling-third-party.adoc[leveloffset=+1] 
+include::{partialsdir}/proc_package-enabling-third-party.adoc[leveloffset=+1]
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]

modules/ROOT/pages/firewalld.adoc

@@ -6,6 +6,8 @@ ifdef::context[:parent-context: {context}]
 [[using-firewalld]]
 = Using firewalld
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 :leveloffset: +1
 
 include::{partialsdir}/con_firewalld.adoc[]

modules/ROOT/pages/getting-started-with-apache-http-server.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='getting-started-with-apache-http-server']
 = Getting started with Apache HTTP Server
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 The Apache HTTP Server is one of the most commonly-used web servers. This section acts as a quick-start guide to deploying and configuring Apache on Fedora.
 
 include::{partialsdir}/proc_installing-httpd.adoc[leveloffset=+1]

modules/ROOT/pages/getting-started-with-selinux.adoc

@@ -7,6 +7,8 @@ ifdef::context[:parent-context: {context}]
 :md: en-US/modules
 :imagesdir: ./images
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 :leveloffset: +1
 include::{partialsdir}/con_introduction-to-selinux.adoc[]
 include::{partialsdir}/con_benefits-of-selinux.adoc[]

modules/ROOT/pages/getting-started-with-virtualization.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='getting-started-with-virtualization']
 = Getting started with virtualization
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Fedora uses the libvirt family of tools as its virtualization solution.
 
 include::{partialsdir}/proc_enabling-hardware-virtualization-support.adoc[leveloffset=+1]

modules/ROOT/pages/howto-file-a-bug.adoc

@@ -1,6 +1,8 @@
 = How to file a bug
 :imagesdir: ./images
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 The purpose of this document is to give step by step instructions on filing bugs in Fedora.
 
 A software bug does not necessarily need to be a software crash. Any undesired behaviour noticed in software should be filed as a bug.

modules/ROOT/pages/installing-and-running-vlc.adoc

@@ -9,6 +9,8 @@ ifdef::context[:parent-context: {context}]
 
 include::{partialsdir}/3rdparty-message.adoc[]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 :leveloffset: +1
 
 include::{partialsdir}/proc_installing_vlc.adoc[]

modules/ROOT/pages/installing-chromium-or-google-chrome-browsers.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 
 include::{partialsdir}/3rdparty-message.adoc[]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/concept_chromium-web-browser.adoc[leveloffset=+1]
 
 include::{partialsdir}/proc_installing-chromium-web-browser.adoc[leveloffset=+1]

modules/ROOT/pages/installing-grub2.adoc

@@ -6,10 +6,12 @@ ifdef::context[:parent-context: {context}]
 = Bootloading with *GRUB2*
 [[bootloading-with-grub2]]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 *GRUB2* is the latest version of *GNU GRUB*, the _GRand Unified Bootloader_.
 A bootloader is the first software program that runs when a computer
 starts. It is responsible for loading and transferring control to the
-operating system kernel. In Fedora, the kernel is Linux. The kernel then initializes 
+operating system kernel. In Fedora, the kernel is Linux. The kernel then initializes
 the rest of the operating system.
 
 *GRUB2* is the follower of the previous version *GRUB* (version 0.9x). The original version is available under the name *GRUB Legacy*.
@@ -28,4 +30,3 @@ include::{partialsdir}/proc_adding-other-operating-systems-grub2.adoc[leveloffse
 
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]
-

modules/ROOT/pages/installing-java.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id="assembly_installing-java"]
 = Installing Java
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Java provides a platform for creating and running applications. You can install various versions of Java to suit your requirements.
 
 include::{partialsdir}/con_about-java.adoc[leveloffset=+1]

modules/ROOT/pages/installing-spotify.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 
 include::{partialsdir}/3rdparty-message.adoc[]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 link:https://www.spotify.com/[Spotify] is a cross-platform proprietary music streaming service.
 Spotify is a freemium service, with advertisements which can be removed by purchasing a subscription.
 Although Spotify is not officially supported on Fedora, it can be installed on Fedora in a number of ways:

modules/ROOT/pages/installing-virtual-systems-with-gnome-boxes.adoc

@@ -6,6 +6,8 @@ ifdef::context[:parent-context: {context}]
 :md: en-US/modules
 :imagesdir: ../images
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 GNOME Boxes is an application in GNOME Desktop Environment, which enables you to virtually access various operating systems.
 
 :leveloffset: +1

modules/ROOT/pages/kernel/build-custom-kernel.adoc

@@ -1,5 +1,8 @@
 [[ch-build-custom-kernel]]
 = Building a Custom Kernel
+
+include::{partialsdir}/unreviewed-message.adoc[]
+
 :toc:
 
 This document provides instructions for advanced users who want to rebuild the

modules/ROOT/pages/kernel/overview.adoc

@@ -1,4 +1,7 @@
 = Fedora Linux Kernel Overview
+
+include::{partialsdir}/unreviewed-message.adoc[]
+
 :toc:
 
 [[section-update-schedule]]

modules/ROOT/pages/kernel/troubleshooting.adoc

@@ -1,5 +1,7 @@
 = Troubleshooting
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 The kernel, like any software, has bugs. It's a large, complex project and it
 can be difficult to troubleshoot problems. This document covers some basic
 troubleshooting techniques to help narrow down the root cause of an issue.

modules/ROOT/pages/managing-keyboard-shortcuts-for-running-app-in-gnome.adoc

@@ -7,6 +7,8 @@ ifdef::context[:parent-context: {context}]
 
 :md: en-US/modules
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 :leveloffset: +1
 
 include::{partialsdir}/proc_adding-shortcut-custom-app-gnome.adoc[]

modules/ROOT/pages/mirroring.adoc

@@ -31,7 +31,7 @@ with the following macro:
 
 '''
 
-
+include::{partialsdir}/unreviewed-message.adoc[]
 
 '''
 

modules/ROOT/pages/openh264.adoc

@@ -31,6 +31,8 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 
 This page contains information on the Cisco
 http://www.openh264.org/[OpenH264] codec.

modules/ROOT/pages/package-management.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 [[package-management-system]]
 Package Management System

modules/ROOT/pages/packagekit-not-found.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 [[missing-package]]
 == Missing Package

modules/ROOT/pages/performing-administration-tasks-using-sudo.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='performing-administration-tasks-using-sudo']
 = Performing administration tasks using sudo
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 How to perform tasks requiring *root* privileges without logging in as *root*.
 
 include::{partialsdir}/con_what-is-sudo.adoc[leveloffset=+1]

modules/ROOT/pages/postgresql.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 [[installation]]
 == Installation

modules/ROOT/pages/proc_installing-RPM.adoc

@@ -1,6 +1,8 @@
 [id='proc_installing-an-RPM-file']
 = Installing an RPM File
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This procedure shows you how to install an RPM file after you have downloaded the file to your desktop. An RPM file contains the required installation packages for a software.
 
 ._Prerequisites_

modules/ROOT/pages/proc_setting-key-shortcut.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [id='setting-key-shortcut_{context}']
 = Setting a key shortcut to run an application in GNOME
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 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.

modules/ROOT/pages/qemu.adoc

@@ -1,5 +1,7 @@
 = How to use QEMU
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 QEMU is a very flexible virtualization technology however it is quite slow and it is recommended that you understand and evaluate alternative solutions before picking this one.
 Refer to https://fedoraproject.org/wiki/Getting_started_with_virtualization[Getting started with virtualization]
 

modules/ROOT/pages/raspberry-pi.adoc

@@ -19,6 +19,8 @@
 :context: rpi
 // 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.
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 The link:https://www.raspberrypi.org[Raspberry Pi] is a credit card-sized ARM based single board computer (SBC).
 The Raspberry Pi Model B versions 2 and 3 are supported for Fedora 25 or newer, without any requirement of third party kernels or scripts to adjust offical images.
 This documentation describes how to get started, and includes a Frequently Asked Questions (FAQ) section at the end of the document about what is supported, and what is not.

modules/ROOT/pages/repositories.adoc

@@ -1,6 +1,8 @@
 = Repositories
-:FedoraVersionNumberNext: 28
-:FedoraVersionNumber: 27
+:FedoraVersionNumberNext: 30
+:FedoraVersionNumber: 29
+
+include::{partialsdir}/unreviewed-message.adoc[]
 
 This page explains the various Fedora repositories that exist for
 different Fedora Releases, the relationship between them, and what

modules/ROOT/pages/reset-root-password.adoc

@@ -1,6 +1,8 @@
 [[chap-how-to-reset-a-root-password]]
 = How to Reset the root Password
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Setting up a root password is one of the steps when installing Fedora.
 If you forget, or lose, the root password, there are two common methods to reset it:
 
@@ -120,7 +122,7 @@ To mount root on a *standard partition* scheme enter:
 
 ----
 
-mount /dev/sda2 /mnt/sysimage 
+mount /dev/sda2 /mnt/sysimage
 
 ----
 +
@@ -197,4 +199,4 @@ Congratulations, your root password has been successfully changed.
 
 . If you have set a password for your boot loader, refer to link:++creating-and-using-a-live-installation-image.html++[Creating and Using a Live Installation Image].
 
-. If you want to reset the boot loader password, refer to the instructions on how to link:++https://fedoraproject.org/wiki/Reset_Bootloader_Password++[Reset the Bootloader Password].
+. If you want to reset the boot loader password, refer to the instructions on how to link:++https://fedoraproject.org/wiki/Reset_Bootloader_Password++[Reset the Bootloader Password].

modules/ROOT/pages/securing-the-system-by-keeping-it-up-to-date.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 [id='securing-the-system-by-keeping-it-up-to-date']
 = Securing the system by keeping it up-to-date
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This section explains:
 
 * Why it is important to update your system regularly (link:#why-it-is-important-keeping-your-system-up-to-date[Why it is important to keep your system up-to-date])

modules/ROOT/pages/switching-desktop-environments.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 [[switching-desktop-environments]]
 = Switching desktop environments
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Fedora's default desktop environment is GNOME 3 in the Workstation spin, but it is very easy to try any of the many other desktop environments that are available without affecting your current desktop environment.
 
 include::{partialsdir}/proc_installing-additional-desktop-enviroments.adoc[leveloffset=+1]

modules/ROOT/pages/troubleshooting_selinux.adoc

@@ -4,6 +4,8 @@ ifdef::context[:parent-context: {context}]
 [id='prod_troubleshooting_selinux']
 = Troubleshooting SELinux
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 This document covers the basics of troubleshooting SELinux.
 
 SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. For example, an SELinux error generated by the Apache web server may appear as `comm="/usr/sbin/httpd"`.

modules/ROOT/pages/uefi-with-qemu.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 [[firmware-installation]]
 Firmware installation

modules/ROOT/pages/understanding-and-administering-systemd.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 [id='understanding-and-administering-systemd']
 = Understanding and administering systemd
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Learn the basic principles of systemd: how to configure it and use to administer the system.
 
 include::{partialsdir}/con_understanding-systemd.adoc[leveloffset=+1]

modules/ROOT/pages/upgrading-fedora-online.adoc

@@ -31,6 +31,7 @@ with the following macro:
 
 '''
 
+include::{partialsdir}/unreviewed-message.adoc[]
 
 This page contains information explaining how to upgrade Fedora online
 using (without the DNF system upgrade plugin).
@@ -119,7 +120,7 @@ A small script named fedora-upgrade is available which aims to automate
 the process outlined below. To run it, do the following
 
 ....
-$ sudo dnf install fedora-upgrade 
+$ sudo dnf install fedora-upgrade
 $ sudo fedora-upgrade
 ....
 

modules/ROOT/pages/upgrading.adoc

@@ -1,6 +1,8 @@
 [[ch-Upgrading]]
 = Upgrading to a new release of Fedora
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 [IMPORTANT]
 ====
 

modules/ROOT/pages/using-adobe-flash.adoc

@@ -5,6 +5,8 @@ ifdef::context[:parent-context: {context}]
 
 include::{partialsdir}/3rdparty-message.adoc[]
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/con_what_is_adobe_flash.adoc[leveloffset=+1]
 
 include::{partialsdir}/proc_checking_fedora_version.adoc[leveloffset=+1]

modules/ROOT/pages/using-aide.adoc

@@ -1,6 +1,8 @@
 [id='sec-Using-AIDE']
 = Checking Integrity With *AIDE*
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Advanced Intrusion Detection Environment (AIDE) is a utility that creates a database of files on the system, and then uses that database to ensure file integrity and detect system intrusions.
 
 == Installing *AIDE*

modules/ROOT/pages/using-nested-virtualization-in-kvm.adoc

@@ -2,6 +2,8 @@ ifdef::context[:parent-context: {context}]
 :context: using-nested-virtiualization-in-kvm
 = How to enable nested virtualization in KVM
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 Learn how to run a virtual machine within a virtual machine.
 
 include::{partialsdir}/proc_enabling-nested-virtualization-in-kvm.adoc[leveloffset=+1]

modules/ROOT/pages/using-shared-system-certificates.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 [[using-shared-system-certificates]]
 = Using Shared System Certificates
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 The Shared System Certificates storage enables NSS, GnuTLS, OpenSSL, and Java to share a default source for retrieving system certificate anchors and black list information. By default, the trust store contains the Mozilla CA list, including positive and negative trust. The system allows updating of the core Mozilla CA list or choosing another certificate list.
 
 include::{partialsdir}/con_using-the-system-wide-trust-store.adoc[leveloffset=+1]

modules/ROOT/pages/viewing-logs.adoc

@@ -3,6 +3,8 @@ ifdef::context[:parent-context: {context}]
 
 = Viewing logs in Fedora
 
+include::{partialsdir}/unreviewed-message.adoc[]
+
 include::{partialsdir}/con_viewing-logs.adoc[leveloffset=+1]
 
 include::{partialsdir}/proc_log-files-command-line.adoc[leveloffset=+1]

modules/ROOT/pages/wine.adoc

@@ -1,6 +1,6 @@
 = Wine
 
-
+include::{partialsdir}/unreviewed-message.adoc[]
 
 http://winehq.org/[Wine] is an open source implementation of the Windows
 API on top of X and OpenGL.