Merge pull request #776 from docker/dtr-2.6-updates

Dtr 2.6 updates

ee/dtr/user/access-tokens.md

@@ -7,33 +7,32 @@ redirect_from:
   - /datacenter/dtr/2.5/guides/user/access-tokens/
 ---
 
-Docker Trusted Registry allows you to issue access tokens so that you can
-integrate with other services without having to give those services your
-credentials. An access token is issued for a user and has the same DTR
-permissions the user has.
+Docker Trusted Registry allows you to create and distribute access tokens to enable programmatic access to DTR. Access tokens are linked to a particular user account and duplicate whatever permissions that account has at time of use. If the account changes permissions, so will the token.
 
-It's better to use access tokens to build integrations since you can issue
-multiple tokens, one for each integration, and revoke them at any time.
+Access tokens are useful in cases such as building integrations since you can issue multiple tokens – one for each integration – and revoke them at any time.
 
 ## Create an access token
 
-In the **DTR web UI**, navigate to your user profile, and choose **Access tokens**.
+1. To create an access token for the first time, log in to `https://<dtr-url` with your UCP credentials.
 
-![Token list](../images/access-tokens-1.png){: .with-border}
+2. Expand your **Profile** from the left navigation pane and select **Profile > Access Tokens**.
 
-Click **New access token**, and assign a meaningful name to your token.
-Choose a name that indicates where the token is going to be used, or what’s the
-purpose for the token. Administrators can also create tokens for other users.
+    ![Token list](../images/access-tokens-1.png){: .with-border}
+
+3. Add a description for your token. Specify something which indicates where the token is going to be used, or set a purpose for the token. Administrators can also create tokens for other users.
 
 ![Create token](../images/access-tokens-2.png){: .with-border}
 
-Once the token is created you won’t be able to see it again, but you can
-rename it if needed.
+## Modify an access token
+
+Once the token is created, you will not be able to see it again. You do have the option to rename, deactivate or delete the token as needed. You can delete the token by selecting it and clicking **Delete**, or you can click **View Details**:
+
+![Create token](../images/access-tokens-3.png){: .with-border}
 
 ## Use the access token
 
-You can use an access token in any place that requires your DTR password.
-As an example you can use access tokens to login in from your Docker CLI client:
+You can use an access token anywhere that requires your DTR password.
+As an example you can pass your access token to the `--password` or `-p` option when logging in from your Docker CLI client:
 
 ```bash
 docker login dtr.example.org --username <username> --password <token>

ee/dtr/user/manage-images/index.md

@@ -9,36 +9,48 @@ redirect_from:
 Since DTR is secure by default, you need to create the image repository before
 being able to push the image to DTR.
 
-In this example, we'll create the 'golang' repository in DTR.
+In this example, we'll create the `wordpress` repository in DTR.
 
 ## Create a repository
 
-To create a new repository, navigate to the **DTR web application**, and click
-the **New repository** button.
+1. To create an image repository for the first time, log in to `https://<dtr-url` with your UCP credentials.
 
-![](../../images/create-repository-1.png){: .with-border}
+2. Select **Repositories** from the left navigation pane and click **New repository** on the upper right corner of the Repositories page.
 
-Add a **name and description** for the repository, and choose whether your
-repository is public or private:
+    ![](../../images/create-repository-1.png){: .with-border}
 
-  * Public repositories are visible to all users, but can only be changed by
-  users granted with permission to write them.
-  * Private repositories can only be seen by users that have been granted
+
+3. Select your namespace and enter a name for your repository. You can optionally add a description.
+
+4.  Choose whether your repository is `public` or `private`:
+
+    * Public repositories are visible to all users, but can only be changed by
+  users with write permissions to them.
+    * Private repositories can only be seen by users that have been granted
   permissions to that repository.
 
-![](../../images/create-repository-2.png){: .with-border}
+    ![](../../images/create-repository-2.png){: .with-border}
 
-Click **Save** to create the repository.
 
-When creating a repository in DTR, the full name of the repository becomes
+5. Click **Create** to create the repository. 
+
+   When creating a repository in DTR, the full name of the repository becomes
 `<dtr-domain-name>/<user-or-org>/<repository-name>`. In this example, the full
-name of our repository will be `dtr.example.org/dave.lauper/golang`.
+name of our repository will be `dtr-example.com/test-user-1/wordpress`.
+
+6. Optional: Click **Show advanced settings** to make your tags immutable or set your image scanning trigger.
+
+    ![](../../images/create-repository-3.png){: .with-border}
+
+> Immutable Tags and Tag Limit
+>
+> Starting in DTR 2.6, repository admins can enable tag pruning by [setting a tag limit](tag-pruning/#set-a-tag-limit). This can only be set if you turn off **Immutability** and allow your repository tags to be overwritten. 
 
 > Image name size for DTR
 >
 > When creating an image name for use with DTR ensure that the organization and repository name has less than 56 characters and that the entire image name which includes domain, organization and repository name does not exceed 255 characters.
 >
-> The 56 character `<user-or-org/repository-name>` limit in DTR is due to an underlying limitation in how the image name information is stored within DTR metadata in RethinkDB.  RethinkDB currently has a Primary Key length limit of 127 characters.
+> The 56-character `<user-or-org/repository-name>` limit in DTR is due to an underlying limitation in how the image name information is stored within DTR metadata in RethinkDB.  RethinkDB currently has a Primary Key length limit of 127 characters.
 >
 > When DTR stores the above data it appends a sha256sum comprised of 72 characters to the end of the value to ensure uniqueness within the database.  If the `<user-or-org/repository-name>` exceeds 56 characters it will then exceed the 127 character limit in RethinkDB (72+56=128).
 {: .important}