mkdocs fixups

Author: ilyagr

docs/sapling-comparison.md

@@ -3,7 +3,7 @@
 ## Introduction
 
 This document attempts to describe how jj is different
-from [Sapling](sapling-scm.com). Sapling is a VCS developed by Meta. It is a
+from [Sapling](https://sapling-scm.com). Sapling is a VCS developed by Meta. It is a
 heavily modified fork of [Mercurial](https://www.mercurial-scm.org/). Because
 jj has copied many ideas from Mercurial, there are many similarities between the
 two tools, such as:

docs/technical/architecture.md

@@ -76,10 +76,10 @@ graph TD;
 
 ### Backend
 
-The [`Backend`](../../lib/src/backend.rs) trait defines the interface each
+The `Backend` trait defines the interface each
 commit backend needs to implement. The current in-tree commit backends
-are [`GitBackend`](../../lib/src/git_backend.rs)
-and [`LocalBackend`](../../lib/src/local_backend.rs).
+are `GitBackend`
+and `LocalBackend`.
 
 Since there are non-commit backends, the `Backend` trait should probably be
 renamed to `CommitBackend`.

docs/technical/concurrency.md

@@ -60,7 +60,7 @@ tags, and the working-copy commit in each workspace. The operation object
 contains a pointer to the view object (like how commit objects point to tree
 objects), pointers to parent operation(s) (like how commit objects point to
 parent commit(s)), and metadata about the operation. These types are defined
-[here](../../lib/protos/op_store.proto). The operation log is normally linear.
+in `op_store.proto` The operation log is normally linear.
 It becomes non-linear if there are concurrent operations.
 
 When a command starts, it loads the repo at the latest operation. Because the
@@ -90,7 +90,7 @@ it will do a 3-way merge of the view objects based on their common ancestor
 are recorded in the resulting view object. For example, if branch `main` was
 moved from commit A to commit B in one operation and moved to commit C in a
 concurrent operation, then `main` will be recorded as "moved from A to B or C".
-See the `RefTarget` [definition](../../lib/protos/op_store.proto).
+See the `RefTarget` definition in `op_store.proto`.
 
 Because we allow branches (etc.) to be in a conflicted state rather than just
 erroring out when there are multiple heads, the user can continue to use the