From 713699ccaa12db830c23f6e94c0d8213dbf7dd88 Mon Sep 17 00:00:00 2001 From: Wang Jie Date: Thu, 2 Mar 2017 04:25:59 +0800 Subject: [PATCH] Update work_issue.md (#2030) Change "re-start" to "restart". Though not included in "Prefered usages" in the documentation guide, but I think "restart" is better and used more frequently. Besides, some other docs here, such as "Keep containers alive during daemon downtime" of "Admin Guide", also use "restart". --- opensource/kitematic/work_issue.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/opensource/kitematic/work_issue.md b/opensource/kitematic/work_issue.md index 21acad2fca..e5d308ecf0 100644 --- a/opensource/kitematic/work_issue.md +++ b/opensource/kitematic/work_issue.md @@ -47,7 +47,7 @@ To do this, edit the container `General Settings` layout. ![Javascript to display container id in kitematic](images/settings-code-example.png) -5. Save the code changes, re-start Kitematic. +5. Save the code changes, restart Kitematic. ``` $ npm start @@ -77,4 +77,4 @@ To do this, edit the container `General Settings` layout. ## Where to go next -At this point, you are ready to [Review your branch and create a pull request](create_pr.md) to merge your new feature into Kitematic. \ No newline at end of file +At this point, you are ready to [Review your branch and create a pull request](create_pr.md) to merge your new feature into Kitematic.