on master help sign in
scries: clarify gall mark behaviour
commit2396ce6fe37796bdd0c47f0f3bff174cfd1f4a75 authortinnus-napbus <admin@tinnus-napbus.xyz> dateThu 16 Sep 2021, 00:19 (5 years ago) parentbb7546e
1 file changed+1−1
content/docs/arvo/concepts/scry.md+1−1
content/docs/arvo/concepts/scry.md+1−1
@@ -40,7 +40,7 @@ To explore what scry endpoints are available for vanes, you can refer to the Scr
4040
4141Gall has a single scry endpoint of its own to check for the existence of an agent, but otherwise all Gall scries are passed through to one of the agents it manages. The target agent to scry is specified in place of the `desk` as described in the diagram above. Each Gall agent includes a `+on-peek` arm that defines its own scry endpoints. For example, `%graph-store` has a number of scry endpoints to access the data it stores, such as chat messages and the like.
4242
43−Gall agents can expose scry endpoints with any `care`, but most commonly they'll take a `%x` `care`. Gall handles `%x` scries specially - it expects an extra field at the end of the `path` that specifies a `mark`. Gall will attempt to perform a `mark` conversion from the `mark` returned by the scry endpoint to the `mark` specified.
43+Gall agents can expose scry endpoints with any `care`, but most commonly they'll take a `%x` `care`. Gall handles `%x` scries specially - it expects an extra field at the end of the `path` that specifies a `mark`. Gall will attempt to perform a `mark` conversion from the `mark` returned by the scry endpoint to the `mark` specified. Note the trailing `mark` in the `path` will not be passed through to the agent itself.
4444
4545### What is an endpoint?
4646