Apply suggestion to doc/administration/monitoring/performance/grafana_configuration.mdphilbz-master-patch-49694

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md
index 6a59f65e6b9..9a83c9c0204 100644
--- a/doc/administration/monitoring/performance/grafana_configuration.md
+++ b/doc/administration/monitoring/performance/grafana_configuration.md
@@ -141,7 +141,7 @@ sudo mv /var/opt/gitlab/grafana/data.bak.xxxx/ /var/opt/gitlab/grafana/data/
 
 However, you should **not** reinstate your old data _except_ under one of the following conditions:
 
-1. If you are certain that you changed your default admin password when you enabled Grafana; or
+1. If you are certain that you changed your default admin password when you enabled Grafana
 2. If you run GitLab in a private network, accessed only by trusted users, and your Grafana login page has not been exposed to the internet
 
 If you require access to your old Grafana data but do not meet one of these criteria, you may consider reinstating it temporarily, [exporting the dashboards](https://grafana.com/docs/reference/export_import/#exporting-a-dashboard) you need, then refreshing the data and [re-importing your dashboards](https://grafana.com/docs/reference/export_import/#importing-a-dashboard). Note that this poses a temporary vulnerability while your old Grafana data is in use, and the decision to do so should be weighed carefully with your need to access existing data and dashboards.