Update CAM references

assets_site/partials/navigation/submenu-navigation.html

@@ -8,7 +8,7 @@
   <li class="{{#ifpage 'sample-site'}}active{{/ifpage}}"><a href="{{root}}websites/sample-site/">Sample pages</a></li>
   <li class="{{#ifpage 'search-guidelines'}}active{{/ifpage}}"><a href="{{root}}websites/meta-patterns/search-guidelines.html">Search guidelines</a></li>
   <li class="{{#ifpage 'usability'}}active{{/ifpage}}"><a href="{{root}}websites/meta-patterns/usability.html">Usability</a></li>
-  <li class="{{#ifpage 'core-content-spec'}}active{{/ifpage}}"><a href="{{root}}general/core-content-spec">Core content spec</a></li>
+  <li class="{{#ifpage 'core-content-spec'}}active{{/ifpage}}"><a href="{{root}}general/core-content-spec">Content-Action Model</a></li>
 {{/ifequal}}
 {{#ifequal submenu 'general'}}
 <li><a href="writing">Writing</a></li>

content/pages/general/core-content-spec/index.html

@@ -24,7 +24,7 @@ The CAM is a method we utilise to:
 
 ### Where
 
-Use this method on a series of web pages or ecosystem. For example a service might have a few models:
+Use this method on a series of web pages or ecosystem. For example a service might have a few CAM records:
 
 1. The homepage
   - A top layer model about how a user engages into the rest of the site.
@@ -40,7 +40,7 @@ The tool we use to make our Content-Action Models is currently a document templa
 1. Let us guide you
   - If this is your first time using the CAM we can help you understand how best to use it: [khawkins@ebi.ac.uk](mailto:khawkins@ebi.ac.uk) or [www-dev@ebi.ac.uk](mailto:www-dev@ebi.ac.uk)
 2. Use the template
-  - Use the below Google Doc as template and documentation for your Core Content Specifications.
+  - Use the below Google Doc as template and guidance.
 
 <a href="https://docs.google.com/document/d/1N8jU9EiRWHKN6h5PUpFmlWNA_pYN8e-5TAQBuD9UZ2Q/edit?usp=sharing" target="_blank" class="button external">Open the document below in Google Docs</a>
 
@@ -51,11 +51,11 @@ The tool we use to make our Content-Action Models is currently a document templa
 Working with the Web Content Committee, Communications, Training, Web Development and other teams, this model has been evolving since the end of 2016. Here is what we have planned for the next evolution:
 
 1. Visualise the data we've collected.
-  - Core Content Specifications share connections between models. We can use those connections to see a bird's eye view of   pathways between models and see which ecosystems are performing as expected.
+  - CAM records share connections. We can use those connections to see a bird's eye view of pathways between records and see which ecosystems are performing as expected.
 2. Performance measurement
   - By looking at the documented content and associated goals, we can use tools like Google Analytics to measure more than time on page, and begin to measure real success.
 3. A real database tool
-  - Many parts of the Google Doc are a relational database and as such are a poor fit to be done by hand. We could build a better system on the web, once the model has fully stabilised (we should be nearly stable).
+  - Many parts of the Google Doc are a relational database and as such are a poor fit to be done by hand. We could build a better system on the web, once the CAM has fully stabilised (we should be nearly stable).
 
 You can <a class="readmore external" href="https://work.allaboutken.com/posts/20180122-content-action-model.html">learn more about the model and plans in this blog post</a>
 

content/sections/intro.html

@@ -34,7 +34,7 @@ How to write, respond and which icons to use on social media sites.
 <div class="column">
 <a href="{{root}}general/core-content-spec" class="block margin-bottom-large" data-equalizer-watch>
 {{#markdown}}
-#### Core content spec
+#### Content-Action Model
 Maximise the effectivness of your content and see if it's working.
 {{/markdown}}
 </a>