run remark linter locally

docs/extensions/settings/values.md

@@ -1,32 +1,34 @@
----
+* * *
+
 title: "Settings Values"
 date: 2020-05-04T00:00:00+00:00
 weight: 51
-geekdocRepo: https://github.com/owncloud/ocis-settings
+geekdocRepo: <https://github.com/owncloud/ocis-settings>
 geekdocEditPath: edit/master/docs
-geekdocFilePath: values.md
----
+
+## geekdocFilePath: values.md
 
 A **Settings Value** is the value an authenticated user has chosen for a specific setting, defined in a
-*settings bundle*. For choosing settings values as a user the sole entry point is the ocis-web extension
+_settings bundle_. For choosing settings values as a user the sole entry point is the ocis-web extension
 provided by this service.
 
 ## Identifying settings values
 
-A *settings value* is uniquely identified by four attributes. Three of them are coming from the definition of
+A _settings value_ is uniquely identified by four attributes. Three of them are coming from the definition of
 the setting within it's settings bundle (see [Settings Bundles](https://owncloud.github.io/extensions/ocis_settings/bundles/)
 for an example). The fourth identifies the user.
-- extension: Key of the extension that registered the settings bundle,
-- bundleKey: Key of the settings bundle,
-- settingKey: Key of the setting as defined within the bundle,
-- accountUuid: The UUID of the authenticated user who has saved the setting.
 
-{{< hint info >}}
+-   extension: Key of the extension that registered the settings bundle,
+-   bundleKey: Key of the settings bundle,
+-   settingKey: Key of the setting as defined within the bundle,
+-   accountUuid: The UUID of the authenticated user who has saved the setting.
+
+{{&lt; hint info >}}
 When requests are going through `ocis-proxy`, the accountUuid attribute can be set to the static keyword `me`
 instead of using a real UUID. `ocis-proxy` will take care of minting the UUID of the authenticated user into
 a JWT, providing it in the HTTP header as `x-access-token`. That UUID is then used in this service, to replace
 `me` with the actual UUID of the authenticated user.
-{{< /hint >}}
+{{&lt; /hint >}}
 
 ## Example of stored settings values
 
@@ -68,8 +70,9 @@ a JWT, providing it in the HTTP header as `x-access-token`. That UUID is then us
 ```
 
 ## gRPC endpoints
+
 The obvious way of modifying settings is the ocis-web extension, as described earlier. However, services can
-use the respective gRPC endpoints of the `ValueService` to query and modify *settings values* as well.
+use the respective gRPC endpoints of the `ValueService` to query and modify _settings values_ as well.
 The gRPC endpoints require the same identifier attributes as described above, so for making a request to
 the `ValueService` you will have to make sure that the accountUuid of the authenticated user is available in
 your service at the time of the request.