From 0cb3c7e340c53d0ab8dbffa1958e71b64df5ad5f Mon Sep 17 00:00:00 2001
From: Nitesh Koushik S <39699046+NiteshKoushik@users.noreply.github.com>
Date: Mon, 12 Oct 2020 11:12:29 +0530
Subject: [PATCH] Grammar correction (#28179)

Grammar correction
---
 .../plugins/add-authentication-for-data-source-plugins.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/developers/plugins/add-authentication-for-data-source-plugins.md b/docs/sources/developers/plugins/add-authentication-for-data-source-plugins.md
index 455a8a8ddbb..fce221e72b8 100644
--- a/docs/sources/developers/plugins/add-authentication-for-data-source-plugins.md
+++ b/docs/sources/developers/plugins/add-authentication-for-data-source-plugins.md
@@ -6,7 +6,7 @@ aliases = ["/docs/grafana/latest/plugins/developing/auth-for-datasources/",  "/d
 
 # Add authentication for data source plugins
 
-This page explains how to use the Grafana data source proxy to authenticate against an third-party API from a data source plugin.
+This page explains how to use the Grafana data source proxy to authenticate against a third-party API from a data source plugin.
 
 When a user saves a password or any other sensitive data as a data source option, Grafana encrypts the data and stores it in the Grafana database. Any encrypted data source options can only be decrypted on the Grafana server. This means that any data source that makes authenticated queries needs to request the decrypted data to be sent to the browser.