[MINOR][DOCS] Fix typos in docs/sql-data-sources-jdbc.md

### What changes were proposed in this pull request?

This PR aims to fix typos in `docs/sql-data-sources-jdbc.md`.

### Why are the changes needed?

Fix typos.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

After removing the redundant </td>, the markdown preview displays normally.
<img width="1155" alt="image" src="https://github.com/user-attachments/assets/7818012f-93ef-44f2-87d2-6587867238b6" />

### Was this patch authored or co-authored using generative AI tooling?

No.

Closes #49700 from wayneguow/jdbc_doc.

Authored-by: Wei Guo <[email protected]>
Signed-off-by: Dongjoon Hyun <[email protected]>

docs/sql-data-sources-jdbc.md

@@ -229,9 +229,9 @@ logging into the data sources.
     <td><code>truncate</code></td>
     <td><code>false</code></td>
     <td>
-      This is a JDBC writer related option. When <code>SaveMode.Overwrite</code> is enabled, this option causes Spark to truncate an existing table instead of dropping and recreating it. This can be more efficient, and prevents the table metadata (e.g., indices) from being removed. However, it will not work in some cases, such as when the new data has a different schema. In case of failures, users should turn off <code>truncate</code> option to use <code>DROP TABLE</code> again. Also, due to the different behavior of <code>TRUNCATE TABLE</code> among DBMS, it's not always safe to use this. MySQLDialect, DB2Dialect, MsSqlServerDialect, DerbyDialect, and OracleDialect supports this while PostgresDialect and default JDBCDirect doesn't. For unknown and unsupported JDBCDirect, the user option <code>truncate</code> is ignored.
+      This is a JDBC writer related option. When <code>SaveMode.Overwrite</code> is enabled, this option causes Spark to truncate an existing table instead of dropping and recreating it. This can be more efficient, and prevents the table metadata (e.g., indices) from being removed. However, it will not work in some cases, such as when the new data has a different schema. In case of failures, users should turn off <code>truncate</code> option to use <code>DROP TABLE</code> again. Also, due to the different behavior of <code>TRUNCATE TABLE</code> among DBMSes, it's not always safe to use this. MySQLDialect, DB2Dialect, MsSqlServerDialect, DerbyDialect, and OracleDialect supports this while PostgresDialect and default JDBCDialect doesn't. For unknown and unsupported JDBCDialect, the user option <code>truncate</code> is ignored.
+    </td>
     <td>write</td>
-   </td>
   </tr>
 
   <tr>