Updated Xmldocs (#3518)

* Updated Xmldocs

Updated Xmldocs to clarify that exceptions are not thrown for bulk actions.

* Updated ThrowExceptions XmlDocs to explicitly mark an exception for SuccessOrKnownError

Author: KPStolk

src/Elasticsearch.Net/Configuration/ConnectionConfiguration.cs

@@ -279,7 +279,7 @@ public T EnableTcpKeepAlive(TimeSpan keepAliveTime, TimeSpan keepAliveInterval)
 		public T DisableAutomaticProxyDetection(bool disable = true) => Assign(a => a._disableAutomaticProxyDetection = disable);
 
 		/// <summary>
-		/// Instead of following a c/go like error checking on response.IsValid always throw an exception
+		/// Instead of following a c/go like error checking on response.IsValid do throw an exception (except when <see cref="IApiCallDetails.SuccessOrKnownError"/> is false)
 		/// on the client when a call resulted in an exception on either the client or the Elasticsearch server.
 		/// <para>Reasons for such exceptions could be search parser errors, index missing exceptions, etc...</para>
 		/// </summary>

src/Elasticsearch.Net/Configuration/IConnectionConfigurationValues.cs

@@ -206,7 +206,7 @@ public interface IConnectionConfigurationValues : IDisposable
 		bool SniffsOnStartup { get; }
 
 		/// <summary>
-		/// Instead of following a c/go like error checking on response.IsValid always throw an exception
+		/// Instead of following a c/go like error checking on response.IsValid do throw an exception (except when <see cref="IApiCallDetails.SuccessOrKnownError"/> is false)
 		/// on the client when a call resulted in an exception on either the client or the Elasticsearch server.
 		/// <para>Reasons for such exceptions could be search parser errors, index missing exceptions, etc...</para>
 		/// </summary>

src/Elasticsearch.Net/Configuration/RequestConfiguration.cs

@@ -88,7 +88,7 @@ public interface IRequestConfiguration
 		string RunAs { get; set; }
 
 		/// <summary>
-		/// Instead of following a c/go like error checking on response.IsValid always throw an exception
+		/// Instead of following a c/go like error checking on response.IsValid do throw an exception (except when <see cref="IApiCallDetails.SuccessOrKnownError"/> is false)
 		/// on the client when a call resulted in an exception on either the client or the Elasticsearch server.
 		/// <para>Reasons for such exceptions could be search parser errors, index missing exceptions, etc...</para>
 		/// </summary>