From dbae842f9cef9153452c20a7c3d999e47d13da3e Mon Sep 17 00:00:00 2001 From: Moses <47298076+mo5e5@users.noreply.github.com> Date: Tue, 2 Mar 2021 07:51:54 +0200 Subject: [PATCH] Period omission at the end of line 7,8 and 10. The suggested bullet sign used "- " does not display Am using google chrome browser Version 88.0.4324.190 (Official Build) (64-bit) --- docs/tutorial/multi-container-apps/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/tutorial/multi-container-apps/index.md b/docs/tutorial/multi-container-apps/index.md index 68a0ed0..20d3ca4 100644 --- a/docs/tutorial/multi-container-apps/index.md +++ b/docs/tutorial/multi-container-apps/index.md @@ -4,12 +4,12 @@ application stack. The following question often arises - "Where will MySQL run? container or run it separately?" In general, **each container should do one thing and do it well.** A few reasons: -- There's a good chance you'd have to scale APIs and front-ends differently than databases -- Separate containers let you version and update versions in isolation +- There's a good chance you'd have to scale APIs and front-ends differently than databases. +- Separate containers let you version and update versions in isolation. - While you may use a container for the database locally, you may want to use a managed service for the database in production. You don't want to ship your database engine with your app then. - Running multiple processes will require a process manager (the container only starts one process), - which adds complexity to container startup/shutdown + which adds complexity to container startup/shutdown. And there are more reasons. So, we will update our application to work like this: