-"doesn't treat an important package in the same way as an extra package: "
-"Between the unpacking of the important package A and his configuration can "
-"then be many other unpack or configuration calls, e.g. for package B which "
-"has no relation to A, but causes the dpkg call to fail (e.g. because "
-"maintainer script of package B generates an error) which results in a system "
-"state in which package A is unpacked but unconfigured - each package "
-"depending on A is now no longer guaranteed to work as their dependency on A "
-"is not longer satisfied. The immediate configuration marker is also applied "
-"to all dependencies which can generate a problem if the dependencies e.g. "
-"form a circle as a dependency with the immediate flag is comparable with a "
-"Pre-Dependency. So in theory it is possible that APT encounters a situation "
-"in which it is unable to perform immediate configuration, error out and "
-"refers to this option so the user can deactivate the immediate configuration "
+"does treat an important package in the same way as an extra package: Between "
+"the unpacking of the important package A and his configuration can then be "
+"many other unpack or configuration calls, e.g. for package B which has no "
+"relation to A, but causes the dpkg call to fail (e.g. because maintainer "
+"script of package B generates an error) which results in a system state in "
+"which package A is unpacked but unconfigured - each package depending on A "
+"is now no longer guaranteed to work as their dependency on A is not longer "
+"satisfied. The immediate configuration marker is also applied to all "
+"dependencies which can generate a problem if the dependencies e.g. form a "
+"circle as a dependency with the immediate flag is comparable with a Pre-"
+"Dependency. So in theory it is possible that APT encounters a situation in "
+"which it is unable to perform immediate configuration, error out and refers "
+"to this option so the user can deactivate the immediate configuration "