Remove unneeded image from protected_tags.md

This image was outdated and isn't needed. Remove it.

doc/user/project/protected_tags.md

@@ -23,9 +23,7 @@ anyone without Maintainer [permissions](../permissions.md) is prevented from cre
 
 To protect a tag, you need to have at least Maintainer [permissions](../permissions.md).
 
-1. Navigate to the project's **Settings > Repository**:
-
-   ![Repository Settings](img/project_repository_settings.png)
+1. Go to the project's **Settings > Repository**.
 
 1. From the **Tag** dropdown menu, select the tag you want to protect or type and click **Create wildcard**. In the screenshot below, we chose to protect all tags matching `v*`:
 

doc/user/project/repository/file_finder.md

@@ -7,17 +7,13 @@ disqus_identifier: 'https://docs.gitlab.com/ee/workflow/file_finder.html'
 
 # File finder **(FREE)**
 
-> [Introduced](https://github.com/gitlabhq/gitlabhq/pull/9889) in GitLab 8.4.
-
 The file finder feature allows you to search for a file in a repository using the
-GitLab UI.
-
-You can find the **Find File** button when in the **Files** section of a
-project.
+GitLab UI. To use it:
 
-![Find file button](img/file_finder_find_button_v12_10.png)
+1. Go to your project's **Repository > Files**.
+1. In the upper right corner, select **Find File**.
 
-If you prefer to keep their fingers on the keyboard, use the
+If you prefer to keep your fingers on the keyboard, use the
 [shortcut button](../../shortcuts.md), which you can invoke from anywhere
 in a project.
 

doc/user/project/repository/git_blame.md

@@ -8,17 +8,15 @@ description: "Documentation on Git file blame."
 
 # Git file blame **(FREE)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/commit/39c657930625ddc3ac8a921f01ffc83acadce68f) in GitLab 2.5.
-
 [Git blame](https://git-scm.com/docs/git-blame) provides more information
 about every line in a file, including the last modified time, author, and
-commit hash.
-
-You can find the **Blame** button with each file in a project.
+commit hash. To view it for a file:
 
-![File blame button](img/file_blame_button_v12_6.png "Blame button")
+1. Go to your project's **Repository > Files**.
+1. Select the file you want to review.
+1. In the upper right corner, select **Blame**.
 
-When you select the **Blame** button, this information is shown:
+When you select **Blame**, this information is displayed:
 
 ![Git blame output](img/file_blame_output_v12_6.png "Blame button output")
 

doc/user/project/repository/git_history.md

@@ -8,16 +8,13 @@ description: "Documentation on Git file history."
 
 # Git file history **(FREE)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab/blob/9ba1224867665844b117fa037e1465bb706b3685/app/controllers/commits_controller.rb) in GitLab 0.8.0
-
 Git file History provides information about the commit history associated
-with a file.
-
-You can find the **History** button with each file in a project.
+with a file. To use it:
 
-![File history button](img/file_history_button_v12_6.png "History button")
+1. Go to your project's **Repository > Files**.
+1. In the upper right corner, select **History**.
 
-When you select the **History** button, this information displays:
+When you select **History**, this information is displayed:
 
 ![Git log output](img/file_history_output_v12_6.png "History button output")