From 576a7c5f749eeb1f2384e514eb44193c72dec0e6 Mon Sep 17 00:00:00 2001
From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Date: Sat, 8 Jan 2022 15:14:31 +0100
Subject: [PATCH] docs(self-hosting examples): misc small fixes (#13426)
---
docs/usage/examples/self-hosting.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/usage/examples/self-hosting.md b/docs/usage/examples/self-hosting.md
index 8e5d50d2c1..f1f5799c81 100644
--- a/docs/usage/examples/self-hosting.md
+++ b/docs/usage/examples/self-hosting.md
@@ -166,7 +166,7 @@ The following example runs Renovate hourly, and looks for the self-hosted config
```yml
version: '2.1'
orbs:
- renovate: daniel-shuy/renovate@2.1.1
+ renovate: daniel-shuy/renovate@2.2.0
workflows:
renovate:
jobs:
@@ -189,7 +189,7 @@ How to validate your config as part of your workflow:
```yml
version: '2.1'
orbs:
- renovate: daniel-shuy/renovate@2.1
+ renovate: daniel-shuy/renovate@2.2.0
workflows:
lint:
jobs:
@@ -250,7 +250,7 @@ If running against GitHub Enterprise, change the above `gitlab` values to the eq
You can save this file as anything you want and then use `RENOVATE_CONFIG_FILE` env variable to tell Renovate where to find it.
Most people will run Renovate via cron, e.g. once per hour.
-Here is an example bash script that you can point `cron` to:
+Here is an example Bash script that you can point `cron` to:
```sh
#!/bin/bash
@@ -273,9 +273,9 @@ You should save and test out this script manually first, and add it to cron once
This section describes how to use Git binary with SSH for GitLab, to avoid API shortcomings.
-You need to first create a SSH key, then add the public part to GitLab (see this [guide](https://docs.gitlab.com/ee/ssh/))
+You need to first create a SSH key, then add the public part to GitLab (see this [guide](https://docs.gitlab.com/ee/ssh/)).
-Then, you need to create the secret to add the SSH key, and the following config to your container
+Then, you need to create the secret to add the SSH key, and the following config to your container:
```
host gitlab.com
@@ -285,13 +285,13 @@ host gitlab.com
User git
```
-To easily create the secret, you can do the following (see [docs](https://kubernetes.io/docs/concepts/configuration/secret/#use-case-pod-with-ssh-keys))
+To easily create the secret, you can do the following (see [docs](https://kubernetes.io/docs/concepts/configuration/secret/#use-case-pod-with-ssh-keys)).
```sh
kubectl create secret generic ssh-key-secret --from-file=config=/path/to/config --from-file=id_rsa=/path/to/.ssh/id_rsa --from-file=id_rsa.pub=/path/to/.ssh/id_rsa.pub
```
-It creates something like this
+It creates something like this:
```yml
apiVersion: v1
--
GitLab