Fix docs typos

2022-05-03 11:04:37 +05:45
parent 8560c3bc00
commit 3fd33957ca
14 changed files with 37 additions and 37 deletions
@@ -55,7 +55,7 @@ Chosen option: "\[option 1\]", because \[justification. e.g., only option, which

 ### Cold Migration

-The migration happens while the service is offline. File metadata, blobs and share data is exported from ownCloud 10 and imported in oCIS. This can happen user by user, where every user export would contain the file blobs, their metadata, trash, versions, shares and all metadata that belongs to the users storage. To prevent group shares from breaking, users in the same groups must be migrated in batch. Depending on the actual group shares in an instance this may effectively require a complete migration in a single batch.
+The migration happens while the service is offline. File metadata, blobs and share data is exported from ownCloud 10 and imported in oCIS. This can happen user by user, where every user export would contain the file blobs, their metadata, trash, versions, shares and all metadata that belongs to the user's storage. To prevent group shares from breaking, users in the same groups must be migrated in batch. Depending on the actual group shares in an instance this may effectively require a complete migration in a single batch.

 - Good, because oCIS can be tested in a staging system without writing to the production system.
 - Good, because file layout on disk can be changed to support new storage driver capabilities.
@@ -69,7 +69,7 @@ The migration happens in subsequent stages while the service is online.

 - Good, because the admin can migrate users from old to new backend in a controlled way.
 - Good, because users and admins can learn to trust the new system.
- Good, because there can be preparations even long before the migrations happens in parallel on the oC10 codebase, ie. addition of metadata that is needed while the system operates.
+- Good, because there can be preparations even long before the migrations happens in parallel on the oC10 codebase, i.e. addition of metadata that is needed while the system operates.
 - Good, because the downtime of the system can be fairly small.
 - Bad, because it is more complex and might drag on for a long time.

@@ -31,7 +31,7 @@ This API would even allow to provide (WebDAV-) endpoints depending on the kind a
 - No longer the need to make assumptions about WebDAV- and other routes in clients.
 - More meta data available about spaces for a better user experience.
 - Part of the bigger spaces plan.
- Important to consider in client migration scenarios, ie. in CERN.
+- Important to consider in client migration scenarios, i.e. in CERN.

 ## Considered Options

@@ -25,7 +25,7 @@ A simple example is the notification feature for oCIS: Users should receive an e

 * Events are supposed to decouple services and raise flexibility, also considering extensions that are not directly controlled by the ownCloud project.
 * Events should bring flexibility in the implementation of sending and receiving services.
-* Events should not obsolete other mechanisms to communicate, ie. grpc calls.
+* Events should not obsolete other mechanisms to communicate, i.e. grpc calls.
 * Sending an event has to be as little resource consuming for the sender as possible.
 * Events are never user visible.

@@ -35,7 +35,7 @@ The `docs` folder contains the source for the [oCIS documentation]({{< ref "../"

 The `deployments` folder contains documented deployment configurations and templates. On a single node, running a single ocis runtime is a resource efficient way to deploy ocis. For multiple nodes docker compose or helm charts for kubernetes examples can be found here.

-The `scripts` folder contains scripts to perform various build, install, analysis, etc operations.
+The `scripts` folder contains scripts to perform various build, install, analysis, etc. operations.

 ## Starting points