From ed201ffe5abbb3eec1e1cefb4d0423e2857e4316 Mon Sep 17 00:00:00 2001
From: "deepsource-autofix[bot]"
 <62050782+deepsource-autofix[bot]@users.noreply.github.com>
Date: Wed, 15 May 2024 07:22:10 +0000
Subject: [PATCH] style: format code with Gofumpt and Prettier

This commit fixes the style issues introduced in 9d125bc according to the output
from Gofumpt and Prettier.

Details: https://github.com/vdaas/vald/pull/2497
---
 docs/user-guides/read-replica-and-rotator.md | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/docs/user-guides/read-replica-and-rotator.md b/docs/user-guides/read-replica-and-rotator.md
index 8bf127d7bf..36e65973d1 100644
--- a/docs/user-guides/read-replica-and-rotator.md
+++ b/docs/user-guides/read-replica-and-rotator.md
@@ -16,7 +16,6 @@ The read replica is managed with a separate chart from the Vald cluster and is d
 
 1. Edit `values.yaml` like below（Please refer to [deployment](deployment) for other fields.）
 
-
    ```yaml
    agent:
    ngt:
@@ -35,18 +34,14 @@ The read replica is managed with a separate chart from the Vald cluster and is d
        rotation_job_concurrency: 2
    ```
 
-
 1. Deploy vald cluster
 
-
    ```bash
    helm install vald vald/vald --values values.yaml
    ```
 
-
 1. Deploy `vald-readreplica` with the same `values.yaml`
 
-
    ```bash
    helm install vald-readreplica vald/vald-readreplica --values values.yaml
    ```
@@ -55,10 +50,8 @@ The read replica is managed with a separate chart from the Vald cluster and is d
 
 1. Edit `valdrelease.yaml` with the same fields as above
 
-
 1. Deploy vald cluster
 
-
    ```bash
    helm install vald-helm-operator-release vald/vald-helm-operator
    kubectl apply -f valdrelease.yaml
@@ -104,7 +97,7 @@ The Kubernetes job to be responsible for the following processes
 
 Result consistency is guaranteed
 
-  There is a time lag between index insertion, agent save, and the completion of read replica rotation. During this time, there may be inconsistencies between the index in the agent itself and the index in the read replica.
+There is a time lag between index insertion, agent save, and the completion of read replica rotation. During this time, there may be inconsistencies between the index in the agent itself and the index in the read replica.
 
 - Sufficient infrastructure is required for QPS scaling