indent

diff --git a/examples/step-49/doc/intro.dox b/examples/step-49/doc/intro.dox
index 83121c5ccfaf8e1c373a0d108722173f9b2d536e..6a174ad14792cfb5962a9cc7b5cddda687e4a361 100644 (file)
--- a/examples/step-49/doc/intro.dox
+++ b/examples/step-49/doc/intro.dox
@@ -306,7 +306,7 @@ specified boundaries.
 
 <img src="https://www.dealii.org/images/steps/developer/step-49.gmsh_picture_2Dmesh_ids.png" alt="">
 
-Finally, we can choose  <code>Mesh -> Save</code> to save the <code>.msh</code> file, which 
+Finally, we can choose  <code>Mesh -> Save</code> to save the <code>.msh</code> file, which
 deal.II's GridIn class can read. You can also generate the <code>.msh</code> from the
 <code>.geo</code> file by running the command
 

diff --git a/examples/step-49/step-49.cc b/examples/step-49/step-49.cc
index 4a81613d77a99d9b744f6e89688861068c03666c..0fff1d213916454ab772e5200414b77b0469f27d 100644 (file)
--- a/examples/step-49/step-49.cc
+++ b/examples/step-49/step-49.cc
@@ -110,14 +110,14 @@ void print_mesh_info(const Triangulation<dim> &triangulation,
 // GMSH_LIBRARY
 // @endcode
 //
-// when building deal.II, then <code>DEAL_II_GMSH_WITH_API</code> gets defined and
-// and we can use <code>GridIn::read_msh()</code>.  More details on the function
-// can be found in its deal.II documentation.
+// when building deal.II, then <code>DEAL_II_GMSH_WITH_API</code> gets defined
+// and and we can use <code>GridIn::read_msh()</code>.  More details on the
+// function can be found in its deal.II documentation.
 //
 // We will be utilizing the SphericalManifold class for the holes. We need to
 // assign manifold IDs for this purpose. As physical IDs from Gmsh are assigned
-// to boundary IDs in deal.II, we will assign manifold IDs based on the boundary IDs loaded
-// from the file.
+// to boundary IDs in deal.II, we will assign manifold IDs based on the boundary
+// IDs loaded from the file.
 void grid_1()
 {
   const Point<2> Top_right_hole_origin(0.42, 2.0);
@@ -139,8 +139,10 @@ void grid_1()
   // hole. We assign both of these boundary IDs 2 because together they make a
   // circle to match the manifold we assign it later.
   triangulation.set_all_manifold_ids_on_boundary(1, 1); // top right hole
-  triangulation.set_all_manifold_ids_on_boundary(2, 2); // top of bottom left hole
-  triangulation.set_all_manifold_ids_on_boundary(3, 2); // bottom of bottom left hole
+  triangulation.set_all_manifold_ids_on_boundary(2,
+                                                 2); // top of bottom left hole
+  triangulation.set_all_manifold_ids_on_boundary(
+    3, 2); // bottom of bottom left hole
 
   triangulation.set_manifold(1, Top_right_manifold);
   triangulation.set_manifold(2, Bottom_left_manifold);