From e29b8f58f19c1ecc09f098249510f172f548f2ca Mon Sep 17 00:00:00 2001 From: V-V Date: Tue, 11 Sep 2018 07:25:36 +0300 Subject: [PATCH] Grammatical fixes in docker/README.md --- docker/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker/README.md b/docker/README.md index b30df3e..e0f71f1 100644 --- a/docker/README.md +++ b/docker/README.md @@ -24,8 +24,8 @@ docker run -ti --rm orbit-db npm run examples:node ## Why would you want to run OrbitDB in container? Containers are nice because as software execution environments they are: -- Reproducible, which helps testing and development because you can revert container to original state by destroying it and creating it again, -- Isolated, which guarantees that external factors like npm versions, operating system version, or other installed software like native compilers do not affect the execution. +- Reproducible, which helps testing and development because you can revert the container to original state by destroying it and creating it again, +- Isolated, which guarantees that external factors like npm versions, the operating system version, or other installed software like native compilers do not affect the execution. They also make implementing virtualized networks for testing and benchmarking easier, which may help projects that use OrbitDB.