typos (#943)

content/docs/operating/integrations.md

@@ -29,7 +29,7 @@ For service discovery mechanisms not natively supported by Prometheus,
 The [remote write](/docs/operating/configuration/#%3Cremote_write%3E) and [remote read](/docs/operating/configuration/#%3Cremote_read%3E)
 features of Prometheus allow transparently sending and receiving samples. This
 is primarily intended for long term storage. It is recommended that you perform
-careful evaulation of any solution in this space to confirm it can handle your
+careful evaluation of any solution in this space to confirm it can handle your
 data volumes.
 
   * [AppOptics](https://github.com/solarwinds/prometheus2appoptics): write

content/docs/operating/security.md

@@ -70,7 +70,7 @@ can send notifications to any email address. If the alert-defined destination
 is a templatable secret field, anyone with access to either Prometheus or
 Alertmanager will be able to view the secrets.
 
-Any secret fields which are templatable are intended for routing notifcations
+Any secret fields which are templatable are intended for routing notifications
 in the above use case. They are not intended as a way for secrets to be
 separated out from the configuration files using the template file feature. Any
 secrets stored in template files could be exfiltrated by anyone able to