Add expectation of disabling FutureTense rule

Tutorials use future tense, so let's build in the expectation that
we will turn off alerts for future tense on those pages.

doc/development/documentation/topic_types/tutorial.md

@@ -43,6 +43,8 @@ Tutorials should be in this format:
 title: Title (starts with "Tutorial:" followed by an active verb, like "Tutorial: Create a website")
 ---
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 A paragraph that explains what the tutorial does, and the expected outcome.
 
 To create a website:
@@ -109,6 +111,7 @@ you can:
 - Add encouraging or congratulatory phrases after tasks.
 - Use future tense from time to time, especially when you're introducing
   steps. For example, `Next, you will associate your issues with your epics`.
+  Disable the Vale rule `gitlab_base.FutureTense` to avoid false positives.
 - Be more conversational. For example, `This task might take a while to complete`.
 
 ## Metadata

doc/tutorials/agile_sprint/_index.md

@@ -5,6 +5,8 @@ info: For assistance with this tutorial, see https://handbook.gitlab.com/handboo
 title: 'Tutorial: Use GitLab to run an Agile iteration'
 ---
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 To run an Agile development iteration in GitLab, you use multiple GitLab features
 that work together.
 

doc/tutorials/compliance_pipeline/_index.md

@@ -22,6 +22,8 @@ This change is a breaking change. For more information, see the [migration guide
 
 {{< /alert >}}
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 You can use [compliance pipelines](../../user/compliance/compliance_pipelines.md) to ensure specific
 compliance-related jobs are run on pipelines for all projects in a group. Compliance pipelines are applied
 to projects through [compliance frameworks](../../user/compliance/compliance_frameworks.md).

doc/tutorials/create_register_first_runner/_index.md

@@ -5,6 +5,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 title: 'Tutorial: Create, register, and run your own project runner'
 ---
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 This tutorial shows you how to configure and run your first runner in GitLab.
 
 A runner is an agent in the GitLab Runner application that runs jobs in a GitLab CI/CD pipeline.

doc/tutorials/fuzz_testing/_index.md

@@ -12,6 +12,8 @@ title: 'Tutorial: Perform fuzz testing in GitLab'
 
 {{< /details >}}
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 [Coverage-guided fuzz testing](../../user/application_security/coverage_fuzzing/_index.md#coverage-guided-fuzz-testing-process) sends unexpected, malformed, or random data to your application, and then monitors
 your application for unstable behaviors and crashes.
 

doc/tutorials/install_gitlab_single_node/_index.md

@@ -12,6 +12,8 @@ title: 'Tutorial: Install and secure a single node GitLab instance'
 
 {{< /details >}}
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 In this tutorial you will learn how to install and securely configure a single
 node GitLab instance that can accommodate up to
 [20 RPS or 1,000 users](../../administration/reference_architectures/1k_users.md).

doc/tutorials/left_sidebar/_index.md

@@ -19,6 +19,8 @@ title: 'Tutorial: Use the left sidebar to navigate GitLab'
 
 {{< /history >}}
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 Follow this tutorial to learn how to use the new left sidebar to navigate the UI.
 
 ## Layout of the left sidebar

doc/tutorials/make_first_git_commit/_index.md

@@ -5,6 +5,8 @@ info: For assistance with this tutorial, see https://handbook.gitlab.com/handboo
 title: 'Tutorial: Make your first Git commit'
 ---
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 This tutorial will teach you a little bit about how Git works. It walks
 you through the steps of creating your own project, editing a file, and
 committing changes to a Git repository from the command line.

doc/tutorials/manage_user/_index.md

@@ -12,6 +12,8 @@ title: 'Tutorial: Set up your organization'
 
 {{< /details >}}
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 In GitLab, you set up and manage your company's GitLab organization by:
 
 - Creating groups, subgroups, and projects.

doc/tutorials/observability/observability_django_tutorial.md

@@ -16,6 +16,7 @@ For more information, see the history of the [**Distributed tracing** feature](.
 In this tutorial, we'll show you how to create, configure, instrument, and monitor a Django application using GitLab observability features.
 
 <!-- vale gitlab_base.SentenceSpacing = NO -->
+<!-- vale gitlab_base.FutureTense = NO -->
 
 ## Before you begin
 

doc/tutorials/product_analytics_onboarding_website_project/_index.md

@@ -13,6 +13,8 @@ title: 'Tutorial: Set up product analytics in a GitLab Pages website project'
 
 {{< /details >}}
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 Understanding how your users engage with your website or application is important for making data-driven decisions.
 By identifying the most and least used features by your users, your team can decide where and how to spend their time effectively.
 

doc/tutorials/set_up_gitlab_google_integration/_index.md

@@ -5,6 +5,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 title: 'Tutorial: Set up the Google Cloud integration'
 ---
 
+<!-- vale gitlab_base.FutureTense = NO -->
+
 This tutorial shows you how to integrate Google Cloud with GitLab,
 so that you can deploy directly to Google Cloud.