From 39249b9296608d81e32da86b6aec889a4ed688a5 Mon Sep 17 00:00:00 2001 From: Ruffin Date: Wed, 12 Aug 2015 11:25:18 -0700 Subject: [PATCH] rm whitespace --- ros/content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ros/content.md b/ros/content.md index 34829a509..6009b32a6 100644 --- a/ros/content.md +++ b/ros/content.md @@ -55,7 +55,7 @@ The ROS runtime "graph" is a peer-to-peer network of processes (potentially dist ## Deployment example -**NOTE:** This requires the experimental version of Docker for future networking features. +**NOTE:** This requires the experimental version of Docker for future networking features. If we want our all ROS nodes to easily talk to each other, we'll can use a virtual network to connect the separate containers. In this short example, we'll create a virtual network, spin up a new container running `roscore` advertised as the `master` service on the new network, then spawn a message publisher and subscriber process as services on the same network. ### Build image