Merge pull request #32410 from rwestMSFT/rw-1114-fix-9928

[SCOPED] Fix typos (PR 9928)

Author: v-regandowner

azure-sql/managed-instance/replication-transactional-overview.md

@@ -212,12 +212,12 @@ If a **subscriber** SQL managed instance is in a failover group, the publication
 
 ### Transaction log and Transactional Replication
 
-In usual circumstances, transcation log is used for recording changes of the data within a database. Changes are recorded in the transaction log, and that makes the log storage consumption to grow. There's also an automatic process that allows safe truncation of the transaction log, and this process reduces the used storage space for the log.
+In usual circumstances, transaction log is used for recording changes of the data within a database. Changes are recorded in the transaction log, and that makes the log storage consumption to grow. There's also an automatic process that allows safe truncation of the transaction log, and this process reduces the used storage space for the log.
 When publishing for Transactional Replication is configured, transaction log truncation is prevented until changes in the log are processed by the log reader job. In some circumstances, processing of the transaction log is effectively blocked, and that state can lead to filling up entire storage reserved for transaction log. When there's no free space for transaction log, and there's no more space for transaction log to grow, we have full transaction log. In this state, the database can no longer process any write workload, and effectively becomes read-only database. 
 
 #### Disabled log reader agent
 
-Sometimes Transactional Replication publication is configured for a database, but log reader agent isn't configured to run. In that case, changes are accumulating in the transaction log, and they aren't being processed. This leads to constant growth of transactional log, and eventually to the full transcation log.
+Sometimes Transactional Replication publication is configured for a database, but log reader agent isn't configured to run. In that case, changes are accumulating in the transaction log, and they aren't being processed. This leads to constant growth of transactional log, and eventually to the full transaction log.
 User should make sure that log reader job exists and is active. Alternative would be to disable Transactional Replication, if it's not needed.
 
 #### Log reader agent query timeouts

docs/connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md

@@ -779,7 +779,7 @@ The `SQLServerBulkCopy` class can be used to write data only to SQL Server table
 | `boolean isTableLock()` | Indicates whether `SQLServerBulkCopy` should obtain a bulk update lock for the duration of the bulk copy operation. |
 | `void setTableLock(boolean tableLock)` | Sets whether `SQLServerBulkCopy` should obtain a bulk update lock for the duration of the bulk copy operation. |
 | `boolean isUseInternalTransaction()` | Indicates whether each batch of the bulk-copy operation will occur within a transaction. |
-| `void setUseInternalTranscation(boolean useInternalTransaction)` | Sets whether each batch of the bulk-copy operations will occur within a transaction or not. |
+| `void setUseInternalTransaction(boolean useInternalTransaction)` | Sets whether each batch of the bulk-copy operations will occur within a transaction or not. |
 | `int getBatchSize()` | Gets the number of rows in each batch. At the end of each batch, the rows in the batch are sent to the server. |
 | `void setBatchSize(int batchSize)` | Sets the number of rows in each batch. At the end of each batch, the rows in the batch are sent to the server. |
 | `int getBulkCopyTimeout()` | Gets the number of seconds for the operation to complete before it times out. |