Update Mock reference url

source/advanced-topics.adoc

@@ -212,7 +212,7 @@ ifdef::community[]
 [[mock]]
 == Mock
 
-https://github.com/rpm-software-management/mock/wiki[Mock] is a tool for
+https://rpm-software-management.github.io/mock[Mock] is a tool for
 building packages. It can build packages for different architectures and
 different Fedora or RHEL versions than the build host has. Mock creates chroots
 and builds packages in them. Its only task is to reliably populate a chroot and
@@ -225,14 +225,14 @@ Mock is capable of building SRPMs from source configuration management if the
 `mock-scm` package is present, then building the SRPM into RPMs. See –scm-enable
 in the documentation. (From the upstream documentation)
 
-NOTE: In order to use https://github.com/rpm-software-management/mock/wiki[Mock]
+NOTE: In order to use https://rpm-software-management.github.io/mock[Mock]
 on a RHEL or CentOS system, you will need to enable the “Extra Packages for
 Enterprise Linux” (https://fedoraproject.org/wiki/EPEL[EPEL]) repository. This
 is a repository provided by the https://getfedora.org/[Fedora] community and has
 many useful tools for RPM Packagers, systems administrators, and developers.
 
 One of the most common use cases RPM Packagers have for
-https://github.com/rpm-software-management/mock/wiki[Mock] is to create what is
+https://rpm-software-management.github.io/mock[Mock] is to create what is
 known as a “pristine build environment”. By using mock as a “pristine build
 environment”, nothing about the current state of your system affects the RPM
 Package itself. Mock uses different configurations to specify what the build
@@ -262,7 +262,7 @@ forgot to actually make the ``BuildRequires: foo`` entry. The build would
 succeed when you run ``rpmbuild`` because ``foo`` was needed to build and it was
 found on the system at build time. However, if you took the SRPM to another
 system that lacked ``foo`` it would fail, causing an unexpected side effect.
-https://github.com/rpm-software-management/mock/wiki[Mock] solves this by first
+https://rpm-software-management.github.io/mock[Mock] solves this by first
 parsing the contents of the SRPM and installing the ``BuildRequires`` into its
 https://en.wikipedia.org/wiki/Chroot[chroot] which means that if you were
 missing the ``BuildRequires`` entry, the build would fail because `mock` would
@@ -271,7 +271,7 @@ not know to install it and it would therefore not be present in the buildroot.
 Another example is the opposite scenario, let’s say you need ``gcc`` to build a
 package but don’t have it installed on your system (which is unlikely as an RPM
 Packager, but just for the sake of the example let us pretend that is true).
-With https://github.com/rpm-software-management/mock/wiki[Mock], you don’t have
+With https://rpm-software-management.github.io/mock[Mock], you don’t have
 to install ``gcc`` on your system because it will get installed in the chroot as
 part of `mock`’s process.
 
@@ -417,7 +417,7 @@ mock target, such as ``mock -r epel-7-x86_64 --init`` which will pre-download
 all the required packages, cache them, and pre-stage the build chroot.
 
 For more information, please consult the
-https://github.com/rpm-software-management/mock/wiki[Mock] upstream
+https://rpm-software-management.github.io/mock[Mock] upstream
 documentation.
 endif::community[]