Fix image paths

Author: agentlecisco

_posts/articles/2017-09-19-cisco-devnet-pubhub.md

@@ -40,7 +40,7 @@ What did the DevNet team come up with? Let's take a look.
 
 ## What site or sites do you create from a set of Git-based repositories?
 
-The site is [developer.cisco.com](https://developer.cisco.com), and content comes from multiple repository sources, with multiple source types including markdown, RAML, and OpenAPI buit with YAML or JSON.
+The site is [developer.cisco.com](https://developer.cisco.com), and content comes from multiple repository sources, with multiple source types including markdown, RAML, and OpenAPI built with YAML or JSON.
 
 There's also [learninglabs.cisco.com](https://learninglabs.cisco.com), which is also built from repositories containing markdown for content, and JSON files for navigation elements.
 

_posts/articles/2018-06-05-cloudify-dont-stop-dreaming.md

@@ -7,7 +7,7 @@ categories: articles
 author: ben_mansheim
 tags: [cicd, circleci, cloudify, Docker, docs, Hugo, Go]
 image:
-  path: /images/docs-as-code-blog-banner.png
+  path: /images/cloudify/docs-as-code-blog-banner.png
   caption: "[Courtesy Cloudify blog](https://cloudify.co/2018/06/05/docs-as-code-dont-stop-dreaming)"
 comments: false
 share: true
@@ -25,7 +25,7 @@ So this is the story…
 
 The first task I received when I arrived at the company seemed simple. “Our sidebar table of contents (TOC) has a long list of top-level categories that are not well organized and confusing to our customers.” Well, sounds easy enough. To get started, we’ll make a hierarchy that simplifies those categories into 5 groups that basically match 5 types of users. Once we get that quick win we can then look at the content in the categories and combine information in the different topics to condense the content into fewer topics. I figured I could have that done in a week with a lot of buffer. My boss said, “Great!”
 
-[](images/cloudify/old-cloudify-docs.png)
+![Old Cloudify docs](../../images/cloudify/old-cloudify-docs.png)
 
 Now, here are the pitfalls that I met along the way:
 
@@ -45,7 +45,7 @@ After a few weeks of struggling to learn where everything was and getting nowher
 
 Then I looked for a Hugo theme that looked good for documentation and found DocDock. It had a lot of the things that I wanted, including TOC based on directory structure , a main landing page, expanding blocks, single-sourced excerpts, and greatly improved search functionality. When I added the theme to my repo, the site built right away. Great, finally something that worked smoothly! I showed the result to my boss and we agreed that there was a lot of hope here. I told her that I think we could get a fully-functioning POC in a week. Turned out to be a little optimistic.
 
-[](images/cloudify/hugo-docdock.png)
+![Hugo Docdock theme](../../images/cloudify/hugo-docdock.png)
 
 Some of the challenges that I faced were:
 
@@ -69,7 +69,7 @@ Release day arrived. I scheduled it on a Sunday to minimize disruption, of cours
 
 I finally merged the changes from my side-branch into the master branch and things went pretty smoothly. Some tweaks were required but nothing so bad that I needed to rollback again. Unfortunately, a few more days of struggle with redirections of old URLs using AWS S3 only brought frustration. Then, I found that I could add an alias to each page so that Hugo published HTML files at the old URL locations to redirect to the new URLs. I can safely say that was the final step that brought the project to a successful conclusion.
 
-[](images/cloudify/new-cloudify-docs.png)
+![New Cloudify docs](images/cloudify/new-cloudify-docs.png)
 
 ## Success at last!