- Rolled back docs change

Author: heath-freenome

packages/docs/docs/migration-guides/v6.x upgrade guide.md

@@ -1,4 +1,4 @@
-# ^6.x Upgrade Guide
+# 6.x Upgrade Guide
 
 ## New packages
 
@@ -189,7 +189,7 @@ Interfaces with `formContext` removed:
 
 The `onChange` handling for fields has been changed to fix a serious bug related to nearly simultaneous updates losing data.
 Previously in 5.x, data change handling worked by passing a complete `newFormData` object up to the `Form` from the underlying `Field`s.
-In ^6.x, data change handling now works by passing just the changed `newValue` for a `Field` and the `path` array of the `Field` within the `formData`, with the `Form` itself being responsible for injecting the changed data into the `formData`.
+In 6.x, data change handling now works by passing just the changed `newValue` for a `Field` and the `path` array of the `Field` within the `formData`, with the `Form` itself being responsible for injecting the changed data into the `formData`.
 
 As a result, the `FieldProps` interface was updated with the following breaking change so that custom `Field` authors are forced to respond to this update:
 
@@ -999,13 +999,13 @@ Because `liveValidate` and `liveOmit` can have serious performance impacts in th
 
 ### Optional Data Controls
 
-RJSF ^6.x introduces a new feature that allows developers to provide a condensed UI for users who don't care to enter an optional list of array items or set of optional object fields.
+RJSF 6.x introduces a new feature that allows developers to provide a condensed UI for users who don't care to enter an optional list of array items or set of optional object fields.
 
 See the documentation for [enableOptionalDataFieldForType](../api-reference/uiSchema.md#enableoptionaldatafieldfortype) for more information.
 
 ### Dynamic UI Schema for Array Items
 
-RJSF ^6.x introduces a new feature that allows dynamic UI schema generation for array items.
+RJSF 6.x introduces a new feature that allows dynamic UI schema generation for array items.
 The `items` property in a `uiSchema` can now accept a function that returns a UI schema based on the array item's data, index, and form context.
 
 ```typescript
@@ -1027,10 +1027,10 @@ See the [Dynamic UI Schema Examples](../api-reference/dynamic-ui-schema-examples
 
 ### Custom field `name` generation
 
-RJSF ^6.x adds support for customizing how HTML `name` attributes are generated for form fields via the new [`nameGenerator`](../api-reference/form-props.md#namegenerator) prop. This enables proper form data submission to backend frameworks that expect specific naming conventions like bracket notation (`root[tasks][0][title]`) for PHP/Rails or dot notation (`root.tasks.0.title`) for other frameworks.
+RJSF 6.x adds support for customizing how HTML `name` attributes are generated for form fields via the new [`nameGenerator`](../api-reference/form-props.md#namegenerator) prop. This enables proper form data submission to backend frameworks that expect specific naming conventions like bracket notation (`root[tasks][0][title]`) for PHP/Rails or dot notation (`root.tasks.0.title`) for other frameworks.
 
 The default behavior is unchanged if the prop is not provided.
 
 ### Opt-in Fallback UI for unsupported types
 
-RJSF ^6.x introduces a new `FallbackField` component that provides a user-friendly UI for unsupported or unrecognized schema types. This new functionality displays a selection box used to choose a JSON primitive type, and a field for the formData that matches the selected type. To use this new feature, which takes the place of the existing `UnsupportedField` component, set the new `useFallbackUiForUnsupportedType` prop to `true` on the `Form` component.
+RJSF 6.x introduces a new `FallbackField` component that provides a user-friendly UI for unsupported or unrecognized schema types. This new functionality displays a selection box used to choose a JSON primitive type, and a field for the formData that matches the selected type. To use this new feature, which takes the place of the existing `UnsupportedField` component, set the new `useFallbackUiForUnsupportedType` prop to `true` on the `Form` component.