issue-8347-reviewed the article and made changes

Author: Dinesh V B

src/_videos/fundamentals/add-new-product-attribute.md

@@ -87,7 +87,7 @@ xsi:noNamespaceSchemaLocation="urn:magento:framework:Module/etc/module.xsd">
 
 {% endcollapsible %}
 
-## Step 2 Create an InstallData script {#instgde-cli-multistore}
+## Step 2 Create an InstallData script {#CreateProductAttributeByUpgradeScript}
 
 Next, we need to create the InstallData script.
 Because adding an attribute technically adds records into several tables, such as `eav_attribute` and `catalog_eav_attribute,` this is data manipulation, not a schema change.
@@ -196,7 +196,7 @@ For now, we’ll just quickly go through most important ones:
 *  **visible_on_front:** A flag that defines whether an attribute should be shown on the “More Information” tab on the frontend
 *  **is_html_allowed_on_front:** Defines whether an attribute value may contain HTML
 
-## Step 3: Add a source model
+## Step 3: Add a source model {#AddSourceModel}
 
 Next, we need to create the source model:
 
@@ -342,36 +342,43 @@ It should be visible and in bold text.
 
 A product attribute of type multiselect or select will present selectable options to the user. These options may be added manually through the admin panel, or by upgrade script. The script process is slightly different depending on whether the options are being added at the moment of attribute creation or whether the options are being added at a later time to an existing attribute.
 
-### ADD OPTIONS ALONG WITH A NEW PRODUCT ATTRIBUTE
+### ADD OPTIONS ALONG WITH A NEW PRODUCT ATTRIBUTE {#AddOptionsAlongNewProductAttribute}
 
-Basic instructions for creating a product attribute by setup or upgrade script can be found [in DevDocs]{#instgde-cli-multistore}. Before scripting the attribute creation, pick one of these two use cases for your options:
+Basic instructions for creating a product attribute by setup or upgrade script can be found [in DevDocs](#CreateProductAttributeByUpgradeScript). Before scripting the attribute creation, pick one of these two use cases for your options:
 
 *  You want a set of options which cannot be modified by a user through the admin panel, and which can only be changed through a future code push.
 *  You want a set of options which can be modified, added, or deleted through the admin panel by any user with admin access and proper authorization.
 
-In the case of Use Case 1 (an 'immutable' set of options), follow Magento's instructions entitled "Step 3: Add a source model." You will create a model that contains and dynamically, on block rendering, returns your attribute's selectable options to the client.
+In the case of Use Case 1 (an 'immutable' set of options), follow Magento's instructions entitled ["Add a source model"](#AddSourceModel) You will create a model that contains and dynamically, on block rendering, returns your attribute's selectable options to the client.
 
-In the case of Use Case 2 (a 'mutable' set of options), review Magento's article entitled "EAV and extension attributes," noting especially the attribute option entitled option. Also make certain to declare 'Magento\Eav\Model\Entity\Attribute\Source\Table' as the value for the 'source' attribute option. This ensures that Magento will store options in the appropriate database table.
+In the case of Use Case 2 (a 'mutable' set of options), review Magento's article entitled ["EAV and extension attributes"](_site/guides/v2.4/extension-dev-guide/attributes.html), noting especially the attribute option entitled option. Also make certain to declare 'Magento\Eav\Model\Entity\Attribute\Source\Table' as the value for the 'source' attribute option. This ensures that Magento will store options in the appropriate database table.
 
 Investigating \Magento\Eav\Setup\EavSetup.php::addAttribute() and \Magento\Eav\Setup\EavSetup.php::addAttributeOptions() reveals that you may add a series of options with the following array:
+
 'option' => ['values' => ['Option 1', 'Option 2', 'Option 3', etc.]]
 
 Alternatively, you may designate a specific option sorting order as follows:
+
 'option' => ['values' => [8 => 'Option 1', 3 => 'Option 2', 11 => 'Option 3', etc.]]
 
-It's worth noting that store_id is hardcoded to default to 0 with no good way to change this other than overriding the class or using the plugin to intercept the database insert method, which would probably be a performance killer as often as that gets called.
+It's worth noting that store_id is hardcoded by default to 0 with no good way to change this other than overriding the class or using the plugin to intercept the database insert method, which would probably be a performance killer as often as that gets called.
+
+### ADD OPTIONS TO AN EXISTING PRODUCT ATTRIBUTE
+
+For relevant background, review the [preceding section](#AddOptionsAlongNewProductAttribute) on adding options at the same time as a new product attribute.
 
-ADD OPTIONS TO AN EXISTING PRODUCT ATTRIBUTE
-For relevant background, review the preceding section on adding options at the same time as a new product attribute.
+*  Adding options to an 'immutable' set of options is as simple as modifying your custom source model with the additional options you wish to provide.
 
-Adding options to an 'immutable' set of options is as simple as modifying your custom source model with the additional options you wish to provide.
+*  Adding options to a 'mutable' set of options leverages the same EavSetup object as you use when creating an attribute with options, but requires an additional step because EavSetup needs to know to which attribute you want to assign new options. This is an example of how you might do this:
 
-Adding options to a 'mutable' set of options leverages the same EavSetup object as you use when creating an attribute with options, but requires an additional step because EavSetup needs to know to which attribute you want to assign new options. This is an example of how you might do this:
 Assign an array of new options to a variable:
+
 $options = ['attribute_id' => null, 'values' => 'Option 1', 'Option 2', etc]];
 
 Update your array with the attribute ID from the database:
+
 $options['attribute_id'] = $eavSetup->getAttributeId($eavSetup->getEntityTypeId('catalog_product'), 'your_attribute_code');
 
 Add your options:
+
 $eavSetup->addAttributeOption($options);