just doc clean-up

README.md

@@ -4,14 +4,14 @@ Congratulations you've made it to Jon's F5 lab. This lab environment is used dai
 
 All the components of this lab are maintained through GitOps (Argo) and CI with GitHub Actions (Terraform and Ansible). The components are loosely coupled, meaning there is no carryover from one GitHub Action to another, or between Terraform and Ansible. This was done on purpose to be able to consume/copy just the needed components.
 
+[![Lab Pipeline](https://github.com/jmcalalang/lab/actions/workflows/main.yaml/badge.svg?branch=main)](https://github.com/jmcalalang/lab/actions/workflows/main.yaml)
+
 ## Configuration vs Infrastructure
 
-My belief is these managed resources should be split. This aligns nicely with day 0-1, and day 2 operations concepts. As the two resources are used, they are loosely coupled, you may have an infrastructure with different configurations or vice versa. Each product will have a breakdown of the tool used Terraform/Ansible, and then within that folder what the tool is managing configuration or infrastructure.
+My belief is these code-managed resources should be split. This aligns nicely with day 0-1, and day 2 operations concepts. As the two resources are used, they are loosely coupled, you may have an infrastructure with different configurations or vice versa. Each product will have a breakdown of the tool used Terraform/Ansible, and then within that folder what the tool is managing configuration or infrastructure.
 
 Terraform state is setup as remote, with app.terraform.io (Terraform Cloud).
 
-[![Lab Pipeline](https://github.com/jmcalalang/lab/actions/workflows/main.yaml/badge.svg?branch=main)](https://github.com/jmcalalang/lab/actions/workflows/main.yaml)
-
 ## Environment
 
 Environment variables are passed from GitHub repository secrets to actions, keeping secrets out of code.