Skip to content

Commit e1fe879

Browse files
committed
update docs
1 parent 048652a commit e1fe879

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Guides/Quickstart.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ $ docker run -it --rm \
8888
Inside the container, run the `unidoc-build` command and pass it a single argument, which is the name of the package you want to build documentation for. In our case, the “package” is `swift`, which is a special name identifying the standard library itself.
8989

9090
```bash
91-
# unidoc-build swift -f
91+
# unidoc-build swift
9292
```
9393

9494
If you navigate to [`localhost:8443/`](https://localhost:8443/) in a browser, you should notice a new documentation volume under **Recent docs** named *swift*.
@@ -122,7 +122,7 @@ $ docker run -it --rm \
122122
Inside the container, run `unidoc-build`, and pass the path to the `/projects/` directory to the `--input` option. Use `swift-nio` as the package name; this **must** match the name of project directory.
123123

124124
```bash
125-
# unidoc-build swift-nio -f --input /projects
125+
# unidoc-build swift-nio --input /projects
126126
```
127127

128128
Unidoc will launch a `swift build` process, which could take a few minutes. It will then compile, upload, and link the documentation. When it is done, you should see a new documentation volume under **Recent docs** named *swift-nio*. Because the documentation is local, it will have the version number `0.0.0`.

0 commit comments

Comments
 (0)