Updated nroff-generated man pages

Signed-off-by: OFIWG Bot <[email protected]>

man/man7/fi_provider.7

@@ -1,16 +1,38 @@
 .\" Automatically generated by Pandoc 2.9.2.1
 .\"
-.TH "fi_provider" "7" "2023\-11\-17" "Libfabric Programmer\[cq]s Manual" "#VERSION#"
+.TH "fi_provider" "7" "2023\-11\-18" "Libfabric Programmer\[cq]s Manual" "#VERSION#"
 .hy
+.SH NAME
+.PP
+fi_provider - Fabric Interface Providers
+.SH OVERVIEW
+.PP
+See \f[C]fi_arch\f[R](7) for a brief description of how providers fit
+into the libfabric architecture.
+.PP
+Conceptually, a fabric provider implements and maps the libfabric API
+over lower-level network software and/or hardware.
+Most application calls into the libfabric API go directly into a
+provider\[cq]s implementation of that API.
+.PP
+Libfabric providers are grouped into different type: core, utility,
+hooking, and offload.
+These are describe in more detail below.
+The following diagram illustrates the architecture between the provider
+types.
 .IP
 .nf
 \f[C]
-               |<-  [core provider] <-peer API-> [offload provider]
+---------------------------- libfabric API ---------------------------- 
+  [core]   provider|<- [hooking provider]
+[services]   API   |  --- libfabric API --- 
+                   |<- [utility provider]
+                   |  ---------------- libfabric API ------------------ 
+                   |<-  [core provider] <-peer API-> [offload provider]
 \f[R]
 .fi
 .PP
-\[ga]\[ga]\[ga] All providers plug into libfabric using an exported
-provider API.
+All providers plug into libfabric using an exported provider API.
 libfabric supports both internal providers, which ship with the library
 for user convenience, as well as external providers.
 External provider libraries must be in the library search path, end with