summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPjotr Prins2021-08-01 08:53:05 +0200
committerPjotr Prins2021-08-01 08:53:08 +0200
commit3aa0699a25bdd31f4da73363784cbdea3ed6a241 (patch)
tree7070678a85c63d8243964b4bd189d7112cd72ff1
parentf7aa6b4a3e9facc5fa7bf9a245c6ca7c9510fd5c (diff)
downloadgn-gemtext-3aa0699a25bdd31f4da73363784cbdea3ed6a241.tar.gz
typo
-rw-r--r--topics/data-uploads/editing-data.gmi2
1 files changed, 1 insertions, 1 deletions
diff --git a/topics/data-uploads/editing-data.gmi b/topics/data-uploads/editing-data.gmi
index 390788d..1bc1bf8 100644
--- a/topics/data-uploads/editing-data.gmi
+++ b/topics/data-uploads/editing-data.gmi
@@ -37,7 +37,7 @@ select * FROM information_schema.COLUMNS WHERE table_schema=DATABASE() AND TABLE
For everything to run, use the latest commit on the main branch from gn3. One way to make sure that you are running the latest changes, make sure that you have genenetwork3 cloned somewhere in your path; and keep it updated. Thereafter set, a PATH in "bin/genenetwork2" which should look something similar to `export PYTHONPATH=/home/bonface/projects/genenetwork3:$PYTHON_GN_PATH:$GN2_BASE_DIR/wqflask:$PYTHONPATH`.
-Alternatively, install gn3 in it's own profile. This can be sometimes inconvenient since the latest changes from gn3 can be ahead of the the package definition in our channel.
+Alternatively, install gn3 in it's own profile. This can be sometimes rinconvenient since the latest changes from gn3 can be ahead of the the package definition in our channel.
### How to edit a trait Editing a trait/ probeset