diff --git a/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md b/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md
index 4a5f06f..5214be8 100644
--- a/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md
+++ b/4a.-JCB-Demo-Component-Directory,-Folders-and-Files.md
@@ -292,13 +292,52 @@ defined('_JEXEC') or die('Restricted access');
 * libraries/src/Component/ComponentHelper.php.Joomla\CMS\Component\ComponentHelper::executeComponent:382  
 * components/com_demo/demo.php.require_once:35  
 
-Some links may be outdated. For example, the Joomla! Platform documentation is no longer maintained and Platform 14 is outdated plus obsolete. It is in the links since it has not been removed from current documentation and at times Joomla! 2.5 is referenced since it still functions as the documentation states. Joomla! has some extensive changes involving namespaces which it relies on heavily and locations of class files vary by release, especially with Joomla! 4 name space changes .
+We see from the NetBeans XDEBUG Trace exactly what line numbers are being reused from the Joomla! core (a myriad of code is behind most), to initiate the entry point for the JCB Demo component, demo.php in the last line, which eventually, using th e same Hoomla! API, which are located in the indictaed paths next, to display the looks view and edit button:
 
-Deprecated class names will be removed in Joomla! 5 so it is wise to use the new ones, aliased starting with Joomla! 3.8. Be sure you note and observe any changes in the current or future versions of Joomla! as code may break if Joomla! team removes it. If a class for example or design pattern is obsolete now and deprecated it is indicated very clearly. These and [other changes](https://developer.joomla.org/news/703-joomla-3-8-beta-released-for-testing.html) should be reviewed in preparation for Joomla! 4. For now, they facilitate backwards compatibility allowing them to be used before the change becomes mandatory for your components to still work.
+Custom Script
+Add PHP (after getting the items)*
+Yes
+
+PHP getItems Method
+Target (array) $items values *
+	// do a quick build of all edit links links
+		if (isset($items) && $items)
+		{
+			foreach ($items as $nr => &$item)
+			{
+				$canDo = [[[Component]]]Helper::getActions('look',$item,'looks');
+				if ($canDo->get('look.edit'))
+				{
+					$item->editLink = '<br /><br /><a class="uk-button uk-button-primary uk-width-1-1" href="';
+					$item->editLink .= JRoute::_('index.php?option=com_[[[component]]]&view=look&task=look.edit&id=' . $item->id);
+					$item->editLink .= '"><i class="uk-icon-pencil"></i><span class="uk-hidden-small">';
+					$item->editLink .= JText::_('Edit Look');
+					$item->editLink .= '</span></a>';
+				}
+				else
+				{
+					$item->editLink = '';
+				}
+			}
+		}
+
+
+
+
+## Editing the Site View  
+http://localhost/demo/administrator/index.php?option=com_componentbuilder&view=dynamic_get&layout=edit&id=36  
+
+
+Some below and previously may be outdated. For example, the Joomla! Platform documentation is no longer maintained and Platform 14 is outdated plus obsolete and the Joomla! 2.5 API Index may also appear. It is in the links since it has not been removed from current Joomla! documentation; many classes in use have early origins as stated in the documentation. Joomla! has some extensive changes though involving namespaces with Joomla! 4 which relies on it heavily. Locations of class files vary by release, made a bit more elusive with Joomla! 4 name space changes. But their is current backwards compatibility and hence alias list do exist as we shall see next.
+
+Since deprecated classes in Joomla 3.8.x will be removed in Joomla! 5 it is wise to use the new ones, aliased starting with Joomla! 3.8. Be sure you note and observe any changes in the current or future versions of Joomla! as code may break if the Joomla! team removes it. If a class for example or design pattern is obsolete now and deprecated it is indicated very clearly. These and [other changes](https://developer.joomla.org/news/703-joomla-3-8-beta-released-for-testing.html) should be reviewed in preparation for Joomla! 4. For now, class names that eventually will raise exceptions and error messages in your component code are facilitated; backwards compatibility exists until Joomla! 5.
 
 A class file that is very important to facilitate this and is currently being used is the class map of aliases for classes that do not conform to the namespace naming convention. The file at \libraries\classmap.php should be consulted when writing your own components. The path on the right has the locations and new standard naming for class files. 
  Be aware that if for eaxmple the path is indicated as JLoader::registerAlias('JControllerLegacy',                 '\\Joomla\\CMS\\MVC\\Controller\\BaseController', '5.0'); the physical path in Joomal! version 3.8.12 is \libraries\src\Application\BaseController.php; its class is  BaseController which extends JObject. What one needs to recall is the old ones will eventually be obsolete starting with Joomla! 5. They are currently deprecated and will log warnings in server log files. These are useful to allow cleaning them up eventually. Each line in the file has the path to the left that is aliased to the path on the right which is the deprecated one. Joomla! developers are using the namespace extensively and this conforms the classes to the new ones that should be used in your components sooner rather than later.
 
+There are some other areas where aliases exist that should be adhered to eventually for class names and their locations:  
+* 
+* 
 - [Add unobtrusive JavaScript support to keep a tab state.](https://api.joomla.org/cms-3/classes/JHtmlBehavior.html#method_tabstate)  
 \libraries\cms\html\behavior.php
 - [Get a document object and set the component css/js.](https://api.joomla.org/cms-2.5/classes/JFactory.html#method_getDocument)