diff --git a/docs/1.10/administration/configure_authentication/db_auth.md b/docs/1.10/administration/configure_authentication/db_auth.md
index de671fdab..de9265cfc 100644
--- a/docs/1.10/administration/configure_authentication/db_auth.md
+++ b/docs/1.10/administration/configure_authentication/db_auth.md
@@ -18,7 +18,7 @@ In database authentication mode, user accounts are stored in the local database.
 
    ![Enable self-registration](../../img/new_self_reg.png)
     
-   If you enable self registration option, users can register themselves in Harbor. Self-registration is disabled by default. If you enable self-registration, unregistered users can sign up for a Harbor account by clicking **Sign up for an account** in the Harbor log in page.
+   If you enable the self registration option, users can register themselves in Harbor. Self-registration is disabled by default. If you enable self-registration, unregistered users can sign up for a Harbor account by clicking **Sign up for an account** in the Harbor log in page.
     
     ![Enable self-registration](../../img/self-registration-login.png)
     
diff --git a/docs/1.10/administration/configure_authentication/oidc_auth.md b/docs/1.10/administration/configure_authentication/oidc_auth.md
index d7451b7e6..33bb7e721 100644
--- a/docs/1.10/administration/configure_authentication/oidc_auth.md
+++ b/docs/1.10/administration/configure_authentication/oidc_auth.md
@@ -15,7 +15,7 @@ Because the users are managed by the OIDC provider, self-registration, creating
 You must configure your OIDC provider so that you can use it with Harbor. For precise information about how to perform these configurations, see the documentation for your OIDC provider.
 
 - Set up the users and groups that will use the OIDC provider to log in to Harbor. You do not need to assign any specific OIDC roles to users or groups as these do not get mapped to Harbor roles.
-- The URL of the OIDC provider endpoint, known as the Authorization Server in OAuth terminology, must service the well-known URI for its configuration document. For more information about the configuration document, see the [OpenID documentation] (https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest).
+- The URL of the OIDC provider endpoint, known as the Authorization Server in OAuth terminology, must service the well-known URI for its configuration document. For more information about the configuration document, see the [OpenID documentation](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest).
 - To manage users by using OIDC groups, create a custom group claim that contains all of the user groups that you want to register in Harbor. The group claim must be mapped in the ID token that is sent to Harbor when users log in. You can enable the `memberof` feature on the OIDC provider. With the `memberof` feature, the OIDC user entity's `memberof` attribute is updated when the group entity's `member` attribute is updated, for example by adding or removing an OIDC user from the OIDC group.
 - Register Harbor as a client application with the OIDC provider. Associate Harbor's callback URI to the client application as a `redirectURI`. This is the address to which the OIDC provider sends ID tokens.
 
diff --git a/docs/1.10/administration/managing_users/user_permissions_by_role.md b/docs/1.10/administration/managing_users/user_permissions_by_role.md
index 32a09e6e5..c69a9150f 100644
--- a/docs/1.10/administration/managing_users/user_permissions_by_role.md
+++ b/docs/1.10/administration/managing_users/user_permissions_by_role.md
@@ -1,3 +1,7 @@
+[Back to table of contents](../../index.md)
+
+----------
+
 # User Permissions By Role
 
 Users have different abilities depending on the role they in a project.
@@ -55,4 +59,8 @@ The following table depicts the various user permission levels in a project.
 | See project quotas                      | ✓             | ✓     | ✓         | ✓      | ✓             |
 | Edit project quotas  *                   |               |       |           |        |               |
 
-* Only the Harbor system administrator can edit project quotas and add new scanners.
\ No newline at end of file
+* Only the Harbor system administrator can edit project quotas and add new scanners.
+
+----------
+
+[Back to table of contents](../../index.md)
\ No newline at end of file