Initial clean up the language in the manual pages.

[gnn]

Summary

The manual pages need a bit of editing for language and clarity.

[0mp]

lib/libcasper/libcasper/libcasper.3

89–90

acacce looks like a typo

lib/libcasper/libcasper/libcasper_service.3

50

In the other manual page, the name of the service seems to be consistently lowercase "casper". I'm not sure if we need to make it consistent across all manual pages.

61

This sentence does not read well. "containing" does not seem to fit at all, does it?

64

I think that mandoc -Tlint recommends to avoid contractions in manual pages.

[debdrup]

Also, to channel bcr:
Remember to bump .Dd :)

[oshogbo]

Wow, thank you, @gnn, for looking at this. I appreciate that!

lib/libcasper/libcasper/libcasper.3

81

This line is longer then 80 lines.

110

and?

118

This line is longer then 80, I'm not sure if this is a bug anymore.

126–127

The domain socket may or may not be provided in cap_wrap.
The Casper daemon may create a socket using cap_init and you also can obtain this descriptor.
Maybe something like:

The
.Fn cap_unwrap
function returns the
.Xr unix 4
domain socket used by the daemon service,
and frees the
.Vt cap_channel_t
structure.

194

I'm not sure what the convention is but in other cases after Oxford Comma you put a new line.

[gnn]

• Address review comments from 0mp, debdrup and oshogbo

[0mp]

lib/libcasper/libcasper/libcasper.3

118

The word *uses* disappeared in the process.

147

lib/libcasper/libcasper/libcasper_service.3

63–64

How about?

where the first argument of the function contains an 
.Xr nvlist 9
of old service limits
and the second argument contains the new limits

[gnn]

• Fix two more nits from 0mp

[debdrup]

There's only one minor nit, but otherwise it looks good to me.

lib/libcasper/libcasper/libcasper_service.3

60–61

There's a period missing at the end of this sentence.