diff --git a/src/v1/function-configuration.ts b/src/v1/function-configuration.ts
index bb5e07f8f..848d103ad 100644
--- a/src/v1/function-configuration.ts
+++ b/src/v1/function-configuration.ts
@@ -261,8 +261,8 @@ export interface DeploymentOptions extends RuntimeOptions {
    *
    * @remarks
    * When setting configuration available in the underlying platform that is not yet available in the Firebase Functions
-   * SDK, we highly recommend setting preserveExternalChanges to true. Otherwise, when Firebase Functions SDK releases
-   * a new version of the SDK with the support for the missing configuration, your functions manually configured setting
+   * SDK, we highly recommend setting `preserveExternalChanges` to `true`. Otherwise, when the Firebase Functions SDK releases
+   * a new version of the SDK with support for the missing configuration, your function's manually configured setting
    * may inadvertently be wiped out.
    */
   preserveExternalChanges?: boolean;
diff --git a/src/v2/options.ts b/src/v2/options.ts
index fc85bf148..91b9b8de6 100644
--- a/src/v2/options.ts
+++ b/src/v2/options.ts
@@ -198,8 +198,8 @@ export interface GlobalOptions {
    *
    * @remarks
    * When setting configuration available in the underlying platform that is not yet available in the Firebase Functions
-   * SDK, we highly recommend setting preserveExternalChanges to true. Otherwise, when Firebase Functions SDK releases
-   * a new version of the SDK with the support for the missing configuration, your functions manually configured setting
+   * SDK, we highly recommend setting `preserveExternalChanges` to `true`. Otherwise, when the Firebase Functions SDK releases
+   * a new version of the SDK with support for the missing configuration, your function's manually configured setting
    * may inadvertently be wiped out.
    */
   preserveExternalChanges?: boolean;