Skip to content

Commit c5793c5

Browse files
committed
Fix typos, punctuation in "Fields public control"
1 parent cf46118 commit c5793c5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/security/fields-public-control.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
Fields public Control
22
=====================
33

4-
You can use `config.fields.*.public` to control if a field needs to be removed the results.
4+
You can use `config.fields.*.public` to control if a field needs to be removed from the results.
55
If `config.fields.*.public` value is true or is not set, the field will be visible.
66
If value is false, then the field will be removed (in any query, including inspection queries).
77

@@ -20,7 +20,7 @@ AnObject:
2020

2121
```
2222

23-
You can also use `config.fieldsDefaultPublic` to handle the setting globally on an object :
23+
You can also use `config.fieldsDefaultPublic` to handle the setting globally on an object:
2424

2525
```yaml
2626
AnObject:
@@ -34,6 +34,6 @@ AnObject:
3434
type: "String"
3535
```
3636
37-
Have you noticed `typeName` and `fieldName` here ? This variables are always set to the current
37+
Have you noticed `typeName` and `fieldName` here? These variables are always set to the current
3838
type name and current field name, meaning you can apply a per field `public` setting on all the
3939
fields with one line of yaml.

0 commit comments

Comments
 (0)