Rename duplicate asciidoc documentation id

Author: russcam

src/Nest/Mapping/Types/Core/Join/JoinField.cs

@@ -2,13 +2,14 @@
 
 namespace Nest
 {
-	/// This does not extend from Union because its intended to be used on folk's _source's
-	/// And the union serialization will bleed into their own JSON.NET serializer should they
-	/// have one configured and then it will blow up because their contractresolver do not extend ours
-	/// from which we can snoop ConnectionSettings.
-	///
-	/// ContractJsonResolverAttribute works as well but I rather keep this class contained as much as possible
-	///
+	// This does not extend from Union because its intended to be used on folk's _source's
+	// And the union serialization will bleed into their own JSON.NET serializer should they
+	// have one configured and then it will blow up because their contractresolver do not extend ours
+	// from which we can snoop ConnectionSettings.
+	//
+	// ContractJsonResolverAttribute works as well but I rather keep this class contained as much as possible
+	/// <summary>
+	/// The field on which a parent-child relationship is joined
 	/// </summary>
 	[ContractJsonConverter(typeof(JoinFieldJsonConverter))]
 	public class JoinField

src/Tests/ClientConcepts/HighLevel/Mapping/ParentChildJoins.doc.cs

@@ -12,22 +12,21 @@
 
 namespace Tests.ClientConcepts.HighLevel.Mapping
 {
-	/**[[multi-fields]]
+	/**[[parent-child-joins]]
 	* === Parent Child joins using the join mapping
 	*
 	* Prior to Elasticsearch 6.x you could have multiple types in a single index. Through the special _parent field mapping of a given type
 	* one could create 1 to N relationship of parent => children documents. This worked because when indexing children you passed a
 	* `_parent` id which would act as the routing key making sure a parent and its (grand)children all lived on the same shard.
 	*
-	* Starting with 6.x indices you may no longer have multiple types in a single index. One reason for this is that if for instance
+	* Starting with 6.x indices, you may no longer have multiple types in a single index. One reason for this is that if for instance
 	* two types * have the same `name` property they need to be mapped exactly the same but all the API's acted as if you could map
 	* them individually which often lead to confusion.
 	*
 	* So how do you create a parent join now that indices no longer allow you store different types in the same index and therefor also
 	* not on the same shard?
 	*
 	*/
-
 	public class ParentChildJoins : DocumentationTestBase
 	{
 		public abstract class MyDocument
@@ -79,8 +78,6 @@ public void SimpleParentChildMapping()
 					)
 				);
 
-			/**
-			 */
 			//json
 			var expected = new
 			{