From 0b9e83c8bebd5bf71b9d2765a66c7fd799fdc2c0 Mon Sep 17 00:00:00 2001 From: ChrissieCW Date: Tue, 8 Jan 2019 09:37:06 +0000 Subject: [PATCH] tweet to Tweet --- docs/data/transparency-authority-trust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data/transparency-authority-trust.md b/docs/data/transparency-authority-trust.md index cd09e6e..8dceb65 100644 --- a/docs/data/transparency-authority-trust.md +++ b/docs/data/transparency-authority-trust.md @@ -28,7 +28,7 @@ Every subject-relation-object Event is an assertion made by the Agent (and in th ## Landing page to DOI mappings -When a blog post or tweet mentions a DOI directly, you know that the author intended to link to the specific piece of content identified by that DOI. When the author uses a landing page, which is more common, we find the best DOI match we can, and describe how performed the match and verification. This is described fully in the [How Crossref Agents match landing pages to DOIs](/data/matching-landing-pages). +When a blog post or Tweet mentions a DOI directly, you know that the author intended to link to the specific piece of content identified by that DOI. When the author uses a landing page, which is more common, we find the best DOI match we can, and describe how performed the match and verification. This is described fully in the [How Crossref Agents match landing pages to DOIs](/data/matching-landing-pages). ## Data aggregator or provider?