diff options
author | Corentin Noël <corentin.noel@collabora.com> | 2021-10-06 18:35:29 +0200 |
---|---|---|
committer | Corentin Noël <tintou@noel.tf> | 2022-04-09 00:44:24 +0200 |
commit | c2df7447154f5e633432a1c192ddd162055e3958 (patch) | |
tree | a546bca01a3700fbc36d5fd4ccca6b0ddc543952 /docs | |
parent | e2e3c17ef45347d91dfc66bc1c5c451af0774d8e (diff) | |
download | gcr-c2df7447154f5e633432a1c192ddd162055e3958.tar.gz |
gck: use the right namespace for GckUriData methods
Diffstat (limited to 'docs')
-rw-r--r-- | docs/gck/pkcs11-links.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/gck/pkcs11-links.md b/docs/gck/pkcs11-links.md index ad89d6c..ee62924 100644 --- a/docs/gck/pkcs11-links.md +++ b/docs/gck/pkcs11-links.md @@ -17,8 +17,8 @@ A PKCS#11 URI can always resolve to more than one object, token or module. A PKCS#11 URI that refers to a token, would (when used in a context that expects objects) refer to all the token on that module. -To parse a PKCS#11 URI, use the [func@uri_parse] function passing in the type of -context in which you're using the URI. To build a URI, use the [func@uri_build] +To parse a PKCS#11 URI, use the [func@Gck.UriData.parse] function passing in the type of +context in which you're using the URI. To build a URI, use the [method@Gck.UriData.build] function. In most cases, the parsing or building of URIs is already handled for you in the |