remove /content from relref paths

content/CORE/CORETutorials/Network/IPMI.md

@@ -12,7 +12,7 @@ tags:
 IPMI requires compatible hardware! Refer to your hardware documentation. Hardware compatibility determines if the IPMI option displays in the TrueNAS web interface.
 {{< /hint >}}
 
-Many [TrueNAS Storage Arrays]({{< relref "/Content/Hardware/_index.md" >}}) provide a built-in out-of-band management port. If the system becomes unavailable through the web interface, you can use this port to provide side-band management. Use IPMI to perform several vital functions. These include checking the log, accessing the BIOS setup, and powering on the system. IPMI does not need physical access to the system.  You can use it to allow another person remote access to the system. This is useful when investigating a configuration or troubleshooting issue.
+Many [TrueNAS Storage Arrays]({{< relref "/Hardware/_index.md" >}}) provide a built-in out-of-band management port. If the system becomes unavailable through the web interface, you can use this port to provide side-band management. Use IPMI to perform several vital functions. These include checking the log, accessing the BIOS setup, and powering on the system. IPMI does not need physical access to the system.  You can use it to allow another person remote access to the system. This is useful when investigating a configuration or troubleshooting issue.
 
 {{< hint type=note >}}
 Some IPMI implementations need updates to work with newer versions of Java. 

content/CORE/CORETutorials/SettingUpUsersAndGroups.md

@@ -18,7 +18,7 @@ Only the root user account can log in to the TrueNAS web interface.
 {{< /hint >}}
 
 When the network uses a directory service, import the existing account information using the instructions in [Directory Services](https://www.truenas.com/docs/core/coretutorials/directoryservices/).
-Using [Active Directory]({{< relref "/content/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md" >}}) requires setting Windows user passwords inside Windows.
+Using [Active Directory]({{< relref "/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md" >}}) requires setting Windows user passwords inside Windows.
 
 To see user accounts, go to **Accounts > Users**.
 
@@ -78,7 +78,7 @@ The account can't use password-based logins for services.
 For example, disabling the password prevents using account credentials to log in to an SMB share or open an SSH session on the system.
 By default, **Disable Password** is *No*.
 
-You can set a specific [shell]({{< relref "ChangingDefaultShell.md" >}})  for the user from the **Shell** dropdown:
+You can set a specific [shell]({{< relref "ChangingDefaultShell.md" >}}) for the user from the **Shell** dropdown:
 
 {{< expand "Shell Options" "v" >}}
 {{< include file="archive/COREshellOptions.md" >}}
@@ -98,7 +98,7 @@ It allows users to access [SMB]({{< relref "/CORE/CORETutorials/Sharing/SMB/_ind
 
 Using groups in TrueNAS is an efficient way to manage permissions for many similar user accounts.
 The interface lets you manage UNIX-style groups.
-If the network uses a directory service, import the existing account information using the instructions in [Active Directory]({{< relref "/content/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md" >}}).
+If the network uses a directory service, import the existing account information using the instructions in [Active Directory]({{< relref "/CORE/CORETutorials/DirectoryServices/ActiveDirectory.md" >}}).
 
 ### View Existing Groups
 

content/CORE/CORETutorials/Storage/Pools/ManagingPools.md

@@ -80,7 +80,7 @@ Increases the size of the pool to match all available disk space.
 This option is typically used when virtual disks are resized apart from TrueNAS.
 {{< /expand >}}
 {{< expand "Upgrade Pool" >}}
-This option only displays when the pool can be upgraded to use new [ZFS feature flags]({{< relref "/content/References/ZFSPrimer.md" >}}).
+This option only displays when the pool can be upgraded to use new [ZFS feature flags]({{< relref "/References/ZFSPrimer.md" >}}).
 Before upgrading an existing pool, be aware of these caveats:
 
 * Upgrading a pool is one-way. This means that if you change your mind. 

content/CORE/CORETutorials/Storage/Pools/_index.md

@@ -85,11 +85,11 @@ Do not have multiple data vdevs with different numbers of disks in each vdev as
 {{< /hint >}}
 {{< /expand >}}
 {{< expand "Cache" >}}
-[ZFS L2ARC]({{< relref "/Content/References/L2ARC.md" >}}) read-cache is used with fast devices to accelerate read operations.
+[ZFS L2ARC]({{< relref "/References/L2ARC.md" >}}) read-cache is used with fast devices to accelerate read operations.
 You can add or remove this after creating the pool.
 {{< /expand >}}
 {{< expand "Log" >}}
-[ZFS LOG]({{< relref "/Content/References/SLOG.md" >}}) is a device that improves synchronous write speeds.
+[ZFS LOG]({{< relref "/References/SLOG.md" >}}) is a device that improves synchronous write speeds.
 You can add or remove this after creating the pool.
 {{< /expand >}}
 {{< expand "Hot Spare" >}}
@@ -104,7 +104,7 @@ When the failed drive is only detached from the pool, the temporary hot spare is
 Metadata vdevs are a special allocation class used to create [Fusion Pools]({{< relref "/CORE/CORETutorials/Storage/Pools/FusionPool.md" >}}) for increased metadata and small block I/O performance.
 {{< /expand >}}
 {{< expand "Dedup" >}}
-**Dedup** vdevs store [ZFS de-duplication]({{< relref "/Content/References/ZFSDeduplication.md" >}}).
+**Dedup** vdevs store [ZFS de-duplication]({{< relref "/References/ZFSDeduplication.md" >}}).
 Requires allocating *X* GiB for every *X* TiB of general storage.
 For example, 1 GiB of dedup vdev capacity for every 1 TiB of data vdev availability.
 {{< /expand >}}

content/CORE/CORETutorials/Tasks/CreatingCloudSyncTasks.md

@@ -27,7 +27,7 @@ iXsystems is not responsible for any charges incurred from the use of third part
 Transferring data from TrueNAS to the Cloud requires saving Cloud Storage Provider credentials on the system.
 
 To maximize security, TrueNAS encrypts credentials after saving.
-However, this means that to restore any cloud credentials from a TrueNAS configuration file, you must enable **Export Password Secret Seed** when generating that [configuration backup]({{< relref "/content/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md" >}}).
+However, this means that to restore any cloud credentials from a TrueNAS configuration file, you must enable **Export Password Secret Seed** when generating that [configuration backup]({{< relref "/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md" >}}).
 Remember to protect any downloaded TrueNAS configuration files.
 
 Go to **System > Cloud Credentials** and click **ADD**.

content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingSoftwareforaMajorVersion.md

@@ -18,7 +18,7 @@ TrueNAS provides flexibility for keeping the operating system up-to-date:<br>
    Boot environments provide the option to return to the previous version of the operating system by rebooting the system and selecting the previous boot environment from the **System > Boot** menu.
 
 The [upgrade instructions](#upgrade-via-iso) instructions describe how to use an <file>.iso</file> file to perform a major version upgrade from an earlier version of FreeNAS/TrueNAS.
-See the [Updating CORE]({{< relref "/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingCORE.md" >}}) or [Updating Enterprise]({{< relref "/content/CORE/CORETutorials/UpdatingTrueNAS/UpdatingENTERPRISE.md" >}}) articles for instructions about using the web interface to keep the system updated.
+See the [Updating CORE]({{< relref "/CORE/CORETutorials/UpdatingTrueNAS/UpdatingCORE.md" >}}) or [Updating Enterprise]({{< relref "/CORE/CORETutorials/UpdatingTrueNAS/UpdatingENTERPRISE.md" >}}) articles for instructions about using the web interface to keep the system updated.
 
 The upgrade path for major versions of FreeNAS/TrueNAS is **9.3 > 9.10 > 11.1 > 11.3 > 12.0**.
 We always recommend upgrading to a [supported version]({{< relref "/CORE/GettingStarted/UserAgreements/SofDevLifecycle.md" >}}) of the software.

content/CORE/UIReference/DirectoryServices/NISScreen.md

@@ -11,7 +11,7 @@ Use the **Directory Services > NIS** screen to configure [Network Information Se
 
 {{< hint type=important >}}
 NIS is limited in scalability and security.
-For modern networks, [LDAP]({{< relref "/content/CORE/UIReference/DirectoryServices/LDAPScreen.md" >}}) has replaced NIS.
+For modern networks, [LDAP]({{< relref "/CORE/UIReference/DirectoryServices/LDAPScreen.md" >}}) has replaced NIS.
 {{< /hint >}}
 
 ![DirectoryServicesNIS](/images/CORE/DirectoryServices/DirectoryServicesNIS.png)

content/CORE/UIReference/System/Advanced.md

@@ -10,7 +10,7 @@ tags:
 
 {{< hint type=important >}}
 These options have reasonable defaults in place.
-Make sure you are comfortable with ZFS, FreeBSD, and system [configuration backup and restoration]({{< relref "/content/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md" >}}) before making any changes.
+Make sure you are comfortable with ZFS, FreeBSD, and system [configuration backup and restoration]({{< relref "/CORE/CORETutorials/SystemConfiguration/UsingConfigurationBackups.md" >}}) before making any changes.
 {{< /hint >}}
 
 ![System Advanced13](/images/CORE/System/SystemAdvanced13.png "Advanced Settings")

content/References/ConceptsAndTerms.md

@@ -54,15 +54,15 @@ While TrueNAS is designed for and ever-evolving towards increased user friendlin
 
 * **Self-Encrypting Drive (SED)**: A SED (or Self-Encrypting Drive) is a hard drive that automatically and continuously encrypts the data on the drive without any user action.
 
-* [**Zettabyte File System (ZFS)**]({{< relref "/content/references/ZFSPrimer.md" >}}): ZFS is a next-generation file system designed by Sun Microsystems that eliminates most, if not all of the shortcomings found in legacy file systems and hardware RAID devices.
+* [**Zettabyte File System (ZFS)**]({{< relref "/references/ZFSPrimer.md" >}}): ZFS is a next-generation file system designed by Sun Microsystems that eliminates most, if not all of the shortcomings found in legacy file systems and hardware RAID devices.
 
 * **iSCSI**: iSCSI stands for Internet Small Computer Systems Interface.
   iSCSI is a transport layer protocol that works on top of the Transport Control Protocol (TCP).
   It provides block-level access to storage devices by carrying SCSI commands over a TCP/IP network.
 
 ### ZFS
 
-* [**L2ARC**]({{< relref "/content/references/L2ARC.md" >}}): sometimes called a CACHE vdev.
+* [**L2ARC**]({{< relref "/references/L2ARC.md" >}}): sometimes called a CACHE vdev.
   This is a special class of vdev.
   ARC stands for Adaptive Replacement Cache and is a caching algorithm that tracks both the blocks in cache and blocks recently evicted from cache.
   The main ARC resides in system memory.
@@ -74,7 +74,7 @@ While TrueNAS is designed for and ever-evolving towards increased user friendlin
 
 * [**ZFS Pools**]({{< relref "CORE/CORETutorials/Storage/Pools/_index.md" >}}): filesystem container that is composed of one or more vdevs.
 
-* [**ZFS vdev**]({{< relref "/content/references/ZFSPrimer.md" >}}): ZFS virtual device.
+* [**ZFS vdev**]({{< relref "/references/ZFSPrimer.md" >}}): ZFS virtual device.
   A ZFS pool is made up by one or more vdevs.
   A vdev can be created using a single disk or many.
   A vdev has many configurations: single disk, stripe, RAIDz1, RAIDz2, RAIDz3, or mirror.

content/References/ZFSDeduplication.md

@@ -21,7 +21,7 @@ ZFS keeps a reference table which links files and pool data to the actual storag
 
 The DDT is a fundamental ZFS structure. It is treated as part of the metadata or the pool. 
 If a pool (or any dataset in the pool) has ever contained deduplicated data, the pool contains a DDT, and that DDT is as fundamental to the pool data as any of its other file system tables. 
-Like any other metadata, DDT contents might be temporarily held in the ARC (RAM/memory cache) or [L2ARC]({{< relref "/content/references/L2ARC.md" >}}) (disk cache) for speed and repeated use, but the DDT is not a disk cache. 
+Like any other metadata, DDT contents might be temporarily held in the ARC (RAM/memory cache) or [L2ARC]({{< relref "/references/L2ARC.md" >}}) (disk cache) for speed and repeated use, but the DDT is not a disk cache. 
 It is a fundamental part of the ZFS pool structure, how ZFS organizes pool data on its disks. 
 Therefore like any other pool data, if DDT data is lost, the pool is likely to become unreadable. So it is important it is stored on redundant devices. 
 

content/Solutions/Integrations/VMware/DeployTNinVMWare.md

@@ -19,13 +19,13 @@ Before starting configuration work in VMWare:
 
 * Download the <file>.iso</file> file from the TrueNAS.com downloads page for TrueNAS [SCALE](https://www.truenas.com/download-truenas-scale/) or [CORE](https://www.truenas.com/download-truenas-core/).
 
-* Visit the TrueNAS [SCALE]({{< relref "/content/SCALE/GettingStarted/Configure/SetUpStorageScale.md" >}}) or [CORE]({{< relref "/content/core/gettingstarted/corehardwareguide.md" >}}) Hardware Guide and take note of the minimal system requirements.
+* Visit the TrueNAS [SCALE]({{< relref "/SCALE/GettingStarted/Configure/SetUpStorageScale.md" >}}) or [CORE]({{< relref "/core/gettingstarted/corehardwareguide.md" >}}) Hardware Guide and take note of the minimal system requirements.
   Also note the information in the **Memory** and **Storage Device Sizing** sections.
 
   The hardware guide provides guidance on how much memory, the number of CPUs, and drive size you need to configure.
 
 * Determine your data storage requirements. Consider the number of storage pools and the type of storage you need for your deployment or how you plan to use the TrueNAS.
-  See the SCALE [Setting Up Storage]({{< relref "/content/CORE/GettingStarted/StoringData.md" >}}) or CORE [Storage Configuration]({{< relref "/content/CORE/GettingStarted/StoringData.md" >}}) for information on pool layouts.
+  See the SCALE [Setting Up Storage]({{< relref "/CORE/GettingStarted/StoringData.md" >}}) or CORE [Storage Configuration]({{< relref "/CORE/GettingStarted/StoringData.md" >}}) for information on pool layouts.
 
   These articles provide guidance on the number of virtual hard drives (vmdks) you want to create when setting up your virtual machine.
   For example, if you want a mirror layout you need to add a minimum of three drives, one for the boot drive and two for the mirrored storage.
@@ -147,7 +147,7 @@ To create the virtual machine for your TrueNAS, from the **Virtual Machines** sc
    Click **Next** to finish creating the VM. You can use the **Edit** option later to add more drives to support your TrueNAS deployment.
 
    Each storage layout has different disk minimum disk requirements.
-   See the SCALE [Setting Up Storage]({{< relref "/content/CORE/GettingStarted/StoringData.md" >}}) or CORE [Storage Configuration]({{< relref "/content/CORE/GettingStarted/StoringData.md" >}}) for information on pool layouts.
+   See the SCALE [Setting Up Storage]({{< relref "/CORE/GettingStarted/StoringData.md" >}}) or CORE [Storage Configuration]({{< relref "/CORE/GettingStarted/StoringData.md" >}}) for information on pool layouts.
 
 6. Review the **Ready to Complete** screen to verify the settings are correct for your deployment.
 
@@ -173,7 +173,7 @@ When the console opens, it displays the TrueNAS Console Setup screen.
 
 {{< trueimage src="/images/VMWareESXi/TrueNASConsoleSetup.png" alt="TrueNAS Console Setup" id="TrueNAS Console Setup" >}}
 
-Follow the installation instructions documented for [SCALE]({{< relref "/content/SCALE/GettingStarted/Install/InstallingSCALE.md #using-the-truenas-installer" >}}) or [CORE]({{< relref "/content/CORE/GettingStarted/Install.md #install-process" >}}) to complete the installation of TrueNAS.
+Follow the installation instructions documented for [SCALE]({{< relref "/SCALE/GettingStarted/Install/InstallingSCALE.md #using-the-truenas-installer" >}}) or [CORE]({{< relref "/CORE/GettingStarted/Install.md #install-process" >}}) to complete the installation of TrueNAS.
 
 ## Editing the Virtual Machine