From 1874e95d67ac557ad13b7823a5b92f188a52db44 Mon Sep 17 00:00:00 2001
From: Matthias Koefferlein <matthias@klayout.de>
Date: Fri, 22 Mar 2024 23:26:52 +0100
Subject: [PATCH] Doc update

---
 src/doc/doc/manual/lvs_connect.xml | 20 +++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/src/doc/doc/manual/lvs_connect.xml b/src/doc/doc/manual/lvs_connect.xml
index 6e99e3080..73e0cb454 100644
--- a/src/doc/doc/manual/lvs_connect.xml
+++ b/src/doc/doc/manual/lvs_connect.xml
@@ -407,7 +407,7 @@ connect(metal2, via1)
   With this definition, the netlist extractor is able to detect the fault
   and raise a warning or an error (in top level mode).
   The warning is shown on the log tab and indicates incomplete wiring plus
-  details about the disconnected subnets, formed by the soft connection.
+  details about the subnets, separated by the soft connections.
   </p>
 
   <p>
@@ -481,4 +481,22 @@ soft_connect(b, a)
   layer second.
   </p>
 
+  <h3>Soft connections and "must connect" nets</h3>
+
+  <p>
+  Soft connections and must connect nets (aka "connect_explicit" and "connect_implicit")
+  serve the same purpose - to detect incomplete wiring. Typically they are used
+  together, such as doing "connect_implicit" on VDD nets and "connect_explicit" 
+  on VDD and NWELL nets if the schematic circuits do not feature an explicit 
+  NWELL pin.
+  </p>
+
+  <p>
+  Soft connections are checked before connect_explicit and connect_implicit
+  are executed. This means, that soft connection errors cannot be masked by
+  declaring them "must connect". On the other hand, that is not a real issue
+  as both checks would raise an warning or error (in the top-level case).
+  It would only be a different kind of warning.
+  </p>
+
 </doc>