Commit 17ca886f authored by Amy Qualls's avatar Amy Qualls

Merge branch 'admin-to-administrator' into 'master'

Various "admin" -> "administrator" fixes

See merge request gitlab-org/gitlab!67996
parents aac9a974 11482578
...@@ -135,10 +135,10 @@ This is not applicable yet as multiple indices functionality is not fully implem ...@@ -135,10 +135,10 @@ This is not applicable yet as multiple indices functionality is not fully implem
Currently GitLab can only handle a single version of setting. Any setting/schema changes would require reindexing everything from scratch. Since reindexing can take a long time, this can cause search functionality downtime. Currently GitLab can only handle a single version of setting. Any setting/schema changes would require reindexing everything from scratch. Since reindexing can take a long time, this can cause search functionality downtime.
To avoid downtime, GitLab is working to support multiple indices that To avoid downtime, GitLab is working to support multiple indices that
can function at the same time. Whenever the schema changes, the admin can function at the same time. Whenever the schema changes, the administrator
will be able to create a new index and reindex to it, while searches will be able to create a new index and reindex to it, while searches
continue to go to the older, stable index. Any data updates will be continue to go to the older, stable index. Any data updates will be
forwarded to both indices. Once the new index is ready, an admin can forwarded to both indices. Once the new index is ready, an administrator can
mark it active, which will direct all searches to it, and remove the old mark it active, which will direct all searches to it, and remove the old
index. index.
......
...@@ -96,7 +96,7 @@ projects that need updating. Those projects can be: ...@@ -96,7 +96,7 @@ projects that need updating. Those projects can be:
- Updated recently: Projects that have a `last_repository_updated_at` - Updated recently: Projects that have a `last_repository_updated_at`
timestamp that is more recent than the `last_repository_successful_sync_at` timestamp that is more recent than the `last_repository_successful_sync_at`
timestamp in the `Geo::ProjectRegistry` model. timestamp in the `Geo::ProjectRegistry` model.
- Manual: The admin can manually flag a repository to resync in the - Manual: The administrator can manually flag a repository to resync in the
[Geo admin panel](../user/admin_area/geo_nodes.md). [Geo admin panel](../user/admin_area/geo_nodes.md).
When we fail to fetch a repository on the secondary `RETRIES_BEFORE_REDOWNLOAD` When we fail to fetch a repository on the secondary `RETRIES_BEFORE_REDOWNLOAD`
......
...@@ -277,7 +277,7 @@ On the Route 53 dashboard, click **Hosted zones** in the left navigation bar: ...@@ -277,7 +277,7 @@ On the Route 53 dashboard, click **Hosted zones** in the left navigation bar:
1. Click **Create**. 1. Click **Create**.
1. If you registered your domain through Route 53, you're done. If you used a different domain registrar, you need to update your DNS records with your domain registrar. You'll need to: 1. If you registered your domain through Route 53, you're done. If you used a different domain registrar, you need to update your DNS records with your domain registrar. You'll need to:
1. Click on **Hosted zones** and select the domain you added above. 1. Click on **Hosted zones** and select the domain you added above.
1. You'll see a list of `NS` records. From your domain registrar's admin panel, add each of these as `NS` records to your domain's DNS records. These steps may vary between domain registrars. If you're stuck, Google **"name of your registrar" add DNS records** and you should find a help article specific to your domain registrar. 1. You'll see a list of `NS` records. From your domain registrar's administrator panel, add each of these as `NS` records to your domain's DNS records. These steps may vary between domain registrars. If you're stuck, Google **"name of your registrar" add DNS records** and you should find a help article specific to your domain registrar.
The steps for doing this vary depending on which registrar you use and is beyond the scope of this guide. The steps for doing this vary depending on which registrar you use and is beyond the scope of this guide.
......
...@@ -31,7 +31,7 @@ _Taken from the slides [ClearCase and the journey to Git](https://docplayer.net/ ...@@ -31,7 +31,7 @@ _Taken from the slides [ClearCase and the journey to Git](https://docplayer.net/
## Why migrate ## Why migrate
ClearCase can be difficult to manage both from a user and an admin perspective. ClearCase can be difficult to manage both from a user and an administrator perspective.
Migrating to Git/GitLab there is: Migrating to Git/GitLab there is:
- **No licensing costs**, Git is GPL while ClearCase is proprietary. - **No licensing costs**, Git is GPL while ClearCase is proprietary.
......
...@@ -64,5 +64,5 @@ in the abuse report's **Message** field. ...@@ -64,5 +64,5 @@ in the abuse report's **Message** field.
## Managing abuse reports ## Managing abuse reports
Admins are able to view and resolve abuse reports. Administrators are able to view and resolve abuse reports.
For more information, see [abuse reports administration documentation](admin_area/review_abuse_reports.md). For more information, see [abuse reports administration documentation](admin_area/review_abuse_reports.md).
...@@ -306,10 +306,10 @@ GitLab instance. ...@@ -306,10 +306,10 @@ GitLab instance.
## Search settings ## Search settings
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/292941) in GitLab 13.8 behind a feature flag, disabled by default. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/292941) in GitLab 13.8 behind a feature flag, disabled by default.
> - [Added to Group, Admin, and User settings](https://gitlab.com/groups/gitlab-org/-/epics/4842) in GitLab 13.9. > - [Added to Group, Administrator, and User settings](https://gitlab.com/groups/gitlab-org/-/epics/4842) in GitLab 13.9.
> - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/294025) in GitLab 13.11. > - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/294025) in GitLab 13.11.
You can search inside a Project, Group, Admin, or User's settings by entering You can search inside a Project, Group, Administrator, or User's settings by entering
a search term in the search box located at the top of the page. The search results a search term in the search box located at the top of the page. The search results
appear highlighted in the sections that match the search term. appear highlighted in the sections that match the search term.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment