Tweak line ending troubleshooting

Author: Chuxel

docs/remote/troubleshooting.md

@@ -270,22 +270,24 @@ To change Docker's drive and folder sharing settings:
 
 ### Resolving Git line ending issues in containers (resulting in many modified files)
 
-Since Windows and Linux use different default line endings, you may see files that appear modified but seem to have no differences aside from the line endings. To prevent this from happening, you can disable automatic line ending conversion. Just add a `.gitattributes` file to your folder and then run:
+Since Windows and Linux use different default line endings, you may see files that appear modified but seem to have no differences aside from the line endings. To prevent this from happening, you can disable automatic line ending conversion and optionally add a `.gitattributes` file to your folder. First, run:
 
 ```bash
 git config --global core.autocrlf false
 ```
 
-You will need to re-clone the repository for this setting to take effect.
-
-Optionally, you can add the following contents to a `.gitattributes` file to force everything in the repo to use LF endings except for windows batch files that require CRLF:
+Next, you can prevent others from facing this issue regardless of their setting by adding or modifying a  `.gitattributes` file in your repository. For example, this will force everything to be LF except for Windows batch files that require CRLF:
 
 ```yaml
 *.* text eol=lf
 *.{cmd,[cC][mM][dD]} text eol=crlf
 *.{bat,[bB][aA][tT]} text eol=crlf
 ```
 
+You can add other file types in your repository that require CRLF to this same file.
+
+Finally, re-clone the repository for so these setting take effect.
+
 ### Avoid setting up Git in a container when using Docker Compose
 
 To avoid having to set up Git a second time in your container, VS Code automatically adds a volume mount to your local Git configuration when referencing an `image` or `Dockerfile`. The Docker Compose scenario gives you more control, but in this case requires adding an extra configuration line to your `docker-compose.yml` file.
@@ -528,22 +530,24 @@ Some extensions rely on libraries not found in the vanilla install of certain WS
 
 ### Resolving Git line ending issues in WSL (resulting in many modified files)
 
-Since Windows and Linux use different default line endings, you may see files that appear modified but seem to have no differences aside from the line endings. To prevent this from happening, you can disable automatic line ending conversion and add a `.gitattributes` file to your folder. Then run:
+Since Windows and Linux use different default line endings, you may see files that appear modified but seem to have no differences aside from the line endings. To prevent this from happening, you can disable automatic line ending conversion and optionally add a `.gitattributes` file to your folder. First, run:
 
 ```bash
 git config --global core.autocrlf false
 ```
 
-You will need to re-clone the repository for this setting to take effect.
-
-Optionally, you can add the following contents to a `.gitattributes` file to force everything to be LF except for windows batch files that require CRLF:
+Next, you can prevent others from facing this issue regardless of their setting by adding or modifying a  `.gitattributes` file in your repository. For example, this will force everything to be LF except for Windows batch files that require CRLF:
 
 ```yaml
 *.* text eol=lf
 *.{cmd,[cC][mM][dD]} text eol=crlf
 *.{bat,[bB][aA][tT]} text eol=crlf
 ```
 
+You can add other file types in your repository that require CRLF to this same file.
+
+Finally, re-clone the repository for so these setting take effect.
+
 ## Extension tips
 
 While many extensions will work unmodified, there are a few issues that can prevent certain features from working as expected. In some cases, you can use another command to work around the issue, while in others the extension may need to be modified. This section provides a quick reference for common issues and tips on resolving them. You can also refer to the main extension article on [Supporting Remote Development](/api/advanced-topics/remote-extensions) for an in-depth guide on modifying extensions when required.