Nesting Templates: Child-Template Pages not Fully Responding to Editable vs. Un-Editable Regions

Question

M'kay, so first and foremost, all of this is being done within Dreamweaver CS5. How I might explain this is that I have a series of Master-Templates for my website, accompanied then by Child-Templates linked off of / nested from my Master-Templates. So far this is going wonderfully, that is, until I try to make a page from one of my Child-Templates.
The page from my Child-Template accurately comments-out an un-editable region (Region in which was editable within the Master-Template, but left as ONLY editable within the Child-Template) so long as I add an EDITABLE region WITHIN it. Under the circumstance that I DO NOT add an editable region within the Master-Template's editable region, the region within the Page is still appearing editable.
For example:
Master Template:
<!-- TemplateBeginEditable name="ChildTemplateCSSLinks" -->
     Child Template CSS Links Here.
<!-- TemplateEndEditable -->
Child Template:
<!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
     Child Template CSS Links Here.
     <!-- TemplateBeginEditable name="ChildPageCSSLinks" -->
          Child PAGE CSS Links Here.
     <!-- TemplateEndEditable -->
<!-- InstanceEndEditable -->
Child Page:
Child Template CSS Links Here. (Accurately appearing Un-Editable - {Master-Template's editable region tags accurately appearing invisible})
<!-- InstanceBeginEditable name="ChildPageCSSLinks" -->
     Child PAGE CSS Links Here. (Accurately appearing Editable)
<!-- InstanceEndEditable -->
This is an example of an editable regions that WORKS. In the Child-Page the "Child Template CSS Links Here." IS appearing commented out and therefore un-editable within the Child-Page, like it's supposed to be. This then allows the "Child PAGE CSS Links Here" to be ACCURATELY editable within the Child-Page.
Now for an example of what DOESN'T work:
Master Template:
<!-- TemplateBeginEditable name="ChildTemplateCSSLinks" -->
     Child Template CSS Links Here.
<!-- TemplateEndEditable -->
Child Template:
<!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
     Child Template CSS Links Here.
     (As you see, I have NOT added an additional editable region within this Master-Template's editable region. This is an area that is ONLY supposed to be editable within the Child-Template and NOT the Child-Page, which SO FAR appears to be accurate.)
<!-- InstanceEndEditable -->
Child Page:
<!-- InstanceBeginEditable name="ChildTemplateCSSLinks" -->
     Child Template CSS Links Here.
     (For some reason, ONLY so long as I DO NOT add an additional Child-Template-editable-region within this Master-Template's editable region, this area is STILL appearing visible as well as editable within the Child-Page.)
<!-- InstanceEndEditable -->
So, under this circumstance, it seems that the only way I can leave a Master-Template's editable region ONLY editable within the Child-Template and NOT editable within the Child-Page is by leaving an ADDITIONAL editable region produced via the Child-Template somewhere within EVERY SINGLE editable region produced via the Master-Template. Unless I am doing something seriously wrong, this so far appears to be a potential defect/bug within Dreamweaver CS5. I can't imagine how this would be accurate, otherwise Child/Nested-Templates would not be possible to make. What might I be doing wrong? Is there any way that I can specify in the Master-Template that an Editable Region is ONLY Editable within the Child-Template and NOT within further Child-Pages (A Page based off of the Child-Template)? Or perhaps is there a way that I can specify in the Child-Template that an editable region WILL NOT be editable within the Child-Page? Furthermore, no, I DO NOT want to make them "Optional Regions," so please do not suggest that.
I know that this is all probably a bit confusing, but hopefully the examples above will help more than the descriptions aside. As you can probably assume, this is definitely a HUGE complication within my website if there doesn't end up being a solution, especially with all the time I have put into making the Child-Templates that I hope to rely on. It really would be a bit ridiculous if I had to script-in an additional editable region within every single Master-Template-editable-region available within my Child-Template just so that I may update my Child-Template, furthermore allowing my edits to drop down to my Child-Pages, especially since it would maintain content that I never wanted to be editable within the Child-Page in the FIRST place.
Some help would be sincerely appreciated, and as soon as possible, if I might ask politely.
Thank you. Sincerely,
~ Miss Cat

Answer 1

=____= I cannot believe that I am saying this, after writing ALL of that up, but thanks to "Dreamweaver CS5 for Dummies," I just learned that if you place: @@(" ")@@ within the Child/Nested Template's editable region that you DO NOT want passed down to your Child-Pages, it won't appear editable. Goodness knows why such an inconspicuous formula was the answer, but I guess whatever works. ...WHY WAS THIS INFORMATION SO DIFFICULT TO FIND?!?!?!?! @____@ Information on Nested Templates in general seems rather difficult to find, however, so I'm glad I figured this out /not ever a full hour/ after writing all this up and posting it. #__#  ...At least my Child-Templates can work thoroughly now, though. So... Scenario FIXED. ^^
I only hope now that such information will appear helpful to anyone else hunting for this information via Google or other Search Engine in the future. And if there is anything at all that I am still officially missing, then do feel free to add it to the feed and let me know, because the last thing I need right now are more surprise difficulties to equally slow down the productivity of this massive project I've been working on... @___@ ..But so far things seem to be going good. ^^ So I can settle myself unbelievably grateful that there ended up being a solution to this ridiculousness after all.
Sincerely,
Miss Cat
[signature promo info removed by moderator]