Be consistent with `struct vattr' naming. Half of this manual used `vpp'

while the other half used `vap', and in one case resulted in code that
made no sense.  Replaced all of them with `vap'.

(Typically, `vpp' is a pointer to a pointer to a struct vnode anyway).

1 files changed, 4 insertions, 4 deletions

diff --git a/share/man/man9/VOP_ATTRIB.9 b/share/man/man9/VOP_ATTRIB.9
index 5c0f35587fe1..5f6ca19e7965 100644
--- a/share/man/man9/VOP_ATTRIB.9
+++ b/share/man/man9/VOP_ATTRIB.9
@@ -51,7 +51,7 @@ The arguments are:
 .Bl -tag -width cred
 .It Ar vp
 the vnode of the file
-.It Ar vpp
+.It Ar vap
 the attributes of the file
 .It Ar cred
 the user credentials of the calling process
@@ -81,11 +81,11 @@ appropriate error is returned.
 .Sh PSEUDOCODE
 .Bd -literal
 int
-vop_getattr(struct vnode *vp, struct vattr *vpp,
+vop_getattr(struct vnode *vp, struct vattr *vap,
 	    struct ucred *cred, struct proc *p)
 {
     /*
-     * Fill in the contents of *vpp with information from
+     * Fill in the contents of *vap with information from
      * the filesystem.
      */
     ...;
@@ -94,7 +94,7 @@ vop_getattr(struct vnode *vp, struct vattr *vpp,
 }
 
 int
-vop_setattr(struct vnode *vp, struct vattr *vpp,
+vop_setattr(struct vnode *vp, struct vattr *vap,
 	    struct ucred *cred, struct proc *p)
 {
     /*