Update build badge (#1957)

* [DRAFT] Update build badge

(Can't create draft PR while authoring a change using GitHub.com, too lazy to do on my box.)

* Update README.md

README.md

@@ -3,15 +3,16 @@
 ### [Click here to find out what's new for //build2019!](https://github.com/Microsoft/botframework/blob/master/whats-new.md#whats-new)
 
 # Bot Framework Web Chat
-<a href="https://badge.fury.io/js/botframework-webchat"><img alt="npm version" src="https://badge.fury.io/js/botframework-webchat.svg" /></a>
-[![Build Status](https://fuselabs.visualstudio.com/BotFramework-WebChat/_apis/build/status/BotFramework-WebChat-CI-PR?branchName=master)](https://fuselabs.visualstudio.com/BotFramework-WebChat/_build/latest?definitionId=510&branchName=master)
-[![Coverage Status](https://coveralls.io/repos/github/Microsoft/BotFramework-WebChat/badge.svg?branch=master)](https://coveralls.io/github/Microsoft/BotFramework-WebChat?branch=master)
+<p align="center">
+  <a href="https://badge.fury.io/js/botframework-webchat"><img alt="npm version" src="https://badge.fury.io/js/botframework-webchat.svg" /></a>
+  <img alt="Build Status" src="https://fuselabs.visualstudio.com/BotFramework-WebChat/_apis/build/status/BotFramework-WebChat-daily?branchName=master" />
+  <a href="https://coveralls.io/github/Microsoft/BotFramework-WebChat?branch=master"><img src="https://coveralls.io/repos/github/Microsoft/BotFramework-WebChat/badge.svg?branch=master" alt="Coverage Status" /></a>
+</p>
 
 This repository contains code for the Bot Framework Web Chat component.  The Bot Framework Web Chat component is a highly-customizable web-based client for the Bot Framework V4 SDK. The Bot Framework SDK v4 enable developers to model conversation and build sophisticated bot applications.
 
 This repo is part of the [Microsoft Bot Framework](https://github.com/microsoft/botframework) - a comprehensive framework for building enterprise-grade conversational AI experiences.
 
-
 ## Migrating from Web Chat v3 to v4
 
 There are three possible paths that migration might take when migrating from v3 to v4. First, please compare your beginning scenario: