Skip to content

Commit ff05e28

Browse files
authored
Merge pull request #105 from kattekrab/revert-80-kattekrab-remove-slash-from-conventions
Revert "Removes ⚡ escaping slashes⚡ from conventions cos they're not needed "
2 parents f5b1acd + e3751ea commit ff05e28

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,10 @@ For example if the git server lives at <code class="language-yaml">https://gitla
2222
put `gitlab-ce.apps.hivec.sandbox1243.opentlc.com`in the box to generate the correct address for the exercises.
2323

2424
## 🦆 Conventions
25-
When running through the exercise, we're tried to call out where things need replacing. The key ones are anything inside an `<>` should be replaced. For example, if your team is called `biscuits` then in the instructions if you see `<TEAM_NAME>` this should be replaced with `biscuits` like so:
25+
When running through the exercise, we're tried to call out where things need replacing. The key ones are anything inside an `<>` should be replaced. For example, if your team is called `biscuits` then in the instructions if you see `\<TEAM_NAME\>` this should be replaced with `biscuits` like so:
2626
<div class="highlight" style="background: #f7f7f7">
2727
<pre><code class="language-bash">
28-
name: <TEAM_NAME>
28+
name: <\TEAM_NAME\>
2929
# ^ this becomes
3030
name: biscuits
3131
</code></pre></div>
@@ -34,4 +34,4 @@ There are lots of code blocks for you to copy and paste. They have little ✂️
3434
```bash
3535
echo "like this one :)"
3636
```
37-
But there are also some blocks that you shouldn't copy and paste which doesn't have the copy✂️ icon. That means you should validate your outputs or yamls against the given block.
37+
But there are also some blocks that you shouldn't copy and paste which doesn't have the copy✂️ icon. That means you should validate your outputs or yamls against the given block.

0 commit comments

Comments
 (0)