Fix typo in ephemeral FS in docker

Solve conflict in information between lines 3 and 9
"stopped (and) removed" in line 3
"stopped (or) removed" in line 9

src/data/roadmaps/docker/content/104-data-persistence/100-ephemeral-container-fs.md

@@ -6,12 +6,12 @@ This temporary or short-lived storage is called the "ephemeral container file sy
 
 ### Ephemeral FS and Data Persistence
 
-As any data stored within the container's ephemeral FS is lost when the container is stopped or removed, it poses a challenge to data persistence in applications. This is especially problematic for applications like databases, which require data to be persisted across multiple container life cycles.
+As any data stored within the container's ephemeral FS is lost when the container is stopped and removed, it poses a challenge to data persistence in applications. This is especially problematic for applications like databases, which require data to be persisted across multiple container life cycles.
 
 To overcome these challenges, Docker provides several methods for data persistence, such as:
 
 - **Volumes**: A Docker managed storage option, stored outside the container's FS, allowing data to be persisted across container restarts and removals.
 - **Bind mounts**: Mapping a host machine's directory or file into a container, effectively sharing host's storage with the container.
 - **tmpfs mounts**: In-memory storage, useful for cases where just the persistence of data within the life-cycle of the container is required.
 
-By implementing these strategies, Docker ensures that application data can be preserved beyond the life-cycle of a single container, making it possible to work with stateful applications.
+By implementing these strategies, Docker ensures that application data can be preserved beyond the life-cycle of a single container, making it possible to work with stateful applications.