  *
  *  <p>You do not create a Callout container as part of the normal layout
  *  of its parent container.
- *  Instead, it appears as a pop-up window on top of its parent.
+ *  Instead, it appears as a pop-up container on top of its parent.
  *  Therefore, you do not create it directly in the MXML code of your application.</p>
  *
  *  <p>Instead, you create is as an MXML component, often in a separate MXML file.

 *    <strong>Properties</strong>
 *    horizontalPosition="auto"
 *    verticalPosition="auto"
 *  /&gt;
 *  </pre>
 *
 *  @see spark.skins.mobile.CalloutSkin
 *
 *  @langversion 3.0
 *  @playerversion AIR 3

[IconFile("Callout.png")]

/**
 *  The Callout container is a SkinnablePopUpContainer that functions as a pop-up
 *  with additional owner-relative positioning options similar to PopUpAnchor.
 *  Callout also adds an optional <code>arrow</code> skin part that visually
 *  displays the direction toward the owner.
 *
 *  <p>You can also use the CalloutButton control to open a callout container. 
 *  The CalloutButton control encapsulates in a single control the callout container 
 *  and all of the logic necessary to open and close the callout. 
 *  The CalloutButton control is then said to the be the owner, or host, 
 *  of the callout.</p>
 *
 *  <p>Callout uses the <code>horizontalPosition</code> and
 *  <code>verticalPosition</code> properties to determine the position of the
 *  Callout relative to the owner that is specified by the <code>open()</code>
 *  method. 
 *  Both properties can be set to <code>CalloutPosition.AUTO</code> which selects a
 *  position based on the aspect ratio of the screen for the Callout to fit
 *  with minimal overlap with the owner and and minimal adjustments at the
 *  screen bounds.</p>
