In the README.txt for the films example, it says:
Without overriding those field types, the name field would have been guessed as a multi-valued string field type .... it makes more sense with this
particular data set domain to have the movie name be a single valued general full-text searchable field,
However, the actual Schema API call does not specify multiValued=false, just that it is of text_general type. That type is defined as multiValued, so the end result is multiValued as well, opposite to the explanation given.