Merge pull request #7324 from jonathoncove3/patch-4

Update rendering-forms.md

Author: sofietoft

13/umbraco-forms/developer/rendering-forms.md

@@ -18,7 +18,7 @@ Six parameters can be provided:
 
 - `formId` is the GUID of a form.
 - `theme` is the name of a theme. If not provided, the default theme is used (see [Themes](./themes.md)).
-- `includeScripts` indicates whether scripts should be rendered with the form (see [Rendering Scripts](./rendering-scripts.md).
+- `includeScripts` indicates whether scripts should be rendered with the form. This is necessary for using conditional fields. See [Rendering Scripts](./rendering-scripts.md) for more details.
 - `recordId` is an optional existing record GUID, used if editing records via the website is [enabled in configuration](../developer/configuration/README.md#alloweditableformsubmissions)
 - `redirectToPageId` is an optional GUID for a content page that, if provided, is redirected to once the form has been submitted. It will be used in preference to post-submission behavior defined on the form itself.
 - `additionalData` is an optional dictionary of string values. When provided it will be used as a source for ["magic string" replacements](./magic-strings.md). The data will be associated with the created record and made available for custom logic or update within workflows.
@@ -71,4 +71,4 @@ Similarly, you can reference a form picker property on your page:
 {
     @await Umbraco.RenderMacroAsync("renderUmbracoForm", new { FormGuid = formId, FormTheme = Model.FormTheme, ExcludeScripts = "1" })
 }
-```
+```