AngularJS never regenerates the HTML again.

AngularJS bindings are . . . . . , meaning that when the value associated with the binding is changed (in the data model), the HTML element will be updated.

You can use the . . . . . . directive, in order to bind the innerHTML of the element to the specified model property.

Any change to the . . . . and . . . . . properties affects these bindings and consequently the user interface content.

In two-way binding, changes done to a model are reflected in the view, but the reverse also holds true sometimes.

You can create bindings only for the data values that are added to the . . . . . object by the controller.

The ng-bind directive . . . . . . allow you to hide your template markup when the HTML content is shown to the user before it is processed by AngularJS.

The drawback of inline bindings is that AngularJS will not find and process every set of {{ and }} characters in your content.

When adding . . . . . and . . . . . . to a view, we are essentially instructing Angular to create data bindings that keep the model and view in sync.