cosmetic changes

kanisterio · Feb 7, 2024 · 869775d · 869775d
1 parent d0cee1f
commit 869775d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/design/kanister-kopia-integration.md b/design/kanister-kopia-integration.md
@@ -604,13 +604,13 @@ If misplaced, Kanister will not be able to recover these credentials.
 
 ### Replace Kopia CLI with SDK
 
-Currently we are using Kopia CLI to perform the repository and kopia repository server operations in Kanister.
+Currently, we are using Kopia CLI to perform the repository and kopia repository server operations in Kanister.
 The repository controller creates a pod, executes commands through `kube.exec` on the pod to perform
 repository operations. The commands include: 
 - repo connect 
 - start server 
 - add users 
 - refresh server 
 
-Kopia provides a SDK to perform repository operations which can be used instead of CLI. The detailed design is explained in the document
+Kopia provides an SDK to perform repository operations which can be used instead of CLI. The detailed design is explained in the document
 [Replace Kopia CLI with Kopia SDK](https://github.com/kanisterio/kanister/blob/master/design/replace-CLI-with-SDK.md).
diff --git a/design/replace-CLI-with-SDK.md b/design/replace-CLI-with-SDK.md
@@ -14,7 +14,7 @@
 
 # Motivation
 
-Kanister uses a Kubernetes custom controller makes use of Kopia as a primary backup and restore tool. 
+Kanister uses a Kubernetes custom controller that makes use of Kopia as a primary backup and restore tool. 
 The detailed design of the customer controller can be found [here](https://github.com/kanisterio/kanister/blob/master/design/kanister-kopia-integration.md)
 
 The custom controller called as repository server controller currently uses Kopia CLI to perform the Kopia operations. All the