chore: documentation cleanup (#853)

Co-authored-by: hackerman <[email protected]>

Author: tomekpapiernik

docs/concepts/managed-ui.mdx

@@ -3,29 +3,35 @@ id: personal-access-token
 title: Personal Access Tokens
 ---
 
-You need to access the Ory administrative APIs if you want to:
+A Personal Access Token (PAT) is a means of authentication you can use when directly calling the Ory APIs. The PAT is bound to the
+Ory Cloud project where it was created. A PAT created for an administrator in project `A` won't be valid in project `B` in any 
+capacity.
 
-- [list](../cli/ory-identities-list.md),
-- [update](../cli/ory-identities-get.md) or
-- [delete](../cli/ory-identities-delete.md) identities,
-- use the [Ory CLI](../guides/cli/10_config-with-cli.mdx) to manage your project
+For example, when calling Ory administrative APIs to [list](../cli/ory-identities-list.md), [update](../cli/ory-identities-get.md),
+or [delete](../cli/ory-identities-delete.md) identities, you must authenticate as an administrator. You can do that by passing
+a PAT in the request's `Authorization` header. The PAT must be generated for a user with administrative rights in the Ory Cloud 
+Project in which you want to manage identities. 
 
-To access administrative APIs at Ory you need to authenticate as an administrator. Ory offers Personal Access Tokens to make this
-process easier for development. You can use PATs to access the admin API from the command line or via scripts.
+:::tip
 
-:::note
-
-Ory's Personal Access Tokens are always prefixed with `ory_pat_`, making them easier to identify in code analysis.
+You can use PATs to call APIs from the command line or through scripts. Ory PATs are always prefixed with `ory_pat_`, which makes 
+it easy to identify them when analyzing code.
 
 :::
 
-Personal Access Tokens are bound to a project. They don't work for other projects than the one they have been created for.
+## Creating a Personal Access Token
+
+Follow these steps to create a Personal Access Token (PAT):
 
-Every member can create many, but not unlimited, personal access tokens. When creating a token you must give it a description to
-help you remember what you created the token for. It helps to name the token after the function it performs or after the person
-that uses it, but the name can be freely chosen.
+1. Open the [Ory Console](https://console.ory.sh/) and sign in.
+2. Select **Connect** from the left navigation bar.
+3. Scroll to the bottom of the page to the **Personal Access Token** section.
+4. Click the **+** icon.
+5. Define the name of the generated token. This name is used for identification purposes only. 
+6. Copy the created PAT and store it in a safe place. 
+  
+  :::warning
 
-The token is only displayed once upon creation. If you lose the token you will have to create a new one.
+  The PAT is displayed only once. If you lose the token, you must generate a new one. 
 
-To see detailed instructions how to create and use Personal Access Tokens, refer to the
-[Create Personal Access Tokens Guide](../guides/create-personal-access-token.mdx).
+  :::

docs/concepts/personal-access-token.mdx

@@ -10,8 +10,6 @@ Internally, Ory Cloud Projects run our popular open source projects in a multi-t
 low-latency, and reliable way. Ory Cloud Projects include additional services (such as dashboards, endpoint security, SLAs, ...)
 which aren't available in the open source.
 
-For a step-by-step guide please visit the [Create Ory Cloud Project](../guides/console/create-project.mdx) document.
-
 ## Project Services
 
 Each Ory Cloud Project consists of the following services :

docs/concepts/project-invite-membership.mdx

@@ -3,12 +3,11 @@ id: redirects
 title: Browser Redirects and Flow Completion
 ---
 
-This document covers browser redirects for Server Side Applications (NodeJs, PHP, Golang etc.) and how to configure them. To learn
-more about the SDK for Single Page Applications, check out the [SDK](./services-api.mdx) documentation.
+This document covers browser redirects for Server Side Applications (NodeJs, PHP, Golang etc.) and how to configure them.
 
 ## Allow List
 
-Set dynamic redirects using the `?return_to=` query parameter on [Self-Service Flows](./self-service.mdx). For example: a user
+Set dynamic redirects using the `?return_to=` query parameter on self-service flows. For example: a user
 opens a sharable link to go to `https://myapp.com/posts`. This URL requires the user to have an active session and redirects the
 user back to the login page. To return the user back to the original URL, append `?return_to=https://myapp.com/posts` when
 starting the [self-service login flow](https://www.ory.sh/docs/reference/api#operation/initializeSelfServiceLoginFlowForBrowsers):
@@ -34,7 +33,7 @@ Ory Cloud has a total of six flows, **Login**, **Registration**, **Verification*
 can be configured to redirect back to any URL. A common use case would be to redirect the user to your application home screen
 after a logout or to a specific URL on a sub-domain after a settings password update.
 
-On project creation the redirect flows are set to the default [Managed User Interface](./managed-ui.mdx).
+On project creation the redirect flows are set to the default Managed User Interface.
 
 ### Login, Registration, and Settings
 
@@ -123,7 +122,7 @@ Default Redirect URL can be an FQDN or a path.
 
 Update or delete a redirect by either changing the current redirects value or deleting the entry and clicking the **Update**
 button. Reset all flows at once with the **Reset Flows** button which will prompt a confirmation box. Resetting all flows will
-reset all the fields back to the default value which is the Ory Cloud [Managed User Interface](./managed-ui.mdx).
+reset all the fields back to the default value which is the Ory Cloud Managed User Interface.
 
 Updates to flows will take effect on **new** flows. It will have no effect on old flows that haven't expired yet.
 

docs/concepts/project.mdx

@@ -31,7 +31,7 @@ section of your Ory Cloud Console.
 
 #### Identity Schema
 
-The JSON Schema that defines an identity in an Ory Cloud Project. Learn more about [Identity Schemas](./identity.mdx).
+The JSON Schema that defines an identity in an Ory Cloud Project.
 
 #### Ory Login Session
 

docs/concepts/redirects.mdx

@@ -1,4 +1,4 @@
 Before you start make sure to either
 
-1. have a running [Ory Cloud Project](../console/create-project.mdx);
+1. have a running Ory Cloud Project
 2. or are running Ory's Identity service (Ory Kratos) on your machine.

docs/concepts/self-service.mdx

@@ -21,13 +21,6 @@ other screens implemented yet? Your configuration would look as follows:
 
 ![Customize UI Endpoints in the Ory Cloud Console](_static/bring-your-user-interface/login-ui.png)
 
-:::note
-
-If you are unsure how to set up your Ory Cloud Project to be connected to your domain (such as `example.org`), head over to
-[Get Ready for Production](../start-building/deploy-auth-production.mdx).
-
-:::
-
 All other flows (registration, settings, verification, recovery, error) would still use Ory Cloud's managed UI!
 
 ## Reference Implementations and Guided Examples