Skip to content

Commit 8ed3f95

Browse files
authored
Merge pull request #211 from styfle/patch-1
docs: Fix minor typos in BestPractices.md
2 parents 00ef7c5 + 6c64e29 commit 8ed3f95

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/BestPractices.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22

33
## Environment Variables
44

5-
Run with `NODE_ENV` set to `production`. This is the way you would pass inn secrets and other runtime configurations to your application as well.
5+
Run with `NODE_ENV` set to `production`. This is the way you would pass in secrets and other runtime configurations to your application as well.
66

77
```
88
-e "NODE_ENV=production"
99
```
1010

1111
## Non-root User
1212

13-
By default Docker runs container as root which inside of the container can pose as a security issue. You would want to run the container as an unprivileged user wherever possible. This is however not supported out of the box with the `node` Docker image.
13+
By default, Docker runs container as root which inside of the container can pose as a security issue. You would want to run the container as an unprivileged user wherever possible. This is however not supported out of the box with the `node` Docker image.
1414

1515
```Dockerfile
1616
FROM node:4.1.2
@@ -26,7 +26,7 @@ This Docker Image can than be run with the `app` user in the following way:
2626

2727
#### Memory
2828

29-
By default any Docker Container may consume as much of the hardware such as CPU and RAM. If you are running multiple containers on the same host you should limit how much memory they can consume.
29+
By default, any Docker Container may consume as much of the hardware such as CPU and RAM. If you are running multiple containers on the same host you should limit how much memory they can consume.
3030

3131
```
3232
-m "300M" --memory-swap "1G"

0 commit comments

Comments
 (0)