X-Git-Url: http://www.git.cypherpunks.ru/?a=blobdiff_plain;f=doc%2Fusecases%2Fairgap.texi;h=a764ca626a5b4f36474db49484acfe0245084873;hb=bb7fe5e770586be9f44a8a7f3321a3139d5345bb;hp=2c75d19ee6a9386a86d430321641db2770143aa6;hpb=8994f66557a7f53c0d808416d16ca33202ac3968;p=nncp.git

diff --git a/doc/usecases/airgap.texi b/doc/usecases/airgap.texi
index 2c75d19..a764ca6 100644
--- a/doc/usecases/airgap.texi
+++ b/doc/usecases/airgap.texi
@@ -1,4 +1,5 @@
 @node UsecaseAirgap
+@cindex air-gap
 @section Highly secure isolated air-gap computers
 
 If you worry much about security, then air-gapped computer could be the
@@ -35,11 +36,11 @@ reached via online connection using @emph{lan} address.
 @emph{bob-airgap} can be reached by sending intermediate relay packet
 through the @emph{bob}.
 
-Any command like @command{nncp-file myfile bob-airgap:} will
+Any command like @command{@ref{nncp-file} myfile bob-airgap:} will
 automatically create an encapsulated packet: one for the destination
 endpoint, and other carrying it for intermediate relaying node.
 
 Pay attention that relaying node knows nothing about the packet inside,
 but just its size and priority. Transition packets are encrypted too:
 using well-known @url{https://en.wikipedia.org/wiki/Onion_routing, onion
-routing} technology. @emph{bob} can not read @emph{bob-airgap}'s packets.
+encryption} technology. @emph{bob} can not read @emph{bob-airgap}'s packets.