Incorporating more of trloft's changes

Author: jschalz

docs/pages/configuration/dev/files/sync.mdx

@@ -277,9 +277,9 @@ dev:
 ```
 
 ### `onUpload.exec`
-The `onUpload.exec` option defines command(s) that should be executed after DevSpace uploaded files and folder to the container. DevSpace will make sure that those commands are not executed while initially syncing the state and command execution will also halt any syncing activities.
+The `onUpload.exec` option defines command(s) that should be executed after DevSpace uploaded files and folder to the container. DevSpace will ensure that those commands are not executed while initially syncing the state, and command execution will also halt any syncing activities.
 
-If this is defined together with `onUpload.restartContainer`, DevSpace will make sure that the commands are always executed **before** the container is restarted.
+If this is defined together with `onUpload.restartContainer`, DevSpace will ensure that the commands are always executed **before** the container is restarted.
 
 #### Example: Post-Upload Commands
 ```yaml {14-29}
@@ -373,7 +373,7 @@ dev:
 
 ### `noWatch`
 
-If the `noWatch` option is specified, DevSpace will stop syncing after initially comparing and resolving differences. This is useful if you want a one-time sync but then continue doing other steps in your pipeline.
+If the `noWatch` option is specified, DevSpace will stop syncing after initially comparing and resolving differences. This is useful if you want a one-time sync, but then continue doing other steps in your pipeline.
 
 ### `initialSync`
 The `initialSync` option expects a string with an initial sync strategy. The following strategies are available:
@@ -431,11 +431,11 @@ dev:
       initialSync: preferRemote
 ```
 **Explanation:**
-With this configuration, `devspace dev` would do the following:
+With this configuration, `devspace dev` performs the following tasks:
 - DevSpace would start port-forwarding and file synchronzation.
 - Initial sync is started automatically.
-- The first sync config section would synchronize all files except files within `node_modules/`. This means that during initial sync, all remote files that are not existing locally would be deleted and other files would be updated to the most recent version.
-- The second sync config section would only synchronize files within `node_modules/` and because of `initialSync: preferRemote`, DevSpace would download all remote files which are not present on the local filesystem and override all local files which are different than the files within the container.
+- The first sync config section synchronizes all files except files within `node_modules/`. This means that during initial sync, all remote files that do not already exist locally are deleted, and other files are updated to the most recent version.
+- The second sync config section only synchronizes files within `node_modules/`. Because of `initialSync: preferRemote`, DevSpace downloads all remote files which are not present on the local filesystem and overrides all local files which are different than the files within the container.
 
 ### `waitInitialSync`
 The `waitInitialSync` option expects a boolean which defines if DevSpace should wait until the initial sync process has terminated before opening the container terminal or the multi-container log streaming.
@@ -463,8 +463,8 @@ dev:
       waitInitialSync: false
 ```
 **Explanation:**
-With the configuration `devspace dev` would do the following:
-- DevSpace would start port-forwarding and file synchronzation.
+With the configuration `devspace dev` the following actions will be taken:
+- DevSpace initiates port-forwarding and file synchronization.
 - Initial sync would be started automatically.
 
 - Before the initial sync process is finished, DevSpace starts the log streaming.