#45 Fan-in Fan-out values inversion?

[natsumme]

It seems the Fan-in and Fan-out values are inverted in the HTML reports.
Fan-in corresponds to the number of suppliers of a class and Fan-out to the number of clients of a class
However, the following definitions taken from
"Guide to the software architectural design phase", ESA Board for Software Standardisation and Control(BSSC), ESA PSS-05-04 Issue 1 Revision 1, March 1995
seems to say the contrary.

Fan-out:
The number of components that a component calls measures its
'fan-out'. Fan-out should usually be small, not more than seven. However
some kinds of constructs force much higher fan-out values (e.g. case
statements) and this is often acceptable.
Simple fan-out rules are: 'make the average fan-out seven or less' or
'make components depend on as few others as possible'.

Fan-in:
The number of components that call a component measures its
'fan-in'. Reusability increases as fan-in increases.
Simple fan-in rules are: 'maximise fan-in' and 'reuse components as
often as possible'.

Please correct me if I'm wrong.

Sincerly