From 3c5a8dd8ddeaa4e893add0787874297c2f7d8a61 Mon Sep 17 00:00:00 2001 From: Michael Bridgen Date: Tue, 11 Dec 2018 17:54:32 +0000 Subject: [PATCH] Make it clear Slack integration uses a service Here I am trying to walk the line between giving accurate advice, and recognising that the notifications are particular to Weave Cloud (albeit fluxcloud can also do something with them). Fixes #1587. --- site/introduction.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/site/introduction.md b/site/introduction.md index 2ed6f248e..063dd5d1b 100644 --- a/site/introduction.md +++ b/site/introduction.md @@ -52,14 +52,14 @@ version. ## Integrations with other devops tools -One final high level feature is that Flux increases visibility of -your application. It provides an audit history for -your deployments and Slack integration for "ChatOps" style -development. - -Clear visibility of the state of a cluster is key for maintaining -operational systems. Developers can be confident in their changes by -observing a predictable series of deployment events. +One final high-level feature is that Flux increases visibility of your +application. Clear visibility of the state of a cluster is key for +maintaining operational systems. Developers can be confident in their +changes by observing a predictable series of deployment events. + +Flux can send notifications to a service (e.g., [Weave +Cloud](https://cloud.weave.works/)) to provide integrations with Slack +and other such media. ## Next