Skip to content

Commit b19279f

Browse files
committed
fix(docs): consistent colon is good colon
1 parent 356bbd9 commit b19279f

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/guides/haproxy-registration-guide.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
Register a service with haproxy
22
===============================
33

4-
1. Ensure that the `salt-master` and `loadbalancer` can be brought up with vagrant locally.
4+
1. Ensure that the `salt-master` and `loadbalancer` can be brought up with vagrant locally:
55
```console
66
vagrant up salt-master
77
vagrant up loadbalancer
88
```
9-
2. In the local repository, create a new state/directory to manage files for your service
9+
2. In the local repository, create a new state/directory to manage files for your service:
1010
```console
1111
touch salt/base/salt.sls
1212
```
13-
3. Additionally, add an `nginx` configuration state and consul-service state that exposes that directory over HTTP
14-
- This configuration might look similar to an existing haproxy service like letsencrypt
13+
3. Additionally, add an `nginx` configuration state and `consul` service state that exposes that directory over HTTP:
14+
- This configuration might look similar to an existing haproxy service like `letsencrypt`
1515
```yaml
1616
/etc/nginx/sites.d/letsencrypt-well-known.conf:
1717
file.managed:
@@ -37,7 +37,7 @@ Register a service with haproxy
3737
- pkg: consul-pkgs
3838
```
3939

40-
4. In your local repository, navigate to `salt/base/config` and add an `nginx` configuration file.
40+
4. In your local repository, navigate to `salt/base/config` and add an `nginx` configuration file:
4141
This configuration file might look similarly to the one of the `letsencrypt` service:
4242
```nginx
4343
server {

0 commit comments

Comments
 (0)