Update documentation for v4.2

docs/models/circuits/circuitgroup.md

@@ -1,7 +1,5 @@
 # Circuit Groups
 
-!!! info "This feature was introduced in NetBox v4.1."
-
 [Circuits](./circuit.md) can be arranged into administrative groups for organization. The assignment of a circuit to a group is optional.
 
 ## Fields

docs/models/circuits/circuittermination.md

@@ -23,6 +23,8 @@ If selected, the circuit termination will be considered "connected" even if no c
 
 ### Termination
 
+!!! info "This field replaced the `site` and `provider_network` fields in NetBox v4.2."
+
 The [region](../dcim/region.md), [site group](../dcim/sitegroup.md), [site](../dcim/site.md), [location](../dcim/location.md) or [provider network](./providernetwork.md) with which this circuit termination is associated. Once created, a cable can be connected between the circuit termination and a device interface (or similar component).
 
 ### Port Speed

docs/models/circuits/virtualcircuit.md

@@ -1,5 +1,7 @@
 # Virtual Circuits
 
+!!! info "This feature was introduced in NetBox v4.2."
+
 A virtual circuit can connect two or more interfaces atop a set of decoupled physical connections. For example, it's very common to form a virtual connection between two virtual interfaces, each of which is bound to a physical interface on its respective device and physically connected to a [provider network](./providernetwork.md) via an independent [physical circuit](./circuit.md).
 
 ## Fields

docs/models/circuits/virtualcircuittermination.md

@@ -1,5 +1,7 @@
 # Virtual Circuit Terminations
 
+!!! info "This feature was introduced in NetBox v4.2."
+
 This model represents the connection of a virtual [interface](../dcim/interface.md) to a [virtual circuit](./virtualcircuit.md).
 
 ## Fields