Edited 'issue board' to be lowercase

We recently decided to standardize on lowercase
for issue board. Previously we were using it
inconsistently. (Sometimes title case, sometimes
lowercase.) Related to: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68387

doc/api/boards.md

@@ -427,7 +427,7 @@ POST /projects/:id/boards/:board_id/lists
 NOTE:
 Label, assignee and milestone arguments are mutually exclusive,
 that is, only one of them are accepted in a request.
-Check the [Issue Board documentation](../user/project/issue_board.md)
+Check the [issue board documentation](../user/project/issue_board.md)
 for more information regarding the required license for each list type.
 
 ```shell

doc/api/group_boards.md

@@ -244,7 +244,7 @@ Example response:
 
 ## Create a group issue board **(PREMIUM)**
 
-Creates a Group Issue Board.
+Creates a group issue board.
 
 ```plaintext
 POST /groups/:id/boards
@@ -283,7 +283,7 @@ Example response:
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/5954) in GitLab 11.1.
 
-Updates a Group Issue Board.
+Updates a group issue board.
 
 ```plaintext
 PUT /groups/:id/boards/:board_id
@@ -351,7 +351,7 @@ Example response:
 
 ## Delete a group issue board **(PREMIUM)**
 
-Deletes a Group Issue Board.
+Deletes a group issue board.
 
 ```plaintext
 DELETE /groups/:id/boards/:board_id
@@ -452,7 +452,7 @@ Example response:
 
 ## New group issue board list
 
-Creates a new Issue Board list.
+Creates an issue board list.
 
 ```plaintext
 POST /groups/:id/boards/:board_id/lists
@@ -493,7 +493,7 @@ Example response:
 
 ## Edit group issue board list
 
-Updates an existing Issue Board list. This call is used to change list position.
+Updates an existing issue board list. This call is used to change list position.
 
 ```plaintext
 PUT /groups/:id/boards/:board_id/lists/:list_id

doc/development/fe_guide/development_process.md

@@ -88,7 +88,7 @@ With the purpose of being [respectful of others' time](https://about.gitlab.com/
    GitLab architecture.
 1. Add a diagram to the issue and ask a frontend maintainer in the Slack channel `#frontend_maintainers` about it.
 
-   ![Diagram of Issue Boards Architecture](img/boards_diagram.png)
+   ![Diagram of issue boards architecture](img/boards_diagram.png)
 
 1. Don't take more than one week between starting work on a feature and
    sharing a Merge Request with a reviewer or a maintainer.

doc/install/requirements.md

@@ -321,7 +321,7 @@ For the listed web browsers, GitLab supports:
 
 NOTE:
 We don't support running GitLab with JavaScript disabled in the browser and have no plans of supporting that
-in the future because we have features such as Issue Boards which require JavaScript extensively.
+in the future because we have features such as issue boards which require JavaScript extensively.
 
 <!-- ## Troubleshooting
 

doc/subscriptions/bronze_starter.md

@@ -32,7 +32,7 @@ the tiers are no longer mentioned in GitLab documentation:
   - [Overriding user permissions](../user/group/index.md#override-user-permissions)
   - [User contribution analytics](../user/group/contribution_analytics/index.md)
   - [Kerberos integration](../integration/kerberos.md)
-- Issue Boards:
+- Issue boards:
   - [Configurable issue boards](../user/project/issue_board.md#configurable-issue-boards)
   - [Sum of issue weights](../user/project/issue_board.md#sum-of-issue-weights)
   - [Work In Progress limits](../user/project/issue_board.md#work-in-progress-limits)

doc/user/analytics/value_stream_analytics.md

@@ -64,7 +64,7 @@ Items aren't included in the stage time calculation if they have not reached the
 
 | Stage   | Description   |
 |---------|---------------|
-| Issue   | Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whichever comes first. The label is tracked only if it already includes an [Issue Board list](../project/issue_board.md) created for it. |
+| Issue   | Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whichever comes first. The label is tracked only if it already includes an [issue board list](../project/issue_board.md) created for it. |
 | Plan    | Measures the median time between the action you took for the previous stage, and pushing the first commit to the branch. That first branch commit triggers the separation between **Plan** and **Code**, and at least one of the commits in the branch must include the related issue number (such as `#42`). If the issue number is *not* included in a commit, that data is not included in the measurement time of the stage. |
 | Code    | Measures the median time between pushing a first commit (previous stage) and creating a merge request (MR). The process is tracked with the [issue closing pattern](../project/issues/managing_issues.md#closing-issues-automatically) in the description of the merge request. For example, if the issue is closed with `Closes #xxx`, it's assumed that `xxx` is issue number for the merge request). If there is no closing pattern, the start time is set to the create time of the first commit. |
 | Test    | Essentially the start to finish time for all pipelines. Measures the median time to run the entire pipeline for that project. Related to the time required by GitLab CI/CD to run every job for the commits pushed to that merge request, as defined in the previous stage. |
@@ -85,7 +85,7 @@ How this works:
 In short, the Value Stream Analytics dashboard tracks data related to [GitLab flow](../../topics/gitlab_flow.md). It does not include data for:
 
 - Merge requests that do not close an issue.
-- Issues that do not include labels present in the Issue Board
+- Issues that do not include labels present in the issue board.
 - Issues without a milestone.
 - Staging stages, in projects without a [production environment](#how-the-production-environment-is-identified).
 

doc/user/group/value_stream_analytics/index.md

@@ -113,7 +113,7 @@ Each stage of Value Stream Analytics is further described in the table below.
 
 | **Stage** | **Description** |
 | --------- | --------------- |
-| Issue     | Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whatever comes first. The label is tracked only if it already has an [Issue Board list](../../project/issue_board.md) created for it. |
+| Issue     | Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whatever comes first. The label is tracked only if it already has an [issue board list](../../project/issue_board.md) created for it. |
 | Plan      | Measures the median time between the action you took for the previous stage, and pushing the first commit to the branch. The very first commit of the branch is the one that triggers the separation between **Plan** and **Code**, and at least one of the commits in the branch needs to contain the related issue number (for example, `#42`). If none of the commits in the branch mention the related issue number, it is not considered to the measurement time of the stage. |
 | Code      | Measures the median time between pushing a first commit (previous stage) and creating a merge request (MR) related to that commit. The key to keep the process tracked is to include the [issue closing pattern](../../project/issues/managing_issues.md#closing-issues-automatically) to the description of the merge request (for example, `Closes #xxx`, where `xxx` is the number of the issue related to this merge request). If the closing pattern is not present, then the calculation takes the creation time of the first commit in the merge request as the start time. |
 | Test      | Measures the median time to run the entire pipeline for that project. It's related to the time GitLab CI/CD takes to run every job for the commits pushed to that merge request defined in the previous stage. It is basically the start->finish time for all pipelines. |
@@ -136,7 +136,7 @@ To sum up, anything that doesn't follow [GitLab flow](../../../topics/gitlab_flo
 Value Stream Analytics dashboard does not present any data for:
 
 - Merge requests that do not close an issue.
-- Issues not labeled with a label present in the Issue Board or for issues not assigned a milestone.
+- Issues not labeled with a label present in the issue board or for issues not assigned a milestone.
 - Staging stage, if the project has no [production environment](#how-the-production-environment-is-identified).
 
 ## How the production environment is identified

doc/user/index.md

@@ -43,7 +43,7 @@ GitLab is a Git-based platform that integrates a great number of essential tools
 - Hosting code in repositories with version control.
 - Tracking proposals for new implementations, bug reports, and feedback with a
   fully featured [Issue tracker](project/issues/index.md).
-- Organizing and prioritizing with [Issue Boards](project/issue_board.md).
+- Organizing and prioritizing with [issue boards](project/issue_board.md).
 - Reviewing code in [Merge Requests](project/merge_requests/index.md) with live-preview changes per
   branch with [Review Apps](../ci/review_apps/index.md).
 - Building, testing, and deploying with built-in [Continuous Integration](../ci/index.md).
@@ -58,7 +58,7 @@ With GitLab Enterprise Edition, you can also:
 - Improve collaboration with:
   - [Merge Request Approvals](project/merge_requests/approvals/index.md).
   - [Multiple Assignees for Issues](project/issues/multiple_assignees_for_issues.md).
-  - [Multiple Issue Boards](project/issue_board.md#multiple-issue-boards).
+  - [Multiple issue boards](project/issue_board.md#multiple-issue-boards).
 - Create formal relationships between issues with [linked issues](project/issues/related_issues.md).
 - Use [Burndown Charts](project/milestones/burndown_and_burnup_charts.md) to track progress during a sprint or while working on a new version of their software.
 - Leverage [Elasticsearch](../integration/elasticsearch.md) with [Advanced Search](search/advanced_search.md) for faster, more advanced code search across your entire GitLab instance.

doc/user/permissions.md

@@ -242,10 +242,10 @@ to learn more.
 Find the current permissions on the Value Stream Analytics dashboard, as described in
 [related documentation](analytics/value_stream_analytics.md#permissions).
 
-### Issue Board permissions
+### Issue board permissions
 
-Find the current permissions for interacting with the Issue Board feature in the
-[Issue Boards permissions page](project/issue_board.md#permissions).
+Find the current permissions for interacting with the issue board feature in the
+[issue boards permissions page](project/issue_board.md#permissions).
 
 ### File Locking permissions **(PREMIUM)**
 

doc/user/project/index.md

@@ -22,8 +22,8 @@ Projects include the following [features](https://about.gitlab.com/features/):
 **Repositories:**
 
 - [Issue tracker](issues/index.md): Discuss implementations with your team.
-  - [Issue Boards](issue_board.md): Organize and prioritize your workflow.
-  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards): Create team-specific workflows (Issue Boards) for a project.
+  - [Issue boards](issue_board.md): Organize and prioritize your workflow.
+  - [Multiple issue boards](issue_board.md#multiple-issue-boards): Create team-specific workflows (issue boards) for a project.
 - [Repositories](repository/index.md): Host your code in a fully-integrated platform.
   - [Branches](repository/branches/index.md): Use Git branching strategies to
   collaborate on code.
@@ -41,8 +41,8 @@ Projects include the following [features](https://about.gitlab.com/features/):
 **Issues and merge requests:**
 
 - [Issue tracker](issues/index.md): Discuss implementations with your team.
-  - [Issue Boards](issue_board.md): Organize and prioritize your workflow.
-  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards): Create team-specific workflows (Issue Boards) for a project.
+  - [Issue boards](issue_board.md): Organize and prioritize your workflow.
+  - [Multiple issue boards](issue_board.md#multiple-issue-boards): Create team-specific workflows (issue boards) for a project.
 - [Merge Requests](merge_requests/index.md): Apply a branching
   strategy and get reviewed by your team.
   - [Merge Request Approvals](merge_requests/approvals/index.md): Ask for approval before
@@ -141,7 +141,7 @@ There are numerous [APIs](../../api/index.md) to use with your projects:
 - [Threads](../../api/discussions.md)
 - [General](../../api/projects.md)
 - [Import/export](../../api/project_import_export.md)
-- [Issue Board](../../api/boards.md)
+- [Issue board](../../api/boards.md)
 - [Labels](../../api/labels.md)
 - [Markdown](../../api/markdown.md)
 - [Merge Requests](../../api/merge_requests.md)

doc/user/project/issue_board.md

@@ -4,9 +4,9 @@ group: Project Management
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# Issue Boards **(FREE)**
+# Issue boards **(FREE)**
 
-The GitLab Issue Board is a software project management tool used to plan,
+The issue board is a software project management tool used to plan,
 organize, and visualize a workflow for a feature or product release.
 It can be used as a [Kanban](https://en.wikipedia.org/wiki/Kanban_(development)) or a
 [Scrum](https://en.wikipedia.org/wiki/Scrum_(software_development)) board.
@@ -46,7 +46,7 @@ To learn more, visit [GitLab Enterprise features for issue boards](#gitlab-enter
 
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
 Watch a [video presentation](https://youtu.be/vjccjHI7aGI) of
-the Issue Board feature.
+the issue board feature.
 
 ## Multiple issue boards
 
@@ -70,7 +70,7 @@ GitLab automatically loads the last board you visited.
 
 To create a new issue board:
 
-1. Click the dropdown with the current board name in the upper left corner of the Issue Boards page.
+1. Click the dropdown with the current board name in the upper left corner of the issue boards page.
 1. Click **Create new board**.
 1. Enter the new board's name and select its scope: milestone, labels, assignee, or weight.
 
@@ -78,7 +78,7 @@ To create a new issue board:
 
 To delete the currently active issue board:
 
-1. Click the dropdown with the current board name in the upper left corner of the Issue Boards page.
+1. Click the dropdown with the current board name in the upper left corner of the issue boards page.
 1. Click **Delete board**.
 1. Click **Delete** to confirm.
 
@@ -195,7 +195,7 @@ card includes:
 ## Permissions
 
 Users with the [Reporter and higher roles](../permissions.md) can use all the functionality of the
-Issue Board feature to create or delete lists. They can also drag issues from one list to another.
+issue board feature to create or delete lists. They can also drag issues from one list to another.
 
 ## How GitLab orders issues in a list
 
@@ -271,7 +271,7 @@ clicking **View scope**.
 
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
 Watch a [video presentation](https://youtu.be/m5UTNCSqaDk) of
-the Configurable Issue Board feature.
+the configurable issue board feature.
 
 ### Focus mode
 

doc/user/project/issues/index.md

@@ -45,7 +45,7 @@ To learn how the GitLab Strategic Marketing department uses GitLab issues with [
 - [Sort issue lists](sorting_issue_lists.md)
 - [Search for issues](../../search/index.md#filtering-issue-and-merge-request-lists)
 - [Epics](../../group/epics/index.md)
-- [Issue Boards](../issue_board.md)
+- [Issue boards](../issue_board.md)
 - [Issues API](../../../api/issues.md)
 - [Configure an external issue tracker](../../../integration/external-issue-tracker.md)
 - [Parts of an issue](issue_data_and_actions.md)

doc/user/project/issues/issue_data_and_actions.md

@@ -129,7 +129,7 @@ element. Due dates can be changed as many times as needed.
 ### Labels
 
 Categorize issues by giving them [labels](../labels.md). They help to organize workflows,
-and they enable you to work with the [GitLab Issue Board](../issue_board.md).
+and they enable you to work with the [issue board](../issue_board.md).
 
 Group Labels, which allow you to use the same labels for all projects in the same
 group, can also be given to issues. They work exactly the same, but are immediately

doc/user/project/issues/managing_issues.md

@@ -44,7 +44,7 @@ There are many ways to get to the New Issue form from a project's page:
 
   ![New issue from a project's dashboard](img/new_issue_from_projects_dashboard.png)
 
-- From an **Issue Board**, create a new issue by clicking on the plus sign (**+**) at the top of a list.
+- From an **issue board**, create a new issue by clicking on the plus sign (**+**) at the top of a list.
   It opens a new issue for that project, pre-labeled with its respective list.
 
   ![From the issue board](img/new_issue_from_issue_board.png)
@@ -237,10 +237,10 @@ using the close button:
 
 ![close issue - button](img/button_close_issue_v13_6.png)
 
-You can also close an issue from the [Issue Boards](../issue_board.md) by dragging an issue card
+You can also close an issue from the [issue boards](../issue_board.md) by dragging an issue card
 from its list and dropping it into the **Closed** list.
 
-![close issue from the Issue Board](img/close_issue_from_board.gif)
+![close issue from the issue board](img/close_issue_from_board.gif)
 
 ### Closing issues automatically
 

doc/user/project/settings/index.md

@@ -213,7 +213,7 @@ Some features depend on others:
 
 - If you disable the **Issues** option, GitLab also removes the following
   features:
-  - **Issue Boards**
+  - **issue boards**
   - [**Service Desk**](#service-desk)
 
   NOTE:

doc/user/search/index.md

@@ -217,12 +217,12 @@ filters them for you as you type.
 You can also **Explore** all public and internal groups available in GitLab.com,
 and sort them by **Last created**, **Oldest created**, **Last updated**, or **Oldest updated**.
 
-## Issue Boards
+## Issue boards
 
-From an [Issue Board](../../user/project/issue_board.md), you can filter issues by **Author**, **Assignee**, **Milestone**, and **Labels**.
+From an [issue board](../../user/project/issue_board.md), you can filter issues by **Author**, **Assignee**, **Milestone**, and **Labels**.
 You can also filter them by name (issue title), from the field **Filter by name**, which is loaded as you type.
 
-To search for issues to add to lists present in your Issue Board, click
+To search for issues to add to lists present in your issue board, click
 the button **Add issues** on the top-right of your screen, opening a modal window from which
 you can, besides filtering them by **Name**, **Author**, **Assignee**, **Milestone**,
 and **Labels**, select multiple issues to add to a list of your choice: