Fix typos and formatting.

Commit migrated from https://github.com/dotnet/corefx/commit/9a6f5b75f27e06eab32f4d9f4457a3c782645ab4

diff --git a/src/libraries/System.Text.Json/source_package/README.md b/src/libraries/System.Text.Json/source_package/README.md
index ff0b0b1..467e654 100644 (file)
--- a/src/libraries/System.Text.Json/source_package/README.md
+++ b/src/libraries/System.Text.Json/source_package/README.md
@@ -4,14 +4,14 @@
 
 * To support consumption of the `System.Text.Json` library outside of .NET Core 3.0+, we have produced a source package, `Microsoft.Bcl.Json.Sources`.
   - This package is unsupported and is only meant for advanced scenarios. Ideally, the project can target .NET Core 3.0 and get the inbox library.
-  - It is intentionally not easy to consume such a package since we avoided any tooling to predict the users intention. For simplicity, treat this like
-    any other source within your application or library. 
+  - It is intentionally not easy to consume such a package since we wanted to avoid any tooling or packaging magic to predict the user's intention.
+    For simplicity, we recommended that you treat this like any other source file within your application or library.
 
-## Common Known Issues and Workarounds
+## Known Issues and Workarounds
 
 ### Language Version
 
-* The `System.Text.Json` sources are built using C# 7.3 and hence you will likely see the following errors:
+* The `System.Text.Json` sources are built using C# 7.3 language features and hence you will likely see the following errors:
   - `error CS8107: Feature 'default literal' is not available in C# 7.0. Please use language version 7.1 or greater.`
   - `error CS8107: Feature 'ref structs' is not available in C# 7.0. Please use language version 7.2 or greater.`
   - `error CS8320: Feature 'extensible fixed statement' is not available in C# 7.2. Please use language version 7.3 or greater.`
@@ -42,6 +42,7 @@
 * Therefore, you will need to add the following package references in your project:
   - `<PackageReference Include="System.Runtime.CompilerServices.Unsafe" Version="..." />`
   - `<PackageReference Include="System.Memory" Version=..." />`
+  - The System.Memory package transitively brings in the other dependencies.
 
 ### CLS Compliance
 
@@ -49,22 +50,22 @@
   You might see warnings like the following (or errors if warnings are treated as errors):
   - `warning CS3021: 'Utf8JsonWriter.WriteNumber(string, ulong, bool)' does not need a CLSCompliant attribute because the assembly does not have a CLSCompliant attribute`
 
-* You could either mark your project as CLSCompliant, or opt out of this warning, or manually modify the sources to remove that attribute where it is used:
+* You could either mark your project as CLSCompliant, or opt-out of this particular warning, or manually modify the sources to remove that attribute where it is used:
   - `<NoWarn>3021</NoWarn>` OR `<CLSCompliant>true</CLSCompliant>`
 
 ### Targeting .NET Core 3.0+
 
 * The `System.Text.Json` library is built as part of .NET Core 3.0. If you reference this source package (unconditionally) and choose to target netcoreapp3.0 or higher,
-  you might see lots of type confligt warnings (or errors if warnings are treated as errors):
+  you might see lots of type conflict warnings (or errors if warnings are treated as errors):
   - `warning CS0436: The type 'JsonTokenType' in '...' conflicts with the imported type 'JsonTokenType' in 'System.Text.Json, Version=...'. Using the type defined in '...\microsoft.bcl.json.sources\...\JsonTokenType.cs'.`
 
 * You should not reference this package if you are targeting .NET Core 3.0 or higher. If you are multi-targeting, then only conditionally include the package reference.
-  Note that this applies to other package references that you include as part of the source package dependency.
+  Note that this applies to other package references that you include to fulfill the dependencies of the source package.
 
 ### PrivateAssets
 
 * It is recommended that you mark your package reference as private so that this dependency does not accidentally leak outside of your package
-  to applications that might be consuming it (for example, visible within the deps.json).
+  to applications that might be consuming it (for example, visible within the `deps.json`).
   ```csproj
   <PackageReference Include="Microsoft.Bcl.Json.Sources" Version="...">
      <PrivateAssets>All</PrivateAssets>