moving ../

Author: kalexand-rh

admin_guide/custom_resource_definitions.adoc

@@ -8,7 +8,6 @@
 :toc: macro
 :toc-title:
 :context: admin-guide-custom-resources
-:relfileprefix: ../
 
 toc::[]
 

modules/create_aggregated_cluster_role_crd.adoc

@@ -11,7 +11,7 @@ Module included in the following assemblies:
 
 After you create cluster-scoped CRDs, you can grant permissions to it. If you
 use the admin, edit, and view 
-xref:architecture/additional_concepts/authorization.adoc#roles[default
+xref:../architecture/additional_concepts/authorization.adoc#roles[default
 cluster roles], take advantage of cluster role aggregation for their rules.
 
 [IMPORTANT]
@@ -22,7 +22,7 @@ assign a rule to a role, you must also assign that verb to roles that have more
 permissions. For example, if you grant the "get crontabs" permission to the view
 role, you must also grant it to the edit and admin roles. The admin or edit role 
 is usually assigned to the user that created a project through the 
-xref:admin_guide/managing_projects.adoc#modifying-the-template-for-new-projects[project 
+xref:../admin_guide/managing_projects.adoc#modifying-the-template-for-new-projects[project 
 template].
 ====
 
@@ -66,7 +66,7 @@ rules:
 <4> Specify this label to grant permissions to the edit default role. 
 <5> Specify the group name of the CRD.
 <6> Specify the plural name of the CRD that these rules apply to.
-<7> Specify the xref:architecture/additional_concepts/authorization.adoc#action[verbs]
+<7> Specify the xref:../architecture/additional_concepts/authorization.adoc#action[verbs]
 that represent the permissions that are granted to the role. For example, apply 
 read and write permissions to the admin and edit roles and only read permission
 to the view role.