@@ -81,7 +81,7 @@ Hooking up the serializer is performed in the `ConnectionSettings` constructor
8181var pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
8282var connectionSettings = new ConnectionSettings(
8383 pool,
84- sourceSerializer: (builtin, settings) => new VanillaSerializer()); <1>
84+ sourceSerializer: (builtin, settings) => new VanillaSerializer()); <1>
8585var client = new ElasticClient(connectionSettings);
8686----
8787<1> what the Func?
@@ -171,7 +171,7 @@ public class MyFirstCustomJsonNetSerializer : ConnectionSettingsAwareSerializerB
171171}
172172----
173173
174- Using `MyCustomJsonNetSerializer `, we can serialize using
174+ Using `MyFirstCustomJsonNetSerializer `, we can serialize using
175175
176176* a Json.NET `NamingStrategy` that snake cases property names
177177
@@ -211,7 +211,7 @@ Hooking up the serializer and using it is as follows
211211var pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
212212var connectionSettings = new ConnectionSettings(
213213 pool,
214- connection: new InMemoryConnection(), <1>
214+ connection: new InMemoryConnection(), <1>
215215 sourceSerializer: (builtin, settings) => new MyFirstCustomJsonNetSerializer(builtin, settings))
216216 .DefaultIndex("my-index");
217217
@@ -289,7 +289,7 @@ public class MySecondCustomJsonNetSerializer : ConnectionSettingsAwareSerializer
289289 };
290290
291291 protected override ConnectionSettingsAwareContractResolver CreateContractResolver() =>
292- new MySecondCustomContractResolver(ConnectionSettings); <1>
292+ new MySecondCustomContractResolver(ConnectionSettings); <1>
293293}
294294----
295295<1> override the contract resolver
0 commit comments