DOC-3174: Some edits

Author: MitchC1999

modules/ROOT/pages/apis/tinymce.userlookup.adoc

@@ -15,15 +15,7 @@ Follow the steps below to configure and use the `userLookup` API within your int
 
 The first step is to tell the editor which user is currently active. This is done using the `+user_id+` initialization option.
 
-[source,js]
-----
-tinymce.init({
-  selector: '#editor',
-  user_id: 'user-42', // <1>
-  // ...
-});
-----
-**This ID will be used as the value of `+editor.userLookup.userId+`.**
+include::partial$configuration/user_id.adoc[leveloffset=+2]
 
 To access it:
 
@@ -37,19 +29,21 @@ editor.on('init', () => {
 [[step-2-provide-a-user-fetcher]]
 === 2. Provide a function to fetch user details
 
-To simulate a backend lookup, define a local object that maps user IDs to their corresponding data.
+To simulate a backend lookup, define a local object that maps user IDs to their corresponding data. 
+
+include::partial$configuration/fetch_users.adoc[]
 
 [source,js]
 ----
 const userDirectory = {
-  'user-1': { id: 'user-1', name: 'Jane Doe', avatar: 'https://example.com/avatar/jane.png' },
-  'user-2': { id: 'user-2', name: 'John Smith' },
-  'user-42': { id: 'user-42', name: 'Alex Taylor', avatar: 'https://example.com/avatar/alex.png' }
+  'janedoe': { id: 'janedoe', name: 'Jane Doe', avatar: 'https://example.com/avatar/jane.png' },
+  'johnsmith': { id: 'johnsmith', name: 'John Smith' },
+  'alextaylor': { id: 'alextaylor', name: 'Alex Taylor', avatar: 'https://example.com/avatar/alex.png' }
 };
 
 tinymce.init({
   selector: '#editor',
-  user_id: 'user-42',
+  user_id: 'alextaylor',
   fetch_users: (userIds) => {
     const results = userIds.map((id) => {
       const user = Object.values(userDirectory).find((user) => user.id === id);

modules/ROOT/pages/userlookup.adoc

@@ -1,7 +1,7 @@
 [[fetch_users]]
 == `fetch_users`
 
-A callback function that retrieves user data for the plugin. It receives an array of user IDs and returns a `Promise` resolving to an array of user objects. The callback uses the xref:#userlookupapi[`UserLookup API`].
+A **required callback function** that fetches user data for the Suggested Edits view. This function is called with an array of user IDs and should return a `Promise` that resolves to an array of user objects. The callback is used by the xref:userlookup.adoc[`UserLookup`] API.
 
 *Type:* `Function`
 
@@ -11,7 +11,8 @@ A callback function that retrieves user data for the plugin. It receives an arra
 *Returns:*
 - `Promise<Array<Object>>`: A promise that resolves to an array of user objects.
 
-.Example
+=== Example: using `fetch_users` option
+
 [source,javascript]
 ----
 tinymce.init({

modules/ROOT/partials/configuration/fetch_users.adoc

@@ -1,10 +1,10 @@
 [[suggestededits_content]]
 == `suggestededits_content`
-The `{plugincode}_content` option determines where the initial content of the document is loaded from. With this option, you can set the content to be loaded from either the editor or the model, allowing you to control the source of truth for the document.
+The `suggestededits_content` option determines where the initial content of the document is loaded from. With this option, you can set the content to be loaded from either the editor or the model, allowing you to control the source of truth for the document.
 
 When set to `'html'`, the editor loads the initial content from the HTML in the textarea or the `content` property. In this case, if a model is provided, it will need to match the content in the editor for the plugin to work correctly
 
-When set to `'model'`, the editor loads the initial content from the `{plugincode}_model` option. In this case, the content in the editor will be overwritten with the content from the model. This would allow you to only require the model for document tracking, though it is still recommended to save the content in the editor externally.
+When set to `'model'`, the editor loads the initial content from the `suggestededits_model` option. In this case, the content in the editor will be overwritten with the content from the model. This would allow you to only require the model for document tracking, though it is still recommended to save the content in the editor externally.
 
 In either case, if a model is not provided, the plugin will generate a new model from the current content of the editor, whether it is empty or not.
 
@@ -14,7 +14,7 @@ In either case, if a model is not provided, the plugin will generate a new model
 
 *Default value:* `'html'`
 
-=== Example: using `{plugincode}_content`
+=== Example: using `suggestededits_content`
 
 [source,js]
 ----

modules/ROOT/partials/configuration/suggestededits_content.adoc

@@ -1,15 +1,18 @@
 [[user_id]]
 == `user_id`
 
-This option specifies a unique identifier for the current user, enabling the plugin to distinguish between different users in the editor. The option uses the xref:#userlookupapi[`UserLookup API`].
+This option sets the unique identifier for the current user in the editor. It is used in the the xref:userlookup.adoc[`UserLookup`] API.
 
 *Type:* `+String+`
 
-.Example
+*Default value:* `'Anonymous'`
+
+=== Example: using `user_id` option
+
 [source,javascript]
 ----
 tinymce.init({
   selector: 'textarea',  // Change this value according to your HTML
-  user_id: 'unique-identifier' // replace this with a unique string to identify the user
+  user_id: 'alextaylor' // replace this with a unique string to identify the user
 });
 ----