Skip to content

Commit 4ae22c9

Browse files
committed
markdown lint
1 parent 0e149fc commit 4ae22c9

File tree

3 files changed

+1
-4
lines changed

3 files changed

+1
-4
lines changed

docs/docs/guides/artifact.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ infrahubctl schema load /tmp/schema.yml
5353

5454
## Creating a group and adding members
5555

56-
We need to create a group for every Artifact Definition that we will define. An artifact will be generated for every member that is part of that group.
56+
We need to create a group for every Artifact Definition that we will define. An artifact will be generated for every member that is part of that group.
5757

5858
Create a Standard Group with the name `DeviceGroup` and add `NetworkDevice` `switch1`, `switch2` and `switch3` as a member.
5959

docs/docs/guides/jinja2-transform.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ The goal of this guide is to develop a Jinja Transform and add it to Infrahub, w
1616
6. Add the repository to Infrahub as an external repository
1717
7. Validate that the transform works by using the render API endpoint
1818

19-
2019
## 1. Loading a schema
2120

2221
In this guide we are going to work with a very simplistic network device model. I won't provide a rendered template that is very useful, the goal is instead to show how the Jinja Rendering works. Once you have mastered the basics you will be ready to go on to create more advanced template.
@@ -140,7 +139,6 @@ mkdir device_config_render
140139

141140
Then save the below query as a text file named `device_config.gql`.
142141

143-
144142
```graphql
145143
query DeviceQuery($name: String!) {
146144
NetworkDevice(name__value: $name) {

docs/docs/guides/python-transform.mdx

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,6 @@ mkdir device_config_render
139139

140140
Then save the below query as a text file named `device_config.gql`.
141141

142-
143142
```graphql
144143
query DeviceQuery($name: String!) {
145144
NetworkDevice(name__value: $name) {

0 commit comments

Comments
 (0)