diff options
| author | Munyoki Kilyungi | 2023-08-09 13:03:10 +0300 |
|---|---|---|
| committer | Munyoki Kilyungi | 2023-08-09 13:03:10 +0300 |
| commit | 5f3fad926e06e2889ed9c7aae2bf94dbd39c870b (patch) | |
| tree | f003d7fde56407b2dab36a24bc7a74185e1d68ad | |
| parent | acdd37aba12ffb24e3459c10f619ee8660c0c13c (diff) | |
| download | gn-gemtext-5f3fad926e06e2889ed9c7aae2bf94dbd39c870b.tar.gz | |
Fix minor typo
Signed-off-by: Munyoki Kilyungi <me@bonfacemunyoki.com>
| -rw-r--r-- | issues/modelling-phenotype-data.gmi | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/issues/modelling-phenotype-data.gmi b/issues/modelling-phenotype-data.gmi index ad0e18e..e7f5951 100644 --- a/issues/modelling-phenotype-data.gmi +++ b/issues/modelling-phenotype-data.gmi @@ -35,7 +35,7 @@ We should explore pre-linking pre-prints with canonical publications---to avoid ## Edge Cases With How We Store Traits -There is an on-going discussion on how to store private/public traits. How we store traits is consistent. This section explains why this is the case. +There is an on-going discussion on how to store private/public traits. How we store traits is inconsistent. This section explains why this is the case. * There are "hanging" traits. In this case, we have cases where we have given metadata about a given trait, but we have no associated vectors. In such a case, we have no clear way of knowing whether that trait is public or private. Here's a query that displays all these cases: |