Updates based on q chat logs

source/by-role/author/index.rst

@@ -1400,9 +1400,9 @@ Here are some controls that authors may encounter while editing content:
 
   |
 
-* Item Selector - Allows the user to select an item from configured sources. Clicking the **Add**
-  button opens a menu that lets the user pick from the list. Clicking on **Add & Close** or
-  **Add Selection** adds the selected item to the selector list
+* Item Selector - Allows the user to select an item from configured sources. It allows cross-referencing
+  and linking between items. Clicking the **Add** button opens a menu that lets the user pick from the list.
+  Clicking on **Add & Close** or **Add Selection** adds the selected item to the selector list
 
   .. image:: /_static/images/form-controls/form-control-item-selector.webp
      :width: 30 %

source/by-role/developer/common/content-modeling/content-modeling.rst

@@ -747,7 +747,7 @@ Content Types are one of two core types: **Pages** and **Components**. Both are
 
 #. Model: The content pieces that will be captured from the content authors for the page or component
 #. View: The view template that will render the content, typically to HTML markup (for Templated, not Headless, projects)
-#. Controller: The controller   that handles the incoming request for the page or component
+#. Controller: The controller that handles the incoming request for the page or component
 
 """""
 Pages

source/by-role/developer/common/content-modeling/form-controls/form-item-selector.rst

@@ -8,6 +8,9 @@ Item Selector Control
 =====================
 Item Selector control.
 
+The field type for an item selector control in a content model is ``node-selector``.
+Use a ``node-selector`` in your content model to allow cross-referencing and linking between items.
+
 -------
 Example
 -------

source/by-role/developer/common/static-content-access.rst

@@ -130,10 +130,10 @@ Please see :ref:`managing-secrets` for more information on how to manage/encode
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 Step 2: Add the controls and data source for uploading files to your S3 bucket to the content type
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-For our example, we'll add an ``Attachment`` field, which is of type ``node-selector`` that is bound to an AWS file upload
-data source, to the ``Page - Article`` content type. To do this:
+For our example, we'll add an ``Attachment`` field, which is of type ``node-selector`` (item selector control) that is
+bound to an AWS file upload data source, to the ``Article`` content type. To do this:
 
-#. Go to |projectTools| and open the ``Page - Article`` content type definition.
+#. Go to |projectTools| and open the ``Article`` content type definition.
 #. We'll add a data source where to upload our files. At the end of the **Data Sources** section, add a ``File Uploaded to S3 Repository`` data source with Title **S3 Upload** and Name **s3Upload**. In the **Profile Id** property, enter the name of ``profile.id`` configured in step 1.
 
    .. image:: /_static/images/guides/s3/attachments-datasource.webp
@@ -673,9 +673,9 @@ Please see :ref:`managing-secrets` for more information on how to manage/encode
 """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 Step 2: Add the control and data source for uploading video to AWS for transcoding, to the content type
 """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
-For our example, we'll add the Video Transcoding from S3 datasource and a Transcoded Video picker control to the ``Page - Article`` content type. To do this:
+For our example, we'll add the Video Transcoding from S3 datasource and a Transcoded Video picker control to the ``Article`` content type. To do this:
 
-#. Go to |projectTools| -> **Content Types** and open the ``Page - Article`` content type definition.
+#. Go to |projectTools| -> **Content Types** and open the ``Article`` content type definition.
 #. We'll add a data source where to upload a video that will be transcoded. At the end of the **Data Sources** section, add a ``Video Transcoding from S3`` data source with Title **Transcode** and Name **transcode**. In the **Input Profile Id** property, enter the MediaConvert ``profile.id`` configured in step 1, used for uploading and triggering the transcode job (``mediaconvert-default`` from the example in step 1). In the **Output Profile Id** property, note the S3 ``profile.id`` configured in step 1, used to access the files generated by the transcode job (``s3-default`` from the example in step 1).
 
    .. image:: /_static/images/guides/s3/mediaConvert-datasource.webp

source/by-role/system-admin/installation.rst

@@ -293,6 +293,8 @@ You can sign up for `Crafter Cloud <https://craftercms.com/products/crafter-clou
 ^^^^^^
 Docker
 ^^^^^^
+You can run CrafterCMS locally using Docker:
+
 """"""""""""""""""""""""""""""""""""
 Quick Start for Evaluation in Docker
 """"""""""""""""""""""""""""""""""""

source/getting-started/index.rst

@@ -14,7 +14,7 @@ Run CrafterCMS
 ^^^^^^^^^^^^^^^^^^^^^^^^
 Try CrafterCMS in Docker
 ^^^^^^^^^^^^^^^^^^^^^^^^
-If you have `Docker <https://www.docker.com/>`_ installed, you can start exploring CrafterCMS in a few minutes. Simply run the following command:
+If you have `Docker <https://www.docker.com/>`_ installed, you can start exploring CrafterCMS locally in a few minutes. Simply run the following command:
 
 .. code-block:: bash
 

source/reference/api/graphql.rst

@@ -291,7 +291,7 @@ Additionally you can create complex filters using expressions like ``and``, ``or
     }
   }
 
-You can also include fields from child components in your model, this applies to fields like ``node-selector``,
+You can also include fields from child components in your model, this applies to fields like ``node-selector`` (item selector control),
 ``checkbox-group`` and ``repeat`` groups. Filters can also be added to fields from child components.
 
 .. code-block:: text

source/reference/modules/studio.rst

@@ -616,7 +616,7 @@ Project Policy
     :version: 4.0.0
 
 The project policy configuration file allows the administrator to configure constraints for content being added to the project
-(via uploads), such as filename constraints, minimum/maximum size of files, permitted content types or file types (MIME-types), etc.
+(via uploads), such as filename/item name constraints, minimum/maximum size of files, permitted content types or file types (MIME-types), etc.
 
 *Note that the project policy does not apply to content created directly on disk via the Git or APIs.*