address a few comments

Author: lorisercole

docs/blog/posts/2026/02/Spack-on-top-of-EESSI-best-of-both-worlds.md

@@ -22,20 +22,24 @@ This utility provides you with a pre-configured EasyBuild installation that you
 Like EasyBuild, [Spack](https://spack.io) is a flexible build tool that also offers a vast repository of build recipes maintained by a large and active community, making it a familiar tool for many HPC users.
 By enabling Spack to leverage packages already available in EESSI as dependencies, we can offer users the best of both worlds: the convenience of a pre-built, optimized software stack combined with the flexibility to quickly build new packages using tools they already know.
 
+<!-- more -->
+
+
 In a previous [blog post](https://www.eessi.io/docs/blog/2026/01/09/Spack-on-top-of-EESSI-PoC/), we presented a first proof-of-concept implementation of this vision. 
 We used a custom-built upstream database to make Spack aware of EESSI's software stack and managed to build a new Quantum ESPRESSO installation that reused dependencies from EESSI.
 
 Thanks to recent updates to Spack (in particular, treating externals as concrete specs and allowing the definition of dependencies – see [this PR](https://github.com/spack/spack/pull/51118)) and an active collaboration with its developers, it is now possible to connect Spack and EESSI in a *seamless* and *Spack-native* way.
 
-<!-- more -->
-
-
 ## How it works
 
 Spack 1.1+ introduces external packages treated as concrete specs (i.e. like any other spec), with dependency support, allowing us to expose EESSI packages as externals along with their dependencies.
-This is the proper, *Spack-onic* way to achieve our goal, and it does not require any* modification of Spack's source code, nor the creation of a custom database.
+This is the proper, *Spack-onic* way to achieve our goal, and it does not require any modification of Spack's source code, nor the creation of a custom database.
+
+!!! note
 
-(*note: currently we need to add a small patch to Spack, to make sure its compiler wrapper works correctly with the unusual sysroot configuration of EESSI. This is a known [issue](https://github.com/spack/spack/issues/51582) that will be addressed in future Spack releases.)
+    Currently we need to add a small patch to Spack to make sure its compiler wrapper works correctly
+    with the unusual sysroot configuration of EESSI. This is a known
+    [issue](https://github.com/spack/spack/issues/51582) that will be addressed in future Spack releases.)
 
 We implement the following workflow to connect Spack to EESSI, and build a new Quantum ESPRESSO with Spack reusing EESSI packages as dependencies.
 
@@ -48,16 +52,18 @@ Declare EESSI software-layer builds as [external packages](https://spack.readthe
 
 *Variants* (e.g. `~mpi+openmp`) should be specified to the best of our knowledge. By default, Spack will fill in the gaps with the package's default variants.
 
-*Link* and *runtime dependencies* should be specified whenever possible. Pure build dependencies are not needed (the only exception being the *compiler*, Spack can reuse this information).
-A dependency spec should unambiguously point to another declared external package. If an ambiguity exists, Spack will throw an error.<br>
-Many packages in EESSI depends on packages of the compatibility layer (e.g. `zlib`), that were filtered out during the build process. To detect these packages, see the [next step](#step-2-optional-suggested-eessi-compat-layer).<br>
+*Link* and *runtime dependencies* should be specified whenever possible. Pure build dependencies are not needed (the only exception being the *compiler*, Spack can reuse this information). A dependency spec should unambiguously point to another declared external package. If an ambiguity exists, Spack will throw an error.
+
+Many packages in EESSI depends on packages of the compatibility layer (e.g. `zlib`), that were filtered out during the build process. To detect these packages, see the [next step](#step-2-optional-suggested-eessi-compat-layer).
+
 Anyway, software packages in EESSI are always RPATH-ed to their dependencies, so in most real-case scenarios linking will likely work even if you forget to declare some dependencies. 
 
 
 ### Step 2 – (optional, suggested) EESSI compat-layer
 
 It is possible to detect OS packages available under the EESSI compat-layer and configure Spack to use them as externals.
-In EESSI, these packages are often dependencies of software-layer packages (see previous example), so it is suggested to include them.<br>
+In EESSI, these packages are often dependencies of software-layer packages (see previous example), so it is suggested to include them.
+
 This can be done automatically via `spack external find`:
 
 ![Detect compat-layer packages with spack external find](spack-eessi-20260205-002.webp)
@@ -80,7 +86,8 @@ We first check what the concretizer comes up with, using `spack spec`:
 
 ![Spack spec for quantum-espresso](spack-eessi-20260205-004.webp)
 
-Looks good! Spack is reusing EESSI packages as external dependencies, and only needs to build the new package itself and a few (Spack-specific) ones (`compiler-wrapper`, `gcc-runtime` which is copy of runtime libraries).
+Looks good! Spack is reusing EESSI packages as external dependencies. 
+It only needs to build the new `quantum-espresso` itself and a few Spack-specific packages: `compiler-wrapper` that is Spack's compiler wrapper, and `gcc-runtime` that is a local copy of the GCC runtime libraries that are provided by EESSI's `gcc@13.2.0`.
 
 Finally, we can proceed with the installation with `spack install quantum-espresso~mpi`:
 
@@ -97,7 +104,7 @@ When we inspect the `pw.x` binary, we can see that it links to libraries provide
 
 ![Inspecting the list of libraries that `pw.x` binary links to](spack-eessi-20260205-007.webp)
 
-(the only exception being `libgomp`, `libgfortran`, `libgcc_s` which come from the `gcc-runtime` package that Spack installs: this is just a local copy of the GCC runtime libraries that were provided by EESSI's `gcc@13.2.0`).
+(the only exception being `libgomp`, `libgfortran`, `libgcc_s` which come from the `gcc-runtime` package that Spack installs).
 
 
 ## Demo code