summaryrefslogtreecommitdiff
path: root/doc/specification
diff options
context:
space:
mode:
authorOliver Reiche <oliver.reiche@huawei.com>2023-06-02 10:12:31 +0200
committerOliver Reiche <oliver.reiche@huawei.com>2023-06-12 16:29:05 +0200
commitec1e9292a887dbb96668f75c1bc86f795ce1c780 (patch)
tree8ed17e43e16425c588057a321c1fd4b5f1c47d29 /doc/specification
parentb66a7359fbbff35af630c88c56598bbc06b393e1 (diff)
downloadjustbuild-ec1e9292a887dbb96668f75c1bc86f795ce1c780.tar.gz
doc: Minor format and consistency improvements
Diffstat (limited to 'doc/specification')
-rw-r--r--doc/specification/remote-protocol.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/specification/remote-protocol.md b/doc/specification/remote-protocol.md
index 1afd7e32..af10d2b8 100644
--- a/doc/specification/remote-protocol.md
+++ b/doc/specification/remote-protocol.md
@@ -140,6 +140,7 @@ message as it is done in the original protocol. The remote side promises
that each blob and subtree contained in the root tree is available in
the remote CAS. Such blobs and trees must be accessible, using the
streaming interface, without specifying the size (since sizes are not
-stored in a git tree). Due to the Protobuf 3 specification, which is
-used in this remote execution API, not specifying the size means the
-default value 0 is used.
+stored in a git tree). Due to the [Protobuf 3
+specification](https://protobuf.dev/reference/protobuf/proto3-spec/), which is
+used in this remote execution API, not specifying the size means the default
+value `0` is used.