lint

Author: Amogh-Bharadwaj

docs/integrations/data-ingestion/clickpipes/mysql/pause_and_resume.md

@@ -12,7 +12,6 @@ import pause_status from '@site/static/images/integrations/data-ingestion/clickp
 import resume_button from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/resume_button.png'
 import resume_dialog from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/resume_dialog.png'
 
-
 There are scenarios where it would be useful to pause a MySQL ClickPipe. For example, you may want to run some analytics on existing data in a static state. Or, you might be performing upgrades on MySQL. Here is how you can pause and resume a MySQL ClickPipe.
 
 ## Steps to pause a MySQL ClickPipe {#pause-clickpipe-steps}

docs/integrations/data-ingestion/clickpipes/mysql/resync.md

@@ -15,7 +15,6 @@ Resync involves the following operations in order:
 3. Initial load is performed on the `_resync` tables.
 4. The `_resync` tables are then swapped with the original tables. Soft deleted rows are transferred from the original tables to the `_resync` tables before the swap.
 
-
 All the settings of the original ClickPipe are retained in the resync ClickPipe. The statistics of the original ClickPipe are cleared in the UI.
 
 ### Use cases for resyncing a ClickPipe {#use-cases-mysql-resync}

docs/integrations/data-ingestion/clickpipes/postgres/resync.md

@@ -15,7 +15,6 @@ Resync involves the following operations in order:
 3. Initial load is performed on the `_resync` tables.
 4. The `_resync` tables are then swapped with the original tables. Soft deleted rows are transferred from the original tables to the `_resync` tables before the swap.
 
-
 All the settings of the original ClickPipe are retained in the resync ClickPipe. The statistics of the original ClickPipe are cleared in the UI.
 
 ### Use cases for resyncing a ClickPipe {#use-cases-postgres-resync}