Update oracle.adoc

[docs] fix typos
This commit is contained in:
Luca Scannapieco 2024-03-13 17:52:08 +01:00 committed by Chris Cranford
parent 7d2ec8f763
commit a5cb8b4596

View File

@ -112,7 +112,7 @@ endif::product[]
.Default workflow that the Oracle connector uses to perform an initial snapshot
The following workflow lists the steps that {prodname} takes to create a snapshot.
These steps describe the process for a snapshot when the xref:{context}-property-snapshot-mode[`snapshot.mode`] configuration property is set to its default value, which is `initial`.
You can customize the way that the connector creates snapshots by changig the value of the `snapshot.mode` property.
You can customize the way that the connector creates snapshots by changing the value of the `snapshot.mode` property.
If you configure a different snapshot mode, the connector completes the snapshot by using a modified version of this workflow.
When the snapshot mode is set to the default, the connector completes the following tasks to create a snapshot:
@ -471,7 +471,7 @@ Optionally, the connector can also xref:oracle-schema-change-topic[emit schema c
=== Schema change topic
You can configure a {prodname} Oracle connector to produce schema change events that describe structural changes that are applied to tables in the database.
The connector writes schema change events to a Kafka topic named `_<serverName>_`, where `_topicName_` is the namespace that is specified in the xref:oracle-property-topic-prefix[`topic.prefix`] configuration property.
The connector writes schema change events to a Kafka topic named `_<serverName>_`, where `_serverName_` is the namespace that is specified in the xref:oracle-property-topic-prefix[`topic.prefix`] configuration property.
{prodname} emits a new message to the schema change topic whenever it streams data from a new table, or when the structure of the table is altered.