Document change (#27808)

Change in keyword "cryptogtraphic" to "cryptographic"

Document change (#27808)
Change in keyword "cryptogtraphic" to "cryptographic"
14895aea · Nitesh Koushik S · GitHub · 4da2fa99 · 14895aea
Commit 14895aea authored Sep 25, 2020 by Nitesh Koushik S Committed by GitHub Sep 25, 2020
Show whitespace changes
Inline Side-by-side

Showing with 1 additions and 1 deletions

docs/sources/administration/image_rendering.md
+1 -1

No files found.
--- a/docs/sources/administration/image_rendering.md
+++ b/docs/sources/administration/image_rendering.md
@@ -178,7 +178,7 @@ libXcomposite libXdamage libXtst cups libXScrnSaver pango atk adwaita-cursor-the

 ### Certificate signed by internal certificate authorities

-In many cases, Grafana runs on internal servers and uses certificates that have not been signed by a CA ([Certificate Authority](https://en.wikipedia.org/wiki/Certificate_authority)) known to Chrome, and therefore cannot be validated. Chrome internally uses NSS ([Network Security Services](https://en.wikipedia.org/wiki/Network_Security_Services)) for cryptogtraphic operations such as the validation of certificates.
+In many cases, Grafana runs on internal servers and uses certificates that have not been signed by a CA ([Certificate Authority](https://en.wikipedia.org/wiki/Certificate_authority)) known to Chrome, and therefore cannot be validated. Chrome internally uses NSS ([Network Security Services](https://en.wikipedia.org/wiki/Network_Security_Services)) for cryptographic operations such as the validation of certificates.

 If you are using the Grafana Image Renderer with a Grafana server that uses a certificate signed by such a custom CA (for example a company-internal CA), rendering images will fail and you will see messages like this in the Grafana log: