From c2a0b6e7fe7d139a3ac8902045ca95650ad8a747 Mon Sep 17 00:00:00 2001
From: Georgios Andreadis <g.andreadis@student.tudelft.nl>
Date: Sat, 30 Sep 2017 12:50:47 +0200
Subject: Center-align component diagram in README

---
 README.md       | 12 +++++++-----
 opendc-frontend |  2 +-
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index d1f368a9..fee04a5b 100644
--- a/README.md
+++ b/README.md
@@ -1,10 +1,10 @@
 <h1 align="center">
-  <img src="images/logo.png" width="100" alt="OpenDC">
-  <br>
-  OpenDC
+    <img src="images/logo.png" width="100" alt="OpenDC">
+    <br>
+    OpenDC
 </h1>
 <p align="center">
-Collaborative Datacenter Simulation and Exploration for Everybody
+    Collaborative Datacenter Simulation and Exploration for Everybody
 </p>
 
 <br>
@@ -25,7 +25,9 @@ OpenDC is a project by the [@Large Research Group](http://atlarge-research.com).
 
 OpenDC consists of four components: a Kotlin simulator, a MariaDB database, a Python Flask web server, and a React.js frontend.
 
-![opendc-component-diagram](https://raw.githubusercontent.com/tudelft-atlarge/opendc/master/images/opendc-component-diagram.png)
+<p align="center">
+    <img src="https://raw.githubusercontent.com/tudelft-atlarge/opendc/master/images/opendc-component-diagram.png" alt="OpenDC Component Diagram">
+</p>
 
 On the frontend, users can construct a topology by specifying a datacenter's rooms, racks and machines, and create experiments to see how a workload trace runs on that topology. The frontend communicates with the web server over SocketIO, through a custom REST request/response layer. For example, the frontend might make a `GET` request to `/api/v1/users/{userId}`, but this request is completed via SocketIO, not plain HTTP requests.
 
diff --git a/opendc-frontend b/opendc-frontend
index 99ede1e1..f94906ca 160000
--- a/opendc-frontend
+++ b/opendc-frontend
@@ -1 +1 @@
-Subproject commit 99ede1e1515b2dcee5cabbfab4fd5f4db675a59f
+Subproject commit f94906ca30ff10ebd85961bfb3659faaaeb6ab2c
-- 
cgit v1.2.3