@@ -352,19 +352,20 @@ public DataSource createDataSource(ConnectionFactoryOptions options) {
352352 * as a strict directive to use TLS, and so it takes precedence over any value
353353 * that may otherwise be specified by the {@code PROTOCOL} option.
354354 * </p><p>
355- * If the {@code SSL} option is not set, then URL is composed with the any
355+ * If the {@code SSL} option is not set, then the URL is composed with any
356356 * value set for {@link ConnectionFactoryOptions#PROTOCOL} option. For
357357 * instance, if the {@code PROTOCOL} option is set to "ldap" then the URL
358- * is composed as: {@code jdbc:oracle:thins :@ldap://...}.
358+ * is composed as: {@code jdbc:oracle:thin :@ldap://...}.
359359 * </p><p>
360360 * For consistency with the Oracle JDBC URL, an Oracle R2DBC URL might include
361- * multiple space separated LDAP addresses, like this:
361+ * multiple space separated LDAP addresses, where the space is percent encoded,
362+ * like this:
362363 * <pre>
363364 * r2dbc:oracle:ldap://example.com:3500/cn=salesdept,cn=OracleContext,dc=com/salesdb%20ldap://example.com:3500/cn=salesdept,cn=OracleContext,dc=com/salesdb
364365 * </pre>
365366 * The %20 encoding of the space character must be used in order for
366367 * {@link ConnectionFactoryOptions#parse(CharSequence)} to recognize the URL
367- * syntax. When multiple address are specified this way, the {@code DATABASE}
368+ * syntax. When multiple addresses are specified this way, the {@code DATABASE}
368369 * option will have the value of:
369370 * <pre>
370371 * cn=salesdept,cn=OracleContext,dc=com/salesdb ldap://example.com:3500/cn=salesdept,cn=OracleContext,dc=com/salesdb
0 commit comments