Move and improve guide to manage custom terms type

Author: Ndpnt

content/collections/how-to/manage-custom-terms-type.md renamed to content/terms/how-to/manage-custom-terms-type.md

@@ -1,18 +1,25 @@
 ---
 title: Manage a custom terms type
-weight: 6
+weight: 4
 ---
 
 # How to manage a custom terms type
 
-When tracking terms and conditions across different services, you might encounter situations where a service uses terms types that aren't yet supported by Open Terms Archive.
+When tracking terms and conditions across different services, you might encounter situations where a service uses terms types that aren't yet supported by Open Terms Archive. 
+
 This guide will help you handle these custom terms types effectively, whether you're working on a new collection or expanding an existing one.
 
+_To better understand what terms types are and how they work, you can read our [detailed explanation]({{< relref "terms/explanation/terms-types" >}})._
+
 ## Prerequisites
 
 Before proceeding with using a custom terms type, please double-check that the type you're considering doesn't already exist in the supported terms types list. Different services often use different names for the same type of terms. For instance, "Terms and Conditions" might be called "Terms of Use" or "Terms of Service" by different services.
 
-Review the [supported types list](https://github.com/OpenTermsArchive/terms-types/blob/main/termsTypes.json) carefully to ensure the terms type you want to track is not already supported under a different name. If it does, use the associated type in your declaration. If you are sure it's not supported, you can proceed with the following steps. If you're unsure, you can ask for help in the [Open Terms Archive community]({{< relref "community/how-to/join" >}}).
+Review the [supported types list](https://github.com/OpenTermsArchive/terms-types/blob/main/termsTypes.json) carefully to ensure the terms type you want to track is not already supported under a different name:
+
+- If it does, use the associated type in your declaration.
+- If you are sure it's not supported, you can proceed with the following steps.
+- If you're unsure, you can ask for help in the [Open Terms Archive community]({{< relref "community/how-to/join" >}}).
 
 ## Long-term solution