From 06b64eab0eb0f221e34cbe7ebbe5baaf41124f8c Mon Sep 17 00:00:00 2001
From: Tom Dykstra <tdykstra@microsoft.com>
Date: Thu, 9 Jan 2020 19:59:22 -0800
Subject: [PATCH] Replace "tools" with "APIs"

---
 .../DataContractJsonSerializer.xml                              | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml b/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml
index 972b9b95f41..a25aa9ec487 100644
--- a/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml
+++ b/xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml
@@ -42,7 +42,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks 
- For most scenarios that involve serializing to JSON and deserializing from JSON, we recommend the [tools in the System.Text.Json namespace](/dotnet/standard/serialization/system-text-json-overview). 
+ For most scenarios that involve serializing to JSON and deserializing from JSON, we recommend the [APIs in the System.Text.Json namespace](/dotnet/standard/serialization/system-text-json-overview). 
  
  If your scenario requires the <xref:System.Runtime.Serialization.Json.DataContractJsonSerializer> class, you can use it to serialize instances of a type into a JSON document and to deserialize a JSON document into an instance of a type. For example, you can create a type named `Person` with properties that contain essential data, such as a name and address. You can then create and manipulate an instance of the `Person` class and write all of its property values in a JSON document for later retrieval. This JSON document can later be deserialized into the `Person` class or another class with an equivalent data contract.