chore: update message

documentation/docs/98-reference/.generated/compile-warnings.md

@@ -635,7 +635,7 @@ In some situations a selector may target an element that is not 'visible' to the
 ### custom_element_props_identifier
 
 ```
-Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructure all the props or add the `customElement.props` option.
+Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructuring all the props or add the `customElement.props` option.
 ```
 
 ### element_implicitly_closed

packages/svelte/messages/compile-warnings/script.md

@@ -1,6 +1,6 @@
 ## custom_element_props_identifier
 
-> Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructure all the props or add the `customElement.props` option.
+> Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructuring all the props or add the `customElement.props` option.
 
 ## export_let_unused
 

packages/svelte/src/compiler/warnings.js

@@ -594,11 +594,11 @@ export function options_renamed_ssr_dom(node) {
 }
 
 /**
- * Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructure all the props or add the `customElement.props` option.
+ * Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructuring all the props or add the `customElement.props` option.
  * @param {null | NodeLike} node
  */
 export function custom_element_props_identifier(node) {
-	w(node, 'custom_element_props_identifier', `Using an identifier or a rest element as the declarator for \`$props\` when compiling to custom elements without declaring \`props\` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructure all the props or add the \`customElement.props\` option.\nhttps://svelte.dev/e/custom_element_props_identifier`);
+	w(node, 'custom_element_props_identifier', `Using an identifier or a rest element as the declarator for \`$props\` when compiling to custom elements without declaring \`props\` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructuring all the props or add the \`customElement.props\` option.\nhttps://svelte.dev/e/custom_element_props_identifier`);
 }
 
 /**

packages/svelte/tests/validator/samples/custom-element-props-identifier-rest/warnings.json

@@ -17,7 +17,7 @@
 			"column": 15,
 			"line": 4
 		},
-		"message": "Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructure all the props or add the `customElement.props` option.",
+		"message": "Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructuring all the props or add the `customElement.props` option.",
 		"start": {
 			"column": 7,
 			"line": 4

packages/svelte/tests/validator/samples/custom-element-props-identifier/warnings.json

@@ -17,7 +17,7 @@
 			"column": 10,
 			"line": 4
 		},
-		"message": "Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructure all the props or add the `customElement.props` option.",
+		"message": "Using an identifier or a rest element as the declarator for `$props` when compiling to custom elements without declaring `props` in the component options means that Svelte can't know which props to expose as properties on the DOM element. Consider explicitly destructuring all the props or add the `customElement.props` option.",
 		"start": {
 			"column": 5,
 			"line": 4