Skip to content

Commit 73aa74d

Browse files
committed
✏️ (Wording improvement) Remove wording that sounds like this is all easy
1 parent 3533b25 commit 73aa74d

File tree

2 files changed

+3
-3
lines changed
  • docs/docs/04_docker_intro

2 files changed

+3
-3
lines changed

docs/docs/04_docker_intro/01_what_is_docker_container/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Docker containers are a bit different because they don't emulate an Operating Sy
1010

1111
Containers have their own storage and networking, but because they don't have to emulate the operating system and everything that entails, they are much more lightweight and efficient. Another benefit of containers is that their start-up time is very fast.
1212

13-
Naturally, there's pros and cons to both. For example, you can't run a Windows Docker container if you are using Mac OS in your machine. You'd have to run a Windows Virtual Machine, and then run Docker containers in that, which isn't very efficient!
13+
There are pros and cons to both. For example, you can't run a Windows Docker container if you are using Mac OS in your machine. You'd have to run a Windows Virtual Machine, and then run Docker containers in that, which isn't very efficient!
1414

1515
:::caution
1616
Because Docker containers use your OS kernel, you can run Linux images in a Mac OS container.

docs/docs/04_docker_intro/04_in_depth_docker_tutorial/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ More info on this when we learn about deploying our app in production!
165165

166166
1. Create a `docker-compose.yml` file in the root of your project.
167167
2. Turn each of the `docker run` commands into a `service` in the `docker-compose.yml` file.
168-
3. This is basically re-creating the flags passed to the `docker run` command, but in YAML format.
168+
3. This is re-creating the flags passed to the `docker run` command, but in YAML format.
169169

170170
Example of the two `docker run`s above:
171171

@@ -205,7 +205,7 @@ Tear it down and remove the containers (but not the volumes) with `docker compos
205205

206206
## Caching in Dockerfile layers
207207

208-
Each layer (basically line of text) in a Dockerfile uses caching.
208+
Each layer (i.e. each line of text) in a Dockerfile uses caching.
209209

210210
That means that if Docker doesn't detect that a layer has changed, it won't re-run it. It'll use the last value / files that were generated for the last build.
211211

0 commit comments

Comments
 (0)