summaryrefslogtreecommitdiff
path: root/doc/tutorial/proto.org
diff options
context:
space:
mode:
authorKlaus Aehlig <klaus.aehlig@huawei.com>2022-12-08 15:52:51 +0100
committerKlaus Aehlig <klaus.aehlig@huawei.com>2022-12-09 15:25:24 +0100
commitb6775e85e3ba52b3b873e9fd54255c3614fba920 (patch)
tree3b1cc6fb8db7e0a63ea94d4236d61160e1d11089 /doc/tutorial/proto.org
parent6a6e0bea83bacee9f04d045b173ff94f9ec8017a (diff)
downloadjustbuild-b6775e85e3ba52b3b873e9fd54255c3614fba920.tar.gz
tutorial: add some clarifying comments
... on parts a first-time reader might (and actually did) stumble upon.
Diffstat (limited to 'doc/tutorial/proto.org')
-rw-r--r--doc/tutorial/proto.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/tutorial/proto.org b/doc/tutorial/proto.org
index c8ccc5fe..70950868 100644
--- a/doc/tutorial/proto.org
+++ b/doc/tutorial/proto.org
@@ -285,7 +285,7 @@ $
#+END_SRC
It should be noted, however, that this tight integration of proto
-into our ~C++~ rules is just convenience of our code base. If had
+into our ~C++~ rules is just convenience of our code base. If we had
to cooperate with rules not aware of proto, we could have created
a separate rule delegating the library creation to the anonymous
target and then simply reflecting the values of that target.