diff --git a/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md b/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md
index 7d3bdae..048a0e4 100644
--- a/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md
+++ b/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md
@@ -19,7 +19,7 @@ tags:
   - linux
   - chromeos
   - homelab
-  - infrastructure-as-code
+  - iaac
 comment: true # Disable comment if false.
 ---
 I've lately been trying to do more with [Salt](https://saltproject.io/) at work, but I'm still very much a novice with that tool. I thought it would be great to have a nice little portable lab environment where I could deploy a few lightweight VMs and practice managing them with Salt - without impacting any systems that are actually being used for anything. Along the way, I figured I'd leverage [HashiCorp Vagrant](https://www.vagrantup.com/) to create and manage the VMs, which would provide a declarative way to define what the VMs should look like. The VM (or even groups of VMs) would be specified in a single file, and I'd bypass all the tedious steps of creating the virtual hardware, attaching the installation media, installing the OS, and performing the initial configuration. Vagrant will help me build up, destroy, and redeploy a development environment in a simple and repeatable way.
diff --git a/content/posts/k8s-on-vsphere-node-template-with-packer/index.md b/content/posts/k8s-on-vsphere-node-template-with-packer/index.md
index f1e5988..3cca2af 100644
--- a/content/posts/k8s-on-vsphere-node-template-with-packer/index.md
+++ b/content/posts/k8s-on-vsphere-node-template-with-packer/index.md
@@ -22,7 +22,7 @@ tags:
   - automation
   - kubernetes
   - containers
-  - infrastructure-as-code
+  - iaac
   - packer
 comment: true # Disable comment if false.
 ---