fixes

Author: shainaraskas

deploy-manage/users-roles.md

@@ -77,9 +77,9 @@ Control access to your {{ece}} [orchestrator](/deploy-manage/deploy/cloud-enterp
 :serverless: all
 :::
 
-As an extension of the [predefined instance access roles](/deploy-manage/users-roles/cloud-organization/user-roles#ec_instance_access_roles) offered for {{serverless-short}} projects, you can create custom roles at the project level to provide more granular control, and provide users with only the access they need within specific projects.
+As an extension of the [predefined instance access roles](/deploy-manage/users-roles/cloud-organization/user-roles.md#ec_instance_access_roles) offered for {{serverless-short}} projects, you can create custom roles at the project level to provide more granular control, and provide users with only the access they need within specific projects.
 
-[Learn more about custom roles for {{serverless-full}} projects](/deploy-manage/users-roles/custom-roles).
+[Learn more about custom roles for {{serverless-full}} projects](/deploy-manage/users-roles/custom-roles.md).
 
 ## Cluster or deployment level
 

deploy-manage/users-roles/custom-roles.md

@@ -32,7 +32,7 @@ You can manage custom roles from within your project, in **{{project-settings}}
 
 Cluster privileges grant access to monitoring and management features in {{es}}. They also enable some stack management capabilities in your project.
 
-:::{image} ../../../images/serverless-custom-roles-cluster-privileges.png
+:::{image} ../../images/serverless-custom-roles-cluster-privileges.png
 :alt: Create a custom role and define {{es}} cluster privileges
 :class: screenshot
 :::
@@ -44,7 +44,7 @@ Refer to [cluster privileges](/deploy-manage/users-roles/cluster-or-deployment-a
 
 Each role can grant access to multiple data indices, and each index can have a different set of privileges. Typically, you will grant the `read` and `view_index_metadata` privileges to each index that you expect your users to work with. For example, grant access to indices that match an `acme-marketing-*` pattern:
 
-:::{image} ../../../images/serverless-custom-roles-index-privileges.png
+:::{image} ../../images/serverless-custom-roles-index-privileges.png
 :alt: Create a custom role and define {{es}} index privileges
 :class: screenshot
 :::
@@ -63,7 +63,7 @@ Document-level and field-level security affords you even more granularity when i
 
 When you create a custom role, click **Add Kibana privilege** to grant access to specific features. The features that are available vary depending on the project type. For example, in {{es-serverless}}:
 
-:::{image} ../../../images/serverless-custom-roles-kibana-privileges.png
+:::{image} ../../images/serverless-custom-roles-kibana-privileges.png
 :alt: Create a custom role and define {{kib}} privileges
 :class: screenshot
 :::

raw-migrated-files/docs-content/serverless/observability-troubleshoot-logs.md

@@ -26,7 +26,7 @@ You need permission to manage API keys
 
 You need to either:
 
-* Ask an administrator to update your user role to at least **Developer** by going to the user icon on the header bar and opening **Organization** → **Members**. Read more about user roles in [Assign user roles and privileges](general-manage-organization.md#general-assign-user-roles). After your use role is updated, restart the onboarding flow.
+* Ask an administrator to update your user role to at least **Developer** by going to the user icon on the header bar and opening **Organization** → **Members**. Read more about user roles in [](/deploy-manage/users-roles/cloud-organization/user-roles.md). After your use role is updated, restart the onboarding flow.
 * Get an API key from an administrator and manually add the API to the {{agent}} configuration. See [Configure the {{agent}}](observability-stream-log-files.md#observability-stream-log-files-step-3-configure-the-agent) for more on manually updating the configuration and adding the API key.