Softened line ending statement

Author: Chuxel

docs/remote/containers.md

@@ -31,7 +31,7 @@ To get started, follow these steps:
 
     2. Right-click on the Docker taskbar item and update **Settings / Preferences > Shared Drives / File Sharing** with any source code locations you want to open in a container. If you run into trouble, see [Docker Desktop for Windows tips](/docs/remote/troubleshooting.md#docker-desktop-for-windows-tips) on avoiding common problems with sharing.
 
-    3. **Windows**: Disable automatic line ending conversion for Git by using a Windows command prompt to run: `git config --global core.autocrlf false` (If left enabled, this setting can cause files that you have not edited to appear modified due to line ending differences.)
+    3. **Windows**: Consider disabling automatic line ending conversion for Git on the **Windows side** by using a command prompt to run: `git config --global core.autocrlf false` If left enabled, this setting can cause files that you have not edited to appear modified due to line ending differences. See [tips and tricks](/docs/remote/troubleshooting.md#resolving-git-line-ending-issues-in-containers-resulting-in-many-modified-filess) for details.
 
     **Linux**:
 

docs/remote/troubleshooting.md

@@ -276,6 +276,12 @@ Since Windows and Linux use different default line endings, you may see files th
 git config --global core.autocrlf false
 ```
 
+This will disable automated conversation. If you would prefer to still always upload Unix-style line endings (LF), you can use the `input` option instead.
+
+```bash
+git config --global core.autocrlf input
+```
+
 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
@@ -536,6 +542,12 @@ Since Windows and Linux use different default line endings, you may see files th
 git config --global core.autocrlf false
 ```
 
+This will disable automated conversation. If you would prefer to still always upload Unix-style line endings (LF), you can use the `input` option instead.
+
+```bash
+git config --global core.autocrlf input
+```
+
 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

docs/remote/wsl.md

@@ -31,7 +31,7 @@ To get started you need to:
 
 3. Install the [Remote Development](https://aka.ms/vscode-remote/download/extension) extension pack.
 
-4. Disable automatic line ending conversion for Git on the **Windows side** by using a command prompt to run: `git config --global core.autocrlf false` (If left enabled, this setting can cause files that you have not edited to appear modified due to line ending differences.)
+4. Consider disabling automatic line ending conversion for Git on the **Windows side** by using a command prompt to run: `git config --global core.autocrlf false` If left enabled, this setting can cause files that you have not edited to appear modified due to line ending differences. See [tips and tricks](/docs/remote/troubleshooting.md#resolving-git-line-ending-issues-in-wsl-resulting-in-many-modified-files) for details.
 
 ### Open a folder in WSL