Update content/blog/using-the-hpegl-hpe-greenlake-and-morpheus-terraform-providers-in-concert-to-create-provision-and-manage-hpe-pce-private-cloud-enterprise-vmaas-instances.md

eamonnotoole · liam-m-carolan · web-flow · commit a4fa1f81cf80 · 2025-02-26T17:09:54.000Z
Co-authored-by: liam-m-carolan &lt;140627800+liam-m-carolan@users.noreply.github.com&gt;
diff --git a/content/blog/using-the-hpegl-hpe-greenlake-and-morpheus-terraform-providers-in-concert-to-create-provision-and-manage-hpe-pce-private-cloud-enterprise-vmaas-instances.md b/content/blog/using-the-hpegl-hpe-greenlake-and-morpheus-terraform-providers-in-concert-to-create-provision-and-manage-hpe-pce-private-cloud-enterprise-vmaas-instances.md
@@ -36,7 +36,7 @@ Note that we plan to write and release a new unified provider which will replace
 
 These two current providers (hpegl and Morpheus) complement each other: 
 
-* hpegl deals with HPE GreenLake IAM and manages VMaaS resources, including VM instances 
+* hpegl deals with HPE GreenLake IAM and manages VMaaS resources, including VM instances. 
 * Morpheus deals with underlying Morpheus resources on which the VMaaS resources – including VM instances – depend. This covers resources such as Clouds, VM images, Node Types, Groups, Instance Types, and Instance Layouts. 
 
 The glue between these two providers is a hpegl *data source* called *hpegl_vmaas_morpheus_details*. For a specific VMaaS *location*, this data source will output: 
