Merge branch 'docs-fix-doc-lint-script' into 'master'

Fix docs-lint job that was missing half the docs

See merge request gitlab-org/gitlab!26951

doc/administration/gitaly/praefect.md

@@ -490,10 +490,10 @@ Particular attention should be shown to:
 
 1. Configure the `external_url` so that files could be served by GitLab
    by proper endpoint access by editing `/etc/gitlab/gitlab.rb`:
-   
+
    You will need to replace `GITLAB_SERVER_URL` with the real URL on which
    current GitLab instance is serving:
-   
+
    ```ruby
    external_url 'GITLAB_SERVER_URL'
    ```

doc/administration/packages/container_registry.md

@@ -741,7 +741,7 @@ To enable the read-only mode:
    ```sh
    # Recycling unused tags
    sudo /opt/gitlab/embedded/bin/registry garbage-collect /var/opt/gitlab/registry/config.yml
-   
+
    # Removing unused layers not referenced by manifests
    sudo /opt/gitlab/embedded/bin/registry garbage-collect -m /var/opt/gitlab/registry/config.yml
    ```

doc/development/fe_guide/vuex.md

@@ -3,12 +3,12 @@
 When there's a clear benefit to separating state management from components (e.g. due to state complexity) we recommend using [Vuex][vuex-docs] over any other Flux pattern. Otherwise, feel free to manage state within the components.
 
 Vuex should be strongly considered when:
+
 - You expect multiple parts of the application to react to state changes
 - There's a need to share data between multiple components
 - There are complex interactions with Backend, e.g. multiple API calls
 - The app involves interacting with backend via both traditional REST API and GraphQL (especially when moving the REST API over to GraphQL is a pending backend task)
 
-
 _Note:_ All of the below is explained in more detail in the official [Vuex documentation][vuex-docs].
 
 ## Separation of concerns

doc/user/group/subgroups/index.md

@@ -64,7 +64,6 @@ Another example of GitLab as a company would be the following:
 
 ---
 
-
 When performing actions such as transferring or importing a project between
 subgroups, the behavior is the same as when performing these actions at the
 `group/project` level.

doc/user/project/clusters/serverless/aws.md

@@ -362,7 +362,7 @@ sam init -h
 
 ### Setting up your AWS credentials with your GitLab account
 
-In order to interact with your AWS account, the GitLab CI/CD pipelines require both 
+In order to interact with your AWS account, the GitLab CI/CD pipelines require both
 `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to be set in the project's CI/CD
 variables.
 

scripts/lint-doc.sh

@@ -48,7 +48,7 @@ then
   exit 1
 fi
 
-MD_DOC_PATH=${MD_DOC_PATH:-doc/**/*.md}
+MD_DOC_PATH=${MD_DOC_PATH:-doc}
 
 function run_locally_or_in_docker() {
   local cmd=$1