From 52496a015bab5e3cc37c11544ddb5eed99d5fdad Mon Sep 17 00:00:00 2001 From: Hamcha Date: Sat, 18 Nov 2023 01:35:04 +0100 Subject: [PATCH] minor typos --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index b401fd1..5d842e2 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ The required scopes are `api, write_repository` and the role should be Maintaine ```json { - "provider": "gitea", + "provider": "gitlab", "api_url": "https:///api/v4", "project_id":"/", "token": "" @@ -99,7 +99,7 @@ Templaters are change operations that operate on a specific type of file, unlike #### JSON -The JSON templater replaces values within a JSON file. Keys are provided as strings using `/` for separation, you can specify array indexes for array (e.g. `nested/field/10/tag` becomes `nested.field[10].tag`). +The JSON templater replaces values within a JSON file. Keys are provided as strings using `/` for separation, you can specify array indexes for arrays (e.g. `nested/field/10/tag` becomes `nested.field[10].tag`). Your changeset should look like this: @@ -120,7 +120,7 @@ The fields **MUST** exist in the file or the change will fail. #### YAML -The YAML templater replaces values within a YAML file. Keys are provided as strings using `.` for separation, you can specify array indexes for array (e.g. `nested.field.10.tag` becomes `nested.field[10].tag`). +The YAML templater replaces values within a YAML file. Keys are provided as strings using `.` for separation, you can specify array indexes for arrays (e.g. `nested.field.10.tag` becomes `nested.field[10].tag`). Your changeset should look like this: