Add more details on Native Image mostly static linking

(cherry picked from commit 2a54b94)

Author: olyagpl

docs/reference-manual/native-image/guides/build-static-and-mostly-static-executable.md

@@ -15,10 +15,10 @@ However, you can create a statically linked or mostly-static linked native execu
 A static native executable is easy to distribute and deploy on a slim or distroless container (a scratch container).
 You can create a static native executable by statically linking it against [musl-libc](https://musl.libc.org/), a lightweight, fast and simple `libc` implementation.
 
-**A mostly-static native executable** is a binary that links everything except the standard C library, `glibc`. This is an alternative option to staticly linking everything.
+**A mostly-static native executable** is a binary that links everything (`zlib`, JDK shared libraries) except the standard C library, `libc`. This is an alternative option to staticly linking everything. Also, depending on the user's code, it may link `libstdc+` and `libgcc`.
 This approach is ideal for deployment on a distroless container image.
 
-> Note: This currently only works when linked against `glibc`.
+> Note: This currently only works when linked against `libc`.
 
 This guide shows how you can take advantage of Native Image linking options including fully dynamic, fully static, and mostly static (except `libc`) to generate an executable ideal for your deployment scenario.
 
@@ -100,8 +100,7 @@ This application iterates over your environment variables and prints out the one
 
 ## Build a Mostly-Static Native Executable
 
-With GraalVM Native Image you can build a mostly-static native executable that statically links everything except `libc`.
-Statically linking all your libraries except `glibc` ensures your application has all the libraries it needs to run on any Linux `glibc`-based distribution.
+With GraalVM Native Image you can build a mostly-static native executable that statically links everything except `libc`. Statically linking all your libraries except `libc` ensures your application has all the libraries it needs to run on any Linux `libc`-based distribution.
 
 To build a mostly-static native executable, use this command:
 
@@ -115,12 +114,15 @@ To build a  a mostly-static native executable for the above `EnvMap` demo, run:
 native-image -H:+StaticExecutableWithDynamicLibC EnvMap
 ```
 
+This produces a native executable that statically links all involved libraries (including JDK shared libraries) except for `libc`. This includes `zlib`. Also, depending on the user's code, it may link `libstdc+` and `libgcc`.
+One way to check what dynamic libraries your application depends on is to run `ldd` with the native executable, for example, `ldd helloworld`.
+
 ### Frequently Asked Questions
 
 #### What is the recommended base Docker image for deploying a static or mostly-static native executable?
 
 A fully static native executable gives you the most flexibility to choose a base container image - it can run on anything including a `FROM scratch` image.
-A mostly-static native executable requires a container image that provides `glibc`, but has no additional requirements.
+A mostly-static native executable requires a container image that provides `libc`, but has no additional requirements.
 In both cases, choosing the base container image generally depends on your native executable's specific requirements.
 
 ### Related Documentation