From the chapter on
Whatever the specific wording in that bulleted list, it is important to understand the message: Flyweight applies to the case where an important part of data can be shared among many objects because it is immutable. The example with font faces makes this quite clear; an example from everyday Java is
java.util.regex.Pattern, the holder of immutable extrinsic state, vs.
Matcher, the flyweight that reuses it and holds local intrinsic state. Many
Matchers can exist in parallel, all reusing the compiled regex on the inside.
This quote makes things clearer than the one from your question:
The more flyweights are shared, the greater the storage savings. The savings increase with the amount of shared state. The greatest savings occur when the objects use substantial quantities of both intrinsic and extrinsic state, and the extrinsic state can be computed rather than stored. Then you save on storage in two ways: Sharing reduces the cost of intrinsic state, and you trade extrinsic state for computation time.