aboutsummaryrefslogtreecommitdiffhomepage
path: root/docs
diff options
context:
space:
mode:
authorAdam Janovsky2023-05-26 14:17:50 +0200
committerAdam Janovsky2023-05-26 14:17:50 +0200
commit8c06ca481e3e72e42c4da9f4c77d10cdcc57aebf (patch)
tree87fac0684e1edaa024e5d93cf102447a377a7ec5 /docs
parent83eea4705203e5eaa954e60ab9548a13ddfc2f6a (diff)
downloadsec-certs-8c06ca481e3e72e42c4da9f4c77d10cdcc57aebf.tar.gz
sec-certs-8c06ca481e3e72e42c4da9f4c77d10cdcc57aebf.tar.zst
sec-certs-8c06ca481e3e72e42c4da9f4c77d10cdcc57aebf.zip
fix typo in docs
Diffstat (limited to 'docs')
-rw-r--r--docs/quickstart.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/quickstart.md b/docs/quickstart.md
index 1088e51a..f2e3690f 100644
--- a/docs/quickstart.md
+++ b/docs/quickstart.md
@@ -53,7 +53,7 @@ This script takes a long time to run (few hours) and will create `./cc_dset` or
## Run sec-certs from docker
-If you installed the docker image (see [installation](installation.md)), use `docker run -it sec-certs` to run the container interactively. From there, you can run the `sec-certs` CLI. Alternatively, you can serve a Jupyter notebook from the docker to use at your host machine and even write your scripts to some shared folder. Example of that use-case follows.
+If you installed the docker image (see [installation](installation.md)), use `docker run -it seccerts/sec-certs` to run the container interactively. From there, you can run the `sec-certs` CLI. Alternatively, you can serve a Jupyter notebook from the docker to use at your host machine and even write your scripts to some shared folder. Example of that use-case follows.
### Persistent files with docker mounts