[dcl.type.cv]/6 "program behavior" vs "behavior"

[dcl.type.cv]/6 reads

> If an attempt is made to refer to an object defined with a volatile-qualified type through the use of a glvalue with
a non-volatile-qualified type, the program behavior is undefined.

This is probably meant to use the much more idiomatic phrase "the behavior is undefined". A distinction between well-definedness of the program's and the implementation's behavior would presumably be inappropriate, anyway.

Author: Arcoth

source/declarations.tex

@@ -1181,7 +1181,7 @@
 implementation-defined.
 If an attempt is made to refer to an object defined with a
 volatile-qualified type through the use of a glvalue with a
-non-volatile-qualified type, the program behavior is undefined.
+non-volatile-qualified type, the behavior is undefined.
 
 \pnum
 \indextext{type~specifier!\idxcode{volatile}}%