diff --git a/docs/sources/alerting/rules.md b/docs/sources/alerting/rules.md
index a30bf885650..ecab88f48d2 100644
--- a/docs/sources/alerting/rules.md
+++ b/docs/sources/alerting/rules.md
@@ -73,7 +73,7 @@ in the scenario below.
 - No new notifications are sent as the alert rule is already in state `Alerting`.
 
 So as you can see from the above scenario Grafana will not send out notifications when other series cause the alert
-to fire if the rule already is in state ´Alerting`. To improve support for queries that return multiple series
+to fire if the rule already is in state `Alerting`. To improve support for queries that return multiple series
 we plan to track state **per series** in a future release.
 
 ### No Data / Null values
@@ -107,6 +107,12 @@ The message can contain anything, information about how you might solve the issu
 The actual notifications are configured and shared between multiple alerts. Read the
 [Notifications]({{< relref "notifications.md" >}}) guide for how to configure and setup notifications.
 
+## Alert State History & Annotations
+
+Alert state changes are recorded in the internal annotation table in Grafana's database. The state changes
+are visualized as annotations in the alert rule's graph panel. You can also go into the `State history`
+submenu in the alert tab to view & clear state history.
+
 ## Troubleshooting
 
 {{< imgbox max-width="40%" img="/img/docs/v4/alert_test_rule.png" caption="Test Rule" >}}
diff --git a/public/sass/pages/_alerting.scss b/public/sass/pages/_alerting.scss
index abe8c775415..b739485f170 100644
--- a/public/sass/pages/_alerting.scss
+++ b/public/sass/pages/_alerting.scss
@@ -50,7 +50,6 @@
 
 .panel-alert-state {
   &--alerting {
-    background-color: mix($critical,$panel-bg, 3%);
     animation: alerting-panel 1.6s cubic-bezier(1,.1,.73,1) 0s infinite alternate;
     box-shadow: 0 0 10px rgba($critical,0.5);
     opacity: 1;