"Add instructional text and other design elements to your forms by using form annotations in Form Builder."https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/form-builder/ta

Explanation/Reference: https://community.servicenow.com/community?
id=community_question&sys_id=cc3803addb1cdbc01dcaf3231f9619b6

Configuring the label of a field in a child table changes the label only on that table, not on the base table or the parent table. The base table is the table that contains the common fields for all the extended tables, and the parent table is the table that is directly extended by the child table. The label of a field on the base table or the parent table can be different from the label on the child table. References: [ServiceNow Docs - Table extension], [ServiceNow Community - How to change field label in child table] Reference: https://community.servicenow.com/community? id=community_question
&sys_id=7ddc4462dbe2b3840be6a345ca9619af

Flow Designer runs automation based on triggers. A primary trigger type is a Record trigger, which starts a flow when a record is created, updated, or created or updated. This matches option A and is one of the most common ways to automate application behavior using table data. Flow Designer also supports triggers tied to SLA-related events, enabling flows to react when an SLA is approaching breach or breaches, which aligns to option E in the way the platform exposes SLA timing events for automation. In addition, flows can be started by an inbound request through supported APIs, allowing external systems or scripts to invoke flow execution, which aligns to option F. By contrast, elevating to security_admin is a privileged security operation, not a Flow trigger; logging in as a specific user is an authentication/session activity rather than an automation trigger; and outbound email is typically an action that a flow can send, not an event that triggers a flow. The correct answers focus on documented Flow trigger categories rather than UI or security behaviors.

The Application Repository is a central location for storing, managing, and distributing custom applications developed on the Now Platform.
From Developer Site > App Repo:
"The ServiceNow Application Repository stores custom applications and enables developers to distribute applications across multiple instances in their organization."