fix(docs): make explicit the under-maintenance definition

juliomrqz · Jun 25, 2019 · b2a41c9 · b2a41c9
1 parent c23d4e1
commit b2a41c9
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/packages/docs/src/es/guide/incidents.md b/packages/docs/src/es/guide/incidents.md
@@ -218,6 +218,10 @@ Debe tener en cuenta que estas definiciones se manejan de manera diferente a los
 - Después que pase la fecha programada ([`scheduled`](#scheduled)), se debe establecer el campo [`resolved`](#resolved) en `true` si la ventana de mantenimiento ha finalizado.
 - Los Mantenimientos Programados no se muestran en la **Línea de Tiempo de Incidentes** ni en el **Historial de Incidentes** mientras no haya llegado la fecha programada ([`scheduled`](#scheduled)).
 
+::: warning IMPORTANTE
+Recuerda establecer el campo `severity` a `under-maintenance` (más información [aquí](#severity)) para considerar la definición de tu Mantenimiento Programado.
+:::
+
 ## Contenido
 
 El contenido de los Incidentes se escribe en un formato de Markdown válido, pero hay Extensiones adicionales que proporciona Statusfy.

diff --git a/packages/docs/src/guide/incidents.md b/packages/docs/src/guide/incidents.md
@@ -210,6 +210,10 @@ You must keep in mind that these definitions are handled in a different way than
 - After the [`scheduled`](#scheduled) date passes you must set the [`resolved`](#resolved) parameneter to `true` if the maintenance window has finished.
 - Scheduled Maintenances are not displayed in the **Incidents Timeline** and the **Incidents History** while the [`scheduled`](#scheduled) date has not arrived.
 
+::: warning IMPORTANT
+Remember to set the `severity` field to `under-maintenance` (more info [here](#severity)) in order to consider your Scheduled Maintenance definition.
+:::
+
 ## Content
 
 The content of the Incidents are written in a valid Markdown format but there are extra Extensions that Statusfy provides.