From 8a5ca92b67ebebf800e9bb7324356d911d60737a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Dennis=20Gl=C3=A4ser?= <dennis.glaeser@iws.uni-stuttgart.de>
Date: Thu, 16 Mar 2023 15:00:42 +0100
Subject: [PATCH] [example][embedded][problem] minor edits

---
 examples/embedded_network_1d3d/problem.hh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/examples/embedded_network_1d3d/problem.hh b/examples/embedded_network_1d3d/problem.hh
index 3c7bb76107..e1065bb4ee 100644
--- a/examples/embedded_network_1d3d/problem.hh
+++ b/examples/embedded_network_1d3d/problem.hh
@@ -27,8 +27,8 @@
 // problem classes: `TissueTransportProblem` and `NetworkTransportProblem` for the
 // respective subdomains. The subdomain problem classes specify boundary and initial
 // conditions for the subdomains separately. For this setup, we specify boundary fluxes
-// (Neumann or Robin-type boundary conditions, weakly imposed) called
-//--somewhat not general enough--`Neumann` in DuMu<sup>x</sup>.
+// via the `neumann` function (note that despite its name, the function allows you to
+// implement both Neumann or Robin-type boundary conditions, weakly imposed).
 //
 // The subdomain problems are coupled to each other. This is evident from the
 // coupling manager pointer that is stored in each subdomain problem (and the
-- 
GitLab