update documentation pointing to aggs vs aggregations which no longer is a section because the property no longer exists

Author: Mpdreamz

src/Tests/Aggregations/Bucket/DateHistogram/DateHistogramAggregationUsageTests.cs

@@ -110,8 +110,9 @@ public DateHistogramAggregationUsageTests(ReadOnlyCluster i, EndpointUsage usage
 		protected override void ExpectResponse(ISearchResponse<Project> response)
 		{
 			/** === Handling responses
-			* Using the `.Aggs` aggregation helper on `ISearchResponse<T>`, we can fetch our aggregation results easily
-			* in the correct type. <<aggs-vs-aggregations, Be sure to read more about .Aggs vs .Aggregations>>
+			* The `AggregateDictionary found on `.Aggregations` on `ISearchResponse<T>` has several helper methods
+			* so we can fetch our aggregation results easily in the correct type.
+			 * <<handling-aggregate-response, Be sure to read more about these helper methods>>
 			*/
 			response.ShouldBeValid();
 

src/Tests/Aggregations/Bucket/DateRange/DateRangeAggregationUsageTests.cs

@@ -77,8 +77,9 @@ public DateRangeAggregationUsageTests(ReadOnlyCluster i, EndpointUsage usage) :
 		protected override void ExpectResponse(ISearchResponse<Project> response)
 		{
 			/** === Handling Responses
-			* Using the `.Agg` aggregation helper we can fetch our aggregation results easily
-			* in the correct type. <<aggs-vs-aggregations, Be sure to read more about .Aggs vs .Aggregations>>
+			* The `AggregateDictionary found on `.Aggregations` on `ISearchResponse<T>` has several helper methods
+			* so we can fetch our aggregation results easily in the correct type.
+			 * <<handling-aggregate-response, Be sure to read more about these helper methods>>
 			*/
 			response.ShouldBeValid();
 

src/Tests/Aggregations/Bucket/Filter/FilterAggregationUsageTests.cs

@@ -60,8 +60,9 @@ public FilterAggregationUsageTests(ReadOnlyCluster i, EndpointUsage usage) : bas
 		protected override void ExpectResponse(ISearchResponse<Project> response)
 		{
 			/** === Handling Responses
-			* Using the `.Aggs` aggregation helper we can fetch our aggregation results easily
-			* in the correct type. <<aggs-vs-aggregations, Be sure to read more about .Aggs vs .Aggregations>>
+			* The `AggregateDictionary found on `.Aggregations` on `ISearchResponse<T>` has several helper methods
+			* so we can fetch our aggregation results easily in the correct type.
+			 * <<handling-aggregate-response, Be sure to read more about these helper methods>>
 			*/
 			response.ShouldBeValid();
 

src/Tests/Aggregations/Bucket/Filters/FiltersAggregationUsageTests.cs

@@ -81,8 +81,9 @@ public FiltersAggregationUsageTests(ReadOnlyCluster i, EndpointUsage usage) : ba
 		protected override void ExpectResponse(ISearchResponse<Project> response)
 		{
 			/** ==== Handling Responses
-			* Using the `.Agg` aggregation helper we can fetch our aggregation results easily
-			* in the correct type. <<aggs-vs-aggregations, Be sure to read more about .Aggs vs .Aggregations>>
+			* The `AggregateDictionary found on `.Aggregations` on `ISearchResponse<T>` has several helper methods
+			* so we can fetch our aggregation results easily in the correct type.
+			 * <<handling-aggregate-response, Be sure to read more about these helper methods>>
 			*/
 			response.ShouldBeValid();
 
@@ -165,8 +166,9 @@ public AnonymousFiltersUsage(ReadOnlyCluster i, EndpointUsage usage) : base(i, u
 		protected override void ExpectResponse(ISearchResponse<Project> response)
 		{
 			/** ==== Handling Responses
-			* Using the `.Agg` aggregation helper we can fetch our aggregation results easily
-			* in the correct type. <<aggs-vs-aggregations, Be sure to read more about .Aggs vs .Aggregations>>
+			* The `AggregateDictionary found on `.Aggregations` on `ISearchResponse<T>` has several helper methods
+			* so we can fetch our aggregation results easily in the correct type.
+			 * <<handling-aggregate-response, Be sure to read more about these helper methods>>
 			*/
 			response.ShouldBeValid();
 

src/Tests/Aggregations/WritingAggregations.doc.cs

@@ -250,7 +250,6 @@ protected override Func<SearchDescriptor<Project>, ISearchRequest> Fluent
 	}
 
 
-	//todo own documentation file (aggregation responses?)
 	/**[float]
 	* [[Aggregate]]
 	*=== Handling aggregate response