diff --git a/man/man3/fi_peer.3 b/man/man3/fi_peer.3
index d09c25c9607..31269e86492 100644
--- a/man/man3/fi_peer.3
+++ b/man/man3/fi_peer.3
@@ -1,6 +1,6 @@
 .\" Automatically generated by Pandoc 2.5
 .\"
-.TH "fi_peer" "3" "2022\-11\-04" "Libfabric Programmer\[cq]s Manual" "#VERSION#"
+.TH "fi_peer" "3" "2022\-11\-29" "Libfabric Programmer\[cq]s Manual" "#VERSION#"
 .hy
 .SH NAME
 .TP
@@ -607,12 +607,11 @@ struct fi_peer_transfer_context {
 .PP
 Peer transfer contexts form a virtual link between endpoints allocated
 on each of the peer providers.
-The setup of a peer transfer context occurs through the fi_endpoint2()
+The setup of a peer transfer context occurs through the fi_endpoint()
 API.
-The main provider calls fi_endpoint2() passing in the FI_PEER_TRANSFER
-flag.
-When specified, the context parameter reference the struct
-fi_peer_transfer_context defined above.
+The main provider calls fi_endpoint() with the FI_PEER_TRANSFER mode bit
+set in the info parameter, and the context parameter must reference the
+struct fi_peer_transfer_context defined above.
 .PP
 The size field indicates the size of struct fi_peer_transfer_context
 being passed to the peer.
@@ -623,13 +622,13 @@ It may be used to report the capabilities and restrictions on peer
 transfers, such as whether memory registration is required, maximum
 message sizes, data and completion ordering semantics, and so forth.
 If the importing provider cannot meet these restrictions, it must fail
-the fi_endpoint2() call.
+the fi_endpoint() call.
 .PP
 The peer_ops field contains callbacks from the main provider into the
 peer and is used to report the completion (success or failure) of peer
 initiated data transfers.
 The callback functions defined in struct fi_ops_transfer_peer must be
-set by the peer provider before returning from the fi_endpoint2() call.
+set by the peer provider before returning from the fi_endpoint() call.
 Actions that the peer provider can take from within the completion
 callbacks are most unrestricted, and can include any of the following
 types of operations: initiation of additional data transfers, writing