Skip to content

Commit

Permalink
Fix typos (#69)
Browse files Browse the repository at this point in the history
Signed-off-by: Endre Czirbesz <[email protected]>
  • Loading branch information
endrec authored Jun 21, 2020
1 parent 8daeec0 commit 0c32ebd
Show file tree
Hide file tree
Showing 23 changed files with 34 additions and 34 deletions.
2 changes: 1 addition & 1 deletion docs/CHANGELOG-0.8.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ aliases:
**Merged pull requests:**

- Prepare docs for 0.8.1 release [\#629](https://github.com/appscode/stash/pull/629) ([tamalsaha](https://github.com/tamalsaha))
- Add missing validator for respository resource in chart [\#628](https://github.com/appscode/stash/pull/628) ([tamalsaha](https://github.com/tamalsaha))
- Add missing validator for repository resource in chart [\#628](https://github.com/appscode/stash/pull/628) ([tamalsaha](https://github.com/tamalsaha))

## [0.8.0](https://github.com/appscode/stash/tree/0.8.0) (2018-12-08)
[Full Changelog](https://github.com/appscode/stash/compare/0.7.0...0.8.0)
Expand Down
4 changes: 2 additions & 2 deletions docs/design.md
Original file line number Diff line number Diff line change
Expand Up @@ -588,7 +588,7 @@ metadata:
namespace: demo
labels:
app: stash-demo
# This annotations indicates that data shoul be recovered on each restart of the workload
# This annotations indicates that data should be recovered on each restart of the workload
annotations:
stash.appscode.com/restorepolicy: "OnRestart"
stash.appscode.com/repository: "demo-backup-repo"
Expand Down Expand Up @@ -899,4 +899,4 @@ spec:
backupSession: ${backupSessionName}
outputJsonDir: ${output-dir}
outputVolumeName: ${output-volume-name}
```
```
2 changes: 1 addition & 1 deletion docs/examples/design/function/volume_recovery.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# volumeRecoveryfunction Recover a Kubernetes volume
# volumeRecovery function Recover a Kubernetes volume
apiVersion: stash.appscode.com/v1beta1
kind: Function
metadata:
Expand Down
2 changes: 1 addition & 1 deletion docs/examples/design/restore/auto-restore.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ metadata:
namespace: demo
labels:
app: stash-demo
# This annotations indicates that data shoul be recovered on each restart of the workload
# This annotations indicates that data should be recovered on each restart of the workload
annotations:
stash.appscode.com/restorepolicy: "OnRestart"
stash.appscode.com/repository: "demo-backup-repo"
Expand Down
2 changes: 1 addition & 1 deletion docs/examples/design/task/volume_recovery.yaml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# volumeRecovery specifies required functions and their inputs to recover kuberenetes volume
# volumeRecovery specifies required functions and their inputs to recover kubernetes volume
apiVersion: stash.appscode.com/v1beta1
kind: Task
metadata:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ spec:
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Backup started for *wordpres-backup*.\n *Targets:*\n- deployment/wordpress-deployment\n- mysql/wordpress-mysql"
"text": "Backup started for *wordpress-backup*.\n *Targets:*\n- deployment/wordpress-deployment\n- mysql/wordpress-mysql"
}
}
]
Expand All @@ -64,7 +64,7 @@ spec:
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Backup has been completed for *wordpres-backup*."
"text": "Backup has been completed for *wordpress-backup*."
}
}
]
Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/advanced-use-case/clone-pvc.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ $ kubectl create secret generic -n demo gcs-secret \
secret/gcs-secret created
```

Now, create a `Respository` using this secret. Below is the YAML of `Repository` crd we are going to create,
Now, create a `Repository` using this secret. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -571,7 +571,7 @@ $ kubectl create secret generic -n demo gcs-secret \
secret/gcs-secret created
```

Now, create a `Respository` using this secret. Below is the YAML of `Repository` crd we are going to create,
Now, create a `Repository` using this secret. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/advanced-use-case/instant-backup.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ $ kubectl create secret generic -n demo gcs-secret \
secret/gcs-secret created
```

Now, create a `Respository` using this secret. Below is the YAML of `Repository` crd we are going to create,
Now, create a `Repository` using this secret. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/advanced-use-case/pause-backup.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@ $ kubectl create secret generic -n demo gcs-secret \
secret/gcs-secret created
```

Now, create a `Respository` using this secret. Below is the YAML of `Repository` crd we are going to create,
Now, create a `Repository` using this secret. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/backends/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ You will see all snapshots taken by Stash at `/snapshot` directory of this repos
## Next Steps

- Learn how to configure `Kuberntes Volume` as backend from [here](/docs/guides/latest/backends/local.md).
- Learn how to configure `Kubernetes Volume` as backend from [here](/docs/guides/latest/backends/local.md).
- Learn how to configure `AWS S3/Minio/Rook` backend from [here](/docs/guides/latest/backends/s3.md).
- Learn how to configure `Google Cloud Storage (GCS)` backend from [here](/docs/guides/latest/backends/gcs.md).
- Learn how to configure `Microsoft Azure Storage` backend from [here](/docs/guides/latest/backends/azure.md).
Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/hooks/backup-and-restore-hooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ secret/gcs-secret created

**Create Repository:**

Now, crete a `Respository` using this secret. Below is the YAML of Repository CR we are going to create,
Now, create a `Repository` using this secret. Below is the YAML of Repository CR we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down
6 changes: 3 additions & 3 deletions docs/guides/latest/hooks/batch-backup-hooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -228,7 +228,7 @@ secret/gcs-secret created

**Create Repository:**

Now, crete a `Respository` using this secret. Below is the YAML of `Repository` CR we are going to create,
Now, create a `Repository` using this secret. Below is the YAML of `Repository` CR we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -356,7 +356,7 @@ spec:
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Backup started for *wordpres-backup*.\n *Targets:*\n- deployment/wordpress-deployment\n- mysql/wordpress-mysql"
"text": "Backup started for *wordpress-backup*.\n *Targets:*\n- deployment/wordpress-deployment\n- mysql/wordpress-mysql"
}
}
]
Expand All @@ -376,7 +376,7 @@ spec:
"type": "section",
"text": {
"type": "mrkdwn",
"text": "Backup has been completed for *wordpres-backup*."
"text": "Backup has been completed for *wordpress-backup*."
}
}
]
Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/platforms/aks.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ type: Opaque
**Create Repository:**
Now, let's create a `Respository` with the information of our desired blob container. Below is the YAML of `Repository` crd we are going to create,
Now, let's create a `Repository` with the information of our desired blob container. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -381,7 +381,7 @@ deployment-backup */1 * * * * False 0 35s 64s

**Wait for BackupSession:**

The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/platforms/eks.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ type: Opaque
**Create Repository:**
Now, let's create a `Respository` with the information of our desired S3 bucket. Below is the YAML of `Repository` crd we are going to create,
Now, let's create a `Repository` with the information of our desired S3 bucket. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -396,7 +396,7 @@ deployment-backup */1 * * * * False 0 24s 2m14s

**Wait for BackupSession:**

The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/platforms/gke.md
Original file line number Diff line number Diff line change
Expand Up @@ -193,7 +193,7 @@ type: Opaque
**Create Repository:**
Now, let's create a `Respository` with the information of our desired GCS bucket. Below is the YAML of `Repository` crd we are going to create,
Now, let's create a `Repository` with the information of our desired GCS bucket. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -401,7 +401,7 @@ deployment-backup */1 * * * * False 0 13s 2m42s

**Wait for BackupSession:**

The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/platforms/minio.md
Original file line number Diff line number Diff line change
Expand Up @@ -196,7 +196,7 @@ type: Opaque
**Create Repository:**
Now, let's create a `Respository` with the information of our desired Minio bucket. Below is the YAML of `Repository` crd we are going to create,
Now, let's create a `Repository` with the information of our desired Minio bucket. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -412,7 +412,7 @@ deployment-backup */1 * * * * False 0 13s 1m50s

**Wait for BackupSession:**

The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/platforms/rook.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ type: Opaque
**Create Repository:**
Now, let's create a `Respository` with the information of our desired Ceph storage bucket. Below is the YAML of `Repository` crd we are going to create,
Now, let's create a `Repository` with the information of our desired Ceph storage bucket. Below is the YAML of `Repository` crd we are going to create,

```yaml
apiVersion: stash.appscode.com/v1alpha1
Expand Down Expand Up @@ -414,7 +414,7 @@ deployment-backup */1 * * * * False 0 13s 1m50s

**Wait for BackupSession:**

The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `deployment-backup` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd. The sidecar container will watch for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/volumesnapshot/deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -258,7 +258,7 @@ deployments-volume-snapshot */1 * * * * False 0 39s 2

**Wait for BackupSession :**

The `deployments-volume-snapshot` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd.
The `deployments-volume-snapshot` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/volumesnapshot/pvc.md
Original file line number Diff line number Diff line change
Expand Up @@ -223,7 +223,7 @@ pvc-volume-snapshot */1 * * * * False 0 39s 2

**Wait for BackupSession :**

The `pvc-volume-snapshot` CronJob will trigger a backup on each scheduled time slot by creating a `BackpSession` crd.
The `pvc-volume-snapshot` CronJob will trigger a backup on each scheduled time slot by creating a `BackupSession` crd.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/latest/volumesnapshot/statefulset.md
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,7 @@ statefulset-volume-snapshot */1 * * * * False 0 <none> 1

**Wait for BackupSession :**

The `statefulset-volume-snapshot` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd.
The `statefulset-volume-snapshot` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down Expand Up @@ -595,7 +595,7 @@ statefulset-volume-snapshot */1 * * * * False 0 <none> 1

**Wait for BackupSession :**

The `statefulset-volume-snapshot` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd.
The `statefulset-volume-snapshot` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/workloads/daemonset.md
Original file line number Diff line number Diff line change
Expand Up @@ -318,7 +318,7 @@ dmn-backup */1 * * * * 3m

**Wait for BackupSession:**

The `dmn-backup` CronJob will trigger a backup on each schedule by creating a `BackpSession` crd. The sidecar container watches for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `dmn-backup` CronJob will trigger a backup on each schedule by creating a `BackupSession` crd. The sidecar container watches for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/workloads/deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -351,7 +351,7 @@ deployment-backup */1 * * * * False 0 35s 64s

**Wait for BackupSession:**

The `deployment-backup` CronJob will trigger a backup on each scheduled slot by creating a `BackpSession` crd. The sidecar container watches for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `deployment-backup` CronJob will trigger a backup on each scheduled slot by creating a `BackupSession` crd. The sidecar container watches for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/latest/workloads/statefulset.md
Original file line number Diff line number Diff line change
Expand Up @@ -363,7 +363,7 @@ ss-backup */1 * * * * 3m41s

**Wait for BackupSession:**

The `ss-backup` CronJob will trigger a backup on each scheduled slot by creating a `BackpSession` crd. The sidecar container watches for the `BackupSession` crd. When it finds one, it will take backup immediately.
The `ss-backup` CronJob will trigger a backup on each scheduled slot by creating a `BackupSession` crd. The sidecar container watches for the `BackupSession` crd. When it finds one, it will take backup immediately.

Wait for the next schedule for backup. Run the following command to watch `BackupSession` crd,

Expand Down

0 comments on commit 0c32ebd

Please sign in to comment.