Description of problem:

There is an incorrect reference to base10 units in the Size[UNIT] variable description.  The description is shown below:

Size[UNIT]
  Size  is  an  input  number that accepts an optional unit.  Input units are always treated as base two values, 
  regardless of capitalization, e.g. 'k' and 'K' both refer to 1024.  The default input unit is specified by letter, 
  followed by |UNIT.  UNIT represents other possible input units: bBsSkKmMgGtTpPeE.  b|B is bytes, s|S  is  sectors  
  of 512 bytes, k|K is kilobytes, m|M is megabytes, g|G is gigabytes, t|T is terabytes, p|P is petabytes, e|E is exabytes.  
  (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)

In this description it says that input units are always treated as base two values, then goes on to say that case does not matter.  However, when showing example units, the base10 is used, as in "k|K is kilobytes".  If we're only using base2 values, then it should be "k|K is kibibytes".

Version-Release number of selected component (if applicable):

lvm2-2.02.171-8.el7.x86_64
lvm2-libs-2.02.171-8.el7.x86_64

Expected results:

Possible edited description shown below:

Size[UNIT]
  Size  is  an  input  number that accepts an optional unit.  Input units are always treated as base two values, 
  regardless of capitalization, e.g. 'k' and 'K' both refer to 1024.  The default input unit is specified by letter, 
  followed by |UNIT. UNIT represents other possible input units: bBsSkKmMgGtTpPeE. b|B is bytes, s|S  is  sectors 
  of 512 bytes, k|K is kibibytes, m|M is mebibytes, g|G is gibibytes, t|T is tebibytes, p|P is pebibytes, e|E is 
  exbibytes. (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)