Skip to content

Commit 9e34b04

Browse files
Clarify OCI_REGION usage beyond gov regions in documentation
1 parent 2ce01db commit 9e34b04

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

ojdbc-provider-oci/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -296,7 +296,7 @@ The following parameters can be used alongside any supported authentication meth
296296
<td><code>OCI_REGION</code></td>
297297
<td>
298298
Specifies the OCI Region Identifier to be used for requests and interactive authentication.
299-
This is especially important in government or non-OC1 regions to ensure authentication is routed correctly.<br>
299+
This allows targeting a specific region for login, which is especially useful when the region differs from the default behavior.<br>
300300
<i>For example, specifying <code>us-langley-1</code> will direct the login to
301301
<code>https://login.us-langley-1.oraclegovcloud.com/</code></i>
302302
</td>
@@ -306,7 +306,7 @@ The following parameters can be used alongside any supported authentication meth
306306
</td>
307307
<td>
308308
<i>If not provided, the login URL will default to <code>https://login.oci.oraclecloud.com</code>,
309-
which may not work for gov regions.</i>
309+
which may not work for your target region.</i>
310310
</td>
311311
</tr>
312312
</tbody>

0 commit comments

Comments
 (0)