From 8743fff510477c10ccb53bf442c97efc16bbeb58 Mon Sep 17 00:00:00 2001
From: hvm-docs-refresh <actions@jpaul.io>
Date: Fri, 22 May 2026 17:39:22 +0000
Subject: [PATCH] =?UTF-8?q?weekly=20refresh:=202026-05-22T17:39Z=20?=
 =?UTF-8?q?=E2=80=94=201161=20content=20change(s)=20across=207=20bundle(s)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

1161 content change(s) across 7 bundle(s)
1161 sidecar metadata update(s)
7 new bundle(s) added

Bundles with content changes:
  hvm_deployment_guide (NEW): 32 page(s)
    - GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA
    - GUID-28F18596-4902-4CD1-83F3-1411430C5534
    - GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259
    - GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C
    - GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB
    ... and 27 more
  hvm_release_notes_8_1_0 (NEW): 1 page(s)
    - sd00007497en_us
  hvm_release_notes_8_1_1 (NEW): 1 page(s)
    - sd00007609en_us
  hvm_release_notes_8_1_2 (NEW): 1 page(s)
    - sd00007734en_us
  hvm_user_manual_8_1_0 (NEW): 374 page(s)
    - GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
    - GUID-02679208-A796-4A58-80AC-33DCF6A4899F
    - GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
    - GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
    - GUID-0503F050-177F-4360-9B1A-49439AF366B8
    ... and 369 more
  hvm_user_manual_8_1_1 (NEW): 376 page(s)
    - GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
    - GUID-02679208-A796-4A58-80AC-33DCF6A4899F
    - GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
    - GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
    - GUID-0503F050-177F-4360-9B1A-49439AF366B8
    ... and 371 more
  hvm_user_manual_8_1_2 (NEW): 376 page(s)
    - GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
    - GUID-02679208-A796-4A58-80AC-33DCF6A4899F
    - GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
    - GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
    - GUID-0503F050-177F-4360-9B1A-49439AF366B8
    ... and 371 more
---
 corpus/.digest/history.jsonl                  |   0
 ...-0F55384D-5632-4CDC-AA39-A21C1C089AFA.json |  11 +
 ...ID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.md |  32 +++
 ...-28F18596-4902-4CD1-83F3-1411430C5534.json |  11 +
 ...ID-28F18596-4902-4CD1-83F3-1411430C5534.md | 125 +++++++++
 ...-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.json |  11 +
 ...ID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.md |  41 +++
 ...-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.json |  11 +
 ...ID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.md |   3 +
 ...-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.json |  11 +
 ...ID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.md |  11 +
 ...-456E190C-E912-4079-A691-8D2368D63748.json |  11 +
 ...ID-456E190C-E912-4079-A691-8D2368D63748.md |  60 ++++
 ...-4767CCB8-A276-45C4-BD8F-4E42865E28C7.json |  11 +
 ...ID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.md |  15 +
 ...-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.json |  11 +
 ...ID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.md |  27 ++
 ...-54192A74-516A-4605-9623-49538D67D590.json |  11 +
 ...ID-54192A74-516A-4605-9623-49538D67D590.md |   7 +
 ...-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.json |  11 +
 ...ID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.md | 100 +++++++
 ...-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.json |  11 +
 ...ID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.md |   5 +
 ...-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.json |  11 +
 ...ID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.md |  11 +
 ...-6EBCB223-4C48-456F-950C-C8ED5610A0F8.json |  11 +
 ...ID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.md |  18 ++
 ...-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.json |  11 +
 ...ID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.md |   9 +
 ...-88494051-74D1-4BD9-BAFF-134A573FF77B.json |  11 +
 ...ID-88494051-74D1-4BD9-BAFF-134A573FF77B.md |   5 +
 ...-8D494112-C361-4300-B7BF-B4DFE06E871C.json |  11 +
 ...ID-8D494112-C361-4300-B7BF-B4DFE06E871C.md |  59 ++++
 ...-94742592-9C85-4F2E-83F2-E68404A73F3B.json |  11 +
 ...ID-94742592-9C85-4F2E-83F2-E68404A73F3B.md |  54 ++++
 ...-97DDED8D-EE6B-4819-8080-E163FD533CAB.json |  11 +
 ...ID-97DDED8D-EE6B-4819-8080-E163FD533CAB.md |  22 ++
 ...-99397996-8315-49C1-9E2F-2EED51CE03F3.json |  11 +
 ...ID-99397996-8315-49C1-9E2F-2EED51CE03F3.md |  59 ++++
 ...-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.json |  11 +
 ...ID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.md |  11 +
 ...-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json |  31 +++
 ...ID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md |  19 ++
 ...-AC33B458-3F39-4BA6-A242-E00B613C60DA.json |  31 +++
 ...ID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md |  17 ++
 ...-ADC37453-056E-43C8-8177-8211A44790FD.json |  11 +
 ...ID-ADC37453-056E-43C8-8177-8211A44790FD.md |  83 ++++++
 ...-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.json |  11 +
 ...ID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.md |   9 +
 ...-BE7493B3-B866-4269-9C13-ABFCF84658F2.json |  11 +
 ...ID-BE7493B3-B866-4269-9C13-ABFCF84658F2.md |  13 +
 ...-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.json |  11 +
 ...ID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.md |  19 ++
 ...-C6EC711D-6F9B-4B71-B209-BA92CD28026B.json |  11 +
 ...ID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.md |   5 +
 ...-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.json |  11 +
 ...ID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.md |  52 ++++
 ...-E3635F0A-11DA-4078-8C3A-8D4B75724849.json |  11 +
 ...ID-E3635F0A-11DA-4078-8C3A-8D4B75724849.md |   5 +
 ...-E49D2EF3-8992-451F-AE3F-55E0380448D2.json |  11 +
 ...ID-E49D2EF3-8992-451F-AE3F-55E0380448D2.md |   5 +
 ...-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.json |  11 +
 ...ID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.md |  52 ++++
 ...-EF5CE241-8260-484D-95C1-6CDEAE24D932.json |  11 +
 ...ID-EF5CE241-8260-484D-95C1-6CDEAE24D932.md |  27 ++
 .../sd00007497en_us.json                      |  26 ++
 .../sd00007497en_us.md                        |  54 ++++
 .../sd00007609en_us.json                      |  26 ++
 .../sd00007609en_us.md                        |  40 +++
 .../sd00007734en_us.json                      |  26 ++
 .../sd00007734en_us.md                        |  52 ++++
 ...-008AF6CD-E219-4D76-B175-B763E5C397CE.json |  26 ++
 ...ID-008AF6CD-E219-4D76-B175-B763E5C397CE.md |  27 ++
 ...-02679208-A796-4A58-80AC-33DCF6A4899F.json |  26 ++
 ...ID-02679208-A796-4A58-80AC-33DCF6A4899F.md |  20 ++
 ...-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json |  26 ++
 ...ID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md |   3 +
 ...-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json |  26 ++
 ...ID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md |   4 +
 ...-0503F050-177F-4360-9B1A-49439AF366B8.json |  26 ++
 ...ID-0503F050-177F-4360-9B1A-49439AF366B8.md |  11 +
 ...-054A7DC4-C03C-4356-8486-19472075129E.json |  26 ++
 ...ID-054A7DC4-C03C-4356-8486-19472075129E.md |  10 +
 ...-06426E05-BE70-4917-89E3-153236303513.json |  26 ++
 ...ID-06426E05-BE70-4917-89E3-153236303513.md |   3 +
 ...-06E4D650-D16A-4E96-98FE-B634E5DEA776.json |  26 ++
 ...ID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md |   3 +
 ...-07778212-ECE2-41DC-A130-1A6271833CA4.json |  26 ++
 ...ID-07778212-ECE2-41DC-A130-1A6271833CA4.md |  80 ++++++
 ...-098F382C-607E-4341-AAE1-7898A7E5D739.json |  26 ++
 ...ID-098F382C-607E-4341-AAE1-7898A7E5D739.md |  33 +++
 ...-09A31CD3-8237-4668-8509-A1C2EA9F3775.json |  26 ++
 ...ID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md |   5 +
 ...-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json |  26 ++
 ...ID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md |  22 ++
 ...-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json |  26 ++
 ...ID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md |   5 +
 ...-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json |  26 ++
 ...ID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md |  11 +
 ...-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json |  26 ++
 ...ID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md |   7 +
 ...-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json |  26 ++
 ...ID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md |   5 +
 ...-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json |  26 ++
 ...ID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md |  77 ++++++
 ...-0DC34FAA-C182-4FAA-BFE3-70147815F471.json |  26 ++
 ...ID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md |  10 +
 ...-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json |  26 ++
 ...ID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md |   5 +
 ...-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json |  26 ++
 ...ID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md |  24 ++
 ...-10A7B17C-6F0D-432A-85BD-3205728606A0.json |  26 ++
 ...ID-10A7B17C-6F0D-432A-85BD-3205728606A0.md |  27 ++
 ...-10D04894-711A-400A-98A7-A3DECE437CDA.json |  26 ++
 ...ID-10D04894-711A-400A-98A7-A3DECE437CDA.md |   7 +
 ...-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json |  26 ++
 ...ID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md |  13 +
 ...-12450828-47CC-4F83-9E94-AF80242C2E3A.json |  26 ++
 ...ID-12450828-47CC-4F83-9E94-AF80242C2E3A.md |  14 +
 ...-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json |  26 ++
 ...ID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md |  19 ++
 ...-1457342F-8258-47AC-AEB3-54E5FE00E434.json |  26 ++
 ...ID-1457342F-8258-47AC-AEB3-54E5FE00E434.md |   3 +
 ...-1569A1AD-385D-4E16-9C85-A1915813FCC8.json |  26 ++
 ...ID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md |   6 +
 ...-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json |  26 ++
 ...ID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md |  25 ++
 ...-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json |  26 ++
 ...ID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md |  19 ++
 ...-17230E5D-DFC2-42A1-900E-1C01A1508954.json |  26 ++
 ...ID-17230E5D-DFC2-42A1-900E-1C01A1508954.md |   7 +
 ...-17B067B3-32C3-4DE7-82DE-B6033C235495.json |  26 ++
 ...ID-17B067B3-32C3-4DE7-82DE-B6033C235495.md |   7 +
 ...-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json |  26 ++
 ...ID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md |   3 +
 ...-187699B7-66AC-465F-BDA4-37F51FB0267B.json |  26 ++
 ...ID-187699B7-66AC-465F-BDA4-37F51FB0267B.md |  11 +
 ...-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json |  26 ++
 ...ID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md |   7 +
 ...-1C1ADB18-710D-40A4-ADCA-660DC7988190.json |  26 ++
 ...ID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md |  25 ++
 ...-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json |  26 ++
 ...ID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md |   3 +
 ...-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json |  26 ++
 ...ID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md |   7 +
 ...-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json |  26 ++
 ...ID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md |  13 +
 ...-1E5AE301-CE00-4509-9820-FB286DDA806A.json |  26 ++
 ...ID-1E5AE301-CE00-4509-9820-FB286DDA806A.md |   5 +
 ...-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json |  26 ++
 ...ID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md |  15 +
 ...-1EB800EB-6832-487E-BB11-07D8520003CF.json |  26 ++
 ...ID-1EB800EB-6832-487E-BB11-07D8520003CF.md |  11 +
 ...-202C8048-0342-4653-97C6-7817B2A9EEB3.json |  26 ++
 ...ID-202C8048-0342-4653-97C6-7817B2A9EEB3.md |   3 +
 ...-20656567-501C-4D21-9EDA-1C6898DF61F5.json |  26 ++
 ...ID-20656567-501C-4D21-9EDA-1C6898DF61F5.md |   9 +
 ...-206AB627-EE3C-4F56-AA25-0DFDECB86281.json |  26 ++
 ...ID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md |  59 ++++
 ...-21972435-BFD0-481F-A3E6-A52B116989F3.json |  26 ++
 ...ID-21972435-BFD0-481F-A3E6-A52B116989F3.md |  52 ++++
 ...-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json |  26 ++
 ...ID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md |  21 ++
 ...-226C1DD5-E007-4F44-A215-2FC03C269EA5.json |  26 ++
 ...ID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md |   8 +
 ...-238F9226-4EB4-4E14-B533-584277951C4B.json |  26 ++
 ...ID-238F9226-4EB4-4E14-B533-584277951C4B.md |   3 +
 ...-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json |  26 ++
 ...ID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md |   7 +
 ...-2581C2D1-AC07-4DE2-B794-20AC25652417.json |  26 ++
 ...ID-2581C2D1-AC07-4DE2-B794-20AC25652417.md |   3 +
 ...-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json |  26 ++
 ...ID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md |  15 +
 ...-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json |  26 ++
 ...ID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md |   5 +
 ...-2686BF33-E793-4BF9-98BE-82F800ED03EB.json |  26 ++
 ...ID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md |  17 ++
 ...-26D622EF-A71E-44D7-A705-176ED6445B3D.json |  26 ++
 ...ID-26D622EF-A71E-44D7-A705-176ED6445B3D.md |  16 ++
 ...-27619E64-03DD-4F3B-B66A-9C2D5350466E.json |  26 ++
 ...ID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md |   7 +
 ...-278B93C4-6B70-476F-B530-A2DBA4269FD8.json |  26 ++
 ...ID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md |   7 +
 ...-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json |  26 ++
 ...ID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md |  14 +
 ...-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json |  26 ++
 ...ID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md |   7 +
 ...-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json |  26 ++
 ...ID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md |   3 +
 ...-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json |  26 ++
 ...ID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md |   3 +
 ...-2D035C3B-0102-4FB3-BE34-74094659DC87.json |  26 ++
 ...ID-2D035C3B-0102-4FB3-BE34-74094659DC87.md |  11 +
 ...-2DEB33CC-132A-494C-B242-CA09B02E9333.json |  26 ++
 ...ID-2DEB33CC-132A-494C-B242-CA09B02E9333.md |   5 +
 ...-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json |  26 ++
 ...ID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md |  51 ++++
 ...-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json |  26 ++
 ...ID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md |   3 +
 ...-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json |  26 ++
 ...ID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md |   6 +
 ...-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json |  26 ++
 ...ID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md |  17 ++
 ...-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json |  26 ++
 ...ID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md |  12 +
 ...-30353E6D-5FA2-470C-BB80-238663945F6F.json |  26 ++
 ...ID-30353E6D-5FA2-470C-BB80-238663945F6F.md |   3 +
 ...-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json |  26 ++
 ...ID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md |   3 +
 ...-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json |  26 ++
 ...ID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md |  25 ++
 ...-30D9F5F5-7572-4440-8B31-9372D7CE352D.json |  26 ++
 ...ID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md |   8 +
 ...-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json |  26 ++
 ...ID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md |   3 +
 ...-334FA46B-AE38-41A7-BACC-8F8384C5D010.json |  26 ++
 ...ID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md |   6 +
 ...-33F3509A-A175-4204-A1A8-F3699338CAC5.json |  26 ++
 ...ID-33F3509A-A175-4204-A1A8-F3699338CAC5.md |  96 +++++++
 ...-34291BF2-6D39-46FD-B18A-338089CAF11E.json |  26 ++
 ...ID-34291BF2-6D39-46FD-B18A-338089CAF11E.md |   3 +
 ...-34B1DB42-8ADD-45C4-B945-137EB77810B6.json |  26 ++
 ...ID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md |  38 +++
 ...-35419962-0058-4856-A6BD-F4923FD0F044.json |  26 ++
 ...ID-35419962-0058-4856-A6BD-F4923FD0F044.md |   3 +
 ...-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json |  26 ++
 ...ID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md |  74 +++++
 ...-3702D75B-9505-40D0-B220-7739F5F72760.json |  26 ++
 ...ID-3702D75B-9505-40D0-B220-7739F5F72760.md |  47 ++++
 ...-371A58A1-F821-449C-8D2D-EC2657C13B56.json |  26 ++
 ...ID-371A58A1-F821-449C-8D2D-EC2657C13B56.md |   9 +
 ...-37CA1665-B331-452A-AA3D-59608D85F006.json |  26 ++
 ...ID-37CA1665-B331-452A-AA3D-59608D85F006.md |   1 +
 ...-392743FA-D99D-4995-A8F6-3E5541271263.json |  26 ++
 ...ID-392743FA-D99D-4995-A8F6-3E5541271263.md |  21 ++
 ...-397630C5-C2CE-4E35-A45D-0228C8F70867.json |  26 ++
 ...ID-397630C5-C2CE-4E35-A45D-0228C8F70867.md |  10 +
 ...-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json |  26 ++
 ...ID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md |   9 +
 ...-3A5066B9-898A-4673-A713-C3E41D502742.json |  26 ++
 ...ID-3A5066B9-898A-4673-A713-C3E41D502742.md |  11 +
 ...-3A5117DE-E11D-41D0-A016-A68154A90DCA.json |  26 ++
 ...ID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md |   9 +
 ...-3A627DBF-D797-42A2-A9AC-AAC321376068.json |  26 ++
 ...ID-3A627DBF-D797-42A2-A9AC-AAC321376068.md |  25 ++
 ...-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json |  26 ++
 ...ID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md |   3 +
 ...-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json |  26 ++
 ...ID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md |  36 +++
 ...-3B34F036-4C25-4058-B5F4-5340545BE821.json |  26 ++
 ...ID-3B34F036-4C25-4058-B5F4-5340545BE821.md |   9 +
 ...-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json |  26 ++
 ...ID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md |  20 ++
 ...-3D27BE17-47C9-476C-AD13-DD516697F862.json |  26 ++
 ...ID-3D27BE17-47C9-476C-AD13-DD516697F862.md |  12 +
 ...-3E03B539-B71C-4D2E-A218-23713D723408.json |  26 ++
 ...ID-3E03B539-B71C-4D2E-A218-23713D723408.md |   5 +
 ...-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json |  26 ++
 ...ID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md |  30 ++
 ...-40300B80-D69C-450B-9848-7A21A3141005.json |  26 ++
 ...ID-40300B80-D69C-450B-9848-7A21A3141005.md |  12 +
 ...-429877DA-255E-41FC-86B6-E7069B0EE7A6.json |  26 ++
 ...ID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md |  63 +++++
 ...-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json |  26 ++
 ...ID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md |   7 +
 ...-443DD312-C75F-4267-A17E-FEDCFD7335FB.json |  26 ++
 ...ID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md |   6 +
 ...-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json |  26 ++
 ...ID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md |   9 +
 ...-44974486-3ED4-4C5C-849B-8746A4899889.json |  26 ++
 ...ID-44974486-3ED4-4C5C-849B-8746A4899889.md |   9 +
 ...-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json |  26 ++
 ...ID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md |  10 +
 ...-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json |  26 ++
 ...ID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md |   9 +
 ...-45B4119E-416A-43FA-B2A0-C7D52D028326.json |  26 ++
 ...ID-45B4119E-416A-43FA-B2A0-C7D52D028326.md |  15 +
 ...-45D07344-870A-4CB7-84D9-4AF78C151B70.json |  26 ++
 ...ID-45D07344-870A-4CB7-84D9-4AF78C151B70.md |  21 ++
 ...-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json |  26 ++
 ...ID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md |   5 +
 ...-46D03C40-2146-434A-B75A-12BBBDB56FF3.json |  26 ++
 ...ID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md |  31 +++
 ...-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json |  26 ++
 ...ID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md |  23 ++
 ...-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json |  26 ++
 ...ID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md |  12 +
 ...-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json |  26 ++
 ...ID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md |  34 +++
 ...-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json |  26 ++
 ...ID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md |   5 +
 ...-4AE72311-7C7E-4384-A7E1-A23048B29C40.json |  26 ++
 ...ID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md |   3 +
 ...-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json |  26 ++
 ...ID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md |  12 +
 ...-4CCF6004-31A7-4B35-996D-5E12877CB443.json |  26 ++
 ...ID-4CCF6004-31A7-4B35-996D-5E12877CB443.md |   3 +
 ...-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json |  26 ++
 ...ID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md |   7 +
 ...-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json |  26 ++
 ...ID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md |  11 +
 ...-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json |  26 ++
 ...ID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md |   3 +
 ...-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json |  26 ++
 ...ID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md |  19 ++
 ...-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json |  26 ++
 ...ID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md |  16 ++
 ...-4F822F1E-105F-48CD-83A7-3BB562A5B147.json |  26 ++
 ...ID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md |   3 +
 ...-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json |  26 ++
 ...ID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md |   4 +
 ...-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json |  26 ++
 ...ID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md |  10 +
 ...-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json |  26 ++
 ...ID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md |  13 +
 ...-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json |  26 ++
 ...ID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md |  43 +++
 ...-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json |  26 ++
 ...ID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md |   5 +
 ...-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json |  26 ++
 ...ID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md |  42 +++
 ...-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json |  26 ++
 ...ID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md |   8 +
 ...-5504862E-8120-469D-8708-2290772E5585.json |  26 ++
 ...ID-5504862E-8120-469D-8708-2290772E5585.md |  13 +
 ...-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json |  26 ++
 ...ID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md |  80 ++++++
 ...-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json |  26 ++
 ...ID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md |   5 +
 ...-5571B267-5385-4EEC-A400-FD23FD4B239C.json |  26 ++
 ...ID-5571B267-5385-4EEC-A400-FD23FD4B239C.md |   3 +
 ...-55BA17AE-7F27-4832-BADC-D76B073635C6.json |  26 ++
 ...ID-55BA17AE-7F27-4832-BADC-D76B073635C6.md |   4 +
 ...-55E760C3-2167-4A03-88ED-D9078C196D74.json |  26 ++
 ...ID-55E760C3-2167-4A03-88ED-D9078C196D74.md |   8 +
 ...-5663C34A-23E8-42CA-B7BF-5A79A0070456.json |  26 ++
 ...ID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md |   7 +
 ...-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json |  26 ++
 ...ID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md |   8 +
 ...-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json |  26 ++
 ...ID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md |  13 +
 ...-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json |  26 ++
 ...ID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md |   8 +
 ...-580E4107-827A-43F6-888D-5CDD41EB42E0.json |  26 ++
 ...ID-580E4107-827A-43F6-888D-5CDD41EB42E0.md |  25 ++
 ...-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json |  26 ++
 ...ID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md |  23 ++
 ...-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json |  26 ++
 ...ID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md |   8 +
 ...-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json |  26 ++
 ...ID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md |   7 +
 ...-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json |  26 ++
 ...ID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md |  53 ++++
 ...-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json |  26 ++
 ...ID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md |   3 +
 ...-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json |  26 ++
 ...ID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md |  20 ++
 ...-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json |  26 ++
 ...ID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md |  13 +
 ...-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json |  26 ++
 ...ID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md |   7 +
 ...-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json |  26 ++
 ...ID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md |  11 +
 ...-5E442E1F-D996-4863-BA47-1EE76E07A12C.json |  26 ++
 ...ID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md |  29 ++
 ...-5F75E5AF-90D3-4F85-B937-F98415300AC5.json |  26 ++
 ...ID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md |  20 ++
 ...-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json |  26 ++
 ...ID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md |   3 +
 ...-61053EC5-4910-454F-8B71-6B06408A6451.json |  26 ++
 ...ID-61053EC5-4910-454F-8B71-6B06408A6451.md |   8 +
 ...-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json |  26 ++
 ...ID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md |  49 ++++
 ...-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json |  26 ++
 ...ID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md |   3 +
 ...-62D603EE-56F3-478D-9625-2FC3B6F189E8.json |  26 ++
 ...ID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md |  25 ++
 ...-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json |  26 ++
 ...ID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md |  23 ++
 ...-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json |  26 ++
 ...ID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md |   9 +
 ...-634760AA-7E46-42A7-AD08-85CCE4656873.json |  26 ++
 ...ID-634760AA-7E46-42A7-AD08-85CCE4656873.md |  36 +++
 ...-63ADF495-37BF-424E-85F4-614EE91DA301.json |  26 ++
 ...ID-63ADF495-37BF-424E-85F4-614EE91DA301.md |  12 +
 ...-63B0F6F4-69CA-40C1-997E-949DD702C77E.json |  26 ++
 ...ID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md |   3 +
 ...-64001B38-0509-46D5-854E-3A8500798DEE.json |  26 ++
 ...ID-64001B38-0509-46D5-854E-3A8500798DEE.md |  13 +
 ...-650706CA-915E-4239-9D69-35902E82B60E.json |  26 ++
 ...ID-650706CA-915E-4239-9D69-35902E82B60E.md |   9 +
 ...-6549D43B-D0BB-4416-9771-AF11F387B629.json |  26 ++
 ...ID-6549D43B-D0BB-4416-9771-AF11F387B629.md |   7 +
 ...-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json |  26 ++
 ...ID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md |  14 +
 ...-69626666-7280-4AF5-9871-FA2D82CED05E.json |  26 ++
 ...ID-69626666-7280-4AF5-9871-FA2D82CED05E.md |  20 ++
 ...-69CE737F-F442-4C04-8B1A-8881930B69AE.json |  26 ++
 ...ID-69CE737F-F442-4C04-8B1A-8881930B69AE.md |  17 ++
 ...-6B35AE72-3D19-447A-A19D-D96DDD769B67.json |  26 ++
 ...ID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md |  84 ++++++
 ...-6B80D87B-8461-414D-9172-07E68896EB06.json |  26 ++
 ...ID-6B80D87B-8461-414D-9172-07E68896EB06.md |  20 ++
 ...-6B9A77F8-731B-43A1-92C8-0163E20D8048.json |  26 ++
 ...ID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md |  28 ++
 ...-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json |  26 ++
 ...ID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md |   3 +
 ...-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json |  26 ++
 ...ID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md |  25 ++
 ...-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json |  26 ++
 ...ID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md |  18 ++
 ...-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json |  26 ++
 ...ID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md |  11 +
 ...-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json |  26 ++
 ...ID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md |  12 +
 ...-712F2BB4-F856-419F-BB88-2E137DD46F72.json |  26 ++
 ...ID-712F2BB4-F856-419F-BB88-2E137DD46F72.md |  11 +
 ...-7138E486-AE62-4778-9358-F098126785A5.json |  26 ++
 ...ID-7138E486-AE62-4778-9358-F098126785A5.md |   5 +
 ...-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json |  26 ++
 ...ID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md |  20 ++
 ...-74590319-12A6-4101-9043-8DDB56BB0720.json |  26 ++
 ...ID-74590319-12A6-4101-9043-8DDB56BB0720.md |  18 ++
 ...-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json |  26 ++
 ...ID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md |  13 +
 ...-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json |  26 ++
 ...ID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md |   6 +
 ...-76B17464-6C1D-468E-B6D2-93ECF87E2289.json |  26 ++
 ...ID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md |  18 ++
 ...-76B546AD-121A-4C3A-B42C-D642C8624A3C.json |  26 ++
 ...ID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md |   7 +
 ...-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json |  26 ++
 ...ID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md |   8 +
 ...-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json |  26 ++
 ...ID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md |  14 +
 ...-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json |  26 ++
 ...ID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md |  22 ++
 ...-7C6154EA-09BC-4E68-8BAB-D784F0582440.json |  26 ++
 ...ID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md |   7 +
 ...-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json |  26 ++
 ...ID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md |  42 +++
 ...-7D80BD98-F855-4690-AC44-6BA192EC1E53.json |  26 ++
 ...ID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md |  13 +
 ...-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json |  26 ++
 ...ID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md |   9 +
 ...-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json |  26 ++
 ...ID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md |  13 +
 ...-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json |  26 ++
 ...ID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md |   3 +
 ...-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json |  26 ++
 ...ID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md |  12 +
 ...-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json |  26 ++
 ...ID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md |  28 ++
 ...-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json |  26 ++
 ...ID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md |   9 +
 ...-83AF39C3-5542-4739-B9ED-C867C472CDCE.json |  26 ++
 ...ID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md |  11 +
 ...-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json |  26 ++
 ...ID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md |  10 +
 ...-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json |  26 ++
 ...ID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md |  15 +
 ...-87FC621D-8EDE-48DE-901B-00058C07E62D.json |  26 ++
 ...ID-87FC621D-8EDE-48DE-901B-00058C07E62D.md |  27 ++
 ...-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json |  26 ++
 ...ID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md |   5 +
 ...-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json |  26 ++
 ...ID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md |  29 ++
 ...-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json |  26 ++
 ...ID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md |  81 ++++++
 ...-8AFBB53F-6749-4E7E-AAF2-310849586320.json |  26 ++
 ...ID-8AFBB53F-6749-4E7E-AAF2-310849586320.md |   7 +
 ...-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json |  26 ++
 ...ID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md |   3 +
 ...-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json |  26 ++
 ...ID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md |  44 +++
 ...-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json |  26 ++
 ...ID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md |  12 +
 ...-8E19FA4E-4408-4784-A629-DD936DEEBA26.json |  26 ++
 ...ID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md |   3 +
 ...-8EC2E33D-2086-4253-BF7D-D953052774A0.json |  26 ++
 ...ID-8EC2E33D-2086-4253-BF7D-D953052774A0.md |   7 +
 ...-91D3F799-4C17-4008-B605-FEE370890091.json |  26 ++
 ...ID-91D3F799-4C17-4008-B605-FEE370890091.md |   3 +
 ...-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json |  26 ++
 ...ID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md |  20 ++
 ...-94133965-3802-4768-A71D-2AD5F8402BD9.json |  26 ++
 ...ID-94133965-3802-4768-A71D-2AD5F8402BD9.md |  13 +
 ...-949DC89F-26C2-4028-9A1F-2616FB466736.json |  26 ++
 ...ID-949DC89F-26C2-4028-9A1F-2616FB466736.md |  13 +
 ...-953F9E2E-D9DD-4469-96EE-A288371FE36E.json |  26 ++
 ...ID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md |  82 ++++++
 ...-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json |  26 ++
 ...ID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md |   7 +
 ...-960DA835-B984-49FB-80DE-EE6D38D42EDD.json |  26 ++
 ...ID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md |  13 +
 ...-967D7E5A-D701-4580-BFCB-0EB3588D2725.json |  26 ++
 ...ID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md |   3 +
 ...-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json |  26 ++
 ...ID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md |  13 +
 ...-97951AE9-439B-4779-823D-E118E1CB08D3.json |  26 ++
 ...ID-97951AE9-439B-4779-823D-E118E1CB08D3.md |   9 +
 ...-9886AD4A-5C64-4E09-A106-B14419362757.json |  26 ++
 ...ID-9886AD4A-5C64-4E09-A106-B14419362757.md |  21 ++
 ...-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json |  26 ++
 ...ID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md |   5 +
 ...-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json |  26 ++
 ...ID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md |  17 ++
 ...-9969BD6B-639D-4633-B825-79578464E8E6.json |  26 ++
 ...ID-9969BD6B-639D-4633-B825-79578464E8E6.md |   8 +
 ...-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json |  26 ++
 ...ID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md |  11 +
 ...-9AA16B50-F8A4-443B-AD6C-6E018596459B.json |  26 ++
 ...ID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md |   5 +
 ...-9BDE2563-18FC-49B0-83D7-47F57E044D97.json |  26 ++
 ...ID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md |   7 +
 ...-9C1E97D3-4285-4F70-ACAF-A56767901C74.json |  26 ++
 ...ID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md |  15 +
 ...-9CB7CEE4-C724-448E-822A-75F155B88EAC.json |  26 ++
 ...ID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md |  11 +
 ...-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json |  26 ++
 ...ID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md |   6 +
 ...-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json |  26 ++
 ...ID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md |   8 +
 ...-9DA38943-BF95-446D-AB09-32323160D51B.json |  26 ++
 ...ID-9DA38943-BF95-446D-AB09-32323160D51B.md |  53 ++++
 ...-9DA820B7-7477-4980-848B-7161BDB5C43E.json |  26 ++
 ...ID-9DA820B7-7477-4980-848B-7161BDB5C43E.md |   9 +
 ...-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json |  26 ++
 ...ID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md |   4 +
 ...-9EC70919-852C-427E-ACDF-D59319D72468.json |  26 ++
 ...ID-9EC70919-852C-427E-ACDF-D59319D72468.md |  23 ++
 ...-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json |  26 ++
 ...ID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md |   6 +
 ...-9FC58214-95C7-4690-91DA-3185640E3712.json |  26 ++
 ...ID-9FC58214-95C7-4690-91DA-3185640E3712.md |   7 +
 ...-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json |  26 ++
 ...ID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md |  26 ++
 ...-9FF6393B-3B5D-4409-B0BC-461062C5F766.json |  26 ++
 ...ID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md |   3 +
 ...-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json |  26 ++
 ...ID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md |  35 +++
 ...-A1E79BA5-CE31-4357-878E-11464E03158C.json |  26 ++
 ...ID-A1E79BA5-CE31-4357-878E-11464E03158C.md |   6 +
 ...-A2A63203-21AB-4358-8706-62DF795EAE62.json |  26 ++
 ...ID-A2A63203-21AB-4358-8706-62DF795EAE62.md |  10 +
 ...-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json |  26 ++
 ...ID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md |   3 +
 ...-A391DC49-6523-4517-9AE1-F2E78CE91411.json |  26 ++
 ...ID-A391DC49-6523-4517-9AE1-F2E78CE91411.md |  11 +
 ...-A3EE4127-5F12-4F3A-89EA-138882DA237B.json |  26 ++
 ...ID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md |   9 +
 ...-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json |  26 ++
 ...ID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md |  12 +
 ...-A5F5433C-0F21-4877-BFC6-522D421A1842.json |  26 ++
 ...ID-A5F5433C-0F21-4877-BFC6-522D421A1842.md |   3 +
 ...-A742B359-6C9C-4BC0-AA52-30189D93AA33.json |  26 ++
 ...ID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md |   7 +
 ...-A745B955-2E59-4769-AB47-E32098A84653.json |  26 ++
 ...ID-A745B955-2E59-4769-AB47-E32098A84653.md |   7 +
 ...-A7CB5566-0283-4C67-BA27-02852732D7C3.json |  26 ++
 ...ID-A7CB5566-0283-4C67-BA27-02852732D7C3.md |  69 +++++
 ...-AAD13737-533B-491F-A155-DDB027057157.json |  26 ++
 ...ID-AAD13737-533B-491F-A155-DDB027057157.md |  14 +
 ...-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json |  31 +++
 ...ID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md |  19 ++
 ...-AB938CF2-D0FE-4516-931D-0238D0662B84.json |  26 ++
 ...ID-AB938CF2-D0FE-4516-931D-0238D0662B84.md |   8 +
 ...-AC33B458-3F39-4BA6-A242-E00B613C60DA.json |  31 +++
 ...ID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md |  17 ++
 ...-AC461BBD-647D-447D-9307-218A41CE368B.json |  26 ++
 ...ID-AC461BBD-647D-447D-9307-218A41CE368B.md |  11 +
 ...-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json |  26 ++
 ...ID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md |   7 +
 ...-ADF74748-AB0E-42F4-BB23-79C5B079A778.json |  26 ++
 ...ID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md |  77 ++++++
 ...-AE27985B-5909-407F-A105-5B0574715D13.json |  26 ++
 ...ID-AE27985B-5909-407F-A105-5B0574715D13.md |   7 +
 ...-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json |  26 ++
 ...ID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md |  38 +++
 ...-AFF4C609-07DB-429C-B7A7-82F9568D6297.json |  26 ++
 ...ID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md |   3 +
 ...-B3241978-4E00-4630-A8AB-E597193E51E2.json |  26 ++
 ...ID-B3241978-4E00-4630-A8AB-E597193E51E2.md |  38 +++
 ...-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json |  26 ++
 ...ID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md |   5 +
 ...-B5387FE3-B36D-4924-B168-329B6E41D811.json |  26 ++
 ...ID-B5387FE3-B36D-4924-B168-329B6E41D811.md |   3 +
 ...-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json |  26 ++
 ...ID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md |  18 ++
 ...-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json |  26 ++
 ...ID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md |   7 +
 ...-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json |  26 ++
 ...ID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md |  14 +
 ...-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json |  26 ++
 ...ID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md |   9 +
 ...-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json |  26 ++
 ...ID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md |  23 ++
 ...-B6F5194C-290E-464F-A718-232984A6E8B5.json |  26 ++
 ...ID-B6F5194C-290E-464F-A718-232984A6E8B5.md |   6 +
 ...-B82658C8-6002-424B-B257-D52A7D603BC3.json |  26 ++
 ...ID-B82658C8-6002-424B-B257-D52A7D603BC3.md |   7 +
 ...-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json |  26 ++
 ...ID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md |   9 +
 ...-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json |  26 ++
 ...ID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md |  10 +
 ...-B8FB507C-D7BB-462A-847F-E5A4B708E142.json |  26 ++
 ...ID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md |   4 +
 ...-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json |  26 ++
 ...ID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md |   1 +
 ...-B94BC2CB-8504-41C6-8848-512529EEE941.json |  26 ++
 ...ID-B94BC2CB-8504-41C6-8848-512529EEE941.md |   4 +
 ...-BB270862-D56D-4B6F-86B7-030ED273E907.json |  26 ++
 ...ID-BB270862-D56D-4B6F-86B7-030ED273E907.md |   3 +
 ...-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json |  26 ++
 ...ID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md | 256 ++++++++++++++++++
 ...-BC17942D-DE0B-4244-900F-DE38D31A09EC.json |  26 ++
 ...ID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md |   6 +
 ...-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json |  26 ++
 ...ID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md |  17 ++
 ...-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json |  26 ++
 ...ID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md |  15 +
 ...-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json |  26 ++
 ...ID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md |  52 ++++
 ...-BD0C3274-B70C-437A-B89C-C77A703FFD53.json |  26 ++
 ...ID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md |  28 ++
 ...-BE852729-65DF-4377-9A64-F05D47CD9D49.json |  26 ++
 ...ID-BE852729-65DF-4377-9A64-F05D47CD9D49.md |  25 ++
 ...-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json |  26 ++
 ...ID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md |  13 +
 ...-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json |  26 ++
 ...ID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md |  10 +
 ...-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json |  26 ++
 ...ID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md |  53 ++++
 ...-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json |  26 ++
 ...ID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md |   6 +
 ...-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json |  26 ++
 ...ID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md |  12 +
 ...-C7399A7B-40C6-4DCA-8A92-EAB777739496.json |  26 ++
 ...ID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md |  25 ++
 ...-C7747582-1A56-458D-B985-DDF459F1CE7C.json |  26 ++
 ...ID-C7747582-1A56-458D-B985-DDF459F1CE7C.md |  73 +++++
 ...-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json |  26 ++
 ...ID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md |   9 +
 ...-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json |  26 ++
 ...ID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md |   4 +
 ...-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json |  26 ++
 ...ID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md |  10 +
 ...-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json |  26 ++
 ...ID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md |   5 +
 ...-CA181AC5-CA1D-47ED-9D44-008642C89290.json |  26 ++
 ...ID-CA181AC5-CA1D-47ED-9D44-008642C89290.md |  97 +++++++
 ...-CA806876-1093-4A39-BE62-439C4802A915.json |  26 ++
 ...ID-CA806876-1093-4A39-BE62-439C4802A915.md |  17 ++
 ...-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json |  26 ++
 ...ID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md |   3 +
 ...-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json |  26 ++
 ...ID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md |   7 +
 ...-CD00669C-741C-480C-B444-67F079061438.json |  26 ++
 ...ID-CD00669C-741C-480C-B444-67F079061438.md |  11 +
 ...-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json |  26 ++
 ...ID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md |   8 +
 ...-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json |  26 ++
 ...ID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md |  76 ++++++
 ...-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json |  26 ++
 ...ID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md |  24 ++
 ...-CDB73B95-18B8-4A10-A09C-4176EE11497D.json |  26 ++
 ...ID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md |  15 +
 ...-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json |  26 ++
 ...ID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md |  11 +
 ...-CFE82665-23A3-49F2-9202-1C2A720CC64D.json |  26 ++
 ...ID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md |  12 +
 ...-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json |  26 ++
 ...ID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md |  26 ++
 ...-D280323C-DF16-4F69-86CA-111B7CFCA25E.json |  26 ++
 ...ID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md |  21 ++
 ...-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json |  26 ++
 ...ID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md | 106 ++++++++
 ...-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json |  26 ++
 ...ID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md |  15 +
 ...-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json |  26 ++
 ...ID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md |  59 ++++
 ...-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json |  26 ++
 ...ID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md |   9 +
 ...-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json |  26 ++
 ...ID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md |  11 +
 ...-D647F00D-6B45-4E18-B442-14835847EFA7.json |  26 ++
 ...ID-D647F00D-6B45-4E18-B442-14835847EFA7.md |  23 ++
 ...-D6B5BF84-8D86-4215-94FF-119D52387FDB.json |  26 ++
 ...ID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md |  14 +
 ...-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json |  26 ++
 ...ID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md |   5 +
 ...-D7A36529-C624-486D-8C0E-FA69A4DC4014.json |  26 ++
 ...ID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md |   5 +
 ...-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json |  26 ++
 ...ID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md |   5 +
 ...-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json |  26 ++
 ...ID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md |   8 +
 ...-DA1898BD-3EB1-432A-BD34-373B29B05B89.json |  26 ++
 ...ID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md |   6 +
 ...-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json |  26 ++
 ...ID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md |   3 +
 ...-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json |  26 ++
 ...ID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md |  23 ++
 ...-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json |  26 ++
 ...ID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md |   3 +
 ...-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json |  26 ++
 ...ID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md |  13 +
 ...-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json |  26 ++
 ...ID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md |  23 ++
 ...-DF02CF23-8387-4D00-87AF-5F2054075F18.json |  26 ++
 ...ID-DF02CF23-8387-4D00-87AF-5F2054075F18.md |  11 +
 ...-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json |  26 ++
 ...ID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md |  11 +
 ...-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json |  26 ++
 ...ID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md |  28 ++
 ...-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json |  26 ++
 ...ID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md |  16 ++
 ...-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json |  26 ++
 ...ID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md |  17 ++
 ...-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json |  26 ++
 ...ID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md |  15 +
 ...-E04CE9DF-E832-41CB-B559-1800B7943A2F.json |  26 ++
 ...ID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md |  20 ++
 ...-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json |  26 ++
 ...ID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md |  64 +++++
 ...-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json |  26 ++
 ...ID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md |   5 +
 ...-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json |  26 ++
 ...ID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md |  31 +++
 ...-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json |  26 ++
 ...ID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md |  77 ++++++
 ...-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json |  26 ++
 ...ID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md |   3 +
 ...-E32D92B2-8DB3-42C3-982C-7E9D88231069.json |  26 ++
 ...ID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md |  19 ++
 ...-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json |  26 ++
 ...ID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md |  15 +
 ...-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json |  26 ++
 ...ID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md |   6 +
 ...-E4F3DF9C-1873-4893-BE81-D85015D67F19.json |  26 ++
 ...ID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md |   7 +
 ...-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json |  26 ++
 ...ID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md |  18 ++
 ...-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json |  26 ++
 ...ID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md |  48 ++++
 ...-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json |  26 ++
 ...ID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md |   7 +
 ...-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json |  26 ++
 ...ID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md |  11 +
 ...-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json |  26 ++
 ...ID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md |   7 +
 ...-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json |  26 ++
 ...ID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md |   3 +
 ...-EB317455-AAFD-4465-8961-6E7C13B48CCB.json |  26 ++
 ...ID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md |  26 ++
 ...-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json |  26 ++
 ...ID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md |  13 +
 ...-EC91E230-8323-4710-9A47-D57A15BE71AA.json |  26 ++
 ...ID-EC91E230-8323-4710-9A47-D57A15BE71AA.md |   8 +
 ...-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json |  26 ++
 ...ID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md | 109 ++++++++
 ...-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json |  26 ++
 ...ID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md |  11 +
 ...-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json |  26 ++
 ...ID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md |   8 +
 ...-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json |  26 ++
 ...ID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md |  24 ++
 ...-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json |  26 ++
 ...ID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md |  31 +++
 ...-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json |  26 ++
 ...ID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md |  13 +
 ...-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json |  26 ++
 ...ID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md |   3 +
 ...-F25A1489-CFA2-4B4A-9340-1C278198A951.json |  26 ++
 ...ID-F25A1489-CFA2-4B4A-9340-1C278198A951.md |   8 +
 ...-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json |  26 ++
 ...ID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md |  29 ++
 ...-F3650ED7-96D8-4542-8D04-ED3527A9C565.json |  26 ++
 ...ID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md |   7 +
 ...-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json |  26 ++
 ...ID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md |  14 +
 ...-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json |  26 ++
 ...ID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md |  18 ++
 ...-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json |  26 ++
 ...ID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md |  18 ++
 ...-F5A818DC-E3A9-4020-84FC-B087B2C14158.json |  26 ++
 ...ID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md |  29 ++
 ...-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json |  26 ++
 ...ID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md |   6 +
 ...-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json |  26 ++
 ...ID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md | 108 ++++++++
 ...-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json |  26 ++
 ...ID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md |  14 +
 ...-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json |  26 ++
 ...ID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md |   8 +
 ...-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json |  26 ++
 ...ID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md |  12 +
 ...-FA7264AB-8547-45E3-8752-8D47B6708F86.json |  26 ++
 ...ID-FA7264AB-8547-45E3-8752-8D47B6708F86.md |  20 ++
 ...-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json |  26 ++
 ...ID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md |  11 +
 ...-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json |  26 ++
 ...ID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md |  21 ++
 ...-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json |  26 ++
 ...ID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md |  14 +
 ...-FB7D15CC-A606-42DC-9DBF-27778D20282D.json |  26 ++
 ...ID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md |  43 +++
 ...-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json |  26 ++
 ...ID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md |  94 +++++++
 ...-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json |  26 ++
 ...ID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md |   3 +
 ...-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json |  26 ++
 ...ID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md |   8 +
 ...-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json |  26 ++
 ...ID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md |   3 +
 ...-FDC357F5-AFCA-4175-ADF4-43928922C384.json |  26 ++
 ...ID-FDC357F5-AFCA-4175-ADF4-43928922C384.md |  13 +
 ...-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json |  26 ++
 ...ID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md |  13 +
 ...-008AF6CD-E219-4D76-B175-B763E5C397CE.json |  26 ++
 ...ID-008AF6CD-E219-4D76-B175-B763E5C397CE.md |  27 ++
 ...-02679208-A796-4A58-80AC-33DCF6A4899F.json |  26 ++
 ...ID-02679208-A796-4A58-80AC-33DCF6A4899F.md |  20 ++
 ...-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json |  26 ++
 ...ID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md |   3 +
 ...-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json |  26 ++
 ...ID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md |   4 +
 ...-0503F050-177F-4360-9B1A-49439AF366B8.json |  26 ++
 ...ID-0503F050-177F-4360-9B1A-49439AF366B8.md |  11 +
 ...-054A7DC4-C03C-4356-8486-19472075129E.json |  26 ++
 ...ID-054A7DC4-C03C-4356-8486-19472075129E.md |  10 +
 ...-06426E05-BE70-4917-89E3-153236303513.json |  26 ++
 ...ID-06426E05-BE70-4917-89E3-153236303513.md |   3 +
 ...-06E4D650-D16A-4E96-98FE-B634E5DEA776.json |  26 ++
 ...ID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md |   3 +
 ...-07778212-ECE2-41DC-A130-1A6271833CA4.json |  26 ++
 ...ID-07778212-ECE2-41DC-A130-1A6271833CA4.md |  80 ++++++
 ...-098F382C-607E-4341-AAE1-7898A7E5D739.json |  26 ++
 ...ID-098F382C-607E-4341-AAE1-7898A7E5D739.md |  33 +++
 ...-09A31CD3-8237-4668-8509-A1C2EA9F3775.json |  26 ++
 ...ID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md |   5 +
 ...-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json |  26 ++
 ...ID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md |  22 ++
 ...-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json |  26 ++
 ...ID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md |   5 +
 ...-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json |  26 ++
 ...ID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md |  11 +
 ...-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json |  26 ++
 ...ID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md |   7 +
 ...-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json |  26 ++
 ...ID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md |   5 +
 ...-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json |  26 ++
 ...ID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md |  77 ++++++
 ...-0DC34FAA-C182-4FAA-BFE3-70147815F471.json |  26 ++
 ...ID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md |  10 +
 ...-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json |  26 ++
 ...ID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md |   5 +
 ...-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json |  26 ++
 ...ID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md |  24 ++
 ...-10A7B17C-6F0D-432A-85BD-3205728606A0.json |  26 ++
 ...ID-10A7B17C-6F0D-432A-85BD-3205728606A0.md |  27 ++
 ...-10D04894-711A-400A-98A7-A3DECE437CDA.json |  26 ++
 ...ID-10D04894-711A-400A-98A7-A3DECE437CDA.md |   7 +
 ...-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json |  26 ++
 ...ID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md |  13 +
 ...-12450828-47CC-4F83-9E94-AF80242C2E3A.json |  26 ++
 ...ID-12450828-47CC-4F83-9E94-AF80242C2E3A.md |  14 +
 ...-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json |  26 ++
 ...ID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md |  19 ++
 ...-1457342F-8258-47AC-AEB3-54E5FE00E434.json |  26 ++
 ...ID-1457342F-8258-47AC-AEB3-54E5FE00E434.md |   3 +
 ...-1569A1AD-385D-4E16-9C85-A1915813FCC8.json |  26 ++
 ...ID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md |   6 +
 ...-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json |  26 ++
 ...ID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md |  25 ++
 ...-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json |  26 ++
 ...ID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md |  19 ++
 ...-17230E5D-DFC2-42A1-900E-1C01A1508954.json |  26 ++
 ...ID-17230E5D-DFC2-42A1-900E-1C01A1508954.md |   7 +
 ...-17B067B3-32C3-4DE7-82DE-B6033C235495.json |  26 ++
 ...ID-17B067B3-32C3-4DE7-82DE-B6033C235495.md |   7 +
 ...-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json |  26 ++
 ...ID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md |   3 +
 ...-187699B7-66AC-465F-BDA4-37F51FB0267B.json |  26 ++
 ...ID-187699B7-66AC-465F-BDA4-37F51FB0267B.md |  11 +
 ...-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json |  26 ++
 ...ID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md |   7 +
 ...-1C1ADB18-710D-40A4-ADCA-660DC7988190.json |  26 ++
 ...ID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md |  25 ++
 ...-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json |  26 ++
 ...ID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md |   3 +
 ...-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json |  26 ++
 ...ID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md |   7 +
 ...-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json |  26 ++
 ...ID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md |  13 +
 ...-1E5AE301-CE00-4509-9820-FB286DDA806A.json |  26 ++
 ...ID-1E5AE301-CE00-4509-9820-FB286DDA806A.md |   5 +
 ...-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json |  26 ++
 ...ID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md |  15 +
 ...-1EB800EB-6832-487E-BB11-07D8520003CF.json |  26 ++
 ...ID-1EB800EB-6832-487E-BB11-07D8520003CF.md |  11 +
 ...-202C8048-0342-4653-97C6-7817B2A9EEB3.json |  26 ++
 ...ID-202C8048-0342-4653-97C6-7817B2A9EEB3.md |   3 +
 ...-20656567-501C-4D21-9EDA-1C6898DF61F5.json |  26 ++
 ...ID-20656567-501C-4D21-9EDA-1C6898DF61F5.md |   9 +
 ...-206AB627-EE3C-4F56-AA25-0DFDECB86281.json |  26 ++
 ...ID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md |  59 ++++
 ...-21972435-BFD0-481F-A3E6-A52B116989F3.json |  26 ++
 ...ID-21972435-BFD0-481F-A3E6-A52B116989F3.md |  52 ++++
 ...-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json |  26 ++
 ...ID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md |  21 ++
 ...-226C1DD5-E007-4F44-A215-2FC03C269EA5.json |  26 ++
 ...ID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md |   8 +
 ...-238F9226-4EB4-4E14-B533-584277951C4B.json |  26 ++
 ...ID-238F9226-4EB4-4E14-B533-584277951C4B.md |   3 +
 ...-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json |  26 ++
 ...ID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md |   7 +
 ...-2581C2D1-AC07-4DE2-B794-20AC25652417.json |  26 ++
 ...ID-2581C2D1-AC07-4DE2-B794-20AC25652417.md |   3 +
 ...-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json |  26 ++
 ...ID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md |  15 +
 ...-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json |  26 ++
 ...ID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md |   5 +
 ...-2686BF33-E793-4BF9-98BE-82F800ED03EB.json |  26 ++
 ...ID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md |  17 ++
 ...-26D622EF-A71E-44D7-A705-176ED6445B3D.json |  26 ++
 ...ID-26D622EF-A71E-44D7-A705-176ED6445B3D.md |  16 ++
 ...-27619E64-03DD-4F3B-B66A-9C2D5350466E.json |  26 ++
 ...ID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md |   7 +
 ...-278B93C4-6B70-476F-B530-A2DBA4269FD8.json |  26 ++
 ...ID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md |   7 +
 ...-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json |  26 ++
 ...ID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md |  14 +
 ...-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json |  26 ++
 ...ID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md |   7 +
 ...-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json |  26 ++
 ...ID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md |   3 +
 ...-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json |  26 ++
 ...ID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md |   3 +
 ...-2D035C3B-0102-4FB3-BE34-74094659DC87.json |  26 ++
 ...ID-2D035C3B-0102-4FB3-BE34-74094659DC87.md |  11 +
 ...-2DEB33CC-132A-494C-B242-CA09B02E9333.json |  26 ++
 ...ID-2DEB33CC-132A-494C-B242-CA09B02E9333.md |   5 +
 ...-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json |  26 ++
 ...ID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md |  51 ++++
 ...-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json |  26 ++
 ...ID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md |   3 +
 ...-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json |  26 ++
 ...ID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md |   6 +
 ...-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json |  26 ++
 ...ID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md |  17 ++
 ...-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json |  26 ++
 ...ID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md |  12 +
 ...-30353E6D-5FA2-470C-BB80-238663945F6F.json |  26 ++
 ...ID-30353E6D-5FA2-470C-BB80-238663945F6F.md |   3 +
 ...-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json |  26 ++
 ...ID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md |   3 +
 ...-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json |  26 ++
 ...ID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md |  25 ++
 ...-30D9F5F5-7572-4440-8B31-9372D7CE352D.json |  26 ++
 ...ID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md |   8 +
 ...-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json |  26 ++
 ...ID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md |   3 +
 ...-334FA46B-AE38-41A7-BACC-8F8384C5D010.json |  26 ++
 ...ID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md |   6 +
 ...-33F3509A-A175-4204-A1A8-F3699338CAC5.json |  26 ++
 ...ID-33F3509A-A175-4204-A1A8-F3699338CAC5.md |  96 +++++++
 ...-34291BF2-6D39-46FD-B18A-338089CAF11E.json |  26 ++
 ...ID-34291BF2-6D39-46FD-B18A-338089CAF11E.md |   3 +
 ...-34B1DB42-8ADD-45C4-B945-137EB77810B6.json |  26 ++
 ...ID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md |  38 +++
 ...-35419962-0058-4856-A6BD-F4923FD0F044.json |  26 ++
 ...ID-35419962-0058-4856-A6BD-F4923FD0F044.md |   3 +
 ...-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json |  26 ++
 ...ID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md |  74 +++++
 ...-3702D75B-9505-40D0-B220-7739F5F72760.json |  26 ++
 ...ID-3702D75B-9505-40D0-B220-7739F5F72760.md |  47 ++++
 ...-371A58A1-F821-449C-8D2D-EC2657C13B56.json |  26 ++
 ...ID-371A58A1-F821-449C-8D2D-EC2657C13B56.md |   9 +
 ...-37CA1665-B331-452A-AA3D-59608D85F006.json |  26 ++
 ...ID-37CA1665-B331-452A-AA3D-59608D85F006.md |   1 +
 ...-392743FA-D99D-4995-A8F6-3E5541271263.json |  26 ++
 ...ID-392743FA-D99D-4995-A8F6-3E5541271263.md |  21 ++
 ...-397630C5-C2CE-4E35-A45D-0228C8F70867.json |  26 ++
 ...ID-397630C5-C2CE-4E35-A45D-0228C8F70867.md |  10 +
 ...-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json |  26 ++
 ...ID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md |   9 +
 ...-3A5066B9-898A-4673-A713-C3E41D502742.json |  26 ++
 ...ID-3A5066B9-898A-4673-A713-C3E41D502742.md |  11 +
 ...-3A5117DE-E11D-41D0-A016-A68154A90DCA.json |  26 ++
 ...ID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md |   9 +
 ...-3A627DBF-D797-42A2-A9AC-AAC321376068.json |  26 ++
 ...ID-3A627DBF-D797-42A2-A9AC-AAC321376068.md |  25 ++
 ...-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json |  26 ++
 ...ID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md |   3 +
 ...-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json |  26 ++
 ...ID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md |  36 +++
 ...-3B34F036-4C25-4058-B5F4-5340545BE821.json |  26 ++
 ...ID-3B34F036-4C25-4058-B5F4-5340545BE821.md |   9 +
 ...-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json |  26 ++
 ...ID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md |  20 ++
 ...-3D27BE17-47C9-476C-AD13-DD516697F862.json |  26 ++
 ...ID-3D27BE17-47C9-476C-AD13-DD516697F862.md |  12 +
 ...-3E03B539-B71C-4D2E-A218-23713D723408.json |  26 ++
 ...ID-3E03B539-B71C-4D2E-A218-23713D723408.md |   5 +
 ...-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json |  26 ++
 ...ID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md |  30 ++
 ...-40300B80-D69C-450B-9848-7A21A3141005.json |  26 ++
 ...ID-40300B80-D69C-450B-9848-7A21A3141005.md |  12 +
 ...-429877DA-255E-41FC-86B6-E7069B0EE7A6.json |  26 ++
 ...ID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md |  63 +++++
 ...-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json |  26 ++
 ...ID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md |   7 +
 ...-443DD312-C75F-4267-A17E-FEDCFD7335FB.json |  26 ++
 ...ID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md |   6 +
 ...-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json |  26 ++
 ...ID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md |   9 +
 ...-44974486-3ED4-4C5C-849B-8746A4899889.json |  26 ++
 ...ID-44974486-3ED4-4C5C-849B-8746A4899889.md |   9 +
 ...-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json |  26 ++
 ...ID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md |  10 +
 ...-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json |  26 ++
 ...ID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md |   9 +
 ...-45B4119E-416A-43FA-B2A0-C7D52D028326.json |  26 ++
 ...ID-45B4119E-416A-43FA-B2A0-C7D52D028326.md |  15 +
 ...-45D07344-870A-4CB7-84D9-4AF78C151B70.json |  26 ++
 ...ID-45D07344-870A-4CB7-84D9-4AF78C151B70.md |  21 ++
 ...-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json |  26 ++
 ...ID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md |   5 +
 ...-46D03C40-2146-434A-B75A-12BBBDB56FF3.json |  26 ++
 ...ID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md |  31 +++
 ...-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json |  26 ++
 ...ID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md |  23 ++
 ...-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json |  26 ++
 ...ID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md |  12 +
 ...-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json |  26 ++
 ...ID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md |  34 +++
 ...-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json |  26 ++
 ...ID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md |   5 +
 ...-4AE72311-7C7E-4384-A7E1-A23048B29C40.json |  26 ++
 ...ID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md |   3 +
 ...-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json |  26 ++
 ...ID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md |  12 +
 ...-4CCF6004-31A7-4B35-996D-5E12877CB443.json |  26 ++
 ...ID-4CCF6004-31A7-4B35-996D-5E12877CB443.md |   3 +
 ...-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json |  26 ++
 ...ID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md |   7 +
 ...-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json |  26 ++
 ...ID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md |  11 +
 ...-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json |  26 ++
 ...ID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md |   3 +
 ...-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json |  26 ++
 ...ID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md |  19 ++
 ...-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json |  26 ++
 ...ID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md |  16 ++
 ...-4F822F1E-105F-48CD-83A7-3BB562A5B147.json |  26 ++
 ...ID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md |   3 +
 ...-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json |  26 ++
 ...ID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md |   4 +
 ...-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json |  26 ++
 ...ID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md |  10 +
 ...-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json |  26 ++
 ...ID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md |  13 +
 ...-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json |  26 ++
 ...ID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md |  65 +++++
 ...-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json |  26 ++
 ...ID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md |   5 +
 ...-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json |  26 ++
 ...ID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md |  42 +++
 ...-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json |  26 ++
 ...ID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md |   8 +
 ...-5504862E-8120-469D-8708-2290772E5585.json |  26 ++
 ...ID-5504862E-8120-469D-8708-2290772E5585.md |  13 +
 ...-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json |  26 ++
 ...ID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md |  80 ++++++
 ...-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json |  26 ++
 ...ID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md |   5 +
 ...-5571B267-5385-4EEC-A400-FD23FD4B239C.json |  26 ++
 ...ID-5571B267-5385-4EEC-A400-FD23FD4B239C.md |   3 +
 ...-55BA17AE-7F27-4832-BADC-D76B073635C6.json |  26 ++
 ...ID-55BA17AE-7F27-4832-BADC-D76B073635C6.md |   4 +
 ...-55E760C3-2167-4A03-88ED-D9078C196D74.json |  26 ++
 ...ID-55E760C3-2167-4A03-88ED-D9078C196D74.md |   8 +
 ...-5663C34A-23E8-42CA-B7BF-5A79A0070456.json |  26 ++
 ...ID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md |   7 +
 ...-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json |  26 ++
 ...ID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md |   8 +
 ...-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json |  26 ++
 ...ID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md |  13 +
 ...-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json |  26 ++
 ...ID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md |   8 +
 ...-580E4107-827A-43F6-888D-5CDD41EB42E0.json |  26 ++
 ...ID-580E4107-827A-43F6-888D-5CDD41EB42E0.md |  25 ++
 ...-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json |  26 ++
 ...ID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md |  23 ++
 ...-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json |  26 ++
 ...ID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md |   8 +
 ...-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json |  26 ++
 ...ID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md |   7 +
 ...-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json |  26 ++
 ...ID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md |  53 ++++
 ...-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json |  26 ++
 ...ID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md |   3 +
 ...-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json |  26 ++
 ...ID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md |  20 ++
 ...-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json |  26 ++
 ...ID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md |  13 +
 ...-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json |  26 ++
 ...ID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md |   7 +
 ...-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json |  26 ++
 ...ID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md |  11 +
 ...-5E442E1F-D996-4863-BA47-1EE76E07A12C.json |  26 ++
 ...ID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md |  29 ++
 ...-5F75E5AF-90D3-4F85-B937-F98415300AC5.json |  26 ++
 ...ID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md |  20 ++
 ...-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json |  26 ++
 ...ID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md |   3 +
 ...-61053EC5-4910-454F-8B71-6B06408A6451.json |  26 ++
 ...ID-61053EC5-4910-454F-8B71-6B06408A6451.md |   8 +
 ...-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json |  26 ++
 ...ID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md |  49 ++++
 ...-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json |  26 ++
 ...ID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md |   3 +
 ...-62D603EE-56F3-478D-9625-2FC3B6F189E8.json |  26 ++
 ...ID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md |  25 ++
 ...-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json |  26 ++
 ...ID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md |  23 ++
 ...-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json |  26 ++
 ...ID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md |   9 +
 ...-634760AA-7E46-42A7-AD08-85CCE4656873.json |  26 ++
 ...ID-634760AA-7E46-42A7-AD08-85CCE4656873.md |  36 +++
 ...-63ADF495-37BF-424E-85F4-614EE91DA301.json |  26 ++
 ...ID-63ADF495-37BF-424E-85F4-614EE91DA301.md |  12 +
 ...-63B0F6F4-69CA-40C1-997E-949DD702C77E.json |  26 ++
 ...ID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md |   3 +
 ...-64001B38-0509-46D5-854E-3A8500798DEE.json |  26 ++
 ...ID-64001B38-0509-46D5-854E-3A8500798DEE.md |  13 +
 ...-650706CA-915E-4239-9D69-35902E82B60E.json |  26 ++
 ...ID-650706CA-915E-4239-9D69-35902E82B60E.md |   9 +
 ...-6549D43B-D0BB-4416-9771-AF11F387B629.json |  26 ++
 ...ID-6549D43B-D0BB-4416-9771-AF11F387B629.md |   7 +
 ...-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json |  26 ++
 ...ID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md |  14 +
 ...-69626666-7280-4AF5-9871-FA2D82CED05E.json |  26 ++
 ...ID-69626666-7280-4AF5-9871-FA2D82CED05E.md |  20 ++
 ...-69CE737F-F442-4C04-8B1A-8881930B69AE.json |  26 ++
 ...ID-69CE737F-F442-4C04-8B1A-8881930B69AE.md |  17 ++
 ...-6B35AE72-3D19-447A-A19D-D96DDD769B67.json |  26 ++
 ...ID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md |  84 ++++++
 ...-6B80D87B-8461-414D-9172-07E68896EB06.json |  26 ++
 ...ID-6B80D87B-8461-414D-9172-07E68896EB06.md |  20 ++
 ...-6B9A77F8-731B-43A1-92C8-0163E20D8048.json |  26 ++
 ...ID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md |  28 ++
 ...-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json |  26 ++
 ...ID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md |   3 +
 ...-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json |  26 ++
 ...ID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md |  25 ++
 ...-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json |  26 ++
 ...ID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md |  18 ++
 ...-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json |  26 ++
 ...ID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md |  11 +
 ...-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json |  26 ++
 ...ID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md |  12 +
 ...-712F2BB4-F856-419F-BB88-2E137DD46F72.json |  26 ++
 ...ID-712F2BB4-F856-419F-BB88-2E137DD46F72.md |  11 +
 ...-7138E486-AE62-4778-9358-F098126785A5.json |  26 ++
 ...ID-7138E486-AE62-4778-9358-F098126785A5.md |   5 +
 ...-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json |  26 ++
 ...ID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md |  20 ++
 ...-74590319-12A6-4101-9043-8DDB56BB0720.json |  26 ++
 ...ID-74590319-12A6-4101-9043-8DDB56BB0720.md |  18 ++
 ...-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json |  26 ++
 ...ID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md |  13 +
 ...-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json |  26 ++
 ...ID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md |   6 +
 ...-76B17464-6C1D-468E-B6D2-93ECF87E2289.json |  26 ++
 ...ID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md |  18 ++
 ...-76B546AD-121A-4C3A-B42C-D642C8624A3C.json |  26 ++
 ...ID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md |   7 +
 ...-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json |  26 ++
 ...ID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md |   8 +
 ...-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json |  26 ++
 ...ID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md |  14 +
 ...-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json |  26 ++
 ...ID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md |  22 ++
 ...-7C6154EA-09BC-4E68-8BAB-D784F0582440.json |  26 ++
 ...ID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md |   7 +
 ...-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json |  26 ++
 ...ID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md |  42 +++
 ...-7D80BD98-F855-4690-AC44-6BA192EC1E53.json |  26 ++
 ...ID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md |  13 +
 ...-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json |  26 ++
 ...ID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md |   9 +
 ...-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json |  26 ++
 ...ID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md |  35 +++
 ...-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json |  26 ++
 ...ID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md |   3 +
 ...-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json |  26 ++
 ...ID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md |  12 +
 ...-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json |  26 ++
 ...ID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md |  28 ++
 ...-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json |  26 ++
 ...ID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md |   9 +
 ...-83AF39C3-5542-4739-B9ED-C867C472CDCE.json |  26 ++
 ...ID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md |  11 +
 ...-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json |  26 ++
 ...ID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md |  10 +
 ...-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json |  26 ++
 ...ID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md |  15 +
 ...-87FC621D-8EDE-48DE-901B-00058C07E62D.json |  26 ++
 ...ID-87FC621D-8EDE-48DE-901B-00058C07E62D.md |  27 ++
 ...-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json |  26 ++
 ...ID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md |   5 +
 ...-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json |  26 ++
 ...ID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md |  29 ++
 ...-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json |  26 ++
 ...ID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md |  81 ++++++
 ...-8AFBB53F-6749-4E7E-AAF2-310849586320.json |  26 ++
 ...ID-8AFBB53F-6749-4E7E-AAF2-310849586320.md |   7 +
 ...-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json |  26 ++
 ...ID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md |   3 +
 ...-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json |  26 ++
 ...ID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md |  44 +++
 ...-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json |  26 ++
 ...ID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md |  12 +
 ...-8E19FA4E-4408-4784-A629-DD936DEEBA26.json |  26 ++
 ...ID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md |   3 +
 ...-8EC2E33D-2086-4253-BF7D-D953052774A0.json |  26 ++
 ...ID-8EC2E33D-2086-4253-BF7D-D953052774A0.md |   7 +
 ...-91D3F799-4C17-4008-B605-FEE370890091.json |  26 ++
 ...ID-91D3F799-4C17-4008-B605-FEE370890091.md |   3 +
 ...-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json |  26 ++
 ...ID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md |  20 ++
 ...-94133965-3802-4768-A71D-2AD5F8402BD9.json |  26 ++
 ...ID-94133965-3802-4768-A71D-2AD5F8402BD9.md |  13 +
 ...-949DC89F-26C2-4028-9A1F-2616FB466736.json |  26 ++
 ...ID-949DC89F-26C2-4028-9A1F-2616FB466736.md |  13 +
 ...-953F9E2E-D9DD-4469-96EE-A288371FE36E.json |  26 ++
 ...ID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md |  82 ++++++
 ...-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json |  26 ++
 ...ID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md |   7 +
 ...-960DA835-B984-49FB-80DE-EE6D38D42EDD.json |  26 ++
 ...ID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md |  13 +
 ...-967D7E5A-D701-4580-BFCB-0EB3588D2725.json |  26 ++
 ...ID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md |   3 +
 ...-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json |  26 ++
 ...ID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md |  13 +
 ...-97951AE9-439B-4779-823D-E118E1CB08D3.json |  26 ++
 ...ID-97951AE9-439B-4779-823D-E118E1CB08D3.md |   9 +
 ...-9886AD4A-5C64-4E09-A106-B14419362757.json |  26 ++
 ...ID-9886AD4A-5C64-4E09-A106-B14419362757.md |  21 ++
 ...-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json |  26 ++
 ...ID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md |   5 +
 ...-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json |  26 ++
 ...ID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md |  17 ++
 ...-9969BD6B-639D-4633-B825-79578464E8E6.json |  26 ++
 ...ID-9969BD6B-639D-4633-B825-79578464E8E6.md |   8 +
 ...-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json |  26 ++
 ...ID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md |  11 +
 ...-9AA16B50-F8A4-443B-AD6C-6E018596459B.json |  26 ++
 ...ID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md |   5 +
 ...-9BDE2563-18FC-49B0-83D7-47F57E044D97.json |  26 ++
 ...ID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md |   7 +
 ...-9C1E97D3-4285-4F70-ACAF-A56767901C74.json |  26 ++
 ...ID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md |  15 +
 ...-9CB7CEE4-C724-448E-822A-75F155B88EAC.json |  26 ++
 ...ID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md |  11 +
 ...-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json |  26 ++
 ...ID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md |   6 +
 ...-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json |  26 ++
 ...ID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md |   8 +
 ...-9DA38943-BF95-446D-AB09-32323160D51B.json |  26 ++
 ...ID-9DA38943-BF95-446D-AB09-32323160D51B.md |  53 ++++
 ...-9DA820B7-7477-4980-848B-7161BDB5C43E.json |  26 ++
 ...ID-9DA820B7-7477-4980-848B-7161BDB5C43E.md |   9 +
 ...-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json |  26 ++
 ...ID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md |   4 +
 ...-9EC70919-852C-427E-ACDF-D59319D72468.json |  26 ++
 ...ID-9EC70919-852C-427E-ACDF-D59319D72468.md |  23 ++
 ...-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json |  26 ++
 ...ID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md |   6 +
 ...-9FC58214-95C7-4690-91DA-3185640E3712.json |  26 ++
 ...ID-9FC58214-95C7-4690-91DA-3185640E3712.md |   7 +
 ...-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json |  26 ++
 ...ID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md |  26 ++
 ...-9FF6393B-3B5D-4409-B0BC-461062C5F766.json |  26 ++
 ...ID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md |   3 +
 ...-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json |  26 ++
 ...ID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md |  35 +++
 ...-A1E79BA5-CE31-4357-878E-11464E03158C.json |  26 ++
 ...ID-A1E79BA5-CE31-4357-878E-11464E03158C.md |   6 +
 ...-A2A63203-21AB-4358-8706-62DF795EAE62.json |  26 ++
 ...ID-A2A63203-21AB-4358-8706-62DF795EAE62.md |  10 +
 ...-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json |  26 ++
 ...ID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md |   3 +
 ...-A391DC49-6523-4517-9AE1-F2E78CE91411.json |  26 ++
 ...ID-A391DC49-6523-4517-9AE1-F2E78CE91411.md |  11 +
 ...-A3EE4127-5F12-4F3A-89EA-138882DA237B.json |  26 ++
 ...ID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md |   9 +
 ...-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json |  21 ++
 ...ID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md |  27 ++
 ...-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json |  26 ++
 ...ID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md |  12 +
 ...-A5F5433C-0F21-4877-BFC6-522D421A1842.json |  26 ++
 ...ID-A5F5433C-0F21-4877-BFC6-522D421A1842.md |   3 +
 ...-A742B359-6C9C-4BC0-AA52-30189D93AA33.json |  26 ++
 ...ID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md |   7 +
 ...-A745B955-2E59-4769-AB47-E32098A84653.json |  26 ++
 ...ID-A745B955-2E59-4769-AB47-E32098A84653.md |   7 +
 ...-A7CB5566-0283-4C67-BA27-02852732D7C3.json |  26 ++
 ...ID-A7CB5566-0283-4C67-BA27-02852732D7C3.md |  69 +++++
 ...-AAD13737-533B-491F-A155-DDB027057157.json |  26 ++
 ...ID-AAD13737-533B-491F-A155-DDB027057157.md |  14 +
 ...-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json |  31 +++
 ...ID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md |  19 ++
 ...-AB938CF2-D0FE-4516-931D-0238D0662B84.json |  26 ++
 ...ID-AB938CF2-D0FE-4516-931D-0238D0662B84.md |   8 +
 ...-AC33B458-3F39-4BA6-A242-E00B613C60DA.json |  31 +++
 ...ID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md |  17 ++
 ...-AC461BBD-647D-447D-9307-218A41CE368B.json |  26 ++
 ...ID-AC461BBD-647D-447D-9307-218A41CE368B.md |  11 +
 ...-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json |  26 ++
 ...ID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md |   7 +
 ...-ADF74748-AB0E-42F4-BB23-79C5B079A778.json |  26 ++
 ...ID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md |  77 ++++++
 ...-AE27985B-5909-407F-A105-5B0574715D13.json |  26 ++
 ...ID-AE27985B-5909-407F-A105-5B0574715D13.md |   7 +
 ...-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json |  26 ++
 ...ID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md |  38 +++
 ...-AFF4C609-07DB-429C-B7A7-82F9568D6297.json |  26 ++
 ...ID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md |   3 +
 ...-B3241978-4E00-4630-A8AB-E597193E51E2.json |  26 ++
 ...ID-B3241978-4E00-4630-A8AB-E597193E51E2.md |  38 +++
 ...-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json |  26 ++
 ...ID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md |   5 +
 ...-B5387FE3-B36D-4924-B168-329B6E41D811.json |  26 ++
 ...ID-B5387FE3-B36D-4924-B168-329B6E41D811.md |   3 +
 ...-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json |  26 ++
 ...ID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md |  18 ++
 ...-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json |  26 ++
 ...ID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md |   7 +
 ...-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json |  26 ++
 ...ID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md |  14 +
 ...-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json |  26 ++
 ...ID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md |   9 +
 ...-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json |  26 ++
 ...ID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md |  23 ++
 ...-B6F5194C-290E-464F-A718-232984A6E8B5.json |  26 ++
 ...ID-B6F5194C-290E-464F-A718-232984A6E8B5.md |   6 +
 ...-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json |  21 ++
 ...ID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md |  17 ++
 ...-B82658C8-6002-424B-B257-D52A7D603BC3.json |  26 ++
 ...ID-B82658C8-6002-424B-B257-D52A7D603BC3.md |   7 +
 ...-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json |  26 ++
 ...ID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md |   9 +
 ...-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json |  26 ++
 ...ID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md |  10 +
 ...-B8FB507C-D7BB-462A-847F-E5A4B708E142.json |  26 ++
 ...ID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md |   4 +
 ...-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json |  26 ++
 ...ID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md |   1 +
 ...-B94BC2CB-8504-41C6-8848-512529EEE941.json |  26 ++
 ...ID-B94BC2CB-8504-41C6-8848-512529EEE941.md |   4 +
 ...-BB270862-D56D-4B6F-86B7-030ED273E907.json |  26 ++
 ...ID-BB270862-D56D-4B6F-86B7-030ED273E907.md |   3 +
 ...-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json |  26 ++
 ...ID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md | 256 ++++++++++++++++++
 ...-BC17942D-DE0B-4244-900F-DE38D31A09EC.json |  26 ++
 ...ID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md |   6 +
 ...-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json |  26 ++
 ...ID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md |  17 ++
 ...-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json |  26 ++
 ...ID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md |  15 +
 ...-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json |  26 ++
 ...ID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md |  52 ++++
 ...-BD0C3274-B70C-437A-B89C-C77A703FFD53.json |  26 ++
 ...ID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md |  28 ++
 ...-BE852729-65DF-4377-9A64-F05D47CD9D49.json |  26 ++
 ...ID-BE852729-65DF-4377-9A64-F05D47CD9D49.md |  25 ++
 ...-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json |  26 ++
 ...ID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md |  13 +
 ...-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json |  26 ++
 ...ID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md |  10 +
 ...-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json |  26 ++
 ...ID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md |  53 ++++
 ...-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json |  26 ++
 ...ID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md |   6 +
 ...-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json |  26 ++
 ...ID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md |  12 +
 ...-C7399A7B-40C6-4DCA-8A92-EAB777739496.json |  26 ++
 ...ID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md |  25 ++
 ...-C7747582-1A56-458D-B985-DDF459F1CE7C.json |  26 ++
 ...ID-C7747582-1A56-458D-B985-DDF459F1CE7C.md |  73 +++++
 ...-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json |  26 ++
 ...ID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md |   9 +
 ...-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json |  26 ++
 ...ID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md |   4 +
 ...-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json |  26 ++
 ...ID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md |  10 +
 ...-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json |  26 ++
 ...ID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md |   5 +
 ...-CA181AC5-CA1D-47ED-9D44-008642C89290.json |  26 ++
 ...ID-CA181AC5-CA1D-47ED-9D44-008642C89290.md |  97 +++++++
 ...-CA806876-1093-4A39-BE62-439C4802A915.json |  26 ++
 ...ID-CA806876-1093-4A39-BE62-439C4802A915.md |  17 ++
 ...-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json |  26 ++
 ...ID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md |   3 +
 ...-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json |  26 ++
 ...ID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md |   7 +
 ...-CD00669C-741C-480C-B444-67F079061438.json |  26 ++
 ...ID-CD00669C-741C-480C-B444-67F079061438.md |  11 +
 ...-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json |  26 ++
 ...ID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md |   8 +
 ...-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json |  26 ++
 ...ID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md |  76 ++++++
 ...-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json |  26 ++
 ...ID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md |  24 ++
 ...-CDB73B95-18B8-4A10-A09C-4176EE11497D.json |  26 ++
 ...ID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md |  15 +
 ...-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json |  26 ++
 ...ID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md |  11 +
 ...-CFE82665-23A3-49F2-9202-1C2A720CC64D.json |  26 ++
 ...ID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md |  12 +
 ...-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json |  26 ++
 ...ID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md |  26 ++
 ...-D280323C-DF16-4F69-86CA-111B7CFCA25E.json |  26 ++
 ...ID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md |  21 ++
 ...-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json |  26 ++
 ...ID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md | 106 ++++++++
 ...-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json |  26 ++
 ...ID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md |  15 +
 ...-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json |  26 ++
 ...ID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md |  59 ++++
 ...-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json |  26 ++
 ...ID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md |   9 +
 ...-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json |  26 ++
 ...ID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md |  11 +
 ...-D647F00D-6B45-4E18-B442-14835847EFA7.json |  26 ++
 ...ID-D647F00D-6B45-4E18-B442-14835847EFA7.md |  23 ++
 ...-D6B5BF84-8D86-4215-94FF-119D52387FDB.json |  26 ++
 ...ID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md |  14 +
 ...-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json |  26 ++
 ...ID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md |   5 +
 ...-D7A36529-C624-486D-8C0E-FA69A4DC4014.json |  26 ++
 ...ID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md |   5 +
 ...-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json |  26 ++
 ...ID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md |   5 +
 ...-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json |  26 ++
 ...ID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md |   8 +
 ...-DA1898BD-3EB1-432A-BD34-373B29B05B89.json |  26 ++
 ...ID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md |   6 +
 ...-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json |  26 ++
 ...ID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md |   3 +
 ...-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json |  26 ++
 ...ID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md |  23 ++
 ...-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json |  26 ++
 ...ID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md |   3 +
 ...-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json |  26 ++
 ...ID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md |  14 +
 ...-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json |  26 ++
 ...ID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md |  23 ++
 ...-DF02CF23-8387-4D00-87AF-5F2054075F18.json |  26 ++
 ...ID-DF02CF23-8387-4D00-87AF-5F2054075F18.md |  11 +
 ...-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json |  26 ++
 ...ID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md |  12 +
 ...-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json |  26 ++
 ...ID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md |  28 ++
 ...-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json |  26 ++
 ...ID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md |  16 ++
 ...-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json |  26 ++
 ...ID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md |  17 ++
 ...-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json |  26 ++
 ...ID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md |  15 +
 ...-E04CE9DF-E832-41CB-B559-1800B7943A2F.json |  26 ++
 ...ID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md |  20 ++
 ...-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json |  26 ++
 ...ID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md |  97 +++++++
 ...-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json |  26 ++
 ...ID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md |   5 +
 ...-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json |  26 ++
 ...ID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md |  31 +++
 ...-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json |  26 ++
 ...ID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md |  77 ++++++
 ...-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json |  26 ++
 ...ID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md |   3 +
 ...-E32D92B2-8DB3-42C3-982C-7E9D88231069.json |  26 ++
 ...ID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md |  19 ++
 ...-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json |  26 ++
 ...ID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md |  15 +
 ...-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json |  26 ++
 ...ID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md |   6 +
 ...-E4F3DF9C-1873-4893-BE81-D85015D67F19.json |  26 ++
 ...ID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md |   7 +
 ...-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json |  26 ++
 ...ID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md |  18 ++
 ...-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json |  26 ++
 ...ID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md |  48 ++++
 ...-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json |  26 ++
 ...ID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md |   7 +
 ...-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json |  26 ++
 ...ID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md |  11 +
 ...-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json |  26 ++
 ...ID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md |   7 +
 ...-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json |  26 ++
 ...ID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md |   3 +
 ...-EB317455-AAFD-4465-8961-6E7C13B48CCB.json |  26 ++
 ...ID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md |  26 ++
 ...-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json |  26 ++
 ...ID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md |  13 +
 ...-EC91E230-8323-4710-9A47-D57A15BE71AA.json |  26 ++
 ...ID-EC91E230-8323-4710-9A47-D57A15BE71AA.md |   8 +
 ...-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json |  26 ++
 ...ID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md | 109 ++++++++
 ...-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json |  26 ++
 ...ID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md |  11 +
 ...-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json |  26 ++
 ...ID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md |   8 +
 ...-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json |  26 ++
 ...ID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md |  24 ++
 ...-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json |  26 ++
 ...ID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md |  31 +++
 ...-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json |  26 ++
 ...ID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md |  13 +
 ...-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json |  26 ++
 ...ID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md |   3 +
 ...-F25A1489-CFA2-4B4A-9340-1C278198A951.json |  26 ++
 ...ID-F25A1489-CFA2-4B4A-9340-1C278198A951.md |   8 +
 ...-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json |  26 ++
 ...ID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md |  29 ++
 ...-F3650ED7-96D8-4542-8D04-ED3527A9C565.json |  26 ++
 ...ID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md |   7 +
 ...-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json |  26 ++
 ...ID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md |  14 +
 ...-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json |  26 ++
 ...ID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md |  18 ++
 ...-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json |  26 ++
 ...ID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md |  18 ++
 ...-F5A818DC-E3A9-4020-84FC-B087B2C14158.json |  26 ++
 ...ID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md |  29 ++
 ...-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json |  26 ++
 ...ID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md |   6 +
 ...-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json |  26 ++
 ...ID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md | 108 ++++++++
 ...-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json |  26 ++
 ...ID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md |  14 +
 ...-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json |  26 ++
 ...ID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md |   8 +
 ...-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json |  26 ++
 ...ID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md |  12 +
 ...-FA7264AB-8547-45E3-8752-8D47B6708F86.json |  26 ++
 ...ID-FA7264AB-8547-45E3-8752-8D47B6708F86.md |  20 ++
 ...-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json |  26 ++
 ...ID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md |  11 +
 ...-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json |  26 ++
 ...ID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md |  21 ++
 ...-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json |  26 ++
 ...ID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md |  14 +
 ...-FB7D15CC-A606-42DC-9DBF-27778D20282D.json |  26 ++
 ...ID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md |  43 +++
 ...-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json |  26 ++
 ...ID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md |  94 +++++++
 ...-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json |  26 ++
 ...ID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md |   3 +
 ...-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json |  26 ++
 ...ID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md |   8 +
 ...-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json |  26 ++
 ...ID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md |   3 +
 ...-FDC357F5-AFCA-4175-ADF4-43928922C384.json |  26 ++
 ...ID-FDC357F5-AFCA-4175-ADF4-43928922C384.md |  13 +
 ...-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json |  26 ++
 ...ID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md |  13 +
 ...-008AF6CD-E219-4D76-B175-B763E5C397CE.json |  26 ++
 ...ID-008AF6CD-E219-4D76-B175-B763E5C397CE.md |  27 ++
 ...-02679208-A796-4A58-80AC-33DCF6A4899F.json |  26 ++
 ...ID-02679208-A796-4A58-80AC-33DCF6A4899F.md |  20 ++
 ...-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json |  26 ++
 ...ID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md |   3 +
 ...-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json |  26 ++
 ...ID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md |   4 +
 ...-0503F050-177F-4360-9B1A-49439AF366B8.json |  26 ++
 ...ID-0503F050-177F-4360-9B1A-49439AF366B8.md |  11 +
 ...-054A7DC4-C03C-4356-8486-19472075129E.json |  26 ++
 ...ID-054A7DC4-C03C-4356-8486-19472075129E.md |  10 +
 ...-06426E05-BE70-4917-89E3-153236303513.json |  26 ++
 ...ID-06426E05-BE70-4917-89E3-153236303513.md |   3 +
 ...-06E4D650-D16A-4E96-98FE-B634E5DEA776.json |  26 ++
 ...ID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md |   3 +
 ...-07778212-ECE2-41DC-A130-1A6271833CA4.json |  26 ++
 ...ID-07778212-ECE2-41DC-A130-1A6271833CA4.md |  80 ++++++
 ...-098F382C-607E-4341-AAE1-7898A7E5D739.json |  26 ++
 ...ID-098F382C-607E-4341-AAE1-7898A7E5D739.md |  33 +++
 ...-09A31CD3-8237-4668-8509-A1C2EA9F3775.json |  26 ++
 ...ID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md |   5 +
 ...-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json |  26 ++
 ...ID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md |  22 ++
 ...-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json |  26 ++
 ...ID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md |   5 +
 ...-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json |  26 ++
 ...ID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md |  11 +
 ...-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json |  26 ++
 ...ID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md |   7 +
 ...-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json |  26 ++
 ...ID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md |   5 +
 ...-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json |  26 ++
 ...ID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md |  77 ++++++
 ...-0DC34FAA-C182-4FAA-BFE3-70147815F471.json |  26 ++
 ...ID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md |  10 +
 ...-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json |  26 ++
 ...ID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md |   5 +
 ...-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json |  26 ++
 ...ID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md |  24 ++
 ...-10A7B17C-6F0D-432A-85BD-3205728606A0.json |  26 ++
 ...ID-10A7B17C-6F0D-432A-85BD-3205728606A0.md |  27 ++
 ...-10D04894-711A-400A-98A7-A3DECE437CDA.json |  26 ++
 ...ID-10D04894-711A-400A-98A7-A3DECE437CDA.md |   7 +
 ...-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json |  26 ++
 ...ID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md |  13 +
 ...-12450828-47CC-4F83-9E94-AF80242C2E3A.json |  26 ++
 ...ID-12450828-47CC-4F83-9E94-AF80242C2E3A.md |  14 +
 ...-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json |  26 ++
 ...ID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md |  19 ++
 ...-1457342F-8258-47AC-AEB3-54E5FE00E434.json |  26 ++
 ...ID-1457342F-8258-47AC-AEB3-54E5FE00E434.md |   3 +
 ...-1569A1AD-385D-4E16-9C85-A1915813FCC8.json |  26 ++
 ...ID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md |   6 +
 ...-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json |  26 ++
 ...ID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md |  25 ++
 ...-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json |  26 ++
 ...ID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md |  19 ++
 ...-17230E5D-DFC2-42A1-900E-1C01A1508954.json |  26 ++
 ...ID-17230E5D-DFC2-42A1-900E-1C01A1508954.md |   7 +
 ...-17B067B3-32C3-4DE7-82DE-B6033C235495.json |  26 ++
 ...ID-17B067B3-32C3-4DE7-82DE-B6033C235495.md |   7 +
 ...-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json |  26 ++
 ...ID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md |   3 +
 ...-187699B7-66AC-465F-BDA4-37F51FB0267B.json |  26 ++
 ...ID-187699B7-66AC-465F-BDA4-37F51FB0267B.md |  11 +
 ...-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json |  26 ++
 ...ID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md |   7 +
 ...-1C1ADB18-710D-40A4-ADCA-660DC7988190.json |  26 ++
 ...ID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md |  25 ++
 ...-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json |  26 ++
 ...ID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md |   3 +
 ...-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json |  26 ++
 ...ID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md |   7 +
 ...-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json |  26 ++
 ...ID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md |  13 +
 ...-1E5AE301-CE00-4509-9820-FB286DDA806A.json |  26 ++
 ...ID-1E5AE301-CE00-4509-9820-FB286DDA806A.md |   5 +
 ...-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json |  26 ++
 ...ID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md |  15 +
 ...-1EB800EB-6832-487E-BB11-07D8520003CF.json |  26 ++
 ...ID-1EB800EB-6832-487E-BB11-07D8520003CF.md |  11 +
 ...-202C8048-0342-4653-97C6-7817B2A9EEB3.json |  26 ++
 ...ID-202C8048-0342-4653-97C6-7817B2A9EEB3.md |   3 +
 ...-20656567-501C-4D21-9EDA-1C6898DF61F5.json |  26 ++
 ...ID-20656567-501C-4D21-9EDA-1C6898DF61F5.md |   9 +
 ...-206AB627-EE3C-4F56-AA25-0DFDECB86281.json |  26 ++
 ...ID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md |  59 ++++
 ...-21972435-BFD0-481F-A3E6-A52B116989F3.json |  26 ++
 ...ID-21972435-BFD0-481F-A3E6-A52B116989F3.md |  52 ++++
 ...-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json |  26 ++
 ...ID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md |  21 ++
 ...-226C1DD5-E007-4F44-A215-2FC03C269EA5.json |  26 ++
 ...ID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md |   8 +
 ...-238F9226-4EB4-4E14-B533-584277951C4B.json |  26 ++
 ...ID-238F9226-4EB4-4E14-B533-584277951C4B.md |   3 +
 ...-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json |  26 ++
 ...ID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md |   7 +
 ...-2581C2D1-AC07-4DE2-B794-20AC25652417.json |  26 ++
 ...ID-2581C2D1-AC07-4DE2-B794-20AC25652417.md |   3 +
 ...-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json |  26 ++
 ...ID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md |  15 +
 ...-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json |  26 ++
 ...ID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md |   5 +
 ...-2686BF33-E793-4BF9-98BE-82F800ED03EB.json |  26 ++
 ...ID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md |  17 ++
 ...-26D622EF-A71E-44D7-A705-176ED6445B3D.json |  26 ++
 ...ID-26D622EF-A71E-44D7-A705-176ED6445B3D.md |  16 ++
 ...-27619E64-03DD-4F3B-B66A-9C2D5350466E.json |  26 ++
 ...ID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md |   7 +
 ...-278B93C4-6B70-476F-B530-A2DBA4269FD8.json |  26 ++
 ...ID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md |   7 +
 ...-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json |  26 ++
 ...ID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md |  14 +
 ...-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json |  26 ++
 ...ID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md |   7 +
 ...-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json |  26 ++
 ...ID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md |   3 +
 ...-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json |  26 ++
 ...ID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md |   3 +
 ...-2D035C3B-0102-4FB3-BE34-74094659DC87.json |  26 ++
 ...ID-2D035C3B-0102-4FB3-BE34-74094659DC87.md |  11 +
 ...-2DEB33CC-132A-494C-B242-CA09B02E9333.json |  26 ++
 ...ID-2DEB33CC-132A-494C-B242-CA09B02E9333.md |   5 +
 ...-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json |  26 ++
 ...ID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md |  51 ++++
 ...-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json |  26 ++
 ...ID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md |   3 +
 ...-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json |  26 ++
 ...ID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md |   6 +
 ...-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json |  26 ++
 ...ID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md |  17 ++
 ...-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json |  26 ++
 ...ID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md |  12 +
 ...-30353E6D-5FA2-470C-BB80-238663945F6F.json |  26 ++
 ...ID-30353E6D-5FA2-470C-BB80-238663945F6F.md |   3 +
 ...-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json |  26 ++
 ...ID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md |   3 +
 ...-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json |  26 ++
 ...ID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md |  25 ++
 ...-30D9F5F5-7572-4440-8B31-9372D7CE352D.json |  26 ++
 ...ID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md |   8 +
 ...-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json |  26 ++
 ...ID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md |   3 +
 ...-334FA46B-AE38-41A7-BACC-8F8384C5D010.json |  26 ++
 ...ID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md |   6 +
 ...-33F3509A-A175-4204-A1A8-F3699338CAC5.json |  26 ++
 ...ID-33F3509A-A175-4204-A1A8-F3699338CAC5.md |  96 +++++++
 ...-34291BF2-6D39-46FD-B18A-338089CAF11E.json |  26 ++
 ...ID-34291BF2-6D39-46FD-B18A-338089CAF11E.md |   3 +
 ...-34B1DB42-8ADD-45C4-B945-137EB77810B6.json |  26 ++
 ...ID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md |  38 +++
 ...-35419962-0058-4856-A6BD-F4923FD0F044.json |  26 ++
 ...ID-35419962-0058-4856-A6BD-F4923FD0F044.md |   3 +
 ...-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json |  26 ++
 ...ID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md |  74 +++++
 ...-3702D75B-9505-40D0-B220-7739F5F72760.json |  26 ++
 ...ID-3702D75B-9505-40D0-B220-7739F5F72760.md |  47 ++++
 ...-371A58A1-F821-449C-8D2D-EC2657C13B56.json |  26 ++
 ...ID-371A58A1-F821-449C-8D2D-EC2657C13B56.md |   9 +
 ...-37CA1665-B331-452A-AA3D-59608D85F006.json |  26 ++
 ...ID-37CA1665-B331-452A-AA3D-59608D85F006.md |   1 +
 ...-392743FA-D99D-4995-A8F6-3E5541271263.json |  26 ++
 ...ID-392743FA-D99D-4995-A8F6-3E5541271263.md |  21 ++
 ...-397630C5-C2CE-4E35-A45D-0228C8F70867.json |  26 ++
 ...ID-397630C5-C2CE-4E35-A45D-0228C8F70867.md |  10 +
 ...-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json |  26 ++
 ...ID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md |   9 +
 ...-3A5066B9-898A-4673-A713-C3E41D502742.json |  26 ++
 ...ID-3A5066B9-898A-4673-A713-C3E41D502742.md |  11 +
 ...-3A5117DE-E11D-41D0-A016-A68154A90DCA.json |  26 ++
 ...ID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md |   9 +
 ...-3A627DBF-D797-42A2-A9AC-AAC321376068.json |  26 ++
 ...ID-3A627DBF-D797-42A2-A9AC-AAC321376068.md |  25 ++
 ...-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json |  26 ++
 ...ID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md |   3 +
 ...-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json |  26 ++
 ...ID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md |  36 +++
 ...-3B34F036-4C25-4058-B5F4-5340545BE821.json |  26 ++
 ...ID-3B34F036-4C25-4058-B5F4-5340545BE821.md |   9 +
 ...-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json |  26 ++
 ...ID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md |  20 ++
 ...-3D27BE17-47C9-476C-AD13-DD516697F862.json |  26 ++
 ...ID-3D27BE17-47C9-476C-AD13-DD516697F862.md |  12 +
 ...-3E03B539-B71C-4D2E-A218-23713D723408.json |  26 ++
 ...ID-3E03B539-B71C-4D2E-A218-23713D723408.md |   5 +
 ...-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json |  26 ++
 ...ID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md |  30 ++
 ...-40300B80-D69C-450B-9848-7A21A3141005.json |  26 ++
 ...ID-40300B80-D69C-450B-9848-7A21A3141005.md |  12 +
 ...-429877DA-255E-41FC-86B6-E7069B0EE7A6.json |  26 ++
 ...ID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md |  63 +++++
 ...-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json |  26 ++
 ...ID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md |   7 +
 ...-443DD312-C75F-4267-A17E-FEDCFD7335FB.json |  26 ++
 ...ID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md |   6 +
 ...-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json |  26 ++
 ...ID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md |   9 +
 ...-44974486-3ED4-4C5C-849B-8746A4899889.json |  26 ++
 ...ID-44974486-3ED4-4C5C-849B-8746A4899889.md |   9 +
 ...-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json |  26 ++
 ...ID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md |  10 +
 ...-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json |  26 ++
 ...ID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md |   9 +
 ...-45B4119E-416A-43FA-B2A0-C7D52D028326.json |  26 ++
 ...ID-45B4119E-416A-43FA-B2A0-C7D52D028326.md |  15 +
 ...-45D07344-870A-4CB7-84D9-4AF78C151B70.json |  26 ++
 ...ID-45D07344-870A-4CB7-84D9-4AF78C151B70.md |  21 ++
 ...-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json |  26 ++
 ...ID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md |   5 +
 ...-46D03C40-2146-434A-B75A-12BBBDB56FF3.json |  26 ++
 ...ID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md |  31 +++
 ...-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json |  26 ++
 ...ID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md |  23 ++
 ...-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json |  26 ++
 ...ID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md |  12 +
 ...-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json |  26 ++
 ...ID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md |  34 +++
 ...-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json |  26 ++
 ...ID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md |   5 +
 ...-4AE72311-7C7E-4384-A7E1-A23048B29C40.json |  26 ++
 ...ID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md |   3 +
 ...-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json |  26 ++
 ...ID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md |  12 +
 ...-4CCF6004-31A7-4B35-996D-5E12877CB443.json |  26 ++
 ...ID-4CCF6004-31A7-4B35-996D-5E12877CB443.md |   3 +
 ...-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json |  26 ++
 ...ID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md |   7 +
 ...-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json |  26 ++
 ...ID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md |  11 +
 ...-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json |  26 ++
 ...ID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md |   3 +
 ...-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json |  26 ++
 ...ID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md |  19 ++
 ...-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json |  26 ++
 ...ID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md |  16 ++
 ...-4F822F1E-105F-48CD-83A7-3BB562A5B147.json |  26 ++
 ...ID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md |   3 +
 ...-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json |  26 ++
 ...ID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md |   4 +
 ...-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json |  26 ++
 ...ID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md |  10 +
 ...-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json |  26 ++
 ...ID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md |  13 +
 ...-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json |  26 ++
 ...ID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md |  65 +++++
 ...-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json |  26 ++
 ...ID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md |   5 +
 ...-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json |  26 ++
 ...ID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md |  42 +++
 ...-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json |  26 ++
 ...ID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md |   8 +
 ...-5504862E-8120-469D-8708-2290772E5585.json |  26 ++
 ...ID-5504862E-8120-469D-8708-2290772E5585.md |  13 +
 ...-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json |  26 ++
 ...ID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md |  80 ++++++
 ...-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json |  26 ++
 ...ID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md |   5 +
 ...-5571B267-5385-4EEC-A400-FD23FD4B239C.json |  26 ++
 ...ID-5571B267-5385-4EEC-A400-FD23FD4B239C.md |   3 +
 ...-55BA17AE-7F27-4832-BADC-D76B073635C6.json |  26 ++
 ...ID-55BA17AE-7F27-4832-BADC-D76B073635C6.md |   4 +
 ...-55E760C3-2167-4A03-88ED-D9078C196D74.json |  26 ++
 ...ID-55E760C3-2167-4A03-88ED-D9078C196D74.md |   8 +
 ...-5663C34A-23E8-42CA-B7BF-5A79A0070456.json |  26 ++
 ...ID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md |   7 +
 ...-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json |  26 ++
 ...ID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md |   8 +
 ...-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json |  26 ++
 ...ID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md |  13 +
 ...-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json |  26 ++
 ...ID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md |   8 +
 ...-580E4107-827A-43F6-888D-5CDD41EB42E0.json |  26 ++
 ...ID-580E4107-827A-43F6-888D-5CDD41EB42E0.md |  25 ++
 ...-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json |  26 ++
 ...ID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md |  23 ++
 ...-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json |  26 ++
 ...ID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md |   8 +
 ...-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json |  26 ++
 ...ID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md |   7 +
 ...-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json |  26 ++
 ...ID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md |  53 ++++
 ...-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json |  26 ++
 ...ID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md |   3 +
 ...-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json |  26 ++
 ...ID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md |  20 ++
 ...-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json |  26 ++
 ...ID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md |  13 +
 ...-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json |  26 ++
 ...ID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md |   7 +
 ...-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json |  26 ++
 ...ID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md |  11 +
 ...-5E442E1F-D996-4863-BA47-1EE76E07A12C.json |  26 ++
 ...ID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md |  29 ++
 ...-5F75E5AF-90D3-4F85-B937-F98415300AC5.json |  26 ++
 ...ID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md |  20 ++
 ...-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json |  26 ++
 ...ID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md |   3 +
 ...-61053EC5-4910-454F-8B71-6B06408A6451.json |  26 ++
 ...ID-61053EC5-4910-454F-8B71-6B06408A6451.md |   8 +
 ...-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json |  26 ++
 ...ID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md |  49 ++++
 ...-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json |  26 ++
 ...ID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md |   3 +
 ...-62D603EE-56F3-478D-9625-2FC3B6F189E8.json |  26 ++
 ...ID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md |  25 ++
 ...-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json |  26 ++
 ...ID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md |  23 ++
 ...-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json |  26 ++
 ...ID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md |   9 +
 ...-634760AA-7E46-42A7-AD08-85CCE4656873.json |  26 ++
 ...ID-634760AA-7E46-42A7-AD08-85CCE4656873.md |  36 +++
 ...-63ADF495-37BF-424E-85F4-614EE91DA301.json |  26 ++
 ...ID-63ADF495-37BF-424E-85F4-614EE91DA301.md |  12 +
 ...-63B0F6F4-69CA-40C1-997E-949DD702C77E.json |  26 ++
 ...ID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md |   3 +
 ...-64001B38-0509-46D5-854E-3A8500798DEE.json |  26 ++
 ...ID-64001B38-0509-46D5-854E-3A8500798DEE.md |  13 +
 ...-650706CA-915E-4239-9D69-35902E82B60E.json |  26 ++
 ...ID-650706CA-915E-4239-9D69-35902E82B60E.md |   9 +
 ...-6549D43B-D0BB-4416-9771-AF11F387B629.json |  26 ++
 ...ID-6549D43B-D0BB-4416-9771-AF11F387B629.md |   7 +
 ...-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json |  26 ++
 ...ID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md |  14 +
 ...-69626666-7280-4AF5-9871-FA2D82CED05E.json |  26 ++
 ...ID-69626666-7280-4AF5-9871-FA2D82CED05E.md |  20 ++
 ...-69CE737F-F442-4C04-8B1A-8881930B69AE.json |  26 ++
 ...ID-69CE737F-F442-4C04-8B1A-8881930B69AE.md |  17 ++
 ...-6B35AE72-3D19-447A-A19D-D96DDD769B67.json |  26 ++
 ...ID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md |  84 ++++++
 ...-6B80D87B-8461-414D-9172-07E68896EB06.json |  26 ++
 ...ID-6B80D87B-8461-414D-9172-07E68896EB06.md |  20 ++
 ...-6B9A77F8-731B-43A1-92C8-0163E20D8048.json |  26 ++
 ...ID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md |  28 ++
 ...-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json |  26 ++
 ...ID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md |   3 +
 ...-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json |  26 ++
 ...ID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md |  25 ++
 ...-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json |  26 ++
 ...ID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md |  18 ++
 ...-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json |  26 ++
 ...ID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md |  11 +
 ...-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json |  26 ++
 ...ID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md |  12 +
 ...-712F2BB4-F856-419F-BB88-2E137DD46F72.json |  26 ++
 ...ID-712F2BB4-F856-419F-BB88-2E137DD46F72.md |  11 +
 ...-7138E486-AE62-4778-9358-F098126785A5.json |  26 ++
 ...ID-7138E486-AE62-4778-9358-F098126785A5.md |   5 +
 ...-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json |  26 ++
 ...ID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md |  20 ++
 ...-74590319-12A6-4101-9043-8DDB56BB0720.json |  26 ++
 ...ID-74590319-12A6-4101-9043-8DDB56BB0720.md |  18 ++
 ...-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json |  26 ++
 ...ID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md |  13 +
 ...-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json |  26 ++
 ...ID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md |   6 +
 ...-76B17464-6C1D-468E-B6D2-93ECF87E2289.json |  26 ++
 ...ID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md |  18 ++
 ...-76B546AD-121A-4C3A-B42C-D642C8624A3C.json |  26 ++
 ...ID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md |   7 +
 ...-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json |  26 ++
 ...ID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md |   8 +
 ...-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json |  26 ++
 ...ID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md |  14 +
 ...-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json |  26 ++
 ...ID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md |  22 ++
 ...-7C6154EA-09BC-4E68-8BAB-D784F0582440.json |  26 ++
 ...ID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md |   7 +
 ...-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json |  26 ++
 ...ID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md |  42 +++
 ...-7D80BD98-F855-4690-AC44-6BA192EC1E53.json |  26 ++
 ...ID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md |  13 +
 ...-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json |  26 ++
 ...ID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md |   9 +
 ...-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json |  26 ++
 ...ID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md |  35 +++
 ...-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json |  26 ++
 ...ID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md |   3 +
 ...-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json |  26 ++
 ...ID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md |  12 +
 ...-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json |  26 ++
 ...ID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md |  28 ++
 ...-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json |  26 ++
 ...ID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md |   9 +
 ...-83AF39C3-5542-4739-B9ED-C867C472CDCE.json |  26 ++
 ...ID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md |  11 +
 ...-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json |  26 ++
 ...ID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md |  10 +
 ...-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json |  26 ++
 ...ID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md |  15 +
 ...-87FC621D-8EDE-48DE-901B-00058C07E62D.json |  26 ++
 ...ID-87FC621D-8EDE-48DE-901B-00058C07E62D.md |  27 ++
 ...-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json |  26 ++
 ...ID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md |   5 +
 ...-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json |  26 ++
 ...ID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md |  29 ++
 ...-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json |  26 ++
 ...ID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md |  81 ++++++
 ...-8AFBB53F-6749-4E7E-AAF2-310849586320.json |  26 ++
 ...ID-8AFBB53F-6749-4E7E-AAF2-310849586320.md |   7 +
 ...-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json |  26 ++
 ...ID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md |   3 +
 ...-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json |  26 ++
 ...ID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md |  44 +++
 ...-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json |  26 ++
 ...ID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md |  12 +
 ...-8E19FA4E-4408-4784-A629-DD936DEEBA26.json |  26 ++
 ...ID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md |   3 +
 ...-8EC2E33D-2086-4253-BF7D-D953052774A0.json |  26 ++
 ...ID-8EC2E33D-2086-4253-BF7D-D953052774A0.md |   7 +
 ...-91D3F799-4C17-4008-B605-FEE370890091.json |  26 ++
 ...ID-91D3F799-4C17-4008-B605-FEE370890091.md |   3 +
 ...-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json |  26 ++
 ...ID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md |  20 ++
 ...-94133965-3802-4768-A71D-2AD5F8402BD9.json |  26 ++
 ...ID-94133965-3802-4768-A71D-2AD5F8402BD9.md |  13 +
 ...-949DC89F-26C2-4028-9A1F-2616FB466736.json |  26 ++
 ...ID-949DC89F-26C2-4028-9A1F-2616FB466736.md |  13 +
 ...-953F9E2E-D9DD-4469-96EE-A288371FE36E.json |  26 ++
 ...ID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md |  82 ++++++
 ...-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json |  26 ++
 ...ID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md |   7 +
 ...-960DA835-B984-49FB-80DE-EE6D38D42EDD.json |  26 ++
 ...ID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md |  13 +
 ...-967D7E5A-D701-4580-BFCB-0EB3588D2725.json |  26 ++
 ...ID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md |   3 +
 ...-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json |  26 ++
 ...ID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md |  13 +
 ...-97951AE9-439B-4779-823D-E118E1CB08D3.json |  26 ++
 ...ID-97951AE9-439B-4779-823D-E118E1CB08D3.md |   9 +
 ...-9886AD4A-5C64-4E09-A106-B14419362757.json |  26 ++
 ...ID-9886AD4A-5C64-4E09-A106-B14419362757.md |  21 ++
 ...-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json |  26 ++
 ...ID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md |   5 +
 ...-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json |  26 ++
 ...ID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md |  17 ++
 ...-9969BD6B-639D-4633-B825-79578464E8E6.json |  26 ++
 ...ID-9969BD6B-639D-4633-B825-79578464E8E6.md |   8 +
 ...-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json |  26 ++
 ...ID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md |  11 +
 ...-9AA16B50-F8A4-443B-AD6C-6E018596459B.json |  26 ++
 ...ID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md |   5 +
 ...-9BDE2563-18FC-49B0-83D7-47F57E044D97.json |  26 ++
 ...ID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md |   7 +
 ...-9C1E97D3-4285-4F70-ACAF-A56767901C74.json |  26 ++
 ...ID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md |  15 +
 ...-9CB7CEE4-C724-448E-822A-75F155B88EAC.json |  26 ++
 ...ID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md |  11 +
 ...-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json |  26 ++
 ...ID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md |   6 +
 ...-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json |  26 ++
 ...ID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md |   8 +
 ...-9DA38943-BF95-446D-AB09-32323160D51B.json |  26 ++
 ...ID-9DA38943-BF95-446D-AB09-32323160D51B.md |  53 ++++
 ...-9DA820B7-7477-4980-848B-7161BDB5C43E.json |  26 ++
 ...ID-9DA820B7-7477-4980-848B-7161BDB5C43E.md |   9 +
 ...-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json |  26 ++
 ...ID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md |   4 +
 ...-9EC70919-852C-427E-ACDF-D59319D72468.json |  26 ++
 ...ID-9EC70919-852C-427E-ACDF-D59319D72468.md |  24 ++
 ...-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json |  26 ++
 ...ID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md |   6 +
 ...-9FC58214-95C7-4690-91DA-3185640E3712.json |  26 ++
 ...ID-9FC58214-95C7-4690-91DA-3185640E3712.md |   7 +
 ...-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json |  26 ++
 ...ID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md |  26 ++
 ...-9FF6393B-3B5D-4409-B0BC-461062C5F766.json |  26 ++
 ...ID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md |   3 +
 ...-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json |  26 ++
 ...ID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md |  35 +++
 ...-A1E79BA5-CE31-4357-878E-11464E03158C.json |  26 ++
 ...ID-A1E79BA5-CE31-4357-878E-11464E03158C.md |   6 +
 ...-A2A63203-21AB-4358-8706-62DF795EAE62.json |  26 ++
 ...ID-A2A63203-21AB-4358-8706-62DF795EAE62.md |  10 +
 ...-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json |  26 ++
 ...ID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md |   3 +
 ...-A391DC49-6523-4517-9AE1-F2E78CE91411.json |  26 ++
 ...ID-A391DC49-6523-4517-9AE1-F2E78CE91411.md |  11 +
 ...-A3EE4127-5F12-4F3A-89EA-138882DA237B.json |  26 ++
 ...ID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md |   9 +
 ...-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json |  21 ++
 ...ID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md |  27 ++
 ...-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json |  26 ++
 ...ID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md |  12 +
 ...-A5F5433C-0F21-4877-BFC6-522D421A1842.json |  26 ++
 ...ID-A5F5433C-0F21-4877-BFC6-522D421A1842.md |   3 +
 ...-A742B359-6C9C-4BC0-AA52-30189D93AA33.json |  26 ++
 ...ID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md |   7 +
 ...-A745B955-2E59-4769-AB47-E32098A84653.json |  26 ++
 ...ID-A745B955-2E59-4769-AB47-E32098A84653.md |   7 +
 ...-A7CB5566-0283-4C67-BA27-02852732D7C3.json |  26 ++
 ...ID-A7CB5566-0283-4C67-BA27-02852732D7C3.md |  69 +++++
 ...-AAD13737-533B-491F-A155-DDB027057157.json |  26 ++
 ...ID-AAD13737-533B-491F-A155-DDB027057157.md |  14 +
 ...-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json |  31 +++
 ...ID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md |  19 ++
 ...-AB938CF2-D0FE-4516-931D-0238D0662B84.json |  26 ++
 ...ID-AB938CF2-D0FE-4516-931D-0238D0662B84.md |   8 +
 ...-AC33B458-3F39-4BA6-A242-E00B613C60DA.json |  31 +++
 ...ID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md |  17 ++
 ...-AC461BBD-647D-447D-9307-218A41CE368B.json |  26 ++
 ...ID-AC461BBD-647D-447D-9307-218A41CE368B.md |  11 +
 ...-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json |  26 ++
 ...ID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md |   7 +
 ...-ADF74748-AB0E-42F4-BB23-79C5B079A778.json |  26 ++
 ...ID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md |  77 ++++++
 ...-AE27985B-5909-407F-A105-5B0574715D13.json |  26 ++
 ...ID-AE27985B-5909-407F-A105-5B0574715D13.md |   7 +
 ...-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json |  26 ++
 ...ID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md |  38 +++
 ...-AFF4C609-07DB-429C-B7A7-82F9568D6297.json |  26 ++
 ...ID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md |   3 +
 ...-B3241978-4E00-4630-A8AB-E597193E51E2.json |  26 ++
 ...ID-B3241978-4E00-4630-A8AB-E597193E51E2.md |  38 +++
 ...-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json |  26 ++
 ...ID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md |   5 +
 ...-B5387FE3-B36D-4924-B168-329B6E41D811.json |  26 ++
 ...ID-B5387FE3-B36D-4924-B168-329B6E41D811.md |   3 +
 ...-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json |  26 ++
 ...ID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md |  18 ++
 ...-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json |  26 ++
 ...ID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md |   7 +
 ...-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json |  26 ++
 ...ID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md |  14 +
 ...-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json |  26 ++
 ...ID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md |   9 +
 ...-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json |  26 ++
 ...ID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md |  23 ++
 ...-B6F5194C-290E-464F-A718-232984A6E8B5.json |  26 ++
 ...ID-B6F5194C-290E-464F-A718-232984A6E8B5.md |   6 +
 ...-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json |  21 ++
 ...ID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md |  17 ++
 ...-B82658C8-6002-424B-B257-D52A7D603BC3.json |  26 ++
 ...ID-B82658C8-6002-424B-B257-D52A7D603BC3.md |   7 +
 ...-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json |  26 ++
 ...ID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md |   9 +
 ...-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json |  26 ++
 ...ID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md |  10 +
 ...-B8FB507C-D7BB-462A-847F-E5A4B708E142.json |  26 ++
 ...ID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md |   4 +
 ...-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json |  26 ++
 ...ID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md |   1 +
 ...-B94BC2CB-8504-41C6-8848-512529EEE941.json |  26 ++
 ...ID-B94BC2CB-8504-41C6-8848-512529EEE941.md |   4 +
 ...-BB270862-D56D-4B6F-86B7-030ED273E907.json |  26 ++
 ...ID-BB270862-D56D-4B6F-86B7-030ED273E907.md |   3 +
 ...-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json |  26 ++
 ...ID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md | 256 ++++++++++++++++++
 ...-BC17942D-DE0B-4244-900F-DE38D31A09EC.json |  26 ++
 ...ID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md |   6 +
 ...-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json |  26 ++
 ...ID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md |  17 ++
 ...-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json |  26 ++
 ...ID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md |  15 +
 ...-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json |  26 ++
 ...ID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md |  52 ++++
 ...-BD0C3274-B70C-437A-B89C-C77A703FFD53.json |  26 ++
 ...ID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md |  28 ++
 ...-BE852729-65DF-4377-9A64-F05D47CD9D49.json |  26 ++
 ...ID-BE852729-65DF-4377-9A64-F05D47CD9D49.md |  25 ++
 ...-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json |  26 ++
 ...ID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md |  13 +
 ...-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json |  26 ++
 ...ID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md |  10 +
 ...-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json |  26 ++
 ...ID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md |  53 ++++
 ...-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json |  26 ++
 ...ID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md |   6 +
 ...-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json |  26 ++
 ...ID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md |  12 +
 ...-C7399A7B-40C6-4DCA-8A92-EAB777739496.json |  26 ++
 ...ID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md |  25 ++
 ...-C7747582-1A56-458D-B985-DDF459F1CE7C.json |  26 ++
 ...ID-C7747582-1A56-458D-B985-DDF459F1CE7C.md |  73 +++++
 ...-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json |  26 ++
 ...ID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md |   9 +
 ...-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json |  26 ++
 ...ID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md |   4 +
 ...-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json |  26 ++
 ...ID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md |  10 +
 ...-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json |  26 ++
 ...ID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md |   5 +
 ...-CA181AC5-CA1D-47ED-9D44-008642C89290.json |  26 ++
 ...ID-CA181AC5-CA1D-47ED-9D44-008642C89290.md |  97 +++++++
 ...-CA806876-1093-4A39-BE62-439C4802A915.json |  26 ++
 ...ID-CA806876-1093-4A39-BE62-439C4802A915.md |  17 ++
 ...-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json |  26 ++
 ...ID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md |   3 +
 ...-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json |  26 ++
 ...ID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md |   7 +
 ...-CD00669C-741C-480C-B444-67F079061438.json |  26 ++
 ...ID-CD00669C-741C-480C-B444-67F079061438.md |  11 +
 ...-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json |  26 ++
 ...ID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md |   8 +
 ...-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json |  26 ++
 ...ID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md |  76 ++++++
 ...-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json |  26 ++
 ...ID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md |  24 ++
 ...-CDB73B95-18B8-4A10-A09C-4176EE11497D.json |  26 ++
 ...ID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md |  15 +
 ...-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json |  26 ++
 ...ID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md |  11 +
 ...-CFE82665-23A3-49F2-9202-1C2A720CC64D.json |  26 ++
 ...ID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md |  12 +
 ...-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json |  26 ++
 ...ID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md |  26 ++
 ...-D280323C-DF16-4F69-86CA-111B7CFCA25E.json |  26 ++
 ...ID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md |  21 ++
 ...-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json |  26 ++
 ...ID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md | 106 ++++++++
 ...-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json |  26 ++
 ...ID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md |  15 +
 ...-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json |  26 ++
 ...ID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md |  59 ++++
 ...-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json |  26 ++
 ...ID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md |   9 +
 ...-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json |  26 ++
 ...ID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md |  11 +
 ...-D647F00D-6B45-4E18-B442-14835847EFA7.json |  26 ++
 ...ID-D647F00D-6B45-4E18-B442-14835847EFA7.md |  23 ++
 ...-D6B5BF84-8D86-4215-94FF-119D52387FDB.json |  26 ++
 ...ID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md |  14 +
 ...-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json |  26 ++
 ...ID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md |   5 +
 ...-D7A36529-C624-486D-8C0E-FA69A4DC4014.json |  26 ++
 ...ID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md |   5 +
 ...-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json |  26 ++
 ...ID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md |   5 +
 ...-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json |  26 ++
 ...ID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md |   8 +
 ...-DA1898BD-3EB1-432A-BD34-373B29B05B89.json |  26 ++
 ...ID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md |   6 +
 ...-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json |  26 ++
 ...ID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md |   3 +
 ...-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json |  26 ++
 ...ID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md |  23 ++
 ...-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json |  26 ++
 ...ID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md |   3 +
 ...-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json |  26 ++
 ...ID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md |  14 +
 ...-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json |  26 ++
 ...ID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md |  23 ++
 ...-DF02CF23-8387-4D00-87AF-5F2054075F18.json |  26 ++
 ...ID-DF02CF23-8387-4D00-87AF-5F2054075F18.md |  11 +
 ...-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json |  26 ++
 ...ID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md |  12 +
 ...-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json |  26 ++
 ...ID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md |  28 ++
 ...-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json |  26 ++
 ...ID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md |  16 ++
 ...-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json |  26 ++
 ...ID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md |  17 ++
 ...-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json |  26 ++
 ...ID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md |  15 +
 ...-E04CE9DF-E832-41CB-B559-1800B7943A2F.json |  26 ++
 ...ID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md |  20 ++
 ...-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json |  26 ++
 ...ID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md |  97 +++++++
 ...-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json |  26 ++
 ...ID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md |   5 +
 ...-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json |  26 ++
 ...ID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md |  31 +++
 ...-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json |  26 ++
 ...ID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md |  77 ++++++
 ...-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json |  26 ++
 ...ID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md |   3 +
 ...-E32D92B2-8DB3-42C3-982C-7E9D88231069.json |  26 ++
 ...ID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md |  19 ++
 ...-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json |  26 ++
 ...ID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md |  15 +
 ...-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json |  26 ++
 ...ID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md |   6 +
 ...-E4F3DF9C-1873-4893-BE81-D85015D67F19.json |  26 ++
 ...ID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md |   7 +
 ...-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json |  26 ++
 ...ID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md |  18 ++
 ...-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json |  26 ++
 ...ID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md |  48 ++++
 ...-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json |  26 ++
 ...ID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md |   7 +
 ...-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json |  26 ++
 ...ID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md |  11 +
 ...-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json |  26 ++
 ...ID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md |   7 +
 ...-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json |  26 ++
 ...ID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md |   3 +
 ...-EB317455-AAFD-4465-8961-6E7C13B48CCB.json |  26 ++
 ...ID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md |  26 ++
 ...-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json |  26 ++
 ...ID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md |  13 +
 ...-EC91E230-8323-4710-9A47-D57A15BE71AA.json |  26 ++
 ...ID-EC91E230-8323-4710-9A47-D57A15BE71AA.md |   8 +
 ...-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json |  26 ++
 ...ID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md | 109 ++++++++
 ...-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json |  26 ++
 ...ID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md |  11 +
 ...-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json |  26 ++
 ...ID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md |   8 +
 ...-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json |  26 ++
 ...ID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md |  24 ++
 ...-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json |  26 ++
 ...ID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md |  31 +++
 ...-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json |  26 ++
 ...ID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md |  13 +
 ...-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json |  26 ++
 ...ID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md |   3 +
 ...-F25A1489-CFA2-4B4A-9340-1C278198A951.json |  26 ++
 ...ID-F25A1489-CFA2-4B4A-9340-1C278198A951.md |   8 +
 ...-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json |  26 ++
 ...ID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md |  29 ++
 ...-F3650ED7-96D8-4542-8D04-ED3527A9C565.json |  26 ++
 ...ID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md |   7 +
 ...-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json |  26 ++
 ...ID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md |  14 +
 ...-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json |  26 ++
 ...ID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md |  18 ++
 ...-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json |  26 ++
 ...ID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md |  18 ++
 ...-F5A818DC-E3A9-4020-84FC-B087B2C14158.json |  26 ++
 ...ID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md |  29 ++
 ...-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json |  26 ++
 ...ID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md |   6 +
 ...-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json |  26 ++
 ...ID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md | 108 ++++++++
 ...-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json |  26 ++
 ...ID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md |  14 +
 ...-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json |  26 ++
 ...ID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md |   8 +
 ...-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json |  26 ++
 ...ID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md |  12 +
 ...-FA7264AB-8547-45E3-8752-8D47B6708F86.json |  26 ++
 ...ID-FA7264AB-8547-45E3-8752-8D47B6708F86.md |  20 ++
 ...-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json |  26 ++
 ...ID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md |  11 +
 ...-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json |  26 ++
 ...ID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md |  21 ++
 ...-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json |  26 ++
 ...ID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md |  14 +
 ...-FB7D15CC-A606-42DC-9DBF-27778D20282D.json |  26 ++
 ...ID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md |  43 +++
 ...-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json |  26 ++
 ...ID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md |  94 +++++++
 ...-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json |  26 ++
 ...ID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md |   3 +
 ...-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json |  26 ++
 ...ID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md |   8 +
 ...-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json |  26 ++
 ...ID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md |   3 +
 ...-FDC357F5-AFCA-4175-ADF4-43928922C384.json |  26 ++
 ...ID-FDC357F5-AFCA-4175-ADF4-43928922C384.md |  13 +
 ...-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json |  26 ++
 ...ID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md |  13 +
 2323 files changed, 51385 insertions(+)
 create mode 100644 corpus/.digest/history.jsonl
 create mode 100644 corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.md
 create mode 100644 corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.json
 create mode 100644 corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.md
 create mode 100644 corpus/hvm_release_notes_8_1_0/sd00007497en_us.json
 create mode 100644 corpus/hvm_release_notes_8_1_0/sd00007497en_us.md
 create mode 100644 corpus/hvm_release_notes_8_1_1/sd00007609en_us.json
 create mode 100644 corpus/hvm_release_notes_8_1_1/sd00007609en_us.md
 create mode 100644 corpus/hvm_release_notes_8_1_2/sd00007734en_us.json
 create mode 100644 corpus/hvm_release_notes_8_1_2/sd00007734en_us.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
 create mode 100644 corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
 create mode 100644 corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
 create mode 100644 corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md

diff --git a/corpus/.digest/history.jsonl b/corpus/.digest/history.jsonl
new file mode 100644
index 0000000..e69de29
diff --git a/corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.json b/corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.json
new file mode 100644
index 0000000..7e55df6
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA",
+  "title": "VME Manager sizing",
+  "ordinal": 5,
+  "parent_title": "Planning and preparation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.md b/corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.md
new file mode 100644
index 0000000..29691e1
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.md
@@ -0,0 +1,32 @@
+# VME Manager sizing
+
+VM Essentials manager can be deployed via the console as one of three predefined sizes: small, medium, or large. The greater the capacity, the greater amount of resources and cluster sizes the VM Essentials manager can manage. For large production environments, it’s recommended you select a large manager.
+
+**Manager VM sizing options**
+
+|  |  |  |  |
+| --- | --- | --- | --- |
+| Size | vCPUs | Memory | Use Case |
+| Small | 2 | 12GB | Testing environments, small clusters |
+| Medium | 4 | 16GB | Standard production, moderate workloads |
+| Large | 4 | 32GB | Large production, high-performance environments |
+
+**Performance guidelines**
+
+**Small configuration:**
+
+- Maximum clusters: Up to One (1) HVM cluster
+- Concurrent operations: Limited provisioning
+- Recommended for: Development, testing, proof-of-concept
+
+**Medium configuration:**
+
+- Maximum clusters: Up to Three (3) HVM clusters with moderate VM density
+- Concurrent operations: Standard provisioning and monitoring
+- Recommended for: Production environments, typical enterprise use
+
+**Large configuration:**
+
+- Maximum clusters: Up to Ten (10) HVM clusters with high VM density
+- Concurrent operations: High-volume provisioning, extensive monitoring
+- Recommended for: Large enterprises, service providers, intensive workloads
diff --git a/corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.json b/corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.json
new file mode 100644
index 0000000..a055a4d
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-28F18596-4902-4CD1-83F3-1411430C5534",
+  "title": "Installing HVM OS on host servers",
+  "ordinal": 16,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.md b/corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.md
new file mode 100644
index 0000000..fd9bf97
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-28F18596-4902-4CD1-83F3-1411430C5534.md
@@ -0,0 +1,125 @@
+# Installing HVM OS on host servers
+
+## Prerequisites
+
+Ensure that before you download the **HVM\_Install\_\*\*\*\*\*\*.iso**, you have the required license.
+
+## About this task
+
+Use the HPE-Provided HVM OS ISO to install your hosts. Download **HVM\_Install\_\*\*\*\*\*\*.iso** from [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/product-details/HPE_VME_EVAL/-/sw360_hpe_internal).
+
+The following example considers a simple active-backup network bond which does not require any advanced configurations on the network switches. It also assumes that the network ports are trunk ports and require the VLANs to be tagged at the host.
+
+## Procedure
+
+1. Mount the HVM OS Install ISO to the DVD drive device on the host machine. You can also mount the ISO using the server's Out of Band Management console.
+2. Boot the server from the DVD drive.
+
+   NOTE
+
+   To install the HVM OS, you must select the uploaded ISO image to boot the system. This will involve updating the boot order to select the device with the ISO mounted before other devices or manually selecting a boot device during the boot sequence. The exact steps to do this will vary depending on the specific manufacturer and system. Refer your system documentation for specific instructions.
+3. Select HVM Install 24.04 when the boot menu appears.
+
+   ![Installing HVM OS-1](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-55B1F206-3935-4A1F-B029-D3E86E5A6E4F-high.png)
+4. Proceed through the installer.
+
+   NOTE
+
+   Use your keyboard’s **Tab** key to navigate the installer TUI.
+5. In the Network configuration screen, create your network bond and add a VLAN.
+   1. Select **Create bond**.
+
+      ![Installing HVM OS](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-B82526E2-BF5C-46EA-9635-30F0949E878A-high.png)
+
+      NOTE
+
+      For details on Bonds, see [Example Network Configurations](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.html).
+   2. Select the network interfaces to be added to the bond.
+
+      ![Installing HVM OS-2](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-963FD78A-8EEA-442E-BD57-B140ABFB35D7-high.png)
+   3. Under Bond mode, select **active-backup**.
+
+      ![Installing HVM OS-3](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-C3322DD0-DB13-44D4-862D-A0ECEE4D28AD-high.png)
+   4. Select **[Create]**
+
+      ![Installing HVM OS-4](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-5FF65520-83FB-4E78-8C09-EE501F14D959-high.png)
+   5. Your bond will show in the interface selection screen.
+
+      ![Installing HVM OS-5](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-DFFC4B9B-C9B1-4102-8D8C-8EB529229D6B-high.png)
+
+      NOTE
+
+      To simplify future configurations, it is highly recommended to create a bond even if only one interface will be used.
+   6. Select your bond to configure it.
+
+      - If your management network needs to be on a tagged VLAN, select **Add a VLAN tag**.
+
+        ![Installing HVM OS-6](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-8A7E8E38-8EDF-4B58-9014-D65932118707-high.png)
+      - Add your Management VLAN ID.
+
+        ![Installing HVM OS-7](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-69B22D67-F2C7-40DB-98C6-4367AEA6054B-high.png)
+      - A new interface with your VLAN ID will show, select it and select **Edit IPv4**.
+
+        ![Installing HVM OS-8](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-83ABEE67-E468-4E1C-8B43-593903A1DBE8-high.png)
+
+        NOTE
+
+        A static IP is required for successful configuration later on.
+      - Select **Manual** for the IPv4 Method.
+
+        ![Installing HVM OS-9](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-CB9620EE-A255-4DD2-950A-CEF53A0F5FB5-high.png)
+      - Enter your network configuration.
+
+        ![Installing HVM OS-10](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-A4BD837D-20D9-48EF-83CE-4F1EB5633BAE-high.png)
+      - Select **[Done]** at the bottom.
+
+        ![Installing HVM OS-11](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-B90A5368-4A3A-4445-8550-5208E77CDE8A-high.png)
+6. Next configure the Storage.
+   1. Leave the default selection to **Use an entire disk** and **Set up this disk as an LVM group** selected and select **[Done]**.
+
+      ![Installing HVM OS-12](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-706707BB-20FE-4672-A96C-2DC911D147C3-high.png)
+
+      NOTE
+
+      The installer selects the disk automatically, check it selected the right one and change it if necessary.
+   2. In the **Guided storage configuration** screen, under **Used Devices**, select **ubuntu-lv**, open the **Options** menu, and select **Edit**.
+
+      ![Installing HVM OS-13](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-E724E0CB-CD93-4940-9C08-532231408B06-high.png)
+   3. Modify the Size to match the maximum disk size, then **Save**.
+
+      ![Installing HVM OS-14](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-D81D43F8-1849-4EB2-B0BA-3462EAF96964-high.png)
+   4. When you are back in the Storage Configuration page, select **Done**.
+   5. On the Confirm Destructive Action prompt, select **Continue**.
+
+      ![Installing HVM OS-15](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-E8B1058C-CEB3-4D22-938C-FC1E3C7D8B8D-high.png)
+
+      NOTE
+
+      This prompt might not appear at this stage.
+7. In the Proxy Configuration screen, configure proxy settings if your environment requires a proxy. Enter the proxy details when prompted during the installation. If a proxy is not required, leave the Proxy address field blank and continue with the installation.
+8. Next, in the **Profile configuration** screen, enter the required details and select **Done**.
+
+   ![Installing HVM OS-16](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-731CC106-A302-4E85-BE21-0943809E4F30-high.png)
+
+   1. The system proceeds with the installation process.
+   2. When the process finishes, select **[Reboot Now]**.
+
+      ![Installing HVM OS-17](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-1C6379FA-BE67-42AD-AC01-3A9F75662BA8-high.png)
+   3. Make sure your ISO is either unmounted or removed from the server.
+9. After the HVM host reboots, login using the user created during installation either via the server's console or using SSH.
+10. To make sure you have all the latest system packages, update your system:
+
+    ```
+    ```
+    sudo apt update && sudo apt upgrade -y
+    ```
+    ```
+
+    NOTE
+
+    All packages will be pulled from a repository curated and maintained by HPE.
+11. Make sure to configure time synchronization (NTP) by following this KB Article: [Configuring NTP for HVM host via /etc/systemd/timesyncd.conf](https://support.hpe.com/hpesc/public/docDisplay?docId=sf000109519en_us&docLocale=en_US). 
+
+    NTP configuration is crucial in any system that needs to coordinate tasks between different services.
+12. Configure locale settings and make further networking configurations using the hpe-vm console. See [Configuring the HVM host using the hpe-vm console](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html).
+13. Repeat this process for all your host servers.
diff --git a/corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.json b/corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.json
new file mode 100644
index 0000000..59820f7
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259",
+  "title": "Scenario 1: Recommended Converged Networking Setup",
+  "ordinal": 8,
+  "parent_title": "Example Network Configurations",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.md b/corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.md
new file mode 100644
index 0000000..be4d627
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.md
@@ -0,0 +1,41 @@
+# Scenario 1: Recommended Converged Networking Setup
+
+This is where management and VM traffic is converged over the same bonded interface and storage traffic is independent. This is where management and VM traffic is converged over the same bonded interface and storage traffic is independent, for use cases where management and traffic separation is needed, review Scenario 2.
+
+In an ideal scenario, you would have at least four network interfaces spread across at least two network cards on the host (shown in green on the diagram below). Ideally you would also have two separate network switches to help ensure resiliency and redundancy. As mentioned in the prior section, these networking examples are all created with resiliency and redundancy in mind. One storage lane is connected to each switch and likewise one management/VM lane is connected to each switch, which are bonded in and active/backup configuration. Consult the bonding table in the prior section for more details on the benefits and drawbacks to different types of network bonds.
+
+**Example 1**
+
+In this scenario, the bond handles management/VM traffic failover while multipathing handles storage failover. A diagram of such a network setup is shown below:
+
+![A network diagram showing the recommended converged networking setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-84F9CBCF-1190-4DC3-88CF-A70AC53F85F7-high.png)
+
+**Example 2**
+
+In the example below, we have native VLAN on the trunk ports and on the storage ports. This means the network switch is tagging all the traffic for you and you don't have to tag it yourself. This allows you to put your IP addresses directly on the interfaces and bonds. Here, the storage VLANS get their own IP address directly on the interface while the management IP address goes directly on the bond as shown in the diagram below. With this configuration, all can be done in the installation wizard as long as the VLANs are piped to the interfaces as expected from the network switches. More specific guidance on using the installation wizard is included in later sections covering the software installation.
+
+NOTE
+
+Your environment an configurations will vary. You may or may not have a native VLAN set up for storage traffic as it is best practice to isolate storage traffic when possible. The need for VLAN tagging on specific interfaces is dependent on whether there is a native VLAN on that interface.
+
+![Networks](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-76104E44-DE07-4703-AF66-9222D2B89CDC-high.png)
+
+Below is a chart showing the connection from the bonded network interfaces created in the example network configuration above to OVS bridges (a virtual switch that connects VMs to the physical network), Virtual Networks (logical virtual networks managed by Libvirt), Libvirt Portgroups (subgroups within Libvirt Networks that can expose configurations, such as VLAN tagging), and tap interfaces (the virtual connection that connects the VM to the OVS bridge).
+
+![Bonded network](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-8A913E31-DFDE-48DE-A616-53438B0C5027-high.png)
+
+**Example 3**
+
+The prior example included native VLANs on the trunk ports and storage ports so we'll now take a look at an example configuration without native VLANs. You need to create VLAN tags on the interfaces because the switch is no longer handling the tagging for you. Your IP addresses then go on those VLAN tags. In this example bond0 becomes the compute interface and bond0.x becomes the management interface when configuring the cluster in a later step (see [Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)). When not using a native VLAN, the storage VLANs still get their own IP address and interface but a VLAN interface gets created on the bond and the management IP address goes on the VLAN interface.
+
+![VLAN Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-D61D44F7-559C-4867-A289-4C4459C7DFF9-high.png)
+
+Just as in the similar chart above, the chart below shows the connection from the bonded network interfaces created in the example network configuration above to OVS bridges (a virtual switch that connects VMs to the physical network), Virtual Networks (logical virtual networks managed by Libvirt), Libvirt Portgroups (subgroups within Libvirt Networks that can expose configurations, such as VLAN tagging), and tap interfaces (the virtual connection that connects the VM to the OVS bridge).
+
+![bonded network interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-CED6C104-09D7-4640-A630-DC67E9E0BF61-high.png)
+
+**Example 4**
+
+The same networking setup can be used with an LACP bond, however this does require extra configuration on the network switch side. The exact setup steps would depend on the specific hardware in your environment. The network setup would look something like the example below:
+
+![LCAP networking setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-9A6A696D-7DA4-4F58-899D-4D33C086757D-high.png)
diff --git a/corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.json b/corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.json
new file mode 100644
index 0000000..e92afb0
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C",
+  "title": "Setup from the HVM host",
+  "ordinal": 25,
+  "parent_title": "Upgrading the manager",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.md b/corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.md
new file mode 100644
index 0000000..ec66dc0
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.md
@@ -0,0 +1,3 @@
+# Setup from the HVM host
+
+Confirm the manager VM name (`virsh list`) and connect with `virsh console <vm name>`. This starts a local VNC serial connection. This method only works if the host has GUI capabilities installed.
diff --git a/corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.json b/corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.json
new file mode 100644
index 0000000..1aa12a4
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB",
+  "title": "Planning and preparation",
+  "ordinal": 3,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.md b/corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.md
new file mode 100644
index 0000000..1cd4e9d
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB.md
@@ -0,0 +1,11 @@
+# Planning and preparation
+
+Describes sizing, networking and storage requirements, and VM Essentials host and virtual machine features requirements.
+
+**Subtopics**  
+
+- **[Host Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.html)**
+- **[VME Manager sizing](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA.html)**
+- **[Example Network Configurations](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.html)**
+- **[Required ports](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.html)**
+- **[Supported storage protocols](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.html)**
diff --git a/corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.json b/corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.json
new file mode 100644
index 0000000..4856bb4
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-456E190C-E912-4079-A691-8D2368D63748",
+  "title": "Configuring the VM Essentials manager for initial setup",
+  "ordinal": 20,
+  "parent_title": "VM Essentials manager installation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-456E190C-E912-4079-A691-8D2368D63748.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.md b/corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.md
new file mode 100644
index 0000000..a690502
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-456E190C-E912-4079-A691-8D2368D63748.md
@@ -0,0 +1,60 @@
+# Configuring the VM Essentials manager for initial setup
+
+## Prerequisites
+
+## About this task
+
+With VM Essentials manager up and running, you can now access the UI front end by pointing your web browser to the appliance URL that you set in a previous step. You’ll be presented with a workflow for the initial VM Essentials manager configuration where you’ll have to fill in the requested information.
+
+## Procedure
+
+1. Fill in the Account Name for the Master Tenant.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-E5441FA0-9E61-4BCD-99A7-E78BC3B895D5-high.png)
+
+   This is just your organization’s name to set it up in the manager.
+
+   NOTE
+
+   HPE Morpheus VM Essentials does not support multi-tenancy, this is just an identifier for the manager to use. (Upgrade or refer to HPE Morpheus Enterprise to enable multi-tenancy capabilities.)
+2. Enter the first user’s information.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-63260306-08CE-4498-A8E2-9801E3657584-high.png)
+
+   This user will become the first System Administrator and will have all the permissions.
+3. Enter a name for the VM Essentials manager appliance.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-7AAAF299-C351-4144-9B8C-4A71DAA5C12F-high.png)
+4. Toggle the **Enable Backups** toggle if you want automated manager database backups to be taken and if you want to enable the native virtual machine backup feature.
+
+   NOTE
+
+   Integrated backups will reside on the manager’s local storage by default, you should enable an external repository later.
+5. Enter your license and select **Complete Setup**. If you don’t have a valid license or are just evaluating the solution, a 30 day evaluation period is activated by default.
+
+   - The main Appliance Setting screen opens with several configuration options. The next steps focus on the main items you’ll need to configure to create your first cluster.
+   - You need a pre-existing Group and Cloud to add your first HVM cluster. Groups define logical groupings of resources and users access those resources based on the Groups associated with their Roles. A Cloud can represent a grouping of HVM clusters or a connection into a VMware vCenter environment. You can read more on [Groups](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007230en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html) and [Clouds](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007230en_us&docLocale=en_US&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html) in the HPE Morpheus VM Essentials Software Documentation. This guide will go through the process of adding Private Cloud-type Clouds which house HVM clusters. For VMware-type Clouds, see the associated [integration guide](https://hpevm-docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware.html).
+6. Create the first group.
+   1. Go to Infrastructure > Groups on the top menu.
+
+      ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-BD2818A0-CC0E-40DD-9B26-2C993BEDEEDD-high.png)
+   2. Click Create.
+
+      ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-611CA228-70AD-4A82-898B-837138390805-high.png)
+   3. Give the group a name and click Save Changes.
+
+      ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-644A6212-E8F9-43E3-BF3B-030CC0BAF4DE-high.png)
+7. Create the first Cloud.
+   1. Go to Infrastructure > Clouds and click Add.
+   2. Select PRIVATE CLOUD.
+
+      NOTE
+
+      To add additional CLOUDs other than HVM or VMware, upgrade to HPE Morpheus Enterprise.
+
+      ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-3709C871-93D2-4951-9EC7-4E4075F3957C-high.png)
+   3. Assign a name and then click Next at the bottom.
+   4. Select your existing Group.
+
+      ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-FC24B1C2-CD08-4B05-A32E-7AC896EC2599-high.png)
+   5. Review and complete the wizard.
diff --git a/corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.json b/corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.json
new file mode 100644
index 0000000..0b0e04e
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7",
+  "title": "Deployment",
+  "ordinal": 14,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.md b/corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.md
new file mode 100644
index 0000000..5f57336
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-4767CCB8-A276-45C4-BD8F-4E42865E28C7.md
@@ -0,0 +1,15 @@
+# Deployment
+
+Provides essential information about how to deploy HPE Morpheus VM Essentials including HVM host and VM Essentials manager installation.
+
+**Subtopics**  
+
+- **[Solution overview](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099_2.html)**  
+   Provides an overview of the components included in HPE Morpheus VM Essentials including HVM, and VM Essentials manager.
+- **[Installation overview](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.html)**
+- **[Installing HVM OS on host servers](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html)**
+- **[Configuring the HVM host using the hpe-vm console](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html)**
+- **[VM Essentials manager installation](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.html)**
+- **[Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)**
+- **[Configuring Linux images for use with HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.html)**
+- **[Configuring Windows Images for Use with HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.html)**
diff --git a/corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.json b/corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.json
new file mode 100644
index 0000000..1bdebea
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA",
+  "title": "Upgrading the manager",
+  "ordinal": 24,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.md b/corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.md
new file mode 100644
index 0000000..f3e85d7
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-4EDB4324-2C3B-435F-80FF-F430D02A2FDA.md
@@ -0,0 +1,27 @@
+# Upgrading the manager
+
+Explains how to upgrade the VM Essentials manager, the Morpheus Agent, and how to update HVM hosts.
+
+To upgrade the VM Essentials manager, you’ll need to obtain the `.deb` upgrade package(s) from the VM Essentials page on the HPE Software Center. Reach out to your account manager if you’re unable to access the downloads as described in the next paragraphs. For an upgrade, you’ll need the debian package (not the ISO, which is for first-time installation). If you are performing an offline upgrade, you will also need the “supplemental” debian package.
+
+Once logged into [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/dashboard/entitlement), click on the “Software” section from the side navigation.
+
+![Software Center](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-08A6235D-3F5D-41F4-BAC1-7744ACA486EE-high.png)
+
+Within the “Software” section, search for HPE Morpheus VM Essentials Software amongst your other software entitlements. A “Product Info” type search for the term “HPE Morpheus VM Essentials Software” may work but depending on the entitlements present in the account and future changes to search functionality, a slightly different search might be required. Once VM Essentials is successfully returned, click on the dropdown menu under “Action” and click on “Get License.”
+
+![Image Search](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-C0D08829-FB25-4BD4-B22C-F4C0D5B4111D-high.png)
+
+From the download page, you’ll see software packages, signature files and license files. Mark the checkbox next to any that you need and download them to your computer.
+
+![Download](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-DCAD98BC-858C-4202-BFC9-E66348ECEB4F-high.png)
+
+For an upgrade, we only need the `.deb` file available in the software center (and potentially the “supplemental” debian package as well if this will be an offline upgrade). To continue, copy the `.deb` file(s) over to the VM Essentials manager VM. On Linux, this could be done with `scp` (`scp /path/to/file.deb username@<VM IP address>:/path/to/destination`). You’ll need the VM user’s password unless you’re using SSH keys. Alternatively, you may also click the "curl Copy" button to download a .txt file containing a curl command which you can paste into a terminal session connected to the HPE Morpheus VM Essentials Manager VM.
+
+With the `.deb` file in place, we need to open a console connection to the VM Essentials manager VM to perform the actual upgrade. There are a number of methods to accomplish this but below are two examples from either an HVM host or from your own computer.
+
+**Subtopics**  
+
+- **[Setup from the HVM host](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C.html)**
+- **[Setup from another computer](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-54192A74-516A-4605-9623-49538D67D590.html)**
+- **[Upgrade process](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.html)**
diff --git a/corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.json b/corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.json
new file mode 100644
index 0000000..e94f396
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-54192A74-516A-4605-9623-49538D67D590",
+  "title": "Setup from another computer",
+  "ordinal": 26,
+  "parent_title": "Upgrading the manager",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-54192A74-516A-4605-9623-49538D67D590.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.md b/corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.md
new file mode 100644
index 0000000..5741e72
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-54192A74-516A-4605-9623-49538D67D590.md
@@ -0,0 +1,7 @@
+# Setup from another computer
+
+- Confirm the manager VM name (run `virsh list` on the HVM host).
+- Next, make note of the VNC port and password for the VM Essentials manager VM. This is done by running `virsh edit <vm name>` on the HVM host and finding it within the block beginning `<graphics`. This block is typically near the bottom of the XML.
+- Having obtained this information, move back over to your own computer (must be a computer with a desktop terminal, access to the VME host, and GUI capabilities).
+- Connect to the SSH tunnel: `ssh -L <VNC PORT>:127.0.0.1:<VNC PORT> <VME Host User>@<Host IP/hostname>`.
+- Then, using a VNC viewer (for example, VNCViewer64), connect to `localhost:<VNCPort>`. Use the password obtained from the VM XML viewed earlier.
diff --git a/corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.json b/corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.json
new file mode 100644
index 0000000..93a5e22
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98",
+  "title": "Updating HVM OS",
+  "ordinal": 28,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.md b/corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.md
new file mode 100644
index 0000000..e9d72fc
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-5D1F22AC-BEE3-4BB5-AC82-9EEB19233B98.md
@@ -0,0 +1,100 @@
+# Updating HVM OS
+
+Explains how to update HVM OS, the base operating system for HVM Hosts
+
+HVM OS is preconfigured with trusted `apt` update repositories, which are hosted by HPE. These repositories enabled customers to apply updates to HVM OS during scheduled maintenance or downtime windows. This ensures systems remain secure and up to date.
+
+The following repositories are configured by default:
+
+HPE Zion Private Repository
+
+- Types: deb
+- URIs: <https://update1.linux.hpe.com/repo/hpevme/zion-private-ubuntu/>
+- Suites: pulp
+- Components: upload
+- Check-Valid-Until: False
+- Trusted: True
+- Signed-By: /etc/apt/keyrings/zion\_repo\_public.key
+
+This repository is used for HPE-provided, platform-specific packages required for the HVM OS environment. It may include custom components, integrations, or fixes validated by HPE.
+
+HPE Zion OS Updates Repository (Ubuntu 24.04 - Noble)
+
+- Types: deb
+- URIs: : <https://update1.linux.hpe.com/repo/hpevme/zion-os-updates-prod/ubuntu2404-os-updates/>
+- Suites: noble-updates
+- Components: main
+- Check-Valid-Until: False
+- Trusted: True
+- Signed-By: /etc/apt/keyrings/zion\_repo\_public.key
+
+This repository provides curated Ubuntu 24.04 (Noble) OS updates aligned with HPE validation and support requirements for HVM OS deployments.
+
+Update Process and Customer Responsibility
+
+Customers can use standard `apt` tooling to apply updates when newer OS packages are available (`apt update` and `apt upgrade`). Updates should be performed only during approved maintenance windows to minimize operational impact.
+
+Complete the update process on one host at a time. Hosts are placed into maintenance mode and the update is run only after confirming the host has successfully entered maintenance. Hosts are placed into maintenance by:
+
+1. Navigating to the cluster detail page
+2. Selecting the Hosts tab
+3. Selecting an individual host
+4. Selecting the ACTIONS menu
+5. selecting "Enter Maintenance"
+
+Once the host has entered maintenance mode, run `sudo apt update` and `sudo apt upgrade`. After completing the update, bring the host back out of maintenance mode and continue to the next host only after confirming the prior host has successfully left maintenance.
+
+All repositories are:
+
+- Explicitly marked as trusted
+- Signed using the HPE Zion public repository key
+- Configured with "Check-Valid-Until: False" to avoid update interruptions caused by metadata expiration
+
+IMPORTANT
+
+Only packages obtained from the preconfigured HPE repositories are supported. Adding external or upstream Ubuntu repositories may lead to unsupported configurations.
+
+Offline HVM OS Updates
+
+For air-gapped environments where cluster hosts don't have access to the public Internet, use the following process to update the underlying base OS (HVM OS). This process should be completed on one host at a time to avoid any cluster downtime.
+
+1. Download the offline upgrade bundle to your workstation from My HPE Software Center
+2. Copy the offline upgrade bundle to the HVM Host. This can be done using `scp` or a similar tool like `WinSC` (ex. `scp hvm-upgrade-bundle.zip user@x.x.x.x:/home/user`)
+3. Remotely access the HVM Host (ex. `ssh user@x.x.x.x`)
+4. From the directory where you copied the offline upgrade bundle, unzip the bundle into its own new directory (ex. `unzip hvm-upgrade-bundle.zip -d hvm-upgrade-bundle/`)
+5. Navigate into the new directory (ex. `cd hvm-upgrade-bundle/`)
+6. The directory contains a tar bundle and a repository key. First, copy the repository key to `/etc/apt/keyrings/` (ex. `sudo cp zion_repo_public.key /etc/apt/keyrings/`)
+7. Convert the key using `sudo gpg --dearmor -o /etc/apt/keyrings/zion_repo_public.gpg zion_repo_public.key`
+8. Set permissions on the converted key using `sudo chmod 644 /etc/apt/keyrings/zion_repo_public.gpg`
+9. The `.key` file can now be deleted using `sudo rm /etc/apt/keyrings/zion_repo_public.key`
+10. Untar the bundle (ex. `tar xvzf hvm_upgrade_bundle_xxx.tar.gz`)
+11. Move up one directory level (`cd ../`)
+12. Move the extracted bundle to `/var/local` (ex. `sudo cp -a hvm-upgrade-bundle /var/local`)
+13. Change the directory owner (ex. `sudo chown -R root:root /var/local/hvm-upgrade-bundle`)
+14. Create a new file for a new addition to the local `apt` repository (ex. `sudo vi /etc/apt/sources.list.d/hpe-local-repo.sources`)
+15. Within the text editor, add the following content to the new file. Then, save the file:
+
+    ```
+    ```
+    Types: deb  
+    URIs: file:/var/local/hvm-upgrade-bundle/ubuntu2404-os-updates  
+    Suites: noble-updates  
+    Components: main  
+    Check-Valid-Until: False  
+    Signed-By: /etc/apt/keyrings/zion_repo_public.gpg
+    ```
+    ```
+16. Within the HPE Morpheus Software UI, put the HVM Host we just worked with into Maintenance Mode. To do this, navigate to **Infrastructure > Clusters > Selected HVM Cluster > Hosts tab > Selected Host**. Once on the HVM Host detail page, click ACTIONS and then click "Enter Maintenance Mode."
+17. Back on the HVM Host, validate that all VMs have stopped with `sudo virsh list --all`. This should show that there are no running VMs
+18. Validate that Pacemaker has entered standby mode with `sudo pcs status`. Status should show standby
+19. Stop Pacemaker with `sudo systemctl stop pacemaker`
+20. Stop Corosync with `sudo systemctl stop corosync`
+21. Update `apt` package data with `sudo apt update`. You will very likely see errors and should confirm these are for online repositories which cannot be reached in an offline environment. Once you've confirmed this is the source of the error, you may ignore the errors and proceed
+22. Upgrade HVM OS with `sudo apt upgrade`
+23. Reboot the system with `sudo reboot -f now`
+24. Validate Pacemaker came back up as expected with `sudo systemctl status pacemaker`
+25. Validate Corosync came back up as expected with `sudo systemctl status corosync`
+26. Bring Corosync back from standby with `sudo pcs node unstandby`
+27. Confirm the HVM Host came out of standby with `sudo pcs status`
+28. Back in HPE Morpheus Software UI once again, take the HVM Host out of Maintenance Mode by navigating to the Host detail page as described previously. Click on the ACTIONS menu and select "Exit Maintenance Mode."
+29. Once the HVM Host is confirmed back from Maintenance Mode, complete this process on all other HVM Hosts which make up the cluster
diff --git a/corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.json b/corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.json
new file mode 100644
index 0000000..acb811e
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB",
+  "title": "User manual",
+  "ordinal": 29,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.md b/corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.md
new file mode 100644
index 0000000..069bd23
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB.md
@@ -0,0 +1,5 @@
+# User manual
+
+Provides further information on configuration and workflows.
+
+For further information about HPE Morpheus VM Essentials configurations and management, see [HPE Morpheus VM Essentials Software Documentation](https://www.hpe.com/support/morpheus-vm-essentials-documentation-latest)
diff --git a/corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.json b/corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.json
new file mode 100644
index 0000000..525ce97
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A",
+  "title": "VM Essentials manager installation",
+  "ordinal": 18,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.md b/corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.md
new file mode 100644
index 0000000..db22925
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-68F53326-BE6E-40DA-801B-FD9A3E3DEC7A.md
@@ -0,0 +1,11 @@
+# VM Essentials manager installation
+
+The Morpheus VM Essentials manager is delivered as a virtual appliance that runs on top of any of the HVM hosts in the cluster. Getting it up and running is a simple, two-step process that involves deploying the appliance virtual machine and initializing the actual VME manager application with some initial settings. The following sections outline both steps:
+
+- [Installing the VM Essentials manager](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html)
+- [Configuring the VM Essentials manager for initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-456E190C-E912-4079-A691-8D2368D63748.html)
+
+**Subtopics**  
+
+- **[Installing the VM Essentials manager](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html)**
+- **[Configuring the VM Essentials manager for initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-456E190C-E912-4079-A691-8D2368D63748.html)**
diff --git a/corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.json b/corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.json
new file mode 100644
index 0000000..7faaf51
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8",
+  "title": "Supported storage protocols",
+  "ordinal": 11,
+  "parent_title": "Planning and preparation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.md b/corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.md
new file mode 100644
index 0000000..91f24ae
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-6EBCB223-4C48-456F-950C-C8ED5610A0F8.md
@@ -0,0 +1,18 @@
+# Supported storage protocols
+
+HPE Morpheus VM Essentials supports different types of storage for storing virtual machines.
+
+Local server storage
+:   While local disks in the HVM hosts can be used to store virtual machines, using local storage doesn’t allow the virtual machines to be migrated live to other hosts and the virtual machines won’t be able to be recovered should the host fail.
+
+External block storage
+:   VM Essentials supports connecting to external storage arrays using either iSCSI or Fiber Channel, in both cases datastores using GFS2 (Global Filesystem 2) can be created on volumes exported to the hosts. With this type of storage, the minimum number of supported HVM hosts in a cluster is three (3).
+
+NFS
+:   VM Essentials can use NFS shares as external shared data stores, in this case the minimum number of HVM hosts in a cluster is two (2) if virtual machine availability is desired.
+
+HPE Alletra MP B10000 Plugin
+:   VM Essentials also includes an integration plugin that allows it to create storage volumes that are directly mapped to each virtual machine’s disk without needing an intermediary clustered filesystem thus simplifying management tasks and improving performance.
+
+HPE SimpliVity
+:   HPE also offers an HCI solution through HPE SimpliVity that allows the creation of high availability clusters using the hosts' local disk while enabling advanced data services like data reduction, backup and replication.
diff --git a/corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.json b/corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.json
new file mode 100644
index 0000000..6c41d20
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290",
+  "title": "Network Bonding",
+  "ordinal": 7,
+  "parent_title": "Example Network Configurations",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.md b/corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.md
new file mode 100644
index 0000000..6786641
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.md
@@ -0,0 +1,9 @@
+# Network Bonding
+
+Network bonding is the combining of multiple network adapters into a single logical interface. This is done to build in redundancy and to increase throughput. Network bonds are configured at the operating system level and there are multiple types of network bonds depending on hardware support and other factors.
+
+In the scenarios described in the following sections, we will call out two types of network bonds that are effective for virtualization (active-backup and LACP) and show them in example configurations. VMware LBT bonds are also shown in the table below for the sake of comparison, though only the other two have been utilized in verified scenarios.
+
+Once established, we can later offer up these bonded interfaces as a compute network (for virtual machine traffic) or storage network (for interacting with external storage) when creating our cluster within the VM Essentials manager.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-3959336C-7ECD-49B7-85FC-62198924DE79-high.png)
diff --git a/corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.json b/corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.json
new file mode 100644
index 0000000..a5078d5
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-88494051-74D1-4BD9-BAFF-134A573FF77B",
+  "title": "API reference",
+  "ordinal": 30,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.md b/corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.md
new file mode 100644
index 0000000..d09f3fc
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-88494051-74D1-4BD9-BAFF-134A573FF77B.md
@@ -0,0 +1,5 @@
+# API reference
+
+Contains the full API reference for interacting programmatically with HPE Morpheus VM Essentials.
+
+See the HPE Morpheus VM Essentials [API reference](https://apidocs.morpheusdata.com/docs/getting_started) for a complete endpoint list and example call formation.
diff --git a/corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.json b/corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.json
new file mode 100644
index 0000000..bf796c0
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-8D494112-C361-4300-B7BF-B4DFE06E871C",
+  "title": "Configuring Linux images for use with HVM Clusters",
+  "ordinal": 22,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.md b/corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.md
new file mode 100644
index 0000000..c0f2c30
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-8D494112-C361-4300-B7BF-B4DFE06E871C.md
@@ -0,0 +1,59 @@
+# Configuring Linux images for use with HVM Clusters
+
+**Prerequisites**: Read: [System requirements](https://ubuntu.com/server/docs/reference/installation/system-requirements/).
+
+This is an example image prep process for creating a deployable Ubuntu 24.04 image for HVM Clusters.
+
+1. Download the latest Ubuntu 24.04 Server ISO from Canonical.
+2. Upload the downloaded Ubuntu ISO as a Virtual Image in the HPE Morpheus VM Essentials Software Manager:
+
+   1. Navigate to Library > Virtual Images
+   2. Click Add
+   3. Select the downloaded ISO
+   4. Configure the "Operating System" (Ubuntu 24.04 64-bit) and leave all other configurations on the default selections. Drag and drop the ISO on the Drop Files Here dropzone near the bottom of the modal.
+   5. Wait until the ISO has completely uploaded. There is a progress bar to provide information on the upload process.
+   6. Once the ISO has fully uploaded, click Save changes.
+3. Provision a new HVM workload to your HVM Cluster:
+
+   1. Navigate to Provisioning > Instances.
+   2. Click + ADD.
+   3. From the Type tab of the provisioning wizard, select HVM and click Next.
+   4. From the Group tab, select the correct Group and Cloud for your HVM Cluster, provide a name for this Instance, and click Next.
+   5. On the Configure tab, the exact configurations for the following fields will depend on the environment and available resources. Use the guidelines below to make appropriate selections. At this point, we simply need an accessible VM so we can successfully install the OS, make a few additional configurations (such as installing cloud-init), and save it as a deployable image.
+
+      Plan
+      :   A number of default plans ship with Morpheus, using a smaller default plan is fine for this purpose.
+
+      Resource Pool
+      :   Select a cluster this VM can run on, when getting started there may only be one.
+
+      Root volume
+      :   Smaller size is fine for this purpose and a specific datastore could be manually selected if desired.
+
+      Network
+      :   Select the network configured for the instance.
+
+      IMAGE
+      :   Select the ISO that was just uploaded.
+   6. Click Next and Complete through the next two tabs to stand up the Instance.
+4. Install and configure your new VM for image creation:
+
+   1. Click into the newly created Instance to view the Instance detail. Launch the console view so installation and configurations can be completed (ACTIONS > Open Console)
+   2. Complete the Ubuntu installation process. In most environments, the default installation configurations will work fine for our purposes here, just ensure the VM will be able to get out to the Internet. During installation, a user profile will be created which will be used to perform additional configurations in the steps ahead.
+   3. When installation is complete, reboot the VM. You will be warned that the ISO is still mounted to the virtual machine. Eject the ISO using the UI tools in the Manager (ACTIONS > Eject Disks). Once ejected, continue with the reboot.
+   4. Following reboot, log in as the user configured during installation and complete these prep steps:
+
+      1. Run updates: `sudo apt update && sudo apt upgrade -y`
+      2. Install cloud-init: `sudo apt install -y cloud-init`
+      3. Verify cloud-init is installed: `cloud-init --version`
+      4. Enable cloud-init services: `sudo systemctl enable cloud-init cloud-init-local cloud-config cloud-final`
+      5. Check status of the service: `sudo systemctl status cloud-init`
+      6. Configure cloud-init data sources by editing the following config file: `sudo vi /etc/cloud/cloud.cfg.d/90_dpkg.cfg` with the following configuration: `datasource_list: [ NoCloud, None ]`. Then, save and close the config file
+      7. Disable things that break templating: `sudo truncate -s 0 /etc/machine-id` and `sudo rm -f /var/lib/dbus/machine-id`
+      8. Clear SSH keys: `sudo rm -f /etc/ssh/ssh_host_*`
+      9. Remove persistent network config: `sudo rm -f /etc/netplan/*.yaml`
+      10. Clean cloud-init state: `sudo cloud-init clean --logs`
+5. Close the console window and shut down the VM using the Manager UI tools from the Instance detail page (ACTIONS > Stop Server.)
+6. Still on the Instance detail page, create an image from your stopped Instance (ACTIONS > Import as Image.)
+7. Back on the Virtual Images list page, you should see a new Virtual Image object being created
+8. Once the image is completely created (status shows as Active), you are ready to provision. Repeat the steps above to add a new Instance but substitute the new deployable image rather than the ISO that was used originally. Now, the disk, network, and default user configurations made during Instance provisioning will apply successfully to new Instances. You can continue to build on this by installing specific software stacks and saving new images for specific service types. Additionally, setup scripts can be written and applied at provision time to add additional orchestration at deployment time.
diff --git a/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.json b/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.json
new file mode 100644
index 0000000..9f4f7f3
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-94742592-9C85-4F2E-83F2-E68404A73F3B",
+  "title": "Upgrade process",
+  "ordinal": 27,
+  "parent_title": "Upgrading the manager",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.md b/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.md
new file mode 100644
index 0000000..a9f9a38
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.md
@@ -0,0 +1,54 @@
+# Upgrade process
+
+Having copied over the needed files and connected to the VM Essentials manager VM, the upgrade is completed in just a few commands. These commands will stop the current services, install the package, and then reconfigure the Manager. Replace the placeholder `.deb` file in the commands below with the correct path and file name of the package you’ve copied over.
+
+IMPORTANT
+
+Upgrading VM Essentials manager will result in downtime of 10-15 minutes. Ensure users are not doing critical work during the upgrade window. This downtime applies only to the Manager itself and has no effect on the hypervisor host(s) or any provisioned VMs currently running.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo dpkg -i xxxx.deb  
+sudo dpkg -i xxxx.supplemental.deb  # Optional -- Only for offline upgrades  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once the UI service is up and running, the upgrade process is complete. Attempt to reach your appliance normally through a web browser to confirm success.
+
+NOTE
+
+- Services will be stopped during package installation and started during the reconfigure process, including the `morpheus-ui` service.
+- If the reconfigure process is interrupted or fails, the `morpheus-ui` service may need to be manually started or restarted.
+- In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+Following upgrade, it's advisable to check for any available HVM Host Agent upgrades. To upgrade the HVM Host Agent, navigate to an HVM Host detail page, expand the ACTIONS menu, and click "Upgrade Agent." This process must be repeated for each HVM Host that makes up the HVM Cluster.
+
+Alternatively, you could also select "Download Agent Script" to download an Agent upgrade script which can be run when connected to the host through a terminal session. The Agent upgrade scripts are Host-specific so an individual script would need to be downloaded for each HVM Host.
+
+## Upgrade sequence procedure
+
+This section contains a table of compatible upgrade paths. The far left column contains the HPE Morpheus VM Essentials Manager version you're starting from. The columns to the right indicate versions compatible for upgrade from your starting version. If the version number is listed, it is a compatible upgrade path. If an "**X**" is listed instead, the upgrade path is unsupported.
+
+NOTE
+
+It is possible to span multiple versions in a single upgrade. For example, you can upgrade directly from HPE Morpheus VM Essentials version 8.0.3 to version 8.0.6, or from version 8.0.7 to version 8.0.11, and so on. Consult the table below for compatible or incompatible version upgrade hops.
+
+| From Version | To Version | | | | | | | | | | | | | | |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| 8.0.1 → | 8.0.2 | 8.0.3 | 8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.2 → |  | 8.0.3 | 8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.3 → |  |  | 8.0.4 | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.4 → |  |  |  | 8.0.5 | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.5 → |  |  |  |  | 8.0.6 | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.6 → |  |  |  |  |  | 8.0.7 | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.7 → |  |  |  |  |  |  | 8.0.8 | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.8 → |  |  |  |  |  |  |  | 8.0.9 | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.9 → |  |  |  |  |  |  |  |  | 8.0.10 | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.10 → |  |  |  |  |  |  |  |  |  | 8.0.11 | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.11 → |  |  |  |  |  |  |  |  |  |  | 8.0.12 | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.12 → |  |  |  |  |  |  |  |  |  |  |  | 8.0.13 | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.0.13 → |  |  |  |  |  |  |  |  |  |  |  |  | 8.1.0 | 8.1.1 | 8.1.2 |
+| 8.1.0 → |  |  |  |  |  |  |  |  |  |  |  |  |  | 8.1.1 | 8.1.2 |
+| 8.1.1 → |  |  |  |  |  |  |  |  |  |  |  |  |  |  | 8.1.2 |
diff --git a/corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.json b/corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.json
new file mode 100644
index 0000000..16594a6
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB",
+  "title": "Required ports",
+  "ordinal": 10,
+  "parent_title": "Planning and preparation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.md b/corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.md
new file mode 100644
index 0000000..ca09a68
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-97DDED8D-EE6B-4819-8080-E163FD533CAB.md
@@ -0,0 +1,22 @@
+# Required ports
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus VM Essentials Agent communication with the HPE Morpheus VM Essentials manager | HVM Host | HPE Morpheus VM Essentials manager | 443 | TCP |
+| HPE Morpheus VM Essentials Agent communication with the HVM Host for hypervisor console | HPE Morpheus VM Essentials manager | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus VM Essentials manager | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus VM Essentials manager SSH access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTP) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.json b/corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.json
new file mode 100644
index 0000000..7ace07d
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-99397996-8315-49C1-9E2F-2EED51CE03F3",
+  "title": "Creating an HVM cluster",
+  "ordinal": 21,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.md b/corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.md
new file mode 100644
index 0000000..b7a9018
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.md
@@ -0,0 +1,59 @@
+# Creating an HVM cluster
+
+## About this task
+
+An HVM cluster is the basic unit of management in VM Essentials, you need to create a cluster even if you are only using one HVM host for testing or for edge data centers. A cluster is a construct that allows you to access the advanced functionality of the solution.
+
+Once the VM Essentials manager is configured, you are ready to create your HVM cluster.
+
+## Procedure
+
+1. Go to Infrastructure > Clusters and click + Add Cluster.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-635E364E-0361-4187-B38C-3BB225FB2A52-high.png)
+2. Select HVM as the cluster type and click Next.
+3. Select the Group the cluster will belong to.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-08F032FA-0C99-403B-A449-015FFA0EBE42-high.png)
+4. Give your cluster a name and, optionally, enter a description and any label to identify it.
+
+   NOTE
+
+   Only fields with a green mark on the left are mandatory.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-DA2D5AF6-F53D-40E6-8A86-46279D6168F3-high.png)
+5. Fill in the required fields.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-E3FD5376-D7FC-464D-A9CB-1F97C67AFAC2-high.png)
+
+   - Leave the layout at the default HVM 1.2 Cluster on HVM/Ubuntu 24.04.
+   - For SSH Hosts, click the + sign on the right to add as many hosts as you need. Enter a name for each host and its management IP address. The exact name entered here is not vital as it's simply an identifier for that specific host within the user interface. It could be the hostname or some other identifier specific to that host.
+   - Enter an SSH Username and SSH Password. This is a set of credentials for an admin user account configured on each host.
+6. Enter the network interfaces in the designated fields.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-2A624E8E-455B-4D54-BBAA-CB64148CC176-high.png)
+
+   - Management net interface: Enter the tagged bond you created for host management.
+   - Compute net interface: To route virtual machine traffic using different VLANs through the same ports your management network uses, enter the untagged bond you created.
+   - Compute VLANs: Enter any VLANs you need, the respective Portgroups will be created.
+
+     NOTE
+
+     - You can obtain the interface names from the host's CLI using the command: `ip address show`.
+     - Selecting the bond with NO TAGGING is crucial for the virtual switch to allow VLANs to flow through.
+7. You can safely leave all the remaining settings by default. Here is a short description.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-650C4EE6-B51F-41A1-A6AC-F5D1966475AC-high.png)
+
+   - CPU Type: Only x86\_64 is supported.
+   - CPU Model: This setting will define the CPU used for virtual machines, you should leave it as “host-passthrough” unless your cluster nodes have different CPU families each.
+   - Dynamic placement: If enabled, the cluster will balance the load automatically by live migrating virtual machines between nodes.
+   - Power policy: Defines if the hosts will optimize for performance or for power consumption.
+8. Click Next and then Complete.
+
+   You are taken back to the cluster screen where you’ll see your cluster name and an icon showing the cluster is being created.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-1DE897F2-CDC9-451B-A0D7-2BB31D6A8D5C-high.png)
+9. To follow up on the creation process, click on the cluster name and then go to the History tab. When the Provision and the Post-Provision activities finish with a green check mark, your cluster is ready to run virtual machines.
+
+   ![VM Essentials manager initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-A7CA7ED2-30EC-49B3-8147-8E05C2A219DF-high.png)
diff --git a/corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.json b/corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.json
new file mode 100644
index 0000000..ca46ac7
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC",
+  "title": "Websites",
+  "ordinal": 32,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.md b/corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.md
new file mode 100644
index 0000000..cd4f271
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-A1201D1E-6CB8-4647-AA3D-EBCB405C51FC.md
@@ -0,0 +1,11 @@
+# Websites
+
+## General websites
+
+Single Point of Connectivity Knowledge (SPOCK) Storage compatibility matrix
+:   <https://www.hpe.com/storage/spock>
+
+Technical papers and analyst reports
+:   <https://www.hpe.com/us/en/resource-library>
+
+For additional websites, see [Support and other resources](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=Standard-Support_and_other_resources.html).
diff --git a/corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json b/corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
new file mode 100644
index 0000000..47d8c87
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+  "title": "Host Features",
+  "ordinal": 12,
+  "parent_title": "VM Essentials features",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md b/corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
new file mode 100644
index 0000000..e6d043d
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
@@ -0,0 +1,19 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and datastores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Governance through VM Essentials RBAC
+- Pass host-attached NVME, USB, and GPU hardware through to VMs running on the host
diff --git a/corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json b/corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
new file mode 100644
index 0000000..c6f3b95
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+  "title": "VM Features",
+  "ordinal": 13,
+  "parent_title": "VM Essentials features",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md b/corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
new file mode 100644
index 0000000..558534e
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Console support for running workloads
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore VM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- VM Essentials library and automation support
+- Claim and consume host-attached NVME, USB, and GPU hardware to run hardware-accelerated workloads on VMs
diff --git a/corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.json b/corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.json
new file mode 100644
index 0000000..742557a
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-ADC37453-056E-43C8-8177-8211A44790FD",
+  "title": "Configuring the HVM host using the hpe-vm console",
+  "ordinal": 17,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.md b/corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.md
new file mode 100644
index 0000000..6526eaf
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-ADC37453-056E-43C8-8177-8211A44790FD.md
@@ -0,0 +1,83 @@
+# Configuring the HVM host using the hpe-vm console
+
+## About this task
+
+The hpe-vm console is an utility built by HPE to simplify host management tasks like setting up the timezone, configure the networks and bootstrapping the VM Essentials manager. Use it to configure important settings in the network bond and to configure the iSCSI storage networks, if iSCSI storage is applicable.
+
+## Procedure
+
+1. Open the hpe-vm console utility by running: `sudo hpe-vm`.
+
+   ![hpe-vm console-1](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-B7AC083D-9D23-4B04-A95F-0FA38B768450-high.png)
+2. Select **Configure Network**. You are presented with a menu where you can make all the needed network configuration changes without any manual editing using the host's CLI.
+
+   ![hpe-vm console-2](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-CB4843C8-4741-437E-86B0-F9F7C7D98520-high.png)
+3. Adjust bond configuration.
+
+   For the active-backup bond to perform interface failover, the mii-monitor-interval needs to be configured as described in this KB article [Setting active/backup bond type parameters with the hpe-vm cli tool](https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000109520en_us). You can do this from the hpe-vm console.
+
+   1. Navigate to **Device Type** and select **bond**.
+
+      ![hpe-vm console-3](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-C2F3E3B3-5A3E-47F6-8259-9F82CDD20E84-high.png)
+   2. Select your bond.
+
+      ![hpe-vm console-4](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-34D3C2F5-AC44-45A6-BAE7-0ED729241AF9-high.png)
+   3. Navigate to the Bond section and select **<edit>** in the parameters option.
+
+      ![hpe-vm console-5](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-7FE8127D-6326-46FD-9607-245106210107-high.png)
+   4. Enter the following values and then select **<Done>**.
+
+      ![hpe-vm console-6](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-3F7E8FD1-1909-4375-80DB-E484EFD3A542-high.png)
+
+      - Mii-monitor-interval: 100
+      - up delay: 200
+      - down delay: 200
+   5. Select **<Done>** to navigate away from the bond menu
+
+      ![hpe-vm console-7](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-C1F02698-2037-44CA-9F15-1F29BC66760A-high.png)
+   6. Select **<Save>**.
+
+      ![hpe-vm console-8](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-54EF7436-C8F4-4ED8-8B9D-E2BBF3E6F7A7-high.png)
+   7. Select **Confirm** in the pop-up notification.
+4. Next, configure the iSCSI interfaces, if applicable.
+
+   iSCSI interfaces are just ethernet adapters so you can configure them from the same hpe-vm console.
+
+   1. Make sure **ethernet** is selected under **Device type**.
+   2. Select **Add**.
+
+      ![hpe-vm console-9](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-A0A99DAB-A81F-40B9-822F-1A2461036407-high.png)
+   3. Under **Device ID**, enter the interface name and select **<Continue>**.
+
+      ![hpe-vm console-10](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-8A7406B8-9433-44F4-8C98-F68F6A855442-high.png)
+
+      NOTE
+
+      The interface name can be obtained by running `ip a` at the host’s CLI.
+   4. Select **<edit>** on the addresses row to configure the IP Address.
+
+      ![hpe-vm console-11](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-FF6888DD-5B72-43E2-9C52-A7023868248A-high.png)
+
+      NOTE
+
+      iSCSI traffic is not usually routed, you won’t need to configure other network parameters unless your specific network requires it.
+
+      Switch ports for iSCSI traffic are usually untagged access ports.
+   5. Set the MTU to `9000`
+
+      ![hpe-vm console-12](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-94729772-4544-437C-953A-5EC4693B9A69-high.png)
+
+      NOTE
+
+      Most iSCSI storage networks use Jumbo Frames for performance, this configuration needs to be consistent across the network.
+   6. Select <Done> and then <Save> from the main network configuration menu.
+   7. Repeat this process for the second interface.
+
+      TIP
+
+      It is not advised to bond storage interfaces as the storage layer at the host handles multipathing to the storage array.
+
+      NOTE
+
+      - Do not use the same subnet for both storage interfaces, this might cause storage access problems.
+      - iSCSI networks should not be routable and do not need a gateway.
diff --git a/corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.json b/corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.json
new file mode 100644
index 0000000..8ed4ab7
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170",
+  "title": "Example Network Configurations",
+  "ordinal": 6,
+  "parent_title": "Planning and preparation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.md b/corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.md
new file mode 100644
index 0000000..ed7faaf
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-BDF3EFBF-EA90-4E6F-88D3-87ABF18C4170.md
@@ -0,0 +1,9 @@
+# Example Network Configurations
+
+If you have the capability to do so, it’s recommended you set up networking with full redundancy. Such a setup could include two network switches and hosts with at least four network interfaces spread across two network cards. This would allow for failover in the event of the loss of a switch and/or one of the host network cards in addition to separating management and compute network traffic to their own interfaces. Hosts with only four NICs each can still be configured for full redundancy but would have to converge management and compute traffic across the same interfaces. Keep in mind also that these examples use MPIO (multi-path input/output) for storage. It would also be possible to use bonding for storage depending on capabilities of the environment. MPIO is recommended whenever fibre channel or iSCSI LUNs are being used for GFS2 datastores.
+
+**Subtopics**  
+
+- **[Network Bonding](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-6F1B4C62-CCE2-4AE5-9CE7-83C407BFE290.html)**
+- **[Scenario 1: Recommended Converged Networking Setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259.html)**
+- **[Scenario 2: Recommended Decoupled Networking Setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.html)**
diff --git a/corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.json b/corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.json
new file mode 100644
index 0000000..5d2a2a6
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2",
+  "title": "Host Requirements",
+  "ordinal": 4,
+  "parent_title": "Planning and preparation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.md b/corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.md
new file mode 100644
index 0000000..68555b4
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-BE7493B3-B866-4269-9C13-ABFCF84658F2.md
@@ -0,0 +1,13 @@
+# Host Requirements
+
+- **Operating System:** HVM OS provided by Hewlett Packard Enterprise.
+- **Hardware:** HPE Proliant server hardware or another compatible server type is recommended (see the [compatibility matrix](https://www.hpe.com/support/vme-compatibility-matrix) for a list of recommended compute server choices). This list is continually expanded as additional hardware SKUs are tested and verified.
+- **CPU:** One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory:** Minimum of 8GB for the HVM runtime OS
+- **Storage:** Minimum of 100GB for operating system storage
+- **Network:** 10 Gbps recommended for production environments
+- **IP Addressing:** One static IP address for management network
+- **Internet Connectivity:** Internet access is required to download and install the required packages and dependencies
+- **Network services:**
+  - Hostnames should be resolvable by the network's DNS servers.
+  - NTP is also crucial in distributed systems.
diff --git a/corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.json b/corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.json
new file mode 100644
index 0000000..9d73004
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099",
+  "title": "Solution overview",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.md b/corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.md
new file mode 100644
index 0000000..c72917c
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099.md
@@ -0,0 +1,19 @@
+# Solution overview
+
+Provides an overview of the components included in HPE Morpheus VM Essentials including HVM, and VM Essentials manager.
+
+HPE Morpheus VM Essentials is a simplified virtualization solution designed for organizations seeking efficient virtual machine (VM) management. It provides core capabilities for provisioning, monitoring, and managing VMs across hybrid environments powered by HPE HVM and VMware by Broadcom environments, enabling enterprises and cloud providers to optimize resources and reduce operational overhead.
+
+Its main components are a virtualization runtime called HVM which is installed on the hosts to run the virtual workloads and a centralized management interface called VME Manager that streamlines VM lifecycle operations—such as provisioning, configuration, and monitoring—while enforcing governance policies and enabling automation for routine tasks. Together, these components deliver a cost-effective, user-friendly platform that enhances agility while leveraging compliance and control in virtualized environments.
+
+![HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-DC38099A-88CA-4236-8F9D-79A2C39593C4-high.png)
+
+**What is HVM?**
+
+HVM is the HPE‑powered virtualization runtime OS that gets installed on the servers that will support running virtual machines. This runtime is installed using an HPE‑provided ISO, which installs the required runtime libraries and components to create an HVM Cluster to create, run, and manage virtual machines. HVM provides a console that runs on top of the HVM Cluster to simplify configuration tasks like keyboard mapping, time synchronization and even the complete networking configuration.
+
+**What is the HPE VM Essentials manager?**
+
+The HPE VM Essentials manager is a centralized management interface that offers a unified control plane for administrators to manage the lifecycle of the HVM hosts, HVM Clusters and virtual machines. It streamlines VM lifecycle operations—such as provisioning, configuration, and monitoring—while enforcing governance policies and enabling automation for routine tasks.
+
+Once deployed, HPE VM Essentials Manager takes advantage of powerful features including live migration of VMs across the HVM Cluster hosts with zero downtime, dynamically distribute workloads based on load, automatic failover of workloads following the loss of a host, and similar HVM capabilities at operational level. Provisioning new workloads is also made easy with the VM Essentials image library, automation tools, and powerful provisioning wizard. In addition to HVM clusters, VM Essentials also includes a deep integration into VMware vCenter, which also takes advantage of the same powerful provisioning wizard, automation engine, and monitoring capabilities.
diff --git a/corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.json b/corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.json
new file mode 100644
index 0000000..d852a9b
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B",
+  "title": "CLI reference",
+  "ordinal": 31,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.md b/corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.md
new file mode 100644
index 0000000..a754285
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-C6EC711D-6F9B-4B71-B209-BA92CD28026B.md
@@ -0,0 +1,5 @@
+# CLI reference
+
+Provides the information needed to install the Morpheus CLI to manage the solution.
+
+See the HPE Morpheus VM Essentials [CLI reference](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006978en_us&docLocale=en_US) for a complete list of commands and options, as well as a guide to installing the tool.
diff --git a/corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.json b/corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.json
new file mode 100644
index 0000000..15cff64
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289",
+  "title": "Installing the VM Essentials manager",
+  "ordinal": 19,
+  "parent_title": "VM Essentials manager installation",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.md b/corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.md
new file mode 100644
index 0000000..c7cee67
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.md
@@ -0,0 +1,52 @@
+# Installing the VM Essentials manager
+
+## About this task
+
+Deploy the VM Essentials manager virtual appliance in one of your HVM hosts. The VM Essentials virtual appliance is delivered inside an ISO (**HPE\_VM\_Essentials\_SW\_image\_´\*\*\*\*\*.iso**) containing the needed .qcow2 file; you can either upload the qcow2 file to your HVM host or upload the complete iso and mount it. This example will run you through the ISO method.
+
+## Procedure
+
+1. Upload the **HPE\_VM\_Essentials\_SW\_image\_´\*\*\*\*\*.iso** downloaded from [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/product-details/HPE_VME_EVAL/-/sw360_hpe_internal) using your preferred SCP client.
+
+   NOTE
+
+   There are multiple SCP client options available for Windows client machines.
+2. Mount the ISO to a path in your HVM host system:
+
+   ```
+   ```
+    sudo mount -o loop HPE_VM_Essentials_SW_image_v8.0.12_S5Q83-11039.iso /media
+   ```
+   ```
+
+   NOTE
+
+   - The indicated filename might be different, this is dictated by your download.
+   - The mount point can be any one you choose, /media is used as an example.
+3. Enter `sudo hpe-vm` to open the hpe-vm console, and select **<Install VME Manager>**.
+4. Fill in the required information.
+
+   ![VM Essentials manager installation-1](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-06123BB1-07B2-42F6-B159-50527015E8AE-high.png)
+5. When filling the information, consider the following guidelines:
+
+   - Use the IP address that will be configured for the VM Essentials manager
+   - For DNS Server, if multiple entries are needed, a comma-delimited list may be added. Bear in mind, the installer does not currently validate for the proper delimiter. This will be fixed in a future release but for now the user must validate the delimiter for themselves.
+   - The appliance URL should be resolvable via DNS (including related PTR record) from the hosts to enable communications between them and the VM Essentials manager.
+   - The username is the user with admin privilege that will be used to login to the manager’s CLI.
+   - For the Image URI, you can select and browse to the qcow2 file in the ISO you mounted previously
+
+     ![VM Essentials manager installation-2](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-42C9D685-B588-4D7F-8D59-B0BEB4DCD0AD-high.png)
+   - If your VM Essentials manager will use the same network for management access as the host’s management network, select the same vlan tagged network interface you configured for the HVM host.
+
+   NOTE
+
+   Leave the **Use Compute VLAN** box unchecked unless you want your VM Essentials manager to use a different network than the management one.
+6. Wait for the installation to finish.
+
+   ![VM Essentials manager installation-3](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-1C575100-EF58-412A-8997-C151B4441CB2-high.png)
+
+   NOTE
+
+   At a certain phase in the install process, you’ll see a message in the progress bar modal stating “Starting Morpheus Services…”. At this point, you can direct a web browser to the appliance URL and see if you can access the appliance. If you get a response returned, even if it is just telling you the appliance is still loading, that is a good sign the web server is installed and things are working even if your progress bar seems to get stuck at a high percentage.
+
+   The exact time for this installation to complete is highly dependent on the amount of compute available, the size of the network pipe, and the level of network congestion. It is common for this process to take long enough for the "Morpheus is Loading" graphic to change to a timeout graphic. This is not an indicator that the process has failed. If there are no other failure indicators, allow at least an hour before considering the installation to be irrecoverably stuck (though it would be very rare for the process to take anywhere near that length of time). To view the setup logs, run the `sudo morpheus-ctl tail morpheus-ui` command from the manager VM through SSH.
diff --git a/corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.json b/corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.json
new file mode 100644
index 0000000..acbfbf5
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849",
+  "title": "Qualification Matrix",
+  "ordinal": 2,
+  "parent_title": null,
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.md b/corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.md
new file mode 100644
index 0000000..a5494fc
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-E3635F0A-11DA-4078-8C3A-8D4B75724849.md
@@ -0,0 +1,5 @@
+# Qualification Matrix
+
+Contains the list of hardware and software that has been tested for compatibility with HPE Morpheus VM Essentials Software.
+
+Hardware and software is continually being tested and certified for compatibility with HPE Morpheus VM Essentials Software. For full details, see [The Qualification Matrix for HPE Morpheus VM Essentials Software](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006551en_us&page=GUID-EA7C0803-E66B-4B17-B994-30D4025A258F.html). Items not listed in that document may be compatible but are untested.
diff --git a/corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.json b/corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.json
new file mode 100644
index 0000000..1e01df0
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2",
+  "title": "Scenario 2: Recommended Decoupled Networking Setup",
+  "ordinal": 9,
+  "parent_title": "Example Network Configurations",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.md b/corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.md
new file mode 100644
index 0000000..07bddf7
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-E49D2EF3-8992-451F-AE3F-55E0380448D2.md
@@ -0,0 +1,5 @@
+# Scenario 2: Recommended Decoupled Networking Setup
+
+When hosts have six or more network interfaces spread across at least two cards, management and VM traffic can be separated for even greater network throughput. The overall configuration is very similar. The storage lanes are still separated as they were previously. In this case, create an additional bond across two of the interfaces for VM traffic. As previously, a bond is also created for management traffic. In this example, these bonds are created in an active/passive configuration. ![Decoupled networking setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-836F5A32-34A0-43D6-A05D-AB05ECB651F0-high.png)
+
+![Networking setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-5C3E4911-46A2-4E57-B199-568E3E2C5AFA-high.png)
diff --git a/corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.json b/corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.json
new file mode 100644
index 0000000..51cb926
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C",
+  "title": "Configuring Windows Images for Use with HVM Clusters ",
+  "ordinal": 23,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.md b/corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.md
new file mode 100644
index 0000000..80b94eb
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-EC50D35A-3B63-44DD-BC2D-1D2A0191E97C.md
@@ -0,0 +1,52 @@
+# Configuring Windows Images for Use with HVM Clusters
+
+This section will go through the steps to prepare a Windows image for deployment on HVM clusters. This image can serve as a template from which additional images and VM Essentials Library items can be built. This section only discusses the Virtual Image configuration fields needed to be successful with this example Windows deployment. For more generalized information on Virtual Images, including configurations needed for successful Linux deployment, see the **Library** **>** **Virtual Images** of the product user manual.
+
+1. In this example case, we’ll start from downloading a Windows Server ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
+2. With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+   - **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2025 ISO”
+   - **OPERATING SYSTEM:** “Windows Server 2025”
+   - **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+3. In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+4. With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space in your VME Manager appliance to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large drop zone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled **Add File** and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal.
+
+   ![Add file](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-EE446E12-71BE-41D8-8396-802AD098FB00-high.png)
+5. After the file has completely uploaded, click SAVE CHANGES. Rather than dropping and uploading the file through this modal, users may also select the URL/PATH radio button. This results in a URL field replacing the file drop zone where a URL to external storage containing the image may be entered.
+
+   NOTE
+
+   Alternatively, you can source the file from an integrated bucket (if any currently exist) by selecting the bucket in the BUCKET field and entering a path to the image in the URL field. When uploading the image via URL or path, the Virtual Image can be saved and closed as soon as all configurations are finished. Image upload will continue in the background. When uploading via file drop, the modal must remain open until the upload process is completed.
+6. Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+7. On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+8. On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration).
+9. Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+10. As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+    ![Advanced Options](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+11. The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+12. Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+13. Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then **Open Console**. This will open a new window with a console session into the VM.
+
+    ![Windows Setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+14. After selecting the language, click **Next**. On the following screen, click **Install Now**. This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click **Next**.
+
+    ![Windows Setup Image OS Selection](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+15. Accept the licensing terms and click **Next**.
+
+    ![Terms and Conditions](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+16. On the next screen, choose a custom install.
+
+    ![Installation Type](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+17. The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+    ![Driver Selection](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+18. After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+    ![Drive Selection](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+19. Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+    ![virtio-win-guest-tools](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+20. Step through the installer. Simply click **Next** or **Install** through each step, there are no configuration changes needed. Once the installer has completed, click **Finish**. You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+    ![ipconfig](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+21. We can now eject the two virtual disks, drives D: and E: in my case.
diff --git a/corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.json b/corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.json
new file mode 100644
index 0000000..123caa0
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.json
@@ -0,0 +1,11 @@
+{
+  "bundle_id": "hvm_deployment_guide",
+  "page_id": "GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932",
+  "title": "Installation overview",
+  "ordinal": 15,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007332en_us",
+  "version": null,
+  "product": "Deployment Guide",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us&page=GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.html"
+}
diff --git a/corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.md b/corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.md
new file mode 100644
index 0000000..b92220f
--- /dev/null
+++ b/corpus/hvm_deployment_guide/GUID-EF5CE241-8260-484D-95C1-6CDEAE24D932.md
@@ -0,0 +1,27 @@
+# Installation overview
+
+To install HPE Morpheus VM Essentials, you must install the HVM OS on all hosts and deploy the VM Essentials manager as a virtual appliance on one of them. The overview of the installation process is outlined below.
+
+- Install the HVM OS Install ISO provided by HPE.
+
+  - Go to [My HPE Software Center](https://myenterpriselicense.hpe.com/cwp-ui/product-details/HPE_VME_EVAL/-/sw360_hpe_internal).
+  - Click **Go to Download Page**.
+  - Download the ISO: **HVM\_Install\_\*\*\*\*\*\*.iso**
+
+  This ISO will get the base system up and running including all the required packages to create and run virtual machines.
+
+  See [Installing HVM OS on host servers](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html).
+- Patch the HVM host to make sure it’s running the latest package versions
+
+  See Step 8 in [Installing HVM OS on host servers](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-28F18596-4902-4CD1-83F3-1411430C5534.html).
+- Configure the HVM hosts’ networks
+
+  See [Configuring the HVM host using the hpe-vm console](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-ADC37453-056E-43C8-8177-8211A44790FD.html).
+- Deploy the VM Essentials manager using the VM Essentials Console on one of the hosts
+
+  See [Installing the VM Essentials manager](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-D8A861D9-D9B6-4D63-8AE7-AD84BCE14289.html).
+- Launch the VM Essentials manager UI, apply the license and configure go through the initial configuration process. Note that a short-term evaluation license will automatically be applied for testing purposes if a permanent license is not immediately available
+
+  See [Configuring the VM Essentials manager for initial setup](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-456E190C-E912-4079-A691-8D2368D63748.html).
+
+![HVM OS installation](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/GUID-D5A7A8B6-F5A2-463F-A7B1-A201B30BEDD0-high.png)
diff --git a/corpus/hvm_release_notes_8_1_0/sd00007497en_us.json b/corpus/hvm_release_notes_8_1_0/sd00007497en_us.json
new file mode 100644
index 0000000..baad422
--- /dev/null
+++ b/corpus/hvm_release_notes_8_1_0/sd00007497en_us.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_release_notes_8_1_0",
+  "page_id": "sd00007497en_us",
+  "title": "v8.1.0 Release Notes",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007497en_us",
+  "version": "8.1.0",
+  "product": "Release Notes",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007497en_us",
+  "topic_cluster": {
+    "clustering_title": "v8.1.0 Release Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_release_notes_8_1_1",
+        "page_id": "sd00007609en_us",
+        "clustering_title": "v8.1.1 Release Notes"
+      },
+      {
+        "bundle_id": "hvm_release_notes_8_1_2",
+        "page_id": "sd00007734en_us",
+        "clustering_title": "v8.1.2 Release Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_release_notes_8_1_0/sd00007497en_us.md b/corpus/hvm_release_notes_8_1_0/sd00007497en_us.md
new file mode 100644
index 0000000..f8f039c
--- /dev/null
+++ b/corpus/hvm_release_notes_8_1_0/sd00007497en_us.md
@@ -0,0 +1,54 @@
+# v8.1.0 Release Notes
+
+# v8.1.0 LTS Release Notes
+
+- Compatible Plugin API version: 1.3.0
+- Compatible HPE Morpheus VM Essentials Worker version: 5.4.8+
+
+Release Dates
+
+- v8.1.0 February 2026
+
+IMPORTANT
+
+After upgrading to v8.1.0, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
+
+# New Features
+
+Alletra MP Plugin
+:   - For complete update details, see the [Alletra MP plugin release notes](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007519en_us)
+
+Appliance
+:   - There is now a single binary installer for both HPE Morpheus Enterprise Software and HPE Morpheus VM Essentials Software. Feature access is controlled solely by licensing. Previously, HPE Morpheus Enterprise and HPE Morpheus VM Essentials had separate binary packages
+    - For newly-installed environments without a paid license configured, the evaluation period has been extended from 30 to 60 days
+
+Aruba CX Plugin
+:   - Version 1.9.0 of the plugin has been released
+    - The serial numbers and health status for each switch are now shown within the network tab of the integration detail
+    - Other internal improvements
+
+Aruba CX DSS Plugin
+:   - Version 1.5.0 of the plugin has been released
+    - Users may now specify a Policy Distribution Target (PDT) when creating a DSS port group
+
+HVM
+:   - Added vCPU placement (NUMA and L3 boundaries) control for HVM clusters
+
+Library
+:   - HPE Morpheus VM Essentials now includes a default library of example images that can be provisioned to HVM Clusters or integrated VMware Clouds right out of the box
+
+Security
+:   - Updates to internal dependency libraries to close potential security vulnerabilities
+
+Tenants
+:   - Storage volume detail pages now show the volume UUID
+
+# Fixes
+
+API & CLI
+:   - Improved the efficiency of making calls to list instances (/api/instances) which, in some environments, could be slow to respond
+
+HVM
+:   - Fixed an issue that caused GFS2 to change to a read-only state when rebooting the HVM Host
+
+Published: February 2026
diff --git a/corpus/hvm_release_notes_8_1_1/sd00007609en_us.json b/corpus/hvm_release_notes_8_1_1/sd00007609en_us.json
new file mode 100644
index 0000000..ada974a
--- /dev/null
+++ b/corpus/hvm_release_notes_8_1_1/sd00007609en_us.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_release_notes_8_1_1",
+  "page_id": "sd00007609en_us",
+  "title": "v8.1.1 Release Notes",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007609en_us",
+  "version": "8.1.1",
+  "product": "Release Notes",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007609en_us",
+  "topic_cluster": {
+    "clustering_title": "v8.1.1 Release Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_release_notes_8_1_0",
+        "page_id": "sd00007497en_us",
+        "clustering_title": "v8.1.0 Release Notes"
+      },
+      {
+        "bundle_id": "hvm_release_notes_8_1_2",
+        "page_id": "sd00007734en_us",
+        "clustering_title": "v8.1.2 Release Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_release_notes_8_1_1/sd00007609en_us.md b/corpus/hvm_release_notes_8_1_1/sd00007609en_us.md
new file mode 100644
index 0000000..7c0f4a0
--- /dev/null
+++ b/corpus/hvm_release_notes_8_1_1/sd00007609en_us.md
@@ -0,0 +1,40 @@
+# v8.1.1 Release Notes
+
+# v8.1.1 LTS Release Notes
+
+- Compatible Plugin API version: 1.3.3
+- Compatible HPE Morpheus VM Essentials Worker version: 5.4.8+
+
+Release Dates
+
+- v8.1.1 March 2026
+
+IMPORTANT
+
+After upgrading to v8.1.1, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
+
+# New Features
+
+Aruba CX DSS Plugin
+:   - Updated the add/edit DSS port group modal to allow users to select one or more security groups
+    - Renamed "Default Firewall Policy" field to "Firewall"
+    - Users may now (optionally) make a Security Group selection for DSS Port Groups
+
+Catalog
+:   - Added CentOS 10 Stream image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+    - Added Debian 13 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+    - Added Alma Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+    - Added Rocky Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+
+HVM
+:   - HVM Host hardware sensor data can now be surfaced into the UI. See HVM cluster documentation for details on configuring hosts to gather and surface this data
+
+# Fixes
+
+Instances
+:   - Fixed manually added VMs, converted to managed, still appearing as discovered
+
+Migrations
+:   - Fixed OVA export timeouts in vCenter which were left even after successful migrations
+
+Published: March 2026
diff --git a/corpus/hvm_release_notes_8_1_2/sd00007734en_us.json b/corpus/hvm_release_notes_8_1_2/sd00007734en_us.json
new file mode 100644
index 0000000..37bde8c
--- /dev/null
+++ b/corpus/hvm_release_notes_8_1_2/sd00007734en_us.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_release_notes_8_1_2",
+  "page_id": "sd00007734en_us",
+  "title": "v8.1.2 Release Notes",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007734en_us",
+  "version": "8.1.2",
+  "product": "Release Notes",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007734en_us",
+  "topic_cluster": {
+    "clustering_title": "v8.1.2 Release Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_release_notes_8_1_0",
+        "page_id": "sd00007497en_us",
+        "clustering_title": "v8.1.0 Release Notes"
+      },
+      {
+        "bundle_id": "hvm_release_notes_8_1_1",
+        "page_id": "sd00007609en_us",
+        "clustering_title": "v8.1.1 Release Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_release_notes_8_1_2/sd00007734en_us.md b/corpus/hvm_release_notes_8_1_2/sd00007734en_us.md
new file mode 100644
index 0000000..92b470a
--- /dev/null
+++ b/corpus/hvm_release_notes_8_1_2/sd00007734en_us.md
@@ -0,0 +1,52 @@
+# v8.1.2 Release Notes
+
+# v8.1.2 LTS Release Notes
+
+- Compatible Plugin API version: 1.3.4
+- Compatible HPE Morpheus VM Essentials Worker version: 5.4.8+
+
+Release Dates
+
+- v8.1.2 April 2026
+
+IMPORTANT
+
+After upgrading to v8.1.2, it is recommended to check for HVM Host agent upgrades as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host. Though many do, it is possible that some version upgrade hops will not contain an HVM Host agent upgrade.
+
+# New Features
+
+Localization
+:   - Added support for the Japanese keyboard layout (101/102 hardware) on hypervisor console sessions using the HPE Morpheus key extension (VMware, vCD, and HVM/KVM). It also includes a new keyboard tips pop-over in the console UI ("?" button). Japanese keyboard layout on 106/109 hardware is a planned future enhancement
+
+# Fixes
+
+API & CLI
+:   - Errors are no longer returned when sending valid DELETE calls to `/api/clusters/{cluster_id}/servers/{server_id}`
+    - Instance resizes to add or remove network interfaces (`PUT /api/instances/{id}/resize`) on HVM or VMware Instances no longer return success messages without actually changing the network interface(s)
+
+HVM
+:   - Fixed VM clones failing when the storage datastore type was changed (ex. local storage to Alletra plugin storage) from the original VM to the clone VM
+    - After restoring a VM from SimpliVity backup and successfully reconfiguring the restored VM, it can now be powered on successfully
+    - HVM Hosts will no longer fail to enter maintenance mode when a VM being live migrated to another Host transitions to a shut off state during migration
+    - Fixed an issue where certain maintenance mode sequences could cause HVM hosts to go offline or become fenced
+    - Disabling networks (unmarking the Active checkbox and saving) will no longer cause spontaneous changes to the "Enable IPV4" and/or the "DHCP Server" checkboxes on the next edit
+    - Volume attach/detach operations on VirtIO controllers no longer fail when attempted while snapshots are in progress
+    - Fixed intermittent provisioning failures when multiple VMs are simultaneously provisioned using the copy operation
+    - Fixed AltGR key input for HVM console sessions
+
+Kubernetes
+:   - Updating worker node counts for Azure AKS clusters now works properly
+
+Labels
+:   - Fixed Cloud filtering by Label for Clouds shared down to child Tenants from a parent Tenant
+
+NSX
+:   - When NSX segments are shared across multiple clusters in a VDC, Morpheus can now associate the NSX segment with multiple vCenter segments
+
+Security
+:   - Added security enhancements
+
+Virtual Images
+:   - Creating Windows VMs with static IP addresses when cloudinit (Cloudbase-init) is set on the Virtual Image now works
+
+Published: April 2026
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json b/corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
new file mode 100644
index 0000000..3346502
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+  "title": "Global Backups Settings",
+  "ordinal": 205,
+  "parent_title": "Initial Backups Setup",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html",
+  "topic_cluster": {
+    "clustering_title": "Global Backups Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+        "clustering_title": "Global Backups Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+        "clustering_title": "Global Backups Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md b/corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
new file mode 100644
index 0000000..d93a136
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
@@ -0,0 +1,27 @@
+# Global Backups Settings
+
+VM Essentials Backups can be enabled under Administration > Settings > Backups.
+
+Scheduled Backups
+:   When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
+
+Create Backups
+:   When enabled, VM Essentials will automatically configure backup jobs for Instances at provision time.
+
+Backup Appliance
+:   When enabled, a Backup will be created to backup the VM Essentials appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
+
+Default Backup Bucket
+:   From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
+
+Default Backup Schedule
+:   From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+Backup Retention Count
+:   The default maximum number of successful backups to retain.
+
+Default Synthetic Full Backup Enabled
+:   When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
+
+Default Synthetic Full Backups Schedule
+:   From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json b/corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
new file mode 100644
index 0000000..aa74071
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+  "title": "Scoping Services",
+  "ordinal": 172,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html",
+  "topic_cluster": {
+    "clustering_title": "Scoping Services",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+        "clustering_title": "Scoping Services"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+        "clustering_title": "Scoping Services"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md b/corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
new file mode 100644
index 0000000..8b76936
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
@@ -0,0 +1,20 @@
+# Scoping Services
+
+NETWORKING
+:   Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
+
+IPAM
+:   IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
+
+SECURITY
+:   Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
+
+DNS
+:   DNS integrations will populate domains in the Infrastructure  >  Network  >  Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+Service Registry
+:   Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+NOTE
+
+Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json b/corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
new file mode 100644
index 0000000..b008ea8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+  "title": "Group and Tenant Access",
+  "ordinal": 143,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html",
+  "topic_cluster": {
+    "clustering_title": "Group and Tenant Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+        "clustering_title": "Group and Tenant Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+        "clustering_title": "Group and Tenant Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md b/corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
new file mode 100644
index 0000000..37ab560
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
@@ -0,0 +1,3 @@
+# Group and Tenant Access
+
+Networks can be configured to provide specific Group access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json b/corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
new file mode 100644
index 0000000..b7af05c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+  "title": "Cloud-Init Agent install mode",
+  "ordinal": 39,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init Agent install mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+        "clustering_title": "Cloud-Init Agent install mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+        "clustering_title": "Cloud-Init Agent install mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md b/corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
new file mode 100644
index 0000000..28af5bf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
@@ -0,0 +1,4 @@
+# Cloud-Init Agent install mode
+
+- Cloud-Init is configured in Administration > Settings > Provisioning section
+- Provisioned image has Cloud-Init (Linux) or Cloudbase-Init (Windows) installed
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json b/corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
new file mode 100644
index 0000000..1ca36cb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+  "title": "Activity",
+  "ordinal": 20,
+  "parent_title": "Operations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md b/corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
new file mode 100644
index 0000000..8a75a04
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
@@ -0,0 +1,11 @@
+# Activity
+
+The Activity section displays a recent activity report for Auditing. VM Essentials defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, etc… This view can be searched and filtered by type, user, and date range.
+
+![Activity page](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-01147D13-F369-4441-B97D-9354DA79DF93-high.png)
+
+**Subtopics**  
+
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html)**
+- **[Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html)**
+- **[History](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.json b/corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
new file mode 100644
index 0000000..179feda
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+  "title": "Add ArubaCX Integration to a Cluster",
+  "ordinal": 354,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html",
+  "topic_cluster": {
+    "clustering_title": "Add ArubaCX Integration to a Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+        "clustering_title": "Add ArubaCX Integration to a Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+        "clustering_title": "Add ArubaCX Integration to a Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.md b/corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
new file mode 100644
index 0000000..33b98cb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
@@ -0,0 +1,10 @@
+# Add ArubaCX Integration to a Cluster
+
+## Procedure
+
+1. In Infrastructure > Clusters select the target Cluster
+2. Select the Edit icon for the Cluster
+3. In the “Integrations” dropdown, select an available ArubaCX Integration
+4. Save Changes 
+
+   ![../../_images/arubacx_edit_cluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-6978CDB6-74D2-492A-B461-2F0EC476F018-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.json b/corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.json
new file mode 100644
index 0000000..1510330
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+  "title": "Group Access",
+  "ordinal": 160,
+  "parent_title": "Editing Domain Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-06426E05-BE70-4917-89E3-153236303513.html",
+  "topic_cluster": {
+    "clustering_title": "Group Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+        "clustering_title": "Group Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+        "clustering_title": "Group Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.md b/corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.md
new file mode 100644
index 0000000..4659567
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-06426E05-BE70-4917-89E3-153236303513.md
@@ -0,0 +1,3 @@
+# Group Access
+
+The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json b/corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
new file mode 100644
index 0000000..e2af541
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+  "title": "Currency Settings",
+  "ordinal": 271,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html",
+  "topic_cluster": {
+    "clustering_title": "Currency Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+        "clustering_title": "Currency Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+        "clustering_title": "Currency Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md b/corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
new file mode 100644
index 0000000..44fd21e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
@@ -0,0 +1,3 @@
+# Currency Settings
+
+In VM Essentials, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, VM Essentials allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json b/corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
new file mode 100644
index 0000000..af91b9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+  "title": "NFSv3 File Shares",
+  "ordinal": 189,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html",
+  "topic_cluster": {
+    "clustering_title": "NFSv3 File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+        "clustering_title": "NFSv3 File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+        "clustering_title": "NFSv3 File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md b/corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
new file mode 100644
index 0000000..c63592d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
@@ -0,0 +1,80 @@
+# NFSv3 File Shares
+
+## About this task
+
+NOTE
+
+Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
+
+NOTE
+
+Upon save VM Essentials will create a persistent mount owned by `morpheus-app.morpheus-app` on the VM Essentials Appliance for the NFSv3 File Share. The VM Essentials appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before VM Essentials is able to successfully mount the share.
+
+To Add a NFSv3 File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select NFSv3 from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   HOST
+   :   Enter the File Share path on the local VM Essentials Appliance.
+
+   EXPORT FOLDER
+   :   Enter the NFSv3 Folder
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+**Subtopics**  
+
+- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json b/corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
new file mode 100644
index 0000000..8e5de9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+  "title": "Add HPE Alletra MP Storage",
+  "ordinal": 366,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html",
+  "topic_cluster": {
+    "clustering_title": "Add HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+        "clustering_title": "Add HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+        "clustering_title": "Add HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md b/corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
new file mode 100644
index 0000000..a7499a6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
@@ -0,0 +1,33 @@
+# Add HPE Alletra MP Storage
+
+## About this task
+
+The first step is to create a storage server in VM Essentials. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage
+2. In the “Servers” tab, Click the + ADD button
+3. From the ADD STORAGE SERVER wizard, input the following: 
+
+   NAME:
+   :   Name of the storage server in VM Essentials
+
+   TYPE:
+   :   Select “HPE Alletra MP”
+
+   URL:
+   :   URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
+
+   USERNAME:
+   :   Add your administrative user account
+
+   PASSWORD:
+   :   Add your administrative user account password
+4. Select SAVE CHANGES
+
+## Results
+
+![../../_images/add-storage-server.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-432FC4EC-3961-492E-9423-55CC7E6BCACA-high.png)
+
+The Storage Server will be added and displayed in the Datastore tab.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json b/corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
new file mode 100644
index 0000000..4509b61
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+  "title": "Plans",
+  "ordinal": 238,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md b/corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
new file mode 100644
index 0000000..7f75bad
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
@@ -0,0 +1,5 @@
+# Plans
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json b/corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
new file mode 100644
index 0000000..38c151a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+  "title": "Cloud Detail View",
+  "ordinal": 93,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Detail View",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+        "clustering_title": "Cloud Detail View"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+        "clustering_title": "Cloud Detail View"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md b/corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
new file mode 100644
index 0000000..7d0b40f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
@@ -0,0 +1,22 @@
+# Cloud Detail View
+
+The Cloud Detail view shows metrics on health, sync status, resource utilization statistics, and resource counts for hosts, virtual machines, or any other constructs under the umbrella of the selected Cloud.
+
+From the Cloud list page, select the name of a Cloud to display that Cloud’s detail page. You’ll notice the following actions are available:
+
+EDIT
+:   Edit the setup configuration of the Cloud.
+
+REFRESH
+:   Force a sync with the Cloud.
+
+DELETE
+:   Delete the Cloud from VM Essentials.
+
+IMPORTANT
+
+All Instances, managed Hosts, and VMs associated with the Cloud must be removed prior to deleting a Cloud.
+
+**Subtopics**  
+
+- **[Cloud Detail Tabs](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json b/corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
new file mode 100644
index 0000000..26e267a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+  "title": "Environments",
+  "ordinal": 286,
+  "parent_title": "Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
+  "topic_cluster": {
+    "clustering_title": "Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md b/corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
new file mode 100644
index 0000000..1d32123
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
@@ -0,0 +1,5 @@
+# Environments
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json b/corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
new file mode 100644
index 0000000..eccc92e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+  "title": "Overview",
+  "ordinal": 356,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md b/corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
new file mode 100644
index 0000000..8018b5a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
@@ -0,0 +1,11 @@
+# Overview
+
+The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus VM Essentials Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
+
+Implemented as a VM Essentials `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for VM Essentials environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM cluster.
+
+On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. VM Essentials integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM hosts in the HVM cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
+
+The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM cluster.
+
+Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json b/corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
new file mode 100644
index 0000000..1262a49
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+  "title": "Editing Domain Permissions",
+  "ordinal": 159,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Domain Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+        "clustering_title": "Editing Domain Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+        "clustering_title": "Editing Domain Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md b/corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
new file mode 100644
index 0000000..8133090
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
@@ -0,0 +1,7 @@
+# Editing Domain Permissions
+
+To edit visibility permissions for a domain, navigate to Infrastructure  >  Network  >  Domains. In the row for the selected domain, click MORE > Permissions. Within the Permissions modal, set Group access permissions.
+
+**Subtopics**  
+
+- **[Group Access](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-06426E05-BE70-4917-89E3-153236303513.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json b/corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
new file mode 100644
index 0000000..e9cbf91
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+  "title": "Disabling Two-Factor Authentication",
+  "ordinal": 299,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.html",
+  "topic_cluster": {
+    "clustering_title": "Disabling Two-Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+        "clustering_title": "Disabling Two-Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+        "clustering_title": "Disabling Two-Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md b/corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
new file mode 100644
index 0000000..13d174a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
@@ -0,0 +1,5 @@
+# Disabling Two-Factor Authentication
+
+When two-factor authentication is set up, this section contains two buttons: DISABLE 2FA and GET 2FA CODE. To generate a new QR code and configure an authenticator app, click GET 2FA CODE. Once you generate a new QR code, the old one is no longer valid. At that point you must reconfigure your authenticator app or you will not be able to access your account on the next login attempt. Generating a new QR code requires your password.
+
+To disable 2FA, click DISABLE 2FA. This action does not require a password.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json b/corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
new file mode 100644
index 0000000..31d89a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+  "title": "Openstack Swift Buckets",
+  "ordinal": 183,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.html",
+  "topic_cluster": {
+    "clustering_title": "Openstack Swift Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+        "clustering_title": "Openstack Swift Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+        "clustering_title": "Openstack Swift Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md b/corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
new file mode 100644
index 0000000..e09082b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
@@ -0,0 +1,77 @@
+# Openstack Swift Buckets
+
+## About this task
+
+To Add an OpenStack Swift Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Openstack Swift from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   USERNAME
+   :   Openstack Swift Username
+
+   API KEY
+   :   Openstack Swift API Key
+
+   BUCKET NAME
+   :   Enter existing Openstack Swift Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   IDENTITY URL
+   :   Openstack Swift Identity URL
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json b/corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
new file mode 100644
index 0000000..eb90fa0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+  "title": "Health Levels",
+  "ordinal": 260,
+  "parent_title": "VM Essentials Health",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.html",
+  "topic_cluster": {
+    "clustering_title": "Health Levels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+        "clustering_title": "Health Levels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+        "clustering_title": "Health Levels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md b/corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
new file mode 100644
index 0000000..31250f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
@@ -0,0 +1,10 @@
+# Health Levels
+
+Health levels provide a live representation of the current memory and CPU load on the appliance. Bear in mind that in an HA appliance, this data will be specific to the appliance node you happen to be using. By default, VM Essentials does not include any endpoint or UI tool which can show you the currently used app node. However, a plugin has been developed which can surface this information if needed. See [this thread](https://discuss.morpheusdata.com/t/custom-ping-endpoint-via-morpheus-plugin/389) in the VM Essentials official forums for additional details about accessing and using the plugin.
+
+- **Morpheus CPU:** Instantaneous amount of CPU capacity in use by VM Essentials processes
+- **System CPU:** Instantaneous amount of CPU capacity in use by all processes
+- **Morpheus Memory:** Instantaneous amount of system memory currently in use by VM Essentials processes (see the Knowledge Base article linked in the TIP box below for more information on how VM Essentials claims and manages available memory)
+- **System Memory:** Instantaneous amount of total system memory currently claimed (this is commonly a high percentage, see the TIP box below)
+- **Used Swap:** Instantaneous amount of total available system swap in use
+- **Storage:** The instantaneous percentage utilization of the filesystem mounted at “/”
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json b/corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
new file mode 100644
index 0000000..ee4334a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+  "title": "Data Stores",
+  "ordinal": 190,
+  "parent_title": "NFSv3 File Shares",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html",
+  "topic_cluster": {
+    "clustering_title": "Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+        "clustering_title": "Data Stores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+        "clustering_title": "Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md b/corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
new file mode 100644
index 0000000..31b9c81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
@@ -0,0 +1,5 @@
+# Data Stores
+
+Data Stores are logical divisions of underlying storage disk. Organizations may use them to divide and track cloud resources by team or department. When integrating certain Cloud types, VM Essentials will onboard all existing data stores and administrators can then make them available to Groups as needed. At provision time, when applicable based on Cloud and Layout, users can select the datastore they wish to provision to.
+
+Here within the Data Store view in the storage section, users can see a list of data stores for each Cloud. In the row for each Cloud, the storage type, associated Cloud, and permissions information are shown.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json b/corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
new file mode 100644
index 0000000..d35c060
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+  "title": "Create HPE ANW DSS Port Group Network",
+  "ordinal": 360,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.html",
+  "topic_cluster": {
+    "clustering_title": "Create HPE ANW DSS Port Group Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+        "clustering_title": "Create HPE ANW DSS Port Group Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+        "clustering_title": "Create HPE ANW DSS Port Group Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md b/corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
new file mode 100644
index 0000000..c0064bf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
@@ -0,0 +1,24 @@
+# Create HPE ANW DSS Port Group Network
+
+## About this task
+
+To create an HPE ANW DSS Port Group network, follow these steps:
+
+## Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select + Add Network > HPE ANW DSS Port Group 
+
+   ![../../_images/3.1_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-3CE7AFEC-D544-4E9A-9277-1343D8DCD7BE-high.png)
+3. Select the Network Service in the CREATE NETWORK form: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-3A253CC3-F827-4CA3-A2C5-58F8FEC8C30D-high.png)
+4. Enter the following details in the CREATE NETWORK form. Note that the values in the screenshot are reference examples. Input only the values intended for the actual network: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-34B08F15-1A6E-4E91-97C0-59D865049E4A-high.png)
+5. Save the network by clicking on Save changes. 
+
+   ![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-EE617F32-2D8B-4384-9EDA-16C02DED8ADF-high.png)
+6. The network will be created and displayed in the list of networks. 
+
+   ![../../_images/3.4_network_created.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-2ABDBDC9-8594-4248-B7F8-056488423C77-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json b/corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
new file mode 100644
index 0000000..db62069
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+  "title": "Credentials",
+  "ordinal": 196,
+  "parent_title": "Trust",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.html",
+  "topic_cluster": {
+    "clustering_title": "Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+        "clustering_title": "Credentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+        "clustering_title": "Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md b/corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
new file mode 100644
index 0000000..0370184
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
@@ -0,0 +1,27 @@
+# Credentials
+
+The credentials section allows for various credential types to be securely stored and called back when necessary, such as when creating new integrations with Cloud accounts or other outside technologies. Credentials can also be used to populate REST-based Option Lists sourced from data behind an authentication wall, as well as to run automation Tasks on remote targets that require authentication. Credentials are stored internally and securely on the VM Essentials appliance. The following credential pair types are currently supported:
+
+- Access Key and Secret Key
+- Client ID and Secret
+- Email and Private Key
+- OAuth 2.0
+- Tenant, Username, and Keypair
+- Username and API Key
+- Username and Keypair
+- Username and Password
+- Username, Password, and Keypair
+
+To create a new credential set, click + ADD and then select the type of credential set you’d like to store. Complete the following:
+
+- **CREDENTIAL STORE:** Select “Internal”, an integrated external Cypher store (if any), or an integrated Hashicorp Vault server (if any). See the section below for instructions on integrating with Vault or standing up and integrating with an external Cypher store.
+- **NAME:** A name for the credential set in VM Essentials
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **CREDENTIAL VALUES:** Depending on the credential pair type selected (listed above), the remaining fields will be specific to the chosen type. See the next section for a more complete walkthrough on storing and using OAuth 2.0 credentials
+
+![../../_images/addCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-6107BD26-E1BA-4F6E-888A-10CEDF3C01D7-high.png)
+
+Finally, click ADD CREDENTIALS. Once saved, the credential set will be available for selection where appropriate in VM Essentials UI. In the screenshot below, I’m integrating a new VMware Cloud. In the credentials section, I have the following options: Creating (and using) a new Username and Password credential set (which includes the option to save internally or to an external Cypher store), choosing a previously-stored credential set, or simply entering my credentials locally and not saving them for reuse.
+
+![../../_images/useCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-714A8DE9-4992-4DB9-B9E2-5CAAD363B7A2-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json b/corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
new file mode 100644
index 0000000..724bee1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+  "title": "Creating Service Plans for GPU Hardware Passthrough",
+  "ordinal": 132,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md b/corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
new file mode 100644
index 0000000..478f1e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
@@ -0,0 +1,7 @@
+# Creating Service Plans for GPU Hardware Passthrough
+
+When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
+
+To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
+
+![../../_images/gpuPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-FEF30612-0724-4835-9310-79D70E4641F1-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json b/corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
new file mode 100644
index 0000000..1a027da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+  "title": "Creating Wikis",
+  "ordinal": 18,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Wikis",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+        "clustering_title": "Creating Wikis"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+        "clustering_title": "Creating Wikis"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md b/corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
new file mode 100644
index 0000000..801e3da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
@@ -0,0 +1,13 @@
+# Creating Wikis
+
+The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
+
+Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
+
+![create wiki](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-4029426C-1AA2-4873-AE1C-CB4677EFB0F7-high.png)
+
+Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many VM Essentials constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
+
+IMPORTANT
+
+All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json b/corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
new file mode 100644
index 0000000..84bb08c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+  "title": "Linux Settings",
+  "ordinal": 302,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md b/corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
new file mode 100644
index 0000000..121937b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
@@ -0,0 +1,14 @@
+# Linux Settings
+
+When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Linux user
+- **Password:** The password that will be used with your Linux user (optional if specifying key)
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
+
+WARNING
+
+If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_linux_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-98554851-1F7D-4D05-A502-2FB93933551A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json b/corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
new file mode 100644
index 0000000..fa01052
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+  "title": "Adding Network Groups",
+  "ordinal": 147,
+  "parent_title": "Network Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+        "clustering_title": "Adding Network Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+        "clustering_title": "Adding Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md b/corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
new file mode 100644
index 0000000..052ae19
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
@@ -0,0 +1,19 @@
+# Adding Network Groups
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks Groups
+2. Select ADD
+3. Enter the following: 
+
+   Group info:
+   :   - Name: Name of the Network Group in VM Essentials
+       - Description: Details of the Network Group in VM Essentials
+
+   Networks
+   :   - Search for and select target Networks for the Network Group
+       - Search for and select target Subnets for the Network Group
+
+   Group Access
+   :   - Set Group Access for the Network Group. Group access controls which Groups at provision time will have access to this resource. Select “all” (default) to give workloads provisioned to any Group access to this resource. If this resource should be restricted only to workloads provisioned to specific Groups, select all that apply.
+4. Select SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json b/corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
new file mode 100644
index 0000000..65c126f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+  "title": "System Status",
+  "ordinal": 8,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.html",
+  "topic_cluster": {
+    "clustering_title": "System Status",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+        "clustering_title": "System Status"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+        "clustering_title": "System Status"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md b/corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
new file mode 100644
index 0000000..d7fe97b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
@@ -0,0 +1,3 @@
+# System Status
+
+System status gives a high-level view of the health of the appliance. More detailed information can be viewed on the appliance health detail page (Administration > Health) and a more detailed breakdown of the meaning of each status indicator is in [VM Essentials Health](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json b/corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
new file mode 100644
index 0000000..67286d5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+  "title": "Selecting a Domain while provisioning an Instance",
+  "ordinal": 164,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.html",
+  "topic_cluster": {
+    "clustering_title": "Selecting a Domain while provisioning an Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+        "clustering_title": "Selecting a Domain while provisioning an Instance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+        "clustering_title": "Selecting a Domain while provisioning an Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md b/corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
new file mode 100644
index 0000000..fdcd970
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
@@ -0,0 +1,6 @@
+# Selecting a Domain while provisioning an Instance
+
+## Procedure
+
+1. While creating an instance, in the Configure section, expand the DNS Options.
+2. Select Domain from the Domain dropdown.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json b/corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
new file mode 100644
index 0000000..fe7280f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+  "title": "Adding Directory Pools",
+  "ordinal": 114,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Directory Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+        "clustering_title": "Adding Directory Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+        "clustering_title": "Adding Directory Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md b/corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
new file mode 100644
index 0000000..82c26c1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
@@ -0,0 +1,25 @@
+# Adding Directory Pools
+
+Before adding a Directory Pool, identify the path to be used as the datastore location. You may use an existing directory, or you may specify a desired path that doesn't yet exist. HPE Morpheus VM Essentials will handle creation of the directory (if necessary), changing its ownership, and defining the storage pool (along with configuring auto-start) all in the background.
+
+To create a new Directory Pool-type datastore:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. Select the Storage tab and the Datastores subtab
+4. Click ADD
+5. Configure the following:
+
+   1. **NAME:** An identifiable name for the datastore used throughout HPE Morpheus VM Essentials UI
+   2. **DIRECTORY:** Directory Pool
+   3. **TARGET PATH:** Your desired path (does not have to currently exist)
+   4. **IMAGE TARGET:** If selected, this datastore will be made available for storage of virtual images
+6. Click SAVE
+
+![The add directory pool modal](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-F74F45D1-59C7-4B4B-BCA2-726D24B4B76A-high.png)
+
+WARNING
+
+When Directory Pools are removed, the target directory is deleted along with all files contained within. Users should take care not to manually store additional files in Directory Pool-targeted directories as the files could be deleted if a datastore were removed.
+
+![The datastores list showing the newly-added directory pool](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-CA6224CA-4FD9-4E70-8FED-81234ABACC40-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json b/corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
new file mode 100644
index 0000000..521dd1d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+  "title": "NFS Pools Overview",
+  "ordinal": 115,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.html",
+  "topic_cluster": {
+    "clustering_title": "NFS Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+        "clustering_title": "NFS Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+        "clustering_title": "NFS Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md b/corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
new file mode 100644
index 0000000..e42a1fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
@@ -0,0 +1,19 @@
+# NFS Pools Overview
+
+NFS Pools enable an HVM Cluster to use an NFS share as a datastore. The exact steps to configure the NFS share will depend on the storage system providing it, but this section will go over the requirements for creating a compatible share and for adding it to the HVM Cluster via the HPE Morpheus VM Essentials UI.
+
+Administrators only need to set up the NFS server, export the desired directories with the proper permissions and options, and ensure the hosts are able to reach it. HPE Morpheus VM Essentials handles everything else, including mounting directories to the filesystem and handling datastore creation.
+
+Compatible NFS shares must meet the following requirements:
+
+- NFS version 3 or 4
+- The share must allow read and write access
+- The share must be configured with the `no-root-squash` export option
+
+NOTE
+
+NFS version 4 is only supported on HPE Morpheus VM Essentials version 8.0.13 and higher. When using the Migrations feature to move VMware VMs to HVM Clusters targeting an NFS Pool datastore, NFS version 4 must be used.
+
+IMPORTANT
+
+The `no-root-squash` export option is required but typically not set by default. When `no-root-squash` is not set, requests from the NFS client are mapped to an anonymous user on the NFS server, which will result in permissions errors that do not allow the NFS Pool to function correctly. You must set this export option in the `/etc/exports` config file or in a management interface depending on the NFS storage system being utilized.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json b/corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
new file mode 100644
index 0000000..38b48e4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+  "title": "Creating a VM Essentials VMware Image",
+  "ordinal": 331,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a VM Essentials VMware Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+        "clustering_title": "Creating a VM Essentials VMware Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+        "clustering_title": "Creating a VM Essentials VMware Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md b/corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
new file mode 100644
index 0000000..9495c81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
@@ -0,0 +1,7 @@
+# Creating a VM Essentials VMware Image
+
+VM Essentials comes out of the box with a default set of blueprints for use in many modern deployment scenarios. These consist mostly of base operating system images with a few additional adjustments. These adjustments typically include the addition of cloud-init (which is highly recommended to be used in most environments, but not mandatory). However, in many on-premise deployments there are custom image requirements as well as networking requirements. This guide will go over how to create a VMware Images for use within VM Essentials.
+
+NOTE
+
+A VM Essentials appliance may have many vCenter Clouds tied to any number of vCenter appliances. If the same images need to be available to multiple vCenter Clouds, you will need to download the OVF from one vCenter and upload it into the others. At that point you can make multiple VM Essentials Node Types from the images and it will be available to all needed vCenter Clouds. This is a vCenter limitation but one which may not be obvious when provisioning via VM Essentials.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json b/corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
new file mode 100644
index 0000000..d65a67a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+  "title": "Library",
+  "ordinal": 51,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
+  "topic_cluster": {
+    "clustering_title": "Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md b/corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
new file mode 100644
index 0000000..bb976cc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
@@ -0,0 +1,7 @@
+# Library
+
+**Subtopics**  
+
+- **[Labels](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.html)**
+- **[Automation](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json b/corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
new file mode 100644
index 0000000..6ca0006
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+  "title": "Creating Clouds",
+  "ordinal": 92,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+        "clustering_title": "Creating Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+        "clustering_title": "Creating Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md b/corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
new file mode 100644
index 0000000..7b2edac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
@@ -0,0 +1,3 @@
+# Creating Clouds
+
+Clouds can be added from Infrastructure > Clouds or in Infrastructure > Groups > (selected Group) > Clouds. A more detailed guide to adding a VMware vCenter Cloud can be found in the vCenter integration guide. The other available Cloud type, known as Private Cloud, is a generic Cloud type that doesn’t directly integrate with any other technology as the vCenter Cloud type does. Instead Private Cloud-type Clouds are used to house your HVM clusters. Make as many Private Cloud-type Clouds as needed to organize your HVM clusters properly.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json b/corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
new file mode 100644
index 0000000..7082bbe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+  "title": "Backups",
+  "ordinal": 209,
+  "parent_title": "Backups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md b/corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
new file mode 100644
index 0000000..a52ecab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
@@ -0,0 +1,11 @@
+# Backups
+
+In the Backups > Backups section, currently-configured Backups can be viewed and managed, and new Instance, Host and Provider backups be configured. Backups must be tied to a Backup Job, which holds the retention count and the schedule on which the backup should automatically be run. You can create a new Job at the same time as the backup is created or you can create the job ahead of time and associate any new backups to the existing job.
+
+NOTE
+
+Role permissions for Backups determine which backups will be accessible to the individual user.
+
+**Subtopics**  
+
+- **[Create an Instance Backup](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9DA38943-BF95-446D-AB09-32323160D51B.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json b/corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
new file mode 100644
index 0000000..c07135b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+  "title": "Deleting Existing Routers",
+  "ordinal": 152,
+  "parent_title": "Routers",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Existing Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+        "clustering_title": "Deleting Existing Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+        "clustering_title": "Deleting Existing Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md b/corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
new file mode 100644
index 0000000..a3b5ee5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
@@ -0,0 +1,7 @@
+# Deleting Existing Routers
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the trash can icon for the appropriate router
+3. Acknowledge the pop-up banner ensuring you wish to delete the router
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json b/corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
new file mode 100644
index 0000000..5777bac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+  "title": "VM Essentials Backup Settings",
+  "ordinal": 285,
+  "parent_title": "Backup Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.html",
+  "topic_cluster": {
+    "clustering_title": "VM Essentials Backup Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+        "clustering_title": "VM Essentials Backup Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+        "clustering_title": "VM Essentials Backup Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md b/corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
new file mode 100644
index 0000000..6ab313c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
@@ -0,0 +1,25 @@
+# VM Essentials Backup Settings
+
+Scheduled Backups
+:   Enable automatic scheduled backups for provisioned instances
+
+Create Backups
+:   When enabled, VM Essentials will automatically configure instances for manual or scheduled backups
+
+Backup Appliance
+:   When enabled, a backup will be created for the VM Essentials appliance database. Select the `Backup` text link to view or edit settings related to the appliance backup
+
+Default Backup Bucket
+:   Select an existing bucket as the default for future backup runs. Click the `Infrastructure Storage` text link to add a new storage bucket to VM Essentials if needed
+
+Default Backup Schedule
+:   Choose a default schedule interval for automated backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
+
+Default Backup Retention
+:   Choose the default number of backups to be retained for automated Instance and appliance backup jobs
+
+Default Synthetic Full Backup enabled
+:   When enabled, full synthetic backups will be on by default in addition to standard backups for supported workload types
+
+Default Synthetic Full Backup Schedule
+:   Choose a default schedule interval for full synthetic backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json b/corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
new file mode 100644
index 0000000..ee62e6a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+  "title": "Roles and Identity Sources",
+  "ordinal": 246,
+  "parent_title": "Roles",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.html",
+  "topic_cluster": {
+    "clustering_title": "Roles and Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+        "clustering_title": "Roles and Identity Sources"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+        "clustering_title": "Roles and Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md b/corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
new file mode 100644
index 0000000..d1711d8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
@@ -0,0 +1,3 @@
+# Roles and Identity Sources
+
+It is very common for large Enterprises to have an existing identity source that they would like to plug in to VM Essentials for authentication. This includes services like LDAP, Active Directory, OKTA, Jump Cloud, One Login, and SAML. When using these services it becomes important to configure a role mapping between the VM Essentials role assignments to the equivalent identity source groups/roles the user belongs to. This is configurable within the identity source management UI. Sections are provided allowing things like LDAP groups to be directly mapped to specific roles within VM Essentials. If a user matches more than one LDAP/role group then both sets of roles are applied to the user automatically. Configuring Identity Sources is done in Administration > Users. Additionally, administrators may opt to lock users to their mapped role in VM Essentials or keep the roles unlocked to manually administer roles in one-off scenarios. See the docs section dedicated to identity sources for more information on configuring the specific SSO technologies VM Essentials supports.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json b/corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
new file mode 100644
index 0000000..fdb9415
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+  "title": "Roles",
+  "ordinal": 243,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md b/corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
new file mode 100644
index 0000000..cf6f270
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
@@ -0,0 +1,7 @@
+# Roles
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.html)**
+- **[Roles and Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.html)**
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json b/corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
new file mode 100644
index 0000000..9e06ae5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+  "title": "Tagging and Metadata",
+  "ordinal": 323,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.html",
+  "topic_cluster": {
+    "clustering_title": "Tagging and Metadata",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+        "clustering_title": "Tagging and Metadata"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+        "clustering_title": "Tagging and Metadata"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md b/corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
new file mode 100644
index 0000000..85e11b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
@@ -0,0 +1,13 @@
+# Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json b/corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
new file mode 100644
index 0000000..7dadd9a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+  "title": "User Process Guides",
+  "ordinal": 306,
+  "parent_title": "Guides",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.html",
+  "topic_cluster": {
+    "clustering_title": "User Process Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+        "clustering_title": "User Process Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+        "clustering_title": "User Process Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md b/corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
new file mode 100644
index 0000000..5307475
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
@@ -0,0 +1,5 @@
+# User Process Guides
+
+**Subtopics**  
+
+- **[Backing Up and Restoring the HPE Morpheus VM Essentials Manager](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json b/corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
new file mode 100644
index 0000000..77d33d4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+  "title": "Failover",
+  "ordinal": 127,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.html",
+  "topic_cluster": {
+    "clustering_title": "Failover",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+        "clustering_title": "Failover"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+        "clustering_title": "Failover"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md b/corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
new file mode 100644
index 0000000..cdb2ade
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
@@ -0,0 +1,15 @@
+# Failover
+
+HVM clusters support automatic failover of running workloads in the event of the loss of a host. Administrators can control the failover behavior through the “Manage Placement” action on any running VM. From the VM detail page, click ACTIONS and select “Manage Placement”. Any VM with a placement strategy of “Auto” or “Failover” will be eligible for an automatic move in the event its host is lost. When the loss of a host does occur, the workload will be up and running from a different cluster host within just a short time if it’s configured to be moved during an automatic failover event. Any VMs pinned to a lost host will not be moved and will not be accessible if the host is lost. When the host is restored, those VMs will be in a stopped state and may be restarted if needed.
+
+![../../_images/threeRunningWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-D85300D8-59A9-406D-99F4-2A83E4812C52-high.png)
+
+Each of these VMs is configured for a different failover strategy. When the host is lost, we should expect to see the first two VMs moved to an available host (since they have the “Auto” and “Failover” placement strategies, respectively). We should not see the third VM moved.
+
+![../../_images/auto.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-4AF17304-D863-46CD-B761-F76CA83B5DA1-high.png) ![../../_images/failover.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-450A2043-9995-4352-B52F-0D85D7A9500E-high.png) ![../../_images/pinned.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-3C5798EF-8010-4C2C-A9C1-B1A07D5BBCE3-high.png)
+
+After loss of the host these three VMs were running on, we can see the lost host still has one associated VM in a stopped state. The other two VMs are running on a second host which is still available.
+
+![../../_images/lostNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-69BB84AC-5461-4818-A90F-10BB7308E937-high.png) ![../../_images/liveNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-688399E1-CBDA-4B89-AC61-80CF6FCBEBCD-high.png)
+
+When the lost host returns, the moved VMs will come back to their original host. The third VM is associated with this host as well and is in a stopped state until it is manually restarted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json b/corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
new file mode 100644
index 0000000..04b294e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+  "title": "Advanced",
+  "ordinal": 326,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-1EB800EB-6832-487E-BB11-07D8520003CF.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+        "clustering_title": "Advanced"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+        "clustering_title": "Advanced"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md b/corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
new file mode 100644
index 0000000..69d8995
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
@@ -0,0 +1,11 @@
+# Advanced
+
+There are several advanced features provided within VM Essentials that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the VM Essentials appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires VM Essentials v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in VM Essentials via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via VM Essentials. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json b/corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
new file mode 100644
index 0000000..f34f42d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+  "title": "Overview",
+  "ordinal": 314,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md b/corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
new file mode 100644
index 0000000..956d25f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
@@ -0,0 +1,3 @@
+# Overview
+
+VMware is a very common cloud integration choice supported by VM Essentials . They have provided a top notch virtualization solution and one might argue pioneered the virtualization space altogether. As such, many companies utilize this technology and all the features that come with it, so VM Essentials covers a broad feature set in vCenter.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json b/corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
new file mode 100644
index 0000000..8f7f3a0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+  "title": "Allow Custom Config",
+  "ordinal": 62,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.html",
+  "topic_cluster": {
+    "clustering_title": "Allow Custom Config",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+        "clustering_title": "Allow Custom Config"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+        "clustering_title": "Allow Custom Config"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md b/corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
new file mode 100644
index 0000000..2784124
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
@@ -0,0 +1,9 @@
+# Allow Custom Config
+
+When “Allow Custom Config” is marked on a Task, the user is shown a text area for custom configuration when the Task is executed manually from the Tasks List Page. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+**Subtopics**  
+
+- **[Example JSON Map:](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.html)**
+- **[Task Types](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.html)**
+- **[Task Management](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json b/corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
new file mode 100644
index 0000000..6dccbf6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+  "title": "Appliance Settings",
+  "ordinal": 265,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+        "clustering_title": "Appliance Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+        "clustering_title": "Appliance Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md b/corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
new file mode 100644
index 0000000..6c34e94
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
@@ -0,0 +1,59 @@
+# Appliance Settings
+
+Appliance URL
+:   The default URL used for Agent install and Agent functionality. All Instances and Hosts must be able to resolve and reach this URL over 443 for successful agent install and communication.
+
+NOTE
+
+Alternate Appliance URLs can be configured per Cloud in the Edit Cloud  >  Advanced Options section.
+
+Internal Appliance URL (PXE)
+:   For PXE-Boot your appliance needs to be routable directly with minimal NAT masquerading. This allows one to override the default appliance url endpoint for use by the PXE Server. If this is unset, the default appliance url will be used instead.
+
+API Allowed Origins
+:   A CORS-related field which specifies the origins that are allowed to access the VM Essentials API. For example, if you were designing a web application which needed to make AJAX calls to VM Essentials API. The origins should be specified here. By default, all origins are allowed. When this field is filled, an exclusive whitelist of allowed origins is established.
+
+Cloud Sync Interval
+:   Data is refreshed through cloud integrations at the interval specified here in seconds, the default value is 300 seconds (five minutes). Appliances managing a very large number of clouds may be adversely affected by setting this value too low.
+
+Cluster Sync Interval
+:   Data is refreshed through provisioned Clusters at the interval specified here in seconds, the default value is 60 seconds. Appliances managing a very large number of Clusters may be adversely affected by setting this value too low.
+
+Usage Retainment
+:   Determines how many days to keep account usage (metered costing data) records. Retainment period is not set by default. Usage records will remain indefinitely if Usage Retainment is not set. Note this does not affect generated Invoice records.
+
+Invoice Retainment
+:   Enter the number of days VM Essentials should keep invoice records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large invoice database tables can affect the stability of the application.
+
+Incident Retainment
+:   Enter the number of days VM Essentials should keep incident records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large incident database tables can affect the stability of the application.
+
+Stats Retainment
+:   Select 30, 60 or 90 days period for stats retainment. Selecting a larger period gives the ability to analyze stats, such as Instance metrics, over a longer period of time. For example, in the Monitoring tab of an Instance detail page, users can select a 60 or 90-day analysis period if the stats have been retained that long
+
+Denied Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which should not be allowed sources for HTTP Tasks or REST-populated Option Lists.
+
+Approved Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which are the only approved sources for HTTP Tasks or REST-populated Option Lists. By entering any values here, all others are automatically denied.
+
+Exchange URL
+:   Enter the URL which should be checked for updates to any installed plugins. The default exchange is: `https://share.morpheusdata.com`
+
+Skip Agent Install
+:   For appliances in which skipping the Agent install is the default selection, enable this global flag to default to skipping the Agent install during provisioning
+
+Enable SSL Verification of Agent (Communications)
+:   Enabling SSL Verification of Agent Communications requires a valid Certificate be installed on the Appliance.
+
+Disable SSH Password Authentication
+:   Only allow ssh login using SSH keys. When true, SSH Password Authentication will not be enabled for VM’s and Hosts provisioned after the setting is enabled.
+
+Default Appliance Locale
+:   Sets the default language and region for all users on the VM Essentials appliance. Users with individual language preferences may also override this selection on their User Settings page
+
+Default Console Gateway
+:   Select a configured VM Essentials Worker as a console gateway or VDI gateway. For more on installation and configuration of a gateway, see the [VDI Gateways section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html#vdi-gateways) of VM Essentials documentation.
+
+Max Option List Size
+:   Sets a maximum size for Option Lists (such as those sourced from REST calls to a remote server) to preserve appliance performance in the event that a very large payload is inadvertently accessed. The entered number is multiplied by 1000 (for example, entering “1” results in a maximum list size of 1000).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json b/corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
new file mode 100644
index 0000000..268301e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+  "title": "Create User",
+  "ordinal": 252,
+  "parent_title": "Users",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-21972435-BFD0-481F-A3E6-A52B116989F3.html",
+  "topic_cluster": {
+    "clustering_title": "Create User",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+        "clustering_title": "Create User"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+        "clustering_title": "Create User"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md b/corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
new file mode 100644
index 0000000..c498f3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
@@ -0,0 +1,52 @@
+# Create User
+
+## About this task
+
+Users are created in Administration > Users.
+
+NOTE
+
+Authorized Identity Source Users will be automatically created upon first sign in.
+
+To create a User:
+
+## Procedure
+
+1. Navigate to Administration > Users
+2. Select + CREATE USER.
+3. From the New User Wizard input: 
+
+   Username & Email
+   :   - First Name
+       - Last Name
+       - Username
+       - Email address
+
+   Receive Notifications
+   :   Enable to receive provisioning email notifications.
+
+   Roles
+   :   Role(s) to be inherited by the user. If multiple roles are selected, the higher permission levels of one role will override the other role(s). See the Roles section of this documentation for more information on stacking Roles and specific Role permissions.
+
+   Password
+   :   Password must contain at least one uppercase letter, one lowercase letter, a number, and a symbol.
+
+   Enabled
+   :   If unchecked, the user will no longer be able to sign into VM Essentials, but their user data will remain.
+
+   Account Locked
+   :   This box is checked when a User has tried unsuccessfully to log in too many times. An administrator will need to uncheck this box in order for the User to be able to make another login attempt.
+
+   Password Expired
+   :   If enabled, the User will be forced to create a new password upon next login. The expired password cannot be used again.
+
+   Linux Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Linux Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this VM Essentials user is a member of.
+
+   Windows Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Windows Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this VM Essentials user is a member of.
+
+       IMPORTANT
+
+       Please ensure password entered is allowable by Windows.
+4. Select SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json b/corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
new file mode 100644
index 0000000..7384dee
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+  "title": "Viewing Volumes",
+  "ordinal": 373,
+  "parent_title": "Volumes tab",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing Volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+        "clustering_title": "Viewing Volumes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+        "clustering_title": "Viewing Volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md b/corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
new file mode 100644
index 0000000..b56ff29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
@@ -0,0 +1,21 @@
+# Viewing Volumes
+
+The Volumes tab provides a list of all volumes, including their summary, capacity information, and ransomware monitoring status.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server name.
+3. Select the Volumes tab. You can view the following information:
+   - **Name**: Displays the volume name for the VM.
+   - **Details**: Displays the CD Drive volume or data disk associated with the VM name.
+   - **Usage**: Displays a progress bar. The progress bar displays:
+     - Used capacity in percentage.
+     - Used capacity in either GiB or TiB, based on its value, in comparison to the total capacity.
+   - **Ransomware Monitoring**: Indicates whether ransomware monitoring is enabled or disabled for the volume. Ransomware monitoring is enabled or disabled while creating the datastore.
+
+     NOTE
+
+     Once ransomware monitoring is enabled for a datastore, the ransomware monitoring status cannot be edited​.
+   - **IOPS**: Displays the number of read and write operations performed by the volume each second.
+   - **Throughput**: Displays the amount of data transferred to or from the volume each second.
+
+   ![Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-8E25EA50-EEC7-48EA-8FCF-973EB252A822-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json b/corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
new file mode 100644
index 0000000..f1a5e16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+  "title": "Base Cluster Details",
+  "ordinal": 104,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.html",
+  "topic_cluster": {
+    "clustering_title": "Base Cluster Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+        "clustering_title": "Base Cluster Details"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+        "clustering_title": "Base Cluster Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md b/corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
new file mode 100644
index 0000000..b44d0e0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
@@ -0,0 +1,8 @@
+# Base Cluster Details
+
+An HVM cluster using the hyperconverged infrastructure (HCI) Layout consists of at least three hosts. Physical hosts are recommended to experience full performance of the solution. In smaller environments, it is possible to create an HVM cluster with three nested virtual machines, a single physical host (non-HCI only), or a single nested virtual machine (non-HCI only) though performance may be reduced. With just one host it won’t be possible to migrate workloads between hosts or take advantage of automatic failover. Currently, the default cluster layout requires hosts be a pre-existing Ubuntu 24.04 box with environment and host system requirements described in this section. An earlier cluster layout requiring Ubuntu 22.04 is also included. VM Essentials handles cluster configuration by providing the IP address(es) for your host(s) and a few other details. Details on adding the cluster to VM Essentials are contained in the next section.
+
+**Subtopics**  
+
+- **[Hardware Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-634760AA-7E46-42A7-AD08-85CCE4656873.html)**
+- **[Example Cluster Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json b/corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
new file mode 100644
index 0000000..4b8e579
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+  "title": "Overview",
+  "ordinal": 154,
+  "parent_title": "IP Pools",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-238F9226-4EB4-4E14-B533-584277951C4B.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md b/corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
new file mode 100644
index 0000000..1c16721
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
@@ -0,0 +1,3 @@
+# Overview
+
+The IP Pools tab in the Networks section allows you to create HVM-type IP Pools (which is an IP address range VM Essentials can use to assign available static IP addresses to Instances) and NSX IP Pools. The IP Pool section also displays pools synced from IPAM integrations like Infoblox, Bluecat and others.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json b/corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
new file mode 100644
index 0000000..fd9ead9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+  "title": "Review",
+  "ordinal": 23,
+  "parent_title": "Activity",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.html",
+  "topic_cluster": {
+    "clustering_title": "Review",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+        "clustering_title": "Review"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+        "clustering_title": "Review"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md b/corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
new file mode 100644
index 0000000..8fcfbfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
@@ -0,0 +1,7 @@
+# Review
+
+To review the item that generated the activity, click the name of the activity and it will go to a new page and display that item. The list of activity can be filtered by type, user or date range.
+
+NOTE
+
+Deleted activities are displayed as an alert and do not contain a link to the event item. If the activity is not a deletion event we provide a link on the activity name to go to the item the activity occurred on. Delete activity alerts are shown for Instances, servers, Clouds, and Groups.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json b/corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
new file mode 100644
index 0000000..872065a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+  "title": "Cluster Permissions",
+  "ordinal": 99,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+        "clustering_title": "Cluster Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+        "clustering_title": "Cluster Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md b/corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
new file mode 100644
index 0000000..f3086d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
@@ -0,0 +1,3 @@
+# Cluster Permissions
+
+Each Cluster has Group and Service Plan access permissions settings (Gear icon > Permissionsfrom the Clusters list page).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json b/corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
new file mode 100644
index 0000000..86a66e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+  "title": "Cypher",
+  "ordinal": 212,
+  "parent_title": "Tools",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html",
+  "topic_cluster": {
+    "clustering_title": "Cypher",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md b/corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
new file mode 100644
index 0000000..8ca3659
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
@@ -0,0 +1,15 @@
+# Cypher
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.html)**
+- **[Mountpoints](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.html)**
+- **[Creating Cypher Keys](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.html)**
+- **[Password](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.html)**
+- **[tfvars](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.html)**
+- **[Secret](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.html)**
+- **[UUID](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.html)**
+- **[Key](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.html)**
+- **[Vault](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.html)**
+- **[Editing Cypher Keys](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.html)**
+- **[Using Cypher Keys in Scripts](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json b/corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
new file mode 100644
index 0000000..eb3510a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+  "title": "Gotchas",
+  "ordinal": 344,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.html",
+  "topic_cluster": {
+    "clustering_title": "Gotchas",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+        "clustering_title": "Gotchas"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+        "clustering_title": "Gotchas"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md b/corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
new file mode 100644
index 0000000..88824c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
@@ -0,0 +1,5 @@
+# Gotchas
+
+SELinux can cause issues with cloud-init when in enforced mode. It may be advisable to set this to permissive unless it is mandatory within your organization to use an enforced SELinux configuration. If that is the case please see the documentation for the cloud\_init\_t security policies.
+
+Network Manager will also prevent the required restart of the Network Service when assigning static IP’s. Disable Network Manager when possible or Static IP assignment may not work until the Network Service is restarted manually.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json b/corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
new file mode 100644
index 0000000..67a78f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+  "title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "ordinal": 307,
+  "parent_title": "User Process Guides",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.html",
+  "topic_cluster": {
+    "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+        "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+        "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md b/corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
new file mode 100644
index 0000000..0f9feef
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
@@ -0,0 +1,17 @@
+# Backing Up and Restoring the HPE Morpheus VM Essentials Manager
+
+NOTE
+
+In the event of a total system failure (full crash), the recovery process requires the user to provision a new, freshly installed VME Manager. You cannot perform this recovery on a partially configured or corrupted appliance. The recovery process involves following:
+
+- Provision the replacement VME Manager
+- Transfer and restore security keys
+- Database injection and reconfiguration
+- Verifying the restored VME Manager
+
+**Subtopics**  
+
+- **[Create A Backup Job](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.html)**
+- **[Integrate a Bucket or File Share](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.html)**
+- **[Configuring HPE Morpheus Enterprise Appliance Backup](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D647F00D-6B45-4E18-B442-14835847EFA7.html)**
+- **[Restoring the HPE Morpheus Enterprise Manager from Backup](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json b/corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
new file mode 100644
index 0000000..9af6214
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+  "title": "Overview",
+  "ordinal": 251,
+  "parent_title": "Users",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md b/corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
new file mode 100644
index 0000000..03960d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
@@ -0,0 +1,16 @@
+# Overview
+
+The Users page displays a list of all Users. The following fields are surfaced for each User:
+
+- Display Name
+- Username
+- Email
+- Role
+
+Users which are grayed out in the list are currently inactive and cannot log in. The pencil and trash icons at the end of each row allow for editing or deleting Users. Click MORE to see the “impersonate” button. This allows administrators to impersonate any User, which may help confirm their Role permissions meet and do not exceed the desired result.
+
+Click on the hyperlinked Display Name of the User to see a page detailing their effective Role permissions. This is especially useful for Users in multiple Roles where it might otherwise be difficult to determine their exact rights. This page looks identical to a User Role detail page except none of the fields are editable. Edit the User Role permissions for the User if changes need to be made.
+
+NOTE
+
+Some User data created through an Identity Source integration (such as Active Directory) is not editable in VM Essentials, as it is synced from the Identity Source.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json b/corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
new file mode 100644
index 0000000..75fa429
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+  "title": "Setting Up Two-Factor Authentication",
+  "ordinal": 298,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.html",
+  "topic_cluster": {
+    "clustering_title": "Setting Up Two-Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+        "clustering_title": "Setting Up Two-Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+        "clustering_title": "Setting Up Two-Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md b/corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
new file mode 100644
index 0000000..dc80942
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
@@ -0,0 +1,7 @@
+# Setting Up Two-Factor Authentication
+
+When two-factor authentication isn’t yet set up, this section contains a single button: ENABLE 2FA. To get started, click this button and VM Essentials will prompt for your password. After entering the password, you’ll be shown a QR code which can be scanned into your authenticator application of choice. Once the QR code is shown, 2FA is active and the supplemental code will need to be entered each time the user logs in.
+
+![../../_images/2fa_qr.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-B46B6795-F044-4E76-BEB1-3A96F5575CE6-high.png)
+
+On subsequent login attempts, the user will be prompted to enter a 2FA code after successful entry of the username and password. Retrieve this code from the 2FA app you set up in the prior section and enter it to complete the login process.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json b/corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
new file mode 100644
index 0000000..2802241
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+  "title": "Performing Instance Actions",
+  "ordinal": 49,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.html",
+  "topic_cluster": {
+    "clustering_title": "Performing Instance Actions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+        "clustering_title": "Performing Instance Actions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+        "clustering_title": "Performing Instance Actions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md b/corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
new file mode 100644
index 0000000..939fc3e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
@@ -0,0 +1,7 @@
+# Performing Instance Actions
+
+## Procedure
+
+1. Select the Provisioning link in the navigation bar.
+2. From the Instances list, select the desired Instance.
+3. Click the Actions dropdown button and select an Action.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json b/corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
new file mode 100644
index 0000000..7a388ca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+  "title": "Overview",
+  "ordinal": 81,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md b/corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
new file mode 100644
index 0000000..c0719a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
@@ -0,0 +1,14 @@
+# Overview
+
+## About this task
+
+Groups in VM Essentials define the available resources for each user. Group access is defined by Roles. Clouds are added to Groups, and a User can only access the Clouds associated with Groups in their Role. Resources such as networks, datastores, resource pools, and folders have additional Group access settings.
+
+The Groups list page displays all current groups, which can be filtered by applied Labels or by simple search. Existing Groups can be edited here and new Groups can be created.
+
+To View Groups:
+
+## Procedure
+
+1. Hover over the Infrastructure link in the menu bar
+2. Click the Groups link
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json b/corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
new file mode 100644
index 0000000..2d747e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+  "title": "Tools",
+  "ordinal": 211,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html",
+  "topic_cluster": {
+    "clustering_title": "Tools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md b/corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
new file mode 100644
index 0000000..c652c34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
@@ -0,0 +1,7 @@
+# Tools
+
+**Subtopics**  
+
+- **[Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html)**
+- **[Archives](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html)**
+- **[Migrations](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json b/corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
new file mode 100644
index 0000000..7a966df
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+  "title": "Task Executions",
+  "ordinal": 14,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.html",
+  "topic_cluster": {
+    "clustering_title": "Task Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+        "clustering_title": "Task Executions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+        "clustering_title": "Task Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md b/corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
new file mode 100644
index 0000000..2c67d7c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
@@ -0,0 +1,3 @@
+# Task Executions
+
+Displays the number of successful and unsuccessful Task executions over the last day, week or month
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json b/corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
new file mode 100644
index 0000000..bcf7ed8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+  "title": "Handling User Lock-Out",
+  "ordinal": 300,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.html",
+  "topic_cluster": {
+    "clustering_title": "Handling User Lock-Out",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+        "clustering_title": "Handling User Lock-Out"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+        "clustering_title": "Handling User Lock-Out"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md b/corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
new file mode 100644
index 0000000..99c89c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
@@ -0,0 +1,3 @@
+# Handling User Lock-Out
+
+If a user loses the device they’ve configured for authentication or if they cannot proceed through 2FA login for any other reason, an administrator should impersonate the user’s account, reset their password, disable 2FA, then share the new temporary password with the user. At that point, the user can login, reset their password to something more secure, and re-enable 2FA (if desired).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json b/corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
new file mode 100644
index 0000000..4f86411
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+  "title": "Prerequisites",
+  "ordinal": 350,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md b/corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
new file mode 100644
index 0000000..1e0fc5a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
@@ -0,0 +1,11 @@
+# Prerequisites
+
+- A pair of ArubaCX 8325 series switches
+- All the hosts in the Cluster are connected to these pair of switches
+- REST API access to the ArubaCX switches with administrative rights
+- User credentials for the ArubaCX switch pair with API access granted and read/write access to the switch configuration
+
+**Subtopics**  
+
+- **[Server Network Configuration (Netplan)](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-392743FA-D99D-4995-A8F6-3E5541271263.html)**
+- **[Switch Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json b/corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
new file mode 100644
index 0000000..8257b05
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+  "title": "Backups",
+  "ordinal": 283,
+  "parent_title": "Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md b/corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
new file mode 100644
index 0000000..f15274d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
@@ -0,0 +1,5 @@
+# Backups
+
+**Subtopics**  
+
+- **[Backup Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3A5066B9-898A-4673-A713-C3E41D502742.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json b/corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
new file mode 100644
index 0000000..275e55a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+  "title": "Adding Domains",
+  "ordinal": 158,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+        "clustering_title": "Adding Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+        "clustering_title": "Adding Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md b/corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
new file mode 100644
index 0000000..0c6aa34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
@@ -0,0 +1,51 @@
+# Adding Domains
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Domains
+2. Select + ADD
+3. Enter the following: 
+
+   Domain Name
+   :   Ex. demo.example.com
+
+   Description
+   :   Descriptive metadata for use in VM Essentials
+
+   Display Name
+   :   Overrides the displayed name in domain selection components, which is useful when using many OU paths
+
+   Public Zone
+   :   Check for Public Zones, leave uncheck for Private Zones
+
+   Workflow
+   :   Select an existing Workflow which will be applied to Instances at provision time when they are associated with the domain. This is useful for any domain-related scripting you may currently use. For example, you may want to ensure a machine is removed from the domain when it’s torn down which could be accomplished by creating a Provisioning Workflow (with teardown phase Tasks) and associating the Workflow with the domain
+
+   Active
+   :   Active Domains are available for selection in Domain selection fields across VM Essentials. Inactive Domains are removed from Domain selection fields.
+
+   Join Domain Controller
+   :   Enable to have Windows instances join a Domain
+
+   Username
+   :   Admin user for Domain. `domain\username` format required when specifying OU Path
+
+   Password
+   :   Password for DC user account
+
+   DC Server
+   :   (optional) Specify the URL or Path of the DC Server
+
+   OU Path
+   :   (optional) Enter the OU Path for the connection string.
+
+   Guest Username
+   :   (optional) If set, this will change the provisioned hosts RPC Service User after domain join. Useful when a domain policy disables the Administrator account that typically would be set as the RPC user on a host record. VM Essentials will update the RPC username and password on the host(s) record after domain join with the specified Guest Username and Guest Password. The RPC username and password are used for auth during Remote Procedure Call (RPC) executions over winrm, ssh and guest tools.
+
+   Guest Password
+   :   (optional) The password for the Guest User account indicated in the prior field
+4. Click Save Changes
+
+## Results
+
+The Domain has been added and will be selectable in the Domain dropdown during provisioning, and in Cloud and Network settings.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json b/corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
new file mode 100644
index 0000000..9156f87
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+  "title": "Role Requirements",
+  "ordinal": 174,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.html",
+  "topic_cluster": {
+    "clustering_title": "Role Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+        "clustering_title": "Role Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+        "clustering_title": "Role Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md b/corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
new file mode 100644
index 0000000..0776daf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
@@ -0,0 +1,3 @@
+# Role Requirements
+
+There are two Role permissions for the Infrastructure > Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage gives Full, Read or No access to the Infrastructure > Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json b/corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
new file mode 100644
index 0000000..ff8d453
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+  "title": "SSH/Winrm",
+  "ordinal": 35,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.html",
+  "topic_cluster": {
+    "clustering_title": "SSH/Winrm",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+        "clustering_title": "SSH/Winrm"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+        "clustering_title": "SSH/Winrm"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md b/corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
new file mode 100644
index 0000000..3977ccc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
@@ -0,0 +1,6 @@
+# SSH/Winrm
+
+**Subtopics**  
+
+- **[Linux Agent](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.html)**
+- **[Windows Agent](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9969BD6B-639D-4633-B825-79578464E8E6.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json b/corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
new file mode 100644
index 0000000..e452aa3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+  "title": "Proxy Settings",
+  "ordinal": 270,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.html",
+  "topic_cluster": {
+    "clustering_title": "Proxy Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+        "clustering_title": "Proxy Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+        "clustering_title": "Proxy Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md b/corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
new file mode 100644
index 0000000..34a07f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
@@ -0,0 +1,17 @@
+# Proxy Settings
+
+The VM Essentials Appliance can be configured to communicate through a Proxy server for Cloud API’s and Agent communication back to the Appliance.
+
+NOTE
+
+Additional Proxy configuration is available in the Infrastructure  >  Network  >  Proxies section. Added Proxies can be scoped to Clouds in the Edit Cloud  >  Advanced Options section of the Cloud.
+
+Add a Global Proxy server by entering the following:
+
+- Proxy Host
+- Proxy Port
+- Proxy User
+- Proxy Password
+- Proxy Domain
+- Proxy Workstation
+- No Proxy
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json b/corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
new file mode 100644
index 0000000..849ed21
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+  "title": "Overview",
+  "ordinal": 157,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md b/corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
new file mode 100644
index 0000000..04a66be
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
@@ -0,0 +1,12 @@
+# Overview
+
+The Domains section is for creating and managing domains for use in VM Essentials. Domains are used for setting FQDNs, joining Domains, and creating DNS records. The Domains section is also a multi-tenant endpoint for managing domain settings across multiple tenants.
+
+- Domains are synced in from Cloud, DNS and Network Integrations. Domains can also be user created.
+- Active Domains are available for selection in the Domain dropdown when provisioning an Instance
+- Default Domains can be set for Clouds and Networks in their Advanced Options sections.
+- Images can be flagged to Auto-Join Domains in the Infrastructure  >  Network  >  Domains section
+
+IMPORTANT
+
+For an Instance to auto-join a Domain, a Domain must set in the Advanced Options section of the Cloud or Network used when provisioning
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json b/corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
new file mode 100644
index 0000000..ebe42c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+  "title": "Service Plans",
+  "ordinal": 319,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-30353E6D-5FA2-470C-BB80-238663945F6F.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+        "clustering_title": "Service Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+        "clustering_title": "Service Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md b/corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
new file mode 100644
index 0000000..a88aee9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
@@ -0,0 +1,3 @@
+# Service Plans
+
+A default set of Service Plans are created in VM Essentials for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json b/corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
new file mode 100644
index 0000000..c3e7d5b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+  "title": "File Detail Page",
+  "ordinal": 229,
+  "parent_title": "Archives",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.html",
+  "topic_cluster": {
+    "clustering_title": "File Detail Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+        "clustering_title": "File Detail Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+        "clustering_title": "File Detail Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md b/corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
new file mode 100644
index 0000000..9c4efb3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
@@ -0,0 +1,3 @@
+# File Detail Page
+
+The File Detail Page contains details about the file itself as well as private and public (if available) URLs. In the lower section are three tabs. The Links tab contains any download links which have been generated (both active and expired). The History tab contains historical information about the file including creation and deletion of download links and download events. The scripts tab contains a guide for getting started using Archive-stored files in scripts.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json b/corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
new file mode 100644
index 0000000..434cb8f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+  "title": "Features",
+  "ordinal": 315,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md b/corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
new file mode 100644
index 0000000..f36ee84
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
@@ -0,0 +1,25 @@
+# Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+- Metadata tag sync
+
+On top of all these features, VM Essentials also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json b/corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
new file mode 100644
index 0000000..372a5cd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+  "title": "Features",
+  "ordinal": 357,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md b/corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
new file mode 100644
index 0000000..20767e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
@@ -0,0 +1,8 @@
+# Features
+
+- Create and delete networks of type `HPE ANW DSS Port Group` directly from the integration
+- Automatically create and delete networks in Aruba Fabric Composer (AFC) when HVM hosts are added or removed from the HVM cluster
+- Manage network configurations through seamless integration with AFC
+- Enable both micro-segmentation and macro-segmentation for flexible network isolation
+- View detailed summaries and status of Aruba CX 10000 switches
+- Ensure automatic, realtime synchronization of network configurations with Aruba CX 10000 switches
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json b/corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
new file mode 100644
index 0000000..0f01b16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+  "title": "Storage Buckets",
+  "ordinal": 176,
+  "parent_title": "Default Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md b/corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
new file mode 100644
index 0000000..47021a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
@@ -0,0 +1,3 @@
+# Storage Buckets
+
+Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json b/corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
new file mode 100644
index 0000000..65104b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+  "title": "Guides",
+  "ordinal": 305,
+  "parent_title": null,
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html",
+  "topic_cluster": {
+    "clustering_title": "Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md b/corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
new file mode 100644
index 0000000..11504f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
@@ -0,0 +1,6 @@
+# Guides
+
+**Subtopics**  
+
+- **[User Process Guides](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.html)**
+- **[Integration Guides](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json b/corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
new file mode 100644
index 0000000..35952ce
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+  "title": "Add Storage Server",
+  "ordinal": 194,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.html",
+  "topic_cluster": {
+    "clustering_title": "Add Storage Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+        "clustering_title": "Add Storage Server"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+        "clustering_title": "Add Storage Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md b/corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
new file mode 100644
index 0000000..c48367d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
@@ -0,0 +1,96 @@
+# Add Storage Server
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+## Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following:
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server
+       :   Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following:
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json b/corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
new file mode 100644
index 0000000..81d55e2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+  "title": "Editing Cypher Keys",
+  "ordinal": 222,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Cypher Keys",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+        "clustering_title": "Editing Cypher Keys"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+        "clustering_title": "Editing Cypher Keys"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md b/corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
new file mode 100644
index 0000000..c72e7ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
@@ -0,0 +1,3 @@
+# Editing Cypher Keys
+
+Cypher key types which accept user-entered values (not generated values) are editable. To edit, click the “ACTIONS” button at the end of the row for the appropriate Cypher key and then click “Edit.” Edit the values and click SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json b/corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
new file mode 100644
index 0000000..7c63b18
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+  "title": "Restoring the HPE Morpheus Enterprise Manager from Backup",
+  "ordinal": 311,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.html",
+  "topic_cluster": {
+    "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+        "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+        "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md b/corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
new file mode 100644
index 0000000..df46efb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
@@ -0,0 +1,38 @@
+# Restoring the HPE Morpheus Enterprise Manager from Backup
+
+Begin by ensuring the Morpheus UI service is stopped on the HPE Morpheus Enterprise Manager VM. Connect to the manager over SSH from your workstation **bearing in mind that most commands in this process will require sudo or root access.** Enter the following command:
+
+```
+```
+[root@app-server~] morpheus-ctl stop morpheus-ui
+```
+```
+
+To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file. View it like so:
+
+```
+```
+[root@app-server~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---- this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Make note of the first `morpheus_password` value as indicated above.
+
+Copy the SQL database backup from the backup bucket or file share to the destination Manager VM at path `/tmp/morpheus_backup.sql`. Then, you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The database backup is now replicated on the new Manager VM. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server~] morpheus-ctl start morpheus-ui
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json b/corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
new file mode 100644
index 0000000..594e96d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+  "title": "File Shares",
+  "ordinal": 185,
+  "parent_title": "Rackspace CDN Buckets",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-35419962-0058-4856-A6BD-F4923FD0F044.html",
+  "topic_cluster": {
+    "clustering_title": "File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+        "clustering_title": "File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+        "clustering_title": "File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md b/corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
new file mode 100644
index 0000000..1a96540
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
@@ -0,0 +1,3 @@
+# File Shares
+
+File Shares are for Backup, Archives, and Virtual Images storage targets. File Shares can be browsed and files and folders can be uploaded, downloaded or deleted from the File Shares section. Retention Policies can be set on Storage File Shares for files to be deleted or backed up to another File Share after a set amount of time.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json b/corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
new file mode 100644
index 0000000..5631bb1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+  "title": "Azure Buckets",
+  "ordinal": 180,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+        "clustering_title": "Azure Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+        "clustering_title": "Azure Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md b/corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
new file mode 100644
index 0000000..1a99064
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
@@ -0,0 +1,74 @@
+# Azure Buckets
+
+## About this task
+
+To Add an Azure Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Azure from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   STORAGE ACCOUNT
+   :   Name of the Storage Account in Azure for the Bucket
+
+   STORAGE KEY
+   :   Storage Key provided from Azure
+
+   SHARE NAME
+   :   Enter existing Azure Storage Share name, or to add a new Share enter a new name and select Create Bucket below.
+
+   CREATE BUCKET
+   :   Enable if the Share entered in SHARE NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json b/corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
new file mode 100644
index 0000000..25a6875
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+  "title": "Adding GFS2 Pools",
+  "ordinal": 118,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3702D75B-9505-40D0-B220-7739F5F72760.html",
+  "topic_cluster": {
+    "clustering_title": "Adding GFS2 Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+        "clustering_title": "Adding GFS2 Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+        "clustering_title": "Adding GFS2 Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md b/corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
new file mode 100644
index 0000000..9df84df
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
@@ -0,0 +1,47 @@
+# Adding GFS2 Pools
+
+In order to utilize GFS2 Pools with HVM Clusters, users must first present the block storage devices to the HVM Hosts. These can be configured via iSCSI or Fibre Channel and all Hosts in the Cluster must be able to access the same block device. For now, this guide will focus more specifically on iSCSI configuration but additional guidance on Fibre Channel configuration may be added in the future.
+
+Once disks are presented to the HVM Hosts, iSCSI targets and GFS2 datastores can be added via the UI. The HPE Morpheus VM Essentials handles most of the configuration from there (including multipathing).
+
+To get started, ensure the following configuration has been made on the storage system. The exact process will depend on the storage system being used:
+
+- Create a LUN and map to an iSCSI target
+- Enable concurrent connections
+- Decide if you want to use CHAP authentication. GFS2 Pools with HVM Clusters support the use of CHAP authentication but there is currently no UI tool to enable it. If you wish to enable it, further instructions are available in [this knowledge article](https://support.hpe.com/hpesc/public/docDisplay?docId=sf000111606en_us&docLocale=en_US)
+
+With the above groundwork laid, create iSCSI target(s) in HPE Morpheus VM Essentials. If two paths to the iSCSI target have been created, two iSCSI objects can be created in the UI and HPE Morpheus VM Essentials will configure multipathing for you.
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the iSCSI subtab
+3. Click Add
+4. Enter the iSCSI target IP address and the port. A default port is already entered for you
+5. Click Save changes
+6. Within a short moment, the modal is dismissed and a new iSCSI target is added to the list
+7. If you intend to go on immediately to the next step of adding a GFS2 datastore, manually refresh the Cluster now (Open the ACTIONS menu on the Cluster detail page and click "Refresh Daily")
+
+IMPORTANT
+
+The above steps are repeated when a second path to the iSCSI target exists. With both paths configured, HPE Morpheus VM Essentials can automatically handle configuration of multipathing. Multipathing cannot be automatically established after the datastore is created in the next step. Both paths must be registered with HPE Morpheus VM Essentials using the process described above prior to creating the datastore in order for multipathing configuration to be handled automatically.
+
+![Adding an iSCSI target](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-ECF9319A-BDC9-48F6-AEB7-9A223C2BD71A-high.png)
+
+![List of added iSCSI targets is shown](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-B8532AB4-AA0A-470B-BEF3-2C0D5C680C3D-high.png)
+
+With the iSCSI targets created, all HVM Hosts should have the LUN mounted as a new block device. With that in place, we can create a new GFS2 datastore.
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the Data Stores subtab
+3. Click Add
+4. Configure the following:
+
+   1. **NAME:** An identifiable name for the datastore in HPE Morpheus VM Essentials
+   2. **TYPE:** GFS2 Pool (Global File System 2)
+   3. **BLOCK DEVICE:** The block device now seen by the host as a result of adding the new iSCSI target(s)
+   4. **ALLOW REFORMATTING:** When marked, HPE Morpheus VM Essentials will reformat the disk if a GFS2 filesystem doesn't currently exist. Marking this box will destroy all data on the disk, use this option with caution
+   5. **IMAGE TARGET:** When marked, this data store will be available to store virtual images. Keep in mind that the HVM Cluster should have just one image target
+5. Click Save
+
+WARNING
+
+Utilizing the "Allow Reformatting" configuration when creating the GFS2 Pool-type datastore will destroy any data currently residing on the disk. Use this option with caution.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json b/corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
new file mode 100644
index 0000000..979fb8c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+  "title": "Activity",
+  "ordinal": 15,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md b/corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
new file mode 100644
index 0000000..ff7809e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
@@ -0,0 +1,9 @@
+# Activity
+
+The activity list displays the last few events that have taken place in VM Essentials by any user. This could be new provisioned workloads, deleted workloads, backups, or a number of other things. A more complete list of recent activities can be viewed in Operations > Activity.
+
+There are three types of activities available in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json b/corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
new file mode 100644
index 0000000..03b2532
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+  "title": "Servers",
+  "ordinal": 193,
+  "parent_title": "Manage Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html",
+  "topic_cluster": {
+    "clustering_title": "Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md b/corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
new file mode 100644
index 0000000..15eee7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
@@ -0,0 +1 @@
+# Servers
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json b/corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
new file mode 100644
index 0000000..d50bc41
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+  "title": "Server Network Configuration (Netplan)",
+  "ordinal": 351,
+  "parent_title": "Prerequisites",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-392743FA-D99D-4995-A8F6-3E5541271263.html",
+  "topic_cluster": {
+    "clustering_title": "Server Network Configuration (Netplan)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+        "clustering_title": "Server Network Configuration (Netplan)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+        "clustering_title": "Server Network Configuration (Netplan)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md b/corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
new file mode 100644
index 0000000..a43ae52
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
@@ -0,0 +1,21 @@
+# Server Network Configuration (Netplan)
+
+## Procedure
+
+1. On each host, configure a `bond0` interface on the management interfaces
+2. The management interfaces should be connected to the ArubaCX switch pair Sample configuration: 
+
+   ```
+   ```
+   {  
+       bonds:  
+         bond0:  
+           interfaces:  
+             - ens2f0np0  
+             - ens1f0np0  
+           parameters:  
+             mode: "active-backup"  
+       ...  
+   }
+   ```
+   ```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json b/corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
new file mode 100644
index 0000000..3dead49
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+  "title": "Role Permissions",
+  "ordinal": 247,
+  "parent_title": "Roles",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md b/corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
new file mode 100644
index 0000000..31a879d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
@@ -0,0 +1,10 @@
+# Role Permissions
+
+NOTE
+
+Permission options for sub-tenant user roles will only list options permitted by the Tenant role applied to the sub-tenant. Sub-Tenant user roles permissions cannot exceed permissions set by the overriding Tenant Role.
+
+**Subtopics**  
+
+- **[Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.html)**
+- **[Feature Access Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json b/corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
new file mode 100644
index 0000000..11776ff
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+  "title": "Add a storage server",
+  "ordinal": 369,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.html",
+  "topic_cluster": {
+    "clustering_title": "Add a storage server",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+        "clustering_title": "Add a storage server"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+        "clustering_title": "Add a storage server"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md b/corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
new file mode 100644
index 0000000..73606c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
@@ -0,0 +1,9 @@
+# Add a storage server
+
+The first step is to create a storage server in VM Essentials. After the storage server is added, you can view the storage summary and alerts, and view or edit volumes. For more information on adding a storage server, see [Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html).
+
+**Subtopics**  
+
+- **[Viewing the Summary page](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.html)**
+- **[Viewing Alerts](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.html)**
+- **[Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json b/corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
new file mode 100644
index 0000000..065dacd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+  "title": "Backup Settings",
+  "ordinal": 284,
+  "parent_title": "Backups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3A5066B9-898A-4673-A713-C3E41D502742.html",
+  "topic_cluster": {
+    "clustering_title": "Backup Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+        "clustering_title": "Backup Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+        "clustering_title": "Backup Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md b/corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
new file mode 100644
index 0000000..8d6e56c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
@@ -0,0 +1,11 @@
+# Backup Settings
+
+The Backup settings page allows you enable or disable scheduled backups, select a default backup bucket, and administer global settings related to backups. Changes to global settings only affect new backups going forward and do not affect existing backups.
+
+NOTE
+
+Appliance backups are subject to a two-hour time limit to complete the backup. Automated backup attempts will be abandoned and will fail once this time limit is exceeded.
+
+**Subtopics**  
+
+- **[VM Essentials Backup Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json b/corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
new file mode 100644
index 0000000..122a5f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+  "title": "Provisioning",
+  "ordinal": 26,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md b/corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
new file mode 100644
index 0000000..e3b3286
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
@@ -0,0 +1,9 @@
+# Provisioning
+
+There are many capabilities in the VM Essentials provisioning engine ranging from virtual machines bound for VMware vCenter and HVM cluster targets to containerized workloads targeting Docker. Deployment management and library template construction are also core aspects of the provisioning engine. This section of VM Essentials documentation covers the provisioning engine itself while the Library section covers template building, image management, and automation stacks.
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.html)**
+- **[Provisioning Concepts](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-44974486-3ED4-4C5C-849B-8746A4899889.html)**
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json b/corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
new file mode 100644
index 0000000..aa7c6b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+  "title": "Migrations Plans",
+  "ordinal": 233,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md b/corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
new file mode 100644
index 0000000..316f81d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
@@ -0,0 +1,25 @@
+# Migrations Plans
+
+Migration plans are created and run from the Migrations section of the Tools menu (Tools > Migrations). Migrations happen by creating and running Migration Plans. Plans are created in a pending state, meaning an additional action must be undertaken to set the plan in motion. Thus, Plans may be created which are intended to be run at a later time. Once finished, completed Plans remain on the Migrations list page for later review and, if desired, deletion.
+
+Creating Migration Plans
+
+Begin creating a Migration Plan from the Migrations list page (Tools > Migrations). This page contains a list of all Migrations already created, including those completed, currently running, and available to be run (pending). To start a new Migration, click + ADD.![A list of all currently-created Migrations.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-93D37CD4-FDF6-48AC-95C5-A5B7D7F30E35-high.png)
+
+From the SETUP tab of the CREATE MIGRATION PLAN modal, configure the following:
+
+- **NAME:** A name to identify the Migration
+- **SOURCE:** The source VMware vCenter Cloud
+- **TARGET:** The target Cloud containing the HVM Cluster
+- **RESOURCE POOL:** The selected destination HVM Cluster
+- **GROUP:** The Group which should own the migrated VMs
+
+When finished, click NEXT.![The SETUP tab of the CREATE MIGRATION PLAN modal.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-D9CD7CB0-1B54-42D7-A75C-010C489E9E09-high.png)
+
+The next step is to choose VMs from the selected VMware source Cloud to migrate. Select as many as desired given current recommendations regarding the maximum size due to storage space and available bandwidth (see the previous section). Selected VMs will form a list at the bottom of the modal. When finished, click NEXT.![Selecting source VMs to migration from the source VMware Cloud.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-EB548317-44C7-4C2C-B943-03241A92389D-high.png)
+
+The next tab establishes resource mapping. Listed, you will see the current networks and storage locations for the selected VMs. Choose destination networks and destination storage locations for each. Optionally, enter existing Linux or Windows user credentials and choose if prechecks or guest tools installation should be skipped. Click NEXT.![Mapping source networks and storage to destination networks and storage.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-7B17FB9E-19D1-42B2-9696-7856C59EC92F-high.png)
+
+The final tab is a review tab where all current selections can be checked. Return to any previous tabs, if necessary, to update selections.
+
+At this point, the Migration is created but will not run without additional input. The Migration is in a "Pending" state. All selections made when configuring the Migration are shown here. To execute the Migration, click RUN. The length of time it will take for the Migration to run depends on many factors. Once run, the Migration detail page will provide status updates on VMs currently being migrated, which have completed successfully, and if any have failed. The History tab provides greater detail on current and past migration actions taken. The Destination tab includes details on VMware VMs which have successfully been migrated to the HVM Cluster. Migrations are run just once and may be kept indefinitely after for review. When a Migration is no longer needed, click DELETE.![The migration detail page showing a migration in a pending state.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-7B7CB8A7-E91D-40E5-9B1B-E040BCFB2A0A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json b/corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
new file mode 100644
index 0000000..6a51544
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+  "title": "Overview",
+  "ordinal": 225,
+  "parent_title": "Archives",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md b/corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
new file mode 100644
index 0000000..7d60909
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
@@ -0,0 +1,3 @@
+# Overview
+
+Archives provides a way to store your files and make them available for download by your scripts and Users. Archives are organized by buckets and can be tied to any existing Bucket or File Share that may be currently integrated (for more on integrating new storage targets, see storage documentation). Thus, storage buckets in public clouds, on networked storage, or even on the appliance itself may be used to host files.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json b/corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
new file mode 100644
index 0000000..235d73b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+  "title": "Configuring Backups during Provisioning",
+  "ordinal": 207,
+  "parent_title": "Backups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Backups during Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+        "clustering_title": "Configuring Backups during Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+        "clustering_title": "Configuring Backups during Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md b/corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
new file mode 100644
index 0000000..6cb06a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
@@ -0,0 +1,36 @@
+# Configuring Backups during Provisioning
+
+When Backups are enabled, Backup options are presented in the AUTOMATION tab of the provisioning wizard. Note that your default backup bucket and default backup schedule will be set according to your global backup settings as mentioned in the previous sections.
+
+NOTE
+
+The Backup options presented in the Automation tab can be disabled using a “Create Backup” Policy. See ../administration/policies/policies
+
+BACKUP TYPE
+:   Select the type for the Backup. Backup Types displayed will be filtered by available options for the selected Instance Layout
+
+BACKUP NAME
+:   Defaults to the Instance name
+
+BACKUP TARGET
+:   Select the Storage Provider target for the Backup (when applicable)
+
+BACKUP JOB TYPE
+:   Create a new job, clone an existing job, or Add to existing job
+
+JOB NAME
+:   Defaults to the Instance name
+
+RETENTION COUNT
+:   Maximum number of successful backups to retain
+
+BACKUP SCHEDULE
+:   Select the schedule for the backup job from the list of existing execution schedules
+
+SYNTHETIC FULL (Currently only available for KVM VM Snapshot-type backups, such as those used with HVM Instances. More Layout types are expected to support synthetic full backups in the future)
+:   When checked, an additional schedule is configured for the backup job during which a synthetic full backup will be taken. In general, this should be on a longer time period than that at which standard backups (full backup followed by incremental backups) are configured
+
+SYNTHETIC FULL SCHEDULE
+:   Select the schedule for the backup job on which synthetic full backups should be taken
+
+Backup Types displayed will be filtered by available options per selected Instance Layout.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json b/corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
new file mode 100644
index 0000000..5eb6fbd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+  "title": "2 Factor Authentication",
+  "ordinal": 297,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3B34F036-4C25-4058-B5F4-5340545BE821.html",
+  "topic_cluster": {
+    "clustering_title": "2 Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+        "clustering_title": "2 Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+        "clustering_title": "2 Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md b/corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
new file mode 100644
index 0000000..ca966e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
@@ -0,0 +1,9 @@
+# 2 Factor Authentication
+
+VM Essentials supports two-factor authentication (2FA) for local user accounts as well as those authenticating through Active Directory and LDAP identity sources. Authentication is handled through a 2FA app such as Authy or Google Authenticator. Other common methods for handling 2FA, such as through email or SMS text message are not currently supported. Two-factor authentication is handled on a per-user basis through the User Settings section. There is not currently a way for an administrator to enforce the use of two-factor authentication appliance-wide.
+
+**Subtopics**  
+
+- **[Setting Up Two-Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.html)**
+- **[Disabling Two-Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.html)**
+- **[Handling User Lock-Out](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json b/corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
new file mode 100644
index 0000000..1bd1116
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+  "title": "Add Existing Key Pair",
+  "ordinal": 198,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.html",
+  "topic_cluster": {
+    "clustering_title": "Add Existing Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+        "clustering_title": "Add Existing Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+        "clustering_title": "Add Existing Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md b/corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
new file mode 100644
index 0000000..eb72ead
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
@@ -0,0 +1,20 @@
+# Add Existing Key Pair
+
+## About this task
+
+To generate a existing Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. From the Add Key Pair modal input the following as needed: 
+
+   - Name
+   - Public Key
+   - Private Key
+   - Passphrase
+
+   NOTE
+
+   Certain features do not require storage of the private key.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json b/corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
new file mode 100644
index 0000000..5481927
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+  "title": "Cloud-Init Settings",
+  "ordinal": 277,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3D27BE17-47C9-476C-AD13-DD516697F862.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+        "clustering_title": "Cloud-Init Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+        "clustering_title": "Cloud-Init Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md b/corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
new file mode 100644
index 0000000..42b69e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
@@ -0,0 +1,12 @@
+# Cloud-Init Settings
+
+VM Essentials can add global users for Linux and Windows at provision time. Cloud-init/Cloudbase-Init or VMware Tools installed on the provisioned virtual images is required.
+
+Linux
+:   - **Username:** Enter User to be added to Linux Instances during provisioning.
+    - **Password:** Enter password to be set for the above Linux user.
+    - **KeyPair:** Select KeyPair to be added for the above Linux user.
+
+NOTE
+
+Either a password, keypair, or both can be populated for the Linux user. Keypairs can be added in the Infrastructure  >  Keys & Certs section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json b/corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
new file mode 100644
index 0000000..7a38343
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+  "title": "Service Plan Permissions",
+  "ordinal": 241,
+  "parent_title": "Overview",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3E03B539-B71C-4D2E-A218-23713D723408.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plan Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+        "clustering_title": "Service Plan Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+        "clustering_title": "Service Plan Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md b/corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
new file mode 100644
index 0000000..4f53c64
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
@@ -0,0 +1,5 @@
+# Service Plan Permissions
+
+Group Access permissions determine availability of a Service Plan to Users based on their associated Roles.
+
+- Group Access determines which Groups the Service Plan will be available in for Provisioning and Reconfigure.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json b/corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
new file mode 100644
index 0000000..3f3bc9b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+  "title": "Managing Groups",
+  "ordinal": 86,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+        "clustering_title": "Managing Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+        "clustering_title": "Managing Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md b/corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
new file mode 100644
index 0000000..1800608
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
@@ -0,0 +1,30 @@
+# Managing Groups
+
+## About this task
+
+To view a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Group name to view/modify
+
+## Results
+
+Available tabs in group view
+
+Hosts
+:   Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.
+
+Virtual Machines
+:   List all Virtual Machines in the Group.
+
+Bare Metal
+:   List all Bare Metal Hosts added to the Group
+
+Clouds
+:   Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.
+
+Wiki
+:   Provides a text area for entering wiki content related to the Group in Markdown format. Additional information on Wiki is available in the Operations > Wiki documentation section
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.json b/corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
new file mode 100644
index 0000000..00f966e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+  "title": "User Settings",
+  "ordinal": 296,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-40300B80-D69C-450B-9848-7A21A3141005.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.md b/corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
new file mode 100644
index 0000000..15db370
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
@@ -0,0 +1,12 @@
+# User Settings
+
+The fields included in this section are described below. By entering any new values in these fields and clicking SAVE, the existing value will be overwritten.
+
+- **Theme:** Choose from a selection of themes including default and dark mode themes. The Theme setting is not available when Whitelabeling is enabled on the current Tenant
+- **Username:** Your VM Essentials username
+- **First Name:** Your first name (together with Last Name makes up your display name)
+- **Last Name:** Your last name (together with First Name makes up your display name)
+- **Email:** Your email address
+- **Password:** Enter a value and save changes to update your password. The value in the Confirm field below must match
+- **Confirm:** Confirm the new password you’ve entered
+- **RECEIEVE NOTIFICATIONS** Determines if provisioning notifications are emailed to this User
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json b/corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
new file mode 100644
index 0000000..605e411
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+  "title": "Synced Images",
+  "ordinal": 30,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.html",
+  "topic_cluster": {
+    "clustering_title": "Synced Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+        "clustering_title": "Synced Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+        "clustering_title": "Synced Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md b/corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
new file mode 100644
index 0000000..62ddd9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
@@ -0,0 +1,63 @@
+# Synced Images
+
+When a provisioning target (Cloud) is added, all available image and template records from that Cloud will be synced in regardless of Inventory settings on the Cloud. These image records will be available in the Virtual Images section and can be provisioned by using the target clouds generic Instance Type (ex. By selecting the HVM or VMware Instance Type from the provisioning wizard).
+
+NOTE
+
+Synced Virtual Images are just metadata records in VM Essentials pointing to the image in the target Cloud. The actual image files are not copied/imported to VM Essentials manager.
+
+Before provisioning a synced Virtual Image, ensure the image is configured properly:
+
+Name
+:   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image file.
+
+Operating System
+:   Specifies the platform and OS of the image. All Windows images will need to have Operating System specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified.
+
+Minimum Memory
+:   The Minimum Memory setting will filter available Plan options during provisioning. Plans that do not meet the minimum memory value set on the Virtual Image will not be provided as Plan choices by the provisioning wizard.
+
+Cloud Init Enabled?
+:   On by default, uncheck for any image that does not have Cloud-Init or Cloudbase-Init installed.
+
+    IMPORTANT
+
+    Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in VM Essentials but does not have cloud-init installed will result in immediate provisioning failure.
+
+Install Agent
+:   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, Task execution, and monitoring (Some utilization stats are still collected by Agent-less workloads).
+
+Username
+:   An existing Username on the Image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init Guest Customizations or Nutanix Sysprep are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the Image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist in the image (aka `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change.
+
+Password
+:   Password for the existing user on the image if the Username field is populated.
+
+Storage Provider
+:   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/VMs`. Additional storage providers can be configured in Infrastructure > Storage.
+
+Cloud-Init User Data
+:   Accepts what would go in `runcmd` and can assume bash syntax. Example use: Script to configure satellite registration at provision time.
+
+Auto Join Domain?
+:   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure > Network and the configured domain set on the provisioned to Cloud or Network).
+
+VirtIO Drivers Loaded?
+:   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors, such as HVM cluster
+
+VM Tools Installed?
+:   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected.
+
+Force Guest Customization?
+:   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This is required for host/computer name definitions. domain joining, licenses and user definitions when using DHCP.
+
+Trial Version
+:   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning.
+
+IMPORTANT
+
+Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in VM Essentials but does not have cloud-init installed will result in immediate provisioning failure.
+
+IMPORTANT
+
+For Linux images without cloud-init, an existing username and password must be defined on the Virtual Image record for Agent Install, Domain joining, licensing, script execution and other automation, and SSH or RDP Console access.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json b/corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
new file mode 100644
index 0000000..456e501
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+  "title": "User Images",
+  "ordinal": 74,
+  "parent_title": "Configuring Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.html",
+  "topic_cluster": {
+    "clustering_title": "User Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+        "clustering_title": "User Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+        "clustering_title": "User Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md b/corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
new file mode 100644
index 0000000..dea9035
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
@@ -0,0 +1,7 @@
+# User Images
+
+Typically VM Essentials does not have sufficient metatdata to successfully provision synced User Images with no additional configuration. After integrating Clouds and User Images have synced, it is highly recommended to configure the images prior to provisioning.
+
+**Subtopics**  
+
+- **[To edit and configure an existing Virtual Image:](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json b/corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
new file mode 100644
index 0000000..fedc95f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+  "title": "Volumes tab",
+  "ordinal": 372,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.html",
+  "topic_cluster": {
+    "clustering_title": "Volumes tab",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+        "clustering_title": "Volumes tab"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+        "clustering_title": "Volumes tab"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md b/corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
new file mode 100644
index 0000000..54e18c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
@@ -0,0 +1,6 @@
+# Volumes tab
+
+**Subtopics**  
+
+- **[Viewing Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.html)**
+- **[Editing volumes](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json b/corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
new file mode 100644
index 0000000..f4faf29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+  "title": "Create vCenter Users and Roles",
+  "ordinal": 328,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.html",
+  "topic_cluster": {
+    "clustering_title": "Create vCenter Users and Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+        "clustering_title": "Create vCenter Users and Roles"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+        "clustering_title": "Create vCenter Users and Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md b/corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
new file mode 100644
index 0000000..8772835
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
@@ -0,0 +1,9 @@
+# Create vCenter Users and Roles
+
+For this example, I’ve added a new local user to be my VM Essentials integration user (Menu > Administration > Users and Groups) but any existing user, whether locally-created or sourced from an identity integration (like Active Directory), works fine.
+
+![../../../_images/addUsers.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-2664505C-63D5-43FB-9E16-21AD005B561C-high.png)
+
+The next step is to create a Role (Menu > Administration > Roles). You can edit an existing Role to be sure it has the correct privileges, I’ve opted to create a new role and assign the correct privileges. Below the screenshot, take note of the complete set of required privileges. Once all privileges are set, name the Role (if it’s a new one) and click Finish.
+
+![../../../_images/addRoles.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-3152339A-7CAC-4795-8CBD-67503905D112-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json b/corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
new file mode 100644
index 0000000..d1d8aeb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+  "title": "Provisioning Concepts",
+  "ordinal": 40,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-44974486-3ED4-4C5C-849B-8746A4899889.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Concepts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+        "clustering_title": "Provisioning Concepts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+        "clustering_title": "Provisioning Concepts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md b/corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
new file mode 100644
index 0000000..f66a8c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
@@ -0,0 +1,9 @@
+# Provisioning Concepts
+
+VM Essentials is a powerful provisioning and management platform for HVM clusters and VMware vCenter private cloud. Compared to other CMP platforms in the space, some terminology and concepts may differ. These concepts are documented in this section along with places where terminology may be slightly different compared with other platforms or with common industry parlance.
+
+**Subtopics**  
+
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.html)**
+- **[Containers / Nodes / Virtual Machines](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.html)**
+- **[Hosts / Servers](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json b/corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
new file mode 100644
index 0000000..5b7c49c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+  "title": "Configuring Networks",
+  "ordinal": 139,
+  "parent_title": "Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+        "clustering_title": "Configuring Networks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+        "clustering_title": "Configuring Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md b/corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
new file mode 100644
index 0000000..39dfbd7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
@@ -0,0 +1,10 @@
+# Configuring Networks
+
+**Subtopics**  
+
+- **[DHCP](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.html)**
+- **[Static and IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.html)**
+- **[Advanced Options (Search Domains)](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.html)**
+- **[Group and Tenant Access](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html)**
+- **[Guest Console SSH Tunnel](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.html)**
+- **[Subnets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9FC58214-95C7-4690-91DA-3185640E3712.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json b/corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
new file mode 100644
index 0000000..e77b71b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+  "title": "HPE Alletra MP Storage",
+  "ordinal": 364,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md b/corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
new file mode 100644
index 0000000..d67d7d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
@@ -0,0 +1,9 @@
+# HPE Alletra MP Storage
+
+**Subtopics**  
+
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.html)**
+- **[Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html)**
+- **[Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html)**
+- **[Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html)**
+- **[Add a storage server](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json b/corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
new file mode 100644
index 0000000..214d209
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+  "title": "Provisioning a Workload",
+  "ordinal": 108,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a Workload",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+        "clustering_title": "Provisioning a Workload"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+        "clustering_title": "Provisioning a Workload"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md b/corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
new file mode 100644
index 0000000..595d446
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
@@ -0,0 +1,15 @@
+# Provisioning a Workload
+
+At this point, the cluster is ready for workloads to be provisioned to it. Within the Instance provisioning wizard (See Provisioning > Instances documentation for more details on provisioning), there is now the “HVM” Instance Type. This Instance will allow you to choose from any HVM cluster-compatible images within your environment. Out of the box, VM Essentials does not include any compatible images but there is a section later in this guide covering the process of onboarding existing QCOW images into the UI as Virtual Images and another section covering the process of prepping Windows images from the downloaded ISO.
+
+After arriving at the Configure tab of the provisioning wizard, select a Plan based on resource needs. From the **RESOURCE POOL** field, select the desired HVM cluster. When configuring **VOLUMES** for the new workload, note that space can be claimed from the configured volume. Within **NETWORKS**, we can add the new workload to one of the **VLANS** set up as part of cluster creation. Finally, note that we can choose the HOST the workload should run on in addition to selecting the compatible image.
+
+TIP
+
+The VOLUMES configuration within the provisioning wizard includes a flyout menu allowing storage type (standard, thin, thick (lazy zero), and thick (eager) and storage profile (cache: none or cache: directsync) configurations to be set on each individual volume.
+
+Review and complete the provisioning wizard. After a short time, the workload should be up and running. With a workload now running on the cluster, we can take a look at some of the monitoring, migration, failover, and other actions we can take for workloads running on HVM clusters.
+
+NOTE
+
+HVM clusters support CPU pinning (tying specific vCPUs associated with running workloads to specific physical CPU cores). Currently, this must be done manually by accessing the appropriate HVM host and issuing `virsh` commands or editing XML. Adding UI tools to view and control CPU pinning is on the product roadmap to be added in the near future. Despite the requirement to edit CPU pinning manually, this is a supported action for workloads running on HVM clusters.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json b/corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
new file mode 100644
index 0000000..a8acb95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+  "title": "Plugins",
+  "ordinal": 256,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.html",
+  "topic_cluster": {
+    "clustering_title": "Plugins",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+        "clustering_title": "Plugins"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+        "clustering_title": "Plugins"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md b/corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
new file mode 100644
index 0000000..366284f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
@@ -0,0 +1,21 @@
+# Plugins
+
+## About this task
+
+The Plugins allow you to extend the functionality of HPE Morpheus VM Essentials beyond its default capabilities.
+
+To add a plugin, perform the following:
+
+## Procedure
+
+1. Navigate to Administration > Integrations.
+2. Click Plugins tab.
+3. Click ADD.
+4. You can upload the `.jar` file using either of the following:
+
+   - Drag and drop the file into the upload window.
+   - Select the file manually and click UPLOAD.
+
+## Results
+
+The plugin activates automatically if the validation succeeds.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json b/corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
new file mode 100644
index 0000000..4f90b16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+  "title": "User Access",
+  "ordinal": 89,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.html",
+  "topic_cluster": {
+    "clustering_title": "User Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+        "clustering_title": "User Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+        "clustering_title": "User Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md b/corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
new file mode 100644
index 0000000..c9e71fe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
@@ -0,0 +1,5 @@
+# User Access
+
+IMPORTANT
+
+User access to Groups is determined by their Role(s). Group access for Roles can be configured in the Group Access section of a Role’s Settings.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json b/corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
new file mode 100644
index 0000000..057e2ee
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+  "title": "Execute Scheduling",
+  "ordinal": 69,
+  "parent_title": "Automation",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+        "clustering_title": "Execute Scheduling"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+        "clustering_title": "Execute Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md b/corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
new file mode 100644
index 0000000..2ba40af
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
@@ -0,0 +1,31 @@
+# Execute Scheduling
+
+Execute Scheduling creates time schedules for automated jobs, such as backups. Backup Jobs are discussed in greater detail in the Backups section and are configured with an execution schedule to coordinate their run times. This section goes through the process of creating and configuring the scheduling object.
+
+Schedules use CRON expressions, such as `0 23 * * 2` equalling `Executes every week on Tuesday at 23:00`. CRON expressions can easily be created by clicking the corresponding translation in the create or edit Execution Schedule modal below the Schedule field and selecting a new value.
+
+NOTE
+
+Execute Schedules CRON expressions should not include seconds or years. The days of the week should be numbered 1-7, beginning with Monday and ending with Sunday. SUN-SAT notation may also be used. For more on writing CRON expressions, many guides are hosted on the Internet including [this one](https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm). VM Essentials execution schedules support most cron syntax but certain more complex expressions may fail to evaluate and the execute schedule will not save. Additionally, some complex expressions may save and work correctly while the friendly written evaluation below the SCHEDULE field is not interpreted correctly. This is due to an issue with the underlying library used to build this feature and cannot easily be resolved at this time.
+
+NAME
+:   Name of the Execution Schedule
+
+    NOTE
+
+    When assigning Execution Schedules, the name value will appear in the selection drop-down. Using a name that makes clear the time interval is often helpful.
+
+DESCRIPTION
+:   Description of the Execution Schedule for reference in the Execution Schedules list
+
+TIME ZONE
+:   The time zone for execution
+
+Enabled
+:   Check to enable the schedule. Uncheck to disable all associated executions and remove the schedule as an option for Jobs in the future
+
+SCHEDULE
+:   Enter CRON expression for the Execution Schedule, for example `0 0 * * *` equals `Every day at 00:00`
+
+SCHEDULE TRANSLATION
+:   The entered CRON schedule is translated below the SCHEDULE field. Highlighted values can be updated by selecting the value, and relevant options will be presented. The CRON expression will automatically be updated
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json b/corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
new file mode 100644
index 0000000..1ae2293
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+  "title": "Storage",
+  "ordinal": 173,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md b/corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
new file mode 100644
index 0000000..6d0a896
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
@@ -0,0 +1,23 @@
+# Storage
+
+Infrastructure  >  Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in VM Essentials.
+
+**Subtopics**  
+
+- **[Role Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.html)**
+- **[Default Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A745B955-2E59-4769-AB47-E32098A84653.html)**
+- **[Supported Bucket Types](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.html)**
+- **[Alibaba Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.html)**
+- **[Amazon S3 Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.html)**
+- **[Azure Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.html)**
+- **[Google Cloud Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.html)**
+- **[Dell EMC ECS Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.html)**
+- **[Openstack Swift Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.html)**
+- **[Rackspace CDN Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.html)**
+- **[Supported File Share Types](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.html)**
+- **[CIFS File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.html)**
+- **[Local Storage File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.html)**
+- **[NFSv3 File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html)**
+- **[Create Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.html)**
+- **[Manage Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.html)**
+- **[Add Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json b/corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
new file mode 100644
index 0000000..b2b5c47
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+  "title": "HPE Morpheus VM Essentials Software",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus VM Essentials Software",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+        "clustering_title": "HPE Morpheus VM Essentials Software"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+        "clustering_title": "HPE Morpheus VM Essentials Software"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md b/corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
new file mode 100644
index 0000000..d23edae
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
@@ -0,0 +1,12 @@
+# HPE Morpheus VM Essentials Software
+
+**Subtopics**  
+
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.html)**
+- **[Operations](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.html)**
+- **[Library](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html)**
+- **[Infrastructure](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.html)**
+- **[Tools](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html)**
+- **[Administration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AAD13737-533B-491F-A155-DDB027057157.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json b/corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
new file mode 100644
index 0000000..37e39fd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+  "title": "Image Preparation",
+  "ordinal": 334,
+  "parent_title": "Creating a Windows Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.html",
+  "topic_cluster": {
+    "clustering_title": "Image Preparation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+        "clustering_title": "Image Preparation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+        "clustering_title": "Image Preparation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md b/corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
new file mode 100644
index 0000000..f4c087f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
@@ -0,0 +1,34 @@
+# Image Preparation
+
+## About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing VM Essentials, provisioning and post deploy scripts can expand drives to desired sizing.
+
+## Procedure
+
+1. Ensure VMware Tools is installed on the operating system.
+2. Apply any service packs / updates to the operating system.
+3. Configure WinRM to allow remote management and open the firewall. This is optional if using VMware Tools RPC mode for agent install and VM Essentials Agent for guest exec. To enable this, under local computer Administrator, open a command prompt and run 
+
+   ```
+   ```
+   winrm quickconfig
+   ```
+   ```
+4. Install .Net at least 4.5.2
+5. Ensure Windows Firewall will allow WinRM connections.
+6. Shutdown the virtual machine and convert to a template.
+
+## Results
+
+NOTE
+
+WinRM is not required and is used as a fallback when using vmtools guest exec and customizations
+
+NOTE
+
+Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
+
+IMPORTANT
+
+VM Essentials supports the use of SR-IOV network adapters with VMware Clouds. Windows images must have SR-IOV network drivers installed to work with this adapter type. If they do not, provisioning will fail.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json b/corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
new file mode 100644
index 0000000..ab56957
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+  "title": "Instances",
+  "ordinal": 41,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md b/corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
new file mode 100644
index 0000000..23ab26a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
@@ -0,0 +1,5 @@
+# Instances
+
+VM Essentials starts with provisioning Instances. In some platforms, an Instance is representative of a singular object like a virtual machine in VMware vCenter. In VM Essentials, this concept was rethought. An Instance is more of a representation of a resource or service. This service may involve several virtual machines, as in the case of a database cluster or horizontally-scaled web servers.
+
+When viewing an Instance detail page, one is able to look at details and statistics specific to a virtual machine or container. VM Essentials simply helps simplify the management model for tracking these services.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json b/corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
new file mode 100644
index 0000000..360a4b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+  "title": "Overview",
+  "ordinal": 290,
+  "parent_title": "License",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md b/corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
new file mode 100644
index 0000000..fdad66a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
@@ -0,0 +1,3 @@
+# Overview
+
+VM Essentials requires a valid license for provisioning new Instances and Clusters, and converting existing Instances to managed. Licenses can be applied and updated in this section, and the current license status, as well as usage metrics, can be checked.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json b/corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
new file mode 100644
index 0000000..d22f045
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+  "title": "Backups",
+  "ordinal": 203,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md b/corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
new file mode 100644
index 0000000..fa5e220
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
@@ -0,0 +1,12 @@
+# Backups
+
+The VM Essentials built-in Backup solution provides VM, Container, Host, Database, File, Directory, Volume and Storage Provider Backup, Snapshot and Replication capabilities. Backups can be automatically configured during provisioning or manually created at any time. Backup Jobs with custom Execution Schedules and retention counts can be created and used across all environments in conjunction with configured Storage Providers. Backups can be restored over current Instances or as new Instances, and downloaded or deleted from VM Essentials.
+
+VM Essentials also integrates with external services to automate availability with other providers.
+
+**Subtopics**  
+
+- **[Initial Backups Setup](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.html)**
+- **[Configuring Backups during Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.html)**
+- **[Summary](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json b/corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
new file mode 100644
index 0000000..166a154
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+  "title": "Overview",
+  "ordinal": 231,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md b/corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
new file mode 100644
index 0000000..387ec01
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
@@ -0,0 +1,3 @@
+# Overview
+
+The bulk migration tool is designed to migrate existing VMs running on integrated VMware vCenter Clouds to HVM Clusters. Thus, creating a migration requires existing vCenter Cloud integration(s) and at least one functional HVM Cluster. See the VMware vCenter integration guide and the HVM Clusters guide elsewhere in this documentation stack for more details on getting started with and using those integrations. Migrations may include multiple VMs and may include both Linux and Windows workloads.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json b/corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
new file mode 100644
index 0000000..fd4ffbb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+  "title": "Windows Provisioning Tips",
+  "ordinal": 317,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Provisioning Tips",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+        "clustering_title": "Windows Provisioning Tips"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+        "clustering_title": "Windows Provisioning Tips"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md b/corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
new file mode 100644
index 0000000..0578b70
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
@@ -0,0 +1,7 @@
+# Windows Provisioning Tips
+
+By default when provisioning windows templates, VM Essentials performs guest customizations which initiates a sysprep. This resets the Administrator user and password. VM Essentials will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json b/corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
new file mode 100644
index 0000000..36747d9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+  "title": "Network",
+  "ordinal": 136,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html",
+  "topic_cluster": {
+    "clustering_title": "Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md b/corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
new file mode 100644
index 0000000..8575f9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
@@ -0,0 +1,11 @@
+# Network
+
+**Subtopics**  
+
+- **[Networks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html)**
+- **[Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html)**
+- **[Routers](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html)**
+- **[IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html)**
+- **[Domains](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json b/corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
new file mode 100644
index 0000000..47ab724
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+  "title": "Multitenancy",
+  "ordinal": 325,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.html",
+  "topic_cluster": {
+    "clustering_title": "Multitenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+        "clustering_title": "Multitenancy"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+        "clustering_title": "Multitenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md b/corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
new file mode 100644
index 0000000..869e9b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
@@ -0,0 +1,3 @@
+# Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json b/corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
new file mode 100644
index 0000000..4f3835d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+  "title": "View HPE Aruba CX DSS Network Integration",
+  "ordinal": 362,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.html",
+  "topic_cluster": {
+    "clustering_title": "View HPE Aruba CX DSS Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+        "clustering_title": "View HPE Aruba CX DSS Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+        "clustering_title": "View HPE Aruba CX DSS Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md b/corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
new file mode 100644
index 0000000..367fbca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
@@ -0,0 +1,19 @@
+# View HPE Aruba CX DSS Network Integration
+
+To view the HPE Aruba CX DSS Network integration, follow these steps:
+:   1. Navigate to Infrastructure > Network > Integrations
+    2. Select the HPE Aruba CX DSS integration from the list.
+
+       ![../../_images/5.1_list_network_integrations.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5F56F425-47AA-4B32-9A7B-48C69C82CFAB-high.png)
+       - `Summary` - Click on the Summary tab to view the summary of the integration.
+
+         ![../../_images/5.2_view_integration_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-0B2B766C-E581-4C17-BE5D-C95F72BDCB20-high.png)
+       - `Switches` - Click the Switches tab to view detailed information about all Aruba CX 10000 switches managed by the integration.
+
+         ![../../_images/5.3_view_integration_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-A5481BCF-8C48-4106-B3C2-F0AD92CEFEE3-high.png)
+       - `Networks` - Click on the Networks tab to view the networks associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-C93D74CC-3795-4FA8-A12A-BADF901EB1AB-high.png)
+       - `Firewalls` - Click on the Firewall tab to view firewall policies associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-FC71FD7B-012A-4291-9519-0AFD8374D65C-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json b/corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
new file mode 100644
index 0000000..c8fa450
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+  "title": "Adding an Archive",
+  "ordinal": 227,
+  "parent_title": "Archives",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an Archive",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+        "clustering_title": "Adding an Archive"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+        "clustering_title": "Adding an Archive"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md b/corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
new file mode 100644
index 0000000..c502d9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
@@ -0,0 +1,16 @@
+# Adding an Archive
+
+To add a new Archive, click + ADD from the Archives list page. Configure the following:
+
+- **NAME:** A friendly name for the Archive in VM Essentials
+- **DESCRIPTION:** An optional description for the Archive
+- **BUCKET:** Select an existing bucket or file share to store files in for this Archive. To integrate a new bucket or file share to use for an Archive, navigate to Infrastructure > Storage
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants selected will have access to the Archive
+- **PUBLIC URL:** When marked, VM Essentials will create a public download URL for all files in the Archive
+
+WARNING
+
+Be sure that no sensitive data will be stored in the Archive if it will be configured to generate public URLs. Anyone with the public URL will be able to download the file without authentication.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json b/corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
new file mode 100644
index 0000000..194d50b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+  "title": "Containers / Nodes / Virtual Machines",
+  "ordinal": 42,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.html",
+  "topic_cluster": {
+    "clustering_title": "Containers / Nodes / Virtual Machines",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+        "clustering_title": "Containers / Nodes / Virtual Machines"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+        "clustering_title": "Containers / Nodes / Virtual Machines"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md b/corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
new file mode 100644
index 0000000..4103f77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
@@ -0,0 +1,3 @@
+# Containers / Nodes / Virtual Machines
+
+In relation to Instances, an Instance can have many nodes. A node is a generic representation of a container or a virtual machine. In most cases, VM Essentials will represent a node as a Container or Virtual Machine depending on the provisioning engine used for the Instance (workload provisioned to a HVM cluster as opposed to a Docker cluster, for example). Node is just a generic naming representation when referring to these types of items. The public VM Essentials developer API, however, often refers to both virtual machines and Docker containers as “containers”. The UI was updated to better delineate this concept for easier understanding but, in essence, the name is valid for both concepts of containerized environments as well as virtual machines.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json b/corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
new file mode 100644
index 0000000..65744ff
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+  "title": "UI",
+  "ordinal": 82,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.html",
+  "topic_cluster": {
+    "clustering_title": "UI",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+        "clustering_title": "UI"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+        "clustering_title": "UI"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md b/corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
new file mode 100644
index 0000000..5256ee8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
@@ -0,0 +1,4 @@
+# UI
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json b/corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
new file mode 100644
index 0000000..8fadc95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+  "title": "Instances",
+  "ordinal": 44,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md b/corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
new file mode 100644
index 0000000..36ea60a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
@@ -0,0 +1,10 @@
+# Instances
+
+Instances are a great starting point for taking advantage of self-service features and spinning up both VMs and containers. The top of the main Instances page shows overall statistics for the listed Instances, including count, status, and resource utilization. You can search for Instances by name, or filter by group, type, or category.
+
+The Instance list contains important information about each Instance, including the Instance name, environment tag, type, IP address and port info, Instance version, the number of virtual machines or containers, the Group, and the associated Cloud.
+
+**Subtopics**  
+
+- **[Creating Instances](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.html)**
+- **[Managing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json b/corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
new file mode 100644
index 0000000..3e872b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+  "title": "Tenant Management Settings",
+  "ordinal": 266,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Management Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+        "clustering_title": "Tenant Management Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+        "clustering_title": "Tenant Management Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md b/corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
new file mode 100644
index 0000000..1c6f78b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
@@ -0,0 +1,13 @@
+# Tenant Management Settings
+
+Registration Enabled
+:   If enabled, the appliance login screen will have a “NEED AN ACCOUNT? SIGN UP HERE” link added, enabling new Tenant registration.
+
+Default Tenant Role
+:   Sets the default Tenant Role applied to Tenants created from Tenant Registration.
+
+Default User Role
+:   Sets the default User Role applied to the User created from a Tenant Registration.
+
+Docker Privileged Mode
+:   Enable to allow Docker containers running on VM Essentials Docker hosts to run in privileged mode which adds additional access to the host hardware and resources but also comes with additional security risks
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json b/corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
new file mode 100644
index 0000000..b23ebc4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+  "title": "Viewing the Summary page",
+  "ordinal": 370,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing the Summary page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+        "clustering_title": "Viewing the Summary page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+        "clustering_title": "Viewing the Summary page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md b/corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
new file mode 100644
index 0000000..440bb5b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
@@ -0,0 +1,43 @@
+# Viewing the Summary page
+
+The Summary tab displays system information, the capacity utilization of the system, and the number of ransomwares detected.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server. The Summary tab displays the information for the selected server. ![Summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-CADEC596-4D47-4B87-85E1-DC2756B5DAD8-high.png)
+
+   The Summary tab contains:
+
+   - **System**
+
+     The following information is displayed in the System tile:
+     - **Name**: Displays the system name of the selected server.
+     - **Model**: Displays the model name of the system.
+     - **Serial Number**: Displays the serial number of the system.
+     - **Health status**: Displays the system health status of the array depending on the highest severity type of the alerts listed in the Alerts tab for the storage system. The health status values can be Critical, Normal, or Warning.
+
+       | Highest Severity Type of Alerts | Health status |
+       | --- | --- |
+       | Critical or Fatal | Critical (The system has some major issues that will affect performance) |
+       | Major | Warning (The system is operational but with some non-critical issues) |
+       | Other types | Normal (The system is functioning as expected) |
+     - **Firmware version**: Displays the firmware version of the storage system.
+     - **WWN**: Displays a unique identifier name of the system.
+     - **Uptime**: Displays the total time that the system has been operational.
+     - **IP Address**: Displays the IP address of the system.
+   - **Capacity Utilization**
+
+     The Capacity Utilization tile displays the total and used capacity percentage of the selected storage system.
+
+     - For models HPE Alletra MP B10000 and later, the Capacity Utilization tile populates the usable capacity.
+     - For models prior to HPE Alletra MP B10000, the Capacity Utilization tile populates the raw capacity information.
+
+     NOTE
+
+     You can get the latest system information by clicking the Summary tab.
+   - **Ransomware Detection**
+
+     The Ransomware Detection tile displays the number of ransomwares detected. A hyperlink is displayed when more than one ransomware alert is detected; otherwise, it is displayed as a plain text.
+
+     On clicking the hyperlink, you can view the details of alert by selecting Ransomware monitoring as the Filter by Type.
+
+     ![Alerts - ransomware monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-0E521724-F9E5-4619-B9D9-BB943E488958-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json b/corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
new file mode 100644
index 0000000..25fc4f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+  "title": "Hosts / Servers",
+  "ordinal": 43,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.html",
+  "topic_cluster": {
+    "clustering_title": "Hosts / Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+        "clustering_title": "Hosts / Servers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+        "clustering_title": "Hosts / Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md b/corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
new file mode 100644
index 0000000..2966bb9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
@@ -0,0 +1,5 @@
+# Hosts / Servers
+
+This concept is mostly tailored to users of VM Essentials who are responsible for managing and maintaining the underlying infrastructure integrations. A Host typically refers to a Docker Host in which a container (within an Instance) is running, or a hypervisor that virtual machines can be provisioned onto. A server is the underlying general representation of a physical or virtual server. It could be a Host representation, a Virtual Machine, or even a Bare Metal delineation.
+
+When a user provisions a VM-based Instance, a corresponding server record is created to represent the link to the actual resource via the underlying provisioning engine. This may seem a bit odd but provides an aspect of VM Essentials that is quite powerful. This singular concept is what allows VM Essentials to ingest “brownfield” environments. We do not need to start clean. VM Essentials can be integrated into existing environments and manage existing virtual machines. The way VM Essentials does this is by periodically syncing existing VMs from the added cloud integrations. A server record will be created and periodically updated (every five minutes, by default) with realtime information and changes. This, in essence, provides CMDB-like capabilities as well. When a server is discovered, the user (given the appropriate access) can convert the virtual machine to a managed Instance. When this is done, a corresponding Instance is made in the provisioning section of VM Essentials and the VM Essentials Agent can optionally be installed to provide more refined guest operating system-level statistics and logging.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json b/corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
new file mode 100644
index 0000000..830e974
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+  "title": "Create Datastore",
+  "ordinal": 367,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html",
+  "topic_cluster": {
+    "clustering_title": "Create Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+        "clustering_title": "Create Datastore"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+        "clustering_title": "Create Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md b/corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
new file mode 100644
index 0000000..01c89ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
@@ -0,0 +1,42 @@
+# Create Datastore
+
+## About this task
+
+Add a Datastore to the Storage Server.
+
+## Procedure
+
+1. Navigate to Infrastructure > Clusters.
+2. Click into the detail page for the cluster where the datastore is to be created.
+3. Select the Storage tab.
+4. Under the Data Stores sub tab, click + ADD.
+5. From the ADD DATASTORE wizard, input the following: 
+
+   NAME:
+   :   Name of the datastore in HPE Morpheus Enterprise.
+
+   TYPE:
+   :   Select the type of storage system.
+
+   STORAGE SERVER:
+   :   Select the storage server that is created using the ADD STORAGE SERVER wizard.
+
+   PROTOCOL TYPE:
+   :   Select the type of storage protocol.
+
+   RANSOMWARE DETECTION:
+   :   Select the check box to enable ransomware detection for all VMs created with this datastore.
+
+   NOTE
+
+   The datastore creation fails if storage servers other than HPE Alletra Storage MP B10000 are selected along with the Ransomware Detection option.
+
+   CPG
+   :   Use the drop-down list to select a Common Provisioning Group (CPG) for allocating storage to the new datastore.
+6. Click SAVE.
+
+## Results
+
+![Add data store](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-6894A520-8797-40DF-9252-2F696167BA9F-high.png)
+
+The datastore is added and displayed in the Datastore tab. Confirm that its status is healthy.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json b/corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
new file mode 100644
index 0000000..df4551e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+  "title": "Migrations",
+  "ordinal": 230,
+  "parent_title": "Tools",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md b/corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
new file mode 100644
index 0000000..2e35a64
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
@@ -0,0 +1,8 @@
+# Migrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html)**
+- **[Migrations Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html)**
+- **[Migrations Plans](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html)**
+- **[Configuring Windows Workloads (Windows 2022 or later) for Migration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.json b/corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.json
new file mode 100644
index 0000000..15b5cab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+  "title": "Provisioning Images",
+  "ordinal": 76,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5504862E-8120-469D-8708-2290772E5585.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+        "clustering_title": "Provisioning Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+        "clustering_title": "Provisioning Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.md b/corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.md
new file mode 100644
index 0000000..6930027
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5504862E-8120-469D-8708-2290772E5585.md
@@ -0,0 +1,13 @@
+# Provisioning Images
+
+When provisioning a system image, VM Essentials will stream the image from Amazon S3 to the target Cloud if the image is not local to the Cloud.
+
+When using images that already exist in the destination Cloud, such as synced or previously copied images, no image stream from S3 through the VM Essentials Appliance to the destination cloud will take place.
+
+NOTE
+
+The VM Essentials Appliance must be able to download from Amazon S3 when provisioning system images.
+
+NOTE
+
+The VM Essentials Appliance must be able reach and resolve the destination Host when provisioning System Images or uploaded Images for the first time. This included being able to resolve ESXi host names in VMware vCenter clouds, and reach the destination ESXi host over port 443.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json b/corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
new file mode 100644
index 0000000..c47ee73
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+  "title": "Privileges",
+  "ordinal": 329,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.html",
+  "topic_cluster": {
+    "clustering_title": "Privileges",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+        "clustering_title": "Privileges"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+        "clustering_title": "Privileges"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md b/corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
new file mode 100644
index 0000000..d31f80c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
@@ -0,0 +1,80 @@
+# Privileges
+
+Content Library
+:   - All Content Library privileges
+
+Datastore/Datastore Cluster
+:   - Allocate Space
+    - Browse Datastore
+    - Low Level file Operations
+    - Remove File
+    - Update virtual machine files
+    - Update virtual machine metadata
+
+Distributed Switch
+:   - Port configuration operation
+    - Port setting operation
+
+Global
+:   - Log Event
+    - Manage custom attributes
+    - Set custom attribute
+
+Network
+:   - Assign Network
+    - Configure
+    - Remove
+
+Resource
+:   - Apply recommendation
+    - Assign vApp to resource pool
+    - Assign virtual machine to resource pool
+    - Migrate powered off virtual machine
+    - Migrate powered on virtual machine
+
+Scheduled task
+:   - Create tasks
+    - Modify task
+    - Remove task
+    - Run task
+
+Tasks
+:   - Create task
+    - Update task
+
+Virtual Machine
+:   - Configuration (all)
+    - Guest Operations (all)
+    - Interaction (all)
+    - Inventory (all)
+    - Provisioning (all)
+    - Service configuration (all)
+    - Snapshot management (all)
+    - vSphere Replication (all)
+
+vApp
+:   - Clone
+    - Export
+    - Import
+
+vSphere Tagging
+:   - Assign or Unassign vSphere Tag
+    - Assign or Unassign vSphere Tag on Object
+    - Create vSphere Tag
+    - Create vSphere Tag Category
+    - Delete vSphere Tag
+    - Delete vSphere Tag Category
+    - Edit vSphere Tag
+    - Edit vSphere Tag Category
+    - Modify UsedBy Field For Category
+    - Modify UsedBy Field For Tag
+    - privilege.InventoryService.Tagging.CreateScope.label
+    - privilege.InventoryService.Tagging.DeleteScope.label
+
+With the User and Role created, add permissions to associate the User and Role to the appropriate usage constructs. Navigate to the usage construct you wish to work with, navigate to the permissions tab, click the plus (+) button. In the screenshot below, I’m adding the permission for the vCenter usage construct. The complete list of usages and whether or not to mark the propagation box is below the image.
+
+NOTE
+
+For organization and security purposes, permissions can also be added to folders. This allows VM Essentials to see the folders and onboard any resources within them (if desired). Once the vCenter Cloud integration has been created in VM Essentials, you can view folders from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > ResourcesTab). By editing the folder here (Actions > Edit), folders can be set as the “Default” and/or the “Image Target”. When a folder is set as Default, this folder is pre-selected when provisioning new Instances into the Cloud. When a folder is set as the Image Target, VM Essentials will look into this folder to onboard VMware images into VM Essentials.
+
+![../../../_images/addPerms.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-C8A5BC12-8BBF-47AF-A193-BD89D2392417-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json b/corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
new file mode 100644
index 0000000..41985ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+  "title": "Instances By Cloud",
+  "ordinal": 12,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.html",
+  "topic_cluster": {
+    "clustering_title": "Instances By Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+        "clustering_title": "Instances By Cloud"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+        "clustering_title": "Instances By Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md b/corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
new file mode 100644
index 0000000..c7551b0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
@@ -0,0 +1,5 @@
+# Instances By Cloud
+
+The total number of Clouds which currently have an Instance provisioned is shown. Hover over each section of the pie chart to see the total number and percentage of Instances provisioned to each Cloud
+
+The number of Instances that have existed at any point in the day with additional breakdown to show the number provisioned to each Cloud. This number will include any pre-existing Instances which have carried over from previous days along with any new Instances that were provisioned and existed on that day even for a short time
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json b/corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
new file mode 100644
index 0000000..3995339
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+  "title": "Supported Versions",
+  "ordinal": 333,
+  "parent_title": "Creating a Windows Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+        "clustering_title": "Supported Versions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+        "clustering_title": "Supported Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md b/corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
new file mode 100644
index 0000000..32be7b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
@@ -0,0 +1,3 @@
+# Supported Versions
+
+2008R2, 2012, 2012R2, 2016, 2019, 2022
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json b/corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
new file mode 100644
index 0000000..fac5055
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+  "title": "Linux Agent",
+  "ordinal": 36,
+  "parent_title": "SSH/Winrm",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+        "clustering_title": "Linux Agent"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+        "clustering_title": "Linux Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md b/corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
new file mode 100644
index 0000000..6e6cdec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
@@ -0,0 +1,4 @@
+# Linux Agent
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json b/corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
new file mode 100644
index 0000000..ecafbc3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+  "title": "Virtual Images",
+  "ordinal": 70,
+  "parent_title": "Library",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md b/corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
new file mode 100644
index 0000000..a18bd0d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
@@ -0,0 +1,8 @@
+# Virtual Images
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.html)**
+- **[Configuring Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html)**
+- **[Provisioning Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5504862E-8120-469D-8708-2290772E5585.html)**
+- **[Add Virtual Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json b/corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
new file mode 100644
index 0000000..a5cc963
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+  "title": "Role Permissions",
+  "ordinal": 57,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md b/corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
new file mode 100644
index 0000000..64e51dd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
@@ -0,0 +1,7 @@
+# Role Permissions
+
+The User Role Permission ‘Provisioning: Tasks FULL’ is required to create, edit and delete Tasks.
+
+**Subtopics**  
+
+- **[Common Options](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json b/corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
new file mode 100644
index 0000000..5f72a79
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+  "title": "Proxies",
+  "ordinal": 165,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html",
+  "topic_cluster": {
+    "clustering_title": "Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md b/corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
new file mode 100644
index 0000000..d2597a5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
@@ -0,0 +1,8 @@
+# Proxies
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.html)**
+- **[Defining Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.html)**
+- **[Cloud Communication](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.html)**
+- **[Provisioning with Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json b/corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
new file mode 100644
index 0000000..ff6c81f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+  "title": "Requirements",
+  "ordinal": 27,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md b/corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
new file mode 100644
index 0000000..f850cec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
@@ -0,0 +1,13 @@
+# Requirements
+
+Provisioning Instances typically involves many steps beyond starting a workload and VM Essentials is centered around automating everything for your application to be fully operational. There is a lot that goes on when spinning up an Instance, and to make the magic happen a few requirements need to be met.
+
+IMPORTANT
+
+By default, Agent Installation is enabled when provisioning unless deselected on the Virtual Image or SKIP AGENT INSTALL is selected from the provisioning wizard.
+
+**Subtopics**  
+
+- **[VM Provision Steps](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.html)**
+- **[Agent Install](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json b/corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
new file mode 100644
index 0000000..937ff81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+  "title": "IP Pools",
+  "ordinal": 153,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html",
+  "topic_cluster": {
+    "clustering_title": "IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md b/corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
new file mode 100644
index 0000000..f48e769
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
@@ -0,0 +1,8 @@
+# IP Pools
+
+Infrastructure  >  Network  >  IP Pools
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-238F9226-4EB4-4E14-B533-584277951C4B.html)**
+- **[To add a VM Essentials Network Pool](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json b/corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
new file mode 100644
index 0000000..b8f7b8e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+  "title": "GPU Passthrough Example",
+  "ordinal": 134,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html",
+  "topic_cluster": {
+    "clustering_title": "GPU Passthrough Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md b/corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
new file mode 100644
index 0000000..11d45f6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
@@ -0,0 +1,25 @@
+# GPU Passthrough Example
+
+In a previous section, a Service Plan was created which consumes a GPU when a VM is provisioned using that Plan. This section shows an example provisioning a workload using that Plan and a GPU-accelerated workload running on the VM. In this example, there is an Nvidia GeForce RTX 3050 connected to one of the HVM Hosts. By passing the GPU hardware through to a provisioned VM, hardware-accelerated AI workloads can be run on the VM.
+
+Begin by navigating to Provisioning > Instances. The list of all currently-managed Instances is here along with high level information (power state, etc). To begin a new Instance, click + ADD. Choose type HVM and click NEXT. On the next pane, choose the Group and Cloud in which your desired HVM Cluster resides, name the Instance, and click NEXT.
+
+On the CONFIGURE tab, the main thing to note for this example is the PLAN configuration. This dropdown contains some default Plans that are included with HPE Morpheus VM Essentials and compatible with the HVM provisioning technology (named “1 CPU, 1GB Memory”, etc). This dropdown also includes user-created Plans, such as those you’ve created to consume GPU hardware. In the screenshot below, you can see the “GPU Plan” was selected.
+
+![../../_images/showPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-1FD71B7E-138D-4F35-B57F-AA2C3AA2E357-high.png)
+
+From here, complete the Instance provisioning wizard selecting any automation or lifecycle configurations and wait for the Instance provisioning to complete.
+
+With provisioning complete, check the attached device(s) from the HPE Morpheus VM Essentials UI. This is done from the VM level rather than the Instance level. From the Instance detail page, click on the Resources tab. Click on the name of the desired VM to access the VM detail page. Click on the Devices tab. As in the screenshot below, the attached GPU should be shown.
+
+![../../_images/attachedGpu.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5AC07D64-3534-439B-925D-858854858310-high.png)
+
+To go further, open a console session to the new VM either through HPE Morpheus VM Essentials UI or by connecting to the VM over SSH from a local terminal session. Use the `lspci` command to view all devices connected to PCI buses. The attached GPU should be shown here as it is in the UI.
+
+At this point, the VM is ready to run GPU-accelerated workloads normally. To test this, I’ll run Ollama which is an open-source tool designed to make it easy to run large language models (LLMs) locally. In the screenshot below, see the AI chatbot response to an input. This result took only a few seconds thanks to GPU hardware acceleration.
+
+![../../_images/ollamaOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-FEED6AA7-831F-4630-93F2-BD77DAB2EF2C-high.png)
+
+With the request completed, we can run the `ollama ps` command which confirms the model was running under GPU acceleration.
+
+![../../_images/gpuUsed.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-15D2AC03-19A9-47B0-8D16-7EA83603BDF2-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json b/corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
new file mode 100644
index 0000000..5f46bbc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+  "title": "Labels",
+  "ordinal": 52,
+  "parent_title": "Library",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.html",
+  "topic_cluster": {
+    "clustering_title": "Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+        "clustering_title": "Labels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+        "clustering_title": "Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md b/corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
new file mode 100644
index 0000000..2a4012b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
@@ -0,0 +1,23 @@
+# Labels
+
+Labels are a categorization feature designed to allow easier filtering of list views in the VM Essentials Library. The following library constructs can be labeled:
+
+- Clouds
+- Groups
+- Tasks
+- Instances
+- Servers
+- Virtual Images
+
+Labels are visible from the list views of any constructs listed above. By default, labels are turned on in the list view but if they aren’t showing, click the gear icon (⚙) and then click Labels to enable them.
+
+The list view contains a row of filters above the list, one of which is Labels. Enter a search string to find an existing label or click the dropdown button within the field to select an existing label. This will filter the list to show only constructs which have the selected label.
+
+NOTE
+
+Any list may be filtered by any label which exists on any construct. When a label is removed from a construct and no other constructs also have that label, VM Essentials will remove the label from the list during its nightly sync. It is normal for a label to continue to exist in this list, even if it’s not currently applied to any constructs, until the next nightly sync has taken place.
+
+**Subtopics**  
+
+- **[Adding and Removing Labels](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.html)**
+- **[Running Automation Against Label Targets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json b/corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
new file mode 100644
index 0000000..0cf69a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+  "title": "Clusters",
+  "ordinal": 96,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html",
+  "topic_cluster": {
+    "clustering_title": "Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md b/corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
new file mode 100644
index 0000000..0522064
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
@@ -0,0 +1,8 @@
+# Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.html)**
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.html)**
+- **[Cluster Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.html)**
+- **[HVM clusters](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CA806876-1093-4A39-BE62-439C4802A915.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json b/corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
new file mode 100644
index 0000000..4f7c8ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+  "title": "Archive Detail Page",
+  "ordinal": 228,
+  "parent_title": "Archives",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.html",
+  "topic_cluster": {
+    "clustering_title": "Archive Detail Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+        "clustering_title": "Archive Detail Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+        "clustering_title": "Archive Detail Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md b/corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
new file mode 100644
index 0000000..b7e89c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
@@ -0,0 +1,7 @@
+# Archive Detail Page
+
+The Archive detail contains information about the Archive configuration as well as a list of files currently stored in the Archive. The Archive detail is accessed by navigating to the Archives list page (Tools > Archives) and selecting an existing Archive. As on the Archives List Page, users can download a ZIP folder containing all files in the Archive and edit the Archive from the ACTIONS menu.
+
+To delete the Archive, click DELETE. New files are added by clicking + ADD. When adding a new file, users may browse the file system on the local computer to select a file.
+
+From the files list, download or delete individual files by clicking on the appropriate selection from the ACTIONS menu.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json b/corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
new file mode 100644
index 0000000..e553125
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+  "title": "Switch Configuration",
+  "ordinal": 352,
+  "parent_title": "Prerequisites",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.html",
+  "topic_cluster": {
+    "clustering_title": "Switch Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+        "clustering_title": "Switch Configuration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+        "clustering_title": "Switch Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md b/corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
new file mode 100644
index 0000000..ea0514a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
@@ -0,0 +1,53 @@
+# Switch Configuration
+
+## Procedure
+
+1. Configure the management interface and IP address on both switches in the pair
+2. The switch pair must be configured with `vsx-sync` enabled for high availability and redundancy 
+
+   Sample configuration:
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role primary  
+       keepalive peer 192.168.0.1 source 192.168.0.0  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role secondary  
+       keepalive peer 192.168.0.0 source 192.168.0.1  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+3. Create a Multi-Chassis Link Aggregation Group (MC-LAG) between the ArubaCX switch and the upstream network, referred to as `lag1`
+4. Configure the `lag1` interface on both switches in the pair Sample configuration: 
+
+   ```
+   ```
+   interface lag 1 multi-chassis  
+       no shutdown  
+       no routing  
+       vlan trunk native 1  
+       vlan trunk allowed 1,175  
+       lacp mode active  
+       loop-protect
+   ```
+   ```
+5. The switch ports connected to the server’s management interfaces should be set to “Trunk mode” with a “Native VLAN” Sample configuration: 
+
+   ```
+   ```
+   interface 1/1/1  
+   no shutdown  
+   no routing  
+   vlan trunk native 175  
+   vlan trunk allowed 175
+   ```
+   ```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json b/corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
new file mode 100644
index 0000000..5ef9b05
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+  "title": "Deployment Guide",
+  "ordinal": 3,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.html",
+  "topic_cluster": {
+    "clustering_title": "Deployment Guide",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+        "clustering_title": "Deployment Guide"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+        "clustering_title": "Deployment Guide"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md b/corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
new file mode 100644
index 0000000..98a5dbc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
@@ -0,0 +1,3 @@
+# Deployment Guide
+
+Deployment, installation, and initialization information is not contained in this user manual. Please refer to our dedicated HPE Morpheus VM Essentials Software [Deployment Guide](https://www.hpe.com/support/morpheus-vm-essentials-deployment-guide) for information on setting up the product and getting started with the first HVM Cluster.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json b/corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
new file mode 100644
index 0000000..ec864fb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+  "title": "tfvars",
+  "ordinal": 217,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.html",
+  "topic_cluster": {
+    "clustering_title": "tfvars",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+        "clustering_title": "tfvars"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+        "clustering_title": "tfvars"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md b/corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
new file mode 100644
index 0000000..c22b34a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
@@ -0,0 +1,20 @@
+# tfvars
+
+A mountpoint to store tfvars files for Terraform App Blueprints.
+
+Key
+:   Pattern “tfvars/key”
+
+    Example: tfvars/my-aws-account
+
+Value
+:   The values for your tfvars file to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES and the stored values will be available for use.
+
+NOTE
+
+You may also see Cloud profiles stored at the tfvars mountpoint. They will have a key pattern like: “tfvars/profile/cloud/$cloudCode/variables”. Terraform Cloud profiles are created on the Cloud detail page (Infrastructure > Clouds > selected Cloud) under the Profiles tab. They allow Terraform apps and specs to be provisioned across multiple Clouds that require differed tfvars. See the [Cloud profiles](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/profiles.html) page for more.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json b/corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
new file mode 100644
index 0000000..7d3f015
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+  "title": "Groups",
+  "ordinal": 80,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html",
+  "topic_cluster": {
+    "clustering_title": "Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md b/corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
new file mode 100644
index 0000000..9876481
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
@@ -0,0 +1,13 @@
+# Groups
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.html)**
+- **[UI](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.html)**
+- **[CLI](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.html)**
+- **[API](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.html)**
+- **[Adding Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.html)**
+- **[Managing Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.html)**
+- **[Edit Group](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.html)**
+- **[Delete Group](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.html)**
+- **[User Access](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json b/corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
new file mode 100644
index 0000000..9e51f1f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+  "title": "Network Groups",
+  "ordinal": 146,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md b/corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
new file mode 100644
index 0000000..88ce127
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
@@ -0,0 +1,7 @@
+# Network Groups
+
+Network Groups are useful for grouping networks during provisioning and scaling or grouping availability subnets together such that during provisioning vm’s within an instance can be round robin provisioned across availability zones.
+
+**Subtopics**  
+
+- **[Adding Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json b/corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
new file mode 100644
index 0000000..78e5ac7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+  "title": "Delete Key Pair",
+  "ordinal": 200,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+        "clustering_title": "Delete Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+        "clustering_title": "Delete Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md b/corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
new file mode 100644
index 0000000..a368fb7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
@@ -0,0 +1,11 @@
+# Delete Key Pair
+
+## About this task
+
+To Delete Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected key pair
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json b/corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
new file mode 100644
index 0000000..70d3366
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+  "title": "Provisioning Settings",
+  "ordinal": 276,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+        "clustering_title": "Provisioning Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+        "clustering_title": "Provisioning Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md b/corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
new file mode 100644
index 0000000..f0e3bd2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
@@ -0,0 +1,29 @@
+# Provisioning Settings
+
+Allow Cloud Selection
+:   Displays or hides Cloud Selection dropdown in Provisioning wizard.
+
+Allow Host Selection
+:   Displays or hides Host Selection dropdown in Provisioning wizard.
+
+Require Environment Selection
+:   Forces users to select and Environment during provisioning
+
+Hide Datastore Stats On Selection
+:   Hides Datastore utilization and size stats in provisioning and app wizards
+
+Cross-Tenant Naming Policies
+:   Enable for the `sequence` value in naming policies to apply across tenants
+
+Reuse Naming Sequence Numbers
+:   When selected, sequence numbers can be reused when Instances are removed. Deselect this option and VM Essentials will track issued sequence numbers and use the next available number each time.
+
+Show Console Keyboard Layout Settings
+:   When enabled Users will see keyboard layout settings in console sessions
+
+Deployment Archive Store
+:   Default Storage Provider for storing Deployment Archives.
+
+    NOTE
+
+    Storage Providers can be configured and managed in the Infrastructure  >  Storage section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json b/corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
new file mode 100644
index 0000000..39c89dc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+  "title": "UUID",
+  "ordinal": 219,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.html",
+  "topic_cluster": {
+    "clustering_title": "UUID",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+        "clustering_title": "UUID"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+        "clustering_title": "UUID"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md b/corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
new file mode 100644
index 0000000..9fefb19
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
@@ -0,0 +1,20 @@
+# UUID
+
+A Cypher UUID Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+Key
+:   Pattern “uuid/key”
+
+    - Example: uuid/myuuid
+
+Value
+:   Leave the Value filed blank for UUID, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the UUID will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate UUID.
+
+To delete the UUID, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json b/corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
new file mode 100644
index 0000000..dcd729c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+  "title": "Overview",
+  "ordinal": 91,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md b/corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
new file mode 100644
index 0000000..0e60a08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
@@ -0,0 +1,3 @@
+# Overview
+
+In VM Essentials, a Cloud represents a grouping of HVM clusters (referred to as a “Private Cloud”) or an integration with a VMware vCenter appliance. This section describes general information about the Clouds construct and UI pages for Clouds. See the VMware integration guide for more specific details on integrating with VMware and the features supported by VM Essentials.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json b/corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
new file mode 100644
index 0000000..00624d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+  "title": "Create New Router",
+  "ordinal": 150,
+  "parent_title": "Routers",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-61053EC5-4910-454F-8B71-6B06408A6451.html",
+  "topic_cluster": {
+    "clustering_title": "Create New Router",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+        "clustering_title": "Create New Router"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+        "clustering_title": "Create New Router"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md b/corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
new file mode 100644
index 0000000..fabff5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
@@ -0,0 +1,8 @@
+# Create New Router
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click + ADD
+3. Select the router type and complete the fields on the resulting modal
+4. Once complete, click ADD NETWORK ROUTER
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json b/corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
new file mode 100644
index 0000000..17365d9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+  "title": "HVM Cluster Networking",
+  "ordinal": 109,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Cluster Networking",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+        "clustering_title": "HVM Cluster Networking"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+        "clustering_title": "HVM Cluster Networking"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md b/corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
new file mode 100644
index 0000000..ef30901
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
@@ -0,0 +1,49 @@
+# HVM Cluster Networking
+
+On initial cluster provisioning, OVS bridges and Libvirt Networks are created and are immediately ready for VM provisioning. However, when adding new network interfaces, you may need to create networking objects in the UI manually. Currently, the HPE Morpheus VM Essentials Software Manager does not discover new interfaces that are not in netplan. You'll need to ensure they are in the `01-base.yml` netplan file, apply it, create the bonds in the `hpe-vm` tool, and then refresh the HVM Cluster via the UI. See the installation section at the beginning of this documentation repository for more information on the `hpe-vm` tool and its use.
+
+HVM network objects are created from the Network tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the HVM Cluster). Two subtabs are shown here for Routers and Networks. From a KVM perspective, OVS Bridges and Libvirt Networks (without any port groups) are created on the Routers subtab. Port Group entries are added to existing Libvirt Networks on the Networks subtab. For this reason, it's often most logical to begin creating new HVM network objects on the Routers subtab before moving onto the Networks subtab. For a higher level discussion and diagram of recommended HVM Cluster network topology and to see where these objects fit in, refer back to the example network configurations in the "Getting Started" section of this user manual.
+
+Adding Routers
+
+1. From the Routers subtab, click + ADD, then select OVS Bridge Domain
+
+   ![The list of router objects associated with an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-BBBDCD20-D1FA-4F83-99A8-84F136F334AF-high.png)
+2. On the ADD NETWORK ROUTER modal, configure the following:
+
+   1. **GROUP:** Select "Shared" to make the router object available to all Groups or select an individual Group
+   2. **NAME:** A name for the router object in HPE Morpheus VM Essentials Software
+   3. **HOST BRIDGE:** Select an existing OVS bridge or choose "Create New"
+   4. **BRIDGE NAME:** Shown only when opting to create a new Host Bridge. Provide a name for the new OVS bridge to be created. The bridge name value entered here will be used to identify the bridge throughout the UI while examining the created objects via a terminal session connected to the Host will show it identified by the interface name
+   5. **NETWORK INTERFACE:** Shown only when opting to create a new Host Bridge. Select a network interface for the new OVS bridge. Keep in mind that currently new interfaces are not discovered automatically. See the opening paragraph of this section for more information on surfacing the new interface to the HVM Cluster
+
+   NOTE
+
+   By adding a router here and selecting an existing OVS bridge, a new Libvirt Network is created without any port groups but no new OVS bridge is created. When selecting "Create New" in the Host Bridge configuration field, a new OVS bridge is created and a new Libvirt Network is also created without any port groups. A free physical interface or bond must be available to create a new OVS bridge and currently these are not automatically discovered by the HVM Cluster. See the opening paragraph of this section for more information on surfacing new interfaces to the HVM Cluster. Libvirt Port Groups are created in the next section on adding networks. For a higher level discussion and diagram of recommended HVM Cluster network topology and to see where these objects fit in, refer back to the example network configurations in the "Getting Started" section of this user manual.
+3. Click ADD NETWORK ROUTER
+
+   ![Adding new router with host bridge created](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-8F3EFC34-3BE1-4E35-B563-E7168F483CC1-high.png)
+
+Once saved, the router object is created and it appears in the list of current routers.
+
+Adding Networks
+
+As mentioned in the previous section, creating network objects on HVM clusters is akin to adding Libvirt Portgroups to an existing Libvirt Network. If continuing from the previous section on adding routers, the OVS bridges and Libvirt networks will be in place to add port groups (referred to as networks here in the UI).
+
+1. From the Networks subtab, click + ADD, then select OVS Port Group
+
+   ![The list of network objects associated with an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-8A44146F-1F64-441D-A007-F3BEC320E60C-high.png)
+2. On the CREATE NETWORK modal, configure the following:
+
+   1. **GROUP:** Select "Shared" to make the router object available to all Groups or select an individual Group
+   2. **NAME:** A name for the network object in HPE Morpheus VM Essentials Software
+   3. **CIDR:** The CIDR range for the new network
+   4. **GATEWAY:** The network gateway address
+   5. **DNS PRIMARY:** The address for the primary DNS server
+   6. **DNS SECONDARY:** The address for the secondary DNS server
+   7. **ROUTER:** Select an existing OVS bridge. If you need to create a new OVS bridge, add a new "OVS Bridge Domain" from the Routers subtab (described above) and select "Create New" for it's "Host Bridge" field configuration. Additional details on router objects are provided above.
+   8. **VLAN ID:** A VLAN ID for the Libvirt Port Group to be created
+   9. **NETWORK POOL:** A typeahead field for selecting a currently-configured IP Pool
+3. Click SAVE CHANGES
+
+   ![Creating a new network object](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-6359D4EE-C3F8-431F-850D-A21F7470714E-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json b/corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
new file mode 100644
index 0000000..284adc6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+  "title": "Overview",
+  "ordinal": 237,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md b/corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
new file mode 100644
index 0000000..fe04374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
@@ -0,0 +1,3 @@
+# Overview
+
+VM Essentials can integrate with many of the most common identity source technologies, such as Active Directory, Okta, and many others. These can be configured via the Identity Sources button on the Users list page (Administration > Users). These integrations map roles within these sign-on tools to equivalent roles in VM Essentials so at first log in users are assigned the appropriate role.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json b/corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
new file mode 100644
index 0000000..b17d430
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+  "title": "A Note on Proxies",
+  "ordinal": 345,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.html",
+  "topic_cluster": {
+    "clustering_title": "A Note on Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+        "clustering_title": "A Note on Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+        "clustering_title": "A Note on Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md b/corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
new file mode 100644
index 0000000..df2d60c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
@@ -0,0 +1,25 @@
+# A Note on Proxies
+
+Proxy configurations are known to vary in some organizations and makes building a base blueprint a little more difficult. In order to fully configure proxies a few environment variables must be set in the /etc/environment file (This can be done automatically in a default user-data script for cloud-init as well in edit cloud).
+
+```
+```
+http_proxy="http://myproxyaddress:8080"  
+https_proxy="http://myproxyaddress:8080"  
+ftp_proxy="http://myproxyaddress:8080"  
+no_proxy=127.0.0.1,localhost,applianceUrl  
+https_no_proxy=127.0.0.1,localhost,applianceUrl
+```
+```
+
+IMPORTANT
+
+It is very important to properly set the no\_proxy list (applianceUrl) should be replaced with the actual appliance url. In future releases, morpheus plans to automatically take care of this.
+
+NOTE
+
+If using cloud-init agent install mode these settings need to be set in the custom Cloud-Init User data section of “Edit Cloud” or “Edit Virtual Image”
+
+IMPORTANT
+
+If using this virtual machine as a docker host, proxy settings must also be configured in the docker config. See Docker guides for instructions on how to properly set this. If necessary this can be wrapped in a task automation workflow for your own use.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json b/corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
new file mode 100644
index 0000000..978156c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+  "title": "Getting Started",
+  "ordinal": 316,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md b/corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
new file mode 100644
index 0000000..c05c099
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
@@ -0,0 +1,23 @@
+# Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow VM Essentials to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json b/corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
new file mode 100644
index 0000000..abca925
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+  "title": "Supported Bucket Types",
+  "ordinal": 177,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Bucket Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+        "clustering_title": "Supported Bucket Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+        "clustering_title": "Supported Bucket Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md b/corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
new file mode 100644
index 0000000..4f07b51
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
@@ -0,0 +1,9 @@
+# Supported Bucket Types
+
+- Alibaba
+- Amazon S3
+- Azure
+- Google Cloud Storage
+- Openstack Swift
+- Rackspace CDN
+- Generic S3
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json b/corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
new file mode 100644
index 0000000..519077e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+  "title": "Hardware Requirements",
+  "ordinal": 105,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-634760AA-7E46-42A7-AD08-85CCE4656873.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+        "clustering_title": "Hardware Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+        "clustering_title": "Hardware Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md b/corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
new file mode 100644
index 0000000..4e65f2b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
@@ -0,0 +1,36 @@
+# Hardware Requirements
+
+- **Operating System**: Ubuntu 24.04 or Ubuntu 22.04
+- **CPU**: One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory**: 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
+- **Disk Space**: For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while VM Essentials will configure Ceph for multi-node clusters
+- **Network Connectivity**: HVM hosts must be assigned static IP addresses. They also need DNS resolution of the VM Essentials appliance and Internet access in order to download and install system packages for dependencies, such as KVM, Open vSwitch (OVS), and more
+
+NOTE
+
+Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.
+
+NOTE
+
+Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus VM Essentials Agent communication with the HPE Morpheus VM Essentials manager | HVM Host | HPE Morpheus VM Essentials manager | 443 | TCP |
+| HPE Morpheus VM Essentials Agent communication with the HVM Host for hypervisor console | HPE Morpheus VM Essentials manager | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus VM Essentials manager | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus VM Essentials manager SSH access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTP) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json b/corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
new file mode 100644
index 0000000..b4076d8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+  "title": "Supported Datastore Types",
+  "ordinal": 111,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-63ADF495-37BF-424E-85F4-614EE91DA301.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Datastore Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+        "clustering_title": "Supported Datastore Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+        "clustering_title": "Supported Datastore Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md b/corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
new file mode 100644
index 0000000..f2f12c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
@@ -0,0 +1,12 @@
+# Supported Datastore Types
+
+In relation to HVM Clusters, discussion of storage primarily centers around datastores, which serve as targets for holding virtual machine disks and storing images. Currently, six datastore types are supported with HVM Clusters:
+
+- Directory Pools
+- NFS Pools
+- GFS2 Pools
+- 3Par
+- HPE Alletra Block Storage HVM
+- HPE Alletra Block Storage Bare Metal
+
+The next several sections will cover Directory Pools, NFS Pools, and GFS2 Pools in detail, including pros and cons of each type, how to configure storage servers, and how to add new datastores through the UI. For more on integrating 3Par servers and HPE Alletra Storage, see the integration guides for those technologies elsewhere in this user manual.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json b/corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
new file mode 100644
index 0000000..fecdf50
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+  "title": "Advanced Options (Search Domains)",
+  "ordinal": 142,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced Options (Search Domains)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+        "clustering_title": "Advanced Options (Search Domains)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+        "clustering_title": "Advanced Options (Search Domains)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md b/corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
new file mode 100644
index 0000000..bb521c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
@@ -0,0 +1,3 @@
+# Advanced Options (Search Domains)
+
+Search domains are appended to DNS searches when a **non** fully qualified domain name (short name) is queried. Search domains can be entered as comma separated values, which will be added to DNS configurations, such as /etc/resolv.conf. These domains are injected through cloud-init or other method chosen for the virtual image.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json b/corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
new file mode 100644
index 0000000..878730a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+  "title": "Setting Heartbeat Datastores",
+  "ordinal": 119,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-64001B38-0509-46D5-854E-3A8500798DEE.html",
+  "topic_cluster": {
+    "clustering_title": "Setting Heartbeat Datastores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+        "clustering_title": "Setting Heartbeat Datastores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+        "clustering_title": "Setting Heartbeat Datastores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md b/corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
new file mode 100644
index 0000000..d0be84b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
@@ -0,0 +1,13 @@
+# Setting Heartbeat Datastores
+
+While not set by default, after creating a datastore, users may choose to set it as a heartbeat datastore. Heartbeat datastores are essential for high-availability failover of VMs in the HVM Cluster. When heartbeat targets are enabled, each HVM Host continuously updates a heartbeat file, which is monitored by the other Hosts. When a Host becomes unavailable, the remaining Hosts detect this by discovering that the heartbeat file is no longer being updated. At that point, the Cluster initiates a failover process to migrate affected VMs to a new host. For greater detail on high-availability and the failover process, see [this knowledge article](https://cdn.support.hpe.com/hpesc/public/docDisplay?docId=sf000111669en_us&docLocale=en_US).
+
+To set selected datastores as heartbeat targets, use the steps below. Multiple heartbeat datastores can be enabled for additional redundancy:
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the Data Stores subtab
+3. Within the Data Stores subtab, edit the desired datastore (pencil icon)
+4. Mark the box labeled "HEARTBEAT TARGET
+5. Click Save changes
+
+![Editing a GFS2 datastore to make it a heartbeat datastore](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5ACF121C-3475-4BFB-8794-ED483A879314-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.json b/corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
new file mode 100644
index 0000000..86d3716
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+  "title": "Setting the default domain on a Network",
+  "ordinal": 163,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-650706CA-915E-4239-9D69-35902E82B60E.html",
+  "topic_cluster": {
+    "clustering_title": "Setting the default domain on a Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+        "clustering_title": "Setting the default domain on a Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+        "clustering_title": "Setting the default domain on a Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.md b/corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
new file mode 100644
index 0000000..cd46239
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
@@ -0,0 +1,9 @@
+# Setting the default domain on a Network
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network.
+2. Edit the target Network.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json b/corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
new file mode 100644
index 0000000..6732e77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+  "title": "System Images",
+  "ordinal": 73,
+  "parent_title": "Configuring Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6549D43B-D0BB-4416-9771-AF11F387B629.html",
+  "topic_cluster": {
+    "clustering_title": "System Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+        "clustering_title": "System Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+        "clustering_title": "System Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md b/corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
new file mode 100644
index 0000000..1b21425
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
@@ -0,0 +1,7 @@
+# System Images
+
+System Virtual Images are pre-configured with metadata and have Cloud-Init or Cloudbase-Init installed. These images are ready to be provisioned with no configuration necessary, however it is required to populate Administration > Settings > Provisioning, Cloud-Init section, with user data as well as User Profile(s) users data when creating additional users prior to provisioning, as the user data from these sections is required when provisioning System provided Virtual Images.
+
+NOTE
+
+System Images settings are not editable.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json b/corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
new file mode 100644
index 0000000..baf7b44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+  "title": "HVM Cluster Storage",
+  "ordinal": 110,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Cluster Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+        "clustering_title": "HVM Cluster Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+        "clustering_title": "HVM Cluster Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md b/corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
new file mode 100644
index 0000000..4bac702
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
@@ -0,0 +1,14 @@
+# HVM Cluster Storage
+
+**Subtopics**  
+
+- **[Supported Datastore Types](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-63ADF495-37BF-424E-85F4-614EE91DA301.html)**
+- **[Datastore Types Pros and Cons](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A1E79BA5-CE31-4357-878E-11464E03158C.html)**
+- **[Directory Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.html)**
+- **[Adding Directory Pools](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.html)**
+- **[NFS Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.html)**
+- **[Adding NFS Pools](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.html)**
+- **[GFS2 Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.html)**
+- **[Adding GFS2 Pools](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3702D75B-9505-40D0-B220-7739F5F72760.html)**
+- **[Setting Heartbeat Datastores](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-64001B38-0509-46D5-854E-3A8500798DEE.html)**
+- **[Maintaining GFS2 Consistency and High Availability](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B3241978-4E00-4630-A8AB-E597193E51E2.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json b/corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
new file mode 100644
index 0000000..1840ed8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+  "title": "For All Agent Install modes",
+  "ordinal": 34,
+  "parent_title": "Agent Install Modes",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-69626666-7280-4AF5-9871-FA2D82CED05E.html",
+  "topic_cluster": {
+    "clustering_title": "For All Agent Install modes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+        "clustering_title": "For All Agent Install modes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+        "clustering_title": "For All Agent Install modes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md b/corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
new file mode 100644
index 0000000..d42267b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
@@ -0,0 +1,20 @@
+# For All Agent Install modes
+
+When an Instance is provisioned and the Agent does not install, verify the following for any agent install mode:
+
+- The VM Essentials `appliance_url` (Administration > Settings) is both reachable and resolvable from the provisioned node.
+- The `appliance_url` begins with to `https://`, not `http://`.
+
+NOTE
+
+Be sure to use `https://` even when using an IP address for the appliance.
+
+- Inbound connectivity access to the VM Essentials Appliance from provisioned VMs and HVM cluster hosts on port 443 (needed for Agent communication)
+- Private images (those not provided with VM Essentials by default) must have their credentials entered. These can be entered or edited in the Library > Virtual Images section by clicking the edit button (pencil icon) next to the appropriate image.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced section during provisioning. IP Pools can also be created in the Infrastructure > Network > IP Pools section and added any Cloud’s network section for IPAM.
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the VM Essentials appliance can be used.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json b/corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
new file mode 100644
index 0000000..da49b5c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+  "title": "Deleting Clouds",
+  "ordinal": 95,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+        "clustering_title": "Deleting Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+        "clustering_title": "Deleting Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md b/corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
new file mode 100644
index 0000000..1902510
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
@@ -0,0 +1,17 @@
+# Deleting Clouds
+
+## About this task
+
+To delete a Cloud:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Clouds link in the sub navigation bar.
+3. Click the Delete icon of the cloud to delete.
+
+## Results
+
+IMPORTANT
+
+All Instances, managed Hosts and VMs must be removed prior to deleting a Cloud.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json b/corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
new file mode 100644
index 0000000..5281925
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+  "title": "Dell EMC ECS Buckets",
+  "ordinal": 182,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.html",
+  "topic_cluster": {
+    "clustering_title": "Dell EMC ECS Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+        "clustering_title": "Dell EMC ECS Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+        "clustering_title": "Dell EMC ECS Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md b/corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
new file mode 100644
index 0000000..050fa0d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
@@ -0,0 +1,84 @@
+# Dell EMC ECS Buckets
+
+## About this task
+
+NOTE
+
+A Dell EMC ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell EMC ECS Bucket.
+
+To Add a Dell EMC ECS Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell EMC ECS bucket.
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json b/corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
new file mode 100644
index 0000000..a71f225
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+  "title": "Adding Tasks",
+  "ordinal": 66,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6B80D87B-8461-414D-9172-07E68896EB06.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+        "clustering_title": "Adding Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+        "clustering_title": "Adding Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md b/corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
new file mode 100644
index 0000000..589fa10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
@@ -0,0 +1,20 @@
+# Adding Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. On the Tasks tab, click the Add button
+3. From the New Task Wizard input a name for the task
+4. Select the type of task from from the type dropdown
+5. Input the appropriate configuration details. These will vary based on the selected Task type.
+6. Once done, click SAVE CHANGES
+
+## Results
+
+TIP
+
+When writing a Task config, it’s often necessary to reference VM Essentials variables which pertain to the specific Instance the Task is being run against. VM Essentials includes a pop-out column along the right side of the Add/Edit Task modal which lists available variables. Click and drag the relevant variable into the config area and VM Essentials will automatically fill in the variable call formatted for the currently chosen Task type. See the screenshot below.
+
+TIP
+
+When writing a Task that calls back into the HPE Morpheus VM Essentials API, pass an `Authorization: Execution <%=executionLeaseToken%>` header. The system API will authenticate against that during the life of the Task execution only. This is preferred over other methods of authorizing Task calls as there was a risk of the token expiring in the middle of the Task run.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json b/corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
new file mode 100644
index 0000000..0b26c2b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+  "title": "Editing volumes",
+  "ordinal": 374,
+  "parent_title": "Volumes tab",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.html",
+  "topic_cluster": {
+    "clustering_title": "Editing volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+        "clustering_title": "Editing volumes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+        "clustering_title": "Editing volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md b/corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
new file mode 100644
index 0000000..25d1a5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
@@ -0,0 +1,28 @@
+# Editing volumes
+
+## About this task
+
+You can edit the volumes individually for VMs created without selecting the Ransomware Detection check box in the ADD DATA STORE screen.
+
+## Procedure
+
+1. Create a datastore without selecting the Ransomware Detection check box. 
+
+   To create a datastore, go to Infrastructure > Clusters, click the cluster name, then click Storage > Add. For more information on creating a datastore, see [Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html).
+2. Create a VM with the Ransomware Detection disabled datastore.
+
+   To begin provisioning a VM instance with the Ransomware Detection disabled datastore, go to Provisioning > Instances. For more information on creating a VM instance, see [Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html).
+3. Navigate to Infrastructure > Storage > Servers > Volumes tab.
+
+   The Actions drop-down menu is available for each volume that has the Ransomware Detection disabled.
+
+   NOTE
+
+   For VMs created with Ransomware Detection enabled datastore, the Actions drop-down is not displayed for such volumes.
+4. Click Actions > Edit.
+
+   The EDIT VOLUME message is displayed.
+
+   ![Edit volume](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-79282845-7740-4731-9DAF-BDAA8AC698BB-high.png)
+5. To change the status, select the Ransomware Detection check box if it is disabled or clear the check box if it is enabled.
+6. Click Save. The changes to the ransomware monitoring are saved.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json b/corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
new file mode 100644
index 0000000..98557e4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+  "title": "CLI",
+  "ordinal": 83,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.html",
+  "topic_cluster": {
+    "clustering_title": "CLI",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+        "clustering_title": "CLI"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+        "clustering_title": "CLI"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md b/corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
new file mode 100644
index 0000000..482c2c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
@@ -0,0 +1,3 @@
+# CLI
+
+To view all groups: `groups list`. To use the group: `groups use <id>` or `groups use "group name"` To get a JSON output of a specific group: `groups get <id> -j` or `groups get "group name" -j`
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json b/corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
new file mode 100644
index 0000000..0c18cfb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+  "title": "Vault",
+  "ordinal": 221,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.html",
+  "topic_cluster": {
+    "clustering_title": "Vault",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+        "clustering_title": "Vault"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+        "clustering_title": "Vault"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md b/corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
new file mode 100644
index 0000000..4b13859
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
@@ -0,0 +1,25 @@
+# Vault
+
+Use this mountpoint to store Cypher secrets in a Hashicorp Vault server backend rather than VM Essentials. Additionally, you can call secrets stored in Vault from this Cypher mountpoint even if they are only saved there and not listed in the VM Essentials Cypher UI. This requires installation and configuration of the Hashicorp Vault plugin. See the YouTube video embedded in this section for more information on adding the plugin, configuration, and a demonstration of its capabilities.
+
+NOTE
+
+It’s recommended that you use a long-lived token as attempts to call Vault-stored values into Tasks will stop working if the token is no longer good. In such a case you’d have to obtain a new token, delete the Cypher entry with the old token, and create a new one to restore functionality once again. Using a long-lived token will prevent the need to do this often.
+
+Key
+:   Pattern “vault/<engineMount>/<secretPath>/data/<key>” (ex. vault/KV2/secret/data/morpheus/lab)
+
+Value
+:   Enter your key/value pair here in valid JSON (ex. {“hello”: “world”} )
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES. The example BASH script below onboards the value stored in Vault from the secret/data/morpheus/lab mountpoint:
+
+```
+```
+from_vault="<%= cypher.read('vault/KV2/secret/data/morpheus/lab') %>"  
+echo $from_vault
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json b/corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
new file mode 100644
index 0000000..847f151
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+  "title": "Agent Install",
+  "ordinal": 32,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+        "clustering_title": "Agent Install"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+        "clustering_title": "Agent Install"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md b/corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
new file mode 100644
index 0000000..5fb334d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
@@ -0,0 +1,18 @@
+# Agent Install
+
+When provisioning an Instance, there are some network and configuration requirements to successfully install the Agent. Typically when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach VM Essentials, or depending on Agent install mode, VM Essentials is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the VM Essentials Appliance via the `appliance_url` set in Administration > Settings over both 443 and 80. When an Instance is provisioned from VM Essentials, it must be able to reach the VM Essentials appliance via the `appliance_url` or the Agent will not be installed.
+
+In addition to the main `appliance_url` in Administration > Settings, additional `appliance_urls` can be set per Cloud in the Advanced options of the Cloud configuration pane when creating or editing a Cloud. When this field is populated, it will override the main appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The VM Essentials current log, located at `/var/log/morpheus/morpheus-ui/current`, is very helpful when troubleshooting Agent installations.
+
+**Subtopics**  
+
+- **[Agent Install Modes](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.html)**
+- **[SSH/Winrm](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.html)**
+- **[VMware tools (vmtools) RPC mode](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.html)**
+- **[Cloud-Init Agent install mode](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json b/corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
new file mode 100644
index 0000000..04a4b45
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+  "title": "Agent Install Modes",
+  "ordinal": 33,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install Modes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+        "clustering_title": "Agent Install Modes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+        "clustering_title": "Agent Install Modes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md b/corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
new file mode 100644
index 0000000..d43b9ab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
@@ -0,0 +1,11 @@
+# Agent Install Modes
+
+There are 3 Agent install modes:
+
+- SSH/WinRM
+- VMware Tools
+- Cloud-init
+
+**Subtopics**  
+
+- **[For All Agent Install modes](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-69626666-7280-4AF5-9871-FA2D82CED05E.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json b/corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
new file mode 100644
index 0000000..0fc8c54
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+  "title": "Summary",
+  "ordinal": 208,
+  "parent_title": "Backups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.html",
+  "topic_cluster": {
+    "clustering_title": "Summary",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+        "clustering_title": "Summary"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+        "clustering_title": "Summary"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md b/corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
new file mode 100644
index 0000000..5d8454a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
@@ -0,0 +1,12 @@
+# Summary
+
+The Backups Summary section shows the following metrics:
+
+- Number of Configured Backups trend
+- Backup Success Rate
+- Number of Completed Backups
+- Number of Failed Backups
+- Total Size of Backups (MB) trend
+- Upcoming and In Progress Backups
+
+If a User’s Role permission for Backups is set to User, the user will only see metrics for backups they own.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json b/corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
new file mode 100644
index 0000000..93dc0b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+  "title": "Overview",
+  "ordinal": 239,
+  "parent_title": "Plans",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md b/corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
new file mode 100644
index 0000000..3102824
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
@@ -0,0 +1,11 @@
+# Overview
+
+Service Plans determine the amount of compute resources available to each Instance. When provisioning new Instances from VM Essentials, a plan is selected which determines the number of CPU cores, amount of memory and the amount of storage available to the associated machines. Additionally, when converting discovered instances in integrated clouds to VM Essentials-managed Instances, the user selects a plan which best fits the instance as it is currently configured. When Instances are reconfigured, a new plan may be selected which redefines the compute resources which should be available to the Instance. Plans can be as specific or open-ended as the user would like, restricting the user to the resources defined in the plan or allowing the user to increase those amounts at provision time.
+
+The Plans section Administration > Plans is where Plans are managed. A set of Service Plans are seeded by VM Essentials for immediate use with supported Cloud type out of the box. Additional Plans may be synced in on integrating additional Clouds depending on the type. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types.
+
+**Subtopics**  
+
+- **[Create Service Plan](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.html)**
+- **[Service Plan Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3E03B539-B71C-4D2E-A218-23713D723408.html)**
+- **[Service Plan Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.json b/corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.json
new file mode 100644
index 0000000..8e6127b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+  "title": "Overview",
+  "ordinal": 149,
+  "parent_title": "Routers",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7138E486-AE62-4778-9358-F098126785A5.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.md b/corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.md
new file mode 100644
index 0000000..719388f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7138E486-AE62-4778-9358-F098126785A5.md
@@ -0,0 +1,5 @@
+# Overview
+
+Routers can be viewed, created, and managed from the Routers tab of the Infrastructure > Networks page. VM Essentials supports the creation of the following router types depending on networks that are currently configured:
+
+- OVS Bridge Domain
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json b/corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
new file mode 100644
index 0000000..54a7ab0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+  "title": "Key",
+  "ordinal": 220,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.html",
+  "topic_cluster": {
+    "clustering_title": "Key",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+        "clustering_title": "Key"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+        "clustering_title": "Key"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md b/corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
new file mode 100644
index 0000000..8475e6f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
@@ -0,0 +1,20 @@
+# Key
+
+A Cypher Key generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key).
+
+Key
+:   Pattern “key/bit\_length/key”
+
+    - Example: key/256/mykey
+
+Value
+:   Leave the Value filed blank for key, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the AES Key will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate AES Key.
+
+To delete the UUID, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json b/corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
new file mode 100644
index 0000000..f0f0c5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+  "title": "API Access",
+  "ordinal": 304,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-74590319-12A6-4101-9043-8DDB56BB0720.html",
+  "topic_cluster": {
+    "clustering_title": "API Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+        "clustering_title": "API Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+        "clustering_title": "API Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md b/corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
new file mode 100644
index 0000000..d9bb04d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
@@ -0,0 +1,18 @@
+# API Access
+
+Click the API Access button to expand the “API ACCESS” modal. In this modal you can generate or refresh access tokens that can be used with Morpheus API and Morpheus CLI.
+
+If no token yet exists for a particular “CLIENT ID”, click ACTIONS and then Generate. If a token has expired, we can also regenerate that token by clicking ACTIONS and then Regenerate. After regenerating a particular token, you would need to ensure any scripts using those tokens are updated.
+
+- **morph-api:** Used for VM Essentials API access and should be the default token-type used
+- **morph-cli:** Used for VM Essentials CLI access
+- **morph-automation:** Used by the internal Task engine and by jRuby-type Tasks to make API calls. It shouldn’t be used externally for other types of access or in external automation. It is surfaced in the UI so users can see if a token exists and can clear it when necessary
+- **morph-customer:** This token is available for legacy implementations and was previously recommended for custom API access (similar to the morph-api token). It’s not recommended for use but is still available to maintain support for legacy custom automation which may still be in use on customer sites
+
+After navigating away from the User Settings page, the complete access and refresh tokens will be masked from view. If these are lost or compromised, you can eliminate a token completely by clicking ACTIONS and then Clear. If you need to generate a new token for the same Client ID, click ACTIONS and then Regenerate.
+
+![../../_images/user-tokens.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-274AD26D-C940-4740-BBC7-7970107CCB4B-high.png)
+
+NOTE
+
+Access Tokens are only displayed/available after generation. Copy new Tokens and store appropriately before navigating from `/user-settings`, they will not be displayed again.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json b/corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
new file mode 100644
index 0000000..2b2ec0e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+  "title": "User Settings",
+  "ordinal": 294,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md b/corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
new file mode 100644
index 0000000..1df1550
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
@@ -0,0 +1,13 @@
+# User Settings
+
+User settings are accessed by clicking on your display name in the far upper-right corner of the application window. In this dropdown menu, click on the “USER SETTINGS” link.
+
+**Subtopics**  
+
+- **[User Photo](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-40300B80-D69C-450B-9848-7A21A3141005.html)**
+- **[2 Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3B34F036-4C25-4058-B5F4-5340545BE821.html)**
+- **[Preferences](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html)**
+- **[Linux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html)**
+- **[API Access](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-74590319-12A6-4101-9043-8DDB56BB0720.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json b/corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
new file mode 100644
index 0000000..a2c8fe0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+  "title": "Deleting Tasks",
+  "ordinal": 68,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+        "clustering_title": "Deleting Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+        "clustering_title": "Deleting Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md b/corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
new file mode 100644
index 0000000..7877e98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
@@ -0,0 +1,6 @@
+# Deleting Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. Click the trash icon (🗑) on the row of the Task you wish to delete
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json b/corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
new file mode 100644
index 0000000..3d8eef4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+  "title": "Role Permission Sections",
+  "ordinal": 248,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+        "clustering_title": "Role Permission Sections"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+        "clustering_title": "Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md b/corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
new file mode 100644
index 0000000..c605cf2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
@@ -0,0 +1,18 @@
+# Role Permission Sections
+
+Features
+:   Controls User access level for UI sections and features in VM Essentials. The complete feature permissions grid is included below.
+
+Groups
+:   Controls User access level for Groups. Groups are not a Multi-Tenant construct, only Groups created in the current Tenant will be visible.
+
+Cluster Types
+:   Controls user access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters (assuming the Role also has feature access to applicable permissions related to adding Clusters) VDI Pools
+
+    Controls User access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+    Workflows
+    :   Controls User access to configured Workflows, including the ability to view, edit, execute, or apply to Library item configurations
+
+Tasks
+:   Controls User access to configured Tasks, including the ability to view, edit, execute, or apply to Workflows
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json b/corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
new file mode 100644
index 0000000..5d2c889
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+  "title": "Editing Existing Routers",
+  "ordinal": 151,
+  "parent_title": "Routers",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Existing Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+        "clustering_title": "Editing Existing Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+        "clustering_title": "Editing Existing Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md b/corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
new file mode 100644
index 0000000..3f7a726
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
@@ -0,0 +1,7 @@
+# Editing Existing Routers
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the pencil icon for the appropriate router
+3. After editing router fields, click SAVE
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json b/corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
new file mode 100644
index 0000000..82b17eb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+  "title": "Editing Tasks",
+  "ordinal": 67,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+        "clustering_title": "Editing Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+        "clustering_title": "Editing Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md b/corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
new file mode 100644
index 0000000..8cc589a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
@@ -0,0 +1,8 @@
+# Editing Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. Click the pencil icon (✎) on the row of the task you wish to edit
+3. Modify Task as needed
+4. Once done, click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json b/corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
new file mode 100644
index 0000000..92eb067
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+  "title": "Converting Discovered Resources to Managed Instances",
+  "ordinal": 46,
+  "parent_title": "Creating Instances",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.html",
+  "topic_cluster": {
+    "clustering_title": "Converting Discovered Resources to Managed Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+        "clustering_title": "Converting Discovered Resources to Managed Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+        "clustering_title": "Converting Discovered Resources to Managed Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md b/corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
new file mode 100644
index 0000000..8dea8c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
@@ -0,0 +1,14 @@
+# Converting Discovered Resources to Managed Instances
+
+When creating new cloud integrations (or updating existing ones), users may opt for VM Essentials to onboard any existing resources that currently reside in the Cloud. For example, these may be virtual machines that exist on vCenter hosts prior to integration with VM Essentials. With the Add/Edit Cloud modal open, mark INVENTORY EXISTING INSTANCES for VM Essentials to automatically onboard these resources. Not only will VM Essentials inventory these hosts at the time the cloud is integrated (or updated), it will also continue to poll the target cloud every five minutes (by default) for newly added or removed servers. Users can see these discovered servers by looking in Infrastructure > Compute. Depending on the type of resource, it may appear on the Virtual Machines tab, the Containers tab, or another tab. Additionally, we can see a list of discovered servers on Cloud detail pages (Infrastructure > Clouds > Selected Cloud). Just click on the tabs for VMs, Containers or Hosts tab. Discovered resources will be indicated as such whereas containers which are associated with a managed Instance will be marked as a “Managed”.
+
+Additionally, VM Essentials allows users to convert discovered resources into managed Instances. Begin from the server detail page (Infrastructure > Compute > Virtual Machines > selected machine) and from the ACTIONS menu select “Convert to Managed”. At this point, we must make a number of selections:
+
+- Select a Group (this dropdown contains a filtered list of Groups in which the associated Cloud resides)
+- Username and password for a seeded account
+- Opt to install VM Essentials Agent or not
+- Select the Instance Type which should be associated with the new Instance containing this VM
+- Identify the operating system
+- Select a Plan (this dropdown contains a filtered list of plans which correlate to the size of the VM)
+
+Finally, click EXECUTE. Once this process is completed, the server will be indicated as “Managed” in the servers list. Additionally, a new Instance will appear on the Instances List page (Provisioning > Instances). We can now work with it in the same way we can work with any other Instance, such as by expanding the Instance horizontally with added nodes.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json b/corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
new file mode 100644
index 0000000..4a03fff
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+  "title": "Create A Backup Job",
+  "ordinal": 308,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.html",
+  "topic_cluster": {
+    "clustering_title": "Create A Backup Job",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+        "clustering_title": "Create A Backup Job"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+        "clustering_title": "Create A Backup Job"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md b/corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
new file mode 100644
index 0000000..e08f865
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
@@ -0,0 +1,22 @@
+# Create A Backup Job
+
+## About this task
+
+A Backup Job in HPE Morpheus Enterprise holds the schedule timing and retention count for automated backups. If you already have a Job configured, you can move on to the next section. If currently-existing options do not make sense for your backup needs or if none currently exist, create a new execution schedule. See the [execute scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html) section of this documentation for additional information on creating these schedules. To begin a new schedule, use the following steps:
+
+## Procedure
+
+1. Navigate to Library > Automation
+2. Click on the “Execute Scheduling” tab
+3. Click + ADD
+4. Enter schedule timing using `cron` notation
+5. Click SAVE
+
+## Results
+
+With the execution schedule created, we can move on to creating the Backup Job itself. A Backup Job includes both the backup retention count and an execution schedule (which we just created).
+
+1. Navigate to Backups > Jobs
+2. Click + ADD
+3. Name the Job, then configure the retention count and select the correct execution schedule
+4. Click SAVE
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json b/corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
new file mode 100644
index 0000000..f67fbe6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+  "title": "Identity Sources",
+  "ordinal": 236,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md b/corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
new file mode 100644
index 0000000..b255a21
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
@@ -0,0 +1,7 @@
+# Identity Sources
+
+Administration > Tenants > (Selected Tenant) > Identity Sources Administration > Users > Identity Sources
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json b/corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
new file mode 100644
index 0000000..92a6158
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+  "title": "Static and IP Pools",
+  "ordinal": 141,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.html",
+  "topic_cluster": {
+    "clustering_title": "Static and IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+        "clustering_title": "Static and IP Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+        "clustering_title": "Static and IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md b/corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
new file mode 100644
index 0000000..2290cd4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
@@ -0,0 +1,42 @@
+# Static and IP Pools
+
+## About this task
+
+To configure a network for Static IP Assignment:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, add the following: 
+
+   - Gateway
+   - DNS Primary
+   - DNS Secondary
+   - CIDR ex 10.10.10.0/22
+   - VLAN ID (if necessary)
+   - Network Pool \* Leave as “choose a pool” for entering a static IP while provisioning \* Select a Pool to use a pre-configured VM Essentials or IPAM Integration IP Pool
+   - The Permissions settings are used for Multi-Tenant resource configuration
+
+     - Leave settings as default if used in a single-tenant environment (only one Tenant in your VM Essentials appliance)
+     - To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public
+     - To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private
+   - Active
+
+     - Leave as enabled to use this network
+     - Disable the active flag to remove this network from available network options
+5. Save Changes
+
+## Results
+
+NOTE
+
+When selecting a network with DHCP disabled and no IP Pool assigned during provisioning, an IP entry field will populate to the right of the selected network(s):
+
+NOTE
+
+When selecting a network with an IP Pool assigned during provisioning, the name of the IP pool will populate to the right of the selected network(s). IP Pools override DHCP.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json b/corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
new file mode 100644
index 0000000..2fd638d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+  "title": "Delete HPE ANW DSS Port Group Network",
+  "ordinal": 361,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.html",
+  "topic_cluster": {
+    "clustering_title": "Delete HPE ANW DSS Port Group Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+        "clustering_title": "Delete HPE ANW DSS Port Group Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+        "clustering_title": "Delete HPE ANW DSS Port Group Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md b/corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
new file mode 100644
index 0000000..619b28e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
@@ -0,0 +1,13 @@
+# Delete HPE ANW DSS Port Group Network
+
+## About this task
+
+To delete a HPE ANW DSS Port Group network, follow these steps:
+
+## Procedure
+
+1. Navigate to
+2. Select the network you want to delete from the list.
+3. Click on the delete icon (🗑) next to the network name. 
+
+   ![../../_images/4_delete_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5DFCE9ED-5DDA-469D-B118-24F0B3AC0429-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json b/corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
new file mode 100644
index 0000000..f235590
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+  "title": "ArubaCX Network Integration",
+  "ordinal": 347,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html",
+  "topic_cluster": {
+    "clustering_title": "ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md b/corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
new file mode 100644
index 0000000..6273a4d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
@@ -0,0 +1,9 @@
+# ArubaCX Network Integration
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.html)**
+- **[Adding ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.html)**
+- **[Add ArubaCX Integration to a Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json b/corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
new file mode 100644
index 0000000..7b2ffdf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+  "title": "Prerequisites",
+  "ordinal": 365,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md b/corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
new file mode 100644
index 0000000..ae0fddc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
@@ -0,0 +1,13 @@
+# Prerequisites
+
+- All HPE Alletra MP Storage iSCSI ports are reachable from each of the cluster hosts
+- The `multipath.conf` settings on each node should be configured as follows:
+
+```
+```
+defaults {  
+    find_multipaths yes  
+    user_friendly_names no  
+}
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json b/corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
new file mode 100644
index 0000000..794e786
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+  "title": "API",
+  "ordinal": 84,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.html",
+  "topic_cluster": {
+    "clustering_title": "API",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+        "clustering_title": "API"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+        "clustering_title": "API"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md b/corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
new file mode 100644
index 0000000..8d4ace2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
@@ -0,0 +1,3 @@
+# API
+
+To view all groups: `curl https://api.gomorpheus.com/api/groups -H "Authorization: BEARER access_token"` To view a specific group: `curl https://api.gomorpheus.com/api/groups/:id -H "Authorization: BEARER access_token"`
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json b/corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
new file mode 100644
index 0000000..0d3d7b4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+  "title": "Infrastructure",
+  "ordinal": 79,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.html",
+  "topic_cluster": {
+    "clustering_title": "Infrastructure",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+        "clustering_title": "Infrastructure"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+        "clustering_title": "Infrastructure"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md b/corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
new file mode 100644
index 0000000..aca7461
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
@@ -0,0 +1,12 @@
+# Infrastructure
+
+The heart of VM Essentials is the ability to manage provisioning across any infrastructure, from bare metal to virtualized clouds and all the way to public infrastructure.
+
+**Subtopics**  
+
+- **[Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html)**
+- **[Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html)**
+- **[Network](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json b/corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
new file mode 100644
index 0000000..9788c14
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+  "title": "Example JSON Map:",
+  "ordinal": 63,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.html",
+  "topic_cluster": {
+    "clustering_title": "Example JSON Map:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+        "clustering_title": "Example JSON Map:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+        "clustering_title": "Example JSON Map:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md b/corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
new file mode 100644
index 0000000..aad0959
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
@@ -0,0 +1,28 @@
+# Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Task is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json b/corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
new file mode 100644
index 0000000..71ca7ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+  "title": "VMware Permissions",
+  "ordinal": 327,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+        "clustering_title": "VMware Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+        "clustering_title": "VMware Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md b/corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
new file mode 100644
index 0000000..e3c0b8a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
@@ -0,0 +1,9 @@
+# VMware Permissions
+
+When integrating VMware vCenter with VM Essentials, users must supply credentials for a vCenter account and VM Essentials will only have access privileges equal to the integrated account. Many users will choose to use a vCenter administrator account so that VM Essentials can freely do any function in vCenter without worrying about hitting access limits. Others, for security reasons, may want to restrict VM Essentials only to the minimum permissions it needs to perform its functions. Follow the guide in this section to configure a user with minimal permissions and associate it with the appropriate usage levels before using it to create a VM Essentials Cloud integration.
+
+**Subtopics**  
+
+- **[Create vCenter Users and Roles](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.html)**
+- **[Privileges](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.html)**
+- **[Usage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json b/corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
new file mode 100644
index 0000000..d64a6aa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+  "title": "VMware - VM Templates Copies",
+  "ordinal": 78,
+  "parent_title": "Add Virtual Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.html",
+  "topic_cluster": {
+    "clustering_title": "VMware - VM Templates Copies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+        "clustering_title": "VMware - VM Templates Copies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+        "clustering_title": "VMware - VM Templates Copies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md b/corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
new file mode 100644
index 0000000..22dd4e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
@@ -0,0 +1,11 @@
+# VMware - VM Templates Copies
+
+In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to VM Essentials, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be synced into VM Essentials.
+
+If all the vCenters are added as Clouds into VM Essentials and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in VM Essentials. This means that as you deploy to the various vCenter Clouds in VM Essentials using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.
+
+VM Essentials supports VMware Content Libraries storing VM templates and syncing into VM Essentials, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.
+
+NOTE
+
+VM templates are a **Datacenter** level object. The same process above applies to a single VMware cloud with multiple logical datacenters. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json b/corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
new file mode 100644
index 0000000..a29eef9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+  "title": "App Blueprint Settings",
+  "ordinal": 281,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.html",
+  "topic_cluster": {
+    "clustering_title": "App Blueprint Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+        "clustering_title": "App Blueprint Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+        "clustering_title": "App Blueprint Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md b/corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
new file mode 100644
index 0000000..bbbcfb9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
@@ -0,0 +1,10 @@
+# App Blueprint Settings
+
+Determines the Default Blueprint Type selected in new App Wizard
+
+- Morpheus
+- ARM Template
+- CloudFormation
+- Terraform
+- Kubernetes Spec
+- Helm Chart
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json b/corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
new file mode 100644
index 0000000..0d9d4e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+  "title": "Overview",
+  "ordinal": 244,
+  "parent_title": "Roles",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md b/corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
new file mode 100644
index 0000000..da709a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
@@ -0,0 +1,15 @@
+# Overview
+
+Within VM Essentials is a wide array of role-based access control capabilities. These roles can be managed within the Administration > Roles section of the VM Essentials UI as well as through the API or CLI. Entire sections within the appliance UI can be hidden based on the specified access levels for features within VM Essentials. Features have different access scopes that can be selected from and can range depending on the specific feature. The most common scope set involves none, read, and full.
+
+There are several handy tricks for creating new roles within VM Essentials and users can be assigned more than one role. When a user is assigned more than one role, permissions are granted by the role with the highest level of scope access. This allows roles to be built with small subsets of features and combined to grant different individuals relevant permission control. With resource permissions (that is, all types of permissions other than Feature permissions), a default access can be given as opposed to a specific (Full or None) permission for any resource. A specific permission will always supersede a default permission regardless of whether it’s more permissive or more restrictive. In other cases (default vs default OR specific vs specific) the more permissive access will be given.
+
+It’s also important to note that built-in Roles, such as the System Admin “Superuser” Role carry no special prominence. For resource permissions, the System Admin user has defaults set to Full in each section. Thus, pairing the System Admin Role with another Role that may include specific line item permissions for various resource categories may cause your System Admin users to take on a reduced permission set.
+
+NOTE
+
+Feature access control not only applies to the VM Essentials UI but also applies to the public developer API. It is sometimes necessary to logout and back in for changes to a users feature access level to be respected.
+
+**Subtopics**  
+
+- **[Role Creation](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json b/corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
new file mode 100644
index 0000000..ce9013d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+  "title": "Mountpoints",
+  "ordinal": 214,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.html",
+  "topic_cluster": {
+    "clustering_title": "Mountpoints",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+        "clustering_title": "Mountpoints"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+        "clustering_title": "Mountpoints"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md b/corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
new file mode 100644
index 0000000..8ff9c93
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
@@ -0,0 +1,27 @@
+# Mountpoints
+
+password
+:   Generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+tfvars
+:   This is a module to store a tfvars file for terraform app blueprints.
+
+secret
+:   This is the standard secret module that stores a key/value in encrypted form.
+
+uuid
+:   Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+key
+:   Generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key)
+
+vault
+:   Configures an integration between VM Essentials and a Hashicorp Vault server. See below for additional configuration instructions.
+
+    - Key lease times are entered in seconds and default to 32 days (2764800 s).
+
+      - Quick Time Reference:
+      - Day: 86400
+      - Week: 604800
+      - Month (30 days): 2592000
+      - Year: 31536000
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json b/corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
new file mode 100644
index 0000000..5ec86f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+  "title": "GFS2 Pools Overview",
+  "ordinal": 117,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.html",
+  "topic_cluster": {
+    "clustering_title": "GFS2 Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+        "clustering_title": "GFS2 Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+        "clustering_title": "GFS2 Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md b/corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
new file mode 100644
index 0000000..68c6d3f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
@@ -0,0 +1,5 @@
+# GFS2 Pools Overview
+
+GFS2 is a shared-disk cluster file system that allows multiple nodes in a cluster to access the same storage at the block level. Adding GFS2 datastores to an HVM Cluster enables live migration and live failover of running VMs.
+
+Administrators only need to present the disks to the HVM Hosts and make a few specific configurations. HPE Morpheus VM Essentials handles everything else, including mounting datastores and enabling multipathing.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json b/corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
new file mode 100644
index 0000000..242d07a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+  "title": "Affinity Groups",
+  "ordinal": 322,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md b/corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
new file mode 100644
index 0000000..c3ce4f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
@@ -0,0 +1,29 @@
+# Affinity Groups
+
+HPE Morpheus VM Essentials Software offers two-way sync for affinity groups with integrated VMware vCenter Clouds. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Affinity groups created from HPE Morpheus VM Essentials create "Should" rules (soft rules) rather than "Must" rules (hard rules) in vCenter. Thus whenever possible, servers configured to "Keep Together" will run on the same cluster host while servers configured to "Keep Separate" will be balanced across cluster hosts to the maximum extent possible. These rules may be broken if necessary to balance resources or recover from failures.
+
+TIP
+
+It is possible to create an empty affinity group (that is, one with no servers selected) in HPE Morpheus VM Essentials even though this is not possible in vCenter. If such an affinity group is created, HPE Morpheus VM Essentials will hold it without syncing to vCenter until at least one server is added and the affinity group becomes compatible with the vCenter API.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-7AD47077-8387-4499-9BDE-BBACFDDA2989-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the VMware Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **CLUSTER:** Select the vCenter cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next Cloud sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-C4C3EDB1-CA6E-4DEA-890C-B5C5B0E3DE13-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-688F89C9-1444-4D3A-94B5-E8DFE9BDC066-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json b/corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
new file mode 100644
index 0000000..b852225
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+  "title": "Rackspace CDN Buckets",
+  "ordinal": 184,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.html",
+  "topic_cluster": {
+    "clustering_title": "Rackspace CDN Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+        "clustering_title": "Rackspace CDN Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+        "clustering_title": "Rackspace CDN Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md b/corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
new file mode 100644
index 0000000..7fbf343
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
@@ -0,0 +1,81 @@
+# Rackspace CDN Buckets
+
+## About this task
+
+To Add a Rackspace CDN Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Rackspace CDN from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   USERNAME
+   :   Rackspace CDN Username
+
+   API KEY
+   :   Rackspace CDN API Key
+
+   REGION
+   :   Enter Rackspace CDN Region
+
+   BUCKET NAME
+   :   Enter existing Rackspace CDN Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+**Subtopics**  
+
+- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-35419962-0058-4856-A6BD-F4923FD0F044.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json b/corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
new file mode 100644
index 0000000..85133f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+  "title": "Overview",
+  "ordinal": 287,
+  "parent_title": "Environments",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md b/corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
new file mode 100644
index 0000000..103a955
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
@@ -0,0 +1,7 @@
+# Overview
+
+The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
+
+**Subtopics**  
+
+- **[Creating Environments](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json b/corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
new file mode 100644
index 0000000..7d2dd0f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+  "title": "Overview",
+  "ordinal": 97,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md b/corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
new file mode 100644
index 0000000..92f8ac2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
@@ -0,0 +1,3 @@
+# Overview
+
+The Infrastructure > Clusters section is where the list of existing HVM clusters can be viewed. Here you can view high-level statistics about all clusters under management by VM Essentials manager, such as aggregate resource usage by all clusters and the number of workloads running across all of them. Click into an existing HVM cluster to view additional metrics such as hosts, VMs, resource utilization by the host, and a lot more.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json b/corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
new file mode 100644
index 0000000..f63787e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+  "title": "Network Interfaces",
+  "ordinal": 337,
+  "parent_title": "Creating a CentOS/RHEL 7 Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Interfaces",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+        "clustering_title": "Network Interfaces"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+        "clustering_title": "Network Interfaces"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md b/corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
new file mode 100644
index 0000000..a831b15
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
@@ -0,0 +1,44 @@
+# Network Interfaces
+
+A slightly annoying change with centOS 7 is that the network interfaces have changed naming convention. You may notice when running ifconfig that the primary network interface is set to something like ens2344 or some other random number. This naming is dynamic typically by hardware id and we don’t want this to fluctuate when provisioning the blueprint in various VMware environments. Fortunately, there is a way to turn this functionality off and restore the interface back to eth0.
+
+Firstly we need to adjust our bootloader to disable interface naming like this.
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The above command adds a few arguments to the kernel args list (namely `net.ifnames=0` and `biosdevname=0`. It may be useful to view the `/etc/default/grub` file and ensure these settings were indeed applied.
+
+The next step is to adjust the network-scripts in centOS. we need to ensure we have a file called `/etc/sysconfig/network-scripts/ifcfg-eth0`
+
+Below is a script that we run on our packer builds to prepare the machines network configuration files.
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to ensure there is a new ifcfg-eth0 config created to replace the old ens config file. Please do verify this config exists after running. If it does not you will have to be sure to build one on your own.
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json b/corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
new file mode 100644
index 0000000..b74e03a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+  "title": "Settings",
+  "ordinal": 263,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.html",
+  "topic_cluster": {
+    "clustering_title": "Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+        "clustering_title": "Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+        "clustering_title": "Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md b/corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
new file mode 100644
index 0000000..b96c1aa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
@@ -0,0 +1,12 @@
+# Settings
+
+The Administration > Settings section sets global configuration parameters for the VM Essentials appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for VM Essentials itself.
+
+**Subtopics**  
+
+- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
+- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
+- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
+- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json b/corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
new file mode 100644
index 0000000..cbba6b0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+  "title": "Overview",
+  "ordinal": 348,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md b/corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
new file mode 100644
index 0000000..e3542c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
@@ -0,0 +1,3 @@
+# Overview
+
+The ArubaCX network plugin is implemented as a VM Essentials `GenericIntegrationProvider` in Groovy. The plugin handles network and cluster events generated by VM Essentials and modifies the configuration of ArubaCX switches based on the cable connections between the affected servers and switches. VM Essentials integrates directly with ArubaCX to create or delete networks for OVS Port Groups that are added or deleted within a configured Cluster.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json b/corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
new file mode 100644
index 0000000..2a1925d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+  "title": "Consuming Currency Exchange in VM Essentials",
+  "ordinal": 273,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.html",
+  "topic_cluster": {
+    "clustering_title": "Consuming Currency Exchange in VM Essentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+        "clustering_title": "Consuming Currency Exchange in VM Essentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+        "clustering_title": "Consuming Currency Exchange in VM Essentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md b/corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
new file mode 100644
index 0000000..3104ca0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
@@ -0,0 +1,7 @@
+# Consuming Currency Exchange in VM Essentials
+
+Currency exchange data is synced from the integrated provider once every 12 hours. When needed, Morpheus will use this cached data to present currency conversions rather than hitting the API directly each time. This limits the total number of API hits and reduces costs.
+
+Exchanged currency values will be shown under conditions similar to the following scenario:
+
+A user is working in a Subtenant configured for Currency B. The user is attempting to provision an instance with pricing sets that have only been defined in Currency A. Morpheus will convert the pricing data from currency A to Currency B for this user (and all users in this Subtenant) since price conversion has been enabled.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.json b/corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
new file mode 100644
index 0000000..e2bc3ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+  "title": "Backups",
+  "ordinal": 13,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-91D3F799-4C17-4008-B605-FEE370890091.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.md b/corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
new file mode 100644
index 0000000..0290649
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
@@ -0,0 +1,3 @@
+# Backups
+
+Displays the number of successful and unsuccessful backups over the last day, week or month
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json b/corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
new file mode 100644
index 0000000..d7ff028
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+  "title": "Password",
+  "ordinal": 216,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.html",
+  "topic_cluster": {
+    "clustering_title": "Password",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+        "clustering_title": "Password"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+        "clustering_title": "Password"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md b/corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
new file mode 100644
index 0000000..4cbc429
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
@@ -0,0 +1,20 @@
+# Password
+
+A Cypher password generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+Key
+:   Pattern “password/character\_length/key”
+
+    Example: password/10/mypassword
+
+Value
+:   Leave the Value filed blank for a password, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the password will be generated and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generated password.
+
+To delete the password key, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json b/corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
new file mode 100644
index 0000000..0e2053b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+  "title": "Domains",
+  "ordinal": 156,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html",
+  "topic_cluster": {
+    "clustering_title": "Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md b/corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
new file mode 100644
index 0000000..b1c4070
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
@@ -0,0 +1,13 @@
+# Domains
+
+Infrastructure  >  Network  >  Domains
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.html)**
+- **[Adding Domains](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.html)**
+- **[Editing Domain Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html)**
+- **[Editing and Removing Domains](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.html)**
+- **[Setting the default domain on a Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-97951AE9-439B-4779-823D-E118E1CB08D3.html)**
+- **[Setting the default domain on a Network](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-650706CA-915E-4239-9D69-35902E82B60E.html)**
+- **[Selecting a Domain while provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json b/corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
new file mode 100644
index 0000000..af82918
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+  "title": "Hardware Passthrough",
+  "ordinal": 131,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md b/corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
new file mode 100644
index 0000000..2b87475
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
@@ -0,0 +1,13 @@
+# Hardware Passthrough
+
+HPE Morpheus VM Essentials includes hardware passthrough and pooling support for VMs provisioned to HVM Clusters. This support extends to GPU, USB, NVME, and any other PCIe device types. In order to be usable, such devices must be attached to a HVM Host or to multiple HVM Hosts. HPE Morpheus VM Essentials includes controls to detach hardware devices from the underlying OS on the hypervisor host and add them to a pool where they are available for consumption by VMs. GPU hardware can be attached to VMs at provision time through custom Service Plans or on an ad-hoc basis by manually attaching hardware to existing VMs. Other supported hardware types must be passed through to the VM after provisioning.
+
+NOTE
+
+HVM Clusters sync certain data every few minutes (short sync) and other data once nightly (daily sync). New hardware attached to hosts is synced into HPE Morpheus VM Essentials during the nightly sync. To consume newly attached hardware immediately, you can force an additional daily sync at any time from the cluster detail page. Just expand the ACTIONS menu and click "Refresh Daily." Within a short time the additional daily sync will complete and newly attached hardware should be consumable from the UI.
+
+**Subtopics**  
+
+- **[Creating Service Plans for GPU Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html)**
+- **[Viewing and Assigning Hardware Devices](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html)**
+- **[GPU Passthrough Example](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json b/corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
new file mode 100644
index 0000000..66dd9d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+  "title": "Local Storage File Shares",
+  "ordinal": 188,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.html",
+  "topic_cluster": {
+    "clustering_title": "Local Storage File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+        "clustering_title": "Local Storage File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+        "clustering_title": "Local Storage File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md b/corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
new file mode 100644
index 0000000..023f157
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
@@ -0,0 +1,82 @@
+# Local Storage File Shares
+
+## About this task
+
+IMPORTANT
+
+Local Storage refers to local to the VM Essentials Appliance and the path must be owned by morpheus-app. Please be conscious of storage space. High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end VM Essentials Appliances.
+
+NOTE
+
+To change the owner of a file path to be used as a Local Storage File Share, run `chown morpheus-app:morpheus-app /path` on the VM Essentials Appliance.
+
+NOTE
+
+VM Essentials will validate path and ownership of the File Share Path.
+
+To Add a Local Storage File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Local Storage Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   STORAGE PATH
+   :   Enter the File Share path on the local VM Essentials Appliance.
+       :   Example: `/var/opt/morpheus/morpheus-ui/vms/virtual-images`
+
+           IMPORTANT
+
+           High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end VM Essentials Appliances.
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json b/corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
new file mode 100644
index 0000000..f20c4e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+  "title": "Virtual Images / Blueprints",
+  "ordinal": 320,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images / Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+        "clustering_title": "Virtual Images / Blueprints"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+        "clustering_title": "Virtual Images / Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md b/corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
new file mode 100644
index 0000000..42d1439
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
@@ -0,0 +1,7 @@
+# Virtual Images / Blueprints
+
+VM Essentials will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for VM Essentials to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to VM Essentials . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints VM Essentials requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json b/corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
new file mode 100644
index 0000000..e746596
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+  "title": "Create Data Stores",
+  "ordinal": 191,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.html",
+  "topic_cluster": {
+    "clustering_title": "Create Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+        "clustering_title": "Create Data Stores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+        "clustering_title": "Create Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md b/corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
new file mode 100644
index 0000000..45a9712
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
@@ -0,0 +1,13 @@
+# Create Data Stores
+
+To a limited extent, data stores can be created from this view. In order to create a data store, you would need to first have an integrated 3Par server. See the section on storage servers for more information on setting up this integration.
+
+NOTE
+
+For all other data store types, create the needed data store within the target Cloud and VM Essentials will automatically sync in the data store on the next Cloud sync. You can force a Cloud sync from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > RefreshMenu > Short).
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click +ADD
+- Enter a Name, select a VMware Cloud, select a 3Par Volume, and select a Host Group
+- Manage permissions in the Group Access and Tenant Permissions sections, if needed
+- Click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json b/corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
new file mode 100644
index 0000000..b0c1af5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+  "title": "Maintenance Mode",
+  "ordinal": 124,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.html",
+  "topic_cluster": {
+    "clustering_title": "Maintenance Mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+        "clustering_title": "Maintenance Mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+        "clustering_title": "Maintenance Mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md b/corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
new file mode 100644
index 0000000..092405b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
@@ -0,0 +1,3 @@
+# Maintenance Mode
+
+HVM hosts can be easily taken out of service for maintenance when needed. From the host detail page, click ACTIONS and then click “Enter Maintenance.” When entering maintenance mode, the host will be removed from the pool. Live VMs that can be migrated will be moved to new hosts. VMs that are powered off will also be moved when possible. When a live VM cannot be moved (such as if it’s “pinned” to the host), the host will not go into maintenance mode until that situation is cleared. You could manually move a VM to a new host or you could power it down if it’s non-essential. After taking that action, attempt to put the host into maintenance mode once again. VM Essentials UI provides a helpful dialog which shows you which VMs live on the host are to be moved as the host goes into maintenance mode. When maintenance has finished, go back to the ACTIONS menu and select “Leave Maintenance.”
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json b/corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
new file mode 100644
index 0000000..9f65de7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+  "title": "Viewing Alerts ",
+  "ordinal": 371,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing Alerts ",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+        "clustering_title": "Viewing Alerts "
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+        "clustering_title": "Viewing Alerts "
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md b/corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
new file mode 100644
index 0000000..53b9027
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
@@ -0,0 +1,13 @@
+# Viewing Alerts
+
+The Alerts tab displays system alerts with severity levels of Fatal, Critical, or Major.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server.
+3. Select the Alerts tab.
+4. Select the type of alert that you want to view from the Filter by Type drop-down list.
+5. The alerts displayed in the Alerts tab provide the following information:
+   - **Severity**: Displays the severity of the alert. The severity can be Fatal, Critical, or Major. The severity of the alert determines the health status of the system.
+   - **Type**: Displays the type of the alert message.
+   - **Message**: Displays the description of the alert message.
+   - **Time**: Displays the time when the alert was created. The UTC timezone is the standard timezone in HPE Morpheus Enterprise.![Alerts tab](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-46AEA56B-E951-48EC-8781-EEAF84D5ADB7-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json b/corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
new file mode 100644
index 0000000..0f93000
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+  "title": "Setting the default domain on a Cloud",
+  "ordinal": 162,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-97951AE9-439B-4779-823D-E118E1CB08D3.html",
+  "topic_cluster": {
+    "clustering_title": "Setting the default domain on a Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+        "clustering_title": "Setting the default domain on a Cloud"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+        "clustering_title": "Setting the default domain on a Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md b/corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
new file mode 100644
index 0000000..8125d16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
@@ -0,0 +1,9 @@
+# Setting the default domain on a Cloud
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Clouds.
+2. Edit the target Cloud.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json b/corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
new file mode 100644
index 0000000..8e3f43f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+  "title": "Provisioning the Cluster",
+  "ordinal": 107,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9886AD4A-5C64-4E09-A106-B14419362757.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+        "clustering_title": "Provisioning the Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+        "clustering_title": "Provisioning the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md b/corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
new file mode 100644
index 0000000..3b9a14e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
@@ -0,0 +1,21 @@
+# Provisioning the Cluster
+
+As mentioned in the previous section, HVM hosts should be running Ubuntu 24.04 to use the latest HVM cluster layout (version 1.2+). HVM hosts running Ubuntu 22.04 can also be used (select HVM cluster layout 1.1). I also have a Private Cloud-type Cloud to house the cluster. Begin the cluster creation process from the Clusters list page (Infrastructure > Clusters). Click + ADD CLUSTER and select “HVM”.
+
+VM Essentials gives the option to select a hyperconverged infrastructure (HCI) **LAYOUT** or non-HCI. In this example, the HCI Layout is used (requires a three-node minimum). Next, configure the names and IP addresses for the host boxes (**SSH HOST**). The SSH HOST name configuration is simply a display name in VM Essentials, it does not need to be a hostname. By default, configuration space is given for three hosts which is what this example cluster will have. You must at least configure one and it’s possible to add more by clicking the (+) button. The **SSH PORT** is pre-configured for port 22, change this value if applicable in your environment. Next, set a pre-existing user on the host boxes (**SSH USERNAME** and **SSH PASSWORD**) and **SSH KEY**. Use a regular user with sudo access.
+
+In the next part of the modal, you’ll configure the storage devices and network interfaces. Find your disk name, if needed, with the `lsblk` command. In my case, the target device is located at `/dev/sdb`.
+
+Though not strictly required, it’s recommended to have separate network interfaces to handle cluster management, storage traffic, and compute. In this example case, `eth0` is configured as the **MANAGEMENT NET INTERFACE** which handles communication between the cluster hosts. `eth1` is configured as the **STORAGE NET INTERFACE** and `eth2` is configured as the **COMPUTE NET INTERFACE**. The **COMPUTE VLANS** field can take a single value (ex. 1) or a range of values (ex. 22-25). This will create OVS port group(s) selectable as networks when provisioning workloads to the cluster. If needed, you can find your network interface names with the `ip a` command.
+
+Next, only one **CPU TYPE** is currently supported (`x86_64`) though this may change in the future. For **CPU MODEL** configuration, we surface the entire database of model configurations from `libvirt`. If unsure or if you don’t know of a specific reason to choose one or the other, select `host-passthrough` which is the default option.
+
+Finally, select a **DYNAMIC PLACEMENT** and **POWER POLICY** configuration. When enabled, Dynamic Placement will automatically balance VMs across cluster hosts based on resource utilization. When disabled, VMs will only migrate to a new host if they are pinned to a specific host or failed over and not running on the preferred host. With Power Policy, set Balanced (default) or Performance configuration. Balanced optimizes for a mix of performance and efficiency. Performance mode is optimized for scenarios requiring maximum performance. It reduces network latency by applying configurations similar to the `tuned` "network-latency" profile and switches CPUs into performance mode.
+
+NOTE
+
+Power Policy settings require Agent version 3.0.0+ running on the HVM Host and take effect following the next sync cycle. You can upgrade HVM Host Agents by navigating to the Host detail page, opening the ACTIONS menu, and selecting Upgrade Agent. Alternatively, you can select Download Agent Script to download a script which can be run on the HVM Host to upgrade its Agent version. Download scripts are specific to the HVM Host so you will need an individual script per HVM Host. Power Policy settings will persist following a HVM Host reboot.
+
+![image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-8FF3A6DF-6A14-4A7D-B4C1-7E6BDB83B44D-high.png)
+
+At this point we’ve kicked off the process for configuring the cluster nodes. Drill into the Cluster detail page and click on the History tab. Here we can monitor the progress of configuring the cluster. HPE Morpheus VM Essentials will run scripts to install KVM, install OVS, and to prepare the cluster. In just a short time, the cluster provisioning should complete and the cluster will be ready to deploy workloads.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json b/corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
new file mode 100644
index 0000000..2f705c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+  "title": "Supported File Share Types",
+  "ordinal": 186,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.html",
+  "topic_cluster": {
+    "clustering_title": "Supported File Share Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+        "clustering_title": "Supported File Share Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+        "clustering_title": "Supported File Share Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md b/corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
new file mode 100644
index 0000000..8d2ef9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
@@ -0,0 +1,5 @@
+# Supported File Share Types
+
+- CIFS (Samba Windows File Sharing)
+- Local Storage
+- NFSv3
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json b/corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
new file mode 100644
index 0000000..b62620a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+  "title": "Generate Key Pair",
+  "ordinal": 202,
+  "parent_title": "Key Pairs",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.html",
+  "topic_cluster": {
+    "clustering_title": "Generate Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+        "clustering_title": "Generate Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+        "clustering_title": "Generate Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md b/corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
new file mode 100644
index 0000000..baa6aa0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
@@ -0,0 +1,17 @@
+# Generate Key Pair
+
+## About this task
+
+To generate a Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Generate Key Pair”
+3. After naming the new key pair, HPE Morpheus VM Essentials will reveal both the public and private key
+
+## Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in HPE Morpheus VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json b/corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
new file mode 100644
index 0000000..86c51a4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+  "title": "Windows Agent",
+  "ordinal": 37,
+  "parent_title": "SSH/Winrm",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9969BD6B-639D-4633-B825-79578464E8E6.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+        "clustering_title": "Windows Agent"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+        "clustering_title": "Windows Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md b/corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
new file mode 100644
index 0000000..79e4ab2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
@@ -0,0 +1,8 @@
+# Windows Agent
+
+- Port 5985 must be open and WinRM enabled for Windows images.
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+NOTE
+
+Administrator user is required for Windows agent install.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json b/corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
new file mode 100644
index 0000000..fa531b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+  "title": "Snapshots",
+  "ordinal": 321,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.html",
+  "topic_cluster": {
+    "clustering_title": "Snapshots",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+        "clustering_title": "Snapshots"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+        "clustering_title": "Snapshots"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md b/corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
new file mode 100644
index 0000000..dbafb29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
@@ -0,0 +1,11 @@
+# Snapshots
+
+VM Essentials allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into VM Essentials every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+VM Essentials supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in VM Essentials for VMs using SR-IOV network adapters.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json b/corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
new file mode 100644
index 0000000..c4d8763
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+  "title": "Enabled Clouds (Types)",
+  "ordinal": 274,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.html",
+  "topic_cluster": {
+    "clustering_title": "Enabled Clouds (Types)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+        "clustering_title": "Enabled Clouds (Types)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+        "clustering_title": "Enabled Clouds (Types)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md b/corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
new file mode 100644
index 0000000..3cc91e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
@@ -0,0 +1,5 @@
+# Enabled Clouds (Types)
+
+Controls which types of Cloud can be created.
+
+- When a Cloud type is disabled, it will be removed from the available options when adding new Clouds in Infrastructure  >  Clouds. Existing Clouds are not affected by changes to this setting.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json b/corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
new file mode 100644
index 0000000..e89a5e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+  "title": "License",
+  "ordinal": 289,
+  "parent_title": "Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html",
+  "topic_cluster": {
+    "clustering_title": "License",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md b/corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
new file mode 100644
index 0000000..3e0518d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
@@ -0,0 +1,7 @@
+# License
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.html)**
+- **[Current License](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.html)**
+- **[Upgrade License Key](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json b/corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
new file mode 100644
index 0000000..0a347b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+  "title": "Cloud-Init",
+  "ordinal": 336,
+  "parent_title": "Creating a CentOS/RHEL 7 Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+        "clustering_title": "Cloud-Init"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+        "clustering_title": "Cloud-Init"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md b/corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
new file mode 100644
index 0000000..68d2374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
@@ -0,0 +1,15 @@
+# Cloud-Init
+
+To get started with a base CentOS image we first install cloud-init. This is a relatively simple process using yum:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+There are two parts to this yum installation. We are first ensuring some core dependencies are installed for automation as well as cloud-init. git for example is installed for use by ansible playbook automation down the line and is therefore optional if not using ansible. The dracut-modules-growroot is responsible for resizing the root partition upon first boot to match the virtual disk size that was potentially adjusted during provisioning.
+
+A great benefit to using cloud-init is credentials don’t have to be locked into the blueprint. It is advisable, within VM Essentials , to configure the default cloud-init user that gets created when the vm boots automatically by cloud-init. This is located in Administration > Settings > Provisioning, within the Cloud-Init Settings section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json b/corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
new file mode 100644
index 0000000..91638f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+  "title": "Adding an NFS Datastore",
+  "ordinal": 128,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an NFS Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+        "clustering_title": "Adding an NFS Datastore"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+        "clustering_title": "Adding an NFS Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md b/corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
new file mode 100644
index 0000000..351b8cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
@@ -0,0 +1,11 @@
+# Adding an NFS Datastore
+
+Existing NFS shares can be used with HVM clusters for virtual machine storage. These are added and viewed from the Storage tab of the cluster detail page and, once added and active, become selectable as targets for virtual machine storage.
+
+NOTE
+
+Ensure NFS is properly configured to allow all of the HVM hosts to access the shared directory, including permissions to read and write. For backup purposes, it’s also helpful to give VM Essentials access to NFS.
+
+Start by navigating to the Storage tab of the cluster detail page. Make sure the Data Stores subtab is also selected. Here you will see a list of existing datastores with some additional information, such as type, capacity, and status. Click ADD. Enter the NAME for the datastore in VM Essentials and select the TYPE as NFS Pool. Note that the datastore name cannot be changed once it has been created. This will update the available fields to include the additional fields needed to integrate the NFS server. Enter the SOURCE HOST which is the hostname or the IP address of the NFS server. Finally, enter the SOURCE DIRECTORY which is the directory path of the NFS share. Click SAVE.
+
+Once the modal is saved, it will take a few minutes to initialize the new datastore and show a successful online status in VM Essentials. Once this initialization process is completed, the datastore can now be used as VM storage for cluster.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json b/corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
new file mode 100644
index 0000000..154a40f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+  "title": "Health",
+  "ordinal": 258,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html",
+  "topic_cluster": {
+    "clustering_title": "Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md b/corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
new file mode 100644
index 0000000..d83bcd4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
@@ -0,0 +1,6 @@
+# Health
+
+**Subtopics**  
+
+- **[VM Essentials Health](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html)**
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json b/corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
new file mode 100644
index 0000000..c3904aa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+  "title": "Networks",
+  "ordinal": 137,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html",
+  "topic_cluster": {
+    "clustering_title": "Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md b/corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
new file mode 100644
index 0000000..251004a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
@@ -0,0 +1,8 @@
+# Networks
+
+Infrastructure  >  Network  >  Networks
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.html)**
+- **[Configuring Networks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json b/corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
new file mode 100644
index 0000000..84b2a4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+  "title": "Create an Instance Backup",
+  "ordinal": 210,
+  "parent_title": "Backups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9DA38943-BF95-446D-AB09-32323160D51B.html",
+  "topic_cluster": {
+    "clustering_title": "Create an Instance Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+        "clustering_title": "Create an Instance Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+        "clustering_title": "Create an Instance Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md b/corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
new file mode 100644
index 0000000..9732aea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
@@ -0,0 +1,53 @@
+# Create an Instance Backup
+
+## About this task
+
+To create Instance backup:
+
+## Procedure
+
+1. Navigate to Backups > Backups
+2. Click + ADD
+3. From the Create Backup Wizard select the radio button for Instance, then click NEXT
+4. Input the following: 
+
+   Instance
+   :   Select an Instance to backup from the typeahead menu
+
+   Name
+   :   Enter a name for the backup job being created
+5. Click NEXT
+6. Depending on the Instance Type selected in the previous step, enter additional details. These can include a specific container, backup type, database name, username and password, or a number of other things depending on the Instance Type
+7. Configure the storage bucket and retention details: 
+
+   Storage
+   :   Select a configured storage bucket as the backup target
+
+   Backup Job Type
+   :   Create a new backup job, add this backup to an existing job, or clone an existing job to handle this backup
+
+   Job Name
+   :   If creating a new job, enter a name for the job
+
+   Retention Count
+   :   If creating a new job, enter the number of backups which should be simultaneously retained
+
+   Schedule
+   :   If creating a new job, select an execution schedule of which to run the backup
+
+   Synthetic Full
+   :   When the backup is targeting an HVM Instance, check this box to schedule synthetic full backups in addition to the normal full and incremental backups
+
+   Synthetic Full Schedule
+   :   If synthetic full backups are enabled, select an execution schedule on which to run the synthetic full backups
+8. Click COMPLETE.
+
+## Results
+
+NOTE
+
+On VMware Cloud types, VM Essentials will merge and consolidate the snapshots held against a VM before exporting the OVF to the storage location or share. This is so VM Essentials has a full and consistent copy of the VM state.
+
+TIP
+
+To edit an existing backup, click on the hyperlinked name of the backup job from the list of backups at Backups > Backups.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json b/corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
new file mode 100644
index 0000000..0794305
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+  "title": "Archives",
+  "ordinal": 224,
+  "parent_title": "Tools",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html",
+  "topic_cluster": {
+    "clustering_title": "Archives",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md b/corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
new file mode 100644
index 0000000..afa9952
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
@@ -0,0 +1,9 @@
+# Archives
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.html)**
+- **[Archives List Page](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.html)**
+- **[Adding an Archive](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.html)**
+- **[Archive Detail Page](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.html)**
+- **[File Detail Page](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json b/corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
new file mode 100644
index 0000000..394bcdc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+  "title": "Editing and Removing Domains",
+  "ordinal": 161,
+  "parent_title": "Domains",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.html",
+  "topic_cluster": {
+    "clustering_title": "Editing and Removing Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+        "clustering_title": "Editing and Removing Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+        "clustering_title": "Editing and Removing Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md b/corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
new file mode 100644
index 0000000..9e62c59
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
@@ -0,0 +1,4 @@
+# Editing and Removing Domains
+
+- Domains can be edited by selecting the Actions dropdown for the Domain and selecting Edit, or by selecting the ✎ icon in list views.
+- Added Domains can be removed from VM Essentials by selecting the Actions dropdown for the Domain and selecting Remove, or the 🗑 icon in list views.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json b/corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
new file mode 100644
index 0000000..b6ad2de
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+  "title": "Migrations Requirements",
+  "ordinal": 232,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md b/corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
new file mode 100644
index 0000000..83e9cea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
@@ -0,0 +1,23 @@
+# Migrations Requirements
+
+This section contains requirements and recommendations that will ensure migrations run successfully. Keep an eye on this section as some requirements will change as this feature is updated over time to become more flexible.
+
+General Requirements
+:   - HVM Hosts must be upgraded to Agent version 2.10.0 at minimum. To upgrade the HVM Host Agent, navigate to the host detail page, open the ACTIONS menu, and select "Upgrade Agent." If this is unsuccessful, you may instead select "Download Agent Script" to download a shell script which may be run manually on the HVM Host. These download scripts are specific to the HVM Host so an individual install script would need to be downloaded for each HVM Host and run on the correct HVM Host.
+    - HVM Hosts must be able to reach ESXi hosts and vCenter on the target VMware vCenter Cloud via the Management Network
+    - The source VMs must be running for the preparation phase of the migration to complete successfully. If VMs are not running, they will automatically be restarted
+
+First Release Requirements
+:   This section includes requirements for the current version of the migration feature which are subject to change and improvement as road-mapped enhancements are included with subsequent versions of the product.
+
+    - If the target datastore is GFS2 or NFS, migrations will be "thin" QCOW2 rather than "thick" to reduce overhead and on-disk footprint. Other target datastore types must have enough "thick" space for each VM
+    - VMs will power down prior to the transfer meaning service of the source workload will be disrupted during the transfer
+    - VirtIO / VirtIO-SCSI target storage must be supported by the source VM
+    - Currently supported operating systems: RedHat, CentOS, Rocky, Alma, SUSE, Ubuntu, Debian, Windows (currently requires manual preparation steps described below)
+    - Source VMs must be capable of getting the `qemu-guest-tools` or `qemu-guest-agent` package installed.
+    - RDM (Raw Device Mappings) are not yet supported
+    - Source VMs must not have any attached ISOs or cdroms. These are not supported and the migration will fail.
+
+Recommendations
+:   - Batch limits and bandwidth limitations testing is still in progress. It's currently recommended you migrate no more than 20 VMs at a time. Testing is still ongoing to determine the upper limits of migrations and this recommendation is likely to increase over time
+    - Begin using this feature with a smaller migration than the limit to make sure your workloads are moving correctly
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json b/corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
new file mode 100644
index 0000000..b57b0c4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+  "title": "Source Options",
+  "ordinal": 61,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.html",
+  "topic_cluster": {
+    "clustering_title": "Source Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+        "clustering_title": "Source Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+        "clustering_title": "Source Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md b/corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
new file mode 100644
index 0000000..ff7c3c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
@@ -0,0 +1,6 @@
+# Source Options
+
+Task configuration code may be entered locally or sourced via URL. Changing the SOURCE type will often update the available fields in the Task modal to accommodate the selected sourcing.
+
+- **Local:** The Task configuration code is written directly in VM Essentials in a large text area. VM Essentials includes syntax highlighting for easier debugging and script writing
+- **URL:** For Task configuration that can be source via an outside URL, specify the address in the URL field
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json b/corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
new file mode 100644
index 0000000..99fdd16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+  "title": "Subnets",
+  "ordinal": 145,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9FC58214-95C7-4690-91DA-3185640E3712.html",
+  "topic_cluster": {
+    "clustering_title": "Subnets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+        "clustering_title": "Subnets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+        "clustering_title": "Subnets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md b/corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
new file mode 100644
index 0000000..5a2a07c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
@@ -0,0 +1,7 @@
+# Subnets
+
+Subnet details can be viewed from the SUBNETS tab on the detail page of a specific network. From the SUBNETS tab, Morpheus allows the user to search and edit existing subnets.
+
+In an Azure VNet, you can also create new subnets with the +ADD button.
+
+![../../_images/create_subnet_421.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-DAD09131-AC63-418D-9EE5-811611F8FB08-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json b/corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
new file mode 100644
index 0000000..0356463
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+  "title": "DHCP",
+  "ordinal": 140,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.html",
+  "topic_cluster": {
+    "clustering_title": "DHCP",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+        "clustering_title": "DHCP"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+        "clustering_title": "DHCP"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md b/corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
new file mode 100644
index 0000000..30a45e6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
@@ -0,0 +1,26 @@
+# DHCP
+
+## About this task
+
+To configure a network for DHCP:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, set the DHCP flag as Active (default)
+5. Save Changes
+
+## Results
+
+IMPORTANT
+
+The DHCP flag tells VM Essentials this network has a DHCP server assigning IP Addresses to hosts. VM Essentials does not act as the DHCP server, and provisioning to a network that has the DHCP server flag active in VM Essentials, but no DHCP server actually on the network will, in most cases, cause the instance to not receive an IP address.
+
+NOTE
+
+When selecting a network with DHCP enabled during provisioning, “DHCP” will populate to the right of the selected network:
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json b/corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
new file mode 100644
index 0000000..86fe83c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+  "title": "Defining Proxies",
+  "ordinal": 167,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.html",
+  "topic_cluster": {
+    "clustering_title": "Defining Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+        "clustering_title": "Defining Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+        "clustering_title": "Defining Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md b/corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
new file mode 100644
index 0000000..1d68520
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
@@ -0,0 +1,3 @@
+# Defining Proxies
+
+Proxies can be used in a few different contexts and optionally scoped to specific networks with which one may be provisioning into or on a cloud integration as a whole. To configure a Proxy for use by the provisioning engines within VM Essentials we must go to Infrastructure  >  Networks  >  Proxies. Here we can create records representing connection information for various proxies. This includes the host ip address, proxy port, and any credentials (if necessary) needed to utilize the proxy. Now that these proxies are defined we can use them in various contexts.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json b/corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
new file mode 100644
index 0000000..2cc0d9b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+  "title": "Adding HPE Aruba CX DSS Network Integration",
+  "ordinal": 359,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE Aruba CX DSS Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+        "clustering_title": "Adding HPE Aruba CX DSS Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+        "clustering_title": "Adding HPE Aruba CX DSS Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md b/corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
new file mode 100644
index 0000000..0af3d2d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
@@ -0,0 +1,35 @@
+# Adding HPE Aruba CX DSS Network Integration
+
+## Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Select + Add > Networking > HPEAruba CX DSS 
+
+   ![../../_images/addIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-61F5952F-CDFE-43E1-8A2B-445824B876A5-high.png)
+3. Enter the following details in the ADD NETWORK INTEGRATION form: 
+
+   NAME
+   :   Name of the integration in VM Essentials
+
+   AFC ADDRESS
+   :   Enter the network address of the AFC
+
+   AFC USERNAME
+   :   Enter the username
+
+   AFC PASSWORD
+   :   Enter the password
+
+   FABRIC NAME
+   :   Enter the fabric name from the AFC
+
+       ![../../_images/2_create_network_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5A349FA9-6B14-494D-B218-9F082BE5E18A-high.png)
+4. Click Add Network Integration
+
+## Results
+
+Upon add, the HPE Aruba CX DSS Network integration will be created.
+
+NOTE
+
+All fields can be edited after saving.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json b/corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
new file mode 100644
index 0000000..e9faa22
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+  "title": "Datastore Types Pros and Cons",
+  "ordinal": 112,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A1E79BA5-CE31-4357-878E-11464E03158C.html",
+  "topic_cluster": {
+    "clustering_title": "Datastore Types Pros and Cons",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+        "clustering_title": "Datastore Types Pros and Cons"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+        "clustering_title": "Datastore Types Pros and Cons"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md b/corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
new file mode 100644
index 0000000..dc0bbc6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
@@ -0,0 +1,6 @@
+# Datastore Types Pros and Cons
+
+| Datastore Type | Directory Pools | NFS Pools | GFS2 Pools |
+| --- | --- | --- | --- |
+| **Pros** | - Simple to set up and easy to configure - No external dependencies - Uses the existing host filesystem | - Simple to set up - Centralized storage enables easy VM migration across hosts | - True shared disk, clustered filesystem - Pacemaker and Corosync provide high availability and fencing (reducing the risk of split brain) - Good for live VM migration and for clustered workloads |
+| **Cons** | - No redundancy - No capability for migration - Creates the potential for filling up the host filesystem and bringing the host down | - NFS server can be a single point of failure unless configured for high availability - Requires additional configuration not needed for Directory Pools - Network latency can cause performance issues | - More complex to configure and maintain - Requires reliable shared storage (SAN, iSCSI, etc) - Troubleshooting can be more complex |
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json b/corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
new file mode 100644
index 0000000..f30d011
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+  "title": "SELinux Settings",
+  "ordinal": 340,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A2A63203-21AB-4358-8706-62DF795EAE62.html",
+  "topic_cluster": {
+    "clustering_title": "SELinux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+        "clustering_title": "SELinux Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+        "clustering_title": "SELinux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md b/corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
new file mode 100644
index 0000000..9e0748e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
@@ -0,0 +1,10 @@
+# SELinux Settings
+
+## About this task
+
+If allowed by your internal IT policies, set SELinux to permissive to avoid potential issues with cloud-init down the road.
+
+## Procedure
+
+1. Edit the following: `vi /etc/selinux/config`
+2. Make the following change: `setenforce 0`
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json b/corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
new file mode 100644
index 0000000..1e7c5f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+  "title": "Terraform Settings",
+  "ordinal": 282,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+        "clustering_title": "Terraform Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+        "clustering_title": "Terraform Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md b/corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
new file mode 100644
index 0000000..b8083c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
@@ -0,0 +1,3 @@
+# Terraform Settings
+
+- **Terraform Runtime:** Select “auto” or “manual”. When selecting “auto”, VM Essentials will automatically download and use the Terraform version indicated in the VERSION field on the Spec Templates that make up a Terraform Instance type or Blueprint. When selecting “manual”, VM Essentials will use the version of Terraform [installed on your appliance](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html?#terraform-installation).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json b/corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
new file mode 100644
index 0000000..1b91c70
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+  "title": "Overview",
+  "ordinal": 71,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md b/corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
new file mode 100644
index 0000000..50ef90f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
@@ -0,0 +1,11 @@
+# Overview
+
+The Virtual Image section displays a list of all images, local and synced, that are available to deploy. VM Essentials includes a rich catalog of pre-configured default images for HVM clusters or for VMware vCenter Cloud targets as well. User Images are automatically synced from Cloud Integrations and added to the Virtual Images section. Images can also be uploaded directly into VM Essentials via local file or url. Understanding the process of prepping images for consumption in VM Essentials is a very important step toward building an effective VM Essentials environment.
+
+IMPORTANT
+
+Invalid Image Settings cause provisioning failures. VM Essentials syncs in as much metadata as possible for synced images, but additional configuration may be needed to ensure successful provisioning.
+
+WARNING
+
+Cloud-init is enabled by default for all Linux images. If your Linux image does not have Cloud-init installed, Cloud-init Enabled must be unchecked before provisioning the image or it will fail immediately.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json b/corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
new file mode 100644
index 0000000..868cffc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+  "title": "Current License",
+  "ordinal": 291,
+  "parent_title": "License",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.html",
+  "topic_cluster": {
+    "clustering_title": "Current License",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+        "clustering_title": "Current License"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+        "clustering_title": "Current License"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md b/corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
new file mode 100644
index 0000000..1e2f58e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
@@ -0,0 +1,9 @@
+# Current License
+
+If a License Key has already been applied, it will be shown in the list of Current Licenses. This page also contains useful information on license usage including start and end dates for the license, the total number of HVM sockets licensed, and how many of the licensed HVM sockets have been used.
+
+NOTE
+
+Once a current License expires or has reached its limits, users will no longer be able to provision new Instances or Clusters and will not be able to convert existing VMs to managed. HPE Morpheus VM Essentials will otherwise continue to function.
+
+![The license settings page](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-DEE9EE99-95C7-48D3-9CA5-26BD14693D4D-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json b/corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
new file mode 100644
index 0000000..4b4571d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+  "title": "Archives List Page",
+  "ordinal": 226,
+  "parent_title": "Archives",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.html",
+  "topic_cluster": {
+    "clustering_title": "Archives List Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+        "clustering_title": "Archives List Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+        "clustering_title": "Archives List Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md b/corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
new file mode 100644
index 0000000..84be63d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
@@ -0,0 +1,12 @@
+# Archives List Page
+
+To view or create Archives, navigate to Tools > Archives. At the Archives list page is a list of all currently-configured Archives. From the list view, the following details about each Archive are shown:
+
+- **NAME:** The name for the Archive in VM Essentials
+- **BUCKET:** The integrated bucket or file share where files in this Archive are stored
+- **# Files:** The number of files in the Archive
+- **SIZE:** The total size of all files in the Archive
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants listed here have access to the Archive
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **PUBLIC URL:** Indicates whether VM Essentials is automatically generating a public download URL for files in this Archive
+- **ACTIONS:** Within the ACTIONS menu users may download a ZIP folder containing all files in the Archive, edit the Archive, or remove it
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json b/corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
new file mode 100644
index 0000000..8214425
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+  "title": "Windows Settings",
+  "ordinal": 278,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md b/corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
new file mode 100644
index 0000000..b496e32
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
@@ -0,0 +1,3 @@
+# Windows Settings
+
+- **Administrator Password:** Enter password to be set for the Windows Administrator User during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json b/corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
new file mode 100644
index 0000000..ba7a3d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+  "title": "Running Automation Against Label Targets",
+  "ordinal": 54,
+  "parent_title": "Labels",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.html",
+  "topic_cluster": {
+    "clustering_title": "Running Automation Against Label Targets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+        "clustering_title": "Running Automation Against Label Targets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+        "clustering_title": "Running Automation Against Label Targets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md b/corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
new file mode 100644
index 0000000..31e5119
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
@@ -0,0 +1,7 @@
+# Running Automation Against Label Targets
+
+Tasks can be run against Instance Labels or Server Labels. When executing the Task, select either Server Label or Instance Label. After specifying the Label, the automation will be run against all Instances or Servers which have the indicated Label. Currently, only one Label may be selected and users cannot enter multiple Labels in the field. If a non-existent Label is entered, the automation simply will not run against any Workloads since the Label does not match any.
+
+NOTE
+
+Instance and server Labels are separate. Even if some Instances or servers have the same Label, the automation is only run against the selected construct (Instance Labels or Server Labels).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.json b/corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
new file mode 100644
index 0000000..7d8efde
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+  "title": "Default Storage",
+  "ordinal": 175,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A745B955-2E59-4769-AB47-E32098A84653.html",
+  "topic_cluster": {
+    "clustering_title": "Default Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+        "clustering_title": "Default Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+        "clustering_title": "Default Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.md b/corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
new file mode 100644
index 0000000..f5d3e93
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
@@ -0,0 +1,7 @@
+# Default Storage
+
+The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is `var/opt/morpheus/morpheus-ui/`. It is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure > Storage section to avoid running out of disk space on the VM Essentials Appliance.
+
+**Subtopics**  
+
+- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json b/corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
new file mode 100644
index 0000000..e1c49f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+  "title": "To edit and configure an existing Virtual Image:",
+  "ordinal": 75,
+  "parent_title": "User Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.html",
+  "topic_cluster": {
+    "clustering_title": "To edit and configure an existing Virtual Image:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+        "clustering_title": "To edit and configure an existing Virtual Image:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+        "clustering_title": "To edit and configure an existing Virtual Image:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md b/corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
new file mode 100644
index 0000000..dde7c74
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
@@ -0,0 +1,69 @@
+# To edit and configure an existing Virtual Image:
+
+## Procedure
+
+1. Select the pencil icon at the right of any row on the Virtual Images list page, or click EDIT on a Virtual Image detail page.
+2. Configure the following on the Image: 
+
+   Name
+   :   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant VM Essentials environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, VM Essentials will install the FIPS-compliant VM Essentials Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to VMware vCenter Clouds. Enable if the Windows Image has been sysprepped. If enabled, VM Essentials will inject `unattend.xml`
+3. Click Save Changes 
+
+   NOTE
+
+   Cloud-Init is enabled by default on all images. Images without Cloud-Init or Cloudbase-Init installed must have the `cloud-init` flag disabled on the Virtual Image setting or Provisioning may fail.
+
+   IMPORTANT
+
+   VM Essentials does not validate or restrict image uploads to certain file types and any type of file may be uploaded as a Virtual Image. For security purposes, these files are stored in a non-executable state so users need not worry about potentially dangerous file types being uploaded (ex. executables).
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.json b/corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.json
new file mode 100644
index 0000000..c7d0b35
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+  "title": "Administration",
+  "ordinal": 235,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AAD13737-533B-491F-A155-DDB027057157.html",
+  "topic_cluster": {
+    "clustering_title": "Administration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+        "clustering_title": "Administration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+        "clustering_title": "Administration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.md b/corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.md
new file mode 100644
index 0000000..4922d33
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AAD13737-533B-491F-A155-DDB027057157.md
@@ -0,0 +1,14 @@
+# Administration
+
+There are several administrative integrations built into VM Essentials that make it great to work with within any organization ranging from small to large. Especially, with its built in white label support and multitenancy capabilities, managed service providers have a wide range of capabilities when it comes to managing customer accounts and users.
+
+**Subtopics**  
+
+- **[Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html)**
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.html)**
+- **[Health](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html)**
+- **[Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json b/corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
new file mode 100644
index 0000000..0aab1ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+  "title": "Host Features",
+  "ordinal": 102,
+  "parent_title": "Features",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_deployment_guide",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md b/corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
new file mode 100644
index 0000000..e6d043d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
@@ -0,0 +1,19 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and datastores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Governance through VM Essentials RBAC
+- Pass host-attached NVME, USB, and GPU hardware through to VMs running on the host
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json b/corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
new file mode 100644
index 0000000..3beb9d7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+  "title": "Routers",
+  "ordinal": 148,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html",
+  "topic_cluster": {
+    "clustering_title": "Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md b/corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
new file mode 100644
index 0000000..5b59a53
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
@@ -0,0 +1,8 @@
+# Routers
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7138E486-AE62-4778-9358-F098126785A5.html)**
+- **[Create New Router](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-61053EC5-4910-454F-8B71-6B06408A6451.html)**
+- **[Editing Existing Routers](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.html)**
+- **[Deleting Existing Routers](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json b/corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
new file mode 100644
index 0000000..d10a851
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+  "title": "VM Features",
+  "ordinal": 103,
+  "parent_title": "Features",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_deployment_guide",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md b/corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
new file mode 100644
index 0000000..558534e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Console support for running workloads
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore VM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- VM Essentials library and automation support
+- Claim and consume host-attached NVME, USB, and GPU hardware to run hardware-accelerated workloads on VMs
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json b/corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
new file mode 100644
index 0000000..a020f24
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+  "title": "Integrating With a Currency Exchange Provider",
+  "ordinal": 272,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AC461BBD-647D-447D-9307-218A41CE368B.html",
+  "topic_cluster": {
+    "clustering_title": "Integrating With a Currency Exchange Provider",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+        "clustering_title": "Integrating With a Currency Exchange Provider"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+        "clustering_title": "Integrating With a Currency Exchange Provider"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md b/corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
new file mode 100644
index 0000000..b1d8f00
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
@@ -0,0 +1,11 @@
+# Integrating With a Currency Exchange Provider
+
+## Procedure
+
+1. Navigate to Administration > Settings > Appliance
+2. Under the Currency Settings heading, make a “Currency Provider” selection
+3. Enter your “Provider API Key”
+
+## Results
+
+The service is now integrated and can be used as described in the next section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json b/corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
new file mode 100644
index 0000000..cf12a5d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+  "title": "Notes",
+  "ordinal": 50,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.html",
+  "topic_cluster": {
+    "clustering_title": "Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+        "clustering_title": "Notes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+        "clustering_title": "Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md b/corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
new file mode 100644
index 0000000..a7a418e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
@@ -0,0 +1,7 @@
+# Notes
+
+Every Instance has a Wiki section for adding useful information about the Instance. Wiki can be added by selecting the Wiki tab on the bottom of the Instance Detail page. Instances with associated VMware VMs will bi-directionally sync VM Essentials Wiki content and VMware VM Notes. See the [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CD00669C-741C-480C-B444-67F079061438.html) Section for more details.
+
+TIP
+
+Markdown Syntax is supported in Wikis.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json b/corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
new file mode 100644
index 0000000..ac4a943
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+  "title": "Alibaba Buckets",
+  "ordinal": 178,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.html",
+  "topic_cluster": {
+    "clustering_title": "Alibaba Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+        "clustering_title": "Alibaba Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+        "clustering_title": "Alibaba Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md b/corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
new file mode 100644
index 0000000..3ee20c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
@@ -0,0 +1,77 @@
+# Alibaba Buckets
+
+## About this task
+
+To Add an Alibaba Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Alibaba from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   ACCESS KEY
+   :   Alibaba Access Key
+
+   SECRET KEY
+   :   Alibaba Secret Key
+
+   REGION
+   :   Enter Alibaba Region for the Bucket
+
+   BUCKET NAME
+   :   Enter existing Alibaba Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   Create Bucket
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json b/corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
new file mode 100644
index 0000000..1a64484
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+  "title": "Integration Guides",
+  "ordinal": 312,
+  "parent_title": "Guides",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html",
+  "topic_cluster": {
+    "clustering_title": "Integration Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md b/corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
new file mode 100644
index 0000000..3732346
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
@@ -0,0 +1,7 @@
+# Integration Guides
+
+**Subtopics**  
+
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA_2.html)**
+- **[Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json b/corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
new file mode 100644
index 0000000..5cf2be4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+  "title": "Utilizing Existing QCOW & ISO Images from an NFS File Share",
+  "ordinal": 129,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.html",
+  "topic_cluster": {
+    "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+        "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+        "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md b/corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
new file mode 100644
index 0000000..6f02037
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
@@ -0,0 +1,38 @@
+# Utilizing Existing QCOW & ISO Images from an NFS File Share
+
+Integrated NFS shares can be used both as a repository for HVM cluster images and as a target for saving new images from existing VMs. This offers benefits of greatly expanding the available storage compared to what’s available on the VM Essentials manager VM, insulates you from issues that can arise from images completely filling the manager storage, and allows for the same images to be easily integrated with multiple VM Essentials appliances.
+
+To begin, we need the NFS file share integrated with VM Essentials. This is done in the Infrastructure > Storage section of the UI. This guide assumes the NFS file share is pre-existing and the VM Essentials manager can reach it. Actually setting up an NFS file share goes beyond the scope of this guide. From the File Shares tab, check to see the desired file share is already integrated. If needed, you can add one by clicking + ADD and then selecting “NFSv3”.
+
+When adding a new file share, configure the following:
+
+- **NAME:** A friendly name for the file share within VM Essentials
+- **HOST:** The IP address or hostname for the NFS file share server
+- **EXPORT FOLDER:** The path to the folder that should be mounted to the manager
+- **ACTIVE:** Must be checked to be able to consume this file share elsewhere in VM Essentials manager UI
+- **DEFAULT VIRTUAL IMAGE STORE:** (Optional) Select if you wish this file share to be the default store for newly uploaded or generated images
+
+When done, click Save changes.
+
+![../../_images/editFileshare.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-CD1D4AB9-1183-4739-8E61-1FB428D244B9-high.png)
+
+IMPORTANT
+
+You must configure the NFS share to give VM Essentials manager read and write access if you want to be able to read images from and write images to the file share. Configuring NFS file shares goes beyond the scope of this guide. Deleting files from an integrated file share deletes the actual file and not just the representation of the file in VM Essentials. This includes Virtual Images. Deleting a Virtual Image that is backed by a QCOW or an ISO image files stored in an integrated file share will also cause the file itself to be deleted in addition to the Virtual Image object within VM Essentials.
+
+With the file share integrated, we can now create Virtual Images which are backed by QCOW or ISO images that are pre-existing in the file share. Navigate to Library > Virtual Images and click + ADD. From the dropdown, select “QCOW2” or "ISO". Make the configurations specified below. Those not mentioned can often be left on the default value. For a deeper explanation of configurations not mentioned here, see the dedicated section of VM Essentials documentation on Virtual Images.
+
+- **NAME:** A friendly name for the image in VM Essentials
+- **OPERATING SYSTEM:** Specify the operating system of the image
+- **MINIMUM MEMORY:** Enter a minimum memory value and VM Essentials will not allow the image to be provisioned using a plan with lower memory
+- **BUCKET:** Select the NFS share integrated in the previous step
+- **CREATE IMAGE ID:** Set to “URL/PATH”
+- **URL:** Enter the path to a QCOW or an ISO image within the file share. See the next paragraph for a deeper explanation of how to enter the path properly
+
+The entered path to the QCOW or an ISO image should not include the name of the NFS share or the name of the file itself. See the portion highlighted in the screenshot:
+
+![../../_images/viewQcow.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5EB8987F-1490-43A7-84A4-875FBCE66FEB-high.png)
+
+It also should only be the path to the folder containing the QCOW or an ISO image. The file name itself should not be part of the path. For example, `templates/qcow/ubuntu/server/2204/011025`. Click Save changes.
+
+With the NFS file share integrated and the Virtual Image created, the image is now usable from the provisioning wizard. This guide won’t fully cover the use of the provisioning wizard but from the Configure tab of the wizard, the image is now selectable (assuming you’ve selected a compatible provisioning target). Additionally, we can now click into the detail page for running Instances and save them to images backed by the NFS file share. From the Instance detail page, click Actions, then “Import as Image.” You’ll be able to set a name for the new image and specify the NFS file share as the target bucket.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json b/corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
new file mode 100644
index 0000000..0a02dd9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+  "title": "Logs",
+  "ordinal": 262,
+  "parent_title": "Health",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.html",
+  "topic_cluster": {
+    "clustering_title": "Logs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+        "clustering_title": "Logs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+        "clustering_title": "Logs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md b/corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
new file mode 100644
index 0000000..419633f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
@@ -0,0 +1,3 @@
+# Logs
+
+The VM Essentials logs tab aggregates appliance-specific logs into one list. If needed, users can export the logs by clicking EXPORT. This action triggers a download containing the last 10,000 log entries as a `.log` file.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json b/corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
new file mode 100644
index 0000000..9267202
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+  "title": "Maintaining GFS2 Consistency and High Availability",
+  "ordinal": 120,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B3241978-4E00-4630-A8AB-E597193E51E2.html",
+  "topic_cluster": {
+    "clustering_title": "Maintaining GFS2 Consistency and High Availability",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+        "clustering_title": "Maintaining GFS2 Consistency and High Availability"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+        "clustering_title": "Maintaining GFS2 Consistency and High Availability"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md b/corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
new file mode 100644
index 0000000..23faa0c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
@@ -0,0 +1,38 @@
+# Maintaining GFS2 Consistency and High Availability
+
+HVM Clusters utilize several open-source technologies to maintain consistency and high availability when GFS2 external storage is utilized. This section lists those technologies and a high level overview of how they work together to prevent data corruption and facilitate smooth failover when a cluster host is lost.
+
+Corosync
+
+- Open-source cluster engine providing a high-performance messaging layer
+- Ensures node communication and consistent cluster state in high availability systems
+- Tracks active nodes and prevents split-brain scenarios
+- Provides are reliable messaging backbone for syncronizing state and data
+- Handles node failures and reconfigures the cluster automatically
+- Works with Pacemaker as part of a full HA stack providing automatic failover
+- Distributes lock information, detects failures, and triggers fencing
+
+Pacemaker
+
+- Open-source HA resource manager
+- Ensures services and resources run on correct nodes, even during failures
+- Works with Corosync for messaging and membership
+- Handles resource management, such as IP addresses, filesystems, and services
+- Depects failures and facilitates automatic failover and restart
+- Manages GFS2 mounts, distributed lock management, and fencing agents (split-brain prevention)
+- Relocates VMs and services automatically on node failure
+
+Distributed Lock Manager (DLM)
+
+- Ensures data integrity in GFS2 clusters by managing file and metadata locks
+- Allows just one node to modify a resource at a time, preventing data corruption
+- Shares lock info across the cluster
+- Utilizes Corosync messaging to synchnonize lock states
+- On node failure, fencing releases locks safety before recovery
+
+Fencing
+
+- Ensures data integrity if a node fails
+- Isolates failed nodes from shared storage to prevent data corruption
+- Uses STONITH fencing method to completely disable nodes considered to be down to ensure they cannot access shared storage
+- Releases locks only when unresponsive nodes are safely fenced
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json b/corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
new file mode 100644
index 0000000..6b3b81e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+  "title": "Users",
+  "ordinal": 250,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html",
+  "topic_cluster": {
+    "clustering_title": "Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md b/corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
new file mode 100644
index 0000000..7c2f80a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
@@ -0,0 +1,5 @@
+# Users
+
+**Subtopics**  
+
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123_2.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json b/corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
new file mode 100644
index 0000000..6a4142f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+  "title": "User Photo",
+  "ordinal": 295,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html",
+  "topic_cluster": {
+    "clustering_title": "User Photo",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md b/corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
new file mode 100644
index 0000000..36ec146
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
@@ -0,0 +1,3 @@
+# User Photo
+
+Upload a custom image for your user avatar that is displayed in the top header and user administration sections. **Suggested Photo Dimensions: 128 x 128**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json b/corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
new file mode 100644
index 0000000..a07dc3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+  "title": "Network Interfaces",
+  "ordinal": 341,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.html",
+  "topic_cluster": {
+    "clustering_title": "Network Interfaces",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+        "clustering_title": "Network Interfaces"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+        "clustering_title": "Network Interfaces"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md b/corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
new file mode 100644
index 0000000..de88cb2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
@@ -0,0 +1,18 @@
+# Network Interfaces
+
+## About this task
+
+Run the following to rename the network NIC. Values inside angle brackets should be filled in with the appropriate value for your environment (ex. <varname>):
+
+## Procedure
+
+1. `sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub`
+2. `grub2-mkconfig -o /boot/grub2/grub.cfg` (location may be different, could be located at /boot/efi/EFI/centos/grub.cfg)
+3. `ifdown <orginal-nic>`
+4. `mv /etc/sysconfig/network-scripts/<orginal-nic> /etc/sysconfig/network-scripts/ifcfg-eth0` (this changes name/device to eth0)
+5. Edit `ifcfg-eth0` and change the NAME to `eth0`
+6. `bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'`
+7. `ip link set <orginal-nic> down`
+8. `ip link set <orginal-nic> name eth0`
+9. `ip link set eth0 up`
+10. `ifup eth0`
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json b/corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
new file mode 100644
index 0000000..3a78d58
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+  "title": "Execute Options",
+  "ordinal": 60,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+        "clustering_title": "Execute Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+        "clustering_title": "Execute Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md b/corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
new file mode 100644
index 0000000..b176cdb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
@@ -0,0 +1,7 @@
+# Execute Options
+
+- **Continue on Error:** When marked, automation stacks including this Task can continue when this Task fails. Additionally, Instances provisioned with this Task as part of its automation stack can be considered provisioned successfully even if this Task has failed
+- **Retryable:** When marked, this Task can be configured to be retried in the event of failure
+- **Retry Count:** The maximum number of times the Task will be retried when there is a failure
+- **Retry Delay:** The length of time (in seconds) VM Essentials will wait to retry the Task
+- **Allow Custom Config:** When marked, a text area is provided at Task execution time to allow the user to pass extra variables or specify extra configuration. See the next section for an example.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json b/corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
new file mode 100644
index 0000000..c310343
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+  "title": "Getting Started",
+  "ordinal": 2,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md b/corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
new file mode 100644
index 0000000..3a4036f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
@@ -0,0 +1,14 @@
+# Getting Started
+
+HPE Morpheus VM Essentials Software is a unified solution allowing for easy deployment of KVM-based HVM workloads and intuitive integration of existing VMware vCenter Clouds, all with administration made easy through the HPE Morpheus VM Essentials Manager. Once deployed, take advantage of powerful features including live migration of VMs across HVM Cluster hosts with zero downtime, dynamically distribute workloads based on load, automatic failover of workloads following the loss of a host, and a lot more. Provisioning new workloads is also made easy with the VM Essentials image library, automation tools, and powerful provisioning wizard. In addition to HVM clusters, VM Essentials also includes a deep integration into VMware vCenter, which also takes advantage of the same powerful provisioning wizard, automation engine, and monitoring capabilities.
+
+This documentation covers the system requirements for HVM clusters and a setup guide for installing VM Essentials manager. It also includes example use cases for effective implementation of the feature set and in-depth sections for each area of the UI detailing the capabilities of each tool.
+
+Before getting started, it’s important to note that administrators have the responsibility to install and configure servers and network equipment in a way that will ensure successful operation of VM Essentials. This includes selecting host servers, storage hardware, and networking hardware that have been certified as compatible with the platform. The VM Essentials section of the [HPE Support Center](https://www.hpe.com/support/VME-Docs) contains a reference architecture document which includes a validated design with specific hardware SKUs. The same section of the HPE Support Center also includes a qualification matrix which lists hardware that has been certified compatible.
+
+Additionally, administrators will be required to perform some setup functions on their own, such as preinstalling Ubuntu 24.04 (or 22.04 though you won’t be able to utilize the latest cluster layouts) on host servers, configuring networking for each host, configuring access to external storage at the OS level, and establishing a network topology that ensures acceptable performance. Subsequent sections of this document will outline some effective network designs and some tips for selecting a network design based on available hardware. It will be the responsibility of the administrator to select a network design based on available hardware and to use the Linux command line to establish appropriate network bonds, storage configuration, and access across the cluster.
+
+**Subtopics**  
+
+- **[Deployment Guide](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.html)**
+- **[Elevating to HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json b/corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
new file mode 100644
index 0000000..c29aa34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+  "title": "Moving Workloads Between Hosts",
+  "ordinal": 122,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.html",
+  "topic_cluster": {
+    "clustering_title": "Moving Workloads Between Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md b/corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
new file mode 100644
index 0000000..13627fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
@@ -0,0 +1,9 @@
+# Moving Workloads Between Hosts
+
+To manually move workloads between hosts, drill into the detail page for the VM (from the VMs tab of the cluster detail page). Click ACTIONS and select “Manage Placement”. Choose a different host and select from the following placement strategies:
+
+- **Auto:** Manages VM placement based on load
+- **Failover:** Moves VMs only when failover is necessary
+- **Pinned:** Will not move this workload from the selected host
+
+Within a short time, the workload is moved to the new host.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json b/corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
new file mode 100644
index 0000000..1efea15
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+  "title": "Managing Instances",
+  "ordinal": 47,
+  "parent_title": "Instances",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+        "clustering_title": "Managing Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+        "clustering_title": "Managing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md b/corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
new file mode 100644
index 0000000..f876101
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
@@ -0,0 +1,23 @@
+# Managing Instances
+
+Instance actions allow you to perform numerous management tasks on instances. The actions available depend on the instance type, hypervisor, roles permissions, and instance state. Actions can be accessed from the Instances list page or from an Instance detail page.
+
+Edit
+:   Edit the Name, Description, Environment, Group, Tags, and Owner for the Instance.
+
+Delete
+:   Deletes the Instance.
+
+IMPORTANT
+
+Deleting an Instance will delete the actual underlying VMs or Containers and cannot be undone.
+
+TIP
+
+You can change the owner of an instance easily by selecting the edit button and entering a new owner in the corresponding field.
+
+**Subtopics**  
+
+- **[Actions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.html)**
+- **[Performing Instance Actions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.html)**
+- **[Notes](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json b/corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
new file mode 100644
index 0000000..0f23533
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+  "title": "Features",
+  "ordinal": 101,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md b/corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
new file mode 100644
index 0000000..767dbf8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
@@ -0,0 +1,6 @@
+# Features
+
+**Subtopics**  
+
+- **[Host Features](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html)**
+- **[VM Features](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json b/corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
new file mode 100644
index 0000000..9d99c70
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+  "title": "Docker",
+  "ordinal": 324,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B82658C8-6002-424B-B257-D52A7D603BC3.html",
+  "topic_cluster": {
+    "clustering_title": "Docker",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+        "clustering_title": "Docker"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+        "clustering_title": "Docker"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md b/corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
new file mode 100644
index 0000000..b506211
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
@@ -0,0 +1,7 @@
+# Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by VM Essentials out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. VM Essentials views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the VM Essentials appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json b/corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
new file mode 100644
index 0000000..edf8e3b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+  "title": "Role Creation",
+  "ordinal": 245,
+  "parent_title": "Overview",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.html",
+  "topic_cluster": {
+    "clustering_title": "Role Creation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+        "clustering_title": "Role Creation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+        "clustering_title": "Role Creation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md b/corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
new file mode 100644
index 0000000..16e3722
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
@@ -0,0 +1,9 @@
+# Role Creation
+
+Roles are created within Administration > Roles. Creating a Role requires minimal information, just a Name for the Role in VM Essentials. You can optionally add a Description and a Landing URL as well. The landing URL determines the starting page for the User on initial login (such as the Instances list page or perhaps the detail page for a primary HVM cluster). Following creation, click into the Role from the Roles list page and you will see the granular controls available to Roles. These controls include access permissions for UI feature sections, Groups, Cluster types, and configured Tasks. Changes are automatically saved for the Role, there is no need to click a button to save any updates. See the next section for a detailed breakdown of individual feature permissions.
+
+Master tenant users are able to create a special type of user role called a multi-tenant user role. A multi-tenant user role is copied / duplicated down to all subtenants within VM Essentials. These can be viewed as canned role templates available to new tenants when their account is first created. Any changes made to the main role are propagated down to the subtenants version of the shared role so long as the subtenant users have not previously adjusted/changed that role. The moment a subtenant makes adjustments to the shared role within their account, it is unlinked from the parent role and treated entirely independently. In order to relink the Role in the Subtenant, a Master Tenant user would have to edit the Role, uncheck MULTITENANT USER ROLE, save the Role, check MULTITENANT USER ROLE once again, then save the Role once again.
+
+Another note about user roles is that when a user role is copied down to a subtenant, the permission scopes cannot supersede the tenant’s assigned tenant role. If they do they are automatically downgraded when propagated to the specific tenant. Any changes made to the tenant role will automatically ensure roles within the tenant are downgraded appropriately.
+
+Master Tenant administrators may edit permissions for Roles in other Tenants by viewing the Tenant detail page (Administration > Tenants > Selected Tenant) and accessing the Roles tab. From there, select the Role to edit and make changes on the resulting Role detail page.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json b/corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
new file mode 100644
index 0000000..787679d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+  "title": "Creating a CentOS/RHEL 8 Image",
+  "ordinal": 338,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a CentOS/RHEL 8 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+        "clustering_title": "Creating a CentOS/RHEL 8 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+        "clustering_title": "Creating a CentOS/RHEL 8 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md b/corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
new file mode 100644
index 0000000..50c1625
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
@@ -0,0 +1,10 @@
+# Creating a CentOS/RHEL 8 Image
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux build. You must be running ESXi 6.7 Update 2 or later.
+
+**Subtopics**  
+
+- **[Prepare The New CentOS 8/RHEL8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.html)**
+- **[SELinux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A2A63203-21AB-4358-8706-62DF795EAE62.html)**
+- **[Network Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.html)**
+- **[Final VMWare Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json b/corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
new file mode 100644
index 0000000..3995cf3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+  "title": "VMware tools (vmtools) RPC mode",
+  "ordinal": 38,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.html",
+  "topic_cluster": {
+    "clustering_title": "VMware tools (vmtools) RPC mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+        "clustering_title": "VMware tools (vmtools) RPC mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+        "clustering_title": "VMware tools (vmtools) RPC mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md b/corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
new file mode 100644
index 0000000..d5332c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
@@ -0,0 +1,4 @@
+# VMware tools (vmtools) RPC mode
+
+- VMware tools is installed on the template(s)
+- Credentials have been entered on the Image if using an uploaded or synced image when Cloud-init or Guest Customizations or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json b/corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
new file mode 100644
index 0000000..989611b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+  "title": "Task Management",
+  "ordinal": 65,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html",
+  "topic_cluster": {
+    "clustering_title": "Task Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md b/corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
new file mode 100644
index 0000000..ef0cd34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
@@ -0,0 +1 @@
+# Task Management
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json b/corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
new file mode 100644
index 0000000..4bc0b87
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+  "title": "PXE Boot Settings",
+  "ordinal": 280,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-B94BC2CB-8504-41C6-8848-512529EEE941.html",
+  "topic_cluster": {
+    "clustering_title": "PXE Boot Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+        "clustering_title": "PXE Boot Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+        "clustering_title": "PXE Boot Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md b/corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
new file mode 100644
index 0000000..c3e2cfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
@@ -0,0 +1,4 @@
+# PXE Boot Settings
+
+Default Root Password
+:   Enter the default password to be set for Root during PXE Boots.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json b/corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
new file mode 100644
index 0000000..4a79cf6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+  "title": "Common Options",
+  "ordinal": 58,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html",
+  "topic_cluster": {
+    "clustering_title": "Common Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md b/corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
new file mode 100644
index 0000000..1918c85
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
@@ -0,0 +1,3 @@
+# Common Options
+
+When creating a Task, the required and optional inputs will vary significantly by the Task type. However, there are options which are common to Tasks of all types.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json b/corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
new file mode 100644
index 0000000..83f6211
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+  "title": "Feature Access Permissions",
+  "ordinal": 249,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.html",
+  "topic_cluster": {
+    "clustering_title": "Feature Access Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+        "clustering_title": "Feature Access Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+        "clustering_title": "Feature Access Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md b/corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
new file mode 100644
index 0000000..8151805
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
@@ -0,0 +1,256 @@
+# Feature Access Permissions
+
+Feature Access settings control permissions for sections and objects in VM Essentials. Permission options include:
+
+None
+:   Hidden or inaccessible for user
+
+Read
+:   User can view but cannot edit or create
+
+Full
+:   User has full access
+
+User
+:   User can access Objects they have created or own
+
+Group
+:   User can access Objects assigned to or shared with Groups the User has access to
+
+Remote Console: Provisioned
+:   Remote Console tab will only appear after instance is successfully provisioned.
+
+Remote Console: Auto Login
+:   RDP and SSH only, controls if user is auto-logged in to Remote Console or presented with login prompt.
+
+Role Mappings
+:   Gives User Access to Role Mappings config in `/admin/roles` for configuring Identity Source Role Mappings without providing Access to other Identity Source configuration settings.
+
+## Admin Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Admin: Ansible | None, Full | Allows or disallows the ability to edit existing Ansible integrations | Ansible integrations are shown on the Integrations list page (Administration > Integrations). Users with access may view and edit them here. | This permission is recommended for those responsible for administering VM Essentials, including creating integrations with third‐party technologies, specifically Ansible |  |
+| Admin: Appliance Settings | None, Full | Allows or disallows access to the Appliance and License tabs in Administration > Settings | The Appliance tab in Administration > Settings is where VM Essentials administrators would configure the appliance URL, Tenant and User management, email, proxy, and currency settings. Additionally, defining which Clouds are available for integration within VM Essentials is done on this page. On the License tab information about the current VM Essentials license may be viewed and a new license may be applied when needed. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant. Those responsible for configuring currency, email, and proxy settings for Cloud API access will need this permission. | This permission is recommended to be set to None on the Tenant Role to restrict this access for all Subtenant Users. |
+| Admin: Backup Settings | None, Full | Allows or disallows access to Administration > Settings > Backups. Master Tenant administrators have additional settings for appliance backups and defaults on this page. | The Backup Settings page is where users define the default VM Essentials backup bucket, backup schedule, and retention count. Additionally, if given to a Master Tenant user they will have the ability to enable scheduled backups, create backups, and backup appliance. | This permission is recommended for those responsible for enabling backups and setting default backup buckets within VM Essentials. |  |
+| Admin: Clients | None, Full | Allows or disallows access to the Clients tab in global settings (Administration > Settings) | The Clients settings section is where API clients are created and edited. Default clients may have their validity and refresh periods edited but cannot be deleted. User‐created API clients may be edited or deleted | This permission is recommended for those responsible for administering API access. |  |
+| Admin: Distributed Workers | None, Full | Allows or disallows access to Administration > Integrations > Distributed Workers Tab |  |  |  |
+| Admin: Environment Settings | None, Full | Allows or disallows access to the Environments tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define the visibility of the environment to either private or public. When given to a Subtenant user the environments are only visible to the subtenant (private). | The Environments tab is where named environments such as development or production are created and given a description as well as a code for use within the API. A display order and visibility is also set. | This permission is recommended for those responsible for defining environments that will be available to select at provision time whether they are the Master Tenant or Subtenant users. |  |
+| Admin: Export/Import | None, Full | Allows access to the Export/Import functionality which is part of the Code Repositories section of VM Essentials UI (Provisioning > Code) | Export/Import tools allow users to configure integrated Git repositories as either export or import targets (or both) and execute exports or imports | This permission is recommended for administrators as it allows wholesale export of VM Essentials constructs (Tasks, Library Items, and more) as code into Git repositories as well as import of new items from repositories into the appliance |  |
+| Admin: Guidance Settings | None, Full | Allows or disallows access to the Guidance tab in Administration > Settings | The Guidance tab controls global thresholds for VM Essentials guidance recommendations | This permission is recommended for those responsible for cost and resource management |  |
+| Admin: Health | None, Read | Determines access to the Administration > Health page, including the VM Essentials Health and VM Essentials Logs tabs. | The Health pages provide an overview of VM Essentials health, notifications from integrations, and the current VM Essentials‐ui log. | This permission is recommended for those responsible for administering and troubleshooting VM Essentials. | This permission is recommended to be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Identity Source | None, Role Mappings, Full | Allows or disallows access to create, edit, or delete integrated Identity Sources associated with subtenants. The “Role Mappings” option allows the user to edit role mappings without seeing higher level details about the integration itself (such as server IP addresses and admin usernames). | The Identity Sources page associated with the selected Tenant allows for creating, editing, and removing of identity sources in addition to configuring role mapping between VM Essentials and the identity provider. | Full permission is recommended for those responsible for integrating VM Essentials with Identity Providers. Role Mapping permission is recommended for those responsible for Role Based Access Control (RBAC). | This permission is recommended to be set to None for any subtenant user roles via use of a Tenant Role unless they manage their own RBAC. |
+| Admin: Integrations | None, Read, Full | This allows or disallows full or read access to Administration > Integrations. | The Administration Integrations tab is where many new or existing integration types can be configured. These include Chef, Puppet, Ansible, Ansible Tower, vRealize Orchestrator, Microsoft DNS, PowerDNS, Route 53, Git, GitHub, Docker, Jenkins, ServiceNow, Cherwell, Remedy, and ACI. | This permission is recommended for those responsible for the integration between VM Essentials and integrated technologies. |  |
+| Admin: License Settings | None, Full | Allows or disallows access to the Licenses tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define specific subtenants in which the licenses may be used. | The Licenses tab is where software licenses may be added for tracking in VM Essentials. VM Essentials may then be configured to apply these licenses on provision. Currently, only Windows license types are available. | This permission is recommended for those responsible for managing Windows licenses. |  |
+| Admin: Log Settings | None, Full | Allows or disallows access to the Administration > Settings > Logs. | The Logs page is where logs are enabled. Syslog forwarding rules are also configured here. | This permission is recommended for those responsible for configuring VM Essentials log settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access to Subtenant Users. |
+| Admin: Message of the day | None, Full | Allows or disallows access to create and edit Message of the Day policies in Administration > Policies | The Policies page is where policies are defined. When creating a policy, users can select “Message of the Day” from the TYPE dropdown with this permission set to Full. | This permission is recommended for those responsible for publishing the Message of the Day. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Monitoring Settings | None, Full | Allows or disallows access to Administration > Settings > Monitoring | The monitoring settings page is where VM Essentials monitoring and monitoring integrations are configured. Monitoring checks can be turned on or off, and availability time frame, check interval period, and reported availability precision are also configured on this page. | This permission is recommended for those responsible for configuring VM Essentials monitoring settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Packages | None, Full | Allows or disallows access to the Packages tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom library packages (mpg) are added. | This permission is recommended for those responsible for managing the Library. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Plugins | None, Full | Allows or disallows access to the Plugins tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom plugins are added to extend VM Essentials functionality. | This permission is recommended for those responsible for extending VM Essentials functionality through custom plugins. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Policies | None, Read, Full | This setting determines the level of access to Administration > Policies. When given to a Master Tenant user the ability to define Global policies and associate them with one or many Subtenants is granted. When given to a Subtenant user, a global policy applies only to their subtenant. | The Policies page is where policies are defined. On create, the type of policy is selected, a name, description, and scope are defined. | This permission is recommended for those responsible for configuring and managing policies either at the Master Tenant or Subtenant. |  |
+| Admin: Profiles | none,read,full | Allows or disallows access to Profiles (Clouds) | Profiles are where Terraform, Key/Value profiles are created and managed. | This permission is recommended for those responsible for managing secrets and other metadata that needs to be accessed by provisioning and automation processes. |  |
+| Admin: Provisioning Settings | None, Full | Allows or disallows access to the Settings tab of the Administration > Settings > Provisioning page. | The Settings tab is where global provisioning settings are configured. For Master Tenant users, these include allowing Cloud selection, allowing host selection, requiring environment selection, showing pricing, hiding datastore stats on selection, cross‐Tenant naming policies, and reusing naming sequence numbers. For both Master Tenant and Subtenant users, defining the deploy archive store, cloud‐init setting, the PXE boot root password, and default App Blueprint types are available. | This permission is recommended to only be assigned to roles utilized within the Master Tenant. |  |
+| Admin: Roles | None, Read, Full | This setting determines access to the Administration > Roles page. When given to a Subtenant user, the ability to create user roles is granted. When given to a Master Tenant user, the ability to create and manage Tenant and Multi‐Tenant Users roles is also granted. | The Roles page is where roles are defined. On create, a name and description are defined. Once created, the Role is accessed and feature access, Group access, Instance Type access and Blueprint access may be configured. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC) either globally or within their Subtenant. |  |
+| Admin: Service Plans | None, Read, Full | This setting determines access to Administration > Plans & Pricing. When given to a Subtenant user, access to the Plans tab is granted. When given to a user in the Master Tenant, the Price Sets and Prices tabs are also available. | The Plans tab is where service plans are defined. On create, a name and code (for API) are defined, display order, provisioning type, storage, memory, core count and the price may be configured. Additionally, the actions menu will allow group access to be scoped. | This permission is recommended for those responsible for defining and managing pricing and applying plans. |  |
+| Admin: Tenant | None, Read, Full | This setting determines access to the Administration > Tenants page. With this permission, local users may be created or deleted within each Tenant. Critical Note: Granting this permission to Subtenant users will expose all Tenants and Tenant users to the Subtenant. | The Tenant page is where all Tenants may be viewed, edited, created, or even deleted. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant who are responsible for the creation, configuration, and/or deletion of Subtenants. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Tenant ‐ Impersonate Users | None, Full | This setting allows or disallows access to impersonate users. This selection is located on the Administration > Users page in the Actions menu. When set to Full, Impersonate selection is available. | This permission allows for users in the Master Tenant to impersonate users of the Master Tenant and Subtenants. | This permission is recommended to be assigned only to Roles utilized within the Master Tenant who are responsible for configuring RBAC or for supporting users. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Users | None, Read, Full | This setting determines access to the Administration > Users page (both Users and User Groups tabs). User Roles can also be set or edited when creating or editing a User on this page. Note: A Master Tenant user with the Admin: Tenants (Full) permission may also access and perform user management from the associated Tenant page. | The User tab is where all users may be viewed, edited, created, or even deleted. The User Groups tab is where User Groups may be viewed, edited, created, or even deleted. Within VM Essentials, a User Group may be selected during provisioning in order to add each group member’s credentials to an Instance. When creating a User Group a name, description, server group (in Linux, name of the group to assign members), sudo access toggle, and a list of users are defined. | This permission is recommended for those responsible for managing users and RBAC. |  |
+| Admin: Whitelabel Settings | None, Full | Allows or disallows access to the Whitelabel tab in Administration > Settings. | The Whitelabel tab is where custom Tenant logos, colors, and security banners may be configured. | This permission is recommended for those responsible for branding tenants, whether they are Master Tenant users or individual Subtenant users. |  |
+
+## API Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| API: Billing | None, Read, Full | Allows or disallows access to invoices and projects via VM Essentials API/CLI. | The invoices API/CLI is used to generate bills and gather highly‐granular costing data for supported Clouds. Read access allows list and get functions and Full allows access to post (refresh). | This permission is recommended for those responsible for generating invoices or projects. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| API: Execution Request | None, Full | Allows or disallows access to an API endpoint. | This endpoint allows users to execute scripts on Instances, containers, or hosts and then polls for a response. | This permission is recommended for those responsible for arbitrary API script execution. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Backups Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Backups | None, View, Read, User, Full | Determines access to the Backups secton of VM Essentials UI, including the Summary, Jobs, Backups, and History subpages. The “User” permission allows access only to backup objects the user owns. | The Summary subpage allows the user to see the number of configured backups, the success rate, recent failures, and the size of the backups, as well as, the upcoming and in‐progress backups. The Jobs subpage is where backup jobs may be created, cloned, edited or deleted. On create, a name, code (for use within the API), retention count, and schedule are selected (Note: Selectable schedules are defined Execution Schedules which are created in the Library > Automation). On the backups subpage, a list of configured backups is provided and new backups may be created or on‐demand backups may be executed. On create, the place where the target exists is selected (Instance, Host, or Provider), the source is selected and a name is defined as well as the selected execution schedule. On the History subpage both the backups and restores tabs are available. Names, statuses, start times, durations and size may be viewed. | This permission is recommended for those responsible for performing the backup and restoration of workloads. |  |
+| Backups: Integrations | None, Read, Full | Determines access to the Backups > Integrations page. | From this page, backup integrations may be created, edited, or deleted. The page also provides the status of existing integrations. On create the integration product is selected and all associated connection and authentication information must be provided. Additionally, visibility is set to either public or private. Integrations available include Avamar, Commvault, Rubrik, Veeam, and Zerto. | This permission is recommended for those responsible for the integration between VM Essentials and backup technologies. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Catalog Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Catalog (Formerly Service Catalog: Catalog) | None, Full | Determines access to Provisioning > Catalog and Catalog in the Service Catalog Persona view | The Catalog page displays the complete list of Catalog Items that can be ordered from the Service Catalog | This permission is recommended for users who will order items from the Service Catalog |  |
+| Catalog: Dashboard (Formerly Service Catalog: Dashboard) | None, Read | Determines access to and Dashboard in Service Catalog Persona view | The Catalog Dashboard contains featured Catalog Items, recently‐ordered Catalog items and Inventory items. The Catalog Dashboard is the default landing page for the Service Catalog Persona view | This permission is recommended for users who will use the Service Catalog |  |
+| Catalog: Inventory (Formerly Service Catalog: Inventory) | None, Full | Determines access to and Dashboard in Service Catalog Persona view | The Inventory is the complete list of user‐owned items provisioned from the Service Catalog | This permission is recommended for users who will use the Service Catalog and need to be able to view details on the items they’ve provisioned from the Catalog |  |
+
+## Infrastructure Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Infrastructure: Boot | None, Read, Full | Determines access to the Integrations > Bootpage, including the Mapping, Boot Menus, Answer Files, Images, and Discovered MAC Addresses tabs. | VM Essentials includes a PXE Server to provide for rapid bare metal provisioning. The Boot page is where users may add, edit, or delete answer files, as well as, manage their own images or use existing ones. Boot menus and mappings are also managed here and discovered MAC addresses are displayed. | This permission is recommend for those responsible for bare metal provisioning. |  |
+| Infrastructure: Certificates | None, Read, Full | Determines access to the SSL Certificates tab on the Infrastructure > Keys& Certs page. | The SSL Certificates page is where certificates may be uploaded and managed. These certificates may then be used within VM Essentials when orchestrating load balancers. | This permission is recommended for personnel who will be orchestrating and provisioning load balancers. |  |
+| Infrastructure: Clouds | None, Read, Group, Full | Determines access to the Infrastructure > Clouds page. The “Group” permission limits the Cloud list page (Infrastructure > Clouds) to show only Clouds in their assigned Groups. | The Cloud page is where new Clouds are integrated with VM Essentials and existing Cloud integrations are managed. This includes creating a code for use within the API, the location, visibility, tenant, whether or not it should be enabled, and if VMs should be automatically powered on. Additionally, Clouds may be integrated from the Clouds tab of a Group detail page. | This permission is recommended for those responsible for configuring RBAC as well as those responsible for VM Essentials Cloud Integrations. |  |
+| Infrastructure: Clusters | None, Read, Group, Full | Determines access to the Infrastructure > Clusters page. | The Clusters page allows you to create and manage Kubernetes, Docker, and KVM Clusters, as well as Cloud‐specific Kubernetes services such as EKS. | This permission is recommend for those creating and managing containers or container services. |  |
+| Infrastructure: Compute | None, Read, Full | Determines access to the Infrastructure > Hostspage, including the Hosts, Virtual Machines, and Bare Metal tabs. | The Hosts page provides for viewing and managing hosts, virtual machines, and bare metal hosts. On the bare metal hosts page, hosts may come from PXE boot or may be manually added. On the Hosts page hypervisors and Docker hosts are displayed. The Virtual Machines page lists all VMs. On all three pages actions may be performed against machines. Additionally, views may be refined by altering the columns displayed and CSV/JSON exporting of lists is available. | This permission is recommend for those whom need to take action on machines and those responsible for bare metal provisioning. |  |
+| Infrastructure: Credentials | None, Read, Full | Determines access to the Credentials tab in Infrastructure > Trust | The credentials tab allows you to create and manage credential sets stored internally and in external Cypher server integrations | This permission is recommended for those responsible for maintaining credentials |  |
+| Infrastructure: Groups | None, Read, Full | Determines access to the Infrastructure > Groups page. | The Groups page is where VM Essentials Groups are created and given a code for use within the API. Additionally, the DNS service, CMDB, service registry, and config management may be selected. Existing Clouds/Hosts or new Clouds/Hosts are added to the Group and virtual or bare metal machines may be viewed. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC). |  |
+| Infrastructure: Keypairs | None, Read, Full | Determines access to the Key Pairs tab on the Infrastructure > Keys& Certs page. | The Keypairs page allows for ease in accessing instances via SSH. On create a name, public key, private key, and passphrase are entered. | This permission is recommended for those whom utilize VM Essentials deployment and management of Linux Instances. |  |
+| Infrastructure: Kubernetes Control | None, Full | Determines access to the Control tab on Kubernetes Cluster detail pages (Infrastructure > Clusters > Selected Kubernetes Cluster > ControlTab) | Run `kubectl` commands, apply templates, and run workloads on the Kubernetes Cluster | This permission is recommended for Kubernetes Cluster administrators |  |
+| Infrastructure: Load Balancers | None, Read, Full | Determines access to the Infrastructure > Load Balancers page, including both the Load Balancers and Virtual Servers tabs. | The Load Balancers page is where new load balancer integrations may be configured. Additionally, existing integrations may be managed. The Virtual Servers page is where virtual servers are managed to include policies, pools, profiles, monitors, nodes, and rule scripts may be managed. | This permission is recommended for those responsible for integrating VM Essentials with load balancers as well as those responsible for managing virtual servers. |  |
+| Infrastructure: Move Servers | None, Full | Determines access to the “Change Cloud” action on server detail pages (Infrastructure > Compute > Virtual Machines tab > SelectedVM > Actions > Change Cloud) | Change Cloud allows server records to be migrated from one Cloud to another. Note that this is not a migration tool but simply allows for upkeep of records in VM Essentials. | This permission is recommended for appliance administrators. See other sections of VM Essentials documentation for more information on the use of this feature. |  |
+| Infrastructure: Networks | None, Read, Group, Full | Determines access to the Infrastructure > Networks page, including the Networks, network groups, and integrations tabs. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Networks page is where networks are configured for DHCP or static IP assignment and existing networks are displayed. The Network Groups page is where networks are grouped to allow round robin provisioning among the group. The Integrations page is where IPAM, DNS, security, service registry, and virtual network tools are integrated. These include Cisco ACI, VMware NSX T and V, Infoblox, Bluecat, phpIPAM, SolarWinds, Stealth, Microsoft DNS, PowerDNS, and Route 53. | This permission is recommended for those responsible for integration with network technologies and the configuration and management of networks to be used during provisioning. |  |
+| Infrastructure: Policies | None, Read, Full | Determines access to the Policies tabs on the Group and Cloud detail pages (Infrastructure > Groups > selected Group OR Infrastructure > Cloud > selected Cloud). | Policies can be created from this tab which are scoped to the Cloud or Group being viewed. | This permission is recommended for users who will need to set quotas which pertain specifically to Groups or Clouds the user has access to. |  |
+| Infrastructure: Security Groups | None, Read, Full | Determines access to the Security Groups tab on the Infrastructure > Networks page. | The Security Groups page is where Security Groups (aka virtual firewalls) are defined. | This permission is recommended for those responsible for firewall configuration and management. |  |
+| Infrastructure: State | None, Read, Full | Determines access to the power state toggle on the Infrastructure > Hostspage. | This toggle moves Hosts between a started and stopped state. | This permission is recommended for those responsible for managing Hosts. |  |
+| Infrastructure: Storage | None, Read, Full | Determines access to the Infrastructure > Storage page, including the Buckets, File Shares, Volumes, Data Stores, and Servers tabs. | The Servers page is where storage integrations are configured. Integrations available include 3Par, AWS S3, Dell EMC ECS and Isilon, Huawei or Open Telekom OBS and Huawei, Open Telekom, OpenStack SFS. The Volumes page is where storage volumes may be created or viewed. The File Shares page is where File Shares of types CIFS, Dell EMC ECS or Isilon, local storage, and NFSv3 may be configured. The Buckets page is where storage buckets of type AWS S3, Alibaba, Azure, Open Telekom OBS, OpenStack Swift, Racspace CDN may be created. Storage buckets are used for Backup, Archives, and Virtual Images. The Data Store page is where permissions to data stores may be managed and new data stores are added. | This permission is recommended for those responsible for storage integrations and configurations. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+| Infrastructure: Storage Browser | None, Read, Full | Determines file browsing access to buckets and file shares on the Buckets and File Shares tabs of the Infrastructure > Storage page. | The Storage Browser permission allows users who also have appropriate Infrastructure: Storage permission to browse, add files and folders, download, and delete from the buckets and file shares. | This permission is recommended for those who need to browse storage. |  |
+| Infrastructure: Trust Integrations | None, Read, Full | Determines access to the Integrations tab of the Infrastructure > Keys& Certs page. | The Integrations tab is where new trust integrations can be configured. | This permission is recommended for those responsible for the integration between VM Essentials and trust providers. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+
+## Library Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Library: App Blueprints (Formerly Provisioning: Blueprints) | None, Read, Full | Determines access to the Library > Blueprints > App Blueprints page. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of VM Essentials is available. | This permission is recommended for those responsible for defining VM Essentials‐type Blueprints. |  |
+| Library: Blueprints ‐ ARM (Formerly Provisioning: Blueprints ‐ ARM) | None, Provision, Full | Determines access to ARM‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from ARM Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of ARM is available. | This permission is recommended for those responsible for defining ARM blueprints. |  |
+| Library: Blueprints ‐ CloudFormation (Formerly Provisioning: Blueprints ‐ CloudFormation) | None, Provision, Full | Determines access to CloudFormation‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from CloudFormation Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of CloudFormation is available. | This permission is recommended for those responsible for defining CloudFormation blueprints. |  |
+| Library: Blueprints ‐ Helm (Formerly Provisioning: Blueprints ‐ Helm) | None, Provision, Full | Determines access to Helm‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Helm Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Helm is available. | This permission is recommended for those responsible for defining Helm blueprints. |  |
+| Library: Blueprints ‐ Kubernetes (Formerly Provisioning: Blueprints ‐ Kubernetes) | None, Provision, Full | Determines access to Kubernetes‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Kubernetes Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Kubernetes is available. | This permission is recommended for those responsible for defining Kubernetes blueprints. |  |
+| Library: Blueprint ‐ Terraform (Formerly Provisioning: Blueprints ‐ Terraform) | None, Provision, Full | Determines access to Terraform‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Terraform Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Terraform is available. | This permission is recommended for those responsible for defining Terraform blueprints. |  |
+| Library: Catalog Items (Formerly Tools: Self Service) | None, Read, Full | Determines access to Library > Blueprints > Catalog Items | Library > Blueprints > Catalog Items allows administrators to configure Catalog Items for the Library Catalog and Self Service Persona users | This permission is recommended for those responsible for creating and managing Library Catalog Items. |  |
+| Library: Instance Types (Formerly Provisioning: Library) | None, Read, Full | Determines access to the Library > Blueprints > Instance Types | Library > Blueprints > Instance Types is where Instance Types are created and maintained. | This permission is recommended for those responsible for managing the Instance Types. |  |
+| Library: Integrations (Formerly Provisioning: Automation Integrations) | None, Read, Full | Determines access to Library > Integrations. | Library > Integrationsis where Library Automation created and maintained.. These include Chef, Puppet, Ansible, Ansible Tower and vRealize Orchestrator. | This permission is recommended for those responsible for the integration between VM Essentials and integrated automation technologies. |  |
+| Library: Packages | None, Read, Full | Determines access to Library > Templates > Cluster Packages. | Library > Templates > Cluster Packages is where Cluster Packages are created or edited. Cluster Packages are associated with Cluster Layouts | This permission is recommended for those responsible for Cluster Layout templating |  |
+| Library: Options | None, Read, Full | Determines access to Library > Options ‐ Inputs (Option Types) and Option Lists. |  | This permission is recommended for those responsible for creating and managing Library Inputs (Option Types) and Option Lists. |  |
+| Library: Scheduling ‐ Execute (Formerly Provisioning: Scheduling ‐ Execute) | None, Read, Full | Determines access to Library > Automation > Execute Scheduling. | The Execute Scheduling is where time schedules for Jobs, including Task, Workflow, and Backup Jobs are created and managed. | This permission is recommended for those responsible to create and manage schedules to be selected when scheduling jobs. |  |
+| Library: Scheduling ‐ Power (Formerly Provisioning: Scheduling ‐ Power) | None, Read, Full | Determines access to Library > Automation > Power Scheduling. | Power Scheduling is where startup and shutdown times are created, these schedules can be applied via policy or manaully. | This permission is recommended for those responsible to create and manage power schedules. |  |
+| Library: Tasks (Formerly Provisioning: Tasks) | None, Read, Full | Determines access to Library > Automation > Tasks and Library > Automation > Workflows. | Library > Automation > Tasks is where Tasks are created and managed. Library > Automation > Workflows is where Workflows are created and managed. Workflows are used to execute one or many tasks during specified phases. | This permission is recommended for those responsible for creating provisioning and operational scripts. |  |
+| Library: Tasks ‐ Script Engines (Formerly Provisioning: Tasks ‐ Script Engines) | None, Full | Determines access to **Execute Target** of **Local** for Tasks. | This permission limits Tasks from being able to run on the Morpheus appliance(s). Additionally, Task Types that only contain the **Execute Target** of **Local** will be removed, such as: Groovy, Javascript, and Python Task Types. | This permission is recommended for those responsible for Tasks that may need to execute on the appliance(s). |  |
+| Library: Templates | None, Read, Full | Determines access to Library > Templates | Library > Templates is where Spec Templates, File Templates, Script Templates and Security Packages are created and managed. | This permission is recommended for those responsible for creating and managing Spec Templates, File Templates, Script Templates and Security Packages. |  |
+| Library: Thresholds (Formerly Provisioning: Thresholds) | None, Read, Full | Determines access to Library > Automation > Scale Thresholds. | Scale Thresholds is where preconfigured settings for auto‐scaling Instances are configured. When adding auto‐scaling to an Instance, existing Scale Thresholds can be selected to define auto‐scaling rules. | This permission is recommended for those responsible for defining auto‐scaling for Instances. | This permission is recommended to be set to None or Read on the Tenant Role to restrict access for Subtenant users. |
+| Library: Virtual Images (Formerly Provisioning: Virtual Images) | None, Read, Full | Determines access to the Library > Virtual Images page. | Library > Virtual Images is where user and system Virtual Images are managed. | This permission is recommended for those who are responsible for image management. |  |
+
+## Lifecycle Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Environment Variables | None, User, Read, Full | Allows access to the Environments tab of the Instance detail page | Allows Instance environment variables to be edited. If set to “User” level only environment variables of Instances owned by the currently logged in user may be edited. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Extend Expirations | None, User, Full | Determines if the user can extend an expiration or shutdown Policy | Allows the user to extend automated shutdown or expiration policies set against any workload (“full” permission) or against the user’s own workloads (“user” permission) | This permission is recommended for administrators or those who need to be able to extend Policies set against their own workloads (“user” level permission) |  |
+| Power Control | None, User, Full | Allows access to power state controls for Instances and servers, including stopping, starting, restarting and suspending. | Allows the user to change the current power state of Instances and servers | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure | None, User, Full | Allows general access to Instance and server reconfigure (resize) feature. See additional reconfigure permissions below for more granular control over specific reconfigure functionality. | Allows general access to reconfigure features for Instances and servers. “User” level permission allows only Instances and servers owned by the currently logged in user to be reconfigured. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Change Plan | None, User, Full | Allows the user to change the Instance service plan | When reconfiguring, the user may change the service plan associated with the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their plans changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Add | None, User, Full | Allows the user to add disks to an Instance or server during reconfigure. | When reconfiguring, the user may add disks to the selected Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Change Type | None, User, Full | Allows the user to change the datastore or volume type during reconfigure. | When reconfiguring, the user may update datastore or volume types. “User” level permission allows only Instances owned by the currently logged in user to have their disk types changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Modify | None, User, Full | Allows the user to modify an attached disk during reconfigure. | When reconfiguring, the user may modify disks attached to the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Remove | None, User, Full | Allows the user to remove disks or volumes during reconfigure. | When reconfiguring, the user may remove disks attached to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks removed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Add | None, User, Full | Allows the user to add a network adapter during reconfigure. | When reconfiguring, the user may add a network interface to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces added. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Modify | None, User, Full | Allows the user to edit network adapters during reconfigure. | When reconfiguring, the user may edit network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces modified. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Remove | None, User, Full | Allows the user to remove network adapters during reconfigure. | When reconfiguring, the user may remove network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces removed. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Retry/Cancel | None, Full | Determines access to retry and cancel buttons for Tasks (for example, in the History tab of an Instance detail page) | Retry and cancel functionality allows failed automation Tasks to be retried or stuck Tasks to be stopped from various places within VM Essentials UI (such as in the History tab of an Instance detail page) |  |  |
+
+## Monitoring Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Monitoring | None, Read, User, Full | Determines level of access to the Monitoring section of VM Essentials UI, including the Status, Apps, Checks, Groups, Incidents, Contacts, and Alert Rules subpages. The “User” permission will allow access only to objects the user owns. | The Checks page is where automatically‐created checks are customized or new checks are created. The Groups and Apps pages are where checks may be grouped. The Incidents page is where incidents are created upon Check failure. The Contacts page is where contacts may be added for notifications. The Alert Rules page is where notification are configured. | This permission is recommended for those responsible for monitoring applications, incidents, or configuring notifications. |  |
+| Monitoring: Logs (Formerly Logs) | None, Read, User, Full | Determines level of access to the Logs section of VM Essentials UI. The “User” permission will allow access only to objects the user owns. | Monitoring > Logs is where Instance and Server logs may be viewed (also must be enabled in order to view Appliance logs from Administration > Health > Morpheus Logs Logs when health permission is also enabled). | This permission is recommended for those who should have access to Instance and Server logs. | Setting permission to Full on the Tenant Role will give Subtenant users full access to all logs appliance‐wide, including to workloads living in other Tenants, for any Subtenant users who also have Full permission on their User Role. It’s recommended that you set this permission to User on the Tenant Role so that Subtenant users are not able to see logs for workloads other than their own. |
+
+## Networks Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Networks: DHCP Relays | None, Read, Full | Determines access to the DHCP Relays in applicable network integrations | Allows DHCP Relays to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: DHCP Servers | None, Read, Full | Determines access to the DHCP Servers in applicable network integrations | Allows DHCP Servers to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: Domains | None, Read, Group, Full | Determines access to the Domains tab on the Infrastructure > Network page. Domains may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into Domains scoped to Groups they can access. | The Domains page is where network domains are managed. Domains are used for setting FQDNs, joining Windows Instances to domains, and creating A‐Records with DNS integrations. On create the domain controller and credentials for domain join must be provided. | This permission is recommended for those responsible for VM Essentials DNS and domain‐join integrations. |  |
+| Networks: Firewalls | None, Read, Manage Rules, Full | Determines access to the Firewall tab on applicable network integrations detail pages. When the “Manage Rules” permission is given, users have read‐only access to firewall groups and the ability to create and manage firewall rules on those groups | The Firewall tab is where network firewall groups and rules are viewed, created and managed | This permission is recommended for those tasked with network security management |  |
+| Networks: Floating IPs | None, Read, Full | Determines access to the Floating IPs tab on the Network list page (Infrastructure > Network) | The Floating IPs tab is where Floating IPs from supported Clouds are listed once synced into VM Essentials Users may also release unattached Floating IPs from this page and link through to any workloads which have Floating IPs attached | This permission is recommended for those tasked with network management |  |
+| Networks: IP Pools | None, Read, Group, Full | Determines access to the IP Pools tab on the Network list page (Infrastructure > Network). IP Pools may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into IP Pools scoped to Groups they can access. | The IP Pools tab is where IP pools from various networks are displayed. Detail pages for IP pools can also be accessed here | This permission is recommended for those tasked with IP address management |  |
+| Networks: Integration | None, Read, Full | Determines access to the Integrations tab on the Network list page (Infrastructure > Network) | The integrations tab is where network integrations can be viewed, added and managed. Additionally, the detail pages for network integrations are accessed here | This permission is recommended for those tasked with handling network integrations and their use within VM Essentials |  |
+| Networks: Proxies | None, Read, Full | Determines access to the Proxies tab on the Infrastructure > Networks page. | The Infrastructure Networks Proxies page is where Proxy configurations are stored, which are available for use by the provisioning engines. | This permission is recommended for those responsible for configuring proxies to be used when provisioning. |  |
+| Networks: Router Firewalls | None, Read, Full | Determines access to Firewall tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Firewall tab is where firewall rules are viewed, created, and managed | This permission is recommended for those responsible for managing firewall rules |  |
+| Networks: Router Interfaces | None, Read, Full | Determines access to Interfaces tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Interface tab is where router interfaces can be viewed, created and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router NAT | None, Read, Full | Determines access to the NAT tab on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The NAT tab is where NAT rules are viewed, created, and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router Redistribution | None, Read, Full | Determines access to Route Redistribution tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Route Redistribution tab is where redistribution rules are viewed, created, and managed | This permission is recommended for those responsible for redistribution rules |  |
+| Networks: Router Routes | None, Read, Full | Determines access to Routing tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Routing tab is where routes are viewed, created, and managed | This permission is recommended for those responsible for network route management |  |
+| Networks: Routers | None, Read, Group, Full | Determines access to the Routers tab on the Infrastructure > Networks page. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Routers page is where virtual routers are created and managed from Cloud and Network integrations. | This permission is recommended for those responsible for network management. |  |
+| Networks: Server Groups | None, Read, Full | Determines access to |  |  |  |
+| Networks: Static Routes | None, Read, Full | Determines access to the routing tab on a router detail page (/infrastructure/networks/routes) | The routers tab is where routes are created and managed | This permission is recommended for those responsible for network management |  |
+
+## Operations Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Operations: Activity | None, Read | Determines access to the Activity and History tabs on the Operations > Activity page. | The Activity page displays four types of recent activities: Provisioning, Alerts, Backups, and Permissions. | This permission is recommended for those responsible to monitor or view activities and their statuses within VM Essentials. |  |
+| Operations: Alarms | None, Read, Full | Determines access to the Alarms tab in the Activity section (Operations > Health) | The Alarms tab is where alarms are listed and acknowledgement actions can be taken against them | This permission is recommended for those responsible for monitoring |  |
+| Operations: Analytics | None, Read, Full | Determines access to the Operations > Analytics page. | The Analytics page gives administrators the ability to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. | This permission is recommended for those responsible for understanding utilization and costs. |  |
+| Operations: Approvals | None, Read, Full | Determines access to the Operations > Approvals page. | When a Provision Approval‐type Policy is enabled for a Group or Cloud, an approval request will be created on each relevant provision attempt. These approvals can be handled directly in VM Essentials or dealt with in ServiceNow with a properly‐configured integration. | This permission is recommended for those responsible for approving, denying, or canceling approval requests. |  |
+| Operations: Budgets | None, Read, Full | Determines access to the Operations > Budgetspage. | The Budgets page is where budgets are created and applied to clouds, tenants, users, or groups. | This permission is recommended for those responsible for managing budgets. |  |
+| Operations: Dashboard | None, Read | Determines access to the Operations > Dashboard page (default VM Essentials landing page). | The Dashboard page is a single pane of glass showing quick, easy‐to‐read performance and configuration information about the VM Essentials environment. | “Read” permission is recommended for all users. When set to None, Operations > Reports becomes the default landing page and attempts to go to the Dashboard will redirect users to their User Settings page. |  |
+| Operations: Guidance | None, Read, Full | Determines access to the Operations > Guidance page. | The Guidance page shows recommendations for resource and cost‐utilization optimization. | This permission is recommended for those responsible to optimize utilization and costs of Cloud‐based resources. |  |
+| Operations: Invoices | None, Read, Full | Determines access to the Invoices tab in Operations > Costing | The Invoices tab allows access to highly‐granular historical costing data | This permission is recommended for those responsible for generating invoices and analyzing spend |  |
+| Operations: Reports | None, Read, Full | Determines access to the Operations > Reports page. | The Reports page is where reports may be generated and exported into JSON or CSV format. | This permission is recommended for those responsible for account, infrastructure, provisioning, usage, and cost reports. |  |
+| Operations: Usage | None, Read, Full | Determines access to the Usage tab on the Operations > Activity page. | The Usage tab shows billing information for Instances and hosts that have pricing configured on their Service Plans. | This permissions is recommended for those responsible for cost accounting. |  |
+| Operations: Wiki | None, Read, Full | Determines access to the Operations > Wiki page. | The Wiki page allows easy UI, API and CLI access to information to be referenced or shared with others. Wiki pages encompass individual Clouds, Groups, Servers, Instances, Clusters, and other pages can be manually created. Wiki pages from resources are accessible from the Operations > Wiki page or within individual resource detail pages on their respective Wiki tabs. | This permission is recommend for those responsible for documentation and knowledge management. |  |
+
+## Projects Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Projects | None, Read, Full | Determines access to Projects through VM Essentials API | Projects are used to associate resources together and apply common tags to their invoices | This permission is recommended for those responsible for cost analysis and invoice reporting |  |
+
+## Provisioning Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Provisioning: Administrator | None, Full | When editing an Instance (Provisioning > Instances > selected Instance > EDITbutton), this permission determines access to changing the owner of an Instance. | Allows you to change the owning user of an Instance. | This permission is recommended for those responsible to ensure all instances are owned by appropriate personnel. |  |
+| Provisioning: Advanced Node Type Options | None, Full | This allows or disallows access to the “Extra Options” field of the Node Types tab on the Library page when the Node Type Technology value is set to “VMware”. | When VMware technology type is selected for a new or existing Node Type (Library > Blueprints > Node Types), the “Extra Options” field will be available in the VMware VM Options section. These allow defining advanced vmx‐file parameters during provisioning. | This permission is recommended for those responsible for managing VMware Node Types (images). |  |
+| Provisioning: Apps | None, Read, User, Full | Determines access to the Provisioning > Apps page. The “User” permission will allow access to only object the user owns. | The Apps page allows Instances to be grouped and tiered logically into Apps. From this page, Apps can be deployed from existing Blueprints and Instances can be added to existing Apps. Security groups and environmental variables (Linux Only) may be added and edited. The App log, history, and monitoring tabs may be viewed. | This permission is recommended for those responsible for provisioning. |  |
+| Provisioning: Code Deployments | None, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Deployments page provides the ability to use git, fetch from a url, or upload a file to be utilized during the provisioning of an Instance or pushed to an existing Instance. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Code Integrations | None, Read, Full | Determines access to the Integrations tab on the Provisioning > Code page. | From this page code integrations may be created, edited, or deleted. Integrations available include Git, Github, and Jenkins. | This permission is recommended for those responsible for the integration between VM Essentials and code repositories and services. |  |
+| Provisioning: Code Repositories | None, List Files, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Code Repositories contains the repositories integrated with VM Essentials allowing users to browse repositories folders and files and view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Execute Script | None, Full | Determines access to the Run Script and Apply Template selections from the Actions menu on an Instance detail page | These selections bring up a menu allowing the user to select a script and run it against the viewed Instance or select a template to write to the Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Task | None, Full | Determines access to the Run Task selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Task and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Workflow | None, Full | Determines access to the Run Workflow selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Workflow and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Executions | None, Read, User | Determines access Provisioning > Executions. When the permission level is set to “User” only the executions owned by the current user are shown | Provisioning > Executions is where Task, Workflow, and Security Scan execution output can be viewed | This permission is recommended for those who are responsible for managing or troubleshooting Task, Workflow, and Security Scan executions. |  |
+| Provisioning: Import Image | None, Full | Determines access to the Import as Image and Clone to Image selections from the Actions menu on an Instance detail page | These selections allow users to create an image from an existing Instance or import the Instance as an image to a selected bucket | This permission is recommended for those responsible for managing the library of provisionable items |  |
+| Provisioning: Instances: Add | None, Full | Gives access to create Instances. Without this permission the user cannot directly add Instances. | The “+ ADD” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance create API actions as well | This permission is recommended for any user who needs to be able to provision Instances |  |
+| Provisioning: Instances: Clone | None, User, Full | Determines the presence of the “Clone” selection under the Actions menu on the Instance detail page and Instance clone API functionality | The “Clone” selection will not be available under the “Actions” menu on the Instance detail page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be cloned. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Delete | None, User, Full | Determines the presence of the “Delete” button on the Instance detail page, delete bulk action on the Instances list page, and Instance delete API functionality | The “Delete” button will not be available on the Instance detail page and the delete action will not be available from the Instances list page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be deleted. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Edit | None, User, Full | Gives access to the Edit Instances modal for existing Instances (and corresponding API functionality). This allows the user to edit an Instance display name, tags, or Input (custom option) values | The “EDIT” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance edit API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be edited. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Force Delete | None, Full | Determines access to the force delete option when deleting Instances | The force delete option (checkbox) will not be available when deleting Instances if this permission is not given. Force deleting allows VM Essentials to delete an Instance object even when it is unable to confirm the delete happened in the target cloud. Occasionally, this may be necessary but improper use can cause orphaned objects. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: List | None, User, Full | Controls which Instances are listed on the Instances list page (Provisioning > Instances). When set to “User”, only Instances owned by the currently logged in user will be displayed. |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Lock/Unlock | None, User, Full | Gives access to the lock/unlock actions on Instance detail pages (and corresponding API functionality). This allows the user to lock or unlock Instances which reduces the chances of accidental removal of important workloads. | The Lock/Unlock selections will not be visible in the Actions menu on the Instances List Page if permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be locked or unlocked. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Remove From Control | None, User, Full | Gives access to deleting an Instance in VM Essentials only. The instance remains in the target cloud. This may only be done for brownfield workloads which were converted to managed VM Essentials Instances |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Scale | None, User, Full | Gives access to the scale tab on Instance detail pages which allow configuration of automated scaling thresholds (and corresponding API functionality). This allows the user to control scaling thresholds and add/remove nodes from an Instance. | The Scale tab on the Instance detail pages will not be visible and the user will not be able to add/remove nodes from Instances if the permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be scaled. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Settings | None, User, Read, Full | Gives access to configuration changes if the Instance supports dynamic settings templates |  |  |  |
+| Provisioning: Job Executions | None, Read | Determines access to the Job Executions tab on the Provisioning > Jobs page. | The Job Executions page contains execution history of completed jobs, including any process outputs and error messages. | This permission is recommended for those who are responsible for managing or troubleshooting jobs. |  |
+| Provisioning: Jobs | None, Read, Full | Determines access to the Jobs tab on the Provisioning > Jobs page. | The Jobs page is where jobs are scheduled for the execution of automation Tasks and Workflows against Instances or servers. | This permission is recommended for those responsible to schedule the exectution of Tasks or Workflows. |  |
+| Provisioning: Remote Console | None, User, Full | Determines access to the console on a Host detail page (Infrastructure > Hosts > selected Host, VM, or Bare Metal resource > Consoletab). The “User” permission gives access to the console only for resources the logged in user owns. | Remote console access for Instances, hosts, virtual machines, and bare metal. | This permission is recommended for those who need console access for provisioned Cloud resources. |  |
+| Provisioning: Remote Console Auto Login | No, Yes | This allows or disallows the ability to automatically log into the remote console. | VM Essentials will automatically log into the machine using the credentials defined on the VM or Host. The credentials are defined either from the virtual image used, added via cloud‐init or VMware Tools using the global cloud‐init settings (Administration > Settings > Provisioning), or the Linux or Windows settings defined in User Settings. | This permission is recommended when an organization utilizes VM Essentials to create user accounts on provisioned or managed machines, as well as, allow remote console access. |  |
+| Provisioning: Service Mesh | None, Read, User, Full | Determines access to the Provisioning > ServiceMesh page, including the Services and DNS tabs. The “User” permission will allow access only to objects the user owns. | The Service Mesh page displays container services and DNS information. A service mesh ensures fast and reliable communication between containerized application services. | This permission is recommended for those responsible for container management. |  |
+| Provisioning: State | None, Read, Full | Determines access to the State tab for a Terraform Instance or App | The State tab is where [Terraform state management](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-app-state-management) is handled for Terraform Instances or Apps | This permission is recommended for those responsible for any Terraform‐based workloads |  |
+
+## Security Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Security: Scanning | None, Read, Full | Determines access to the Security Packages tab on the Jobs list page (Provisioning > Jobs), Security Scanning type Jobs, and Security Subtab inside the Software tab on a server detail page where the results of security scans are viewed | Allows access to view, create, and run security scans on existing systems, as well as view the results of previously‐run scans | This permission is recommended for those responsible for security compliance of existing systems |  |
+
+## Snapshots Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Snapshots | None, Read, Full | Determines access to the “Create Snapshot” function in the Actions menu on an Instance detail page (Provisoning > Instances > selected Instance). | If utilizing a VMware Cloud, the ability to create snapshots is available on the Instance detail page (Provisoning > Instances > selected Instance). | This permission is recommended for Instance owners who should be allowed to take snapshots. |  |
+| Snapshots: Linked Clone | None, Full | For VMware Cloud Instances, this controls access to the ability to create linked clone snapshots on the Instance detail page |  |  |  |
+
+## Tools Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Tools: Archives | None, Read, Full | Determines access to the Tools > Archives page. | Archives provides a way to store files and make them available for download by scripts and users. Archives are organized by buckets. Each bucket has a unique name that is used to identify it in URLs and Scripts. | This permission is recommended for those responsible for storage or scripts which will use the Archive. |  |
+| Tools: Cypher | None, Read, User, Full, Full Decrypt | Determines access to the Tools > Cypher page. The “User” permission will allow access only to objects the user owns. The “Full Decrypt” permission will allow for decryption of secrets. | Secure key/value store. Cypher keys can be used in scripts. | Recommended for those who need to store or use security key value pairs. |  |
+| Tools: Image Builder | None, Read, Full | Determines access to the Tools > Image Builder page, Image Builds, Boot Scripts, and Preseed Scripts tabs. | The VM Essentials Image Builder tool creates vmdk, qcow2, vhd and raw images. The Image Builder creates a blank VM in VMware, attaches an OS ISO, executes a boot script on the VM at startup via VNC, which calls a preseed script that runs the unattended OS installation and configuration. VM Essentials then executes an OVA export of the completed vmdk to the target storage provider and converts the image to all other specified formats. | Recommended for those who are responsible for image creation. |  |
+| Tools: Kubernetes | None, Read, User, Full | Allows for the management of Kubernetes clusters via the API (may be deprecated in the near future). | Allows for the management of Kubernetes clusters via the API | This permission is recommended for those who need to manage Kubernetes clusters via the API. | It is recommended this permission is set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Virtual Desktop Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Virtual Desktop: Copy/Paste | None, Full | Allows copy and paste access from the virtual desktop terminal | Enables the user to copy and paste values from a virtual desktop session into the paste buffer of their local computer |  |  |
+| Virtual Desktop: Local Printer | None, Full | Enables printing from a virtual desktop session to a locally installed printer |  |  |  |
+| Tools: VDI Pools | None, Read, Full | Allows for the management of virtual desktop (VDI) pools. | Enables the user to access the VDI Pools section (Tools > VDI Pools) and view existing pools (with “read” permission) or create and edit pools (with “full” permission). Related API functions are also granted with this feature permission. | This permission is recommended for those needing to manage VDI pools |  |
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json b/corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
new file mode 100644
index 0000000..6a3999c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+  "title": "Networking Integrations",
+  "ordinal": 346,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html",
+  "topic_cluster": {
+    "clustering_title": "Networking Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md b/corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
new file mode 100644
index 0000000..1cd3dab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
@@ -0,0 +1,6 @@
+# Networking Integrations
+
+**Subtopics**  
+
+- **[ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html)**
+- **[HPE Aruba CX DSS](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json b/corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
new file mode 100644
index 0000000..4236fa6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+  "title": "Dashboard",
+  "ordinal": 6,
+  "parent_title": "Operations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.html",
+  "topic_cluster": {
+    "clustering_title": "Dashboard",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+        "clustering_title": "Dashboard"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+        "clustering_title": "Dashboard"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md b/corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
new file mode 100644
index 0000000..880d8fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
@@ -0,0 +1,17 @@
+# Dashboard
+
+The Dashboard is a single, high-level view into your environment which includes easy-to-read performance and configuration information. In many cases other areas within VM Essentials UI will allow you to drill deeper into the information presented in the dashboard.
+
+![dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-EED20D75-2987-4570-A0F2-5AD920F49D1D-high.png)
+
+**Subtopics**  
+
+- **[Environment](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.html)**
+- **[System Status](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.html)**
+- **[Favorites](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.html)**
+- **[Alarms (dashboard)](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.html)**
+- **[Instance Status](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.html)**
+- **[Instances By Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-91D3F799-4C17-4008-B605-FEE370890091.html)**
+- **[Task Executions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json b/corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
new file mode 100644
index 0000000..1d00a16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+  "title": "Using Cypher Keys in Scripts",
+  "ordinal": 223,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.html",
+  "topic_cluster": {
+    "clustering_title": "Using Cypher Keys in Scripts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+        "clustering_title": "Using Cypher Keys in Scripts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+        "clustering_title": "Using Cypher Keys in Scripts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md b/corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
new file mode 100644
index 0000000..3cb9e8b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
@@ -0,0 +1,15 @@
+# Using Cypher Keys in Scripts
+
+To use a Cypher key in a script, use the following syntax:
+
+`<%=cypher.read('var_name')%>`
+
+Example: `PASSWORD=<%=cypher.read('secret/myuserpassword')%>`
+
+Cypher also includes an option to read a value from the `password/*` mountpoint or create one if it doesn’t already exist. Use the following syntax:
+
+`<%=cypher.readPassword('var_name')%>`
+
+Example: `` PASSWORD=<%=cypher.readPassword('myuserpassword')%>` ``
+
+It should be noted that when Cypher keys are created using the `readPassword` function, the subsequent reads can only come from the same user. If another VM Essentials user attempts to run the automation script containing the `readPassword` call, the secret value will not be read and it’s very likely the script will fail. For Tasks that need to be run by multiple users, use a pre-existing Cypher key and reference it back in the script using `read` rather than `readPassword`.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json b/corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
new file mode 100644
index 0000000..b55120f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+  "title": "Hypervisor Console Keyboards",
+  "ordinal": 135,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html",
+  "topic_cluster": {
+    "clustering_title": "Hypervisor Console Keyboards",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md b/corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
new file mode 100644
index 0000000..51b6b77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
@@ -0,0 +1,52 @@
+# Hypervisor Console Keyboards
+
+HVM VMs support guest console access as well as hypervisor console access. For each HVM VM, users can set a keyboard layout configuration which will then be set for use on each session.
+
+IMPORTANT
+
+This feature requires HVM Host agent version 3.0.3 or greater. Upgrade the host agent from the host detail page for **each** host by expanding the ACTIONS menu and clicking "Upgrade Agent." Alternatively, select "Download Agent Script" to download a script to run against the host manually from a terminal session. These scripts are specific to each host so you must download a script for each host and run the correct script against the correct host.
+
+Currently, the following layouts are supported:
+
+- Dutch (Belgium)
+- French (Belgium)
+- German
+- Italian
+- English (United Kingdom)
+- English (United States)
+- French
+- Spanish
+- German (Switzerland)
+- Finnish
+- French (Switzerland)
+- Icelandic
+- Norwegian
+- Portuguese
+- Danish
+
+Setting the Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click EDIT
+6. Expand the Advanced Options section
+7. In the KEYBOARD LAYOUT field, select the desired keyboard localization
+8. Click SAVE CHANGES
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-6EC36C91-5E13-4B5B-AB20-10DE225F85B3-high.png)
+
+Using the Configured Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click on the Console tab
+6. Click on the dropdown labeled GUEST and change the selection to Hypervisor
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-B75612CA-1867-4066-937C-B66FA952D251-high.png)
+7. Click on the keyboard icon and see the keyboard layout has changed to the selected layout
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-EC09C556-7F46-4036-ABDF-7E36BE8BFD8D-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json b/corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
new file mode 100644
index 0000000..a0f500e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+  "title": "Affinity Groups",
+  "ordinal": 125,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md b/corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
new file mode 100644
index 0000000..88598d1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
@@ -0,0 +1,28 @@
+# Affinity Groups
+
+HVM Clusters offer affinity groups and anti-affinity groups. These work similarly to affinity groups on other platforms, such as the affinity rules concept in VMware vSphere. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Whenever possible, servers configured to "Keep Together" will run on the same HVM Host. Servers configured to "Keep Separate" will be balanced across HVM Hosts to the maximum extent possible.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-C5C8E073-11BC-4D5A-A900-14571F77280D-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next cluster sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+TIP
+
+Placement settings (ex. pinning a VM to a specific host) can override an affinity group. HVM Clusters will attempt to implement affinity groups intelligently to work around VM placement. For example, in a group of five VMs configured to "keep together" with one pinned to host 1, the Cluster would run all five VMs on host 1 (if possible) to simultaneously honor the placement and the affinity group. In some scenarios, it will not be possible to simultaneously honor all placements and affinities/anti-affinities.
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-9C039E15-FE97-4CFD-987E-07A16E644534-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-12E8B43B-9A47-46D9-8A99-3EBDF1FAD577-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json b/corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
new file mode 100644
index 0000000..af07886
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+  "title": "VMware vCenter",
+  "ordinal": 313,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html",
+  "topic_cluster": {
+    "clustering_title": "VMware vCenter",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md b/corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
new file mode 100644
index 0000000..1ee0ffe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
@@ -0,0 +1,25 @@
+# VMware vCenter
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.html)**
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.html)**
+- **[Windows Provisioning Tips](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.html)**
+- **[Existing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.html)**
+- **[Service Plans](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-30353E6D-5FA2-470C-BB80-238663945F6F.html)**
+- **[Virtual Images / Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.html)**
+- **[Snapshots](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.html)**
+- **[Tagging and Metadata](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.html)**
+- **[Docker](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B82658C8-6002-424B-B257-D52A7D603BC3.html)**
+- **[Multitenancy](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.html)**
+- **[Advanced](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1EB800EB-6832-487E-BB11-07D8520003CF.html)**
+- **[VMware Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.html)**
+- **[Creating a VM Essentials VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.html)**
+- **[Creating a Windows Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.html)**
+- **[Creating a CentOS/RHEL 7 Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.html)**
+- **[Creating a CentOS/RHEL 8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.html)**
+- **[Creating an Ubuntu 20.04 Image](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.html)**
+- **[Gotchas](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.html)**
+- **[A Note on Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json b/corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
new file mode 100644
index 0000000..9dd6892
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+  "title": "Delete Group",
+  "ordinal": 88,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Group",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+        "clustering_title": "Delete Group"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+        "clustering_title": "Delete Group"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md b/corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
new file mode 100644
index 0000000..39958a6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
@@ -0,0 +1,13 @@
+# Delete Group
+
+## About this task
+
+To delete a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to delete.
+4. Click the Delete button.
+5. Confirm
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json b/corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
new file mode 100644
index 0000000..202446d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+  "title": "Automation",
+  "ordinal": 55,
+  "parent_title": "Library",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.html",
+  "topic_cluster": {
+    "clustering_title": "Automation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+        "clustering_title": "Automation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+        "clustering_title": "Automation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md b/corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
new file mode 100644
index 0000000..47ea9a5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
@@ -0,0 +1,10 @@
+# Automation
+
+Library  >  Automation
+
+The automation section is where scripts, known as Tasks, can be created. Tasks are individual Bash or Powershell scripts which can be selected to run against Instances at the time they are provisioned from the Instance provisioning wizard. In this section, users can also create execution schedules which are configured time intervals on which automated jobs (such as backups) would be carried out.
+
+**Subtopics**  
+
+- **[Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html)**
+- **[Execute Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json b/corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
new file mode 100644
index 0000000..c15cbe1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+  "title": "Google Cloud Storage Buckets",
+  "ordinal": 181,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.html",
+  "topic_cluster": {
+    "clustering_title": "Google Cloud Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+        "clustering_title": "Google Cloud Storage Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+        "clustering_title": "Google Cloud Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md b/corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
new file mode 100644
index 0000000..c485aa7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
@@ -0,0 +1,53 @@
+# Google Cloud Storage Buckets
+
+## About this task
+
+NOTE
+
+Google Cloud Storage Buckets are associated with an existing GCP Cloud integration. Ensure the GCP Cloud integration is pre-existing before attempting to create a new Google Cloud Storage Bucket. On the initial integration and subsequent cloud syncs, Google Cloud Storage Buckets are automatically onboarded and updated.
+
+To add a Google Cloud Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Select the Storage link in the sub-navigation bar
+3. In the BUCKETS tab, Click the + ADD button
+4. Select Google Cloud Storage from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   A friendly name for the bucket in VM Essentials
+
+   STORAGE SERVICE
+   :   Select the GCP cloud integration this bucket should be created in
+
+   PROJECT ID
+   :   Select the Project to create the group under, Projects are a GCP-specific concept and are logical grouping for your resources. Select any existing project associated with your selected GCP cloud integration
+
+   BUCKET NAME
+   :   The name for the bucket resource on the GCP side
+
+   LOCATION TYPE
+   :   Select Region, Dual-Region, or Multi-Region. Buckets with a Region location type will be stored in one GCP region, such as “us-east1 (South Carolina)”. Dual-Region and Multi-Region data is stored in two (or more, in the case of multi-region) GCP regions separated by a significant physical distance. Dual-Region and Multi-Region data is geo-redundant across the multiple selected regions
+
+   LOCATION
+   :   A selected GCP region (or regions, in the case of dual and multi-location data) where the data will be stored
+
+   STORAGE CLASS
+   :   Select Standard, Nearline, Coldline, or Archive. The appropriate storage class will depend on how frequently the bucket data is accessed and how long the type of data in the bucket is expected to be stored. More information on storage classes can be found in [GCP Documentation](https://cloud.google.com/storage/docs/storage-classes#descriptions)
+
+   ACTIVE
+   :   When marked, the bucket is available for use in VM Essentials
+
+   DEFAULT BACKUP TARGET
+   :   Sets the bucket as the default storage option when creating backups at provision time or in the Backups section of VM Essentials
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this Bucket as the default storage target when uploading deployment files in the Deployments section
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this bucket as the default storage target when uploading virtual images from the Virtual Images section, importing images from Instance actions, creating images with the Image Builder, and when creating new images from Migrations
+
+   RETENTION POLICY
+   :   Select None and the files in this bucket will never be deleted or backed up by VM Essentials. When selecting ‘Backup Old Files’, VM Essentials will backup files into another selected bucket once they reach a certain number of days old. When selecting ‘Delete Old Files’, VM Essentials will delete any files that reach a certain number of days old
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json b/corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
new file mode 100644
index 0000000..2eb7ea9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+  "title": "Creating a Windows Image",
+  "ordinal": 332,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Windows Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+        "clustering_title": "Creating a Windows Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+        "clustering_title": "Creating a Windows Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md b/corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
new file mode 100644
index 0000000..9ee003b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
@@ -0,0 +1,6 @@
+# Creating a Windows Image
+
+**Subtopics**  
+
+- **[Supported Versions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.html)**
+- **[Image Preparation](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json b/corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
new file mode 100644
index 0000000..0ec8812
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+  "title": "Activity",
+  "ordinal": 21,
+  "parent_title": "Activity",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md b/corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
new file mode 100644
index 0000000..c5c832f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
@@ -0,0 +1,12 @@
+# Activity
+
+There are three types of activities that are displayed in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
+
+**Subtopics**  
+
+- **[To View a Recent Activity report:](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.html)**
+- **[Review](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json b/corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
new file mode 100644
index 0000000..dfb2449
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+  "title": "Creating Instances",
+  "ordinal": 45,
+  "parent_title": "Instances",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+        "clustering_title": "Creating Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+        "clustering_title": "Creating Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md b/corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
new file mode 100644
index 0000000..1815ffd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
@@ -0,0 +1,25 @@
+# Creating Instances
+
+The Instance catalog is where you will create new workloads targeting the HVM clusters and/or VMware vCenter Clouds available to the VM Essentials environment. The list contains only Instance Types relevant to the provisioning engines which enabled and integrated in the current appliance.
+
+To get started, simply click the + Add button in the upper right of the Provisioning > Instances page. A modal will display allowing the catalog to be searched. Once an item is selected, it is just a matter of following the steps through the wizard.
+
+TIP
+
+The Instance catalog can be customized via role-based access control (RBAC) to restrict provision types only to certain Roles. It is completely customizable.
+
+The next step will ask for a Group and Cloud to be selected. The Group is an abstract representation that can contain multiple HVM clusters or VMware vCenter integrations. Clouds can be in multiple Groups and Groups are also useful for using RBAC to restrict provisioning access and set retainment policies. The wizard continues by allowing us to choose a name for the Instance as well as an environment.
+
+NOTE
+
+Currently the Environment option is most useful for presenting the user with informative metadata around the Instance when coming back to it later.
+
+Moving on, it is now time to configure the Instance. Depending on the Instance Configuration that is chosen, fields will change. This can include cloud-specific fields (i.e. target hosts for HVM clusters or datastores for VMware Clouds). There will also be options like setting an initial user account. Some of these fields are optional and will be represented as such in the wizard.
+
+One last step before the Instance can be provisioned is the Automation step. It is here that you can select Tasks which will run during the provision process and these Tasks must complete successfully in order for the Instance status to be reported as successful. Tasks are either Bash or Powershell scripts which can be configured in the Library > Automationsection.
+
+Now that the steps are completed for provisioning the selected Instance type, simply review your selections and complete. The Instance will automatically show up in the Instances list and its provisioning state will be represented. Depending on what was provisioned this step can range from seconds to minutes.
+
+**Subtopics**  
+
+- **[Converting Discovered Resources to Managed Instances](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json b/corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
new file mode 100644
index 0000000..16fe4fd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+  "title": "Adding ArubaCX Integration",
+  "ordinal": 353,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.html",
+  "topic_cluster": {
+    "clustering_title": "Adding ArubaCX Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+        "clustering_title": "Adding ArubaCX Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+        "clustering_title": "Adding ArubaCX Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md b/corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
new file mode 100644
index 0000000..d3ff52e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
@@ -0,0 +1,73 @@
+# Adding ArubaCX Integration
+
+## About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.
+
+## Procedure
+
+1. Navigate to Administration > Integrations
+2. Select + New Integration > Other > ArubaCX 
+
+   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
+3. Enter the following: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   ENABLED
+   :   Deselect to disable the integration
+
+   USERNAME
+   :   User username for all switches
+
+   PASSWORD
+   :   User password for all switches
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 4
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 4
+
+   UPLINK LAG INTERFACE
+   :   Name of the uplink LAG interface (default is 'lag1')
+4. Select SAVE CHANGES
+
+## Results
+
+Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:
+
+![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)
+
+NOTE
+
+All fields can be edited after saving.
+
+Sample Reference Architecture for EVPN Configuration
+
+1. Minimum four leaf switches, two spine switches, and one core switch
+2. At least two servers in separate racks
+3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
+4. VMs on servers in different racks communicate through the EVPN switch configuration
+5. Route traffic between racks through spine switches
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json b/corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
new file mode 100644
index 0000000..c8ce28a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+  "title": "Trust",
+  "ordinal": 195,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md b/corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
new file mode 100644
index 0000000..9bb75f0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
@@ -0,0 +1,9 @@
+# Trust
+
+The Trust section is where credentials and SSH keypairs are stored. Stored credentials are useful for easy integration with VMware Clouds or other third party technologies using stored credential sets. In the keypairs section, generate SSH keypairs which can be associated with your user account so that your public key is automatically added to the authorized keys file on provisioned workloads for easy access.
+
+**Subtopics**  
+
+- **[Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.html)**
+- **[OAuth 2.0 Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.html)**
+- **[Key Pairs](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json b/corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
new file mode 100644
index 0000000..31387d8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+  "title": "Requirements",
+  "ordinal": 98,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md b/corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
new file mode 100644
index 0000000..c38ea78
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
@@ -0,0 +1,4 @@
+# Requirements
+
+- VM Essentials Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters
+- VM Essentials Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json b/corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
new file mode 100644
index 0000000..dfadc00
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+  "title": "To View a Recent Activity report:",
+  "ordinal": 22,
+  "parent_title": "Activity",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.html",
+  "topic_cluster": {
+    "clustering_title": "To View a Recent Activity report:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+        "clustering_title": "To View a Recent Activity report:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+        "clustering_title": "To View a Recent Activity report:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md b/corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
new file mode 100644
index 0000000..31fea08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
@@ -0,0 +1,10 @@
+# To View a Recent Activity report:
+
+## Procedure
+
+1. Select the `Operations` link in the navigation bar.
+2. Select `Activity` in the sub navigation bar.
+
+## Results
+
+Recent activity is displayed in order from recent to oldest. This view can be searched and filtered by type, user, and date range.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json b/corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
new file mode 100644
index 0000000..130d90a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+  "title": "Adding and Removing Labels",
+  "ordinal": 53,
+  "parent_title": "Labels",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.html",
+  "topic_cluster": {
+    "clustering_title": "Adding and Removing Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+        "clustering_title": "Adding and Removing Labels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+        "clustering_title": "Adding and Removing Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md b/corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
new file mode 100644
index 0000000..65ea1eb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
@@ -0,0 +1,5 @@
+# Adding and Removing Labels
+
+Labels can be created when adding or edited any of the supported constructs listed above. When adding or editing the object, enter or edit the comma-separated list of labels you wish to apply.
+
+![../_images/labeladd.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-B0C645F7-A738-4975-9AA9-9F5E0C581874-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json b/corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
new file mode 100644
index 0000000..c0118b8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+  "title": "Creating an Ubuntu 20.04 Image",
+  "ordinal": 343,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an Ubuntu 20.04 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+        "clustering_title": "Creating an Ubuntu 20.04 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+        "clustering_title": "Creating an Ubuntu 20.04 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md b/corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
new file mode 100644
index 0000000..c360e34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
@@ -0,0 +1,97 @@
+# Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Change the network interface to `eth0` by editing `/etc/default/grub`. The line `GRUB_CMDLINE_LINUX=""` should be edited to `GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"`.
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to VM Essentials to onboard the image and use it to begin building your provisioning library.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.json b/corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
new file mode 100644
index 0000000..4b68fe5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+  "title": "HVM clusters",
+  "ordinal": 100,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CA806876-1093-4A39-BE62-439C4802A915.html",
+  "topic_cluster": {
+    "clustering_title": "HVM clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+        "clustering_title": "HVM clusters"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+        "clustering_title": "HVM clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.md b/corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
new file mode 100644
index 0000000..ed740b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
@@ -0,0 +1,17 @@
+# HVM clusters
+
+An HVM cluster is a hypervisor clustering technology utilizing KVM. Beginning with just a few basic Ubuntu boxes, VM Essentials can create a cluster of HVM hypervisor hosts complete with monitoring, failover, easy migration of workloads across the cluster, and zero-downtime maintenance access to hypervisor host nodes. All of this is backed by a highly-granular RBAC engine, and image library with automation stacks.
+
+**Subtopics**  
+
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html)**
+- **[Base Cluster Details](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.html)**
+- **[Provisioning the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9886AD4A-5C64-4E09-A106-B14419362757.html)**
+- **[Provisioning a Workload](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.html)**
+- **[HVM Cluster Networking](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html)**
+- **[HVM Cluster Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html)**
+- **[Utilizing Existing QCOW & ISO Images from an NFS File Share](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.html)**
+- **[Image Prep (Windows)](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html)**
+- **[Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html)**
+- **[Hypervisor Console Keyboards](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json b/corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
new file mode 100644
index 0000000..2b7a2f6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+  "title": "Overview",
+  "ordinal": 171,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md b/corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
new file mode 100644
index 0000000..f012482
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
@@ -0,0 +1,3 @@
+# Overview
+
+The Network Integrations section allows you to add and manage IPAM, DNS, and Service Registry integrations.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json b/corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
new file mode 100644
index 0000000..06af88a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+  "title": "Operations",
+  "ordinal": 5,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html",
+  "topic_cluster": {
+    "clustering_title": "Operations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md b/corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
new file mode 100644
index 0000000..4ff1d1a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
@@ -0,0 +1,7 @@
+# Operations
+
+**Subtopics**  
+
+- **[Dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.html)**
+- **[Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CD00669C-741C-480C-B444-67F079061438.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.json b/corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.json
new file mode 100644
index 0000000..5d290eb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+  "title": "Wiki",
+  "ordinal": 16,
+  "parent_title": "Operations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CD00669C-741C-480C-B444-67F079061438.html",
+  "topic_cluster": {
+    "clustering_title": "Wiki",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+        "clustering_title": "Wiki"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+        "clustering_title": "Wiki"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.md b/corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.md
new file mode 100644
index 0000000..369495a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD00669C-741C-480C-B444-67F079061438.md
@@ -0,0 +1,11 @@
+# Wiki
+
+The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, and Clusters. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations > Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
+
+![wiki](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-F0F0DA3A-4058-45D6-AECA-8A5BEF62FDBA-high.png)
+
+**Subtopics**  
+
+- **[Highlights](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.html)**
+- **[Creating Wikis](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.html)**
+- **[Hosting Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json b/corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
new file mode 100644
index 0000000..93ff195
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+  "title": "Final VMWare Tasks",
+  "ordinal": 342,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.html",
+  "topic_cluster": {
+    "clustering_title": "Final VMWare Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+        "clustering_title": "Final VMWare Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+        "clustering_title": "Final VMWare Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md b/corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
new file mode 100644
index 0000000..e205cf3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
@@ -0,0 +1,8 @@
+# Final VMWare Tasks
+
+## Procedure
+
+1. Detach any install media
+2. Shutdown the VM
+3. Convert the VM to template on the VM Essentials side
+4. Refresh the VM Essentials Cloud to allow the new template to sync
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json b/corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
new file mode 100644
index 0000000..d64e498
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+  "title": "CIFS File Shares",
+  "ordinal": 187,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.html",
+  "topic_cluster": {
+    "clustering_title": "CIFS File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+        "clustering_title": "CIFS File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+        "clustering_title": "CIFS File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md b/corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
new file mode 100644
index 0000000..4860113
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
@@ -0,0 +1,76 @@
+# CIFS File Shares
+
+## About this task
+
+To Add a CIFS File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select CIFS (Samba Windows File Sharing) from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   HOST
+   :   Enter host IP or resolvable hostname
+       :   Example: `192.168.200.210`
+
+   USERNAME
+   :   CIFS Share Username
+
+   PASSWORD
+   :   CIFS Share User Password
+
+   SHARE PATH
+   :   Enter CIFS Share Path
+       :   Example: `cifs`
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json b/corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
new file mode 100644
index 0000000..3f67029
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+  "title": "Creating Environments",
+  "ordinal": 288,
+  "parent_title": "Overview",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+        "clustering_title": "Creating Environments"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+        "clustering_title": "Creating Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md b/corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
new file mode 100644
index 0000000..1df2e04
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
@@ -0,0 +1,24 @@
+# Creating Environments
+
+## Procedure
+
+1. Select + Create Environment
+2. Populate the following for the New Environment: 
+
+   Name
+   :   The friendly name for the environment in VM Essentials
+
+   Code
+   :   Shortcode used for API and CLI
+
+   Description
+   :   Environment description displayed on the Environments list page
+
+   Display Order
+   :   The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
+
+## Results
+
+NOTE
+
+User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. VM Essentials-default environments can only be hidden from users during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json b/corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
new file mode 100644
index 0000000..950cf98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+  "title": "Example Cluster Deployment",
+  "ordinal": 106,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.html",
+  "topic_cluster": {
+    "clustering_title": "Example Cluster Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+        "clustering_title": "Example Cluster Deployment"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+        "clustering_title": "Example Cluster Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md b/corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
new file mode 100644
index 0000000..0d8747e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
@@ -0,0 +1,15 @@
+# Example Cluster Deployment
+
+In this example cluster, each host box consists of:
+
+- 4 vCPU
+- 16 GB memory
+- 20 GB OS boot disk
+- 250 GB data disk (deployed to `/dev/sdb`)
+- 3 network interfaces for management, storage, and compute traffic (set to `eth0`, `eth1`, and `eth2`, respectively, in this example. Your environment may differ.)
+
+NOTE
+
+250 GB data disks used in this example are simply for demonstration purposes. A typical test cluster should consist of at least 500 GB storage and more will be required for production. Do not raid disks on physical servers. Multiple disks may be specified per host by giving a comma-separated list (ex. /dev/sda,/dev/sdb,/dev/sdc,etc.) in the DATA DEVICE field during cluster setup. These along with disks from all other nodes will be added to the total storage, which is presented as one large volume.
+
+HVM clusters must also live in Private Cloud-type Clouds (See Infrastructure > Clouds). A pre-existing Cloud may be used or a new Cloud could be created to house HVM clusters.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json b/corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
new file mode 100644
index 0000000..f2fb6b9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+  "title": "Directory Pools Overview",
+  "ordinal": 113,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.html",
+  "topic_cluster": {
+    "clustering_title": "Directory Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+        "clustering_title": "Directory Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+        "clustering_title": "Directory Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md b/corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
new file mode 100644
index 0000000..58e01a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
@@ -0,0 +1,11 @@
+# Directory Pools Overview
+
+Directory Pools allow designation of a directory on the local host filesystem as a datastore. By default on creation of the HVM cluster, three Directory Pools are automatically created which helps ensure HVM can work straight out of the box even without other integrated storage. The default Directory Pools are:
+
+- `local` at `/var/morpheus/kvm/local` for storage of virtual disks for VMs
+- `morpheus-cloud-init` at `/var/morpheus/kvm/cloud-init` for storage of ephemeral clout-init ISOs
+- `morpheus-images` at `/var/morpheus/kvm/images` for storage of virtual images
+
+TIP
+
+Of these default Directory Pools, only the `local` pool is selectable as a provisioning target for storing virtual disks. Using this Directory Pool runs the risk of filling up the HVM Host filesystem and bringing down the host. For this reason, it may be advisable to edit this datastore and make it inactive. Use an alternative datastore, such as an NFS Pool or GFS Pool (discussed in the upcoming sections) to avoid filling up the local filesystem. The other two default Directory Pools can remain active as they are created for specific purposes and will not be selectable for users as a datastore at provision time.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json b/corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
new file mode 100644
index 0000000..7487ab9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+  "title": "Tasks",
+  "ordinal": 56,
+  "parent_title": "Automation",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html",
+  "topic_cluster": {
+    "clustering_title": "Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md b/corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
new file mode 100644
index 0000000..af3934c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
@@ -0,0 +1,12 @@
+# Tasks
+
+**Subtopics**  
+
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.html)**
+- **[Target Options](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.html)**
+- **[Execute Options](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.html)**
+- **[Source Options](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.html)**
+- **[Allow Custom Config](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.html)**
+- **[Adding Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6B80D87B-8461-414D-9172-07E68896EB06.html)**
+- **[Editing Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.html)**
+- **[Deleting Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json b/corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
new file mode 100644
index 0000000..b41c2b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+  "title": "To add a VM Essentials Network Pool",
+  "ordinal": 155,
+  "parent_title": "IP Pools",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.html",
+  "topic_cluster": {
+    "clustering_title": "To add a VM Essentials Network Pool",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+        "clustering_title": "To add a VM Essentials Network Pool"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+        "clustering_title": "To add a VM Essentials Network Pool"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md b/corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
new file mode 100644
index 0000000..3e4e7b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
@@ -0,0 +1,26 @@
+# To add a VM Essentials Network Pool
+
+## Procedure
+
+1. Click + ADD in Infrastructure  >  Network  >  IP Pools
+2. Enter the following:
+   :   Name
+       :   A friendly name for the IP Pool in VM Essentials.
+
+       Pool Type
+       :   Currently, HVM-type IP Pools and NSX IP Pools (with a configured integration) can be created directly from VM Essentials
+
+       Starting Address
+       :   The starting IP address of the IP Pool address range. ex: 192.168.0.2
+
+       Ending Address:
+       :   The ending IP address of the IP Pool address range. ex: 192.168.0.255
+3. Save Changes
+
+## Results
+
+NOTE
+
+Multiple Address Ranges can be added to a pool by selecting the + icon next to the address range.
+
+After saving the IP pool will be available for assignment to networks in the NETWORK POOL dropdown when adding or editing a network.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json b/corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
new file mode 100644
index 0000000..c93e4f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+  "title": "Adding NFS Pools",
+  "ordinal": 116,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.html",
+  "topic_cluster": {
+    "clustering_title": "Adding NFS Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+        "clustering_title": "Adding NFS Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+        "clustering_title": "Adding NFS Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md b/corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
new file mode 100644
index 0000000..0afef44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
@@ -0,0 +1,21 @@
+# Adding NFS Pools
+
+Before adding an NFS Pool, ensure your NFS target is configured as described in the previous section. With configuration complete, follow the steps below:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. Click into the Storage tab and then the Data Stores subtab
+4. Click ADD
+5. From the ADD DATA STORE modal, configure the following:
+
+   1. **NAME:** An identifiable name for the datastore in the UI
+   2. **TYPE:** NFS Pool
+   3. **SOURCE HOST:** The NFS server name or IP address
+   4. **SOURCE DIRECTORY:** The path of the exported NFS share
+   5. **VERSION:** Either 3 or 4 depending on the NFS version running on the source server
+   6. **IMAGE TARGET:** Marked if this datastore should be used as a storage location for virtual images
+6. Click Save
+
+![The add datastore modal for NFS-type datastores](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-D53B7324-222A-4953-9222-824F49846CB0-high.png)
+
+At this point the HVM manager will automatically mount the NFS share on all hosts within the cluster. It will also handle setting various other options such as autostart and management of mountpoint for the share within the host filesystem.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json b/corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
new file mode 100644
index 0000000..a896194
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+  "title": "Additional System Health Indices",
+  "ordinal": 261,
+  "parent_title": "VM Essentials Health",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.html",
+  "topic_cluster": {
+    "clustering_title": "Additional System Health Indices",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+        "clustering_title": "Additional System Health Indices"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+        "clustering_title": "Additional System Health Indices"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md b/corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
new file mode 100644
index 0000000..eb71eb7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
@@ -0,0 +1,106 @@
+# Additional System Health Indices
+
+CPU
+:   - Processor Count
+    - Process Time
+    - Morpheus CPU
+    - System CPU
+    - System Load
+
+MEMORY
+:   - Morpheus Memory
+    - Morpheus Used Memory
+    - Morpheus Free Memory
+    - Morpheus Memory Usage
+    - System Memory
+    - System Used Memory
+    - System Free Memory
+    - System Memory Usage
+    - System Swap
+    - Free Swap
+
+DATABASE
+:   - Lifetime Connections
+    - Aborted Connections
+    - Max Used Connections
+    - Max Connections
+    - Threads Running
+    - Threads Connected
+    - Slow Queries
+    - Temp Tables
+    - Key Reads
+    - Handler Reads
+    - Buffer Pool Free
+    - Open Tables
+    - Table Scans
+    - Full Joins
+    - Key Read Requests
+    - Key Reads
+    - Engine Waits
+    - Lock Waits
+    - Handler Reads
+    - Engine IO Writes
+    - Engine IO Reads
+    - Engine IO Double Writes
+    - Engine Log Writes
+    - Engine Memory
+    - Dictionary Memory
+    - Buffer Pool Size
+    - Free Buffers
+    - Database Pages
+    - Old Pages
+    - Dirty Page Percent
+    - Max Dirty Pages
+    - Pending Reads
+    - Insert Rate
+    - Update Rate
+    - Delete Rate
+    - Read Rate
+    - Buffer Hit Rate
+    - Read Write Ratio
+    - Uptime
+
+ELASTIC
+:   - Status
+    - Cluster
+    - Node Count
+    - Data Nodes
+    - Shards
+    - Primary Shards
+    - Relocating Shards
+    - Initializing
+    - Unassigned
+    - Pending Tasks
+    - Active Shards
+
+NOTE
+
+status is typical for Elasticsearch
+
+Elastic Nodes
+:   - Node
+    - Master
+    - Location
+    - Heap Usage
+    - Memory Usage
+    - CPU Usage
+    - 1M Load
+    - 5M Load
+    - 15M Load
+
+Elastic Indices
+:   - Health
+    - Index
+    - Status
+    - Primary
+    - Replicas
+    - Doc
+    - Count
+    - Primary
+    - Size
+    - Total Size
+
+Queues
+:   - Queue Count
+    - Busy Queues
+    - Error Queues
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json b/corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
new file mode 100644
index 0000000..2aebc25
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+  "title": "VM Essentials Health",
+  "ordinal": 259,
+  "parent_title": "Health",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html",
+  "topic_cluster": {
+    "clustering_title": "VM Essentials Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+        "clustering_title": "VM Essentials Health"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+        "clustering_title": "VM Essentials Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md b/corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
new file mode 100644
index 0000000..d4be1d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
@@ -0,0 +1,15 @@
+# VM Essentials Health
+
+The VM Essentials Health section provides an overview of the health of your VM Essentials appliance. It includes an appliance health summary in the following areas:
+
+- **CPU:** Appliance CPU usage is checked. If usage is greater than 50%, this indicator will be in a yellow or warning state. If VM Essentials is unable to complete the check, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to upgrade to increase CPU. The **Overall** health indicator will mirror the CPU health indicator
+- **Memory:** If swap usage is above 60% or VM Essentials memory usage is above 95%, this indicator will be in a yellow or warning state. If VM Essentials is unable to complete the check for any reason, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to increase swap, upgrade the appliance to add memory, or consider a different appliance architecture for those using single-node appliances
+- **Storage:** If utilization of the filesystem mounted at “/” exceeds 80%, this indicator will be in a yellow warned status. Above 90% will put this indicator in red or error status
+- **Database:** The database is checked. If the number of database connections exceeds the configured maximum number of connections or if any test queries are reported as being slow, this indicator will be in a yellow or warning state. If VM Essentials is unable to communicate with the database, it will be in a red or error state. In the database section further down the page, you can check the number of maximum used connections against the number of max connections. In the case of database connections exceeding the maximum, consider increasing the maximum settings connection
+- **Elastic:** Elasticsearch is polled for the health status of each index. If any indices are not reporting a “green” health status, this indicator will be in a yellow or warning state.
+- **Queues:** RabbitMQ queues are checked. Any queues containing more than 1000 messages are considered to be in an error state. Appliance Queue health is given in a yellow or warning status when any queues are in such an error state. In the Queues section further down the page you can see the individual Queues listed and which have messages piling up. When the appliance is unable to complete the check for any reason, this indicator will be in a red or error state
+
+**Subtopics**  
+
+- **[Health Levels](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.html)**
+- **[Additional System Health Indices](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json b/corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
new file mode 100644
index 0000000..6cefbfb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+  "title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+  "ordinal": 234,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md b/corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
new file mode 100644
index 0000000..8fa4d9d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
@@ -0,0 +1,59 @@
+# Configuring Windows Workloads (Windows 2022 or later) for Migration
+
+Migrating Windows workloads from VMware vCenter Clouds to HVM Clusters using the bulk Migrations feature requires some initial configurations checks. This section goes through an example preparation process for a Windows VM running on vCenter.
+
+This guide makes the following assumptions about the workload to be migrated:
+
+- Configured to boot as EFI or BIOS
+- Virtualization Based Security (VBS) is enabled
+- Secure Boot is enabled
+- Trusted Platform Module (TPM) is disabled
+- The VM has access to the recovery partition (if not, a Windows Recovery Environment disc or installation media may be required to access some of the menus referenced in this section)
+
+Inject VirtIO Drivers
+
+To begin, restart the VMware Windows guest in the [Windows Recovery Environment (Windows RE)](https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b). In Windows RE, choose a keyboard layout if prompted. Then, select the **Troubleshoot** option. From the Troubleshoot menu, select **Command Prompt**.
+
+Within the Command Prompt session, enter **diskpart** using this command: `diskpart`. Check the disks that are available with `list disk`. At this point, you may receive the message that "There are no fixed disks to show." or the disk with Windows OS might not be listed. If that is the case, follow the steps in the next section to mount the drives. If that is not the case, skip to the following section to continue the process of injecting the VirtIO drivers.
+
+![Enter dispart command line tool and list disks](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-6D43B362-18E8-4E21-8CE1-733555398E59-high.png)
+
+Mounting the Drives
+
+From vCenter, mount the VMware Tools installer to the VM using the "Install VMware Tools..." option (**Actions > Guest OS > Install VMware Tools...**). Then, back in diskpart, use the following command to find the CD/DVD-ROM drive letter: `list volume`. Make note of the CD-ROM drive letter, which in the case of this example is drive "D." Exit diskpart with the `exit` command.
+
+![listing volumes in diskpart](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-E8FB0956-0BE4-4600-ACC9-DD48E590F2CE-high.png)
+
+Enter the following command to load the storage drivers which will enable you to see the hard disks: `drvload "D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64\pvscsi.inf"`. Note that the prior command references Windows 10 as the operating system but choose the most appropriate or the latest available. It also references drive "D" which may vary from case to case.
+
+With the driver loaded, once again confirm the disks are mounted with `diskpart` and `list disk`. They're now mounted but the partitions/volumes need drive letters so, while still in diskpart, list the volumes with: `list volume`. In this example case, "Volume 1" is the primary Windows volume. Select the volume and assign a drive letter, in the example case the assigned letter will be "C": `select volume 1` and `assign letter=c`. Check your work by listing the volumes again, the primary Windows volume should be assigned the correct drive letter: `list volume`.
+
+![Assigning a drive letter to a volume](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-8506AA86-13D4-4086-B361-5C5AB0CFC5E9-high.png)
+
+Exit diskpart once again (`exit`) and unmount the VMware Tools installer from the VM back in the vCenter console (**Actions > Guest OS > Unmount VMware Tools Installer**).
+
+Inject VirtIO drivers (cont.)
+
+Download the [latest](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) or [stable](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/) VirtIO drivers ISO to your local workstation. The latest is recommended but often they are the same. Add the ISO to vCenter either by uploading it to a datastore or to the Content Library. Still in vCenter, mount the ISO using a CD-ROM device on the VM and make sure it's connected. Enter the following commands to inject the VirtIO storage drivers into the Windows boot-start drivers from the mounted ISO: `dism /image:C:\ /add-driver:D:\viostor\2k22\amd64\viostor.inf` and `dism /image:C:\ /add-driver:D:\vioscsi\2k22\amd64\vioscsi.inf`. Note once again that the OS volume will not be assigned the "C" drive letter and the CD-ROM device will not be assigned the "D" drive letter in every case. Similarly, in this example "2k22" is used but that won't be appropriate in every case. If successful, a message will be received that the driver packages were successfully installed. Close the Command Prompt window and click **Continue** to boot Windows once again.
+
+![installing viostor.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-A481A334-59CE-42D9-857D-0B5FDEE31BAB-high.png)![installing vioscsi.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-10CEA2F9-9885-464E-A57B-303AC913FBBD-high.png)
+
+Prepare the OS
+
+Once logged back in, install the VirtIO drivers in the OS using the ISO, which is still mounted, by navigating to the CD-ROM/DVD-ROM drive. Install `virtio-win-gt-x64.msi` and `virtio-win-guest-tools.exe` from the root of the ISO. Maintain all default selections during the installation. Next, unmount any ISOs still attached to the VM, either by ejecting in Windows or by setting the CD-ROM drive to "Client Device" in vCenter.
+
+Now, shut down the VM. Keep in mind that the VMware Cloud integration may be configured to automatically maintain power state of associated VMs. Navigate to Infrastructure > Clouds and edit the Cloud. Make note of the "AUTOMATICALLY POWER ON VMS" configuration. If checked, you will need to shut down the VM via the product UI tools rather than from the vCenter console or from within the guest OS. Alternatively, you could uncheck "AUTOMATICALLY POWER ON VMS", save changes to the Cloud, and then power down the VM from vCenter or from the guest OS but bear in mind changing this configuration would affect all VMs associated with the Cloud in the product.
+
+Migrating
+
+This completes the preparation steps. From here, create a new Migration Plan that includes the prepared VM and run it. Take a look at the previous section for more information on creating and running Migration Plans.
+
+Post-Conversion
+
+As a final note, bear in mind that the migration tool does not uninstall VMware Tools following conversion, which can lead to start-up errors being surfaced in migrated VMs. In some cases, the VMware Tools installation may become corrupted which prevents simply uninstalling using the Control Panel.
+
+To prevent VMware Tools from executing at startup, within the Windows guest navigate to Settings > Apps > Startup and turn off VMware Tools Core Service. See the example screenshot below for a Windows 2022 Guest.
+
+![Turning off VMware Tools Core Service at Windows guest startup](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-EEC38EAD-A903-41BD-8C98-BACAC114BA0E-high.png)
+
+Additionally, you can attempt to uninstall VMware Tools completely using Microsoft recommended processes and tooling for uninstalling stuck programs. See [this article](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d) from the Microsoft Support for procedure and links to a helpful tool.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json b/corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
new file mode 100644
index 0000000..787b260
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+  "title": "Task Types",
+  "ordinal": 64,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.html",
+  "topic_cluster": {
+    "clustering_title": "Task Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+        "clustering_title": "Task Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+        "clustering_title": "Task Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md b/corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
new file mode 100644
index 0000000..7784855
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
@@ -0,0 +1,9 @@
+# Task Types
+
+Available Task Types
+
+         |  | Task Type | Task Description | Source Options | Execute Target Options | Configuration Requirements | Role Permissions Requirements |
+| --- | --- | --- | --- | --- | --- | --- |
+| powershell | PowerShell Script | Execute PowerShell Script on the Target Resource | Local, Repository, Url | Remote, Resource, Local | None | Library: Tasks |
+| restart | Restart | Restarts target VM/Host/Container and confirms startup status before executing next task in Workflow | System | Resource | None | Library: Tasks |
+| shellscript | Shell Script | Executes Bash script on the target resource | Local, Repository, Url | Local, Remote, Resource | None | Library: Tasks |
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json b/corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
new file mode 100644
index 0000000..4343633
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+  "title": "Existing Instances",
+  "ordinal": 318,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.html",
+  "topic_cluster": {
+    "clustering_title": "Existing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+        "clustering_title": "Existing Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+        "clustering_title": "Existing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md b/corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
new file mode 100644
index 0000000..b8a8b9a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
@@ -0,0 +1,11 @@
+# Existing Instances
+
+VM Essentials provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into VM Essentials. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, VM Essentials will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json b/corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
new file mode 100644
index 0000000..cd70097
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+  "title": "Configuring HPE Morpheus Enterprise Appliance Backup",
+  "ordinal": 310,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D647F00D-6B45-4E18-B442-14835847EFA7.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+        "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+        "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md b/corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
new file mode 100644
index 0000000..9f20e4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
@@ -0,0 +1,23 @@
+# Configuring HPE Morpheus Enterprise Appliance Backup
+
+## About this task
+
+With the groundwork laid in the previous sections, we’re ready to enable and configure HPE Morpheus Enterprise appliance backup.
+
+## Procedure
+
+1. Navigate to Administration > Settings > Backups
+2. Slide the switch labeled “Backup Appliance”
+3. Click SAVE
+
+## Results
+
+On saving this change, a text link labeled “Backup” will be activated which will take you directly to the automatically-generated appliance backup job. Click this link to continue.
+
+1. Click the EDIT button
+2. Enter a name for the appliance backup job if you wish to change it from the default
+3. Select the appropriate storage bucket or file share
+4. Choose a pre-created backup job. If you do not have an existing backup job that fits, a retention count and schedule can be manually created in this modal. If you manually configure retention counts and schedules in addition to associating a Job, the Job values will override any manual settings.
+5. Click SAVE CHANGES
+
+At this point, your appliance will be automatically backed up on the schedule you chose and stored in the selected location. An appliance backup will store backup copies of the appliance MySQL database. Should you need to restore or migrate your database from backup, follow the steps in the next section of this guide.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json b/corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
new file mode 100644
index 0000000..42ba7c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+  "title": "Upgrade License Key",
+  "ordinal": 292,
+  "parent_title": "License",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrade License Key",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+        "clustering_title": "Upgrade License Key"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+        "clustering_title": "Upgrade License Key"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md b/corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
new file mode 100644
index 0000000..f5d10b4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
@@ -0,0 +1,14 @@
+# Upgrade License Key
+
+## About this task
+
+To add a new or update an existing License:
+
+## Procedure
+
+1. Copy the license key into the large text area at the bottom of the page
+2. Click UPDATE
+
+## Results
+
+If valid, the new License will be applied. Note that the new license may replace an existing license or may stack onto an existing license.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json b/corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
new file mode 100644
index 0000000..4185fe2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+  "title": "Overview",
+  "ordinal": 166,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md b/corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
new file mode 100644
index 0000000..61dbeb6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
@@ -0,0 +1,5 @@
+# Overview
+
+In many situations, organizations deploy virtual machines in proxy restricted environments for things such as PCI Compliance, or just general security. As a result of this VM Essentials provides out of the box support for proxy connectivity. Proxy authentication support is also provided with both Basic Authentication capabilities as well as NTLM for Windows Proxy environments. VM Essentials is even able to configure virtual machines it provisions to utilize these proxies by setting up the operating systems proxy settings directly (restricted to cloud-init based Linux platforms for now, but can also be done on windows based platforms in a different manner).
+
+To get started with Proxies, it may first be important to configure the VM Essentials appliance itself to have access to proxy communication for downloading service catalog images. To configure this, visit the Administration > Settings page where a section labeled “Proxy Settings” is located. Fill in the relevant connection info needed to utilize the proxy. It may also be advised to ensure that the Linux environment’s `http_proxy`, `https_proxy`, and no\_proxy are set appropriately.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json b/corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
new file mode 100644
index 0000000..464ff4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+  "title": "Storage",
+  "ordinal": 363,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md b/corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
new file mode 100644
index 0000000..70c11f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
@@ -0,0 +1,5 @@
+# Storage
+
+**Subtopics**  
+
+- **[HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json b/corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
new file mode 100644
index 0000000..bc5cc95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+  "title": "Provisioning with Proxies",
+  "ordinal": 169,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning with Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+        "clustering_title": "Provisioning with Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+        "clustering_title": "Provisioning with Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md b/corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
new file mode 100644
index 0000000..ef3dff8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
@@ -0,0 +1,5 @@
+# Provisioning with Proxies
+
+Proxy configurations can vary from operating system to operating system and in some cases it is necessary for these to be configured in the blueprint as a prerequisite. In other cases it can also be configured automatically. Mostly with the use of cloud-init (which all of our out of the box service catalog utilizes on all clouds). When editing/creating a cloud there is a setting for “Provisioning Proxy” in “Provisioning Options”. If this proxy is set, VM Essentials will automatically apply these proxy settings to the guest operating system.
+
+Overriding proxy settings can also be done on the Network record. Networks (or subnets) can be configured in Infrastructure  >  Networks or on the Networks tab of the relevant Cloud detail page. Here, a proxy can also be assigned as well as additional options like the No Proxy rules for proxy exceptions.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json b/corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
new file mode 100644
index 0000000..83357da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+  "title": "Initial Backups Setup",
+  "ordinal": 204,
+  "parent_title": "Backups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.html",
+  "topic_cluster": {
+    "clustering_title": "Initial Backups Setup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+        "clustering_title": "Initial Backups Setup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+        "clustering_title": "Initial Backups Setup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md b/corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
new file mode 100644
index 0000000..b12f1fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
@@ -0,0 +1,8 @@
+# Initial Backups Setup
+
+Global Backup settings (Administration > Settings > Backups), Storage Providers (Infrastructure > Storage) and Execution Schedules (Library > Automation > Execute Scheduling) should be configured prior to creating backups. Global backup settings are where scheduled backups can be globally enabled or disabled and certain global backup default settings can be configured. Storage providers include local and remote configured storage locations that can be used as backup targets. Execution schedules are timed intervals at which individual automated backup jobs will run. See the next two sections for full details on global backup settings and configuring execution schedules. See VM Essentials UI [storage documentation](https://docs.morpheusdata.com/en/latest/infrastructure/storage/storage.html) for more information about configuring local and remote storage targets and/or integrating with third party storage providers.
+
+**Subtopics**  
+
+- **[Global Backups Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html)**
+- **[Execution Schedules](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json b/corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
new file mode 100644
index 0000000..490928f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+  "title": "Configuring Virtual Images",
+  "ordinal": 72,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md b/corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
new file mode 100644
index 0000000..293f4e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
@@ -0,0 +1,6 @@
+# Configuring Virtual Images
+
+**Subtopics**  
+
+- **[System Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-6549D43B-D0BB-4416-9771-AF11F387B629.html)**
+- **[User Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json b/corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
new file mode 100644
index 0000000..2aa2411
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+  "title": "Alarms (dashboard)",
+  "ordinal": 10,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.html",
+  "topic_cluster": {
+    "clustering_title": "Alarms (dashboard)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+        "clustering_title": "Alarms (dashboard)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+        "clustering_title": "Alarms (dashboard)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md b/corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
new file mode 100644
index 0000000..47a8563
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
@@ -0,0 +1,3 @@
+# Alarms (dashboard)
+
+The most recent five Alarms are displayed here and the user may link through to the resource which triggered the Alarm. For the complete list of Alarms and more information on each Alarm navigate to Operations > Activity > Alarms
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json b/corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
new file mode 100644
index 0000000..718fda5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+  "title": "Viewing and Assigning Hardware Devices",
+  "ordinal": 133,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing and Assigning Hardware Devices",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md b/corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
new file mode 100644
index 0000000..d28ff12
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
@@ -0,0 +1,23 @@
+# Viewing and Assigning Hardware Devices
+
+Hardware Devices are surfaced at the Host detail level and the VM (server) detail level through a Devices tab. The Host detail will show all attached hardware devices and their current status: Attached (to the host), detached (from the host), or assigned (to a VM). The VM detail will show only hardware devices currently attached to that VM. To begin consuming hardware devices with HVM Cluster VMs, look again at the list in the Devices tab on the Host detail page. Detach a piece of hardware from the host using the ACTIONS dropdown for that piece of hardware. As shown in the screenshot below, DETACH DEVICE is selected for a USB device.
+
+![../../_images/detachDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-A94BDC5A-C89C-426E-9EF6-2914BC84AC21-high.png)
+
+Once detached, the status of the device is changed to “Detached” (see screenshot below) and the device is available for consumption by VMs running on this host.
+
+![../../_images/deviceDetached.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-34E14A70-071B-4A63-BD76-5D0A1261BC20-high.png)
+
+To assign the hardware to a specific VM, click the ACTIONS dropdown once again for the now-detached hardware. Now, click ASSIGN DEVICE.
+
+![../../_images/assignDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-443A34ED-8373-4AB9-9F26-730FF70DDD3C-high.png)
+
+Within the ASSIGN DEVICE modal that will appear, select the server for device assignment and click EXECUTE.
+
+![../../_images/assignToServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-F76B03BD-5880-4AC2-8B3D-98537D873BDE-high.png)
+
+The icon and status for the device in the hardware list has now changed to “Assigned.” If we then open a console session with this VM, we can see the USB device is assigned successfully and is usable by the guest OS.
+
+![../../_images/vmConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-C1FCF142-72C3-4E92-9EBB-6277EC6DD1AA-high.png)
+
+The same process can be used to detach and assign GPU or NVME devices.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json b/corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
new file mode 100644
index 0000000..2a15f08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+  "title": "User Settings",
+  "ordinal": 254,
+  "parent_title": "Users",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md b/corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
new file mode 100644
index 0000000..e5ee51f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
@@ -0,0 +1,3 @@
+# User Settings
+
+Additional settings for a User can be found in the User Settings section, including a user photo, API access, two-factor authentication settings, default Groups and Clouds, and more. User Settings is accessed by clicking on the name of the User in the upper-right corner of the application window and selecting “User Settings.” See the dedicated section on User Settings elsewhere in this documentation for a more in-depth description of User Settings.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json b/corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
new file mode 100644
index 0000000..d0e4ff3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+  "title": "Monitoring the Cluster",
+  "ordinal": 121,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md b/corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
new file mode 100644
index 0000000..60a329b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
@@ -0,0 +1,13 @@
+# Monitoring the Cluster
+
+With the server provisioned and a workload running, take a look at the monitoring and actions capabilities on the cluster detail page (Infrastructure > Clusters, then click on the new HVM cluster). View cluster performance and resource usage (Summary and Monitoring tabs), drill into individual hosts (Hosts tab), see individual workloads (VMs tab), and more.
+
+**Subtopics**  
+
+- **[Moving Workloads Between Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.html)**
+- **[Adding hosts](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.html)**
+- **[Maintenance Mode](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html)**
+- **[vCPU Placement](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html)**
+- **[Failover](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.html)**
+- **[Adding an NFS Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json b/corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
new file mode 100644
index 0000000..4e67b04
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+  "title": "Email Settings",
+  "ordinal": 268,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.html",
+  "topic_cluster": {
+    "clustering_title": "Email Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+        "clustering_title": "Email Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+        "clustering_title": "Email Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md b/corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
new file mode 100644
index 0000000..11fefe0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
@@ -0,0 +1,23 @@
+# Email Settings
+
+In this section, you can configure an SMTP server for email notification delivery. You will need to provide VM Essentials the following information, your mail server systems administrator can assist you in filling these fields and with the preferred encryption method.
+
+- From Address
+- SMTP Server
+- SMTP Port
+- SSL Enabled
+- TLS Encryption
+- SMTP User
+- SMTP Password
+
+We recommend that you add the VM Essentials server to your SMTP whitelist as well as using user authentication as an additional security measure.
+
+Once you have added your SMTP server information into VM Essentials, scroll down to the bottom of the page and press the blue SAVE button which can be found under the Enabled Clouds section.
+
+When you have saved your SMTP server settings in the VM Essentials appliance you will then need to restart the UI. To restart the morpheus-ui, connect to your VM Essentials server via SSH and run the below command:
+
+`sudo morpheus-ctl restart morpheus-ui`
+
+IMPORTANT
+
+If you do not restart morpheus-ui, the notifications will not be sent. Please note it can take up to three minutes for the UI to become reachable again.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json b/corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
new file mode 100644
index 0000000..8ad1661
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+  "title": "Provisioning",
+  "ordinal": 275,
+  "parent_title": "Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md b/corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
new file mode 100644
index 0000000..3c6af1a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
@@ -0,0 +1,11 @@
+# Provisioning
+
+**Subtopics**  
+
+- **[Provisioning Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.html)**
+- **[Cloud-Init Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3D27BE17-47C9-476C-AD13-DD516697F862.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.html)**
+- **[Library Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.html)**
+- **[PXE Boot Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-B94BC2CB-8504-41C6-8848-512529EEE941.html)**
+- **[App Blueprint Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.html)**
+- **[Terraform Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json b/corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
new file mode 100644
index 0000000..d6e38e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+  "title": "HPE Aruba CX DSS",
+  "ordinal": 355,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Aruba CX DSS",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md b/corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
new file mode 100644
index 0000000..7c2234d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
@@ -0,0 +1,11 @@
+# HPE Aruba CX DSS
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.html)**
+- **[Adding HPE Aruba CX DSS Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.html)**
+- **[Create HPE ANW DSS Port Group Network](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.html)**
+- **[Delete HPE ANW DSS Port Group Network](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.html)**
+- **[View HPE Aruba CX DSS Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json b/corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
new file mode 100644
index 0000000..194d91d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+  "title": "vCPU Placement",
+  "ordinal": 126,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html",
+  "topic_cluster": {
+    "clustering_title": "vCPU Placement",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md b/corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
new file mode 100644
index 0000000..045999e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
@@ -0,0 +1,28 @@
+# vCPU Placement
+
+vCPU placement settings relate to vCPU placement within the physical topology of the CPU. Since a vCPU is just a schedulable thread the hypervisor maps onto physical cores, we can create performance increases through smart scheduling. A simplified CPU topology might look something like this:
+
+```
+```
+Socket  
+ └── NUMA node  
+     └── Core  
+         └── Threads (SMT / Hyper-Threading)
+```
+```
+
+As you can see from the diagram above, multiple physical cores can reside within the same NUMA node. Physical CPU cores within the same NUMA node share the same region of the L3 cache and local memory access. By scheduling vCPUs making up a single VM to cores within the same NUMA node, we can avoid the performance penalties associated with crossing NUMA boundaries and accessing remote memory locations.
+
+HVM Clusters offer three vCPU placement settings. The default setting is **Unmanaged**. Clusters with unmanaged vCPU placement will make no special effort to schedule vCPUs within the same NUMA region. Next is **Region**. Clusters with this vCPU placement will attempt to schedule vCPUs associated with the same VM within the same NUMA region. When flexibility is needed, vCPUs may hop to different physical cores but they will be kept within the same NUMA region. Third is **Pinned**. Clusters with this vCPU placement will also attempt to schedule vCPUS associated with the same VM within the same NUMA region but the vCPUs will remain pinned to same cores. In certain cases, pinning may improve performance and in other cases creating inflexibility may introduce inefficiency.
+
+TIP
+
+Setting **Region** placement is a sensible starting configuration if you don't have a specific reason to choose one of the other two. In internal testing, a 7-10% improvement in prime number generation time was observed with Region pinning versus Unmanaged pinning.
+
+How to Configure vCPU Placement Settings
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. From the Cluster detail page, click Edit
+4. Within the vCPU Placement field, select the desired value. See the paragraphs above for a description of each configuration
+5. Click Save changes
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json b/corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
new file mode 100644
index 0000000..ac4c250
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+  "title": "Utilities",
+  "ordinal": 293,
+  "parent_title": "Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.html",
+  "topic_cluster": {
+    "clustering_title": "Utilities",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+        "clustering_title": "Utilities"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+        "clustering_title": "Utilities"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md b/corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
new file mode 100644
index 0000000..84b2aac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
@@ -0,0 +1,16 @@
+# Utilities
+
+System administrators have access to a utilities panel with the following options:
+
+- **Reindex all searchable data:** Execute
+- **Toggle Maintenance Mode:** Enable
+
+NOTE
+
+Maintenance mode cleanly places VM Essentials into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting VM Essentials UI disables maintenance mode.
+
+NOTE
+
+When using VM Essentials in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
+
+A VM Essentials node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json b/corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
new file mode 100644
index 0000000..b9425db
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+  "title": "Generate Key Pair",
+  "ordinal": 199,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.html",
+  "topic_cluster": {
+    "clustering_title": "Generate Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+        "clustering_title": "Generate Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+        "clustering_title": "Generate Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md b/corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
new file mode 100644
index 0000000..5f86685
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
@@ -0,0 +1,17 @@
+# Generate Key Pair
+
+## About this task
+
+To generate a Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. After naming the new key pair, VM Essentials will reveal both the public and private key
+
+## Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json b/corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
new file mode 100644
index 0000000..2d365f4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+  "title": "History",
+  "ordinal": 25,
+  "parent_title": "Activity",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html",
+  "topic_cluster": {
+    "clustering_title": "History",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+        "clustering_title": "History"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+        "clustering_title": "History"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md b/corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
new file mode 100644
index 0000000..bf45107
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
@@ -0,0 +1,15 @@
+# History
+
+The HISTORY section shows process history from Instance processes. This is an aggregate view of the `History` tab contained in each Instance detail page.
+
+![History](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-DE8D2A86-CAB3-4D94-9D4C-83C5FA49585A-high.png)
+
+Processes can be expanded to view all process steps and process history detail including output and errors.
+
+Access to HISTORY is given by the `Operations:Activity` Role permission.
+
+The Logs displayed in Administration > Health > Morpheus Logs are from `/var/log/morpheus/morpheus-ui/current`. These logs show all ui activity and are useful for troubleshooting and auditing.
+
+NOTE
+
+Stack traces in Administration > Health > Morpheus Logs are filtered for VM Essentials services. Complete stack traces can be found in `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json b/corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
new file mode 100644
index 0000000..2668ded
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+  "title": "Key Pairs",
+  "ordinal": 201,
+  "parent_title": "Trust",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html",
+  "topic_cluster": {
+    "clustering_title": "Key Pairs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md b/corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
new file mode 100644
index 0000000..bc9221d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
@@ -0,0 +1,20 @@
+# Key Pairs
+
+The key pairs section enables the following actions: Add and Delete key pairs. Key pairs are commonly used by HPE Morpheus VM Essentials for accessing instances via SSH. HPE Morpheus VM Essentials stores key pairs to simplify administration and access across both private and public clouds.
+
+HPE Morpheus VM Essentials only accepts key pairs in PEM format (for example, a private key beginning with `-----BEGIN RSA PRIVATE KEY-----`) and accepts RSA (PKCS#1 or PKCS#8, default), DSA (PKCS#1 or PKCS#8), EC (PKCS#8), and ed25519 (PKCS#8) keys. If you have a key in another format, such as OpenSSH, convert the key:
+
+```
+```
+#No passphrase  
+ssh-keygen -m pem -f /path/to/key  
+#With passphrase  
+ssh-keygen -p -P "old passphrase" -N "new passphrase" -m pem -f path/to/key
+```
+```
+
+**Subtopics**  
+
+- **[Add Existing Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C_2.html)**
+- **[Generate Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.html)**
+- **[Delete Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1_2.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json b/corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
new file mode 100644
index 0000000..b0ab40d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+  "title": "Create Instance",
+  "ordinal": 368,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html",
+  "topic_cluster": {
+    "clustering_title": "Create Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+        "clustering_title": "Create Instance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+        "clustering_title": "Create Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md b/corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
new file mode 100644
index 0000000..f643d31
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
@@ -0,0 +1,64 @@
+# Create Instance
+
+## About this task
+
+Create an Instance with the Datastore.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances
+2. In the Instances tab, Click the + ADD button
+3. From the ADD INSTANCE wizard input the following: 
+
+   - From the TYPE section: Select “HVM”
+   - Click NEXT
+
+     ![../../_images/create-instance-type.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-55F890E0-47C6-4621-9A97-C399B1AD1BB0-high.png)
+   - From the GROUP tab, input the following:
+
+     GROUP:
+     :   Select the Group for the Instance
+
+     CLOUD:
+     :   Select the Cloud for the Instance
+
+     NAME:
+     :   Name for the Instance in VM Essentials
+   - Click NEXT
+
+     ![../../_images/create-instance-group.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-4EEB766E-54E0-4C82-A60B-59AE6B75D705-high.png)
+   - From the CONFIGURE tab, input the following:
+
+     LAYOUT:
+     :   Select the Layout for the Instance
+
+     PLAN:
+     :   Select the Plan for the Instance
+
+     RESOURCE POOL:
+     :   Select the Resource Pool (Cluster) for the Instance
+
+     VOLUMES:
+     :   Add one or more Volumes to the Instance. Select the datastore created in the previous section
+
+     NETWORK:
+     :   Add Networks to the Instance
+
+     IMAGE:
+     :   Select the Image for the Instance
+
+     HOST:
+     :   Select the cluster host for the Instance
+
+     Other configurations may be added as needed.
+
+     ![../../_images/create-instance-configure.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-358491C6-43F7-4197-9F53-94D50A1E99F1-high.png)
+   - Click NEXT
+   - Add Automation Tasks, if needed
+   - Click NEXT
+   - Review the Instance configuration
+   - Click COMPLETE![../../_images/create-instance-review.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-22C7AB89-6966-4E4D-8514-6A2FAD489B61-high.png)
+
+## Results
+
+The Instance is now provisioned to the new datastore and is viewable within the Instances (Provisioning > Instances) section.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json b/corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
new file mode 100644
index 0000000..66d0b3a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+  "title": "Overview",
+  "ordinal": 138,
+  "parent_title": "Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md b/corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
new file mode 100644
index 0000000..034629a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
@@ -0,0 +1,5 @@
+# Overview
+
+The Networks section is for configuring networks across all Clouds in VM Essentials. Existing networks from Clouds added in VM Essentials will auto-populate in the Networks section.
+
+Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, VM Essentials allows administrators to restrict management of VM Essentials-created Networks through Role permissions.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json b/corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
new file mode 100644
index 0000000..013562c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+  "title": "User Management Settings",
+  "ordinal": 267,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.html",
+  "topic_cluster": {
+    "clustering_title": "User Management Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+        "clustering_title": "User Management Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+        "clustering_title": "User Management Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md b/corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
new file mode 100644
index 0000000..acf2b22
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
@@ -0,0 +1,31 @@
+# User Management Settings
+
+Min Password Length
+:   User passwords must at least be as many characters in length as the entered value
+
+Min Password Uppercase
+:   User passwords must include at least as many uppercase characters as the entered value
+
+Min Password Numbers
+:   User passwords must include at least as many numerals as the entered value
+
+Min Password Symbols
+:   User passwords must include at least as many special characters as the entered value
+
+Session Expires (Minutes)
+:   A user session is forcibly logged out after the entered number of minutes of inactivity
+
+Session Warning (Minutes)
+:   A pop-up warning is shown to the user when they have been inactive for the number of minutes entered. Example: If sessions are set to expire after 90 minutes, warn the user after 60 minutes if you intend to provide 30 minutes advance warning
+
+Expire Password After (Days)
+:   User account passwords will expire after the entered number of days. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User After Attempts (Number of Attempts)
+:   Disable a User account after a specified number of failed login attempts. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User If Inactive For (Days)
+:   Disable a User account if inactive for the entered number of days. The User will not be able to log into the appliance again until another User with sufficient rights enables the account. Enter 0 or leave the field empty to opt out of this feature.
+
+Send warning email before deactivating (Days)
+:   Enter the number of days prior to account deactivation that a warning email should be sent. For example, enter “5” to warn the User when they are five days short of the deactivation time entered in the prior field. Enter 0 or leave the field empty to opt out of this feature.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json b/corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
new file mode 100644
index 0000000..6d0d4e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+  "title": "Amazon S3 Buckets",
+  "ordinal": 179,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.html",
+  "topic_cluster": {
+    "clustering_title": "Amazon S3 Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+        "clustering_title": "Amazon S3 Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+        "clustering_title": "Amazon S3 Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md b/corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
new file mode 100644
index 0000000..2308261
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
@@ -0,0 +1,77 @@
+# Amazon S3 Buckets
+
+## About this task
+
+To Add an Amazon S3 Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Amazon S3 from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   ACCESS KEY
+   :   AWS IAM Access Key
+
+   SECRET KEY
+   :   AWS IAM Secret Key
+
+   BUCKET NAME
+   :   Enter existing S3 Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   CREATE BUCKET
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created. If enabled, select an AWS Region to create the Bucket in.
+
+   ENDPOINT URL
+   :   Optional endpoint URL if pointing to an object store other than amazon that mimics the Amazon S3 APIs.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json b/corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
new file mode 100644
index 0000000..6ff1b52
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+  "title": "Favorites",
+  "ordinal": 9,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.html",
+  "topic_cluster": {
+    "clustering_title": "Favorites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+        "clustering_title": "Favorites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+        "clustering_title": "Favorites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md b/corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
new file mode 100644
index 0000000..0baa217
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
@@ -0,0 +1,3 @@
+# Favorites
+
+Any Instances you’ve “favorited” will appear here along with the Instance name, type, and IP address
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json b/corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
new file mode 100644
index 0000000..a4a205f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+  "title": "Integrate a Bucket or File Share",
+  "ordinal": 309,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.html",
+  "topic_cluster": {
+    "clustering_title": "Integrate a Bucket or File Share",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+        "clustering_title": "Integrate a Bucket or File Share"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+        "clustering_title": "Integrate a Bucket or File Share"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md b/corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
new file mode 100644
index 0000000..8065438
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
@@ -0,0 +1,19 @@
+# Integrate a Bucket or File Share
+
+## About this task
+
+When configuring a HPE Morpheus Enterprise appliance backup, a storage location is selected. If you already have the destination bucket or file share integrated with HPE Morpheus Enterprise, skip to the next section. To integrate a new storage bucket, follow the steps below:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage
+2. Click on the Buckets or File Shares tab depending on your chosen storage type
+3. Click + ADD
+4. Select the appropriate bucket or file share type
+5. Complete the required fields and click SAVE CHANGES
+
+## Results
+
+NOTE
+
+Additional guidance on integrating each of the supported bucket and file share types can be found in [storage](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html) documentation.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json b/corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
new file mode 100644
index 0000000..78e7c6a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+  "title": "Integrations",
+  "ordinal": 255,
+  "parent_title": "Administration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md b/corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
new file mode 100644
index 0000000..41ce8bc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
@@ -0,0 +1,15 @@
+# Integrations
+
+The Integrations allows administrators to manage platform extensions and packages. Using Integrations, you can add, update, and remove plugins and packages to extend the functionality and standardize configurations.
+
+To access the Integrations, click Administration > Integrations.
+
+The Integrations page contains the following tabs:
+
+- Plugins
+- Packages
+
+**Subtopics**  
+
+- **[Plugins](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.html)**
+- **[Packages](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json b/corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
new file mode 100644
index 0000000..b6f2852
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+  "title": "Integrations",
+  "ordinal": 170,
+  "parent_title": "Network",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md b/corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
new file mode 100644
index 0000000..cf9cd67
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
@@ -0,0 +1,6 @@
+# Integrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.html)**
+- **[Scoping Services](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json b/corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
new file mode 100644
index 0000000..4eaca60
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+  "title": "Alarms",
+  "ordinal": 24,
+  "parent_title": "Activity",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html",
+  "topic_cluster": {
+    "clustering_title": "Alarms",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+        "clustering_title": "Alarms"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+        "clustering_title": "Alarms"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md b/corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
new file mode 100644
index 0000000..7c683e5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
@@ -0,0 +1,7 @@
+# Alarms
+
+The Alarms section shows Operation notifications from Cloud and other Service Integrations. Cloud and other Service Integration Alarms are not generated by HPE Morpheus VM Essentials Software but synced and displayed for visibility in HPE Morpheus VM Essentials Software.
+
+For the complete list of Alarms and more information on each Alarm, navigate to Operations > Activity > Alarms.
+
+![Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-444E2530-12E2-439A-A1C7-EED4D7F91D38-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json b/corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
new file mode 100644
index 0000000..81d9810
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+  "title": "Usage",
+  "ordinal": 330,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.html",
+  "topic_cluster": {
+    "clustering_title": "Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+        "clustering_title": "Usage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+        "clustering_title": "Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md b/corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
new file mode 100644
index 0000000..4de7e18
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
@@ -0,0 +1,18 @@
+# Usage
+
+vCenter
+:   - Non-Propagating
+
+Datacenter
+:   - Non-Propagating
+
+Cluster
+:   - Non-Propagating
+
+Host
+:   - Non-Propagating
+
+Datastore/Datastore Cluster
+:   - Propagating
+
+After completing the above steps, all VMware Cloud functionality should be available in VM Essentials without running into permissions errors.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json b/corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
new file mode 100644
index 0000000..506f457
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+  "title": "VM Provision Steps",
+  "ordinal": 28,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html",
+  "topic_cluster": {
+    "clustering_title": "VM Provision Steps",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+        "clustering_title": "VM Provision Steps"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+        "clustering_title": "VM Provision Steps"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md b/corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
new file mode 100644
index 0000000..9ac9fd5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
@@ -0,0 +1,48 @@
+# VM Provision Steps
+
+While many things can happen during an individual provisioning process, the basic order is:
+
+- Look for the Virtual Image
+
+  VM Essentials will check if the Virtual Image set on the Node Type or selected from a list of images during provisioning is already available to the HVM cluster or to a vCenter Cloud target. If not and it is an uploaded or local image, VM Essentials will attempt to upload the image to the HVM cluster or vCenter target.
+
+  **Upload Image**
+
+  For uploaded or local images that do not exist in the target, VM Essentials will need to upload the Image. Ensure the Virtual Image is valid for the target technology, the image meets the target upload requirements, and VM Essentials has network access and permissions to upload the image.
+
+  NOTE
+
+  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+  **Clone Image**
+
+  Once the Image is confirmed available in the target cloud, VM Essentials will clone the Image to the target Datastore.
+
+  NOTE
+
+  The target host must have access to the target Datastore of the Image
+- Reconfigure Image
+
+  Once cloned, VM Essentials will resize the Image based off provisioning parameters
+- Cloud-init (if enabled)
+  :   Attached cloud-init iso
+      :   When using cloud-init, VM Essentials will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.
+
+      VM Tools
+      :   VM Essentials will run guest customizations via VMware VM Tools, including network config when assigning static IP addresses.
+- Wait for Power On status and Network info
+
+  VM Essentials will wait to hear back from the target that the VM has successfully started and has an IP address.
+
+  NOTE
+
+  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, VM Essentials will skip waiting for network.
+- Finalize
+
+  By default, this step will include Agent installation.
+
+  IMPORTANT
+
+  If the VM is stuck in finalize for long periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.
+
+  If agent installation is not possible or is not desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json b/corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
new file mode 100644
index 0000000..9270a5a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+  "title": "Target Options",
+  "ordinal": 59,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.html",
+  "topic_cluster": {
+    "clustering_title": "Target Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+        "clustering_title": "Target Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+        "clustering_title": "Target Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md b/corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
new file mode 100644
index 0000000..e03bb7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
@@ -0,0 +1,7 @@
+# Target Options
+
+When creating a Task, users can select a target to perform the execution. Some Task types allow for any of the three execution targets listed below and some will limit the user to two or just one. The table in the next section lists the available execution targets for each Task type.
+
+- **Resource:** A VM Essentials-managed Instance or server is selected to execute the Task
+- **Local:** The Task is executed by the VM Essentials appliance node
+- **Remote:** The user specifies a remote box which will execute the Task
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json b/corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
new file mode 100644
index 0000000..e9aafc3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+  "title": "Adding hosts",
+  "ordinal": 123,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.html",
+  "topic_cluster": {
+    "clustering_title": "Adding hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+        "clustering_title": "Adding hosts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+        "clustering_title": "Adding hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md b/corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
new file mode 100644
index 0000000..7044493
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
@@ -0,0 +1,11 @@
+# Adding hosts
+
+The process of adding hosts to a pre-existing cluster is very similar to the process of provisioning the cluster initially. The requirements for the new worker node will be identical to the nodes initially added when the cluster was first provisioned. See the earlier sections in this guide for additional details on configuring the worker nodes.
+
+To add the host, begin from the Cluster detail page (selected from the list at Infrastructure > Clusters). From the Cluster detail page, click ACTIONS and select “Add Worker”. Configurations required are the same as those given when the cluster was first created. Refer to the section above on “Provisioning the Cluster” for a detailed description of each configuration.
+
+Once VM Essentials has completed its configuration scripts and joined the new worker node to the cluster, it will appear in a ready state within the Hosts tab of the Cluster detail page. When provisioning workloads to this Cluster in the future, the new node will be selectable as a target host for new Instances. It will also be an available target for managing placement of existing VMs running on the cluster.
+
+NOTE
+
+It’s useful to confirm all scripts related to creating the new host and joining the new host to the cluster completed successfully. To confirm, navigate to the detail page for the new host (Infrastructure > Clusters > Selected Cluster > HostsTab > SelectedHost) and click on the History tab. Confirm all scripts, even those run on the pre-existing hosts, completed successfully as it’s possible the new host was added successfully (green status) but failed in joining the cluster. When such a situation occurs it may appear adding the new host was successful though it will not be possible to provision workloads onto it due to not joining the cluster successfully.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json b/corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
new file mode 100644
index 0000000..0e0ef8f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+  "title": "Overview",
+  "ordinal": 213,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md b/corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
new file mode 100644
index 0000000..a591a1c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
@@ -0,0 +1,7 @@
+# Overview
+
+Cypher at its core is a secure Key/Value store. But what makes Cypher useful is the ability to securely store or generate credentials to connect to your Instances. Not only are these credentials encrypted but by using Cypher you don’t have to burn in connection credentials between Instances into your apps.
+
+Cypher keys can be revoked, either through lease timeouts or manually. So, even if somebody were to gain access to your keys you could revoke access to the keys and generate new ones for your applications.
+
+Keys can have different behaviors depending on the specified mountpoint.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json b/corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
new file mode 100644
index 0000000..512579d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+  "title": "Instance Status",
+  "ordinal": 11,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Status",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+        "clustering_title": "Instance Status"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+        "clustering_title": "Instance Status"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md b/corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
new file mode 100644
index 0000000..a76f11f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
@@ -0,0 +1,3 @@
+# Instance Status
+
+The total number of Instances is listed along with a pie chart showing the statuses of each. Hover over each section of the pie chart to see the total number and percentage of Instances in that state. States may include running, stopped, provisioning, and more
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json b/corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
new file mode 100644
index 0000000..628b469
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+  "title": "OAuth 2.0 Credentials",
+  "ordinal": 197,
+  "parent_title": "Trust",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.html",
+  "topic_cluster": {
+    "clustering_title": "OAuth 2.0 Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+        "clustering_title": "OAuth 2.0 Credentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+        "clustering_title": "OAuth 2.0 Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md b/corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
new file mode 100644
index 0000000..8db04ad
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
@@ -0,0 +1,26 @@
+# OAuth 2.0 Credentials
+
+VM Essentials supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
+
+To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
+
+- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
+- **NAME:** A name for the credential set in VM Essentials
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **GRANT TYPE:** Client Credentials or Password Credentials
+- **ACCESS TOKEN URL:** The authorization server’s token endpoint
+- **CLIENT ID:** The client ID for an app registered with the target service
+- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
+- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
+- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
+- **SCOPE:** The scope of access requested to the target resource
+- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how VM Essentials should issue the token received in requests to the target resource
+
+Once done, click ADD CREDENTIALS.
+
+**Subtopics**  
+
+- **[Add Existing Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.html)**
+- **[Generate Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.html)**
+- **[Delete Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json b/corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
new file mode 100644
index 0000000..e548fbc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+  "title": "Manage Permissions",
+  "ordinal": 192,
+  "parent_title": "Storage",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.html",
+  "topic_cluster": {
+    "clustering_title": "Manage Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+        "clustering_title": "Manage Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+        "clustering_title": "Manage Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md b/corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
new file mode 100644
index 0000000..9ccc833
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
@@ -0,0 +1,13 @@
+# Manage Permissions
+
+From this view, users can manage permissions for any data store synced from integrated Clouds. This includes setting which Groups have access to the data store. To edit data store permissions:
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click ACTIONS > Edit
+- **Groups:** Select “all” Groups or select specific Groups which should have access to the data store
+- **Active:** When marked, the data store is active and available for provisioning
+- Click SAVE CHANGES
+
+**Subtopics**  
+
+- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json b/corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
new file mode 100644
index 0000000..d798a11
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+  "title": "Clouds",
+  "ordinal": 90,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html",
+  "topic_cluster": {
+    "clustering_title": "Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md b/corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
new file mode 100644
index 0000000..90d7017
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
@@ -0,0 +1,8 @@
+# Clouds
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.html)**
+- **[Creating Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.html)**
+- **[Cloud Detail View](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html)**
+- **[Deleting Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json b/corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
new file mode 100644
index 0000000..79ed5ab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+  "title": "Elevating to HPE Morpheus Enterprise",
+  "ordinal": 4,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.html",
+  "topic_cluster": {
+    "clustering_title": "Elevating to HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+        "clustering_title": "Elevating to HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+        "clustering_title": "Elevating to HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md b/corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
new file mode 100644
index 0000000..3669039
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
@@ -0,0 +1,109 @@
+# Elevating to HPE Morpheus Enterprise
+
+This section of the guide goes over the process for upgrading a HPE Morpheus VM Essentials Software appliance to a HPE Morpheus Enterprise Software appliance. HPE Morpheus VM Essentials and HPE Morpheus Enterprise are essentially the same product with HPE Morpheus VM Essentials focused specifically on management and consumption of HVM clusters and HPE Morpheus Enterprise adding on support for many other public and private Cloud types with a richer orchestration and automation experience (in addition to all features included with HPE Morpheus VM Essentials). HPE Morpheus Enterprise requires separate licensing, reach out to your account manager if you’re unsure which licensing entitlements you can access. This guide is intended for HPE Morpheus VM Essentials administrators to upgrade their existing appliances and assumes a level of comfort with the Linux command line and the version upgrade process for HPE Morpheus VM Essentials and/or HPE Morpheus Enterprise. After upgrading, refer to HPE Morpheus Enterprise [documentation](https://www.hpe.com/support/morpheus-enterprise-documentation-latest) for use guides to consuming the full HPE Morpheus Enterprise feature set.
+
+## Prerequisites
+
+- HPE Morpheus VM Essentials manager version 8.0.1+
+- A bucket integrated with HPE Morpheus VM Essentials manager which can house an appliance database backup
+- The HPE Morpheus Enterprise upgrade package (version 8.0.4+)
+- A HPE Morpheus Enterprise license to add following the upgrade to enable the full feature set
+
+## Back Up the Appliance
+
+Start by taking a fresh backup of the appliance database. View the appliance backup job by navigating to Backups > Jobs. As in the screenshot, there should be a backup job named “Morpheus Appliance.” If an appliance backup job is not shown, enable the “Backup Appliance” setting within global settings (Administration > Settings > Backups).
+
+![../_images/upgradeCheckBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-983B614F-468D-405F-8143-085388C6B629-high.png)
+
+Click Run Now and wait for a new green checkmark to appear indicating a new run of the backup job was successful.
+
+## Package Installation
+
+Upgrading the HPE Morpheus VM Essentials manager to a HPE Morpheus Enterprise appliance is as simple as installing the HPE Morpheus Enterprise package over the existing HPE Morpheus VM Essentials package in a process very similar to version upgrades you may have done in the past. First, download the HPE Morpheus Enterprise `.deb` package. The download URL shown below is a placeholder, reach out to your account manager if you’re unsure where to find the download URL for the latest package.
+
+```
+```
+wget https://url.to.morpheus-appliance_x.x.x-x.deb
+```
+```
+
+Next, stop the HPE Morpheus VM Essentials UI.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui
+```
+```
+
+Install the HPE Morpheus Enterprise package and force it to overwrite.
+
+```
+```
+dpkg -i --force-overwrite morpheus-appliance_x.x.x-x.deb
+```
+```
+
+Wait for the installation to complete. There will be warnings about conflicts which may be safely ignored. When installation is complete, you will see a message similar to the screenshot below:
+
+![../_images/upgradeFinishInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-967FDDAE-077D-492D-A9E6-27259A79FCCB-high.png)
+
+Now, remove the HPE Morpheus VM Essentials package.
+
+```
+```
+sudo apt-get remove -y hpe-vm-essentials
+```
+```
+
+Following removal, restart any recommended services if prompted.
+
+![../_images/upgradeRemoveVme.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-DCBE5796-22E4-4207-B179-DD8B37BA91EF-high.png)
+
+We must now clean up OpenSearch directories. Currently, HPE Morpheus Enterprise uses ElasticSearch while HPE Morpheus VM Essentials manager uses OpenSearch. Migration through snapshots is not supported due to this incompatibility. In general, OpenSearch and ElasticSearch contain VM performance metrics. This data can be considered ephemeral and safely deleted as the default retention is only 30 days. HPE Morpheus Enterprise is planned to migrate to OpenSearch in the future and at that point, this cleanup step will not be required and metrics will persist across an upgrade to HPE Morpheus Enterprise. Remove the following directories:
+
+```
+```
+rm -rf /var/run/morpheus/opensearch  
+rm -rf /opt/morpheus/service/opensearch
+```
+```
+
+Next, run the reconfigure command. This will configure ElasticSearch for use with the upgraded appliance.
+
+```
+```
+sudo morpheus-ctl reconfigure
+```
+```
+
+Once the reconfigure is complete, make sure all HPE Morpheus Enterprise services are started
+
+```
+```
+sudo morpheus-ctl status
+```
+```
+
+If any services need started, use the following command:
+
+```
+```
+sudo morpheus-ctl start {service name}
+```
+```
+
+You can watch the logs to see when the UI comes back up:
+
+```
+```
+sudo morpheus-ctl tail morpheus-ui
+```
+```
+
+When the Morpheus ASCII logo appears, you should be able to reach the UI from a web browser.
+
+## Upgrading the License
+
+Now that HPE Morpheus Enterprise UI is reachable, the license must be upgraded. Navigate to Administration > Settings > License where you’ll see a field to paste in your license key. Once again, contact your account manager if you have questions on accessing your license key. Finally, make sure you select the appropriate option of either stacking the license onto an existing license or replacing it. Then, click Update.
+
+At this point, the process is complete. Now that the full Morpheus feature set is unlocked, refer to Morpheus [documentation](https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=1014895562&tab=manuals&cep=on) going forward.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json b/corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
new file mode 100644
index 0000000..2da0ed9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+  "title": "Local Virtual Images",
+  "ordinal": 31,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.html",
+  "topic_cluster": {
+    "clustering_title": "Local Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+        "clustering_title": "Local Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+        "clustering_title": "Local Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md b/corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
new file mode 100644
index 0000000..4188c74
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
@@ -0,0 +1,11 @@
+# Local Virtual Images
+
+A Local Virtual Image means it has been uploaded to VM Essentials. To provision, VM Essentials will need to upload the image to the provisioning target upon first provision.
+
+- Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and VM Essentials has network access and permissions to upload the image.
+
+NOTE
+
+When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+Once a local Virtual Image has been uploaded to a provisioning target, subsequent provisions will use the image local to the target instead of uploading again as long as the copied image is still available.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json b/corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
new file mode 100644
index 0000000..cd4c0f3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+  "title": "Preferences",
+  "ordinal": 301,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html",
+  "topic_cluster": {
+    "clustering_title": "Preferences",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md b/corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
new file mode 100644
index 0000000..7840391
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
@@ -0,0 +1,8 @@
+# Preferences
+
+- **Default Group:** Sets the default Group selection when provisioning
+- **Default Cloud:** Sets the default Cloud selection when provisioning
+- **Default Persona:** Sets the default Persona used when logging in
+- **Default Locale:** Sets the user’s preferred language and region, this setting will override the global locale for the individual user
+
+![../../_images/user_settings_preferences_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-1FDED76C-74B0-4FCA-A922-28AD152EC59A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json b/corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
new file mode 100644
index 0000000..5ad76b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+  "title": "Prerequisites",
+  "ordinal": 358,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md b/corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
new file mode 100644
index 0000000..225d649
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
@@ -0,0 +1,24 @@
+# Prerequisites
+
+The following requirements must be met to deploy and configure the HPE Aruba CX DSS Network plugin in VM Essentials
+
+- Aruba CX 10000 series switches
+
+  - At least two Aruba CX 10000 switches are configured
+  - VSX and KeepAlive are configured
+  - Switches are connected to the upstream network
+- Pre-existing HVM cluster
+
+  - Ensure all hosts within the HVM cluster are physically connected to the CX 10000 switches for optimal network integration and redundancy
+- VM Essentials appliance version 8.0.6 or higher
+
+  - AFC and PSM are deployed and reachable from the VM Essentials manager
+- Aruba Fabric Composer (AFC) version 7.2 or higher, deployed as a VM
+- AMD Pensando PSM (Policy and Services Manager), deployed as a VM
+
+NOTE
+
+- Download AFC and PSM from the [HPE Networking Support portal](https://networkingsupport.hpe.com/downloads/software/RmlsZTo0YzQ2MzIyYS0xOTU2LTExZjAtYTMzNS0yZmRkN2QyMjdhOTY%253D)
+- For more information on deploying AFC and PSM, refer to the official documentation
+- The AFC and PSM must have network connectivity to the CX 10000 switches
+- Making full use of the VM Essentials Aruba CX 10000 integration requires credentials for AFC with API access granted and read/write access to AFC configuration
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json b/corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
new file mode 100644
index 0000000..8d821cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+  "title": "Service Plan Configuration",
+  "ordinal": 242,
+  "parent_title": "Overview",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plan Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+        "clustering_title": "Service Plan Configuration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+        "clustering_title": "Service Plan Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md b/corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
new file mode 100644
index 0000000..03161e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
@@ -0,0 +1,31 @@
+# Service Plan Configuration
+
+NOTE
+
+Not all fields listed below are available for every provision type. After selecting the provision type, the correct fields for that type of Service Plan will be revealed. Not all fields are required to save a valid Service Plan
+
+- **NAME:** The name of the Service Plan in VM Essentials
+- **ACTIVE:** Inactive Service Plans are not available for selection during provisioning or reconfigure. New discovered records cannot be associated with deactivated Plans when converting to managed resources. Any resources attached to a Plan will continue to be associated if the Plan is later deactivated
+- **CODE:** A unique identifier for use in VM Essentials API and CLI
+- **DISPLAY ORDER:** Configures the order in which plans are displayed relative to other plans associated with the same provision type. Note that Plans will be displayed in low-to-high order based on the Display Order property. This is reversed from Layouts which are displayed in high-to-low order
+- **PROVISION TYPE:** Determines the resource Provision Type this Service Plan is available for when provisioning, reconfiguring and converting discovered resources to managed
+- **REGION CODE:** (Optional) Limits availability of the Service Plan to Clouds with the specified Region Code
+- **STORAGE:** The default storage size of the root volume (in MB or GB)
+- **CUSTOMIZE ROOT VOLUME:** Allows the root volume size to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CUSTOMIZE EXTRA VOLUMES:** Allows the extra volume sizes to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **ADD VOLUMES:** Allows additional volumes to be added during provisioning or reconfigure
+- **MEMORY:** The amount of memory included with the plan (in MB or GB)
+- **CUSTOM MEMORY:** Allows the amount of memory to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORE COUNT:** The number of virtual CPU cores included with the plan
+- **CUSTOM CORES:** Allows the number of virtual CPU cores to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORES PER SOCKET:** Determines core distribution across sockets. CORES PER SOCKET cannot be larger than CORE COUNT, and CORE COUNT must be divisible by CORES PER SOCKET. For example four CORES with two CORES PER SOCKET means two sockets would have two cores each assigned. Four CORES with one CORE PER SOCKET would have four sockets with one core each assigned, and four CORES with four CORES PER SOCKET would have one socket with four cores assigned
+- **TOTAL STORAGE:** When custom storage is enabled for the plan, this sets a minimum and maximum total storage allowed (all disks combined)
+- **PER DISK SIZE:** When custom storage is enabled for the plan, this sets the minimum and maximum storage for each disk
+- **CUSTOM MEMORY RANGE:** The minimum and maximum allowed amount of memory for the Plan when CUSTOM MEMORY is enabled for the Plan
+- **CUSTOM CORES RANGE:** The minimum and maximum allowed amount of virtual CPU cores for the Plan when CUSTOM CORES is enabled for the Plan
+- **SOCKETS:** The minimum and maximum allowed sockets range for the Plan when CUSTOM CORES is enabled for the Plan
+- **CORES PER SOCKET:** The minimum and maximum allowed cores per socket for the Plan when CUSTOM CORES is enabled for the Plan
+
+TIP
+
+Custom Range storage and memory values units (GB/MB) are inherited from the :STORAGE:: and :MEMORY:: GB/MB settings in the same Plan. For example, if :STORAGE: is configured for for 40 GB, a custom range for Storage would also be in GB.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json b/corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
new file mode 100644
index 0000000..8afdbde
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+  "title": "Windows Settings",
+  "ordinal": 303,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md b/corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
new file mode 100644
index 0000000..f55689c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
@@ -0,0 +1,13 @@
+# Windows Settings
+
+When provisioning a Windows-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Windows accounts
+- **Password:** The password that will be used with your Windows accounts
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+
+WARNING
+
+If your users Windows Settings password is not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_windows_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-4558D828-A24E-42F3-8ACD-F5E4ACCD556C-high.png)
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json b/corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
new file mode 100644
index 0000000..dba3117
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+  "title": "Features",
+  "ordinal": 349,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md b/corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
new file mode 100644
index 0000000..52c9abf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
@@ -0,0 +1,3 @@
+# Features
+
+- Network - Create or Delete OVS Port Group.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json b/corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
new file mode 100644
index 0000000..4ed2100
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+  "title": "Prepare The New CentOS 8/RHEL8 Image",
+  "ordinal": 339,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.html",
+  "topic_cluster": {
+    "clustering_title": "Prepare The New CentOS 8/RHEL8 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+        "clustering_title": "Prepare The New CentOS 8/RHEL8 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+        "clustering_title": "Prepare The New CentOS 8/RHEL8 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md b/corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
new file mode 100644
index 0000000..9bfd361
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
@@ -0,0 +1,8 @@
+# Prepare The New CentOS 8/RHEL8 Image
+
+## Procedure
+
+1. Install epel-release: `yum -y install epel-release` (This step is not necessary for RHEL)
+2. Install git, wget, curl, cloud-init, cloud-utils-gropart, and open-vm-tools: `yum -y install git wget curl cloud-init cloud-utils-growpart open-vm-tools`
+3. Update: `yum -y update`
+4. Finally run: `rpm -qa kernel | sed 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}`
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json b/corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
new file mode 100644
index 0000000..9c51c29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+  "title": "Packages",
+  "ordinal": 257,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.html",
+  "topic_cluster": {
+    "clustering_title": "Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+        "clustering_title": "Packages"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+        "clustering_title": "Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md b/corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
new file mode 100644
index 0000000..94cc0ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
@@ -0,0 +1,29 @@
+# Packages
+
+## About this task
+
+Packages define reusable HPE Morpheus Essentials resources that you can upload and use across appliances. The platform supports package files in `.morpkg`, `.mpkg`, or `.mopkg` format.
+
+HPE Morpheus Essentials supports task object. Whereas Morpheus Enterprise supports automation objects, such as:
+
+- Instance Types
+- Layouts
+- Node Types
+- Tasks
+- Spec Templates
+- Cluster layouts
+
+Perform the following to upload a package:
+
+## Procedure
+
+1. Navigate to Administration > Integrations.
+2. Click Packages tab.
+3. Navigate to Package Upload section.
+4. Click Choose File.
+5. Select the required package.
+6. Click Upload.
+
+## Results
+
+The system extracts the package and populates the Library with the contained resources. The package appears in the list with its installation status.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json b/corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
new file mode 100644
index 0000000..03ecdd7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+  "title": "Twilio SMS Settings",
+  "ordinal": 269,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.html",
+  "topic_cluster": {
+    "clustering_title": "Twilio SMS Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+        "clustering_title": "Twilio SMS Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+        "clustering_title": "Twilio SMS Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md b/corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
new file mode 100644
index 0000000..a3d77d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
@@ -0,0 +1,7 @@
+# Twilio SMS Settings
+
+Configure SMS text message delivery for VM Essentials alerts. Previously, customers could use VM Essentials’ own account for delivery, but for security reasons clients must now supply their own. Complete the fields indicated below and then restart all VM Essentials nodes to apply the changes.
+
+- **Account SID:** Twilio Account SID
+- **SMS From #:** The “From” number to receive the text message from
+- **Auth Token:** The Twilio API authentication token for your account
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json b/corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
new file mode 100644
index 0000000..2d443d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+  "title": "Edit Group",
+  "ordinal": 87,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.html",
+  "topic_cluster": {
+    "clustering_title": "Edit Group",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+        "clustering_title": "Edit Group"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+        "clustering_title": "Edit Group"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md b/corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
new file mode 100644
index 0000000..583d1cd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
@@ -0,0 +1,14 @@
+# Edit Group
+
+## About this task
+
+To edit a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to edit.
+4. Click the Edit button.
+5. From the Edit Group Wizard modify information as needed.
+6. Click the Save Changes button to save.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json b/corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
new file mode 100644
index 0000000..48a5250
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+  "title": "Edit User",
+  "ordinal": 253,
+  "parent_title": "Users",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.html",
+  "topic_cluster": {
+    "clustering_title": "Edit User",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+        "clustering_title": "Edit User"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+        "clustering_title": "Edit User"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md b/corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
new file mode 100644
index 0000000..418e2a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
@@ -0,0 +1,18 @@
+# Edit User
+
+## About this task
+
+User settings can be edited from Administration > Users.
+
+NOTE
+
+Some User data from Users created via an Identity Source Integration such as Active Directory is not editable in VM Essentials, as it is synced with the Identity Source.
+
+To edit a User from the Administration > Users Section:
+
+## Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Click the edit (pencil) icon from within the row of the selected User
+4. Make changes and select SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json b/corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
new file mode 100644
index 0000000..5a335bc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+  "title": "Guest Console SSH Tunnel",
+  "ordinal": 144,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.html",
+  "topic_cluster": {
+    "clustering_title": "Guest Console SSH Tunnel",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+        "clustering_title": "Guest Console SSH Tunnel"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+        "clustering_title": "Guest Console SSH Tunnel"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md b/corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
new file mode 100644
index 0000000..e955611
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
@@ -0,0 +1,18 @@
+# Guest Console SSH Tunnel
+
+In some scenarios, Instances that are segregated from the VM Essentials appliance by port restrictions, or other mechanisms, can cause difficulties to access the guest console via the VM Essentials web UI. Guest Console SSH Tunnel settings allow the administrator to configure a jump host’s settings that is dual-homed, accessible by VM Essentials but also resides on the segregated network. When the guest console is configured with the SSH protocol, the traffic will be routed to the jump host, which will then relay to the target instance.
+
+GUEST CONSOLE JUMP HOST
+:   DNS hostname or IP of the jump host to relay the traffic
+
+GUEST CONSOLE JUMP PORT
+:   Port override, if different than 22 for SSH
+
+GUEST CONSOLE JUMP USERNAME
+:   Username used to authenticate to the jump host
+
+GUEST CONSOLE JUMP PASSWORD
+:   Password that is used with the username to autenticate to the jump host
+
+GUEST CONSOLE KEYPAIR
+:   Keypair saved in VM Essentials to be used in lieu of, or in addition to, the password to the jump host, which is associated with the configured username Keypairs can be imported at: Infrastructure > Trust > Key Pairs
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json b/corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
new file mode 100644
index 0000000..cb1691b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+  "title": "Cloud Detail Tabs",
+  "ordinal": 94,
+  "parent_title": "Cloud Detail View",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Detail Tabs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+        "clustering_title": "Cloud Detail Tabs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+        "clustering_title": "Cloud Detail Tabs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md b/corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
new file mode 100644
index 0000000..39c0ec9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
@@ -0,0 +1,29 @@
+# Cloud Detail Tabs
+
+NOTE
+
+Not all tabs are available for all Cloud Types.
+
+Clusters
+:   The Clusters tab displays clusters provisioned into the Cloud being viewed, including their status, type, name, layout, workers, and compute, memory, and storage stats. You can add a cluster by clicking ADD CLUSTER.
+
+Hosts
+:   The Hosts tab displays available hosts in the Cloud and displays power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status. You can add a resource by clicking ADD RESOURCE, add a hypervisor host by clicking ADD HYPERVISOR, or perform action an action by selecting one or more Hosts and clicking ACTIONS.
+
+    VMs
+    :   Displays an inventory of existing Instances in your Cloud configuration and provides details such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Bare Metal
+:   Setup PXE Boot in the Boot section to add bare metal servers. Once set up you can view information such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Security Groups
+:   The Security Groups tab displays a list of existing security groups in the cloud. You can add a security group to this cloud by clicking EDIT SECURITY GROUPS.
+
+Networks
+:   Displays Networks synced or added to the Cloud, including their name, type, CIDR, pool, DHCP status, visibility and targeted Tenant.
+
+Data Stores
+:   Displays Datastores synced or added to the Cloud, including their name, type, capacity, online status, visibility, and targeted Tenant.
+
+Resources
+:   Displays Resource Pools synced from the Cloud, including their name, description, and targeted Tenant.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json b/corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
new file mode 100644
index 0000000..60e2082
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+  "title": "Creating Cypher Keys",
+  "ordinal": 215,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Cypher Keys",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+        "clustering_title": "Creating Cypher Keys"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+        "clustering_title": "Creating Cypher Keys"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md b/corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
new file mode 100644
index 0000000..60553b6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
@@ -0,0 +1,6 @@
+# Creating Cypher Keys
+
+## Procedure
+
+1. Navigate to Tools > Cypher and select + ADD
+2. Configure one of the following types of Keys:
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json b/corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
new file mode 100644
index 0000000..acc1e3e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+  "title": "Add Virtual Image",
+  "ordinal": 77,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.html",
+  "topic_cluster": {
+    "clustering_title": "Add Virtual Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+        "clustering_title": "Add Virtual Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+        "clustering_title": "Add Virtual Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md b/corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
new file mode 100644
index 0000000..77b52d9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
@@ -0,0 +1,108 @@
+# Add Virtual Image
+
+## About this task
+
+Virtual Images can be uploaded to VM Essentials from local files or URLs.
+
+WARNING
+
+Be conscious of your Storage Provider selection. The default Storage Provider is the VM Essentials Appliance at `/var/opt/morpheus/morpheus-ui/vms`. Uploading large images to the VM Essentials Appliance when there is inadequate space will cause upload failures and impact Appliance functionality. Ensure there is adequate space on your selected Storage Provider. Additional Storage Provider can be added at Infrastructure  >  Storage, which can be configured as the default Virtual Image Store or selected when uploading Images.
+
+NOTE
+
+VMware-type OVF Virtual Images do not support mounted ISO uploads
+
+To Add Virtual Image:
+
+## Procedure
+
+1. Select + Add in the Virtual Images page.
+2. Select Image format: 
+
+   - ISO
+   - QCOW2
+   - RAW
+   - VMware (vmdk/ovf/ova)
+3. Configure the following on the Virtual Image: 
+
+   Name
+   :   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant VM Essentials environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, VM Essentials will install the FIPS-compliant VM Essentials Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to VMware vCenter Clouds. Enable if the Windows Image has been sysprepped. If enabled, VM Essentials will inject `unattend.xml`
+
+   NOTE
+
+   Default Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage. Ensure local folders are owned by morpheus-app.morpheus-app if used.
+
+   WARNING
+
+   Provisioning will fail if Cloud init Enabled is checked and Cloud-Init is not installed on the Image.
+
+   NOTE
+
+   Existing Image credentials are required for Linux Images that are not Cloud-Init enabled and for Windows Images when Guest Customizations are not used. Cloud-Init and Windows user settings need to be configured in Administration > Settings > Provisioning when using Cloud-Init or Guest Customizations and new credentials are not set on the Virtual Image.
+4. Upload Image
+   :   Images can be uploaded by File or URL:
+       :   File
+           :   Drag and Drop the image file, or select Add File to select the image file.
+
+           Url
+           :   Select the URL radio button, and enter URL of the Image.
+
+       NOTE
+
+       The Virtual Image configuration can be saved when using a URL and the upload will finish in the background. When selecting/drag and dropping a file, the image files must upload completely before saving the Virtual Image record or the Image will not be valid.
+5. Save Changes.
+
+**Subtopics**  
+
+- **[VMware - VM Templates Copies](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json b/corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
new file mode 100644
index 0000000..0d99adc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+  "title": "Virtual Images",
+  "ordinal": 29,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md b/corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
new file mode 100644
index 0000000..b7cdd3a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
@@ -0,0 +1,14 @@
+# Virtual Images
+
+The most common provisioning method within VM Essentials involves Virtual Machines, and the most important part of provisioning a VM is the Virtual Image. When provisioning a VM, VM Essentials will need to do a few things depending on the location of the Virtual Image and if agent install and console access are desired.
+
+Synced Images need to be properly configured
+:   VM Essentials gathers as much metadata for synced images as possible, but depending on the target (HVM cluster or VMware vCenter), OS, image configuration, or agent install settings, the synced Virtual Images may not be ready to provision without some configuration within VM Essentials. The Virtual Image is already at the target Cloud, but datastore selection, credentials, cloud-init settings, networks, and security settings on the Virtual Image can cause provisioning issues.
+
+Local/Uploaded Virtual Images
+:   Images uploaded to VM Essentials are configured during the Add Virtual Image process, however VM Essentials in most scenarios will still need to copy the Virtual Image to the target Hypervisor/Cloud upon the first provision to the target Cloud. In addition to the requirements for provisioning a synced Virtual Image, copying an uploaded Virtual Image to the target Cloud is required. Network and image configurations can cause upload failures, resulting in provisioning issues.
+
+**Subtopics**  
+
+- **[Synced Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.html)**
+- **[Local Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json b/corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
new file mode 100644
index 0000000..c38d6f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+  "title": "Library Settings",
+  "ordinal": 279,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.html",
+  "topic_cluster": {
+    "clustering_title": "Library Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+        "clustering_title": "Library Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+        "clustering_title": "Library Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md b/corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
new file mode 100644
index 0000000..54e1ae9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
@@ -0,0 +1,8 @@
+# Library Settings
+
+In this section, enable or disable access globally to provisioning sections of Catalog (self-service shopping cart provisioning), Apps (apps deployed from configured App Blueprints), and Instances
+
+- Enable Catalog
+- Enable Apps
+- Enable Instances
+- Provisioning Order: Sets the order for Instances, Apps, and Catalog to appear in the Provisioning menu
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json b/corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
new file mode 100644
index 0000000..ed889eb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+  "title": "Create Service Plan",
+  "ordinal": 240,
+  "parent_title": "Overview",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.html",
+  "topic_cluster": {
+    "clustering_title": "Create Service Plan",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+        "clustering_title": "Create Service Plan"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+        "clustering_title": "Create Service Plan"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md b/corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
new file mode 100644
index 0000000..7c6ac10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
@@ -0,0 +1,12 @@
+# Create Service Plan
+
+## About this task
+
+Perform the following to create a service plan:
+
+## Procedure
+
+1. Navigate to Administration > Plans (`/admin/service-plans`)
+2. Click the + ADD dropdown and select the appropriate Plan type
+3. Configure details for the Plan on the General tab, the configuration options will depend on the Plan type. See the section above for a detailed description of each configuration option available for Service Plans
+4. Click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json b/corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
new file mode 100644
index 0000000..488d271
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+  "title": "Secret",
+  "ordinal": 218,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.html",
+  "topic_cluster": {
+    "clustering_title": "Secret",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+        "clustering_title": "Secret"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+        "clustering_title": "Secret"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md b/corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
new file mode 100644
index 0000000..6a1e555
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
@@ -0,0 +1,20 @@
+# Secret
+
+A Cypher secret is the standard secret module that stores a key/value in encrypted form.
+
+Key
+:   Pattern “secret/key”
+
+    - EXAMPLE: secret/mysecret
+
+Value
+:   Add the secret value to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the secret will be encrypted and available for use.
+
+If your VM Essentials user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the secret.
+
+To delete the secret, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json b/corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
new file mode 100644
index 0000000..8b5efea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+  "title": "Hosting Images",
+  "ordinal": 19,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.html",
+  "topic_cluster": {
+    "clustering_title": "Hosting Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+        "clustering_title": "Hosting Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+        "clustering_title": "Hosting Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md b/corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
new file mode 100644
index 0000000..2cb96fa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
@@ -0,0 +1,11 @@
+# Hosting Images
+
+It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the VM Essentials appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
+
+```
+```
+![my alt text](https://myimage.com/image.jpg)
+```
+```
+
+The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The VM Essentials [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the VM Essentials appliance local storage. VM Essentials generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in VM Essentials Archives within your Wiki pages.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json b/corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
new file mode 100644
index 0000000..03505a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+  "title": "Creating a CentOS/RHEL 7 Image",
+  "ordinal": 335,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a CentOS/RHEL 7 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+        "clustering_title": "Creating a CentOS/RHEL 7 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+        "clustering_title": "Creating a CentOS/RHEL 7 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md b/corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
new file mode 100644
index 0000000..06f04cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
@@ -0,0 +1,21 @@
+# Creating a CentOS/RHEL 7 Image
+
+## About this task
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+## Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install open-vm-tools using command `yum install open-vm-tools`
+6. Install git by running `yum install git`
+7. Install epel-release repo using command `yum install epel-release`
+8. selinux set to permissive (enforced can cause problems with cloud-init) `sudo vi /etc/selinux/config`
+
+**Subtopics**  
+
+- **[Cloud-Init](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.html)**
+- **[Network Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json b/corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
new file mode 100644
index 0000000..130f925
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+  "title": "Appliance",
+  "ordinal": 264,
+  "parent_title": "Settings",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md b/corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
new file mode 100644
index 0000000..4fa2ce6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
@@ -0,0 +1,14 @@
+# Appliance
+
+**Subtopics**  
+
+- **[Appliance Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html)**
+- **[Tenant Management Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.html)**
+- **[User Management Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.html)**
+- **[Email Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.html)**
+- **[Twilio SMS Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.html)**
+- **[Proxy Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.html)**
+- **[Currency Settings](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html)**
+- **[Integrating With a Currency Exchange Provider](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-AC461BBD-647D-447D-9307-218A41CE368B.html)**
+- **[Consuming Currency Exchange in VM Essentials](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.html)**
+- **[Enabled Clouds (Types)](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/render?page=GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.html)**
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json b/corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
new file mode 100644
index 0000000..74ec2a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+  "title": "Actions",
+  "ordinal": 48,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.html",
+  "topic_cluster": {
+    "clustering_title": "Actions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+        "clustering_title": "Actions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+        "clustering_title": "Actions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md b/corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
new file mode 100644
index 0000000..d3dc184
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
@@ -0,0 +1,43 @@
+# Actions
+
+Available options in the Actions dropdown can include:
+
+Suspend
+:   Puts the VM in a suspended state without shutting down the OS.
+
+Stop/Start/Restart Server
+:   Stops, Starts or Restarts the Virtual Machine.
+
+Import as Image
+:   Clones and exports VM in its current state to target Storage provider and adds a Virtual Image record with metadata matching the source Instance configuration.
+
+Clone to Image
+:   Clones and converts VM in its current state to image in the source Cloud and adds a Virtual Image record with metadata matching the source Instance configuration.
+
+Lock/Unlock Instance
+:   A locked Instance cannot be deleted until it is unlocked.
+
+Reconfigure
+:   The Reconfigure action allows service plan, disk, CPU, memory, networks and storage controller changes. Available options depend on the type and Plan configuration. Some resize actions require an Instance restart.
+
+Clone
+:   Creates a new Instance from the Instance at its current state.
+
+Backup
+:   Immediately executes a backup of the Instance. This is only available for Instances with backups enabled.
+
+Run Task
+:   Select a currently-configured Task to run against the Instance. Tasks can be created and edited in Library > Automation.
+
+Add Node
+:   Adds an additional node to the configuration. Additional options and configurations are required in the add node wizard depending on Instance configuration and type.
+
+Eject Disk
+:   Ejects attached disks (ISOs).
+
+Clone to Template (VMware)
+:   Creates a new VMware Template from the Instance with corresponding VM Essentials Virtual Image record.
+
+TIP
+
+Scrolling down in the Actions dropdown may be necessary to see all options.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json b/corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
new file mode 100644
index 0000000..7821eb7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+  "title": "Image Prep (Windows)",
+  "ordinal": 130,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html",
+  "topic_cluster": {
+    "clustering_title": "Image Prep (Windows)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+        "clustering_title": "Image Prep (Windows)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+        "clustering_title": "Image Prep (Windows)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md b/corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
new file mode 100644
index 0000000..a921c38
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
@@ -0,0 +1,94 @@
+# Image Prep (Windows)
+
+This section will go through the steps to prepare a Windows image which can be successfully provisioned to HVM clusters. Additionally, this image can serve as a template from which additional images and VM Essentials Library items can be built. In this example case, we’ll start from downloading a Windows Server 2019 ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
+
+With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+
+- **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2019 ISO”
+- **OPERATING SYSTEM:** “windows server 2019”
+- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+
+In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+
+With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large dropzone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled “Add File” and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES.
+
+![../../_images/progress.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-984BC461-04D2-4759-9E91-D9ACF2C6EB23-high.png)
+
+Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+
+On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+
+On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+
+As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+![../../_images/configTabBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+
+The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+
+Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+
+Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then “Open Console.” This will open a new window with a console session into the VM.
+
+![../../_images/initialConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+
+After selecting the language, click “Next.” On the following screen, click “Install Now.” This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click “Next.”
+
+![../../_images/chooseOs.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+
+Accept the licensing terms and click “Next.”
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+
+On the next screen, choose a custom install.
+
+![../../_images/clickInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+
+The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+![../../_images/selectVirtioPackage.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+
+After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+![../../_images/selectDisk.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+
+Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+![../../_images/windowsExp.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+
+Step through the installer. Simply click “Next” or “Install” through each step, there are no configuration changes needed. Once the installer has completed, click “Finish.” You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+![../../_images/showInterface.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+
+We can now eject the two virtual disks, drives D: and E: in my case. Then, launch Windows Security so we can disable firewalls. Turn off firewall for domain, private network, and public network.
+
+![../../_images/winDefender.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-DAA8652B-17E0-4AF2-9273-C548F0FA0614-high.png)
+
+Next, back in Command Prompt, run `winrm quickconfig` to configure `winrm`. Within `Services`, ensure that `winrm` (Windows Remote Management) is set to automatic on startup. Right-click on the Start button and select Run. Enter “sysprep” and click OK. In the Windows Explorer window that appears, right-click on `sysprep` and click “Run as Administrator”. Under “Shutdown Options”, choose Quit and click OK. If this is set to shutdown, VM Essentials will simply restart the VM. Once this is completed, a new file `Sysprep_succeeded.tag` appears in Windows Explorer.
+
+![../../_images/sysprepComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007520en_us/GUID-A11613FB-FC10-42BC-A6A3-3FB44D08260B-high.png)
+
+We’re now done configuring Windows and the console window can be closed. We’ll move on to creating a template from the VM we just configured. Begin by opening an SSH session into the VM Essentials appliance server. Confirm `jq` is up to date on the appliance box (`apt install jq`). Then, go ahead and stop the running Windows VM. We can do this from the Instance detail page in VM Essentials. Click ACTIONS and then “Stop Server.” Still on the Instance detail page, click ACTIONS and then “Import as Image.” This will perform a snapshot and create a new Virtual Image (Library > Virtual Images).
+
+The Virtual Image is not usable until it’s in an active status and the UI indication may display an active status even before it’s fully ready. If it’s “SAVING” or “QUEUED,” it is still being prepared and saved. To determine the current status of the Virtual Image, check with a call to VM Essentials API like the one below. When the return output lists a status of “Active,” the image is ready to be provisioned from.
+
+```
+```
+curl -k --request GET --url https://xx.xx.xx.xx/api/virtual-images/<id>  
+--header 'accept: application/json' --header 'authorization: Bearer xxx-xxx-xxx-xxx-xxx' |  
+jq '.virtualImage.status'
+```
+```
+
+Once saved, additional configurations are needed on the Virtual Image in VM Essentials. Edit the new Virtual Image and check the following configurations:
+
+- **MINIMUM MEMORY:** Set as appropriate
+- **SYSPREPPED/GENERALIZED IMAGE?:** Checked
+- **INSTALL AGENT?:** Checked
+- **USERNAME:** Remove if present
+- **PASSWORD:** Remove if present
+- **VIRTIO DRIVERS LOADED?:** Checked
+
+All other checkbox-type configurations not mentioned in the above list should be unchecked. Click SAVE CHANGES.
+
+At this point all image preparation steps are completed. Repeat the process of provisioning an HVM Instance Type selecting the new image in the future when needed.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json b/corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
new file mode 100644
index 0000000..a357771
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+  "title": "Execution Schedules",
+  "ordinal": 206,
+  "parent_title": "Initial Backups Setup",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.html",
+  "topic_cluster": {
+    "clustering_title": "Execution Schedules",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+        "clustering_title": "Execution Schedules"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+        "clustering_title": "Execution Schedules"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md b/corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
new file mode 100644
index 0000000..e923e44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
@@ -0,0 +1,3 @@
+# Execution Schedules
+
+Backup Execution Schedules can be configured and managed in Library > Automation > Execute Scheduling. An execution schedule stores only the interval at which some execution should be run and they can apply to both backups and automation scripts. To create a new backup job with this schedule, navigate to Backups  >  Backups and click “+ADD”. In the final step of creating the backup job we are able to select any of our created execution schedules. The Default Backup Schedule set in Administration > Settings > Backups will be selected when creating a backup job and not specifying an execution schedule.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json b/corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
new file mode 100644
index 0000000..5092ad9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+  "title": "Environment",
+  "ordinal": 7,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.html",
+  "topic_cluster": {
+    "clustering_title": "Environment",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+        "clustering_title": "Environment"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+        "clustering_title": "Environment"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md b/corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
new file mode 100644
index 0000000..7ec85ea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
@@ -0,0 +1,8 @@
+# Environment
+
+- **Groups:** Total number of Groups currently created
+- **Clouds:** Total number of Clouds currently integrated
+- **Clusters:** Total number of clusters currently provisioned
+- **Apps:** Total number of Apps currently provisioned
+- **Instances:** Total number of Instances currently provisioned
+- **Users:** Total number of VM Essentials user accounts
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json b/corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
new file mode 100644
index 0000000..6694396
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+  "title": "Cloud Communication",
+  "ordinal": 168,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Communication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+        "clustering_title": "Cloud Communication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+        "clustering_title": "Cloud Communication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md b/corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
new file mode 100644
index 0000000..b70bd48
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
@@ -0,0 +1,3 @@
+# Cloud Communication
+
+When morpheus needs to connect to various cloud APIs to issue provisioning commands or to sync in existing environments, we need to ensure that those api endpoints are accessible by the appliance. In some cases the appliance may be behind a proxy when it comes to public cloud access like Azure and AWS. To configure the cloud integration to utilize a proxy, when adding or editing a cloud there is a setting called “API Proxy” under “Advanced Options”. This is where the proxy of choice can be selected to instruct the Provisioning engine how to communicate with the public cloud. Simply adjust this setting and the cloud should start being able to receive/issue instructions.
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json b/corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
new file mode 100644
index 0000000..6f2d7eb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+  "title": "Adding Groups",
+  "ordinal": 85,
+  "parent_title": "Groups",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+        "clustering_title": "Adding Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+        "clustering_title": "Adding Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md b/corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
new file mode 100644
index 0000000..7cb5270
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
@@ -0,0 +1,13 @@
+# Adding Groups
+
+## About this task
+
+To add a group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Create Group button
+4. Input out the Name and Location (optional) fields
+5. Click the Save Changes button to save
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json b/corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
new file mode 100644
index 0000000..359be86
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_0",
+  "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+  "title": "Highlights",
+  "ordinal": 17,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007520en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007520en_us&page=GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.html",
+  "topic_cluster": {
+    "clustering_title": "Highlights",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+        "clustering_title": "Highlights"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+        "clustering_title": "Highlights"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md b/corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
new file mode 100644
index 0000000..89866df
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_0/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
@@ -0,0 +1,13 @@
+# Highlights
+
+- Main Wiki section is at Operations > Wiki
+- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, and Clusters detail pages
+- Additional Wiki Pages and Categories can be created from Operations > Wiki
+- When a Wiki tab is populated, a Page is automatically added and accessible at Operations > Wiki
+- The Wiki is accessible from the UI, CLI and API.
+- Wiki access is RBAC-controlled via the Operations: Wiki permission in Roles (None, Read and Full)
+- Page updates are stamped with the “Last Updated By” user and the time the edit was made
+- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
+- All wiki pages are encrypted using AES 256-bit encryption
+- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
+- Create a new page with title “Home” to replace the default Wiki landing page that ships with VM Essentials
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json b/corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
new file mode 100644
index 0000000..79f266c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+  "title": "Global Backups Settings",
+  "ordinal": 206,
+  "parent_title": "Initial Backups Setup",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html",
+  "topic_cluster": {
+    "clustering_title": "Global Backups Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+        "clustering_title": "Global Backups Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+        "clustering_title": "Global Backups Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md b/corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
new file mode 100644
index 0000000..d93a136
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
@@ -0,0 +1,27 @@
+# Global Backups Settings
+
+VM Essentials Backups can be enabled under Administration > Settings > Backups.
+
+Scheduled Backups
+:   When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
+
+Create Backups
+:   When enabled, VM Essentials will automatically configure backup jobs for Instances at provision time.
+
+Backup Appliance
+:   When enabled, a Backup will be created to backup the VM Essentials appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
+
+Default Backup Bucket
+:   From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
+
+Default Backup Schedule
+:   From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+Backup Retention Count
+:   The default maximum number of successful backups to retain.
+
+Default Synthetic Full Backup Enabled
+:   When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
+
+Default Synthetic Full Backups Schedule
+:   From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json b/corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
new file mode 100644
index 0000000..a2e3779
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+  "title": "Scoping Services",
+  "ordinal": 173,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html",
+  "topic_cluster": {
+    "clustering_title": "Scoping Services",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+        "clustering_title": "Scoping Services"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+        "clustering_title": "Scoping Services"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md b/corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
new file mode 100644
index 0000000..8b76936
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
@@ -0,0 +1,20 @@
+# Scoping Services
+
+NETWORKING
+:   Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
+
+IPAM
+:   IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
+
+SECURITY
+:   Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
+
+DNS
+:   DNS integrations will populate domains in the Infrastructure  >  Network  >  Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+Service Registry
+:   Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+NOTE
+
+Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json b/corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
new file mode 100644
index 0000000..8acb62f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+  "title": "Group and Tenant Access",
+  "ordinal": 144,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html",
+  "topic_cluster": {
+    "clustering_title": "Group and Tenant Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+        "clustering_title": "Group and Tenant Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+        "clustering_title": "Group and Tenant Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md b/corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
new file mode 100644
index 0000000..37ab560
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
@@ -0,0 +1,3 @@
+# Group and Tenant Access
+
+Networks can be configured to provide specific Group access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json b/corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
new file mode 100644
index 0000000..308c8bd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+  "title": "Cloud-Init Agent install mode",
+  "ordinal": 39,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init Agent install mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+        "clustering_title": "Cloud-Init Agent install mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+        "clustering_title": "Cloud-Init Agent install mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md b/corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
new file mode 100644
index 0000000..28af5bf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
@@ -0,0 +1,4 @@
+# Cloud-Init Agent install mode
+
+- Cloud-Init is configured in Administration > Settings > Provisioning section
+- Provisioned image has Cloud-Init (Linux) or Cloudbase-Init (Windows) installed
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json b/corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
new file mode 100644
index 0000000..a029aaa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+  "title": "Activity",
+  "ordinal": 20,
+  "parent_title": "Operations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md b/corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
new file mode 100644
index 0000000..f5e2bfb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
@@ -0,0 +1,11 @@
+# Activity
+
+The Activity section displays a recent activity report for Auditing. VM Essentials defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, etc… This view can be searched and filtered by type, user, and date range.
+
+![Activity page](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-01147D13-F369-4441-B97D-9354DA79DF93-high.png)
+
+**Subtopics**  
+
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html)**
+- **[Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html)**
+- **[History](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.json b/corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
new file mode 100644
index 0000000..8d6132e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+  "title": "Add ArubaCX Integration to a Cluster",
+  "ordinal": 355,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html",
+  "topic_cluster": {
+    "clustering_title": "Add ArubaCX Integration to a Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+        "clustering_title": "Add ArubaCX Integration to a Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+        "clustering_title": "Add ArubaCX Integration to a Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.md b/corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
new file mode 100644
index 0000000..ab37100
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
@@ -0,0 +1,10 @@
+# Add ArubaCX Integration to a Cluster
+
+## Procedure
+
+1. In Infrastructure > Clusters select the target Cluster
+2. Select the Edit icon for the Cluster
+3. In the “Integrations” dropdown, select an available ArubaCX Integration
+4. Save Changes 
+
+   ![../../_images/arubacx_edit_cluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-6978CDB6-74D2-492A-B461-2F0EC476F018-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.json b/corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.json
new file mode 100644
index 0000000..b7a631d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+  "title": "Group Access",
+  "ordinal": 161,
+  "parent_title": "Editing Domain Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-06426E05-BE70-4917-89E3-153236303513.html",
+  "topic_cluster": {
+    "clustering_title": "Group Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+        "clustering_title": "Group Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+        "clustering_title": "Group Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.md b/corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.md
new file mode 100644
index 0000000..4659567
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-06426E05-BE70-4917-89E3-153236303513.md
@@ -0,0 +1,3 @@
+# Group Access
+
+The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json b/corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
new file mode 100644
index 0000000..30b1de9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+  "title": "Currency Settings",
+  "ordinal": 272,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html",
+  "topic_cluster": {
+    "clustering_title": "Currency Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+        "clustering_title": "Currency Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+        "clustering_title": "Currency Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md b/corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
new file mode 100644
index 0000000..44fd21e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
@@ -0,0 +1,3 @@
+# Currency Settings
+
+In VM Essentials, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, VM Essentials allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json b/corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
new file mode 100644
index 0000000..1cd6223
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+  "title": "NFSv3 File Shares",
+  "ordinal": 190,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html",
+  "topic_cluster": {
+    "clustering_title": "NFSv3 File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+        "clustering_title": "NFSv3 File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+        "clustering_title": "NFSv3 File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md b/corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
new file mode 100644
index 0000000..08203c4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
@@ -0,0 +1,80 @@
+# NFSv3 File Shares
+
+## About this task
+
+NOTE
+
+Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
+
+NOTE
+
+Upon save VM Essentials will create a persistent mount owned by `morpheus-app.morpheus-app` on the VM Essentials Appliance for the NFSv3 File Share. The VM Essentials appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before VM Essentials is able to successfully mount the share.
+
+To Add a NFSv3 File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select NFSv3 from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   HOST
+   :   Enter the File Share path on the local VM Essentials Appliance.
+
+   EXPORT FOLDER
+   :   Enter the NFSv3 Folder
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+**Subtopics**  
+
+- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json b/corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
new file mode 100644
index 0000000..2f9113d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+  "title": "Add HPE Alletra MP Storage",
+  "ordinal": 368,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html",
+  "topic_cluster": {
+    "clustering_title": "Add HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+        "clustering_title": "Add HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+        "clustering_title": "Add HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md b/corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
new file mode 100644
index 0000000..8856bed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
@@ -0,0 +1,33 @@
+# Add HPE Alletra MP Storage
+
+## About this task
+
+The first step is to create a storage server in VM Essentials. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage
+2. In the “Servers” tab, Click the + ADD button
+3. From the ADD STORAGE SERVER wizard, input the following: 
+
+   NAME:
+   :   Name of the storage server in VM Essentials
+
+   TYPE:
+   :   Select “HPE Alletra MP”
+
+   URL:
+   :   URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
+
+   USERNAME:
+   :   Add your administrative user account
+
+   PASSWORD:
+   :   Add your administrative user account password
+4. Select SAVE CHANGES
+
+## Results
+
+![../../_images/add-storage-server.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-432FC4EC-3961-492E-9423-55CC7E6BCACA-high.png)
+
+The Storage Server will be added and displayed in the Datastore tab.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json b/corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
new file mode 100644
index 0000000..c1d6cab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+  "title": "Plans",
+  "ordinal": 239,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md b/corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
new file mode 100644
index 0000000..9305dc8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
@@ -0,0 +1,5 @@
+# Plans
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json b/corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
new file mode 100644
index 0000000..b2a2b8e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+  "title": "Cloud Detail View",
+  "ordinal": 93,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Detail View",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+        "clustering_title": "Cloud Detail View"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+        "clustering_title": "Cloud Detail View"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md b/corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
new file mode 100644
index 0000000..9f19c07
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
@@ -0,0 +1,22 @@
+# Cloud Detail View
+
+The Cloud Detail view shows metrics on health, sync status, resource utilization statistics, and resource counts for hosts, virtual machines, or any other constructs under the umbrella of the selected Cloud.
+
+From the Cloud list page, select the name of a Cloud to display that Cloud’s detail page. You’ll notice the following actions are available:
+
+EDIT
+:   Edit the setup configuration of the Cloud.
+
+REFRESH
+:   Force a sync with the Cloud.
+
+DELETE
+:   Delete the Cloud from VM Essentials.
+
+IMPORTANT
+
+All Instances, managed Hosts, and VMs associated with the Cloud must be removed prior to deleting a Cloud.
+
+**Subtopics**  
+
+- **[Cloud Detail Tabs](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json b/corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
new file mode 100644
index 0000000..6a9fce6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+  "title": "Environments",
+  "ordinal": 287,
+  "parent_title": "Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
+  "topic_cluster": {
+    "clustering_title": "Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md b/corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
new file mode 100644
index 0000000..3a0b083
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
@@ -0,0 +1,5 @@
+# Environments
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json b/corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
new file mode 100644
index 0000000..3cf6d7c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+  "title": "Overview",
+  "ordinal": 357,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md b/corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
new file mode 100644
index 0000000..8018b5a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
@@ -0,0 +1,11 @@
+# Overview
+
+The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus VM Essentials Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
+
+Implemented as a VM Essentials `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for VM Essentials environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM cluster.
+
+On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. VM Essentials integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM hosts in the HVM cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
+
+The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM cluster.
+
+Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json b/corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
new file mode 100644
index 0000000..457313c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+  "title": "Editing Domain Permissions",
+  "ordinal": 160,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Domain Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+        "clustering_title": "Editing Domain Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+        "clustering_title": "Editing Domain Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md b/corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
new file mode 100644
index 0000000..c5024ca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
@@ -0,0 +1,7 @@
+# Editing Domain Permissions
+
+To edit visibility permissions for a domain, navigate to Infrastructure  >  Network  >  Domains. In the row for the selected domain, click MORE > Permissions. Within the Permissions modal, set Group access permissions.
+
+**Subtopics**  
+
+- **[Group Access](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-06426E05-BE70-4917-89E3-153236303513.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json b/corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
new file mode 100644
index 0000000..53efa68
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+  "title": "Disabling Two-Factor Authentication",
+  "ordinal": 300,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.html",
+  "topic_cluster": {
+    "clustering_title": "Disabling Two-Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+        "clustering_title": "Disabling Two-Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+        "clustering_title": "Disabling Two-Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md b/corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
new file mode 100644
index 0000000..13d174a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
@@ -0,0 +1,5 @@
+# Disabling Two-Factor Authentication
+
+When two-factor authentication is set up, this section contains two buttons: DISABLE 2FA and GET 2FA CODE. To generate a new QR code and configure an authenticator app, click GET 2FA CODE. Once you generate a new QR code, the old one is no longer valid. At that point you must reconfigure your authenticator app or you will not be able to access your account on the next login attempt. Generating a new QR code requires your password.
+
+To disable 2FA, click DISABLE 2FA. This action does not require a password.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json b/corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
new file mode 100644
index 0000000..54e2eca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+  "title": "Openstack Swift Buckets",
+  "ordinal": 184,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.html",
+  "topic_cluster": {
+    "clustering_title": "Openstack Swift Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+        "clustering_title": "Openstack Swift Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+        "clustering_title": "Openstack Swift Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md b/corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
new file mode 100644
index 0000000..e09082b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
@@ -0,0 +1,77 @@
+# Openstack Swift Buckets
+
+## About this task
+
+To Add an OpenStack Swift Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Openstack Swift from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   USERNAME
+   :   Openstack Swift Username
+
+   API KEY
+   :   Openstack Swift API Key
+
+   BUCKET NAME
+   :   Enter existing Openstack Swift Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   IDENTITY URL
+   :   Openstack Swift Identity URL
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json b/corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
new file mode 100644
index 0000000..3cac859
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+  "title": "Health Levels",
+  "ordinal": 261,
+  "parent_title": "VM Essentials Health",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.html",
+  "topic_cluster": {
+    "clustering_title": "Health Levels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+        "clustering_title": "Health Levels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+        "clustering_title": "Health Levels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md b/corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
new file mode 100644
index 0000000..31250f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
@@ -0,0 +1,10 @@
+# Health Levels
+
+Health levels provide a live representation of the current memory and CPU load on the appliance. Bear in mind that in an HA appliance, this data will be specific to the appliance node you happen to be using. By default, VM Essentials does not include any endpoint or UI tool which can show you the currently used app node. However, a plugin has been developed which can surface this information if needed. See [this thread](https://discuss.morpheusdata.com/t/custom-ping-endpoint-via-morpheus-plugin/389) in the VM Essentials official forums for additional details about accessing and using the plugin.
+
+- **Morpheus CPU:** Instantaneous amount of CPU capacity in use by VM Essentials processes
+- **System CPU:** Instantaneous amount of CPU capacity in use by all processes
+- **Morpheus Memory:** Instantaneous amount of system memory currently in use by VM Essentials processes (see the Knowledge Base article linked in the TIP box below for more information on how VM Essentials claims and manages available memory)
+- **System Memory:** Instantaneous amount of total system memory currently claimed (this is commonly a high percentage, see the TIP box below)
+- **Used Swap:** Instantaneous amount of total available system swap in use
+- **Storage:** The instantaneous percentage utilization of the filesystem mounted at “/”
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json b/corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
new file mode 100644
index 0000000..8eb208d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+  "title": "Data Stores",
+  "ordinal": 191,
+  "parent_title": "NFSv3 File Shares",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html",
+  "topic_cluster": {
+    "clustering_title": "Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+        "clustering_title": "Data Stores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+        "clustering_title": "Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md b/corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
new file mode 100644
index 0000000..31b9c81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
@@ -0,0 +1,5 @@
+# Data Stores
+
+Data Stores are logical divisions of underlying storage disk. Organizations may use them to divide and track cloud resources by team or department. When integrating certain Cloud types, VM Essentials will onboard all existing data stores and administrators can then make them available to Groups as needed. At provision time, when applicable based on Cloud and Layout, users can select the datastore they wish to provision to.
+
+Here within the Data Store view in the storage section, users can see a list of data stores for each Cloud. In the row for each Cloud, the storage type, associated Cloud, and permissions information are shown.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json b/corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
new file mode 100644
index 0000000..f012c7e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+  "title": "Create HPE ANW DSS Port Group Network",
+  "ordinal": 362,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.html",
+  "topic_cluster": {
+    "clustering_title": "Create HPE ANW DSS Port Group Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+        "clustering_title": "Create HPE ANW DSS Port Group Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+        "clustering_title": "Create HPE ANW DSS Port Group Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md b/corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
new file mode 100644
index 0000000..0b2f6fd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
@@ -0,0 +1,24 @@
+# Create HPE ANW DSS Port Group Network
+
+## About this task
+
+To create an HPE ANW DSS Port Group network, follow these steps:
+
+## Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select + Add Network > HPE ANW DSS Port Group 
+
+   ![../../_images/3.1_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-3CE7AFEC-D544-4E9A-9277-1343D8DCD7BE-high.png)
+3. Select the Network Service in the CREATE NETWORK form: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-3A253CC3-F827-4CA3-A2C5-58F8FEC8C30D-high.png)
+4. Enter the following details in the CREATE NETWORK form. Note that the values in the screenshot are reference examples. Input only the values intended for the actual network: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-34B08F15-1A6E-4E91-97C0-59D865049E4A-high.png)
+5. Save the network by clicking on Save changes. 
+
+   ![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-02143765-1935-4568-A755-9A6B134CA122-high.png)![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-BF4B2385-7813-4CB8-912B-DCF724834F47-high.png)
+6. The network will be created and displayed in the list of networks. 
+
+   ![../../_images/3.4_network_created.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-2ABDBDC9-8594-4248-B7F8-056488423C77-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json b/corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
new file mode 100644
index 0000000..f2b89c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+  "title": "Credentials",
+  "ordinal": 197,
+  "parent_title": "Trust",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.html",
+  "topic_cluster": {
+    "clustering_title": "Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+        "clustering_title": "Credentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+        "clustering_title": "Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md b/corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
new file mode 100644
index 0000000..197d897
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
@@ -0,0 +1,27 @@
+# Credentials
+
+The credentials section allows for various credential types to be securely stored and called back when necessary, such as when creating new integrations with Cloud accounts or other outside technologies. Credentials can also be used to populate REST-based Option Lists sourced from data behind an authentication wall, as well as to run automation Tasks on remote targets that require authentication. Credentials are stored internally and securely on the VM Essentials appliance. The following credential pair types are currently supported:
+
+- Access Key and Secret Key
+- Client ID and Secret
+- Email and Private Key
+- OAuth 2.0
+- Tenant, Username, and Keypair
+- Username and API Key
+- Username and Keypair
+- Username and Password
+- Username, Password, and Keypair
+
+To create a new credential set, click + ADD and then select the type of credential set you’d like to store. Complete the following:
+
+- **CREDENTIAL STORE:** Select “Internal”, an integrated external Cypher store (if any), or an integrated Hashicorp Vault server (if any). See the section below for instructions on integrating with Vault or standing up and integrating with an external Cypher store.
+- **NAME:** A name for the credential set in VM Essentials
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **CREDENTIAL VALUES:** Depending on the credential pair type selected (listed above), the remaining fields will be specific to the chosen type. See the next section for a more complete walkthrough on storing and using OAuth 2.0 credentials
+
+![../../_images/addCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-6107BD26-E1BA-4F6E-888A-10CEDF3C01D7-high.png)
+
+Finally, click ADD CREDENTIALS. Once saved, the credential set will be available for selection where appropriate in VM Essentials UI. In the screenshot below, I’m integrating a new VMware Cloud. In the credentials section, I have the following options: Creating (and using) a new Username and Password credential set (which includes the option to save internally or to an external Cypher store), choosing a previously-stored credential set, or simply entering my credentials locally and not saving them for reuse.
+
+![../../_images/useCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-714A8DE9-4992-4DB9-B9E2-5CAAD363B7A2-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json b/corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
new file mode 100644
index 0000000..4813e3c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+  "title": "Creating Service Plans for GPU Hardware Passthrough",
+  "ordinal": 133,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md b/corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
new file mode 100644
index 0000000..d4723b4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
@@ -0,0 +1,7 @@
+# Creating Service Plans for GPU Hardware Passthrough
+
+When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
+
+To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
+
+![../../_images/gpuPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-FEF30612-0724-4835-9310-79D70E4641F1-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json b/corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
new file mode 100644
index 0000000..b14bfa5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+  "title": "Creating Wikis",
+  "ordinal": 18,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Wikis",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+        "clustering_title": "Creating Wikis"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+        "clustering_title": "Creating Wikis"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md b/corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
new file mode 100644
index 0000000..19e08cc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
@@ -0,0 +1,13 @@
+# Creating Wikis
+
+The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
+
+Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
+
+![create wiki](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4029426C-1AA2-4873-AE1C-CB4677EFB0F7-high.png)
+
+Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many VM Essentials constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
+
+IMPORTANT
+
+All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json b/corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
new file mode 100644
index 0000000..7eceb7e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+  "title": "Linux Settings",
+  "ordinal": 303,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md b/corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
new file mode 100644
index 0000000..5d892c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
@@ -0,0 +1,14 @@
+# Linux Settings
+
+When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Linux user
+- **Password:** The password that will be used with your Linux user (optional if specifying key)
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
+
+WARNING
+
+If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_linux_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-98554851-1F7D-4D05-A502-2FB93933551A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json b/corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
new file mode 100644
index 0000000..536e7ee
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+  "title": "Adding Network Groups",
+  "ordinal": 148,
+  "parent_title": "Network Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+        "clustering_title": "Adding Network Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+        "clustering_title": "Adding Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md b/corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
new file mode 100644
index 0000000..052ae19
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
@@ -0,0 +1,19 @@
+# Adding Network Groups
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks Groups
+2. Select ADD
+3. Enter the following: 
+
+   Group info:
+   :   - Name: Name of the Network Group in VM Essentials
+       - Description: Details of the Network Group in VM Essentials
+
+   Networks
+   :   - Search for and select target Networks for the Network Group
+       - Search for and select target Subnets for the Network Group
+
+   Group Access
+   :   - Set Group Access for the Network Group. Group access controls which Groups at provision time will have access to this resource. Select “all” (default) to give workloads provisioned to any Group access to this resource. If this resource should be restricted only to workloads provisioned to specific Groups, select all that apply.
+4. Select SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json b/corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
new file mode 100644
index 0000000..1e2b867
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+  "title": "System Status",
+  "ordinal": 8,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.html",
+  "topic_cluster": {
+    "clustering_title": "System Status",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+        "clustering_title": "System Status"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+        "clustering_title": "System Status"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md b/corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
new file mode 100644
index 0000000..b0d9d0d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
@@ -0,0 +1,3 @@
+# System Status
+
+System status gives a high-level view of the health of the appliance. More detailed information can be viewed on the appliance health detail page (Administration > Health) and a more detailed breakdown of the meaning of each status indicator is in [VM Essentials Health](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json b/corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
new file mode 100644
index 0000000..5bc47b5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+  "title": "Selecting a Domain while provisioning an Instance",
+  "ordinal": 165,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.html",
+  "topic_cluster": {
+    "clustering_title": "Selecting a Domain while provisioning an Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+        "clustering_title": "Selecting a Domain while provisioning an Instance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+        "clustering_title": "Selecting a Domain while provisioning an Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md b/corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
new file mode 100644
index 0000000..fdcd970
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
@@ -0,0 +1,6 @@
+# Selecting a Domain while provisioning an Instance
+
+## Procedure
+
+1. While creating an instance, in the Configure section, expand the DNS Options.
+2. Select Domain from the Domain dropdown.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json b/corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
new file mode 100644
index 0000000..aad5fd2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+  "title": "Adding Directory Pools",
+  "ordinal": 114,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Directory Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+        "clustering_title": "Adding Directory Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+        "clustering_title": "Adding Directory Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md b/corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
new file mode 100644
index 0000000..8cd00fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
@@ -0,0 +1,25 @@
+# Adding Directory Pools
+
+Before adding a Directory Pool, identify the path to be used as the datastore location. You may use an existing directory, or you may specify a desired path that doesn't yet exist. HPE Morpheus VM Essentials will handle creation of the directory (if necessary), changing its ownership, and defining the storage pool (along with configuring auto-start) all in the background.
+
+To create a new Directory Pool-type datastore:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. Select the Storage tab and the Datastores subtab
+4. Click ADD
+5. Configure the following:
+
+   1. **NAME:** An identifiable name for the datastore used throughout HPE Morpheus VM Essentials UI
+   2. **DIRECTORY:** Directory Pool
+   3. **TARGET PATH:** Your desired path (does not have to currently exist)
+   4. **IMAGE TARGET:** If selected, this datastore will be made available for storage of virtual images
+6. Click SAVE
+
+![The add directory pool modal](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-F74F45D1-59C7-4B4B-BCA2-726D24B4B76A-high.png)
+
+WARNING
+
+When Directory Pools are removed, the target directory is deleted along with all files contained within. Users should take care not to manually store additional files in Directory Pool-targeted directories as the files could be deleted if a datastore were removed.
+
+![The datastores list showing the newly-added directory pool](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-CA6224CA-4FD9-4E70-8FED-81234ABACC40-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json b/corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
new file mode 100644
index 0000000..c0c00a0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+  "title": "NFS Pools Overview",
+  "ordinal": 115,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.html",
+  "topic_cluster": {
+    "clustering_title": "NFS Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+        "clustering_title": "NFS Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+        "clustering_title": "NFS Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md b/corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
new file mode 100644
index 0000000..e42a1fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
@@ -0,0 +1,19 @@
+# NFS Pools Overview
+
+NFS Pools enable an HVM Cluster to use an NFS share as a datastore. The exact steps to configure the NFS share will depend on the storage system providing it, but this section will go over the requirements for creating a compatible share and for adding it to the HVM Cluster via the HPE Morpheus VM Essentials UI.
+
+Administrators only need to set up the NFS server, export the desired directories with the proper permissions and options, and ensure the hosts are able to reach it. HPE Morpheus VM Essentials handles everything else, including mounting directories to the filesystem and handling datastore creation.
+
+Compatible NFS shares must meet the following requirements:
+
+- NFS version 3 or 4
+- The share must allow read and write access
+- The share must be configured with the `no-root-squash` export option
+
+NOTE
+
+NFS version 4 is only supported on HPE Morpheus VM Essentials version 8.0.13 and higher. When using the Migrations feature to move VMware VMs to HVM Clusters targeting an NFS Pool datastore, NFS version 4 must be used.
+
+IMPORTANT
+
+The `no-root-squash` export option is required but typically not set by default. When `no-root-squash` is not set, requests from the NFS client are mapped to an anonymous user on the NFS server, which will result in permissions errors that do not allow the NFS Pool to function correctly. You must set this export option in the `/etc/exports` config file or in a management interface depending on the NFS storage system being utilized.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json b/corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
new file mode 100644
index 0000000..72ba774
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+  "title": "Creating a VM Essentials VMware Image",
+  "ordinal": 332,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a VM Essentials VMware Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+        "clustering_title": "Creating a VM Essentials VMware Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+        "clustering_title": "Creating a VM Essentials VMware Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md b/corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
new file mode 100644
index 0000000..9495c81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
@@ -0,0 +1,7 @@
+# Creating a VM Essentials VMware Image
+
+VM Essentials comes out of the box with a default set of blueprints for use in many modern deployment scenarios. These consist mostly of base operating system images with a few additional adjustments. These adjustments typically include the addition of cloud-init (which is highly recommended to be used in most environments, but not mandatory). However, in many on-premise deployments there are custom image requirements as well as networking requirements. This guide will go over how to create a VMware Images for use within VM Essentials.
+
+NOTE
+
+A VM Essentials appliance may have many vCenter Clouds tied to any number of vCenter appliances. If the same images need to be available to multiple vCenter Clouds, you will need to download the OVF from one vCenter and upload it into the others. At that point you can make multiple VM Essentials Node Types from the images and it will be available to all needed vCenter Clouds. This is a vCenter limitation but one which may not be obvious when provisioning via VM Essentials.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json b/corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
new file mode 100644
index 0000000..afc30a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+  "title": "Library",
+  "ordinal": 51,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
+  "topic_cluster": {
+    "clustering_title": "Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md b/corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
new file mode 100644
index 0000000..c65ee1c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
@@ -0,0 +1,7 @@
+# Library
+
+**Subtopics**  
+
+- **[Labels](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.html)**
+- **[Automation](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json b/corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
new file mode 100644
index 0000000..53cb62f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+  "title": "Creating Clouds",
+  "ordinal": 92,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+        "clustering_title": "Creating Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+        "clustering_title": "Creating Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md b/corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
new file mode 100644
index 0000000..7b2edac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
@@ -0,0 +1,3 @@
+# Creating Clouds
+
+Clouds can be added from Infrastructure > Clouds or in Infrastructure > Groups > (selected Group) > Clouds. A more detailed guide to adding a VMware vCenter Cloud can be found in the vCenter integration guide. The other available Cloud type, known as Private Cloud, is a generic Cloud type that doesn’t directly integrate with any other technology as the vCenter Cloud type does. Instead Private Cloud-type Clouds are used to house your HVM clusters. Make as many Private Cloud-type Clouds as needed to organize your HVM clusters properly.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json b/corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
new file mode 100644
index 0000000..814574c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+  "title": "Backups",
+  "ordinal": 210,
+  "parent_title": "Backups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md b/corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
new file mode 100644
index 0000000..382ce5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
@@ -0,0 +1,11 @@
+# Backups
+
+In the Backups > Backups section, currently-configured Backups can be viewed and managed, and new Instance, Host and Provider backups be configured. Backups must be tied to a Backup Job, which holds the retention count and the schedule on which the backup should automatically be run. You can create a new Job at the same time as the backup is created or you can create the job ahead of time and associate any new backups to the existing job.
+
+NOTE
+
+Role permissions for Backups determine which backups will be accessible to the individual user.
+
+**Subtopics**  
+
+- **[Create an Instance Backup](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9DA38943-BF95-446D-AB09-32323160D51B.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json b/corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
new file mode 100644
index 0000000..27d875c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+  "title": "Deleting Existing Routers",
+  "ordinal": 153,
+  "parent_title": "Routers",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Existing Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+        "clustering_title": "Deleting Existing Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+        "clustering_title": "Deleting Existing Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md b/corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
new file mode 100644
index 0000000..a3b5ee5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
@@ -0,0 +1,7 @@
+# Deleting Existing Routers
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the trash can icon for the appropriate router
+3. Acknowledge the pop-up banner ensuring you wish to delete the router
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json b/corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
new file mode 100644
index 0000000..24be1c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+  "title": "VM Essentials Backup Settings",
+  "ordinal": 286,
+  "parent_title": "Backup Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.html",
+  "topic_cluster": {
+    "clustering_title": "VM Essentials Backup Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+        "clustering_title": "VM Essentials Backup Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+        "clustering_title": "VM Essentials Backup Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md b/corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
new file mode 100644
index 0000000..6ab313c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
@@ -0,0 +1,25 @@
+# VM Essentials Backup Settings
+
+Scheduled Backups
+:   Enable automatic scheduled backups for provisioned instances
+
+Create Backups
+:   When enabled, VM Essentials will automatically configure instances for manual or scheduled backups
+
+Backup Appliance
+:   When enabled, a backup will be created for the VM Essentials appliance database. Select the `Backup` text link to view or edit settings related to the appliance backup
+
+Default Backup Bucket
+:   Select an existing bucket as the default for future backup runs. Click the `Infrastructure Storage` text link to add a new storage bucket to VM Essentials if needed
+
+Default Backup Schedule
+:   Choose a default schedule interval for automated backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
+
+Default Backup Retention
+:   Choose the default number of backups to be retained for automated Instance and appliance backup jobs
+
+Default Synthetic Full Backup enabled
+:   When enabled, full synthetic backups will be on by default in addition to standard backups for supported workload types
+
+Default Synthetic Full Backup Schedule
+:   Choose a default schedule interval for full synthetic backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json b/corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
new file mode 100644
index 0000000..2bd81a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+  "title": "Roles and Identity Sources",
+  "ordinal": 247,
+  "parent_title": "Roles",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.html",
+  "topic_cluster": {
+    "clustering_title": "Roles and Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+        "clustering_title": "Roles and Identity Sources"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+        "clustering_title": "Roles and Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md b/corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
new file mode 100644
index 0000000..d1711d8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
@@ -0,0 +1,3 @@
+# Roles and Identity Sources
+
+It is very common for large Enterprises to have an existing identity source that they would like to plug in to VM Essentials for authentication. This includes services like LDAP, Active Directory, OKTA, Jump Cloud, One Login, and SAML. When using these services it becomes important to configure a role mapping between the VM Essentials role assignments to the equivalent identity source groups/roles the user belongs to. This is configurable within the identity source management UI. Sections are provided allowing things like LDAP groups to be directly mapped to specific roles within VM Essentials. If a user matches more than one LDAP/role group then both sets of roles are applied to the user automatically. Configuring Identity Sources is done in Administration > Users. Additionally, administrators may opt to lock users to their mapped role in VM Essentials or keep the roles unlocked to manually administer roles in one-off scenarios. See the docs section dedicated to identity sources for more information on configuring the specific SSO technologies VM Essentials supports.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json b/corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
new file mode 100644
index 0000000..50cd29e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+  "title": "Roles",
+  "ordinal": 244,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md b/corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
new file mode 100644
index 0000000..fe9e3e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
@@ -0,0 +1,7 @@
+# Roles
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.html)**
+- **[Roles and Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.html)**
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json b/corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
new file mode 100644
index 0000000..852f944
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+  "title": "Tagging and Metadata",
+  "ordinal": 324,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.html",
+  "topic_cluster": {
+    "clustering_title": "Tagging and Metadata",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+        "clustering_title": "Tagging and Metadata"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+        "clustering_title": "Tagging and Metadata"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md b/corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
new file mode 100644
index 0000000..55a2a77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
@@ -0,0 +1,13 @@
+# Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json b/corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
new file mode 100644
index 0000000..ad146c1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+  "title": "User Process Guides",
+  "ordinal": 307,
+  "parent_title": "Guides",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.html",
+  "topic_cluster": {
+    "clustering_title": "User Process Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+        "clustering_title": "User Process Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+        "clustering_title": "User Process Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md b/corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
new file mode 100644
index 0000000..708570d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
@@ -0,0 +1,5 @@
+# User Process Guides
+
+**Subtopics**  
+
+- **[Backing Up and Restoring the HPE Morpheus VM Essentials Manager](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json b/corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
new file mode 100644
index 0000000..aed4d6c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+  "title": "Failover",
+  "ordinal": 128,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.html",
+  "topic_cluster": {
+    "clustering_title": "Failover",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+        "clustering_title": "Failover"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+        "clustering_title": "Failover"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md b/corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
new file mode 100644
index 0000000..7b69966
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
@@ -0,0 +1,15 @@
+# Failover
+
+HVM clusters support automatic failover of running workloads in the event of the loss of a host. Administrators can control the failover behavior through the “Manage Placement” action on any running VM. From the VM detail page, click ACTIONS and select “Manage Placement”. Any VM with a placement strategy of “Auto” or “Failover” will be eligible for an automatic move in the event its host is lost. When the loss of a host does occur, the workload will be up and running from a different cluster host within just a short time if it’s configured to be moved during an automatic failover event. Any VMs pinned to a lost host will not be moved and will not be accessible if the host is lost. When the host is restored, those VMs will be in a stopped state and may be restarted if needed.
+
+![../../_images/threeRunningWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-D85300D8-59A9-406D-99F4-2A83E4812C52-high.png)
+
+Each of these VMs is configured for a different failover strategy. When the host is lost, we should expect to see the first two VMs moved to an available host (since they have the “Auto” and “Failover” placement strategies, respectively). We should not see the third VM moved.
+
+![../../_images/auto.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4AF17304-D863-46CD-B761-F76CA83B5DA1-high.png) ![../../_images/failover.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-450A2043-9995-4352-B52F-0D85D7A9500E-high.png) ![../../_images/pinned.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-3C5798EF-8010-4C2C-A9C1-B1A07D5BBCE3-high.png)
+
+After loss of the host these three VMs were running on, we can see the lost host still has one associated VM in a stopped state. The other two VMs are running on a second host which is still available.
+
+![../../_images/lostNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-69BB84AC-5461-4818-A90F-10BB7308E937-high.png) ![../../_images/liveNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-688399E1-CBDA-4B89-AC61-80CF6FCBEBCD-high.png)
+
+When the lost host returns, the moved VMs will come back to their original host. The third VM is associated with this host as well and is in a stopped state until it is manually restarted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json b/corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
new file mode 100644
index 0000000..f7fabd0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+  "title": "Advanced",
+  "ordinal": 327,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-1EB800EB-6832-487E-BB11-07D8520003CF.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+        "clustering_title": "Advanced"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+        "clustering_title": "Advanced"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md b/corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
new file mode 100644
index 0000000..69d8995
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
@@ -0,0 +1,11 @@
+# Advanced
+
+There are several advanced features provided within VM Essentials that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the VM Essentials appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires VM Essentials v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in VM Essentials via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via VM Essentials. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json b/corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
new file mode 100644
index 0000000..ef1a96c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+  "title": "Overview",
+  "ordinal": 315,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md b/corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
new file mode 100644
index 0000000..956d25f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
@@ -0,0 +1,3 @@
+# Overview
+
+VMware is a very common cloud integration choice supported by VM Essentials . They have provided a top notch virtualization solution and one might argue pioneered the virtualization space altogether. As such, many companies utilize this technology and all the features that come with it, so VM Essentials covers a broad feature set in vCenter.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json b/corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
new file mode 100644
index 0000000..3dcc1ff
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+  "title": "Allow Custom Config",
+  "ordinal": 62,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.html",
+  "topic_cluster": {
+    "clustering_title": "Allow Custom Config",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+        "clustering_title": "Allow Custom Config"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+        "clustering_title": "Allow Custom Config"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md b/corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
new file mode 100644
index 0000000..8ea4c3e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
@@ -0,0 +1,9 @@
+# Allow Custom Config
+
+When “Allow Custom Config” is marked on a Task, the user is shown a text area for custom configuration when the Task is executed manually from the Tasks List Page. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+**Subtopics**  
+
+- **[Example JSON Map:](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.html)**
+- **[Task Types](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.html)**
+- **[Task Management](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json b/corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
new file mode 100644
index 0000000..68230f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+  "title": "Appliance Settings",
+  "ordinal": 266,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+        "clustering_title": "Appliance Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+        "clustering_title": "Appliance Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md b/corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
new file mode 100644
index 0000000..6c34e94
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
@@ -0,0 +1,59 @@
+# Appliance Settings
+
+Appliance URL
+:   The default URL used for Agent install and Agent functionality. All Instances and Hosts must be able to resolve and reach this URL over 443 for successful agent install and communication.
+
+NOTE
+
+Alternate Appliance URLs can be configured per Cloud in the Edit Cloud  >  Advanced Options section.
+
+Internal Appliance URL (PXE)
+:   For PXE-Boot your appliance needs to be routable directly with minimal NAT masquerading. This allows one to override the default appliance url endpoint for use by the PXE Server. If this is unset, the default appliance url will be used instead.
+
+API Allowed Origins
+:   A CORS-related field which specifies the origins that are allowed to access the VM Essentials API. For example, if you were designing a web application which needed to make AJAX calls to VM Essentials API. The origins should be specified here. By default, all origins are allowed. When this field is filled, an exclusive whitelist of allowed origins is established.
+
+Cloud Sync Interval
+:   Data is refreshed through cloud integrations at the interval specified here in seconds, the default value is 300 seconds (five minutes). Appliances managing a very large number of clouds may be adversely affected by setting this value too low.
+
+Cluster Sync Interval
+:   Data is refreshed through provisioned Clusters at the interval specified here in seconds, the default value is 60 seconds. Appliances managing a very large number of Clusters may be adversely affected by setting this value too low.
+
+Usage Retainment
+:   Determines how many days to keep account usage (metered costing data) records. Retainment period is not set by default. Usage records will remain indefinitely if Usage Retainment is not set. Note this does not affect generated Invoice records.
+
+Invoice Retainment
+:   Enter the number of days VM Essentials should keep invoice records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large invoice database tables can affect the stability of the application.
+
+Incident Retainment
+:   Enter the number of days VM Essentials should keep incident records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large incident database tables can affect the stability of the application.
+
+Stats Retainment
+:   Select 30, 60 or 90 days period for stats retainment. Selecting a larger period gives the ability to analyze stats, such as Instance metrics, over a longer period of time. For example, in the Monitoring tab of an Instance detail page, users can select a 60 or 90-day analysis period if the stats have been retained that long
+
+Denied Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which should not be allowed sources for HTTP Tasks or REST-populated Option Lists.
+
+Approved Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which are the only approved sources for HTTP Tasks or REST-populated Option Lists. By entering any values here, all others are automatically denied.
+
+Exchange URL
+:   Enter the URL which should be checked for updates to any installed plugins. The default exchange is: `https://share.morpheusdata.com`
+
+Skip Agent Install
+:   For appliances in which skipping the Agent install is the default selection, enable this global flag to default to skipping the Agent install during provisioning
+
+Enable SSL Verification of Agent (Communications)
+:   Enabling SSL Verification of Agent Communications requires a valid Certificate be installed on the Appliance.
+
+Disable SSH Password Authentication
+:   Only allow ssh login using SSH keys. When true, SSH Password Authentication will not be enabled for VM’s and Hosts provisioned after the setting is enabled.
+
+Default Appliance Locale
+:   Sets the default language and region for all users on the VM Essentials appliance. Users with individual language preferences may also override this selection on their User Settings page
+
+Default Console Gateway
+:   Select a configured VM Essentials Worker as a console gateway or VDI gateway. For more on installation and configuration of a gateway, see the [VDI Gateways section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html#vdi-gateways) of VM Essentials documentation.
+
+Max Option List Size
+:   Sets a maximum size for Option Lists (such as those sourced from REST calls to a remote server) to preserve appliance performance in the event that a very large payload is inadvertently accessed. The entered number is multiplied by 1000 (for example, entering “1” results in a maximum list size of 1000).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json b/corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
new file mode 100644
index 0000000..ea13c03
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+  "title": "Create User",
+  "ordinal": 253,
+  "parent_title": "Users",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-21972435-BFD0-481F-A3E6-A52B116989F3.html",
+  "topic_cluster": {
+    "clustering_title": "Create User",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+        "clustering_title": "Create User"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+        "clustering_title": "Create User"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md b/corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
new file mode 100644
index 0000000..c498f3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
@@ -0,0 +1,52 @@
+# Create User
+
+## About this task
+
+Users are created in Administration > Users.
+
+NOTE
+
+Authorized Identity Source Users will be automatically created upon first sign in.
+
+To create a User:
+
+## Procedure
+
+1. Navigate to Administration > Users
+2. Select + CREATE USER.
+3. From the New User Wizard input: 
+
+   Username & Email
+   :   - First Name
+       - Last Name
+       - Username
+       - Email address
+
+   Receive Notifications
+   :   Enable to receive provisioning email notifications.
+
+   Roles
+   :   Role(s) to be inherited by the user. If multiple roles are selected, the higher permission levels of one role will override the other role(s). See the Roles section of this documentation for more information on stacking Roles and specific Role permissions.
+
+   Password
+   :   Password must contain at least one uppercase letter, one lowercase letter, a number, and a symbol.
+
+   Enabled
+   :   If unchecked, the user will no longer be able to sign into VM Essentials, but their user data will remain.
+
+   Account Locked
+   :   This box is checked when a User has tried unsuccessfully to log in too many times. An administrator will need to uncheck this box in order for the User to be able to make another login attempt.
+
+   Password Expired
+   :   If enabled, the User will be forced to create a new password upon next login. The expired password cannot be used again.
+
+   Linux Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Linux Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this VM Essentials user is a member of.
+
+   Windows Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Windows Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this VM Essentials user is a member of.
+
+       IMPORTANT
+
+       Please ensure password entered is allowable by Windows.
+4. Select SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json b/corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
new file mode 100644
index 0000000..1831a88
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+  "title": "Viewing Volumes",
+  "ordinal": 375,
+  "parent_title": "Volumes tab",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing Volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+        "clustering_title": "Viewing Volumes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+        "clustering_title": "Viewing Volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md b/corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
new file mode 100644
index 0000000..4996357
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
@@ -0,0 +1,21 @@
+# Viewing Volumes
+
+The Volumes tab provides a list of all volumes, including their summary, capacity information, and ransomware monitoring status.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server name.
+3. Select the Volumes tab. You can view the following information:
+   - **Name**: Displays the volume name for the VM.
+   - **Details**: Displays the CD Drive volume or data disk associated with the VM name.
+   - **Usage**: Displays a progress bar. The progress bar displays:
+     - Used capacity in percentage.
+     - Used capacity in either GiB or TiB, based on its value, in comparison to the total capacity.
+   - **Ransomware Monitoring**: Indicates whether ransomware monitoring is enabled or disabled for the volume. Ransomware monitoring is enabled or disabled while creating the datastore.
+
+     NOTE
+
+     Once ransomware monitoring is enabled for a datastore, the ransomware monitoring status cannot be edited​.
+   - **IOPS**: Displays the number of read and write operations performed by the volume each second.
+   - **Throughput**: Displays the amount of data transferred to or from the volume each second.
+
+   ![Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-8E25EA50-EEC7-48EA-8FCF-973EB252A822-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json b/corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
new file mode 100644
index 0000000..c70fef6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+  "title": "Base Cluster Details",
+  "ordinal": 104,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.html",
+  "topic_cluster": {
+    "clustering_title": "Base Cluster Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+        "clustering_title": "Base Cluster Details"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+        "clustering_title": "Base Cluster Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md b/corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
new file mode 100644
index 0000000..2535803
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
@@ -0,0 +1,8 @@
+# Base Cluster Details
+
+An HVM cluster using the hyperconverged infrastructure (HCI) Layout consists of at least three hosts. Physical hosts are recommended to experience full performance of the solution. In smaller environments, it is possible to create an HVM cluster with three nested virtual machines, a single physical host (non-HCI only), or a single nested virtual machine (non-HCI only) though performance may be reduced. With just one host it won’t be possible to migrate workloads between hosts or take advantage of automatic failover. Currently, the default cluster layout requires hosts be a pre-existing Ubuntu 24.04 box with environment and host system requirements described in this section. An earlier cluster layout requiring Ubuntu 22.04 is also included. VM Essentials handles cluster configuration by providing the IP address(es) for your host(s) and a few other details. Details on adding the cluster to VM Essentials are contained in the next section.
+
+**Subtopics**  
+
+- **[Hardware Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-634760AA-7E46-42A7-AD08-85CCE4656873.html)**
+- **[Example Cluster Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json b/corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
new file mode 100644
index 0000000..fa0b9cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+  "title": "Overview",
+  "ordinal": 155,
+  "parent_title": "IP Pools",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-238F9226-4EB4-4E14-B533-584277951C4B.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md b/corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
new file mode 100644
index 0000000..1c16721
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
@@ -0,0 +1,3 @@
+# Overview
+
+The IP Pools tab in the Networks section allows you to create HVM-type IP Pools (which is an IP address range VM Essentials can use to assign available static IP addresses to Instances) and NSX IP Pools. The IP Pool section also displays pools synced from IPAM integrations like Infoblox, Bluecat and others.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json b/corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
new file mode 100644
index 0000000..1180ef8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+  "title": "Review",
+  "ordinal": 23,
+  "parent_title": "Activity",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.html",
+  "topic_cluster": {
+    "clustering_title": "Review",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+        "clustering_title": "Review"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+        "clustering_title": "Review"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md b/corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
new file mode 100644
index 0000000..8fcfbfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
@@ -0,0 +1,7 @@
+# Review
+
+To review the item that generated the activity, click the name of the activity and it will go to a new page and display that item. The list of activity can be filtered by type, user or date range.
+
+NOTE
+
+Deleted activities are displayed as an alert and do not contain a link to the event item. If the activity is not a deletion event we provide a link on the activity name to go to the item the activity occurred on. Delete activity alerts are shown for Instances, servers, Clouds, and Groups.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json b/corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
new file mode 100644
index 0000000..460f0ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+  "title": "Cluster Permissions",
+  "ordinal": 99,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+        "clustering_title": "Cluster Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+        "clustering_title": "Cluster Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md b/corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
new file mode 100644
index 0000000..f3086d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
@@ -0,0 +1,3 @@
+# Cluster Permissions
+
+Each Cluster has Group and Service Plan access permissions settings (Gear icon > Permissionsfrom the Clusters list page).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json b/corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
new file mode 100644
index 0000000..0d20357
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+  "title": "Cypher",
+  "ordinal": 213,
+  "parent_title": "Tools",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html",
+  "topic_cluster": {
+    "clustering_title": "Cypher",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md b/corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
new file mode 100644
index 0000000..55e649b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
@@ -0,0 +1,15 @@
+# Cypher
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.html)**
+- **[Mountpoints](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.html)**
+- **[Creating Cypher Keys](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.html)**
+- **[Password](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.html)**
+- **[tfvars](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.html)**
+- **[Secret](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.html)**
+- **[UUID](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.html)**
+- **[Key](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.html)**
+- **[Vault](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.html)**
+- **[Editing Cypher Keys](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.html)**
+- **[Using Cypher Keys in Scripts](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json b/corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
new file mode 100644
index 0000000..5310984
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+  "title": "Gotchas",
+  "ordinal": 345,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.html",
+  "topic_cluster": {
+    "clustering_title": "Gotchas",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+        "clustering_title": "Gotchas"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+        "clustering_title": "Gotchas"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md b/corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
new file mode 100644
index 0000000..88824c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
@@ -0,0 +1,5 @@
+# Gotchas
+
+SELinux can cause issues with cloud-init when in enforced mode. It may be advisable to set this to permissive unless it is mandatory within your organization to use an enforced SELinux configuration. If that is the case please see the documentation for the cloud\_init\_t security policies.
+
+Network Manager will also prevent the required restart of the Network Service when assigning static IP’s. Disable Network Manager when possible or Static IP assignment may not work until the Network Service is restarted manually.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json b/corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
new file mode 100644
index 0000000..47d27d5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+  "title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "ordinal": 308,
+  "parent_title": "User Process Guides",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.html",
+  "topic_cluster": {
+    "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+        "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+        "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md b/corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
new file mode 100644
index 0000000..cab9c14
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
@@ -0,0 +1,17 @@
+# Backing Up and Restoring the HPE Morpheus VM Essentials Manager
+
+NOTE
+
+In the event of a total system failure (full crash), the recovery process requires the user to provision a new, freshly installed VME Manager. You cannot perform this recovery on a partially configured or corrupted appliance. The recovery process involves following:
+
+- Provision the replacement VME Manager
+- Transfer and restore security keys
+- Database injection and reconfiguration
+- Verifying the restored VME Manager
+
+**Subtopics**  
+
+- **[Create A Backup Job](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.html)**
+- **[Integrate a Bucket or File Share](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.html)**
+- **[Configuring HPE Morpheus Enterprise Appliance Backup](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D647F00D-6B45-4E18-B442-14835847EFA7.html)**
+- **[Restoring the HPE Morpheus Enterprise Manager from Backup](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json b/corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
new file mode 100644
index 0000000..0848fe7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+  "title": "Overview",
+  "ordinal": 252,
+  "parent_title": "Users",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md b/corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
new file mode 100644
index 0000000..03960d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
@@ -0,0 +1,16 @@
+# Overview
+
+The Users page displays a list of all Users. The following fields are surfaced for each User:
+
+- Display Name
+- Username
+- Email
+- Role
+
+Users which are grayed out in the list are currently inactive and cannot log in. The pencil and trash icons at the end of each row allow for editing or deleting Users. Click MORE to see the “impersonate” button. This allows administrators to impersonate any User, which may help confirm their Role permissions meet and do not exceed the desired result.
+
+Click on the hyperlinked Display Name of the User to see a page detailing their effective Role permissions. This is especially useful for Users in multiple Roles where it might otherwise be difficult to determine their exact rights. This page looks identical to a User Role detail page except none of the fields are editable. Edit the User Role permissions for the User if changes need to be made.
+
+NOTE
+
+Some User data created through an Identity Source integration (such as Active Directory) is not editable in VM Essentials, as it is synced from the Identity Source.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json b/corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
new file mode 100644
index 0000000..eedc8c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+  "title": "Setting Up Two-Factor Authentication",
+  "ordinal": 299,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.html",
+  "topic_cluster": {
+    "clustering_title": "Setting Up Two-Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+        "clustering_title": "Setting Up Two-Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+        "clustering_title": "Setting Up Two-Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md b/corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
new file mode 100644
index 0000000..17014b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
@@ -0,0 +1,7 @@
+# Setting Up Two-Factor Authentication
+
+When two-factor authentication isn’t yet set up, this section contains a single button: ENABLE 2FA. To get started, click this button and VM Essentials will prompt for your password. After entering the password, you’ll be shown a QR code which can be scanned into your authenticator application of choice. Once the QR code is shown, 2FA is active and the supplemental code will need to be entered each time the user logs in.
+
+![../../_images/2fa_qr.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-B46B6795-F044-4E76-BEB1-3A96F5575CE6-high.png)
+
+On subsequent login attempts, the user will be prompted to enter a 2FA code after successful entry of the username and password. Retrieve this code from the 2FA app you set up in the prior section and enter it to complete the login process.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json b/corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
new file mode 100644
index 0000000..670ae98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+  "title": "Performing Instance Actions",
+  "ordinal": 49,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.html",
+  "topic_cluster": {
+    "clustering_title": "Performing Instance Actions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+        "clustering_title": "Performing Instance Actions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+        "clustering_title": "Performing Instance Actions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md b/corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
new file mode 100644
index 0000000..939fc3e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
@@ -0,0 +1,7 @@
+# Performing Instance Actions
+
+## Procedure
+
+1. Select the Provisioning link in the navigation bar.
+2. From the Instances list, select the desired Instance.
+3. Click the Actions dropdown button and select an Action.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json b/corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
new file mode 100644
index 0000000..ccd199c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+  "title": "Overview",
+  "ordinal": 81,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md b/corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
new file mode 100644
index 0000000..c0719a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
@@ -0,0 +1,14 @@
+# Overview
+
+## About this task
+
+Groups in VM Essentials define the available resources for each user. Group access is defined by Roles. Clouds are added to Groups, and a User can only access the Clouds associated with Groups in their Role. Resources such as networks, datastores, resource pools, and folders have additional Group access settings.
+
+The Groups list page displays all current groups, which can be filtered by applied Labels or by simple search. Existing Groups can be edited here and new Groups can be created.
+
+To View Groups:
+
+## Procedure
+
+1. Hover over the Infrastructure link in the menu bar
+2. Click the Groups link
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json b/corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
new file mode 100644
index 0000000..1569ab1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+  "title": "Tools",
+  "ordinal": 212,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html",
+  "topic_cluster": {
+    "clustering_title": "Tools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md b/corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
new file mode 100644
index 0000000..815329b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
@@ -0,0 +1,7 @@
+# Tools
+
+**Subtopics**  
+
+- **[Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html)**
+- **[Archives](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html)**
+- **[Migrations](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json b/corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
new file mode 100644
index 0000000..fd5b7bc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+  "title": "Task Executions",
+  "ordinal": 14,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.html",
+  "topic_cluster": {
+    "clustering_title": "Task Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+        "clustering_title": "Task Executions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+        "clustering_title": "Task Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md b/corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
new file mode 100644
index 0000000..2c67d7c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
@@ -0,0 +1,3 @@
+# Task Executions
+
+Displays the number of successful and unsuccessful Task executions over the last day, week or month
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json b/corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
new file mode 100644
index 0000000..c8c55a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+  "title": "Handling User Lock-Out",
+  "ordinal": 301,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.html",
+  "topic_cluster": {
+    "clustering_title": "Handling User Lock-Out",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+        "clustering_title": "Handling User Lock-Out"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+        "clustering_title": "Handling User Lock-Out"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md b/corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
new file mode 100644
index 0000000..99c89c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
@@ -0,0 +1,3 @@
+# Handling User Lock-Out
+
+If a user loses the device they’ve configured for authentication or if they cannot proceed through 2FA login for any other reason, an administrator should impersonate the user’s account, reset their password, disable 2FA, then share the new temporary password with the user. At that point, the user can login, reset their password to something more secure, and re-enable 2FA (if desired).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json b/corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
new file mode 100644
index 0000000..01e0527
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+  "title": "Prerequisites",
+  "ordinal": 351,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md b/corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
new file mode 100644
index 0000000..706f9f4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
@@ -0,0 +1,11 @@
+# Prerequisites
+
+- A pair of ArubaCX 8325 series switches
+- All the hosts in the Cluster are connected to these pair of switches
+- REST API access to the ArubaCX switches with administrative rights
+- User credentials for the ArubaCX switch pair with API access granted and read/write access to the switch configuration
+
+**Subtopics**  
+
+- **[Server Network Configuration (Netplan)](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-392743FA-D99D-4995-A8F6-3E5541271263.html)**
+- **[Switch Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json b/corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
new file mode 100644
index 0000000..3dfae99
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+  "title": "Backups",
+  "ordinal": 284,
+  "parent_title": "Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md b/corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
new file mode 100644
index 0000000..fcdf249
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
@@ -0,0 +1,5 @@
+# Backups
+
+**Subtopics**  
+
+- **[Backup Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3A5066B9-898A-4673-A713-C3E41D502742.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json b/corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
new file mode 100644
index 0000000..93488af
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+  "title": "Adding Domains",
+  "ordinal": 159,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+        "clustering_title": "Adding Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+        "clustering_title": "Adding Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md b/corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
new file mode 100644
index 0000000..0c6aa34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
@@ -0,0 +1,51 @@
+# Adding Domains
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Domains
+2. Select + ADD
+3. Enter the following: 
+
+   Domain Name
+   :   Ex. demo.example.com
+
+   Description
+   :   Descriptive metadata for use in VM Essentials
+
+   Display Name
+   :   Overrides the displayed name in domain selection components, which is useful when using many OU paths
+
+   Public Zone
+   :   Check for Public Zones, leave uncheck for Private Zones
+
+   Workflow
+   :   Select an existing Workflow which will be applied to Instances at provision time when they are associated with the domain. This is useful for any domain-related scripting you may currently use. For example, you may want to ensure a machine is removed from the domain when it’s torn down which could be accomplished by creating a Provisioning Workflow (with teardown phase Tasks) and associating the Workflow with the domain
+
+   Active
+   :   Active Domains are available for selection in Domain selection fields across VM Essentials. Inactive Domains are removed from Domain selection fields.
+
+   Join Domain Controller
+   :   Enable to have Windows instances join a Domain
+
+   Username
+   :   Admin user for Domain. `domain\username` format required when specifying OU Path
+
+   Password
+   :   Password for DC user account
+
+   DC Server
+   :   (optional) Specify the URL or Path of the DC Server
+
+   OU Path
+   :   (optional) Enter the OU Path for the connection string.
+
+   Guest Username
+   :   (optional) If set, this will change the provisioned hosts RPC Service User after domain join. Useful when a domain policy disables the Administrator account that typically would be set as the RPC user on a host record. VM Essentials will update the RPC username and password on the host(s) record after domain join with the specified Guest Username and Guest Password. The RPC username and password are used for auth during Remote Procedure Call (RPC) executions over winrm, ssh and guest tools.
+
+   Guest Password
+   :   (optional) The password for the Guest User account indicated in the prior field
+4. Click Save Changes
+
+## Results
+
+The Domain has been added and will be selectable in the Domain dropdown during provisioning, and in Cloud and Network settings.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json b/corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
new file mode 100644
index 0000000..8a8ee24
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+  "title": "Role Requirements",
+  "ordinal": 175,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.html",
+  "topic_cluster": {
+    "clustering_title": "Role Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+        "clustering_title": "Role Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+        "clustering_title": "Role Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md b/corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
new file mode 100644
index 0000000..0776daf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
@@ -0,0 +1,3 @@
+# Role Requirements
+
+There are two Role permissions for the Infrastructure > Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage gives Full, Read or No access to the Infrastructure > Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json b/corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
new file mode 100644
index 0000000..e1a3ed8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+  "title": "SSH/Winrm",
+  "ordinal": 35,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.html",
+  "topic_cluster": {
+    "clustering_title": "SSH/Winrm",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+        "clustering_title": "SSH/Winrm"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+        "clustering_title": "SSH/Winrm"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md b/corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
new file mode 100644
index 0000000..72512e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
@@ -0,0 +1,6 @@
+# SSH/Winrm
+
+**Subtopics**  
+
+- **[Linux Agent](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.html)**
+- **[Windows Agent](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9969BD6B-639D-4633-B825-79578464E8E6.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json b/corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
new file mode 100644
index 0000000..d9203a4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+  "title": "Proxy Settings",
+  "ordinal": 271,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.html",
+  "topic_cluster": {
+    "clustering_title": "Proxy Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+        "clustering_title": "Proxy Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+        "clustering_title": "Proxy Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md b/corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
new file mode 100644
index 0000000..34a07f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
@@ -0,0 +1,17 @@
+# Proxy Settings
+
+The VM Essentials Appliance can be configured to communicate through a Proxy server for Cloud API’s and Agent communication back to the Appliance.
+
+NOTE
+
+Additional Proxy configuration is available in the Infrastructure  >  Network  >  Proxies section. Added Proxies can be scoped to Clouds in the Edit Cloud  >  Advanced Options section of the Cloud.
+
+Add a Global Proxy server by entering the following:
+
+- Proxy Host
+- Proxy Port
+- Proxy User
+- Proxy Password
+- Proxy Domain
+- Proxy Workstation
+- No Proxy
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json b/corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
new file mode 100644
index 0000000..6d36190
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+  "title": "Overview",
+  "ordinal": 158,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md b/corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
new file mode 100644
index 0000000..04a66be
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
@@ -0,0 +1,12 @@
+# Overview
+
+The Domains section is for creating and managing domains for use in VM Essentials. Domains are used for setting FQDNs, joining Domains, and creating DNS records. The Domains section is also a multi-tenant endpoint for managing domain settings across multiple tenants.
+
+- Domains are synced in from Cloud, DNS and Network Integrations. Domains can also be user created.
+- Active Domains are available for selection in the Domain dropdown when provisioning an Instance
+- Default Domains can be set for Clouds and Networks in their Advanced Options sections.
+- Images can be flagged to Auto-Join Domains in the Infrastructure  >  Network  >  Domains section
+
+IMPORTANT
+
+For an Instance to auto-join a Domain, a Domain must set in the Advanced Options section of the Cloud or Network used when provisioning
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json b/corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
new file mode 100644
index 0000000..333325e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+  "title": "Service Plans",
+  "ordinal": 320,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-30353E6D-5FA2-470C-BB80-238663945F6F.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+        "clustering_title": "Service Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+        "clustering_title": "Service Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md b/corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
new file mode 100644
index 0000000..a88aee9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
@@ -0,0 +1,3 @@
+# Service Plans
+
+A default set of Service Plans are created in VM Essentials for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json b/corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
new file mode 100644
index 0000000..f91f053
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+  "title": "File Detail Page",
+  "ordinal": 230,
+  "parent_title": "Archives",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.html",
+  "topic_cluster": {
+    "clustering_title": "File Detail Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+        "clustering_title": "File Detail Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+        "clustering_title": "File Detail Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md b/corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
new file mode 100644
index 0000000..9c4efb3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
@@ -0,0 +1,3 @@
+# File Detail Page
+
+The File Detail Page contains details about the file itself as well as private and public (if available) URLs. In the lower section are three tabs. The Links tab contains any download links which have been generated (both active and expired). The History tab contains historical information about the file including creation and deletion of download links and download events. The scripts tab contains a guide for getting started using Archive-stored files in scripts.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json b/corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
new file mode 100644
index 0000000..6256bdb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+  "title": "Features",
+  "ordinal": 316,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md b/corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
new file mode 100644
index 0000000..f36ee84
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
@@ -0,0 +1,25 @@
+# Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+- Metadata tag sync
+
+On top of all these features, VM Essentials also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json b/corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
new file mode 100644
index 0000000..bbd4f11
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+  "title": "Features",
+  "ordinal": 358,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md b/corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
new file mode 100644
index 0000000..20767e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
@@ -0,0 +1,8 @@
+# Features
+
+- Create and delete networks of type `HPE ANW DSS Port Group` directly from the integration
+- Automatically create and delete networks in Aruba Fabric Composer (AFC) when HVM hosts are added or removed from the HVM cluster
+- Manage network configurations through seamless integration with AFC
+- Enable both micro-segmentation and macro-segmentation for flexible network isolation
+- View detailed summaries and status of Aruba CX 10000 switches
+- Ensure automatic, realtime synchronization of network configurations with Aruba CX 10000 switches
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json b/corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
new file mode 100644
index 0000000..bd52052
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+  "title": "Storage Buckets",
+  "ordinal": 177,
+  "parent_title": "Default Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md b/corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
new file mode 100644
index 0000000..47021a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
@@ -0,0 +1,3 @@
+# Storage Buckets
+
+Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json b/corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
new file mode 100644
index 0000000..2111f13
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+  "title": "Guides",
+  "ordinal": 306,
+  "parent_title": null,
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html",
+  "topic_cluster": {
+    "clustering_title": "Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md b/corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
new file mode 100644
index 0000000..362c324
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
@@ -0,0 +1,6 @@
+# Guides
+
+**Subtopics**  
+
+- **[User Process Guides](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.html)**
+- **[Integration Guides](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json b/corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
new file mode 100644
index 0000000..914573b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+  "title": "Add Storage Server",
+  "ordinal": 195,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.html",
+  "topic_cluster": {
+    "clustering_title": "Add Storage Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+        "clustering_title": "Add Storage Server"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+        "clustering_title": "Add Storage Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md b/corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
new file mode 100644
index 0000000..c48367d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
@@ -0,0 +1,96 @@
+# Add Storage Server
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+## Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following:
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server
+       :   Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following:
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json b/corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
new file mode 100644
index 0000000..493ccc2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+  "title": "Editing Cypher Keys",
+  "ordinal": 223,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Cypher Keys",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+        "clustering_title": "Editing Cypher Keys"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+        "clustering_title": "Editing Cypher Keys"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md b/corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
new file mode 100644
index 0000000..c72e7ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
@@ -0,0 +1,3 @@
+# Editing Cypher Keys
+
+Cypher key types which accept user-entered values (not generated values) are editable. To edit, click the “ACTIONS” button at the end of the row for the appropriate Cypher key and then click “Edit.” Edit the values and click SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json b/corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
new file mode 100644
index 0000000..159e747
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+  "title": "Restoring the HPE Morpheus Enterprise Manager from Backup",
+  "ordinal": 312,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.html",
+  "topic_cluster": {
+    "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+        "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+        "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md b/corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
new file mode 100644
index 0000000..df46efb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
@@ -0,0 +1,38 @@
+# Restoring the HPE Morpheus Enterprise Manager from Backup
+
+Begin by ensuring the Morpheus UI service is stopped on the HPE Morpheus Enterprise Manager VM. Connect to the manager over SSH from your workstation **bearing in mind that most commands in this process will require sudo or root access.** Enter the following command:
+
+```
+```
+[root@app-server~] morpheus-ctl stop morpheus-ui
+```
+```
+
+To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file. View it like so:
+
+```
+```
+[root@app-server~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---- this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Make note of the first `morpheus_password` value as indicated above.
+
+Copy the SQL database backup from the backup bucket or file share to the destination Manager VM at path `/tmp/morpheus_backup.sql`. Then, you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The database backup is now replicated on the new Manager VM. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server~] morpheus-ctl start morpheus-ui
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json b/corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
new file mode 100644
index 0000000..65bcf43
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+  "title": "File Shares",
+  "ordinal": 186,
+  "parent_title": "Rackspace CDN Buckets",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-35419962-0058-4856-A6BD-F4923FD0F044.html",
+  "topic_cluster": {
+    "clustering_title": "File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+        "clustering_title": "File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+        "clustering_title": "File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md b/corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
new file mode 100644
index 0000000..1a96540
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
@@ -0,0 +1,3 @@
+# File Shares
+
+File Shares are for Backup, Archives, and Virtual Images storage targets. File Shares can be browsed and files and folders can be uploaded, downloaded or deleted from the File Shares section. Retention Policies can be set on Storage File Shares for files to be deleted or backed up to another File Share after a set amount of time.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json b/corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
new file mode 100644
index 0000000..a4ee8e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+  "title": "Azure Buckets",
+  "ordinal": 181,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+        "clustering_title": "Azure Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+        "clustering_title": "Azure Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md b/corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
new file mode 100644
index 0000000..1a99064
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
@@ -0,0 +1,74 @@
+# Azure Buckets
+
+## About this task
+
+To Add an Azure Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Azure from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   STORAGE ACCOUNT
+   :   Name of the Storage Account in Azure for the Bucket
+
+   STORAGE KEY
+   :   Storage Key provided from Azure
+
+   SHARE NAME
+   :   Enter existing Azure Storage Share name, or to add a new Share enter a new name and select Create Bucket below.
+
+   CREATE BUCKET
+   :   Enable if the Share entered in SHARE NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json b/corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
new file mode 100644
index 0000000..68d7265
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+  "title": "Adding GFS2 Pools",
+  "ordinal": 118,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3702D75B-9505-40D0-B220-7739F5F72760.html",
+  "topic_cluster": {
+    "clustering_title": "Adding GFS2 Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+        "clustering_title": "Adding GFS2 Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+        "clustering_title": "Adding GFS2 Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md b/corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
new file mode 100644
index 0000000..69eac95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
@@ -0,0 +1,47 @@
+# Adding GFS2 Pools
+
+In order to utilize GFS2 Pools with HVM Clusters, users must first present the block storage devices to the HVM Hosts. These can be configured via iSCSI or Fibre Channel and all Hosts in the Cluster must be able to access the same block device. For now, this guide will focus more specifically on iSCSI configuration but additional guidance on Fibre Channel configuration may be added in the future.
+
+Once disks are presented to the HVM Hosts, iSCSI targets and GFS2 datastores can be added via the UI. The HPE Morpheus VM Essentials handles most of the configuration from there (including multipathing).
+
+To get started, ensure the following configuration has been made on the storage system. The exact process will depend on the storage system being used:
+
+- Create a LUN and map to an iSCSI target
+- Enable concurrent connections
+- Decide if you want to use CHAP authentication. GFS2 Pools with HVM Clusters support the use of CHAP authentication but there is currently no UI tool to enable it. If you wish to enable it, further instructions are available in [this knowledge article](https://support.hpe.com/hpesc/public/docDisplay?docId=sf000111606en_us&docLocale=en_US)
+
+With the above groundwork laid, create iSCSI target(s) in HPE Morpheus VM Essentials. If two paths to the iSCSI target have been created, two iSCSI objects can be created in the UI and HPE Morpheus VM Essentials will configure multipathing for you.
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the iSCSI subtab
+3. Click Add
+4. Enter the iSCSI target IP address and the port. A default port is already entered for you
+5. Click Save changes
+6. Within a short moment, the modal is dismissed and a new iSCSI target is added to the list
+7. If you intend to go on immediately to the next step of adding a GFS2 datastore, manually refresh the Cluster now (Open the ACTIONS menu on the Cluster detail page and click "Refresh Daily")
+
+IMPORTANT
+
+The above steps are repeated when a second path to the iSCSI target exists. With both paths configured, HPE Morpheus VM Essentials can automatically handle configuration of multipathing. Multipathing cannot be automatically established after the datastore is created in the next step. Both paths must be registered with HPE Morpheus VM Essentials using the process described above prior to creating the datastore in order for multipathing configuration to be handled automatically.
+
+![Adding an iSCSI target](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-ECF9319A-BDC9-48F6-AEB7-9A223C2BD71A-high.png)
+
+![List of added iSCSI targets is shown](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-B8532AB4-AA0A-470B-BEF3-2C0D5C680C3D-high.png)
+
+With the iSCSI targets created, all HVM Hosts should have the LUN mounted as a new block device. With that in place, we can create a new GFS2 datastore.
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the Data Stores subtab
+3. Click Add
+4. Configure the following:
+
+   1. **NAME:** An identifiable name for the datastore in HPE Morpheus VM Essentials
+   2. **TYPE:** GFS2 Pool (Global File System 2)
+   3. **BLOCK DEVICE:** The block device now seen by the host as a result of adding the new iSCSI target(s)
+   4. **ALLOW REFORMATTING:** When marked, HPE Morpheus VM Essentials will reformat the disk if a GFS2 filesystem doesn't currently exist. Marking this box will destroy all data on the disk, use this option with caution
+   5. **IMAGE TARGET:** When marked, this data store will be available to store virtual images. Keep in mind that the HVM Cluster should have just one image target
+5. Click Save
+
+WARNING
+
+Utilizing the "Allow Reformatting" configuration when creating the GFS2 Pool-type datastore will destroy any data currently residing on the disk. Use this option with caution.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json b/corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
new file mode 100644
index 0000000..ed24201
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+  "title": "Activity",
+  "ordinal": 15,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md b/corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
new file mode 100644
index 0000000..ff7809e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
@@ -0,0 +1,9 @@
+# Activity
+
+The activity list displays the last few events that have taken place in VM Essentials by any user. This could be new provisioned workloads, deleted workloads, backups, or a number of other things. A more complete list of recent activities can be viewed in Operations > Activity.
+
+There are three types of activities available in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json b/corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
new file mode 100644
index 0000000..aacd524
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+  "title": "Servers",
+  "ordinal": 194,
+  "parent_title": "Manage Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html",
+  "topic_cluster": {
+    "clustering_title": "Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md b/corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
new file mode 100644
index 0000000..15eee7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
@@ -0,0 +1 @@
+# Servers
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json b/corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
new file mode 100644
index 0000000..5f8b031
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+  "title": "Server Network Configuration (Netplan)",
+  "ordinal": 352,
+  "parent_title": "Prerequisites",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-392743FA-D99D-4995-A8F6-3E5541271263.html",
+  "topic_cluster": {
+    "clustering_title": "Server Network Configuration (Netplan)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+        "clustering_title": "Server Network Configuration (Netplan)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+        "clustering_title": "Server Network Configuration (Netplan)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md b/corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
new file mode 100644
index 0000000..a43ae52
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
@@ -0,0 +1,21 @@
+# Server Network Configuration (Netplan)
+
+## Procedure
+
+1. On each host, configure a `bond0` interface on the management interfaces
+2. The management interfaces should be connected to the ArubaCX switch pair Sample configuration: 
+
+   ```
+   ```
+   {  
+       bonds:  
+         bond0:  
+           interfaces:  
+             - ens2f0np0  
+             - ens1f0np0  
+           parameters:  
+             mode: "active-backup"  
+       ...  
+   }
+   ```
+   ```
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json b/corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
new file mode 100644
index 0000000..38048cd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+  "title": "Role Permissions",
+  "ordinal": 248,
+  "parent_title": "Roles",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md b/corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
new file mode 100644
index 0000000..0043a1e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
@@ -0,0 +1,10 @@
+# Role Permissions
+
+NOTE
+
+Permission options for sub-tenant user roles will only list options permitted by the Tenant role applied to the sub-tenant. Sub-Tenant user roles permissions cannot exceed permissions set by the overriding Tenant Role.
+
+**Subtopics**  
+
+- **[Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.html)**
+- **[Feature Access Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json b/corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
new file mode 100644
index 0000000..0326ffb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+  "title": "Add a storage server",
+  "ordinal": 371,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.html",
+  "topic_cluster": {
+    "clustering_title": "Add a storage server",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+        "clustering_title": "Add a storage server"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+        "clustering_title": "Add a storage server"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md b/corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
new file mode 100644
index 0000000..40fefcc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
@@ -0,0 +1,9 @@
+# Add a storage server
+
+The first step is to create a storage server in VM Essentials. After the storage server is added, you can view the storage summary and alerts, and view or edit volumes. For more information on adding a storage server, see [Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html).
+
+**Subtopics**  
+
+- **[Viewing the Summary page](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.html)**
+- **[Viewing Alerts](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.html)**
+- **[Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json b/corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
new file mode 100644
index 0000000..7db3caa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+  "title": "Backup Settings",
+  "ordinal": 285,
+  "parent_title": "Backups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3A5066B9-898A-4673-A713-C3E41D502742.html",
+  "topic_cluster": {
+    "clustering_title": "Backup Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+        "clustering_title": "Backup Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+        "clustering_title": "Backup Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md b/corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
new file mode 100644
index 0000000..ca7536a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
@@ -0,0 +1,11 @@
+# Backup Settings
+
+The Backup settings page allows you enable or disable scheduled backups, select a default backup bucket, and administer global settings related to backups. Changes to global settings only affect new backups going forward and do not affect existing backups.
+
+NOTE
+
+Appliance backups are subject to a two-hour time limit to complete the backup. Automated backup attempts will be abandoned and will fail once this time limit is exceeded.
+
+**Subtopics**  
+
+- **[VM Essentials Backup Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json b/corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
new file mode 100644
index 0000000..2dd0629
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+  "title": "Provisioning",
+  "ordinal": 26,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md b/corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
new file mode 100644
index 0000000..3d3585b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
@@ -0,0 +1,9 @@
+# Provisioning
+
+There are many capabilities in the VM Essentials provisioning engine ranging from virtual machines bound for VMware vCenter and HVM cluster targets to containerized workloads targeting Docker. Deployment management and library template construction are also core aspects of the provisioning engine. This section of VM Essentials documentation covers the provisioning engine itself while the Library section covers template building, image management, and automation stacks.
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.html)**
+- **[Provisioning Concepts](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-44974486-3ED4-4C5C-849B-8746A4899889.html)**
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json b/corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
new file mode 100644
index 0000000..b35ea89
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+  "title": "Migrations Plans",
+  "ordinal": 234,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md b/corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
new file mode 100644
index 0000000..23ce29e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
@@ -0,0 +1,25 @@
+# Migrations Plans
+
+Migration plans are created and run from the Migrations section of the Tools menu (Tools > Migrations). Migrations happen by creating and running Migration Plans. Plans are created in a pending state, meaning an additional action must be undertaken to set the plan in motion. Thus, Plans may be created which are intended to be run at a later time. Once finished, completed Plans remain on the Migrations list page for later review and, if desired, deletion.
+
+Creating Migration Plans
+
+Begin creating a Migration Plan from the Migrations list page (Tools > Migrations). This page contains a list of all Migrations already created, including those completed, currently running, and available to be run (pending). To start a new Migration, click + ADD.![A list of all currently-created Migrations.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-93D37CD4-FDF6-48AC-95C5-A5B7D7F30E35-high.png)
+
+From the SETUP tab of the CREATE MIGRATION PLAN modal, configure the following:
+
+- **NAME:** A name to identify the Migration
+- **SOURCE:** The source VMware vCenter Cloud
+- **TARGET:** The target Cloud containing the HVM Cluster
+- **RESOURCE POOL:** The selected destination HVM Cluster
+- **GROUP:** The Group which should own the migrated VMs
+
+When finished, click NEXT.![The SETUP tab of the CREATE MIGRATION PLAN modal.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-D9CD7CB0-1B54-42D7-A75C-010C489E9E09-high.png)
+
+The next step is to choose VMs from the selected VMware source Cloud to migrate. Select as many as desired given current recommendations regarding the maximum size due to storage space and available bandwidth (see the previous section). Selected VMs will form a list at the bottom of the modal. When finished, click NEXT.![Selecting source VMs to migration from the source VMware Cloud.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-EB548317-44C7-4C2C-B943-03241A92389D-high.png)
+
+The next tab establishes resource mapping. Listed, you will see the current networks and storage locations for the selected VMs. Choose destination networks and destination storage locations for each. Optionally, enter existing Linux or Windows user credentials and choose if prechecks or guest tools installation should be skipped. Click NEXT.![Mapping source networks and storage to destination networks and storage.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-7B17FB9E-19D1-42B2-9696-7856C59EC92F-high.png)
+
+The final tab is a review tab where all current selections can be checked. Return to any previous tabs, if necessary, to update selections.
+
+At this point, the Migration is created but will not run without additional input. The Migration is in a "Pending" state. All selections made when configuring the Migration are shown here. To execute the Migration, click RUN. The length of time it will take for the Migration to run depends on many factors. Once run, the Migration detail page will provide status updates on VMs currently being migrated, which have completed successfully, and if any have failed. The History tab provides greater detail on current and past migration actions taken. The Destination tab includes details on VMware VMs which have successfully been migrated to the HVM Cluster. Migrations are run just once and may be kept indefinitely after for review. When a Migration is no longer needed, click DELETE.![The migration detail page showing a migration in a pending state.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-7B7CB8A7-E91D-40E5-9B1B-E040BCFB2A0A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json b/corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
new file mode 100644
index 0000000..66af3ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+  "title": "Overview",
+  "ordinal": 226,
+  "parent_title": "Archives",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md b/corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
new file mode 100644
index 0000000..7d60909
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
@@ -0,0 +1,3 @@
+# Overview
+
+Archives provides a way to store your files and make them available for download by your scripts and Users. Archives are organized by buckets and can be tied to any existing Bucket or File Share that may be currently integrated (for more on integrating new storage targets, see storage documentation). Thus, storage buckets in public clouds, on networked storage, or even on the appliance itself may be used to host files.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json b/corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
new file mode 100644
index 0000000..43f11d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+  "title": "Configuring Backups during Provisioning",
+  "ordinal": 208,
+  "parent_title": "Backups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Backups during Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+        "clustering_title": "Configuring Backups during Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+        "clustering_title": "Configuring Backups during Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md b/corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
new file mode 100644
index 0000000..6cb06a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
@@ -0,0 +1,36 @@
+# Configuring Backups during Provisioning
+
+When Backups are enabled, Backup options are presented in the AUTOMATION tab of the provisioning wizard. Note that your default backup bucket and default backup schedule will be set according to your global backup settings as mentioned in the previous sections.
+
+NOTE
+
+The Backup options presented in the Automation tab can be disabled using a “Create Backup” Policy. See ../administration/policies/policies
+
+BACKUP TYPE
+:   Select the type for the Backup. Backup Types displayed will be filtered by available options for the selected Instance Layout
+
+BACKUP NAME
+:   Defaults to the Instance name
+
+BACKUP TARGET
+:   Select the Storage Provider target for the Backup (when applicable)
+
+BACKUP JOB TYPE
+:   Create a new job, clone an existing job, or Add to existing job
+
+JOB NAME
+:   Defaults to the Instance name
+
+RETENTION COUNT
+:   Maximum number of successful backups to retain
+
+BACKUP SCHEDULE
+:   Select the schedule for the backup job from the list of existing execution schedules
+
+SYNTHETIC FULL (Currently only available for KVM VM Snapshot-type backups, such as those used with HVM Instances. More Layout types are expected to support synthetic full backups in the future)
+:   When checked, an additional schedule is configured for the backup job during which a synthetic full backup will be taken. In general, this should be on a longer time period than that at which standard backups (full backup followed by incremental backups) are configured
+
+SYNTHETIC FULL SCHEDULE
+:   Select the schedule for the backup job on which synthetic full backups should be taken
+
+Backup Types displayed will be filtered by available options per selected Instance Layout.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json b/corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
new file mode 100644
index 0000000..adbd483
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+  "title": "2 Factor Authentication",
+  "ordinal": 298,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3B34F036-4C25-4058-B5F4-5340545BE821.html",
+  "topic_cluster": {
+    "clustering_title": "2 Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+        "clustering_title": "2 Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+        "clustering_title": "2 Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md b/corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
new file mode 100644
index 0000000..9f13228
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
@@ -0,0 +1,9 @@
+# 2 Factor Authentication
+
+VM Essentials supports two-factor authentication (2FA) for local user accounts as well as those authenticating through Active Directory and LDAP identity sources. Authentication is handled through a 2FA app such as Authy or Google Authenticator. Other common methods for handling 2FA, such as through email or SMS text message are not currently supported. Two-factor authentication is handled on a per-user basis through the User Settings section. There is not currently a way for an administrator to enforce the use of two-factor authentication appliance-wide.
+
+**Subtopics**  
+
+- **[Setting Up Two-Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.html)**
+- **[Disabling Two-Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.html)**
+- **[Handling User Lock-Out](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json b/corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
new file mode 100644
index 0000000..03379fd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+  "title": "Add Existing Key Pair",
+  "ordinal": 199,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.html",
+  "topic_cluster": {
+    "clustering_title": "Add Existing Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+        "clustering_title": "Add Existing Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+        "clustering_title": "Add Existing Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md b/corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
new file mode 100644
index 0000000..eb72ead
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
@@ -0,0 +1,20 @@
+# Add Existing Key Pair
+
+## About this task
+
+To generate a existing Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. From the Add Key Pair modal input the following as needed: 
+
+   - Name
+   - Public Key
+   - Private Key
+   - Passphrase
+
+   NOTE
+
+   Certain features do not require storage of the private key.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json b/corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
new file mode 100644
index 0000000..f8227b0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+  "title": "Cloud-Init Settings",
+  "ordinal": 278,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3D27BE17-47C9-476C-AD13-DD516697F862.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+        "clustering_title": "Cloud-Init Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+        "clustering_title": "Cloud-Init Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md b/corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
new file mode 100644
index 0000000..42b69e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
@@ -0,0 +1,12 @@
+# Cloud-Init Settings
+
+VM Essentials can add global users for Linux and Windows at provision time. Cloud-init/Cloudbase-Init or VMware Tools installed on the provisioned virtual images is required.
+
+Linux
+:   - **Username:** Enter User to be added to Linux Instances during provisioning.
+    - **Password:** Enter password to be set for the above Linux user.
+    - **KeyPair:** Select KeyPair to be added for the above Linux user.
+
+NOTE
+
+Either a password, keypair, or both can be populated for the Linux user. Keypairs can be added in the Infrastructure  >  Keys & Certs section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json b/corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
new file mode 100644
index 0000000..eb90c0e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+  "title": "Service Plan Permissions",
+  "ordinal": 242,
+  "parent_title": "Overview",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3E03B539-B71C-4D2E-A218-23713D723408.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plan Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+        "clustering_title": "Service Plan Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+        "clustering_title": "Service Plan Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md b/corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
new file mode 100644
index 0000000..4f53c64
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
@@ -0,0 +1,5 @@
+# Service Plan Permissions
+
+Group Access permissions determine availability of a Service Plan to Users based on their associated Roles.
+
+- Group Access determines which Groups the Service Plan will be available in for Provisioning and Reconfigure.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json b/corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
new file mode 100644
index 0000000..800b4fe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+  "title": "Managing Groups",
+  "ordinal": 86,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+        "clustering_title": "Managing Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+        "clustering_title": "Managing Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md b/corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
new file mode 100644
index 0000000..1800608
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
@@ -0,0 +1,30 @@
+# Managing Groups
+
+## About this task
+
+To view a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Group name to view/modify
+
+## Results
+
+Available tabs in group view
+
+Hosts
+:   Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.
+
+Virtual Machines
+:   List all Virtual Machines in the Group.
+
+Bare Metal
+:   List all Bare Metal Hosts added to the Group
+
+Clouds
+:   Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.
+
+Wiki
+:   Provides a text area for entering wiki content related to the Group in Markdown format. Additional information on Wiki is available in the Operations > Wiki documentation section
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.json b/corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
new file mode 100644
index 0000000..227a620
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+  "title": "User Settings",
+  "ordinal": 297,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-40300B80-D69C-450B-9848-7A21A3141005.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.md b/corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
new file mode 100644
index 0000000..15db370
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
@@ -0,0 +1,12 @@
+# User Settings
+
+The fields included in this section are described below. By entering any new values in these fields and clicking SAVE, the existing value will be overwritten.
+
+- **Theme:** Choose from a selection of themes including default and dark mode themes. The Theme setting is not available when Whitelabeling is enabled on the current Tenant
+- **Username:** Your VM Essentials username
+- **First Name:** Your first name (together with Last Name makes up your display name)
+- **Last Name:** Your last name (together with First Name makes up your display name)
+- **Email:** Your email address
+- **Password:** Enter a value and save changes to update your password. The value in the Confirm field below must match
+- **Confirm:** Confirm the new password you’ve entered
+- **RECEIEVE NOTIFICATIONS** Determines if provisioning notifications are emailed to this User
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json b/corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
new file mode 100644
index 0000000..091bdcf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+  "title": "Synced Images",
+  "ordinal": 30,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.html",
+  "topic_cluster": {
+    "clustering_title": "Synced Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+        "clustering_title": "Synced Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+        "clustering_title": "Synced Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md b/corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
new file mode 100644
index 0000000..62ddd9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
@@ -0,0 +1,63 @@
+# Synced Images
+
+When a provisioning target (Cloud) is added, all available image and template records from that Cloud will be synced in regardless of Inventory settings on the Cloud. These image records will be available in the Virtual Images section and can be provisioned by using the target clouds generic Instance Type (ex. By selecting the HVM or VMware Instance Type from the provisioning wizard).
+
+NOTE
+
+Synced Virtual Images are just metadata records in VM Essentials pointing to the image in the target Cloud. The actual image files are not copied/imported to VM Essentials manager.
+
+Before provisioning a synced Virtual Image, ensure the image is configured properly:
+
+Name
+:   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image file.
+
+Operating System
+:   Specifies the platform and OS of the image. All Windows images will need to have Operating System specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified.
+
+Minimum Memory
+:   The Minimum Memory setting will filter available Plan options during provisioning. Plans that do not meet the minimum memory value set on the Virtual Image will not be provided as Plan choices by the provisioning wizard.
+
+Cloud Init Enabled?
+:   On by default, uncheck for any image that does not have Cloud-Init or Cloudbase-Init installed.
+
+    IMPORTANT
+
+    Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in VM Essentials but does not have cloud-init installed will result in immediate provisioning failure.
+
+Install Agent
+:   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, Task execution, and monitoring (Some utilization stats are still collected by Agent-less workloads).
+
+Username
+:   An existing Username on the Image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init Guest Customizations or Nutanix Sysprep are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the Image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist in the image (aka `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change.
+
+Password
+:   Password for the existing user on the image if the Username field is populated.
+
+Storage Provider
+:   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/VMs`. Additional storage providers can be configured in Infrastructure > Storage.
+
+Cloud-Init User Data
+:   Accepts what would go in `runcmd` and can assume bash syntax. Example use: Script to configure satellite registration at provision time.
+
+Auto Join Domain?
+:   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure > Network and the configured domain set on the provisioned to Cloud or Network).
+
+VirtIO Drivers Loaded?
+:   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors, such as HVM cluster
+
+VM Tools Installed?
+:   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected.
+
+Force Guest Customization?
+:   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This is required for host/computer name definitions. domain joining, licenses and user definitions when using DHCP.
+
+Trial Version
+:   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning.
+
+IMPORTANT
+
+Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in VM Essentials but does not have cloud-init installed will result in immediate provisioning failure.
+
+IMPORTANT
+
+For Linux images without cloud-init, an existing username and password must be defined on the Virtual Image record for Agent Install, Domain joining, licensing, script execution and other automation, and SSH or RDP Console access.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json b/corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
new file mode 100644
index 0000000..8b6b18c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+  "title": "User Images",
+  "ordinal": 74,
+  "parent_title": "Configuring Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.html",
+  "topic_cluster": {
+    "clustering_title": "User Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+        "clustering_title": "User Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+        "clustering_title": "User Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md b/corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
new file mode 100644
index 0000000..6870d34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
@@ -0,0 +1,7 @@
+# User Images
+
+Typically VM Essentials does not have sufficient metatdata to successfully provision synced User Images with no additional configuration. After integrating Clouds and User Images have synced, it is highly recommended to configure the images prior to provisioning.
+
+**Subtopics**  
+
+- **[To edit and configure an existing Virtual Image:](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json b/corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
new file mode 100644
index 0000000..97afac7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+  "title": "Volumes tab",
+  "ordinal": 374,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.html",
+  "topic_cluster": {
+    "clustering_title": "Volumes tab",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+        "clustering_title": "Volumes tab"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+        "clustering_title": "Volumes tab"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md b/corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
new file mode 100644
index 0000000..5745e2f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
@@ -0,0 +1,6 @@
+# Volumes tab
+
+**Subtopics**  
+
+- **[Viewing Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.html)**
+- **[Editing volumes](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json b/corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
new file mode 100644
index 0000000..520eb5d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+  "title": "Create vCenter Users and Roles",
+  "ordinal": 329,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.html",
+  "topic_cluster": {
+    "clustering_title": "Create vCenter Users and Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+        "clustering_title": "Create vCenter Users and Roles"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+        "clustering_title": "Create vCenter Users and Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md b/corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
new file mode 100644
index 0000000..fbc6c60
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
@@ -0,0 +1,9 @@
+# Create vCenter Users and Roles
+
+For this example, I’ve added a new local user to be my VM Essentials integration user (Menu > Administration > Users and Groups) but any existing user, whether locally-created or sourced from an identity integration (like Active Directory), works fine.
+
+![../../../_images/addUsers.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-2664505C-63D5-43FB-9E16-21AD005B561C-high.png)
+
+The next step is to create a Role (Menu > Administration > Roles). You can edit an existing Role to be sure it has the correct privileges, I’ve opted to create a new role and assign the correct privileges. Below the screenshot, take note of the complete set of required privileges. Once all privileges are set, name the Role (if it’s a new one) and click Finish.
+
+![../../../_images/addRoles.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-3152339A-7CAC-4795-8CBD-67503905D112-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json b/corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
new file mode 100644
index 0000000..9ef1a67
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+  "title": "Provisioning Concepts",
+  "ordinal": 40,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-44974486-3ED4-4C5C-849B-8746A4899889.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Concepts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+        "clustering_title": "Provisioning Concepts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+        "clustering_title": "Provisioning Concepts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md b/corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
new file mode 100644
index 0000000..349299b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
@@ -0,0 +1,9 @@
+# Provisioning Concepts
+
+VM Essentials is a powerful provisioning and management platform for HVM clusters and VMware vCenter private cloud. Compared to other CMP platforms in the space, some terminology and concepts may differ. These concepts are documented in this section along with places where terminology may be slightly different compared with other platforms or with common industry parlance.
+
+**Subtopics**  
+
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.html)**
+- **[Containers / Nodes / Virtual Machines](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.html)**
+- **[Hosts / Servers](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json b/corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
new file mode 100644
index 0000000..d951b3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+  "title": "Configuring Networks",
+  "ordinal": 140,
+  "parent_title": "Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+        "clustering_title": "Configuring Networks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+        "clustering_title": "Configuring Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md b/corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
new file mode 100644
index 0000000..1b0b2a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
@@ -0,0 +1,10 @@
+# Configuring Networks
+
+**Subtopics**  
+
+- **[DHCP](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.html)**
+- **[Static and IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.html)**
+- **[Advanced Options (Search Domains)](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.html)**
+- **[Group and Tenant Access](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html)**
+- **[Guest Console SSH Tunnel](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.html)**
+- **[Subnets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9FC58214-95C7-4690-91DA-3185640E3712.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json b/corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
new file mode 100644
index 0000000..f93c488
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+  "title": "HPE Alletra MP Storage",
+  "ordinal": 366,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md b/corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
new file mode 100644
index 0000000..00d4784
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
@@ -0,0 +1,9 @@
+# HPE Alletra MP Storage
+
+**Subtopics**  
+
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.html)**
+- **[Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html)**
+- **[Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html)**
+- **[Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html)**
+- **[Add a storage server](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json b/corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
new file mode 100644
index 0000000..1d48951
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+  "title": "Provisioning a Workload",
+  "ordinal": 108,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a Workload",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+        "clustering_title": "Provisioning a Workload"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+        "clustering_title": "Provisioning a Workload"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md b/corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
new file mode 100644
index 0000000..595d446
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
@@ -0,0 +1,15 @@
+# Provisioning a Workload
+
+At this point, the cluster is ready for workloads to be provisioned to it. Within the Instance provisioning wizard (See Provisioning > Instances documentation for more details on provisioning), there is now the “HVM” Instance Type. This Instance will allow you to choose from any HVM cluster-compatible images within your environment. Out of the box, VM Essentials does not include any compatible images but there is a section later in this guide covering the process of onboarding existing QCOW images into the UI as Virtual Images and another section covering the process of prepping Windows images from the downloaded ISO.
+
+After arriving at the Configure tab of the provisioning wizard, select a Plan based on resource needs. From the **RESOURCE POOL** field, select the desired HVM cluster. When configuring **VOLUMES** for the new workload, note that space can be claimed from the configured volume. Within **NETWORKS**, we can add the new workload to one of the **VLANS** set up as part of cluster creation. Finally, note that we can choose the HOST the workload should run on in addition to selecting the compatible image.
+
+TIP
+
+The VOLUMES configuration within the provisioning wizard includes a flyout menu allowing storage type (standard, thin, thick (lazy zero), and thick (eager) and storage profile (cache: none or cache: directsync) configurations to be set on each individual volume.
+
+Review and complete the provisioning wizard. After a short time, the workload should be up and running. With a workload now running on the cluster, we can take a look at some of the monitoring, migration, failover, and other actions we can take for workloads running on HVM clusters.
+
+NOTE
+
+HVM clusters support CPU pinning (tying specific vCPUs associated with running workloads to specific physical CPU cores). Currently, this must be done manually by accessing the appropriate HVM host and issuing `virsh` commands or editing XML. Adding UI tools to view and control CPU pinning is on the product roadmap to be added in the near future. Despite the requirement to edit CPU pinning manually, this is a supported action for workloads running on HVM clusters.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json b/corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
new file mode 100644
index 0000000..4afdf60
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+  "title": "Plugins",
+  "ordinal": 257,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.html",
+  "topic_cluster": {
+    "clustering_title": "Plugins",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+        "clustering_title": "Plugins"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+        "clustering_title": "Plugins"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md b/corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
new file mode 100644
index 0000000..366284f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
@@ -0,0 +1,21 @@
+# Plugins
+
+## About this task
+
+The Plugins allow you to extend the functionality of HPE Morpheus VM Essentials beyond its default capabilities.
+
+To add a plugin, perform the following:
+
+## Procedure
+
+1. Navigate to Administration > Integrations.
+2. Click Plugins tab.
+3. Click ADD.
+4. You can upload the `.jar` file using either of the following:
+
+   - Drag and drop the file into the upload window.
+   - Select the file manually and click UPLOAD.
+
+## Results
+
+The plugin activates automatically if the validation succeeds.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json b/corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
new file mode 100644
index 0000000..c1203d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+  "title": "User Access",
+  "ordinal": 89,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.html",
+  "topic_cluster": {
+    "clustering_title": "User Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+        "clustering_title": "User Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+        "clustering_title": "User Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md b/corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
new file mode 100644
index 0000000..c9e71fe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
@@ -0,0 +1,5 @@
+# User Access
+
+IMPORTANT
+
+User access to Groups is determined by their Role(s). Group access for Roles can be configured in the Group Access section of a Role’s Settings.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json b/corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
new file mode 100644
index 0000000..957503e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+  "title": "Execute Scheduling",
+  "ordinal": 69,
+  "parent_title": "Automation",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+        "clustering_title": "Execute Scheduling"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+        "clustering_title": "Execute Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md b/corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
new file mode 100644
index 0000000..2ba40af
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
@@ -0,0 +1,31 @@
+# Execute Scheduling
+
+Execute Scheduling creates time schedules for automated jobs, such as backups. Backup Jobs are discussed in greater detail in the Backups section and are configured with an execution schedule to coordinate their run times. This section goes through the process of creating and configuring the scheduling object.
+
+Schedules use CRON expressions, such as `0 23 * * 2` equalling `Executes every week on Tuesday at 23:00`. CRON expressions can easily be created by clicking the corresponding translation in the create or edit Execution Schedule modal below the Schedule field and selecting a new value.
+
+NOTE
+
+Execute Schedules CRON expressions should not include seconds or years. The days of the week should be numbered 1-7, beginning with Monday and ending with Sunday. SUN-SAT notation may also be used. For more on writing CRON expressions, many guides are hosted on the Internet including [this one](https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm). VM Essentials execution schedules support most cron syntax but certain more complex expressions may fail to evaluate and the execute schedule will not save. Additionally, some complex expressions may save and work correctly while the friendly written evaluation below the SCHEDULE field is not interpreted correctly. This is due to an issue with the underlying library used to build this feature and cannot easily be resolved at this time.
+
+NAME
+:   Name of the Execution Schedule
+
+    NOTE
+
+    When assigning Execution Schedules, the name value will appear in the selection drop-down. Using a name that makes clear the time interval is often helpful.
+
+DESCRIPTION
+:   Description of the Execution Schedule for reference in the Execution Schedules list
+
+TIME ZONE
+:   The time zone for execution
+
+Enabled
+:   Check to enable the schedule. Uncheck to disable all associated executions and remove the schedule as an option for Jobs in the future
+
+SCHEDULE
+:   Enter CRON expression for the Execution Schedule, for example `0 0 * * *` equals `Every day at 00:00`
+
+SCHEDULE TRANSLATION
+:   The entered CRON schedule is translated below the SCHEDULE field. Highlighted values can be updated by selecting the value, and relevant options will be presented. The CRON expression will automatically be updated
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json b/corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
new file mode 100644
index 0000000..b16afbe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+  "title": "Storage",
+  "ordinal": 174,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md b/corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
new file mode 100644
index 0000000..1233b03
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
@@ -0,0 +1,23 @@
+# Storage
+
+Infrastructure  >  Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in VM Essentials.
+
+**Subtopics**  
+
+- **[Role Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.html)**
+- **[Default Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A745B955-2E59-4769-AB47-E32098A84653.html)**
+- **[Supported Bucket Types](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.html)**
+- **[Alibaba Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.html)**
+- **[Amazon S3 Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.html)**
+- **[Azure Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.html)**
+- **[Google Cloud Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.html)**
+- **[Dell EMC ECS Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.html)**
+- **[Openstack Swift Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.html)**
+- **[Rackspace CDN Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.html)**
+- **[Supported File Share Types](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.html)**
+- **[CIFS File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.html)**
+- **[Local Storage File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.html)**
+- **[NFSv3 File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html)**
+- **[Create Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.html)**
+- **[Manage Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.html)**
+- **[Add Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json b/corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
new file mode 100644
index 0000000..dce1cc2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+  "title": "HPE Morpheus VM Essentials Software",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus VM Essentials Software",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+        "clustering_title": "HPE Morpheus VM Essentials Software"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+        "clustering_title": "HPE Morpheus VM Essentials Software"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md b/corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
new file mode 100644
index 0000000..679514a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
@@ -0,0 +1,12 @@
+# HPE Morpheus VM Essentials Software
+
+**Subtopics**  
+
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.html)**
+- **[Operations](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.html)**
+- **[Library](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html)**
+- **[Infrastructure](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.html)**
+- **[Tools](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html)**
+- **[Administration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AAD13737-533B-491F-A155-DDB027057157.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json b/corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
new file mode 100644
index 0000000..f32c447
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+  "title": "Image Preparation",
+  "ordinal": 335,
+  "parent_title": "Creating a Windows Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.html",
+  "topic_cluster": {
+    "clustering_title": "Image Preparation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+        "clustering_title": "Image Preparation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+        "clustering_title": "Image Preparation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md b/corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
new file mode 100644
index 0000000..f4c087f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
@@ -0,0 +1,34 @@
+# Image Preparation
+
+## About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing VM Essentials, provisioning and post deploy scripts can expand drives to desired sizing.
+
+## Procedure
+
+1. Ensure VMware Tools is installed on the operating system.
+2. Apply any service packs / updates to the operating system.
+3. Configure WinRM to allow remote management and open the firewall. This is optional if using VMware Tools RPC mode for agent install and VM Essentials Agent for guest exec. To enable this, under local computer Administrator, open a command prompt and run 
+
+   ```
+   ```
+   winrm quickconfig
+   ```
+   ```
+4. Install .Net at least 4.5.2
+5. Ensure Windows Firewall will allow WinRM connections.
+6. Shutdown the virtual machine and convert to a template.
+
+## Results
+
+NOTE
+
+WinRM is not required and is used as a fallback when using vmtools guest exec and customizations
+
+NOTE
+
+Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
+
+IMPORTANT
+
+VM Essentials supports the use of SR-IOV network adapters with VMware Clouds. Windows images must have SR-IOV network drivers installed to work with this adapter type. If they do not, provisioning will fail.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json b/corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
new file mode 100644
index 0000000..52f5fe2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+  "title": "Instances",
+  "ordinal": 41,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md b/corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
new file mode 100644
index 0000000..23ab26a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
@@ -0,0 +1,5 @@
+# Instances
+
+VM Essentials starts with provisioning Instances. In some platforms, an Instance is representative of a singular object like a virtual machine in VMware vCenter. In VM Essentials, this concept was rethought. An Instance is more of a representation of a resource or service. This service may involve several virtual machines, as in the case of a database cluster or horizontally-scaled web servers.
+
+When viewing an Instance detail page, one is able to look at details and statistics specific to a virtual machine or container. VM Essentials simply helps simplify the management model for tracking these services.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json b/corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
new file mode 100644
index 0000000..e9e8c7b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+  "title": "Overview",
+  "ordinal": 291,
+  "parent_title": "License",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md b/corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
new file mode 100644
index 0000000..fdad66a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
@@ -0,0 +1,3 @@
+# Overview
+
+VM Essentials requires a valid license for provisioning new Instances and Clusters, and converting existing Instances to managed. Licenses can be applied and updated in this section, and the current license status, as well as usage metrics, can be checked.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json b/corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
new file mode 100644
index 0000000..69fc798
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+  "title": "Backups",
+  "ordinal": 204,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md b/corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
new file mode 100644
index 0000000..eaf4a81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
@@ -0,0 +1,12 @@
+# Backups
+
+The VM Essentials built-in Backup solution provides VM, Container, Host, Database, File, Directory, Volume and Storage Provider Backup, Snapshot and Replication capabilities. Backups can be automatically configured during provisioning or manually created at any time. Backup Jobs with custom Execution Schedules and retention counts can be created and used across all environments in conjunction with configured Storage Providers. Backups can be restored over current Instances or as new Instances, and downloaded or deleted from VM Essentials.
+
+VM Essentials also integrates with external services to automate availability with other providers.
+
+**Subtopics**  
+
+- **[Initial Backups Setup](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.html)**
+- **[Configuring Backups during Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.html)**
+- **[Summary](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json b/corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
new file mode 100644
index 0000000..4902bb3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+  "title": "Overview",
+  "ordinal": 232,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md b/corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
new file mode 100644
index 0000000..387ec01
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
@@ -0,0 +1,3 @@
+# Overview
+
+The bulk migration tool is designed to migrate existing VMs running on integrated VMware vCenter Clouds to HVM Clusters. Thus, creating a migration requires existing vCenter Cloud integration(s) and at least one functional HVM Cluster. See the VMware vCenter integration guide and the HVM Clusters guide elsewhere in this documentation stack for more details on getting started with and using those integrations. Migrations may include multiple VMs and may include both Linux and Windows workloads.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json b/corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
new file mode 100644
index 0000000..691fc8b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+  "title": "Windows Provisioning Tips",
+  "ordinal": 318,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Provisioning Tips",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+        "clustering_title": "Windows Provisioning Tips"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+        "clustering_title": "Windows Provisioning Tips"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md b/corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
new file mode 100644
index 0000000..0578b70
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
@@ -0,0 +1,7 @@
+# Windows Provisioning Tips
+
+By default when provisioning windows templates, VM Essentials performs guest customizations which initiates a sysprep. This resets the Administrator user and password. VM Essentials will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json b/corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
new file mode 100644
index 0000000..79e3465
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+  "title": "Network",
+  "ordinal": 137,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html",
+  "topic_cluster": {
+    "clustering_title": "Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md b/corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
new file mode 100644
index 0000000..dbf690e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
@@ -0,0 +1,11 @@
+# Network
+
+**Subtopics**  
+
+- **[Networks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html)**
+- **[Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html)**
+- **[Routers](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html)**
+- **[IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html)**
+- **[Domains](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json b/corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
new file mode 100644
index 0000000..32cc4d9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+  "title": "Multitenancy",
+  "ordinal": 326,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.html",
+  "topic_cluster": {
+    "clustering_title": "Multitenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+        "clustering_title": "Multitenancy"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+        "clustering_title": "Multitenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md b/corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
new file mode 100644
index 0000000..869e9b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
@@ -0,0 +1,3 @@
+# Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json b/corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
new file mode 100644
index 0000000..0e7b6b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+  "title": "View HPE Aruba CX DSS Network Integration",
+  "ordinal": 364,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.html",
+  "topic_cluster": {
+    "clustering_title": "View HPE Aruba CX DSS Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+        "clustering_title": "View HPE Aruba CX DSS Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+        "clustering_title": "View HPE Aruba CX DSS Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md b/corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
new file mode 100644
index 0000000..09fa54d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
@@ -0,0 +1,19 @@
+# View HPE Aruba CX DSS Network Integration
+
+To view the HPE Aruba CX DSS Network integration, follow these steps:
+:   1. Navigate to Infrastructure > Network > Integrations
+    2. Select the HPE Aruba CX DSS integration from the list.
+
+       ![../../_images/5.1_list_network_integrations.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5F56F425-47AA-4B32-9A7B-48C69C82CFAB-high.png)
+       - `Summary` - Click on the Summary tab to view the summary of the integration.
+
+         ![../../_images/5.2_view_integration_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-0B2B766C-E581-4C17-BE5D-C95F72BDCB20-high.png)
+       - `Switches` - Click the Switches tab to view detailed information about all Aruba CX 10000 switches managed by the integration.
+
+         ![../../_images/5.3_view_integration_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-A5481BCF-8C48-4106-B3C2-F0AD92CEFEE3-high.png)
+       - `Networks` - Click on the Networks tab to view the networks associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-C93D74CC-3795-4FA8-A12A-BADF901EB1AB-high.png)
+       - `Firewalls` - Click on the Firewall tab to view firewall policies associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-FC71FD7B-012A-4291-9519-0AFD8374D65C-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json b/corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
new file mode 100644
index 0000000..66e8bf3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+  "title": "Adding an Archive",
+  "ordinal": 228,
+  "parent_title": "Archives",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an Archive",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+        "clustering_title": "Adding an Archive"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+        "clustering_title": "Adding an Archive"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md b/corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
new file mode 100644
index 0000000..c502d9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
@@ -0,0 +1,16 @@
+# Adding an Archive
+
+To add a new Archive, click + ADD from the Archives list page. Configure the following:
+
+- **NAME:** A friendly name for the Archive in VM Essentials
+- **DESCRIPTION:** An optional description for the Archive
+- **BUCKET:** Select an existing bucket or file share to store files in for this Archive. To integrate a new bucket or file share to use for an Archive, navigate to Infrastructure > Storage
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants selected will have access to the Archive
+- **PUBLIC URL:** When marked, VM Essentials will create a public download URL for all files in the Archive
+
+WARNING
+
+Be sure that no sensitive data will be stored in the Archive if it will be configured to generate public URLs. Anyone with the public URL will be able to download the file without authentication.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json b/corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
new file mode 100644
index 0000000..b2ec3f0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+  "title": "Containers / Nodes / Virtual Machines",
+  "ordinal": 42,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.html",
+  "topic_cluster": {
+    "clustering_title": "Containers / Nodes / Virtual Machines",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+        "clustering_title": "Containers / Nodes / Virtual Machines"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+        "clustering_title": "Containers / Nodes / Virtual Machines"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md b/corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
new file mode 100644
index 0000000..4103f77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
@@ -0,0 +1,3 @@
+# Containers / Nodes / Virtual Machines
+
+In relation to Instances, an Instance can have many nodes. A node is a generic representation of a container or a virtual machine. In most cases, VM Essentials will represent a node as a Container or Virtual Machine depending on the provisioning engine used for the Instance (workload provisioned to a HVM cluster as opposed to a Docker cluster, for example). Node is just a generic naming representation when referring to these types of items. The public VM Essentials developer API, however, often refers to both virtual machines and Docker containers as “containers”. The UI was updated to better delineate this concept for easier understanding but, in essence, the name is valid for both concepts of containerized environments as well as virtual machines.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json b/corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
new file mode 100644
index 0000000..f4d90c6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+  "title": "UI",
+  "ordinal": 82,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.html",
+  "topic_cluster": {
+    "clustering_title": "UI",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+        "clustering_title": "UI"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+        "clustering_title": "UI"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md b/corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
new file mode 100644
index 0000000..5256ee8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
@@ -0,0 +1,4 @@
+# UI
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json b/corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
new file mode 100644
index 0000000..7faea8d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+  "title": "Instances",
+  "ordinal": 44,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md b/corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
new file mode 100644
index 0000000..42d1d5b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
@@ -0,0 +1,10 @@
+# Instances
+
+Instances are a great starting point for taking advantage of self-service features and spinning up both VMs and containers. The top of the main Instances page shows overall statistics for the listed Instances, including count, status, and resource utilization. You can search for Instances by name, or filter by group, type, or category.
+
+The Instance list contains important information about each Instance, including the Instance name, environment tag, type, IP address and port info, Instance version, the number of virtual machines or containers, the Group, and the associated Cloud.
+
+**Subtopics**  
+
+- **[Creating Instances](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.html)**
+- **[Managing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json b/corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
new file mode 100644
index 0000000..6883f4b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+  "title": "Tenant Management Settings",
+  "ordinal": 267,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Management Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+        "clustering_title": "Tenant Management Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+        "clustering_title": "Tenant Management Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md b/corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
new file mode 100644
index 0000000..1c6f78b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
@@ -0,0 +1,13 @@
+# Tenant Management Settings
+
+Registration Enabled
+:   If enabled, the appliance login screen will have a “NEED AN ACCOUNT? SIGN UP HERE” link added, enabling new Tenant registration.
+
+Default Tenant Role
+:   Sets the default Tenant Role applied to Tenants created from Tenant Registration.
+
+Default User Role
+:   Sets the default User Role applied to the User created from a Tenant Registration.
+
+Docker Privileged Mode
+:   Enable to allow Docker containers running on VM Essentials Docker hosts to run in privileged mode which adds additional access to the host hardware and resources but also comes with additional security risks
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json b/corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
new file mode 100644
index 0000000..092bcb4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+  "title": "Viewing the Summary page",
+  "ordinal": 372,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing the Summary page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+        "clustering_title": "Viewing the Summary page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+        "clustering_title": "Viewing the Summary page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md b/corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
new file mode 100644
index 0000000..aa4027d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
@@ -0,0 +1,65 @@
+# Viewing the Summary page
+
+The Summary tab displays system information, capacity utilization of the system, and the number of ransomware alerts detected
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server. The Summary tab displays the information for the selected server. ![Summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-CADEC596-4D47-4B87-85E1-DC2756B5DAD8-high.png)
+
+   The Summary tab contains:
+
+   - **System**
+
+     The following information is displayed in the System tile:
+     - **Name**: Displays the system name of the selected server.
+     - **Model**: Displays the model name of the system.
+     - **Serial Number**: Displays the serial number of the system.
+     - **Health status**: Displays the system health status of the array depending on the highest severity type of the alerts listed in the Alerts tab for the storage system. The health status values can be Critical, Normal, or Warning.
+
+       | Highest Severity Type of Alerts | Health status |
+       | --- | --- |
+       | Critical or Fatal | Critical (The system has some major issues that will affect performance) |
+       | Major | Warning (The system is operational but with some non-critical issues) |
+       | Other types | Normal (The system is functioning as expected) |
+     - **Firmware version**: Displays the firmware version of the storage system.
+     - **WWN**: Displays a unique identifier name of the system.
+     - **Uptime**: Displays the total time the system has been operational.
+     - **IP Address**: Displays the IP address of the system.
+   - **Capacity Utilization**
+
+     The Capacity Utilization tile displays the total and used capacity percentage of the selected storage system.
+
+     - For models HPE Alletra MP B10000 and later, the Capacity Utilization tile populates the usable capacity.
+     - For models prior to HPE Alletra MP B10000, the Capacity Utilization tile populates the raw capacity information.
+
+     NOTE
+
+     You can get the latest system information by clicking the Summary tab.
+   - **Ransomware Detection**
+
+     The Ransomware Detection tile displays the number of ransomware alerts detected. A hyperlink is displayed when more than one ransomware alert is detected; otherwise, it is displayed as a plain text.
+
+     On clicking the hyperlink, you can view the details of alert by selecting Ransomware monitoring as the Filter by Type.
+
+     ![Alerts - ransomware monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-0E521724-F9E5-4619-B9D9-BB943E488958-high.png)
+   - **Protection**
+
+     Using the Filter by drop-down list, you can view the protection status for a `VM` or an `Instance`.
+
+     This tile displays the snapshot protection and remote replication status of both virtual machines (VMs) and instances on the storage system. You can also view the total percentage of VMs or Instances that are protected. Protection is determined based on snapshot availability with or without remote replication. The protection data is auto-refreshed periodically.
+
+     NOTE
+
+     Hover over the information (i) icon beside each field to display the description.
+
+     For VMs, the following information is displayed:
+     - **Snapshot:** Count of VMs where each volume has a point-in-time snapshot.
+     - **Remote Replication:** Count of VMs that have replicated volumes.
+     - **Snapshot + Remote Replication:** Count of VMs that have replicated volumes, where each volume also has a point in time snapshot.
+     - **Unprotected:** Count of VMs that have neither replicated volumes nor point-in-time snapshot on any volume.
+
+     For Instances, the following information is displayed:
+     - **Snapshot:** Count of instances where every volume associated with each VM has a point-in-time snapshot.
+     - **Remote Replication:** Count of instances where every volume associated with each VM is replicated.
+     - **Snapshot + Remote Replication:** Count of instances where each associated VM has replicated volumes and every volume has a point-in-time snapshot.
+     - **Unprotected:** Count of instances where each associated VM neither has replicated volumes nor point-in-time snapshot on any volume.
+     - **Partially Protected:** Count of instances where some, but not all, of the instance's VMs have snapshots and can be in remote replication.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json b/corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
new file mode 100644
index 0000000..f4a508a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+  "title": "Hosts / Servers",
+  "ordinal": 43,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.html",
+  "topic_cluster": {
+    "clustering_title": "Hosts / Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+        "clustering_title": "Hosts / Servers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+        "clustering_title": "Hosts / Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md b/corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
new file mode 100644
index 0000000..2966bb9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
@@ -0,0 +1,5 @@
+# Hosts / Servers
+
+This concept is mostly tailored to users of VM Essentials who are responsible for managing and maintaining the underlying infrastructure integrations. A Host typically refers to a Docker Host in which a container (within an Instance) is running, or a hypervisor that virtual machines can be provisioned onto. A server is the underlying general representation of a physical or virtual server. It could be a Host representation, a Virtual Machine, or even a Bare Metal delineation.
+
+When a user provisions a VM-based Instance, a corresponding server record is created to represent the link to the actual resource via the underlying provisioning engine. This may seem a bit odd but provides an aspect of VM Essentials that is quite powerful. This singular concept is what allows VM Essentials to ingest “brownfield” environments. We do not need to start clean. VM Essentials can be integrated into existing environments and manage existing virtual machines. The way VM Essentials does this is by periodically syncing existing VMs from the added cloud integrations. A server record will be created and periodically updated (every five minutes, by default) with realtime information and changes. This, in essence, provides CMDB-like capabilities as well. When a server is discovered, the user (given the appropriate access) can convert the virtual machine to a managed Instance. When this is done, a corresponding Instance is made in the provisioning section of VM Essentials and the VM Essentials Agent can optionally be installed to provide more refined guest operating system-level statistics and logging.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json b/corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
new file mode 100644
index 0000000..999fd7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+  "title": "Create Datastore",
+  "ordinal": 369,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html",
+  "topic_cluster": {
+    "clustering_title": "Create Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+        "clustering_title": "Create Datastore"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+        "clustering_title": "Create Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md b/corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
new file mode 100644
index 0000000..28e2416
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
@@ -0,0 +1,42 @@
+# Create Datastore
+
+## About this task
+
+Add a Datastore to the Storage Server.
+
+## Procedure
+
+1. Navigate to Infrastructure > Clusters.
+2. Click into the detail page for the cluster where the datastore is to be created.
+3. Select the Storage tab.
+4. Under the Data Stores sub tab, click + ADD.
+5. From the ADD DATASTORE wizard, input the following: 
+
+   NAME:
+   :   Name of the datastore in HPE Morpheus Enterprise.
+
+   TYPE:
+   :   Select the type of storage system.
+
+   STORAGE SERVER:
+   :   Select the storage server that is created using the ADD STORAGE SERVER wizard.
+
+   PROTOCOL TYPE:
+   :   Select the type of storage protocol.
+
+   RANSOMWARE DETECTION:
+   :   Select the check box to enable ransomware detection for all VMs created with this datastore.
+
+   NOTE
+
+   The datastore creation fails if storage servers other than HPE Alletra Storage MP B10000 are selected along with the Ransomware Detection option.
+
+   CPG
+   :   Use the drop-down list to select a Common Provisioning Group (CPG) for allocating storage to the new datastore.
+6. Click SAVE.
+
+## Results
+
+![Add data store](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-6894A520-8797-40DF-9252-2F696167BA9F-high.png)
+
+The datastore is added and displayed in the Datastore tab. Confirm that its status is healthy.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json b/corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
new file mode 100644
index 0000000..743780f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+  "title": "Migrations",
+  "ordinal": 231,
+  "parent_title": "Tools",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md b/corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
new file mode 100644
index 0000000..578dc21
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
@@ -0,0 +1,8 @@
+# Migrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html)**
+- **[Migrations Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html)**
+- **[Migrations Plans](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html)**
+- **[Configuring Windows Workloads (Windows 2022 or later) for Migration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.json b/corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.json
new file mode 100644
index 0000000..9e7714f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+  "title": "Provisioning Images",
+  "ordinal": 76,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5504862E-8120-469D-8708-2290772E5585.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+        "clustering_title": "Provisioning Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+        "clustering_title": "Provisioning Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.md b/corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.md
new file mode 100644
index 0000000..6930027
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5504862E-8120-469D-8708-2290772E5585.md
@@ -0,0 +1,13 @@
+# Provisioning Images
+
+When provisioning a system image, VM Essentials will stream the image from Amazon S3 to the target Cloud if the image is not local to the Cloud.
+
+When using images that already exist in the destination Cloud, such as synced or previously copied images, no image stream from S3 through the VM Essentials Appliance to the destination cloud will take place.
+
+NOTE
+
+The VM Essentials Appliance must be able to download from Amazon S3 when provisioning system images.
+
+NOTE
+
+The VM Essentials Appliance must be able reach and resolve the destination Host when provisioning System Images or uploaded Images for the first time. This included being able to resolve ESXi host names in VMware vCenter clouds, and reach the destination ESXi host over port 443.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json b/corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
new file mode 100644
index 0000000..a5935e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+  "title": "Privileges",
+  "ordinal": 330,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.html",
+  "topic_cluster": {
+    "clustering_title": "Privileges",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+        "clustering_title": "Privileges"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+        "clustering_title": "Privileges"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md b/corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
new file mode 100644
index 0000000..88cd34a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
@@ -0,0 +1,80 @@
+# Privileges
+
+Content Library
+:   - All Content Library privileges
+
+Datastore/Datastore Cluster
+:   - Allocate Space
+    - Browse Datastore
+    - Low Level file Operations
+    - Remove File
+    - Update virtual machine files
+    - Update virtual machine metadata
+
+Distributed Switch
+:   - Port configuration operation
+    - Port setting operation
+
+Global
+:   - Log Event
+    - Manage custom attributes
+    - Set custom attribute
+
+Network
+:   - Assign Network
+    - Configure
+    - Remove
+
+Resource
+:   - Apply recommendation
+    - Assign vApp to resource pool
+    - Assign virtual machine to resource pool
+    - Migrate powered off virtual machine
+    - Migrate powered on virtual machine
+
+Scheduled task
+:   - Create tasks
+    - Modify task
+    - Remove task
+    - Run task
+
+Tasks
+:   - Create task
+    - Update task
+
+Virtual Machine
+:   - Configuration (all)
+    - Guest Operations (all)
+    - Interaction (all)
+    - Inventory (all)
+    - Provisioning (all)
+    - Service configuration (all)
+    - Snapshot management (all)
+    - vSphere Replication (all)
+
+vApp
+:   - Clone
+    - Export
+    - Import
+
+vSphere Tagging
+:   - Assign or Unassign vSphere Tag
+    - Assign or Unassign vSphere Tag on Object
+    - Create vSphere Tag
+    - Create vSphere Tag Category
+    - Delete vSphere Tag
+    - Delete vSphere Tag Category
+    - Edit vSphere Tag
+    - Edit vSphere Tag Category
+    - Modify UsedBy Field For Category
+    - Modify UsedBy Field For Tag
+    - privilege.InventoryService.Tagging.CreateScope.label
+    - privilege.InventoryService.Tagging.DeleteScope.label
+
+With the User and Role created, add permissions to associate the User and Role to the appropriate usage constructs. Navigate to the usage construct you wish to work with, navigate to the permissions tab, click the plus (+) button. In the screenshot below, I’m adding the permission for the vCenter usage construct. The complete list of usages and whether or not to mark the propagation box is below the image.
+
+NOTE
+
+For organization and security purposes, permissions can also be added to folders. This allows VM Essentials to see the folders and onboard any resources within them (if desired). Once the vCenter Cloud integration has been created in VM Essentials, you can view folders from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > ResourcesTab). By editing the folder here (Actions > Edit), folders can be set as the “Default” and/or the “Image Target”. When a folder is set as Default, this folder is pre-selected when provisioning new Instances into the Cloud. When a folder is set as the Image Target, VM Essentials will look into this folder to onboard VMware images into VM Essentials.
+
+![../../../_images/addPerms.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-C8A5BC12-8BBF-47AF-A193-BD89D2392417-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json b/corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
new file mode 100644
index 0000000..f1f1c35
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+  "title": "Instances By Cloud",
+  "ordinal": 12,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.html",
+  "topic_cluster": {
+    "clustering_title": "Instances By Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+        "clustering_title": "Instances By Cloud"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+        "clustering_title": "Instances By Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md b/corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
new file mode 100644
index 0000000..c7551b0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
@@ -0,0 +1,5 @@
+# Instances By Cloud
+
+The total number of Clouds which currently have an Instance provisioned is shown. Hover over each section of the pie chart to see the total number and percentage of Instances provisioned to each Cloud
+
+The number of Instances that have existed at any point in the day with additional breakdown to show the number provisioned to each Cloud. This number will include any pre-existing Instances which have carried over from previous days along with any new Instances that were provisioned and existed on that day even for a short time
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json b/corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
new file mode 100644
index 0000000..b30b7e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+  "title": "Supported Versions",
+  "ordinal": 334,
+  "parent_title": "Creating a Windows Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+        "clustering_title": "Supported Versions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+        "clustering_title": "Supported Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md b/corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
new file mode 100644
index 0000000..32be7b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
@@ -0,0 +1,3 @@
+# Supported Versions
+
+2008R2, 2012, 2012R2, 2016, 2019, 2022
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json b/corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
new file mode 100644
index 0000000..ca3cb93
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+  "title": "Linux Agent",
+  "ordinal": 36,
+  "parent_title": "SSH/Winrm",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+        "clustering_title": "Linux Agent"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+        "clustering_title": "Linux Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md b/corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
new file mode 100644
index 0000000..6e6cdec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
@@ -0,0 +1,4 @@
+# Linux Agent
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json b/corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
new file mode 100644
index 0000000..bd440c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+  "title": "Virtual Images",
+  "ordinal": 70,
+  "parent_title": "Library",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md b/corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
new file mode 100644
index 0000000..dceaa95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
@@ -0,0 +1,8 @@
+# Virtual Images
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.html)**
+- **[Configuring Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html)**
+- **[Provisioning Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5504862E-8120-469D-8708-2290772E5585.html)**
+- **[Add Virtual Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json b/corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
new file mode 100644
index 0000000..0fd19a4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+  "title": "Role Permissions",
+  "ordinal": 57,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md b/corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
new file mode 100644
index 0000000..8cc07f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
@@ -0,0 +1,7 @@
+# Role Permissions
+
+The User Role Permission ‘Provisioning: Tasks FULL’ is required to create, edit and delete Tasks.
+
+**Subtopics**  
+
+- **[Common Options](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json b/corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
new file mode 100644
index 0000000..b53f39c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+  "title": "Proxies",
+  "ordinal": 166,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html",
+  "topic_cluster": {
+    "clustering_title": "Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md b/corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
new file mode 100644
index 0000000..d01db4e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
@@ -0,0 +1,8 @@
+# Proxies
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.html)**
+- **[Defining Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.html)**
+- **[Cloud Communication](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.html)**
+- **[Provisioning with Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json b/corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
new file mode 100644
index 0000000..1183bea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+  "title": "Requirements",
+  "ordinal": 27,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md b/corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
new file mode 100644
index 0000000..763c099
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
@@ -0,0 +1,13 @@
+# Requirements
+
+Provisioning Instances typically involves many steps beyond starting a workload and VM Essentials is centered around automating everything for your application to be fully operational. There is a lot that goes on when spinning up an Instance, and to make the magic happen a few requirements need to be met.
+
+IMPORTANT
+
+By default, Agent Installation is enabled when provisioning unless deselected on the Virtual Image or SKIP AGENT INSTALL is selected from the provisioning wizard.
+
+**Subtopics**  
+
+- **[VM Provision Steps](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.html)**
+- **[Agent Install](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json b/corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
new file mode 100644
index 0000000..51a1908
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+  "title": "IP Pools",
+  "ordinal": 154,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html",
+  "topic_cluster": {
+    "clustering_title": "IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md b/corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
new file mode 100644
index 0000000..e1c7e81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
@@ -0,0 +1,8 @@
+# IP Pools
+
+Infrastructure  >  Network  >  IP Pools
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-238F9226-4EB4-4E14-B533-584277951C4B.html)**
+- **[To add a VM Essentials Network Pool](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json b/corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
new file mode 100644
index 0000000..b24c87f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+  "title": "GPU Passthrough Example",
+  "ordinal": 135,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html",
+  "topic_cluster": {
+    "clustering_title": "GPU Passthrough Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md b/corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
new file mode 100644
index 0000000..81a8c26
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
@@ -0,0 +1,25 @@
+# GPU Passthrough Example
+
+In a previous section, a Service Plan was created which consumes a GPU when a VM is provisioned using that Plan. This section shows an example provisioning a workload using that Plan and a GPU-accelerated workload running on the VM. In this example, there is an Nvidia GeForce RTX 3050 connected to one of the HVM Hosts. By passing the GPU hardware through to a provisioned VM, hardware-accelerated AI workloads can be run on the VM.
+
+Begin by navigating to Provisioning > Instances. The list of all currently-managed Instances is here along with high level information (power state, etc). To begin a new Instance, click + ADD. Choose type HVM and click NEXT. On the next pane, choose the Group and Cloud in which your desired HVM Cluster resides, name the Instance, and click NEXT.
+
+On the CONFIGURE tab, the main thing to note for this example is the PLAN configuration. This dropdown contains some default Plans that are included with HPE Morpheus VM Essentials and compatible with the HVM provisioning technology (named “1 CPU, 1GB Memory”, etc). This dropdown also includes user-created Plans, such as those you’ve created to consume GPU hardware. In the screenshot below, you can see the “GPU Plan” was selected.
+
+![../../_images/showPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-1FD71B7E-138D-4F35-B57F-AA2C3AA2E357-high.png)
+
+From here, complete the Instance provisioning wizard selecting any automation or lifecycle configurations and wait for the Instance provisioning to complete.
+
+With provisioning complete, check the attached device(s) from the HPE Morpheus VM Essentials UI. This is done from the VM level rather than the Instance level. From the Instance detail page, click on the Resources tab. Click on the name of the desired VM to access the VM detail page. Click on the Devices tab. As in the screenshot below, the attached GPU should be shown.
+
+![../../_images/attachedGpu.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5AC07D64-3534-439B-925D-858854858310-high.png)
+
+To go further, open a console session to the new VM either through HPE Morpheus VM Essentials UI or by connecting to the VM over SSH from a local terminal session. Use the `lspci` command to view all devices connected to PCI buses. The attached GPU should be shown here as it is in the UI.
+
+At this point, the VM is ready to run GPU-accelerated workloads normally. To test this, I’ll run Ollama which is an open-source tool designed to make it easy to run large language models (LLMs) locally. In the screenshot below, see the AI chatbot response to an input. This result took only a few seconds thanks to GPU hardware acceleration.
+
+![../../_images/ollamaOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-FEED6AA7-831F-4630-93F2-BD77DAB2EF2C-high.png)
+
+With the request completed, we can run the `ollama ps` command which confirms the model was running under GPU acceleration.
+
+![../../_images/gpuUsed.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-15D2AC03-19A9-47B0-8D16-7EA83603BDF2-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json b/corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
new file mode 100644
index 0000000..ed5f3da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+  "title": "Labels",
+  "ordinal": 52,
+  "parent_title": "Library",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.html",
+  "topic_cluster": {
+    "clustering_title": "Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+        "clustering_title": "Labels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+        "clustering_title": "Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md b/corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
new file mode 100644
index 0000000..659de50
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
@@ -0,0 +1,23 @@
+# Labels
+
+Labels are a categorization feature designed to allow easier filtering of list views in the VM Essentials Library. The following library constructs can be labeled:
+
+- Clouds
+- Groups
+- Tasks
+- Instances
+- Servers
+- Virtual Images
+
+Labels are visible from the list views of any constructs listed above. By default, labels are turned on in the list view but if they aren’t showing, click the gear icon (⚙) and then click Labels to enable them.
+
+The list view contains a row of filters above the list, one of which is Labels. Enter a search string to find an existing label or click the dropdown button within the field to select an existing label. This will filter the list to show only constructs which have the selected label.
+
+NOTE
+
+Any list may be filtered by any label which exists on any construct. When a label is removed from a construct and no other constructs also have that label, VM Essentials will remove the label from the list during its nightly sync. It is normal for a label to continue to exist in this list, even if it’s not currently applied to any constructs, until the next nightly sync has taken place.
+
+**Subtopics**  
+
+- **[Adding and Removing Labels](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.html)**
+- **[Running Automation Against Label Targets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json b/corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
new file mode 100644
index 0000000..4d0b9f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+  "title": "Clusters",
+  "ordinal": 96,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html",
+  "topic_cluster": {
+    "clustering_title": "Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md b/corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
new file mode 100644
index 0000000..f40f8da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
@@ -0,0 +1,8 @@
+# Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.html)**
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.html)**
+- **[Cluster Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.html)**
+- **[HVM clusters](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CA806876-1093-4A39-BE62-439C4802A915.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json b/corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
new file mode 100644
index 0000000..a11272e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+  "title": "Archive Detail Page",
+  "ordinal": 229,
+  "parent_title": "Archives",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.html",
+  "topic_cluster": {
+    "clustering_title": "Archive Detail Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+        "clustering_title": "Archive Detail Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+        "clustering_title": "Archive Detail Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md b/corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
new file mode 100644
index 0000000..b7e89c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
@@ -0,0 +1,7 @@
+# Archive Detail Page
+
+The Archive detail contains information about the Archive configuration as well as a list of files currently stored in the Archive. The Archive detail is accessed by navigating to the Archives list page (Tools > Archives) and selecting an existing Archive. As on the Archives List Page, users can download a ZIP folder containing all files in the Archive and edit the Archive from the ACTIONS menu.
+
+To delete the Archive, click DELETE. New files are added by clicking + ADD. When adding a new file, users may browse the file system on the local computer to select a file.
+
+From the files list, download or delete individual files by clicking on the appropriate selection from the ACTIONS menu.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json b/corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
new file mode 100644
index 0000000..adce3a8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+  "title": "Switch Configuration",
+  "ordinal": 353,
+  "parent_title": "Prerequisites",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.html",
+  "topic_cluster": {
+    "clustering_title": "Switch Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+        "clustering_title": "Switch Configuration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+        "clustering_title": "Switch Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md b/corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
new file mode 100644
index 0000000..ea0514a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
@@ -0,0 +1,53 @@
+# Switch Configuration
+
+## Procedure
+
+1. Configure the management interface and IP address on both switches in the pair
+2. The switch pair must be configured with `vsx-sync` enabled for high availability and redundancy 
+
+   Sample configuration:
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role primary  
+       keepalive peer 192.168.0.1 source 192.168.0.0  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role secondary  
+       keepalive peer 192.168.0.0 source 192.168.0.1  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+3. Create a Multi-Chassis Link Aggregation Group (MC-LAG) between the ArubaCX switch and the upstream network, referred to as `lag1`
+4. Configure the `lag1` interface on both switches in the pair Sample configuration: 
+
+   ```
+   ```
+   interface lag 1 multi-chassis  
+       no shutdown  
+       no routing  
+       vlan trunk native 1  
+       vlan trunk allowed 1,175  
+       lacp mode active  
+       loop-protect
+   ```
+   ```
+5. The switch ports connected to the server’s management interfaces should be set to “Trunk mode” with a “Native VLAN” Sample configuration: 
+
+   ```
+   ```
+   interface 1/1/1  
+   no shutdown  
+   no routing  
+   vlan trunk native 175  
+   vlan trunk allowed 175
+   ```
+   ```
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json b/corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
new file mode 100644
index 0000000..9f9f684
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+  "title": "Deployment Guide",
+  "ordinal": 3,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.html",
+  "topic_cluster": {
+    "clustering_title": "Deployment Guide",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+        "clustering_title": "Deployment Guide"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+        "clustering_title": "Deployment Guide"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md b/corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
new file mode 100644
index 0000000..98a5dbc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
@@ -0,0 +1,3 @@
+# Deployment Guide
+
+Deployment, installation, and initialization information is not contained in this user manual. Please refer to our dedicated HPE Morpheus VM Essentials Software [Deployment Guide](https://www.hpe.com/support/morpheus-vm-essentials-deployment-guide) for information on setting up the product and getting started with the first HVM Cluster.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json b/corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
new file mode 100644
index 0000000..15f7a76
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+  "title": "tfvars",
+  "ordinal": 218,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.html",
+  "topic_cluster": {
+    "clustering_title": "tfvars",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+        "clustering_title": "tfvars"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+        "clustering_title": "tfvars"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md b/corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
new file mode 100644
index 0000000..c22b34a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
@@ -0,0 +1,20 @@
+# tfvars
+
+A mountpoint to store tfvars files for Terraform App Blueprints.
+
+Key
+:   Pattern “tfvars/key”
+
+    Example: tfvars/my-aws-account
+
+Value
+:   The values for your tfvars file to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES and the stored values will be available for use.
+
+NOTE
+
+You may also see Cloud profiles stored at the tfvars mountpoint. They will have a key pattern like: “tfvars/profile/cloud/$cloudCode/variables”. Terraform Cloud profiles are created on the Cloud detail page (Infrastructure > Clouds > selected Cloud) under the Profiles tab. They allow Terraform apps and specs to be provisioned across multiple Clouds that require differed tfvars. See the [Cloud profiles](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/profiles.html) page for more.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json b/corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
new file mode 100644
index 0000000..6b72f17
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+  "title": "Groups",
+  "ordinal": 80,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html",
+  "topic_cluster": {
+    "clustering_title": "Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md b/corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
new file mode 100644
index 0000000..f2a4ca0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
@@ -0,0 +1,13 @@
+# Groups
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.html)**
+- **[UI](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.html)**
+- **[CLI](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.html)**
+- **[API](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.html)**
+- **[Adding Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.html)**
+- **[Managing Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.html)**
+- **[Edit Group](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.html)**
+- **[Delete Group](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.html)**
+- **[User Access](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json b/corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
new file mode 100644
index 0000000..dbf9b0d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+  "title": "Network Groups",
+  "ordinal": 147,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md b/corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
new file mode 100644
index 0000000..eed0e86
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
@@ -0,0 +1,7 @@
+# Network Groups
+
+Network Groups are useful for grouping networks during provisioning and scaling or grouping availability subnets together such that during provisioning vm’s within an instance can be round robin provisioned across availability zones.
+
+**Subtopics**  
+
+- **[Adding Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json b/corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
new file mode 100644
index 0000000..9bbb992
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+  "title": "Delete Key Pair",
+  "ordinal": 201,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+        "clustering_title": "Delete Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+        "clustering_title": "Delete Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md b/corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
new file mode 100644
index 0000000..a368fb7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
@@ -0,0 +1,11 @@
+# Delete Key Pair
+
+## About this task
+
+To Delete Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected key pair
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json b/corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
new file mode 100644
index 0000000..db4da15
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+  "title": "Provisioning Settings",
+  "ordinal": 277,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+        "clustering_title": "Provisioning Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+        "clustering_title": "Provisioning Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md b/corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
new file mode 100644
index 0000000..f0e3bd2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
@@ -0,0 +1,29 @@
+# Provisioning Settings
+
+Allow Cloud Selection
+:   Displays or hides Cloud Selection dropdown in Provisioning wizard.
+
+Allow Host Selection
+:   Displays or hides Host Selection dropdown in Provisioning wizard.
+
+Require Environment Selection
+:   Forces users to select and Environment during provisioning
+
+Hide Datastore Stats On Selection
+:   Hides Datastore utilization and size stats in provisioning and app wizards
+
+Cross-Tenant Naming Policies
+:   Enable for the `sequence` value in naming policies to apply across tenants
+
+Reuse Naming Sequence Numbers
+:   When selected, sequence numbers can be reused when Instances are removed. Deselect this option and VM Essentials will track issued sequence numbers and use the next available number each time.
+
+Show Console Keyboard Layout Settings
+:   When enabled Users will see keyboard layout settings in console sessions
+
+Deployment Archive Store
+:   Default Storage Provider for storing Deployment Archives.
+
+    NOTE
+
+    Storage Providers can be configured and managed in the Infrastructure  >  Storage section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json b/corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
new file mode 100644
index 0000000..0023a2c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+  "title": "UUID",
+  "ordinal": 220,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.html",
+  "topic_cluster": {
+    "clustering_title": "UUID",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+        "clustering_title": "UUID"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+        "clustering_title": "UUID"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md b/corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
new file mode 100644
index 0000000..9fefb19
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
@@ -0,0 +1,20 @@
+# UUID
+
+A Cypher UUID Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+Key
+:   Pattern “uuid/key”
+
+    - Example: uuid/myuuid
+
+Value
+:   Leave the Value filed blank for UUID, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the UUID will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate UUID.
+
+To delete the UUID, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json b/corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
new file mode 100644
index 0000000..ae75cd4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+  "title": "Overview",
+  "ordinal": 91,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md b/corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
new file mode 100644
index 0000000..0e60a08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
@@ -0,0 +1,3 @@
+# Overview
+
+In VM Essentials, a Cloud represents a grouping of HVM clusters (referred to as a “Private Cloud”) or an integration with a VMware vCenter appliance. This section describes general information about the Clouds construct and UI pages for Clouds. See the VMware integration guide for more specific details on integrating with VMware and the features supported by VM Essentials.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json b/corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
new file mode 100644
index 0000000..c7a392a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+  "title": "Create New Router",
+  "ordinal": 151,
+  "parent_title": "Routers",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-61053EC5-4910-454F-8B71-6B06408A6451.html",
+  "topic_cluster": {
+    "clustering_title": "Create New Router",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+        "clustering_title": "Create New Router"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+        "clustering_title": "Create New Router"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md b/corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
new file mode 100644
index 0000000..fabff5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
@@ -0,0 +1,8 @@
+# Create New Router
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click + ADD
+3. Select the router type and complete the fields on the resulting modal
+4. Once complete, click ADD NETWORK ROUTER
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json b/corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
new file mode 100644
index 0000000..595c75e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+  "title": "HVM Cluster Networking",
+  "ordinal": 109,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Cluster Networking",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+        "clustering_title": "HVM Cluster Networking"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+        "clustering_title": "HVM Cluster Networking"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md b/corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
new file mode 100644
index 0000000..1373321
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
@@ -0,0 +1,49 @@
+# HVM Cluster Networking
+
+On initial cluster provisioning, OVS bridges and Libvirt Networks are created and are immediately ready for VM provisioning. However, when adding new network interfaces, you need to create networking objects in the UI manually. Currently, the HPE Morpheus VM Essentials Software Manager does not discover new interfaces that are not in netplan. You will need to ensure they are available in the `01-base.yml` netplan file, apply it, create the bonds in the `hpe-vm` tool, and then refresh the HVM Cluster through the UI. For details, refer the installation section at the beginning of this documentation repository for more information on the `hpe-vm` tool and its use.
+
+HVM network objects are created from the Network tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the HVM Cluster). Two subtabs are shown here for Routers and Networks. From a KVM perspective, OVS Bridges and Libvirt Networks (without any port groups) are created on the Routers subtab. Port Group entries are added to existing Libvirt Networks on the Networks subtab. For this reason, it is often most logical to begin creating new HVM network objects on the Routers subtab before moving onto the Networks subtab. For a higher level discussion and diagram of recommended HVM Cluster network topology and to see where these objects fit in, refer to the example network configurations in the "Getting Started" section of this user manual.
+
+Adding Routers
+
+1. From the Routers subtab, click + ADD, then select OVS Bridge Domain
+
+   ![The list of router objects associated with an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-BBBDCD20-D1FA-4F83-99A8-84F136F334AF-high.png)
+2. On the ADD NETWORK ROUTER modal, configure the following:
+
+   1. **GROUP:** Select "Shared" to make the router object available to all Groups or select an individual Group
+   2. **NAME:** A name for the router object in HPE Morpheus VM Essentials Software
+   3. **HOST BRIDGE:** Select an existing OVS bridge or choose "Create New"
+   4. **BRIDGE NAME:** Shown only when opting to create a new Host Bridge. Provide a name for the new OVS bridge to be created. The bridge name value entered here will be used to identify the bridge throughout the UI while examining the created objects via a terminal session connected to the Host will show it identified by the interface name
+   5. **NETWORK INTERFACE:** Shown only when opting to create a new Host Bridge. Select a network interface for the new OVS bridge. Keep in mind that currently new interfaces are not discovered automatically. See the opening paragraph of this section for more information on surfacing the new interface to the HVM Cluster
+
+   NOTE
+
+   By adding a router here and selecting an existing OVS bridge, a new Libvirt Network is created without any port groups but no new OVS bridge is created. When selecting "Create New" in the Host Bridge configuration field, a new OVS bridge is created and a new Libvirt Network is also created without any port groups. A free physical interface or bond must be available to create a new OVS bridge and currently these are not automatically discovered by the HVM Cluster. See the opening paragraph of this section for more information on surfacing new interfaces to the HVM Cluster. Libvirt Port Groups are created in the next section on adding networks. For a higher level discussion and diagram of recommended HVM Cluster network topology and to see where these objects fit in, refer back to the example network configurations in the "Getting Started" section of this user manual.
+3. Click ADD NETWORK ROUTER
+
+   ![Adding new router with host bridge created](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-8F3EFC34-3BE1-4E35-B563-E7168F483CC1-high.png)
+
+Once saved, the router object is created and it appears in the list of current routers.
+
+Adding Networks
+
+As mentioned in the previous section, creating network objects on HVM clusters is akin to adding Libvirt Portgroups to an existing Libvirt Network. If continuing from the previous section on adding routers, the OVS bridges and Libvirt networks will be in place to add port groups (referred to as networks here in the UI).
+
+1. From the Networks subtab, click + ADD, then select OVS Port Group
+
+   ![The list of network objects associated with an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-8A44146F-1F64-441D-A007-F3BEC320E60C-high.png)
+2. On the CREATE NETWORK modal, configure the following:
+
+   1. **GROUP:** Select "Shared" to make the router object available to all Groups or select an individual Group
+   2. **NAME:** A name for the network object in HPE Morpheus VM Essentials Software
+   3. **CIDR:** The CIDR range for the new network
+   4. **GATEWAY:** The network gateway address
+   5. **DNS PRIMARY:** The address for the primary DNS server
+   6. **DNS SECONDARY:** The address for the secondary DNS server
+   7. **ROUTER:** Select an existing OVS bridge. If you need to create a new OVS bridge, add a new "OVS Bridge Domain" from the Routers subtab (described above) and select "Create New" for it's "Host Bridge" field configuration. Additional details on router objects are provided above.
+   8. **VLAN ID:** A VLAN ID for the Libvirt Port Group to be created
+   9. **NETWORK POOL:** A typeahead field for selecting a currently-configured IP Pool
+3. Click SAVE CHANGES
+
+   ![Creating a new network object](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-6359D4EE-C3F8-431F-850D-A21F7470714E-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json b/corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
new file mode 100644
index 0000000..dc82f6d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+  "title": "Overview",
+  "ordinal": 238,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md b/corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
new file mode 100644
index 0000000..fe04374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
@@ -0,0 +1,3 @@
+# Overview
+
+VM Essentials can integrate with many of the most common identity source technologies, such as Active Directory, Okta, and many others. These can be configured via the Identity Sources button on the Users list page (Administration > Users). These integrations map roles within these sign-on tools to equivalent roles in VM Essentials so at first log in users are assigned the appropriate role.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json b/corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
new file mode 100644
index 0000000..65d8c7b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+  "title": "A Note on Proxies",
+  "ordinal": 346,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.html",
+  "topic_cluster": {
+    "clustering_title": "A Note on Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+        "clustering_title": "A Note on Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+        "clustering_title": "A Note on Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md b/corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
new file mode 100644
index 0000000..df2d60c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
@@ -0,0 +1,25 @@
+# A Note on Proxies
+
+Proxy configurations are known to vary in some organizations and makes building a base blueprint a little more difficult. In order to fully configure proxies a few environment variables must be set in the /etc/environment file (This can be done automatically in a default user-data script for cloud-init as well in edit cloud).
+
+```
+```
+http_proxy="http://myproxyaddress:8080"  
+https_proxy="http://myproxyaddress:8080"  
+ftp_proxy="http://myproxyaddress:8080"  
+no_proxy=127.0.0.1,localhost,applianceUrl  
+https_no_proxy=127.0.0.1,localhost,applianceUrl
+```
+```
+
+IMPORTANT
+
+It is very important to properly set the no\_proxy list (applianceUrl) should be replaced with the actual appliance url. In future releases, morpheus plans to automatically take care of this.
+
+NOTE
+
+If using cloud-init agent install mode these settings need to be set in the custom Cloud-Init User data section of “Edit Cloud” or “Edit Virtual Image”
+
+IMPORTANT
+
+If using this virtual machine as a docker host, proxy settings must also be configured in the docker config. See Docker guides for instructions on how to properly set this. If necessary this can be wrapped in a task automation workflow for your own use.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json b/corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
new file mode 100644
index 0000000..ba31419
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+  "title": "Getting Started",
+  "ordinal": 317,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md b/corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
new file mode 100644
index 0000000..c05c099
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
@@ -0,0 +1,23 @@
+# Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow VM Essentials to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json b/corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
new file mode 100644
index 0000000..6d1c7ca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+  "title": "Supported Bucket Types",
+  "ordinal": 178,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Bucket Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+        "clustering_title": "Supported Bucket Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+        "clustering_title": "Supported Bucket Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md b/corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
new file mode 100644
index 0000000..4f07b51
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
@@ -0,0 +1,9 @@
+# Supported Bucket Types
+
+- Alibaba
+- Amazon S3
+- Azure
+- Google Cloud Storage
+- Openstack Swift
+- Rackspace CDN
+- Generic S3
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json b/corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
new file mode 100644
index 0000000..50e7c97
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+  "title": "Hardware Requirements",
+  "ordinal": 105,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-634760AA-7E46-42A7-AD08-85CCE4656873.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+        "clustering_title": "Hardware Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+        "clustering_title": "Hardware Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md b/corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
new file mode 100644
index 0000000..4e65f2b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
@@ -0,0 +1,36 @@
+# Hardware Requirements
+
+- **Operating System**: Ubuntu 24.04 or Ubuntu 22.04
+- **CPU**: One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory**: 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
+- **Disk Space**: For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while VM Essentials will configure Ceph for multi-node clusters
+- **Network Connectivity**: HVM hosts must be assigned static IP addresses. They also need DNS resolution of the VM Essentials appliance and Internet access in order to download and install system packages for dependencies, such as KVM, Open vSwitch (OVS), and more
+
+NOTE
+
+Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.
+
+NOTE
+
+Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus VM Essentials Agent communication with the HPE Morpheus VM Essentials manager | HVM Host | HPE Morpheus VM Essentials manager | 443 | TCP |
+| HPE Morpheus VM Essentials Agent communication with the HVM Host for hypervisor console | HPE Morpheus VM Essentials manager | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus VM Essentials manager | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus VM Essentials manager SSH access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTP) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json b/corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
new file mode 100644
index 0000000..af440da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+  "title": "Supported Datastore Types",
+  "ordinal": 111,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-63ADF495-37BF-424E-85F4-614EE91DA301.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Datastore Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+        "clustering_title": "Supported Datastore Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+        "clustering_title": "Supported Datastore Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md b/corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
new file mode 100644
index 0000000..f2f12c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
@@ -0,0 +1,12 @@
+# Supported Datastore Types
+
+In relation to HVM Clusters, discussion of storage primarily centers around datastores, which serve as targets for holding virtual machine disks and storing images. Currently, six datastore types are supported with HVM Clusters:
+
+- Directory Pools
+- NFS Pools
+- GFS2 Pools
+- 3Par
+- HPE Alletra Block Storage HVM
+- HPE Alletra Block Storage Bare Metal
+
+The next several sections will cover Directory Pools, NFS Pools, and GFS2 Pools in detail, including pros and cons of each type, how to configure storage servers, and how to add new datastores through the UI. For more on integrating 3Par servers and HPE Alletra Storage, see the integration guides for those technologies elsewhere in this user manual.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json b/corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
new file mode 100644
index 0000000..f28d629
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+  "title": "Advanced Options (Search Domains)",
+  "ordinal": 143,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced Options (Search Domains)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+        "clustering_title": "Advanced Options (Search Domains)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+        "clustering_title": "Advanced Options (Search Domains)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md b/corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
new file mode 100644
index 0000000..bb521c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
@@ -0,0 +1,3 @@
+# Advanced Options (Search Domains)
+
+Search domains are appended to DNS searches when a **non** fully qualified domain name (short name) is queried. Search domains can be entered as comma separated values, which will be added to DNS configurations, such as /etc/resolv.conf. These domains are injected through cloud-init or other method chosen for the virtual image.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json b/corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
new file mode 100644
index 0000000..27813cc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+  "title": "Setting Heartbeat Datastores",
+  "ordinal": 119,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-64001B38-0509-46D5-854E-3A8500798DEE.html",
+  "topic_cluster": {
+    "clustering_title": "Setting Heartbeat Datastores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+        "clustering_title": "Setting Heartbeat Datastores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+        "clustering_title": "Setting Heartbeat Datastores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md b/corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
new file mode 100644
index 0000000..e760503
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
@@ -0,0 +1,13 @@
+# Setting Heartbeat Datastores
+
+While not set by default, after creating a datastore, users may choose to set it as a heartbeat datastore. Heartbeat datastores are essential for high-availability failover of VMs in the HVM Cluster. When heartbeat targets are enabled, each HVM Host continuously updates a heartbeat file, which is monitored by the other Hosts. When a Host becomes unavailable, the remaining Hosts detect this by discovering that the heartbeat file is no longer being updated. At that point, the Cluster initiates a failover process to migrate affected VMs to a new host. For greater detail on high-availability and the failover process, see [this knowledge article](https://cdn.support.hpe.com/hpesc/public/docDisplay?docId=sf000111669en_us&docLocale=en_US).
+
+To set selected datastores as heartbeat targets, use the steps below. Multiple heartbeat datastores can be enabled for additional redundancy:
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the Data Stores subtab
+3. Within the Data Stores subtab, edit the desired datastore (pencil icon)
+4. Mark the box labeled "HEARTBEAT TARGET
+5. Click Save changes
+
+![Editing a GFS2 datastore to make it a heartbeat datastore](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5ACF121C-3475-4BFB-8794-ED483A879314-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.json b/corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
new file mode 100644
index 0000000..0849fce
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+  "title": "Setting the default domain on a Network",
+  "ordinal": 164,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-650706CA-915E-4239-9D69-35902E82B60E.html",
+  "topic_cluster": {
+    "clustering_title": "Setting the default domain on a Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+        "clustering_title": "Setting the default domain on a Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+        "clustering_title": "Setting the default domain on a Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.md b/corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
new file mode 100644
index 0000000..cd46239
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
@@ -0,0 +1,9 @@
+# Setting the default domain on a Network
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network.
+2. Edit the target Network.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json b/corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
new file mode 100644
index 0000000..019c549
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+  "title": "System Images",
+  "ordinal": 73,
+  "parent_title": "Configuring Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6549D43B-D0BB-4416-9771-AF11F387B629.html",
+  "topic_cluster": {
+    "clustering_title": "System Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+        "clustering_title": "System Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+        "clustering_title": "System Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md b/corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
new file mode 100644
index 0000000..1b21425
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
@@ -0,0 +1,7 @@
+# System Images
+
+System Virtual Images are pre-configured with metadata and have Cloud-Init or Cloudbase-Init installed. These images are ready to be provisioned with no configuration necessary, however it is required to populate Administration > Settings > Provisioning, Cloud-Init section, with user data as well as User Profile(s) users data when creating additional users prior to provisioning, as the user data from these sections is required when provisioning System provided Virtual Images.
+
+NOTE
+
+System Images settings are not editable.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json b/corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
new file mode 100644
index 0000000..11600c0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+  "title": "HVM Cluster Storage",
+  "ordinal": 110,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Cluster Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+        "clustering_title": "HVM Cluster Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+        "clustering_title": "HVM Cluster Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md b/corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
new file mode 100644
index 0000000..75d3366
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
@@ -0,0 +1,14 @@
+# HVM Cluster Storage
+
+**Subtopics**  
+
+- **[Supported Datastore Types](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-63ADF495-37BF-424E-85F4-614EE91DA301.html)**
+- **[Datastore Types Pros and Cons](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A1E79BA5-CE31-4357-878E-11464E03158C.html)**
+- **[Directory Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.html)**
+- **[Adding Directory Pools](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.html)**
+- **[NFS Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.html)**
+- **[Adding NFS Pools](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.html)**
+- **[GFS2 Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.html)**
+- **[Adding GFS2 Pools](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3702D75B-9505-40D0-B220-7739F5F72760.html)**
+- **[Setting Heartbeat Datastores](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-64001B38-0509-46D5-854E-3A8500798DEE.html)**
+- **[Maintaining GFS2 Consistency and High Availability](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B3241978-4E00-4630-A8AB-E597193E51E2.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json b/corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
new file mode 100644
index 0000000..e181da5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+  "title": "For All Agent Install modes",
+  "ordinal": 34,
+  "parent_title": "Agent Install Modes",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-69626666-7280-4AF5-9871-FA2D82CED05E.html",
+  "topic_cluster": {
+    "clustering_title": "For All Agent Install modes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+        "clustering_title": "For All Agent Install modes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+        "clustering_title": "For All Agent Install modes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md b/corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
new file mode 100644
index 0000000..d42267b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
@@ -0,0 +1,20 @@
+# For All Agent Install modes
+
+When an Instance is provisioned and the Agent does not install, verify the following for any agent install mode:
+
+- The VM Essentials `appliance_url` (Administration > Settings) is both reachable and resolvable from the provisioned node.
+- The `appliance_url` begins with to `https://`, not `http://`.
+
+NOTE
+
+Be sure to use `https://` even when using an IP address for the appliance.
+
+- Inbound connectivity access to the VM Essentials Appliance from provisioned VMs and HVM cluster hosts on port 443 (needed for Agent communication)
+- Private images (those not provided with VM Essentials by default) must have their credentials entered. These can be entered or edited in the Library > Virtual Images section by clicking the edit button (pencil icon) next to the appropriate image.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced section during provisioning. IP Pools can also be created in the Infrastructure > Network > IP Pools section and added any Cloud’s network section for IPAM.
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the VM Essentials appliance can be used.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json b/corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
new file mode 100644
index 0000000..36e1ba2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+  "title": "Deleting Clouds",
+  "ordinal": 95,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+        "clustering_title": "Deleting Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+        "clustering_title": "Deleting Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md b/corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
new file mode 100644
index 0000000..1902510
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
@@ -0,0 +1,17 @@
+# Deleting Clouds
+
+## About this task
+
+To delete a Cloud:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Clouds link in the sub navigation bar.
+3. Click the Delete icon of the cloud to delete.
+
+## Results
+
+IMPORTANT
+
+All Instances, managed Hosts and VMs must be removed prior to deleting a Cloud.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json b/corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
new file mode 100644
index 0000000..6c02606
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+  "title": "Dell EMC ECS Buckets",
+  "ordinal": 183,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.html",
+  "topic_cluster": {
+    "clustering_title": "Dell EMC ECS Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+        "clustering_title": "Dell EMC ECS Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+        "clustering_title": "Dell EMC ECS Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md b/corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
new file mode 100644
index 0000000..050fa0d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
@@ -0,0 +1,84 @@
+# Dell EMC ECS Buckets
+
+## About this task
+
+NOTE
+
+A Dell EMC ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell EMC ECS Bucket.
+
+To Add a Dell EMC ECS Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell EMC ECS bucket.
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json b/corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
new file mode 100644
index 0000000..2dcc303
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+  "title": "Adding Tasks",
+  "ordinal": 66,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6B80D87B-8461-414D-9172-07E68896EB06.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+        "clustering_title": "Adding Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+        "clustering_title": "Adding Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md b/corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
new file mode 100644
index 0000000..589fa10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
@@ -0,0 +1,20 @@
+# Adding Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. On the Tasks tab, click the Add button
+3. From the New Task Wizard input a name for the task
+4. Select the type of task from from the type dropdown
+5. Input the appropriate configuration details. These will vary based on the selected Task type.
+6. Once done, click SAVE CHANGES
+
+## Results
+
+TIP
+
+When writing a Task config, it’s often necessary to reference VM Essentials variables which pertain to the specific Instance the Task is being run against. VM Essentials includes a pop-out column along the right side of the Add/Edit Task modal which lists available variables. Click and drag the relevant variable into the config area and VM Essentials will automatically fill in the variable call formatted for the currently chosen Task type. See the screenshot below.
+
+TIP
+
+When writing a Task that calls back into the HPE Morpheus VM Essentials API, pass an `Authorization: Execution <%=executionLeaseToken%>` header. The system API will authenticate against that during the life of the Task execution only. This is preferred over other methods of authorizing Task calls as there was a risk of the token expiring in the middle of the Task run.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json b/corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
new file mode 100644
index 0000000..a7b37ae
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+  "title": "Editing volumes",
+  "ordinal": 376,
+  "parent_title": "Volumes tab",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.html",
+  "topic_cluster": {
+    "clustering_title": "Editing volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+        "clustering_title": "Editing volumes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+        "clustering_title": "Editing volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md b/corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
new file mode 100644
index 0000000..40660a6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
@@ -0,0 +1,28 @@
+# Editing volumes
+
+## About this task
+
+You can edit the volumes individually for VMs created without selecting the Ransomware Detection check box in the ADD DATA STORE screen.
+
+## Procedure
+
+1. Create a datastore without selecting the Ransomware Detection check box. 
+
+   To create a datastore, go to Infrastructure > Clusters, click the cluster name, then click Storage > Add. For more information on creating a datastore, see [Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html).
+2. Create a VM with the Ransomware Detection disabled datastore.
+
+   To begin provisioning a VM instance with the Ransomware Detection disabled datastore, go to Provisioning > Instances. For more information on creating a VM instance, see [Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html).
+3. Navigate to Infrastructure > Storage > Servers > Volumes tab.
+
+   The Actions drop-down menu is available for each volume that has the Ransomware Detection disabled.
+
+   NOTE
+
+   For VMs created with Ransomware Detection enabled datastore, the Actions drop-down is not displayed for such volumes.
+4. Click Actions > Edit.
+
+   The EDIT VOLUME message is displayed.
+
+   ![Edit volume](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-79282845-7740-4731-9DAF-BDAA8AC698BB-high.png)
+5. To change the status, select the Ransomware Detection check box if it is disabled or clear the check box if it is enabled.
+6. Click Save. The changes to the ransomware monitoring are saved.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json b/corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
new file mode 100644
index 0000000..0c2d17c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+  "title": "CLI",
+  "ordinal": 83,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.html",
+  "topic_cluster": {
+    "clustering_title": "CLI",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+        "clustering_title": "CLI"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+        "clustering_title": "CLI"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md b/corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
new file mode 100644
index 0000000..482c2c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
@@ -0,0 +1,3 @@
+# CLI
+
+To view all groups: `groups list`. To use the group: `groups use <id>` or `groups use "group name"` To get a JSON output of a specific group: `groups get <id> -j` or `groups get "group name" -j`
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json b/corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
new file mode 100644
index 0000000..1ed817f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+  "title": "Vault",
+  "ordinal": 222,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.html",
+  "topic_cluster": {
+    "clustering_title": "Vault",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+        "clustering_title": "Vault"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+        "clustering_title": "Vault"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md b/corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
new file mode 100644
index 0000000..4b13859
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
@@ -0,0 +1,25 @@
+# Vault
+
+Use this mountpoint to store Cypher secrets in a Hashicorp Vault server backend rather than VM Essentials. Additionally, you can call secrets stored in Vault from this Cypher mountpoint even if they are only saved there and not listed in the VM Essentials Cypher UI. This requires installation and configuration of the Hashicorp Vault plugin. See the YouTube video embedded in this section for more information on adding the plugin, configuration, and a demonstration of its capabilities.
+
+NOTE
+
+It’s recommended that you use a long-lived token as attempts to call Vault-stored values into Tasks will stop working if the token is no longer good. In such a case you’d have to obtain a new token, delete the Cypher entry with the old token, and create a new one to restore functionality once again. Using a long-lived token will prevent the need to do this often.
+
+Key
+:   Pattern “vault/<engineMount>/<secretPath>/data/<key>” (ex. vault/KV2/secret/data/morpheus/lab)
+
+Value
+:   Enter your key/value pair here in valid JSON (ex. {“hello”: “world”} )
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES. The example BASH script below onboards the value stored in Vault from the secret/data/morpheus/lab mountpoint:
+
+```
+```
+from_vault="<%= cypher.read('vault/KV2/secret/data/morpheus/lab') %>"  
+echo $from_vault
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json b/corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
new file mode 100644
index 0000000..c2611a8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+  "title": "Agent Install",
+  "ordinal": 32,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+        "clustering_title": "Agent Install"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+        "clustering_title": "Agent Install"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md b/corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
new file mode 100644
index 0000000..f0a5ef5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
@@ -0,0 +1,18 @@
+# Agent Install
+
+When provisioning an Instance, there are some network and configuration requirements to successfully install the Agent. Typically when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach VM Essentials, or depending on Agent install mode, VM Essentials is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the VM Essentials Appliance via the `appliance_url` set in Administration > Settings over both 443 and 80. When an Instance is provisioned from VM Essentials, it must be able to reach the VM Essentials appliance via the `appliance_url` or the Agent will not be installed.
+
+In addition to the main `appliance_url` in Administration > Settings, additional `appliance_urls` can be set per Cloud in the Advanced options of the Cloud configuration pane when creating or editing a Cloud. When this field is populated, it will override the main appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The VM Essentials current log, located at `/var/log/morpheus/morpheus-ui/current`, is very helpful when troubleshooting Agent installations.
+
+**Subtopics**  
+
+- **[Agent Install Modes](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.html)**
+- **[SSH/Winrm](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.html)**
+- **[VMware tools (vmtools) RPC mode](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.html)**
+- **[Cloud-Init Agent install mode](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json b/corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
new file mode 100644
index 0000000..1af1407
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+  "title": "Agent Install Modes",
+  "ordinal": 33,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install Modes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+        "clustering_title": "Agent Install Modes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+        "clustering_title": "Agent Install Modes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md b/corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
new file mode 100644
index 0000000..0817434
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
@@ -0,0 +1,11 @@
+# Agent Install Modes
+
+There are 3 Agent install modes:
+
+- SSH/WinRM
+- VMware Tools
+- Cloud-init
+
+**Subtopics**  
+
+- **[For All Agent Install modes](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-69626666-7280-4AF5-9871-FA2D82CED05E.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json b/corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
new file mode 100644
index 0000000..7f75f5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+  "title": "Summary",
+  "ordinal": 209,
+  "parent_title": "Backups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.html",
+  "topic_cluster": {
+    "clustering_title": "Summary",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+        "clustering_title": "Summary"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+        "clustering_title": "Summary"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md b/corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
new file mode 100644
index 0000000..5d8454a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
@@ -0,0 +1,12 @@
+# Summary
+
+The Backups Summary section shows the following metrics:
+
+- Number of Configured Backups trend
+- Backup Success Rate
+- Number of Completed Backups
+- Number of Failed Backups
+- Total Size of Backups (MB) trend
+- Upcoming and In Progress Backups
+
+If a User’s Role permission for Backups is set to User, the user will only see metrics for backups they own.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json b/corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
new file mode 100644
index 0000000..fa8facd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+  "title": "Overview",
+  "ordinal": 240,
+  "parent_title": "Plans",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md b/corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
new file mode 100644
index 0000000..a7402f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
@@ -0,0 +1,11 @@
+# Overview
+
+Service Plans determine the amount of compute resources available to each Instance. When provisioning new Instances from VM Essentials, a plan is selected which determines the number of CPU cores, amount of memory and the amount of storage available to the associated machines. Additionally, when converting discovered instances in integrated clouds to VM Essentials-managed Instances, the user selects a plan which best fits the instance as it is currently configured. When Instances are reconfigured, a new plan may be selected which redefines the compute resources which should be available to the Instance. Plans can be as specific or open-ended as the user would like, restricting the user to the resources defined in the plan or allowing the user to increase those amounts at provision time.
+
+The Plans section Administration > Plans is where Plans are managed. A set of Service Plans are seeded by VM Essentials for immediate use with supported Cloud type out of the box. Additional Plans may be synced in on integrating additional Clouds depending on the type. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types.
+
+**Subtopics**  
+
+- **[Create Service Plan](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.html)**
+- **[Service Plan Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3E03B539-B71C-4D2E-A218-23713D723408.html)**
+- **[Service Plan Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.json b/corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.json
new file mode 100644
index 0000000..2d909b9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+  "title": "Overview",
+  "ordinal": 150,
+  "parent_title": "Routers",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7138E486-AE62-4778-9358-F098126785A5.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.md b/corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.md
new file mode 100644
index 0000000..719388f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7138E486-AE62-4778-9358-F098126785A5.md
@@ -0,0 +1,5 @@
+# Overview
+
+Routers can be viewed, created, and managed from the Routers tab of the Infrastructure > Networks page. VM Essentials supports the creation of the following router types depending on networks that are currently configured:
+
+- OVS Bridge Domain
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json b/corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
new file mode 100644
index 0000000..92feb25
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+  "title": "Key",
+  "ordinal": 221,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.html",
+  "topic_cluster": {
+    "clustering_title": "Key",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+        "clustering_title": "Key"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+        "clustering_title": "Key"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md b/corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
new file mode 100644
index 0000000..8475e6f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
@@ -0,0 +1,20 @@
+# Key
+
+A Cypher Key generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key).
+
+Key
+:   Pattern “key/bit\_length/key”
+
+    - Example: key/256/mykey
+
+Value
+:   Leave the Value filed blank for key, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the AES Key will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate AES Key.
+
+To delete the UUID, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json b/corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
new file mode 100644
index 0000000..3b69546
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+  "title": "API Access",
+  "ordinal": 305,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-74590319-12A6-4101-9043-8DDB56BB0720.html",
+  "topic_cluster": {
+    "clustering_title": "API Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+        "clustering_title": "API Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+        "clustering_title": "API Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md b/corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
new file mode 100644
index 0000000..0a624e5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
@@ -0,0 +1,18 @@
+# API Access
+
+Click the API Access button to expand the “API ACCESS” modal. In this modal you can generate or refresh access tokens that can be used with Morpheus API and Morpheus CLI.
+
+If no token yet exists for a particular “CLIENT ID”, click ACTIONS and then Generate. If a token has expired, we can also regenerate that token by clicking ACTIONS and then Regenerate. After regenerating a particular token, you would need to ensure any scripts using those tokens are updated.
+
+- **morph-api:** Used for VM Essentials API access and should be the default token-type used
+- **morph-cli:** Used for VM Essentials CLI access
+- **morph-automation:** Used by the internal Task engine and by jRuby-type Tasks to make API calls. It shouldn’t be used externally for other types of access or in external automation. It is surfaced in the UI so users can see if a token exists and can clear it when necessary
+- **morph-customer:** This token is available for legacy implementations and was previously recommended for custom API access (similar to the morph-api token). It’s not recommended for use but is still available to maintain support for legacy custom automation which may still be in use on customer sites
+
+After navigating away from the User Settings page, the complete access and refresh tokens will be masked from view. If these are lost or compromised, you can eliminate a token completely by clicking ACTIONS and then Clear. If you need to generate a new token for the same Client ID, click ACTIONS and then Regenerate.
+
+![../../_images/user-tokens.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-274AD26D-C940-4740-BBC7-7970107CCB4B-high.png)
+
+NOTE
+
+Access Tokens are only displayed/available after generation. Copy new Tokens and store appropriately before navigating from `/user-settings`, they will not be displayed again.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json b/corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
new file mode 100644
index 0000000..bc8171c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+  "title": "User Settings",
+  "ordinal": 295,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md b/corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
new file mode 100644
index 0000000..745b4a8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
@@ -0,0 +1,13 @@
+# User Settings
+
+User settings are accessed by clicking on your display name in the far upper-right corner of the application window. In this dropdown menu, click on the “USER SETTINGS” link.
+
+**Subtopics**  
+
+- **[User Photo](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-40300B80-D69C-450B-9848-7A21A3141005.html)**
+- **[2 Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3B34F036-4C25-4058-B5F4-5340545BE821.html)**
+- **[Preferences](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html)**
+- **[Linux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html)**
+- **[API Access](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-74590319-12A6-4101-9043-8DDB56BB0720.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json b/corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
new file mode 100644
index 0000000..881d069
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+  "title": "Deleting Tasks",
+  "ordinal": 68,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+        "clustering_title": "Deleting Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+        "clustering_title": "Deleting Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md b/corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
new file mode 100644
index 0000000..7877e98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
@@ -0,0 +1,6 @@
+# Deleting Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. Click the trash icon (🗑) on the row of the Task you wish to delete
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json b/corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
new file mode 100644
index 0000000..f7233d9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+  "title": "Role Permission Sections",
+  "ordinal": 249,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+        "clustering_title": "Role Permission Sections"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+        "clustering_title": "Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md b/corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
new file mode 100644
index 0000000..c605cf2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
@@ -0,0 +1,18 @@
+# Role Permission Sections
+
+Features
+:   Controls User access level for UI sections and features in VM Essentials. The complete feature permissions grid is included below.
+
+Groups
+:   Controls User access level for Groups. Groups are not a Multi-Tenant construct, only Groups created in the current Tenant will be visible.
+
+Cluster Types
+:   Controls user access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters (assuming the Role also has feature access to applicable permissions related to adding Clusters) VDI Pools
+
+    Controls User access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+    Workflows
+    :   Controls User access to configured Workflows, including the ability to view, edit, execute, or apply to Library item configurations
+
+Tasks
+:   Controls User access to configured Tasks, including the ability to view, edit, execute, or apply to Workflows
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json b/corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
new file mode 100644
index 0000000..ed8b2c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+  "title": "Editing Existing Routers",
+  "ordinal": 152,
+  "parent_title": "Routers",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Existing Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+        "clustering_title": "Editing Existing Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+        "clustering_title": "Editing Existing Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md b/corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
new file mode 100644
index 0000000..3f7a726
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
@@ -0,0 +1,7 @@
+# Editing Existing Routers
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the pencil icon for the appropriate router
+3. After editing router fields, click SAVE
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json b/corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
new file mode 100644
index 0000000..d4881da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+  "title": "Editing Tasks",
+  "ordinal": 67,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+        "clustering_title": "Editing Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+        "clustering_title": "Editing Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md b/corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
new file mode 100644
index 0000000..8cc589a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
@@ -0,0 +1,8 @@
+# Editing Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. Click the pencil icon (✎) on the row of the task you wish to edit
+3. Modify Task as needed
+4. Once done, click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json b/corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
new file mode 100644
index 0000000..0179011
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+  "title": "Converting Discovered Resources to Managed Instances",
+  "ordinal": 46,
+  "parent_title": "Creating Instances",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.html",
+  "topic_cluster": {
+    "clustering_title": "Converting Discovered Resources to Managed Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+        "clustering_title": "Converting Discovered Resources to Managed Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+        "clustering_title": "Converting Discovered Resources to Managed Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md b/corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
new file mode 100644
index 0000000..8dea8c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
@@ -0,0 +1,14 @@
+# Converting Discovered Resources to Managed Instances
+
+When creating new cloud integrations (or updating existing ones), users may opt for VM Essentials to onboard any existing resources that currently reside in the Cloud. For example, these may be virtual machines that exist on vCenter hosts prior to integration with VM Essentials. With the Add/Edit Cloud modal open, mark INVENTORY EXISTING INSTANCES for VM Essentials to automatically onboard these resources. Not only will VM Essentials inventory these hosts at the time the cloud is integrated (or updated), it will also continue to poll the target cloud every five minutes (by default) for newly added or removed servers. Users can see these discovered servers by looking in Infrastructure > Compute. Depending on the type of resource, it may appear on the Virtual Machines tab, the Containers tab, or another tab. Additionally, we can see a list of discovered servers on Cloud detail pages (Infrastructure > Clouds > Selected Cloud). Just click on the tabs for VMs, Containers or Hosts tab. Discovered resources will be indicated as such whereas containers which are associated with a managed Instance will be marked as a “Managed”.
+
+Additionally, VM Essentials allows users to convert discovered resources into managed Instances. Begin from the server detail page (Infrastructure > Compute > Virtual Machines > selected machine) and from the ACTIONS menu select “Convert to Managed”. At this point, we must make a number of selections:
+
+- Select a Group (this dropdown contains a filtered list of Groups in which the associated Cloud resides)
+- Username and password for a seeded account
+- Opt to install VM Essentials Agent or not
+- Select the Instance Type which should be associated with the new Instance containing this VM
+- Identify the operating system
+- Select a Plan (this dropdown contains a filtered list of plans which correlate to the size of the VM)
+
+Finally, click EXECUTE. Once this process is completed, the server will be indicated as “Managed” in the servers list. Additionally, a new Instance will appear on the Instances List page (Provisioning > Instances). We can now work with it in the same way we can work with any other Instance, such as by expanding the Instance horizontally with added nodes.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json b/corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
new file mode 100644
index 0000000..0fc2374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+  "title": "Create A Backup Job",
+  "ordinal": 309,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.html",
+  "topic_cluster": {
+    "clustering_title": "Create A Backup Job",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+        "clustering_title": "Create A Backup Job"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+        "clustering_title": "Create A Backup Job"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md b/corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
new file mode 100644
index 0000000..1f4e5e0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
@@ -0,0 +1,22 @@
+# Create A Backup Job
+
+## About this task
+
+A Backup Job in HPE Morpheus Enterprise holds the schedule timing and retention count for automated backups. If you already have a Job configured, you can move on to the next section. If currently-existing options do not make sense for your backup needs or if none currently exist, create a new execution schedule. See the [execute scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html) section of this documentation for additional information on creating these schedules. To begin a new schedule, use the following steps:
+
+## Procedure
+
+1. Navigate to Library > Automation
+2. Click on the “Execute Scheduling” tab
+3. Click + ADD
+4. Enter schedule timing using `cron` notation
+5. Click SAVE
+
+## Results
+
+With the execution schedule created, we can move on to creating the Backup Job itself. A Backup Job includes both the backup retention count and an execution schedule (which we just created).
+
+1. Navigate to Backups > Jobs
+2. Click + ADD
+3. Name the Job, then configure the retention count and select the correct execution schedule
+4. Click SAVE
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json b/corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
new file mode 100644
index 0000000..10894de
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+  "title": "Identity Sources",
+  "ordinal": 237,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md b/corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
new file mode 100644
index 0000000..7b54334
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
@@ -0,0 +1,7 @@
+# Identity Sources
+
+Administration > Tenants > (Selected Tenant) > Identity Sources Administration > Users > Identity Sources
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json b/corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
new file mode 100644
index 0000000..b5da061
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+  "title": "Static and IP Pools",
+  "ordinal": 142,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.html",
+  "topic_cluster": {
+    "clustering_title": "Static and IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+        "clustering_title": "Static and IP Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+        "clustering_title": "Static and IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md b/corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
new file mode 100644
index 0000000..2290cd4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
@@ -0,0 +1,42 @@
+# Static and IP Pools
+
+## About this task
+
+To configure a network for Static IP Assignment:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, add the following: 
+
+   - Gateway
+   - DNS Primary
+   - DNS Secondary
+   - CIDR ex 10.10.10.0/22
+   - VLAN ID (if necessary)
+   - Network Pool \* Leave as “choose a pool” for entering a static IP while provisioning \* Select a Pool to use a pre-configured VM Essentials or IPAM Integration IP Pool
+   - The Permissions settings are used for Multi-Tenant resource configuration
+
+     - Leave settings as default if used in a single-tenant environment (only one Tenant in your VM Essentials appliance)
+     - To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public
+     - To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private
+   - Active
+
+     - Leave as enabled to use this network
+     - Disable the active flag to remove this network from available network options
+5. Save Changes
+
+## Results
+
+NOTE
+
+When selecting a network with DHCP disabled and no IP Pool assigned during provisioning, an IP entry field will populate to the right of the selected network(s):
+
+NOTE
+
+When selecting a network with an IP Pool assigned during provisioning, the name of the IP pool will populate to the right of the selected network(s). IP Pools override DHCP.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json b/corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
new file mode 100644
index 0000000..49ebc25
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+  "title": "Delete HPE ANW DSS Port Group Network",
+  "ordinal": 363,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.html",
+  "topic_cluster": {
+    "clustering_title": "Delete HPE ANW DSS Port Group Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+        "clustering_title": "Delete HPE ANW DSS Port Group Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+        "clustering_title": "Delete HPE ANW DSS Port Group Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md b/corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
new file mode 100644
index 0000000..1de674b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
@@ -0,0 +1,13 @@
+# Delete HPE ANW DSS Port Group Network
+
+## About this task
+
+To delete a HPE ANW DSS Port Group network, follow these steps:
+
+## Procedure
+
+1. Navigate to
+2. Select the network you want to delete from the list.
+3. Click on the delete icon (🗑) next to the network name. 
+
+   ![../../_images/4_delete_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5DFCE9ED-5DDA-469D-B118-24F0B3AC0429-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json b/corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
new file mode 100644
index 0000000..79e415b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+  "title": "ArubaCX Network Integration",
+  "ordinal": 348,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html",
+  "topic_cluster": {
+    "clustering_title": "ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md b/corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
new file mode 100644
index 0000000..cb0c172
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
@@ -0,0 +1,9 @@
+# ArubaCX Network Integration
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.html)**
+- **[Adding ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.html)**
+- **[Add ArubaCX Integration to a Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json b/corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
new file mode 100644
index 0000000..e5257f6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+  "title": "Prerequisites",
+  "ordinal": 367,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md b/corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
new file mode 100644
index 0000000..0f6c283
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
@@ -0,0 +1,35 @@
+# Prerequisites
+
+- All HPE Alletra MP Storage iSCSI ports are reachable from each of the cluster hosts
+- The `multipath.conf` settings on each node should be configured as follows:
+
+```
+```
+defaults {  
+    find_multipaths yes  
+    user_friendly_names no  
+}
+```
+```
+
+Before you set up Active-Active Peer Persistence (AAPP) replication, ensure that the following requirements are met:
+
+**Supported configurations**
+
+- Remote Copy is configured using either Fibre Channel (RCFC) or IP (RCIP).
+- Replication targets are synchronous only.
+- HPE Alletra MP B10000 arrays are running OS version 10.5.0 or later.
+- AAPP replication supports only a 1:1 target mapping.
+
+**Array configuration (outside VM Essentials)**
+
+- Complete the AAPP Remote Copy configuration on both primary and secondary arrays.
+- Configure replication ports and define targets on both arrays.
+- Configure a Quorum Witness for the arrays.
+
+For more information about array configuration, see HPE GreenLake for Block Storage UI 2.5 User Guide.
+
+**VM Essentials setup**
+
+- Add both primary and secondary arrays as Storage Servers in Infrastructure > Storage > Server.
+- Create a datastore on both the primary and secondary Storage Servers.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json b/corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
new file mode 100644
index 0000000..171cc82
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+  "title": "API",
+  "ordinal": 84,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.html",
+  "topic_cluster": {
+    "clustering_title": "API",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+        "clustering_title": "API"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+        "clustering_title": "API"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md b/corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
new file mode 100644
index 0000000..8d4ace2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
@@ -0,0 +1,3 @@
+# API
+
+To view all groups: `curl https://api.gomorpheus.com/api/groups -H "Authorization: BEARER access_token"` To view a specific group: `curl https://api.gomorpheus.com/api/groups/:id -H "Authorization: BEARER access_token"`
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json b/corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
new file mode 100644
index 0000000..674bf37
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+  "title": "Infrastructure",
+  "ordinal": 79,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.html",
+  "topic_cluster": {
+    "clustering_title": "Infrastructure",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+        "clustering_title": "Infrastructure"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+        "clustering_title": "Infrastructure"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md b/corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
new file mode 100644
index 0000000..5786a7b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
@@ -0,0 +1,12 @@
+# Infrastructure
+
+The heart of VM Essentials is the ability to manage provisioning across any infrastructure, from bare metal to virtualized clouds and all the way to public infrastructure.
+
+**Subtopics**  
+
+- **[Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html)**
+- **[Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html)**
+- **[Network](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json b/corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
new file mode 100644
index 0000000..80f8424
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+  "title": "Example JSON Map:",
+  "ordinal": 63,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.html",
+  "topic_cluster": {
+    "clustering_title": "Example JSON Map:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+        "clustering_title": "Example JSON Map:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+        "clustering_title": "Example JSON Map:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md b/corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
new file mode 100644
index 0000000..aad0959
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
@@ -0,0 +1,28 @@
+# Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Task is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json b/corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
new file mode 100644
index 0000000..a4e65c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+  "title": "VMware Permissions",
+  "ordinal": 328,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+        "clustering_title": "VMware Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+        "clustering_title": "VMware Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md b/corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
new file mode 100644
index 0000000..c42030c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
@@ -0,0 +1,9 @@
+# VMware Permissions
+
+When integrating VMware vCenter with VM Essentials, users must supply credentials for a vCenter account and VM Essentials will only have access privileges equal to the integrated account. Many users will choose to use a vCenter administrator account so that VM Essentials can freely do any function in vCenter without worrying about hitting access limits. Others, for security reasons, may want to restrict VM Essentials only to the minimum permissions it needs to perform its functions. Follow the guide in this section to configure a user with minimal permissions and associate it with the appropriate usage levels before using it to create a VM Essentials Cloud integration.
+
+**Subtopics**  
+
+- **[Create vCenter Users and Roles](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.html)**
+- **[Privileges](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.html)**
+- **[Usage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json b/corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
new file mode 100644
index 0000000..b51f8a9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+  "title": "VMware - VM Templates Copies",
+  "ordinal": 78,
+  "parent_title": "Add Virtual Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.html",
+  "topic_cluster": {
+    "clustering_title": "VMware - VM Templates Copies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+        "clustering_title": "VMware - VM Templates Copies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+        "clustering_title": "VMware - VM Templates Copies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md b/corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
new file mode 100644
index 0000000..22dd4e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
@@ -0,0 +1,11 @@
+# VMware - VM Templates Copies
+
+In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to VM Essentials, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be synced into VM Essentials.
+
+If all the vCenters are added as Clouds into VM Essentials and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in VM Essentials. This means that as you deploy to the various vCenter Clouds in VM Essentials using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.
+
+VM Essentials supports VMware Content Libraries storing VM templates and syncing into VM Essentials, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.
+
+NOTE
+
+VM templates are a **Datacenter** level object. The same process above applies to a single VMware cloud with multiple logical datacenters. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json b/corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
new file mode 100644
index 0000000..eb91a50
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+  "title": "App Blueprint Settings",
+  "ordinal": 282,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.html",
+  "topic_cluster": {
+    "clustering_title": "App Blueprint Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+        "clustering_title": "App Blueprint Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+        "clustering_title": "App Blueprint Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md b/corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
new file mode 100644
index 0000000..bbbcfb9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
@@ -0,0 +1,10 @@
+# App Blueprint Settings
+
+Determines the Default Blueprint Type selected in new App Wizard
+
+- Morpheus
+- ARM Template
+- CloudFormation
+- Terraform
+- Kubernetes Spec
+- Helm Chart
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json b/corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
new file mode 100644
index 0000000..fa9bf98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+  "title": "Overview",
+  "ordinal": 245,
+  "parent_title": "Roles",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md b/corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
new file mode 100644
index 0000000..59d6da4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
@@ -0,0 +1,15 @@
+# Overview
+
+Within VM Essentials is a wide array of role-based access control capabilities. These roles can be managed within the Administration > Roles section of the VM Essentials UI as well as through the API or CLI. Entire sections within the appliance UI can be hidden based on the specified access levels for features within VM Essentials. Features have different access scopes that can be selected from and can range depending on the specific feature. The most common scope set involves none, read, and full.
+
+There are several handy tricks for creating new roles within VM Essentials and users can be assigned more than one role. When a user is assigned more than one role, permissions are granted by the role with the highest level of scope access. This allows roles to be built with small subsets of features and combined to grant different individuals relevant permission control. With resource permissions (that is, all types of permissions other than Feature permissions), a default access can be given as opposed to a specific (Full or None) permission for any resource. A specific permission will always supersede a default permission regardless of whether it’s more permissive or more restrictive. In other cases (default vs default OR specific vs specific) the more permissive access will be given.
+
+It’s also important to note that built-in Roles, such as the System Admin “Superuser” Role carry no special prominence. For resource permissions, the System Admin user has defaults set to Full in each section. Thus, pairing the System Admin Role with another Role that may include specific line item permissions for various resource categories may cause your System Admin users to take on a reduced permission set.
+
+NOTE
+
+Feature access control not only applies to the VM Essentials UI but also applies to the public developer API. It is sometimes necessary to logout and back in for changes to a users feature access level to be respected.
+
+**Subtopics**  
+
+- **[Role Creation](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json b/corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
new file mode 100644
index 0000000..96f4983
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+  "title": "Mountpoints",
+  "ordinal": 215,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.html",
+  "topic_cluster": {
+    "clustering_title": "Mountpoints",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+        "clustering_title": "Mountpoints"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+        "clustering_title": "Mountpoints"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md b/corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
new file mode 100644
index 0000000..8ff9c93
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
@@ -0,0 +1,27 @@
+# Mountpoints
+
+password
+:   Generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+tfvars
+:   This is a module to store a tfvars file for terraform app blueprints.
+
+secret
+:   This is the standard secret module that stores a key/value in encrypted form.
+
+uuid
+:   Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+key
+:   Generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key)
+
+vault
+:   Configures an integration between VM Essentials and a Hashicorp Vault server. See below for additional configuration instructions.
+
+    - Key lease times are entered in seconds and default to 32 days (2764800 s).
+
+      - Quick Time Reference:
+      - Day: 86400
+      - Week: 604800
+      - Month (30 days): 2592000
+      - Year: 31536000
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json b/corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
new file mode 100644
index 0000000..d16f73c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+  "title": "GFS2 Pools Overview",
+  "ordinal": 117,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.html",
+  "topic_cluster": {
+    "clustering_title": "GFS2 Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+        "clustering_title": "GFS2 Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+        "clustering_title": "GFS2 Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md b/corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
new file mode 100644
index 0000000..68c6d3f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
@@ -0,0 +1,5 @@
+# GFS2 Pools Overview
+
+GFS2 is a shared-disk cluster file system that allows multiple nodes in a cluster to access the same storage at the block level. Adding GFS2 datastores to an HVM Cluster enables live migration and live failover of running VMs.
+
+Administrators only need to present the disks to the HVM Hosts and make a few specific configurations. HPE Morpheus VM Essentials handles everything else, including mounting datastores and enabling multipathing.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json b/corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
new file mode 100644
index 0000000..f4cc6c4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+  "title": "Affinity Groups",
+  "ordinal": 323,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md b/corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
new file mode 100644
index 0000000..bfb9c2a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
@@ -0,0 +1,29 @@
+# Affinity Groups
+
+HPE Morpheus VM Essentials Software offers two-way sync for affinity groups with integrated VMware vCenter Clouds. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Affinity groups created from HPE Morpheus VM Essentials create "Should" rules (soft rules) rather than "Must" rules (hard rules) in vCenter. Thus whenever possible, servers configured to "Keep Together" will run on the same cluster host while servers configured to "Keep Separate" will be balanced across cluster hosts to the maximum extent possible. These rules may be broken if necessary to balance resources or recover from failures.
+
+TIP
+
+It is possible to create an empty affinity group (that is, one with no servers selected) in HPE Morpheus VM Essentials even though this is not possible in vCenter. If such an affinity group is created, HPE Morpheus VM Essentials will hold it without syncing to vCenter until at least one server is added and the affinity group becomes compatible with the vCenter API.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-7AD47077-8387-4499-9BDE-BBACFDDA2989-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the VMware Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **CLUSTER:** Select the vCenter cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next Cloud sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-C4C3EDB1-CA6E-4DEA-890C-B5C5B0E3DE13-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-688F89C9-1444-4D3A-94B5-E8DFE9BDC066-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json b/corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
new file mode 100644
index 0000000..155c7b5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+  "title": "Rackspace CDN Buckets",
+  "ordinal": 185,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.html",
+  "topic_cluster": {
+    "clustering_title": "Rackspace CDN Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+        "clustering_title": "Rackspace CDN Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+        "clustering_title": "Rackspace CDN Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md b/corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
new file mode 100644
index 0000000..4401479
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
@@ -0,0 +1,81 @@
+# Rackspace CDN Buckets
+
+## About this task
+
+To Add a Rackspace CDN Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Rackspace CDN from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   USERNAME
+   :   Rackspace CDN Username
+
+   API KEY
+   :   Rackspace CDN API Key
+
+   REGION
+   :   Enter Rackspace CDN Region
+
+   BUCKET NAME
+   :   Enter existing Rackspace CDN Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+**Subtopics**  
+
+- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-35419962-0058-4856-A6BD-F4923FD0F044.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json b/corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
new file mode 100644
index 0000000..8422bde
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+  "title": "Overview",
+  "ordinal": 288,
+  "parent_title": "Environments",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md b/corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
new file mode 100644
index 0000000..4ca0f68
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
@@ -0,0 +1,7 @@
+# Overview
+
+The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
+
+**Subtopics**  
+
+- **[Creating Environments](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json b/corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
new file mode 100644
index 0000000..80451d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+  "title": "Overview",
+  "ordinal": 97,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md b/corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
new file mode 100644
index 0000000..92f8ac2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
@@ -0,0 +1,3 @@
+# Overview
+
+The Infrastructure > Clusters section is where the list of existing HVM clusters can be viewed. Here you can view high-level statistics about all clusters under management by VM Essentials manager, such as aggregate resource usage by all clusters and the number of workloads running across all of them. Click into an existing HVM cluster to view additional metrics such as hosts, VMs, resource utilization by the host, and a lot more.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json b/corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
new file mode 100644
index 0000000..9ccdf8f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+  "title": "Network Interfaces",
+  "ordinal": 338,
+  "parent_title": "Creating a CentOS/RHEL 7 Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Interfaces",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+        "clustering_title": "Network Interfaces"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+        "clustering_title": "Network Interfaces"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md b/corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
new file mode 100644
index 0000000..a831b15
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
@@ -0,0 +1,44 @@
+# Network Interfaces
+
+A slightly annoying change with centOS 7 is that the network interfaces have changed naming convention. You may notice when running ifconfig that the primary network interface is set to something like ens2344 or some other random number. This naming is dynamic typically by hardware id and we don’t want this to fluctuate when provisioning the blueprint in various VMware environments. Fortunately, there is a way to turn this functionality off and restore the interface back to eth0.
+
+Firstly we need to adjust our bootloader to disable interface naming like this.
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The above command adds a few arguments to the kernel args list (namely `net.ifnames=0` and `biosdevname=0`. It may be useful to view the `/etc/default/grub` file and ensure these settings were indeed applied.
+
+The next step is to adjust the network-scripts in centOS. we need to ensure we have a file called `/etc/sysconfig/network-scripts/ifcfg-eth0`
+
+Below is a script that we run on our packer builds to prepare the machines network configuration files.
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to ensure there is a new ifcfg-eth0 config created to replace the old ens config file. Please do verify this config exists after running. If it does not you will have to be sure to build one on your own.
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json b/corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
new file mode 100644
index 0000000..b856eed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+  "title": "Settings",
+  "ordinal": 264,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.html",
+  "topic_cluster": {
+    "clustering_title": "Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+        "clustering_title": "Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+        "clustering_title": "Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md b/corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
new file mode 100644
index 0000000..121b078
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
@@ -0,0 +1,12 @@
+# Settings
+
+The Administration > Settings section sets global configuration parameters for the VM Essentials appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for VM Essentials itself.
+
+**Subtopics**  
+
+- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
+- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
+- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
+- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json b/corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
new file mode 100644
index 0000000..f1d8334
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+  "title": "Overview",
+  "ordinal": 349,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md b/corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
new file mode 100644
index 0000000..e3542c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
@@ -0,0 +1,3 @@
+# Overview
+
+The ArubaCX network plugin is implemented as a VM Essentials `GenericIntegrationProvider` in Groovy. The plugin handles network and cluster events generated by VM Essentials and modifies the configuration of ArubaCX switches based on the cable connections between the affected servers and switches. VM Essentials integrates directly with ArubaCX to create or delete networks for OVS Port Groups that are added or deleted within a configured Cluster.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json b/corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
new file mode 100644
index 0000000..bb42af7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+  "title": "Consuming Currency Exchange in VM Essentials",
+  "ordinal": 274,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.html",
+  "topic_cluster": {
+    "clustering_title": "Consuming Currency Exchange in VM Essentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+        "clustering_title": "Consuming Currency Exchange in VM Essentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+        "clustering_title": "Consuming Currency Exchange in VM Essentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md b/corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
new file mode 100644
index 0000000..3104ca0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
@@ -0,0 +1,7 @@
+# Consuming Currency Exchange in VM Essentials
+
+Currency exchange data is synced from the integrated provider once every 12 hours. When needed, Morpheus will use this cached data to present currency conversions rather than hitting the API directly each time. This limits the total number of API hits and reduces costs.
+
+Exchanged currency values will be shown under conditions similar to the following scenario:
+
+A user is working in a Subtenant configured for Currency B. The user is attempting to provision an instance with pricing sets that have only been defined in Currency A. Morpheus will convert the pricing data from currency A to Currency B for this user (and all users in this Subtenant) since price conversion has been enabled.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.json b/corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
new file mode 100644
index 0000000..1f314d1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+  "title": "Backups",
+  "ordinal": 13,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-91D3F799-4C17-4008-B605-FEE370890091.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.md b/corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
new file mode 100644
index 0000000..0290649
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
@@ -0,0 +1,3 @@
+# Backups
+
+Displays the number of successful and unsuccessful backups over the last day, week or month
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json b/corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
new file mode 100644
index 0000000..72c991b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+  "title": "Password",
+  "ordinal": 217,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.html",
+  "topic_cluster": {
+    "clustering_title": "Password",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+        "clustering_title": "Password"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+        "clustering_title": "Password"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md b/corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
new file mode 100644
index 0000000..4cbc429
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
@@ -0,0 +1,20 @@
+# Password
+
+A Cypher password generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+Key
+:   Pattern “password/character\_length/key”
+
+    Example: password/10/mypassword
+
+Value
+:   Leave the Value filed blank for a password, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the password will be generated and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generated password.
+
+To delete the password key, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json b/corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
new file mode 100644
index 0000000..d1235ca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+  "title": "Domains",
+  "ordinal": 157,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html",
+  "topic_cluster": {
+    "clustering_title": "Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md b/corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
new file mode 100644
index 0000000..2b7ea39
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
@@ -0,0 +1,13 @@
+# Domains
+
+Infrastructure  >  Network  >  Domains
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.html)**
+- **[Adding Domains](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.html)**
+- **[Editing Domain Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html)**
+- **[Editing and Removing Domains](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.html)**
+- **[Setting the default domain on a Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-97951AE9-439B-4779-823D-E118E1CB08D3.html)**
+- **[Setting the default domain on a Network](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-650706CA-915E-4239-9D69-35902E82B60E.html)**
+- **[Selecting a Domain while provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json b/corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
new file mode 100644
index 0000000..87411df
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+  "title": "Hardware Passthrough",
+  "ordinal": 132,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md b/corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
new file mode 100644
index 0000000..1e12029
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
@@ -0,0 +1,13 @@
+# Hardware Passthrough
+
+HPE Morpheus VM Essentials includes hardware passthrough and pooling support for VMs provisioned to HVM Clusters. This support extends to GPU, USB, NVME, and any other PCIe device types. In order to be usable, such devices must be attached to a HVM Host or to multiple HVM Hosts. HPE Morpheus VM Essentials includes controls to detach hardware devices from the underlying OS on the hypervisor host and add them to a pool where they are available for consumption by VMs. GPU hardware can be attached to VMs at provision time through custom Service Plans or on an ad-hoc basis by manually attaching hardware to existing VMs. Other supported hardware types must be passed through to the VM after provisioning.
+
+NOTE
+
+HVM Clusters sync certain data every few minutes (short sync) and other data once nightly (daily sync). New hardware attached to hosts is synced into HPE Morpheus VM Essentials during the nightly sync. To consume newly attached hardware immediately, you can force an additional daily sync at any time from the cluster detail page. Just expand the ACTIONS menu and click "Refresh Daily." Within a short time the additional daily sync will complete and newly attached hardware should be consumable from the UI.
+
+**Subtopics**  
+
+- **[Creating Service Plans for GPU Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html)**
+- **[Viewing and Assigning Hardware Devices](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html)**
+- **[GPU Passthrough Example](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json b/corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
new file mode 100644
index 0000000..9cf219d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+  "title": "Local Storage File Shares",
+  "ordinal": 189,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.html",
+  "topic_cluster": {
+    "clustering_title": "Local Storage File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+        "clustering_title": "Local Storage File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+        "clustering_title": "Local Storage File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md b/corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
new file mode 100644
index 0000000..023f157
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
@@ -0,0 +1,82 @@
+# Local Storage File Shares
+
+## About this task
+
+IMPORTANT
+
+Local Storage refers to local to the VM Essentials Appliance and the path must be owned by morpheus-app. Please be conscious of storage space. High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end VM Essentials Appliances.
+
+NOTE
+
+To change the owner of a file path to be used as a Local Storage File Share, run `chown morpheus-app:morpheus-app /path` on the VM Essentials Appliance.
+
+NOTE
+
+VM Essentials will validate path and ownership of the File Share Path.
+
+To Add a Local Storage File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Local Storage Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   STORAGE PATH
+   :   Enter the File Share path on the local VM Essentials Appliance.
+       :   Example: `/var/opt/morpheus/morpheus-ui/vms/virtual-images`
+
+           IMPORTANT
+
+           High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end VM Essentials Appliances.
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json b/corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
new file mode 100644
index 0000000..d3a77a9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+  "title": "Virtual Images / Blueprints",
+  "ordinal": 321,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images / Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+        "clustering_title": "Virtual Images / Blueprints"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+        "clustering_title": "Virtual Images / Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md b/corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
new file mode 100644
index 0000000..42d1439
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
@@ -0,0 +1,7 @@
+# Virtual Images / Blueprints
+
+VM Essentials will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for VM Essentials to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to VM Essentials . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints VM Essentials requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json b/corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
new file mode 100644
index 0000000..2e509a5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+  "title": "Create Data Stores",
+  "ordinal": 192,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.html",
+  "topic_cluster": {
+    "clustering_title": "Create Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+        "clustering_title": "Create Data Stores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+        "clustering_title": "Create Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md b/corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
new file mode 100644
index 0000000..45a9712
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
@@ -0,0 +1,13 @@
+# Create Data Stores
+
+To a limited extent, data stores can be created from this view. In order to create a data store, you would need to first have an integrated 3Par server. See the section on storage servers for more information on setting up this integration.
+
+NOTE
+
+For all other data store types, create the needed data store within the target Cloud and VM Essentials will automatically sync in the data store on the next Cloud sync. You can force a Cloud sync from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > RefreshMenu > Short).
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click +ADD
+- Enter a Name, select a VMware Cloud, select a 3Par Volume, and select a Host Group
+- Manage permissions in the Group Access and Tenant Permissions sections, if needed
+- Click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json b/corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
new file mode 100644
index 0000000..4673424
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+  "title": "Maintenance Mode",
+  "ordinal": 124,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.html",
+  "topic_cluster": {
+    "clustering_title": "Maintenance Mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+        "clustering_title": "Maintenance Mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+        "clustering_title": "Maintenance Mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md b/corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
new file mode 100644
index 0000000..092405b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
@@ -0,0 +1,3 @@
+# Maintenance Mode
+
+HVM hosts can be easily taken out of service for maintenance when needed. From the host detail page, click ACTIONS and then click “Enter Maintenance.” When entering maintenance mode, the host will be removed from the pool. Live VMs that can be migrated will be moved to new hosts. VMs that are powered off will also be moved when possible. When a live VM cannot be moved (such as if it’s “pinned” to the host), the host will not go into maintenance mode until that situation is cleared. You could manually move a VM to a new host or you could power it down if it’s non-essential. After taking that action, attempt to put the host into maintenance mode once again. VM Essentials UI provides a helpful dialog which shows you which VMs live on the host are to be moved as the host goes into maintenance mode. When maintenance has finished, go back to the ACTIONS menu and select “Leave Maintenance.”
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json b/corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
new file mode 100644
index 0000000..09d14f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+  "title": "Viewing Alerts ",
+  "ordinal": 373,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing Alerts ",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+        "clustering_title": "Viewing Alerts "
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+        "clustering_title": "Viewing Alerts "
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md b/corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
new file mode 100644
index 0000000..0edeb92
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
@@ -0,0 +1,13 @@
+# Viewing Alerts
+
+The Alerts tab displays system alerts with severity levels of Fatal, Critical, or Major.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server.
+3. Select the Alerts tab.
+4. Select the type of alert that you want to view from the Filter by Type drop-down list.
+5. The alerts displayed in the Alerts tab provide the following information:
+   - **Severity**: Displays the severity of the alert. The severity can be Fatal, Critical, or Major. The severity of the alert determines the health status of the system.
+   - **Type**: Displays the type of the alert message.
+   - **Message**: Displays the description of the alert message.
+   - **Time**: Displays the time when the alert was created. The UTC timezone is the standard timezone in HPE Morpheus Enterprise.![Alerts tab](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-46AEA56B-E951-48EC-8781-EEAF84D5ADB7-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json b/corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
new file mode 100644
index 0000000..c5a5949
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+  "title": "Setting the default domain on a Cloud",
+  "ordinal": 163,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-97951AE9-439B-4779-823D-E118E1CB08D3.html",
+  "topic_cluster": {
+    "clustering_title": "Setting the default domain on a Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+        "clustering_title": "Setting the default domain on a Cloud"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+        "clustering_title": "Setting the default domain on a Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md b/corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
new file mode 100644
index 0000000..8125d16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
@@ -0,0 +1,9 @@
+# Setting the default domain on a Cloud
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Clouds.
+2. Edit the target Cloud.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json b/corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
new file mode 100644
index 0000000..ff65ee8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+  "title": "Provisioning the Cluster",
+  "ordinal": 107,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9886AD4A-5C64-4E09-A106-B14419362757.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+        "clustering_title": "Provisioning the Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+        "clustering_title": "Provisioning the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md b/corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
new file mode 100644
index 0000000..ec5d7d8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
@@ -0,0 +1,21 @@
+# Provisioning the Cluster
+
+As mentioned in the previous section, HVM hosts should be running Ubuntu 24.04 to use the latest HVM cluster layout (version 1.2+). HVM hosts running Ubuntu 22.04 can also be used (select HVM cluster layout 1.1). I also have a Private Cloud-type Cloud to house the cluster. Begin the cluster creation process from the Clusters list page (Infrastructure > Clusters). Click + ADD CLUSTER and select “HVM”.
+
+VM Essentials gives the option to select a hyperconverged infrastructure (HCI) **LAYOUT** or non-HCI. In this example, the HCI Layout is used (requires a three-node minimum). Next, configure the names and IP addresses for the host boxes (**SSH HOST**). The SSH HOST name configuration is simply a display name in VM Essentials, it does not need to be a hostname. By default, configuration space is given for three hosts which is what this example cluster will have. You must at least configure one and it’s possible to add more by clicking the (+) button. The **SSH PORT** is pre-configured for port 22, change this value if applicable in your environment. Next, set a pre-existing user on the host boxes (**SSH USERNAME** and **SSH PASSWORD**) and **SSH KEY**. Use a regular user with sudo access.
+
+In the next part of the modal, you’ll configure the storage devices and network interfaces. Find your disk name, if needed, with the `lsblk` command. In my case, the target device is located at `/dev/sdb`.
+
+Though not strictly required, it’s recommended to have separate network interfaces to handle cluster management, storage traffic, and compute. In this example case, `eth0` is configured as the **MANAGEMENT NET INTERFACE** which handles communication between the cluster hosts. `eth1` is configured as the **STORAGE NET INTERFACE** and `eth2` is configured as the **COMPUTE NET INTERFACE**. The **COMPUTE VLANS** field can take a single value (ex. 1) or a range of values (ex. 22-25). This will create OVS port group(s) selectable as networks when provisioning workloads to the cluster. If needed, you can find your network interface names with the `ip a` command.
+
+Next, only one **CPU TYPE** is currently supported (`x86_64`) though this may change in the future. For **CPU MODEL** configuration, we surface the entire database of model configurations from `libvirt`. If unsure or if you don’t know of a specific reason to choose one or the other, select `host-passthrough` which is the default option.
+
+Finally, select a **DYNAMIC PLACEMENT** and **POWER POLICY** configuration. When enabled, Dynamic Placement will automatically balance VMs across cluster hosts based on resource utilization. When disabled, VMs will only migrate to a new host if they are pinned to a specific host or failed over and not running on the preferred host. With Power Policy, set Balanced (default) or Performance configuration. Balanced optimizes for a mix of performance and efficiency. Performance mode is optimized for scenarios requiring maximum performance. It reduces network latency by applying configurations similar to the `tuned` "network-latency" profile and switches CPUs into performance mode.
+
+NOTE
+
+Power Policy settings require Agent version 3.0.0+ running on the HVM Host and take effect following the next sync cycle. You can upgrade HVM Host Agents by navigating to the Host detail page, opening the ACTIONS menu, and selecting Upgrade Agent. Alternatively, you can select Download Agent Script to download a script which can be run on the HVM Host to upgrade its Agent version. Download scripts are specific to the HVM Host so you will need an individual script per HVM Host. Power Policy settings will persist following a HVM Host reboot.
+
+![image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-8FF3A6DF-6A14-4A7D-B4C1-7E6BDB83B44D-high.png)
+
+At this point we’ve kicked off the process for configuring the cluster nodes. Drill into the Cluster detail page and click on the History tab. Here we can monitor the progress of configuring the cluster. HPE Morpheus VM Essentials will run scripts to install KVM, install OVS, and to prepare the cluster. In just a short time, the cluster provisioning should complete and the cluster will be ready to deploy workloads.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json b/corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
new file mode 100644
index 0000000..0128840
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+  "title": "Supported File Share Types",
+  "ordinal": 187,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.html",
+  "topic_cluster": {
+    "clustering_title": "Supported File Share Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+        "clustering_title": "Supported File Share Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+        "clustering_title": "Supported File Share Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md b/corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
new file mode 100644
index 0000000..8d2ef9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
@@ -0,0 +1,5 @@
+# Supported File Share Types
+
+- CIFS (Samba Windows File Sharing)
+- Local Storage
+- NFSv3
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json b/corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
new file mode 100644
index 0000000..6d16fbb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+  "title": "Generate Key Pair",
+  "ordinal": 203,
+  "parent_title": "Key Pairs",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.html",
+  "topic_cluster": {
+    "clustering_title": "Generate Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+        "clustering_title": "Generate Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+        "clustering_title": "Generate Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md b/corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
new file mode 100644
index 0000000..baa6aa0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
@@ -0,0 +1,17 @@
+# Generate Key Pair
+
+## About this task
+
+To generate a Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Generate Key Pair”
+3. After naming the new key pair, HPE Morpheus VM Essentials will reveal both the public and private key
+
+## Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in HPE Morpheus VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json b/corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
new file mode 100644
index 0000000..7ab0e95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+  "title": "Windows Agent",
+  "ordinal": 37,
+  "parent_title": "SSH/Winrm",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9969BD6B-639D-4633-B825-79578464E8E6.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+        "clustering_title": "Windows Agent"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+        "clustering_title": "Windows Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md b/corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
new file mode 100644
index 0000000..79e4ab2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
@@ -0,0 +1,8 @@
+# Windows Agent
+
+- Port 5985 must be open and WinRM enabled for Windows images.
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+NOTE
+
+Administrator user is required for Windows agent install.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json b/corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
new file mode 100644
index 0000000..09138f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+  "title": "Snapshots",
+  "ordinal": 322,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.html",
+  "topic_cluster": {
+    "clustering_title": "Snapshots",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+        "clustering_title": "Snapshots"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+        "clustering_title": "Snapshots"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md b/corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
new file mode 100644
index 0000000..dbafb29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
@@ -0,0 +1,11 @@
+# Snapshots
+
+VM Essentials allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into VM Essentials every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+VM Essentials supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in VM Essentials for VMs using SR-IOV network adapters.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json b/corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
new file mode 100644
index 0000000..fc93380
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+  "title": "Enabled Clouds (Types)",
+  "ordinal": 275,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.html",
+  "topic_cluster": {
+    "clustering_title": "Enabled Clouds (Types)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+        "clustering_title": "Enabled Clouds (Types)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+        "clustering_title": "Enabled Clouds (Types)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md b/corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
new file mode 100644
index 0000000..3cc91e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
@@ -0,0 +1,5 @@
+# Enabled Clouds (Types)
+
+Controls which types of Cloud can be created.
+
+- When a Cloud type is disabled, it will be removed from the available options when adding new Clouds in Infrastructure  >  Clouds. Existing Clouds are not affected by changes to this setting.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json b/corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
new file mode 100644
index 0000000..d1547e0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+  "title": "License",
+  "ordinal": 290,
+  "parent_title": "Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html",
+  "topic_cluster": {
+    "clustering_title": "License",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md b/corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
new file mode 100644
index 0000000..c5db727
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
@@ -0,0 +1,7 @@
+# License
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.html)**
+- **[Current License](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.html)**
+- **[Upgrade License Key](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json b/corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
new file mode 100644
index 0000000..89c4d60
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+  "title": "Cloud-Init",
+  "ordinal": 337,
+  "parent_title": "Creating a CentOS/RHEL 7 Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+        "clustering_title": "Cloud-Init"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+        "clustering_title": "Cloud-Init"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md b/corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
new file mode 100644
index 0000000..68d2374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
@@ -0,0 +1,15 @@
+# Cloud-Init
+
+To get started with a base CentOS image we first install cloud-init. This is a relatively simple process using yum:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+There are two parts to this yum installation. We are first ensuring some core dependencies are installed for automation as well as cloud-init. git for example is installed for use by ansible playbook automation down the line and is therefore optional if not using ansible. The dracut-modules-growroot is responsible for resizing the root partition upon first boot to match the virtual disk size that was potentially adjusted during provisioning.
+
+A great benefit to using cloud-init is credentials don’t have to be locked into the blueprint. It is advisable, within VM Essentials , to configure the default cloud-init user that gets created when the vm boots automatically by cloud-init. This is located in Administration > Settings > Provisioning, within the Cloud-Init Settings section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json b/corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
new file mode 100644
index 0000000..504a394
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+  "title": "Adding an NFS Datastore",
+  "ordinal": 129,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an NFS Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+        "clustering_title": "Adding an NFS Datastore"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+        "clustering_title": "Adding an NFS Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md b/corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
new file mode 100644
index 0000000..351b8cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
@@ -0,0 +1,11 @@
+# Adding an NFS Datastore
+
+Existing NFS shares can be used with HVM clusters for virtual machine storage. These are added and viewed from the Storage tab of the cluster detail page and, once added and active, become selectable as targets for virtual machine storage.
+
+NOTE
+
+Ensure NFS is properly configured to allow all of the HVM hosts to access the shared directory, including permissions to read and write. For backup purposes, it’s also helpful to give VM Essentials access to NFS.
+
+Start by navigating to the Storage tab of the cluster detail page. Make sure the Data Stores subtab is also selected. Here you will see a list of existing datastores with some additional information, such as type, capacity, and status. Click ADD. Enter the NAME for the datastore in VM Essentials and select the TYPE as NFS Pool. Note that the datastore name cannot be changed once it has been created. This will update the available fields to include the additional fields needed to integrate the NFS server. Enter the SOURCE HOST which is the hostname or the IP address of the NFS server. Finally, enter the SOURCE DIRECTORY which is the directory path of the NFS share. Click SAVE.
+
+Once the modal is saved, it will take a few minutes to initialize the new datastore and show a successful online status in VM Essentials. Once this initialization process is completed, the datastore can now be used as VM storage for cluster.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json b/corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
new file mode 100644
index 0000000..e1cc66c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+  "title": "Health",
+  "ordinal": 259,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html",
+  "topic_cluster": {
+    "clustering_title": "Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md b/corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
new file mode 100644
index 0000000..a3b4596
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
@@ -0,0 +1,6 @@
+# Health
+
+**Subtopics**  
+
+- **[VM Essentials Health](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html)**
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json b/corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
new file mode 100644
index 0000000..b7dabb8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+  "title": "Networks",
+  "ordinal": 138,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html",
+  "topic_cluster": {
+    "clustering_title": "Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md b/corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
new file mode 100644
index 0000000..c25adea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
@@ -0,0 +1,8 @@
+# Networks
+
+Infrastructure  >  Network  >  Networks
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.html)**
+- **[Configuring Networks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json b/corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
new file mode 100644
index 0000000..9b4f197
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+  "title": "Create an Instance Backup",
+  "ordinal": 211,
+  "parent_title": "Backups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9DA38943-BF95-446D-AB09-32323160D51B.html",
+  "topic_cluster": {
+    "clustering_title": "Create an Instance Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+        "clustering_title": "Create an Instance Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+        "clustering_title": "Create an Instance Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md b/corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
new file mode 100644
index 0000000..9732aea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
@@ -0,0 +1,53 @@
+# Create an Instance Backup
+
+## About this task
+
+To create Instance backup:
+
+## Procedure
+
+1. Navigate to Backups > Backups
+2. Click + ADD
+3. From the Create Backup Wizard select the radio button for Instance, then click NEXT
+4. Input the following: 
+
+   Instance
+   :   Select an Instance to backup from the typeahead menu
+
+   Name
+   :   Enter a name for the backup job being created
+5. Click NEXT
+6. Depending on the Instance Type selected in the previous step, enter additional details. These can include a specific container, backup type, database name, username and password, or a number of other things depending on the Instance Type
+7. Configure the storage bucket and retention details: 
+
+   Storage
+   :   Select a configured storage bucket as the backup target
+
+   Backup Job Type
+   :   Create a new backup job, add this backup to an existing job, or clone an existing job to handle this backup
+
+   Job Name
+   :   If creating a new job, enter a name for the job
+
+   Retention Count
+   :   If creating a new job, enter the number of backups which should be simultaneously retained
+
+   Schedule
+   :   If creating a new job, select an execution schedule of which to run the backup
+
+   Synthetic Full
+   :   When the backup is targeting an HVM Instance, check this box to schedule synthetic full backups in addition to the normal full and incremental backups
+
+   Synthetic Full Schedule
+   :   If synthetic full backups are enabled, select an execution schedule on which to run the synthetic full backups
+8. Click COMPLETE.
+
+## Results
+
+NOTE
+
+On VMware Cloud types, VM Essentials will merge and consolidate the snapshots held against a VM before exporting the OVF to the storage location or share. This is so VM Essentials has a full and consistent copy of the VM state.
+
+TIP
+
+To edit an existing backup, click on the hyperlinked name of the backup job from the list of backups at Backups > Backups.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json b/corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
new file mode 100644
index 0000000..b46d063
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+  "title": "Archives",
+  "ordinal": 225,
+  "parent_title": "Tools",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html",
+  "topic_cluster": {
+    "clustering_title": "Archives",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md b/corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
new file mode 100644
index 0000000..93f331f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
@@ -0,0 +1,9 @@
+# Archives
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.html)**
+- **[Archives List Page](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.html)**
+- **[Adding an Archive](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.html)**
+- **[Archive Detail Page](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.html)**
+- **[File Detail Page](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json b/corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
new file mode 100644
index 0000000..d0fa921
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+  "title": "Editing and Removing Domains",
+  "ordinal": 162,
+  "parent_title": "Domains",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.html",
+  "topic_cluster": {
+    "clustering_title": "Editing and Removing Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+        "clustering_title": "Editing and Removing Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+        "clustering_title": "Editing and Removing Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md b/corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
new file mode 100644
index 0000000..9e62c59
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
@@ -0,0 +1,4 @@
+# Editing and Removing Domains
+
+- Domains can be edited by selecting the Actions dropdown for the Domain and selecting Edit, or by selecting the ✎ icon in list views.
+- Added Domains can be removed from VM Essentials by selecting the Actions dropdown for the Domain and selecting Remove, or the 🗑 icon in list views.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json b/corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
new file mode 100644
index 0000000..e0f827c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+  "title": "Migrations Requirements",
+  "ordinal": 233,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md b/corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
new file mode 100644
index 0000000..83e9cea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
@@ -0,0 +1,23 @@
+# Migrations Requirements
+
+This section contains requirements and recommendations that will ensure migrations run successfully. Keep an eye on this section as some requirements will change as this feature is updated over time to become more flexible.
+
+General Requirements
+:   - HVM Hosts must be upgraded to Agent version 2.10.0 at minimum. To upgrade the HVM Host Agent, navigate to the host detail page, open the ACTIONS menu, and select "Upgrade Agent." If this is unsuccessful, you may instead select "Download Agent Script" to download a shell script which may be run manually on the HVM Host. These download scripts are specific to the HVM Host so an individual install script would need to be downloaded for each HVM Host and run on the correct HVM Host.
+    - HVM Hosts must be able to reach ESXi hosts and vCenter on the target VMware vCenter Cloud via the Management Network
+    - The source VMs must be running for the preparation phase of the migration to complete successfully. If VMs are not running, they will automatically be restarted
+
+First Release Requirements
+:   This section includes requirements for the current version of the migration feature which are subject to change and improvement as road-mapped enhancements are included with subsequent versions of the product.
+
+    - If the target datastore is GFS2 or NFS, migrations will be "thin" QCOW2 rather than "thick" to reduce overhead and on-disk footprint. Other target datastore types must have enough "thick" space for each VM
+    - VMs will power down prior to the transfer meaning service of the source workload will be disrupted during the transfer
+    - VirtIO / VirtIO-SCSI target storage must be supported by the source VM
+    - Currently supported operating systems: RedHat, CentOS, Rocky, Alma, SUSE, Ubuntu, Debian, Windows (currently requires manual preparation steps described below)
+    - Source VMs must be capable of getting the `qemu-guest-tools` or `qemu-guest-agent` package installed.
+    - RDM (Raw Device Mappings) are not yet supported
+    - Source VMs must not have any attached ISOs or cdroms. These are not supported and the migration will fail.
+
+Recommendations
+:   - Batch limits and bandwidth limitations testing is still in progress. It's currently recommended you migrate no more than 20 VMs at a time. Testing is still ongoing to determine the upper limits of migrations and this recommendation is likely to increase over time
+    - Begin using this feature with a smaller migration than the limit to make sure your workloads are moving correctly
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json b/corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
new file mode 100644
index 0000000..f6caef7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+  "title": "Source Options",
+  "ordinal": 61,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.html",
+  "topic_cluster": {
+    "clustering_title": "Source Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+        "clustering_title": "Source Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+        "clustering_title": "Source Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md b/corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
new file mode 100644
index 0000000..ff7c3c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
@@ -0,0 +1,6 @@
+# Source Options
+
+Task configuration code may be entered locally or sourced via URL. Changing the SOURCE type will often update the available fields in the Task modal to accommodate the selected sourcing.
+
+- **Local:** The Task configuration code is written directly in VM Essentials in a large text area. VM Essentials includes syntax highlighting for easier debugging and script writing
+- **URL:** For Task configuration that can be source via an outside URL, specify the address in the URL field
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json b/corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
new file mode 100644
index 0000000..245d46a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+  "title": "Subnets",
+  "ordinal": 146,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9FC58214-95C7-4690-91DA-3185640E3712.html",
+  "topic_cluster": {
+    "clustering_title": "Subnets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+        "clustering_title": "Subnets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+        "clustering_title": "Subnets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md b/corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
new file mode 100644
index 0000000..7b0bd17
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
@@ -0,0 +1,7 @@
+# Subnets
+
+Subnet details can be viewed from the SUBNETS tab on the detail page of a specific network. From the SUBNETS tab, Morpheus allows the user to search and edit existing subnets.
+
+In an Azure VNet, you can also create new subnets with the +ADD button.
+
+![../../_images/create_subnet_421.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-DAD09131-AC63-418D-9EE5-811611F8FB08-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json b/corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
new file mode 100644
index 0000000..012edd7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+  "title": "DHCP",
+  "ordinal": 141,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.html",
+  "topic_cluster": {
+    "clustering_title": "DHCP",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+        "clustering_title": "DHCP"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+        "clustering_title": "DHCP"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md b/corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
new file mode 100644
index 0000000..30a45e6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
@@ -0,0 +1,26 @@
+# DHCP
+
+## About this task
+
+To configure a network for DHCP:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, set the DHCP flag as Active (default)
+5. Save Changes
+
+## Results
+
+IMPORTANT
+
+The DHCP flag tells VM Essentials this network has a DHCP server assigning IP Addresses to hosts. VM Essentials does not act as the DHCP server, and provisioning to a network that has the DHCP server flag active in VM Essentials, but no DHCP server actually on the network will, in most cases, cause the instance to not receive an IP address.
+
+NOTE
+
+When selecting a network with DHCP enabled during provisioning, “DHCP” will populate to the right of the selected network:
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json b/corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
new file mode 100644
index 0000000..54e560c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+  "title": "Defining Proxies",
+  "ordinal": 168,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.html",
+  "topic_cluster": {
+    "clustering_title": "Defining Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+        "clustering_title": "Defining Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+        "clustering_title": "Defining Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md b/corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
new file mode 100644
index 0000000..1d68520
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
@@ -0,0 +1,3 @@
+# Defining Proxies
+
+Proxies can be used in a few different contexts and optionally scoped to specific networks with which one may be provisioning into or on a cloud integration as a whole. To configure a Proxy for use by the provisioning engines within VM Essentials we must go to Infrastructure  >  Networks  >  Proxies. Here we can create records representing connection information for various proxies. This includes the host ip address, proxy port, and any credentials (if necessary) needed to utilize the proxy. Now that these proxies are defined we can use them in various contexts.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json b/corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
new file mode 100644
index 0000000..a790324
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+  "title": "Adding HPE Aruba CX DSS Network Integration",
+  "ordinal": 360,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE Aruba CX DSS Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+        "clustering_title": "Adding HPE Aruba CX DSS Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+        "clustering_title": "Adding HPE Aruba CX DSS Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md b/corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
new file mode 100644
index 0000000..ceb130e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
@@ -0,0 +1,35 @@
+# Adding HPE Aruba CX DSS Network Integration
+
+## Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Select + Add > Networking > HPEAruba CX DSS 
+
+   ![../../_images/addIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-61F5952F-CDFE-43E1-8A2B-445824B876A5-high.png)
+3. Enter the following details in the ADD NETWORK INTEGRATION form: 
+
+   NAME
+   :   Name of the integration in VM Essentials
+
+   AFC ADDRESS
+   :   Enter the network address of the AFC
+
+   AFC USERNAME
+   :   Enter the username
+
+   AFC PASSWORD
+   :   Enter the password
+
+   FABRIC NAME
+   :   Enter the fabric name from the AFC
+
+       ![../../_images/2_create_network_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5A349FA9-6B14-494D-B218-9F082BE5E18A-high.png)
+4. Click Add Network Integration
+
+## Results
+
+Upon add, the HPE Aruba CX DSS Network integration will be created.
+
+NOTE
+
+All fields can be edited after saving.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json b/corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
new file mode 100644
index 0000000..505a91b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+  "title": "Datastore Types Pros and Cons",
+  "ordinal": 112,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A1E79BA5-CE31-4357-878E-11464E03158C.html",
+  "topic_cluster": {
+    "clustering_title": "Datastore Types Pros and Cons",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+        "clustering_title": "Datastore Types Pros and Cons"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+        "clustering_title": "Datastore Types Pros and Cons"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md b/corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
new file mode 100644
index 0000000..dc0bbc6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
@@ -0,0 +1,6 @@
+# Datastore Types Pros and Cons
+
+| Datastore Type | Directory Pools | NFS Pools | GFS2 Pools |
+| --- | --- | --- | --- |
+| **Pros** | - Simple to set up and easy to configure - No external dependencies - Uses the existing host filesystem | - Simple to set up - Centralized storage enables easy VM migration across hosts | - True shared disk, clustered filesystem - Pacemaker and Corosync provide high availability and fencing (reducing the risk of split brain) - Good for live VM migration and for clustered workloads |
+| **Cons** | - No redundancy - No capability for migration - Creates the potential for filling up the host filesystem and bringing the host down | - NFS server can be a single point of failure unless configured for high availability - Requires additional configuration not needed for Directory Pools - Network latency can cause performance issues | - More complex to configure and maintain - Requires reliable shared storage (SAN, iSCSI, etc) - Troubleshooting can be more complex |
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json b/corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
new file mode 100644
index 0000000..980c65b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+  "title": "SELinux Settings",
+  "ordinal": 341,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A2A63203-21AB-4358-8706-62DF795EAE62.html",
+  "topic_cluster": {
+    "clustering_title": "SELinux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+        "clustering_title": "SELinux Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+        "clustering_title": "SELinux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md b/corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
new file mode 100644
index 0000000..9e0748e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
@@ -0,0 +1,10 @@
+# SELinux Settings
+
+## About this task
+
+If allowed by your internal IT policies, set SELinux to permissive to avoid potential issues with cloud-init down the road.
+
+## Procedure
+
+1. Edit the following: `vi /etc/selinux/config`
+2. Make the following change: `setenforce 0`
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json b/corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
new file mode 100644
index 0000000..a24f29a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+  "title": "Terraform Settings",
+  "ordinal": 283,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+        "clustering_title": "Terraform Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+        "clustering_title": "Terraform Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md b/corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
new file mode 100644
index 0000000..b8083c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
@@ -0,0 +1,3 @@
+# Terraform Settings
+
+- **Terraform Runtime:** Select “auto” or “manual”. When selecting “auto”, VM Essentials will automatically download and use the Terraform version indicated in the VERSION field on the Spec Templates that make up a Terraform Instance type or Blueprint. When selecting “manual”, VM Essentials will use the version of Terraform [installed on your appliance](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html?#terraform-installation).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json b/corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
new file mode 100644
index 0000000..61fb810
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+  "title": "Overview",
+  "ordinal": 71,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md b/corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
new file mode 100644
index 0000000..50ef90f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
@@ -0,0 +1,11 @@
+# Overview
+
+The Virtual Image section displays a list of all images, local and synced, that are available to deploy. VM Essentials includes a rich catalog of pre-configured default images for HVM clusters or for VMware vCenter Cloud targets as well. User Images are automatically synced from Cloud Integrations and added to the Virtual Images section. Images can also be uploaded directly into VM Essentials via local file or url. Understanding the process of prepping images for consumption in VM Essentials is a very important step toward building an effective VM Essentials environment.
+
+IMPORTANT
+
+Invalid Image Settings cause provisioning failures. VM Essentials syncs in as much metadata as possible for synced images, but additional configuration may be needed to ensure successful provisioning.
+
+WARNING
+
+Cloud-init is enabled by default for all Linux images. If your Linux image does not have Cloud-init installed, Cloud-init Enabled must be unchecked before provisioning the image or it will fail immediately.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json b/corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
new file mode 100644
index 0000000..fc7030d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+  "title": "Current License",
+  "ordinal": 292,
+  "parent_title": "License",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.html",
+  "topic_cluster": {
+    "clustering_title": "Current License",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+        "clustering_title": "Current License"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+        "clustering_title": "Current License"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md b/corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
new file mode 100644
index 0000000..24e8cf2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
@@ -0,0 +1,9 @@
+# Current License
+
+If a License Key has already been applied, it will be shown in the list of Current Licenses. This page also contains useful information on license usage including start and end dates for the license, the total number of HVM sockets licensed, and how many of the licensed HVM sockets have been used.
+
+NOTE
+
+Once a current License expires or has reached its limits, users will no longer be able to provision new Instances or Clusters and will not be able to convert existing VMs to managed. HPE Morpheus VM Essentials will otherwise continue to function.
+
+![The license settings page](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-DEE9EE99-95C7-48D3-9CA5-26BD14693D4D-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json b/corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
new file mode 100644
index 0000000..b0e8148
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
@@ -0,0 +1,21 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+  "title": "Host Hardware Sensor Data Collection",
+  "ordinal": 127,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html",
+  "topic_cluster": {
+    "clustering_title": "Host Hardware Sensor Data Collection",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+        "clustering_title": "Host Hardware Sensor Data Collection"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md b/corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
new file mode 100644
index 0000000..e3da4c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
@@ -0,0 +1,27 @@
+# Host Hardware Sensor Data Collection
+
+If properly configured, HVM Hosts can display detailed hardware information on the HVM Hosts detail pages. This information includes system health LED state, CPU temperature, ambient temperature, fan speeds, power supply state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-BC8DF5F3-1416-4BE4-B58F-CB1926EF7DD2-high.png)
+
+Configuration
+
+In order to surface hardware sensor data into the UI, IPMI tool and it's dependency packages must be installed on each host. Following installation, the host agent must be restarted.
+
+1. Install IPMI tool and its dependency packages (`freeipmi-common`, `ipmitool`, `libfreeipmi17`, `openipmi`)
+
+   NOTE
+
+   This tool can also be installed via apt package manager provided that the corresponding Ubuntu mirrors (main and universe module repos) are enabled. Run `sudo apt update` and then `sudo apt install ipmitool`.
+2. To confirm installation, run `sudo ipmitool -v` and the installed version should be displayed
+3. Restart the host agent with `sudo morpheus-node-ctl restart`
+4. Repeat this process on all cluster hosts
+
+Viewing Hardware Sensor Data
+
+When properly configured, hardware sensor data may be viewed from the host detail page:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM cluster
+3. Select the Health subtab
+4. The hardware sensor states and hardware events are shown in the Sensors and Events subtabs
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json b/corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
new file mode 100644
index 0000000..e67651b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+  "title": "Archives List Page",
+  "ordinal": 227,
+  "parent_title": "Archives",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.html",
+  "topic_cluster": {
+    "clustering_title": "Archives List Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+        "clustering_title": "Archives List Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+        "clustering_title": "Archives List Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md b/corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
new file mode 100644
index 0000000..84be63d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
@@ -0,0 +1,12 @@
+# Archives List Page
+
+To view or create Archives, navigate to Tools > Archives. At the Archives list page is a list of all currently-configured Archives. From the list view, the following details about each Archive are shown:
+
+- **NAME:** The name for the Archive in VM Essentials
+- **BUCKET:** The integrated bucket or file share where files in this Archive are stored
+- **# Files:** The number of files in the Archive
+- **SIZE:** The total size of all files in the Archive
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants listed here have access to the Archive
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **PUBLIC URL:** Indicates whether VM Essentials is automatically generating a public download URL for files in this Archive
+- **ACTIONS:** Within the ACTIONS menu users may download a ZIP folder containing all files in the Archive, edit the Archive, or remove it
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json b/corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
new file mode 100644
index 0000000..1ec305a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+  "title": "Windows Settings",
+  "ordinal": 279,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md b/corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
new file mode 100644
index 0000000..b496e32
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
@@ -0,0 +1,3 @@
+# Windows Settings
+
+- **Administrator Password:** Enter password to be set for the Windows Administrator User during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json b/corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
new file mode 100644
index 0000000..467bf9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+  "title": "Running Automation Against Label Targets",
+  "ordinal": 54,
+  "parent_title": "Labels",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.html",
+  "topic_cluster": {
+    "clustering_title": "Running Automation Against Label Targets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+        "clustering_title": "Running Automation Against Label Targets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+        "clustering_title": "Running Automation Against Label Targets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md b/corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
new file mode 100644
index 0000000..31e5119
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
@@ -0,0 +1,7 @@
+# Running Automation Against Label Targets
+
+Tasks can be run against Instance Labels or Server Labels. When executing the Task, select either Server Label or Instance Label. After specifying the Label, the automation will be run against all Instances or Servers which have the indicated Label. Currently, only one Label may be selected and users cannot enter multiple Labels in the field. If a non-existent Label is entered, the automation simply will not run against any Workloads since the Label does not match any.
+
+NOTE
+
+Instance and server Labels are separate. Even if some Instances or servers have the same Label, the automation is only run against the selected construct (Instance Labels or Server Labels).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.json b/corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
new file mode 100644
index 0000000..4919bbe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+  "title": "Default Storage",
+  "ordinal": 176,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A745B955-2E59-4769-AB47-E32098A84653.html",
+  "topic_cluster": {
+    "clustering_title": "Default Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+        "clustering_title": "Default Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+        "clustering_title": "Default Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.md b/corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
new file mode 100644
index 0000000..efa02f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
@@ -0,0 +1,7 @@
+# Default Storage
+
+The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is `var/opt/morpheus/morpheus-ui/`. It is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure > Storage section to avoid running out of disk space on the VM Essentials Appliance.
+
+**Subtopics**  
+
+- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json b/corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
new file mode 100644
index 0000000..327cd7d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+  "title": "To edit and configure an existing Virtual Image:",
+  "ordinal": 75,
+  "parent_title": "User Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.html",
+  "topic_cluster": {
+    "clustering_title": "To edit and configure an existing Virtual Image:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+        "clustering_title": "To edit and configure an existing Virtual Image:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+        "clustering_title": "To edit and configure an existing Virtual Image:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md b/corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
new file mode 100644
index 0000000..dde7c74
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
@@ -0,0 +1,69 @@
+# To edit and configure an existing Virtual Image:
+
+## Procedure
+
+1. Select the pencil icon at the right of any row on the Virtual Images list page, or click EDIT on a Virtual Image detail page.
+2. Configure the following on the Image: 
+
+   Name
+   :   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant VM Essentials environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, VM Essentials will install the FIPS-compliant VM Essentials Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to VMware vCenter Clouds. Enable if the Windows Image has been sysprepped. If enabled, VM Essentials will inject `unattend.xml`
+3. Click Save Changes 
+
+   NOTE
+
+   Cloud-Init is enabled by default on all images. Images without Cloud-Init or Cloudbase-Init installed must have the `cloud-init` flag disabled on the Virtual Image setting or Provisioning may fail.
+
+   IMPORTANT
+
+   VM Essentials does not validate or restrict image uploads to certain file types and any type of file may be uploaded as a Virtual Image. For security purposes, these files are stored in a non-executable state so users need not worry about potentially dangerous file types being uploaded (ex. executables).
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.json b/corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.json
new file mode 100644
index 0000000..5534247
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+  "title": "Administration",
+  "ordinal": 236,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AAD13737-533B-491F-A155-DDB027057157.html",
+  "topic_cluster": {
+    "clustering_title": "Administration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+        "clustering_title": "Administration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+        "clustering_title": "Administration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.md b/corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.md
new file mode 100644
index 0000000..e5fbfee
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AAD13737-533B-491F-A155-DDB027057157.md
@@ -0,0 +1,14 @@
+# Administration
+
+There are several administrative integrations built into VM Essentials that make it great to work with within any organization ranging from small to large. Especially, with its built in white label support and multitenancy capabilities, managed service providers have a wide range of capabilities when it comes to managing customer accounts and users.
+
+**Subtopics**  
+
+- **[Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html)**
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.html)**
+- **[Health](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html)**
+- **[Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json b/corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
new file mode 100644
index 0000000..11cc2c6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+  "title": "Host Features",
+  "ordinal": 102,
+  "parent_title": "Features",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_deployment_guide",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md b/corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
new file mode 100644
index 0000000..e6d043d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
@@ -0,0 +1,19 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and datastores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Governance through VM Essentials RBAC
+- Pass host-attached NVME, USB, and GPU hardware through to VMs running on the host
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json b/corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
new file mode 100644
index 0000000..41b6b8a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+  "title": "Routers",
+  "ordinal": 149,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html",
+  "topic_cluster": {
+    "clustering_title": "Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md b/corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
new file mode 100644
index 0000000..6fadfd1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
@@ -0,0 +1,8 @@
+# Routers
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7138E486-AE62-4778-9358-F098126785A5.html)**
+- **[Create New Router](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-61053EC5-4910-454F-8B71-6B06408A6451.html)**
+- **[Editing Existing Routers](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.html)**
+- **[Deleting Existing Routers](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json b/corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
new file mode 100644
index 0000000..ad7adc5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+  "title": "VM Features",
+  "ordinal": 103,
+  "parent_title": "Features",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_deployment_guide",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md b/corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
new file mode 100644
index 0000000..558534e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Console support for running workloads
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore VM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- VM Essentials library and automation support
+- Claim and consume host-attached NVME, USB, and GPU hardware to run hardware-accelerated workloads on VMs
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json b/corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
new file mode 100644
index 0000000..5749787
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+  "title": "Integrating With a Currency Exchange Provider",
+  "ordinal": 273,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AC461BBD-647D-447D-9307-218A41CE368B.html",
+  "topic_cluster": {
+    "clustering_title": "Integrating With a Currency Exchange Provider",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+        "clustering_title": "Integrating With a Currency Exchange Provider"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+        "clustering_title": "Integrating With a Currency Exchange Provider"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md b/corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
new file mode 100644
index 0000000..b1d8f00
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
@@ -0,0 +1,11 @@
+# Integrating With a Currency Exchange Provider
+
+## Procedure
+
+1. Navigate to Administration > Settings > Appliance
+2. Under the Currency Settings heading, make a “Currency Provider” selection
+3. Enter your “Provider API Key”
+
+## Results
+
+The service is now integrated and can be used as described in the next section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json b/corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
new file mode 100644
index 0000000..3ca1b5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+  "title": "Notes",
+  "ordinal": 50,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.html",
+  "topic_cluster": {
+    "clustering_title": "Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+        "clustering_title": "Notes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+        "clustering_title": "Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md b/corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
new file mode 100644
index 0000000..f733972
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
@@ -0,0 +1,7 @@
+# Notes
+
+Every Instance has a Wiki section for adding useful information about the Instance. Wiki can be added by selecting the Wiki tab on the bottom of the Instance Detail page. Instances with associated VMware VMs will bi-directionally sync VM Essentials Wiki content and VMware VM Notes. See the [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CD00669C-741C-480C-B444-67F079061438.html) Section for more details.
+
+TIP
+
+Markdown Syntax is supported in Wikis.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json b/corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
new file mode 100644
index 0000000..887f76a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+  "title": "Alibaba Buckets",
+  "ordinal": 179,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.html",
+  "topic_cluster": {
+    "clustering_title": "Alibaba Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+        "clustering_title": "Alibaba Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+        "clustering_title": "Alibaba Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md b/corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
new file mode 100644
index 0000000..3ee20c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
@@ -0,0 +1,77 @@
+# Alibaba Buckets
+
+## About this task
+
+To Add an Alibaba Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Alibaba from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   ACCESS KEY
+   :   Alibaba Access Key
+
+   SECRET KEY
+   :   Alibaba Secret Key
+
+   REGION
+   :   Enter Alibaba Region for the Bucket
+
+   BUCKET NAME
+   :   Enter existing Alibaba Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   Create Bucket
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json b/corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
new file mode 100644
index 0000000..ee0f194
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+  "title": "Integration Guides",
+  "ordinal": 313,
+  "parent_title": "Guides",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html",
+  "topic_cluster": {
+    "clustering_title": "Integration Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md b/corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
new file mode 100644
index 0000000..7dddadb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
@@ -0,0 +1,7 @@
+# Integration Guides
+
+**Subtopics**  
+
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA_2.html)**
+- **[Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json b/corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
new file mode 100644
index 0000000..8a225bb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+  "title": "Utilizing Existing QCOW & ISO Images from an NFS File Share",
+  "ordinal": 130,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.html",
+  "topic_cluster": {
+    "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+        "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+        "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md b/corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
new file mode 100644
index 0000000..2a28e9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
@@ -0,0 +1,38 @@
+# Utilizing Existing QCOW & ISO Images from an NFS File Share
+
+Integrated NFS shares can be used both as a repository for HVM cluster images and as a target for saving new images from existing VMs. This offers benefits of greatly expanding the available storage compared to what’s available on the VM Essentials manager VM, insulates you from issues that can arise from images completely filling the manager storage, and allows for the same images to be easily integrated with multiple VM Essentials appliances.
+
+To begin, we need the NFS file share integrated with VM Essentials. This is done in the Infrastructure > Storage section of the UI. This guide assumes the NFS file share is pre-existing and the VM Essentials manager can reach it. Actually setting up an NFS file share goes beyond the scope of this guide. From the File Shares tab, check to see the desired file share is already integrated. If needed, you can add one by clicking + ADD and then selecting “NFSv3”.
+
+When adding a new file share, configure the following:
+
+- **NAME:** A friendly name for the file share within VM Essentials
+- **HOST:** The IP address or hostname for the NFS file share server
+- **EXPORT FOLDER:** The path to the folder that should be mounted to the manager
+- **ACTIVE:** Must be checked to be able to consume this file share elsewhere in VM Essentials manager UI
+- **DEFAULT VIRTUAL IMAGE STORE:** (Optional) Select if you wish this file share to be the default store for newly uploaded or generated images
+
+When done, click Save changes.
+
+![../../_images/editFileshare.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-CD1D4AB9-1183-4739-8E61-1FB428D244B9-high.png)
+
+IMPORTANT
+
+You must configure the NFS share to give VM Essentials manager read and write access if you want to be able to read images from and write images to the file share. Configuring NFS file shares goes beyond the scope of this guide. Deleting files from an integrated file share deletes the actual file and not just the representation of the file in VM Essentials. This includes Virtual Images. Deleting a Virtual Image that is backed by a QCOW or an ISO image files stored in an integrated file share will also cause the file itself to be deleted in addition to the Virtual Image object within VM Essentials.
+
+With the file share integrated, we can now create Virtual Images which are backed by QCOW or ISO images that are pre-existing in the file share. Navigate to Library > Virtual Images and click + ADD. From the dropdown, select “QCOW2” or "ISO". Make the configurations specified below. Those not mentioned can often be left on the default value. For a deeper explanation of configurations not mentioned here, see the dedicated section of VM Essentials documentation on Virtual Images.
+
+- **NAME:** A friendly name for the image in VM Essentials
+- **OPERATING SYSTEM:** Specify the operating system of the image
+- **MINIMUM MEMORY:** Enter a minimum memory value and VM Essentials will not allow the image to be provisioned using a plan with lower memory
+- **BUCKET:** Select the NFS share integrated in the previous step
+- **CREATE IMAGE ID:** Set to “URL/PATH”
+- **URL:** Enter the path to a QCOW or an ISO image within the file share. See the next paragraph for a deeper explanation of how to enter the path properly
+
+The entered path to the QCOW or an ISO image should not include the name of the NFS share or the name of the file itself. See the portion highlighted in the screenshot:
+
+![../../_images/viewQcow.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5EB8987F-1490-43A7-84A4-875FBCE66FEB-high.png)
+
+It also should only be the path to the folder containing the QCOW or an ISO image. The file name itself should not be part of the path. For example, `templates/qcow/ubuntu/server/2204/011025`. Click Save changes.
+
+With the NFS file share integrated and the Virtual Image created, the image is now usable from the provisioning wizard. This guide won’t fully cover the use of the provisioning wizard but from the Configure tab of the wizard, the image is now selectable (assuming you’ve selected a compatible provisioning target). Additionally, we can now click into the detail page for running Instances and save them to images backed by the NFS file share. From the Instance detail page, click Actions, then “Import as Image.” You’ll be able to set a name for the new image and specify the NFS file share as the target bucket.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json b/corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
new file mode 100644
index 0000000..acdc0d3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+  "title": "Logs",
+  "ordinal": 263,
+  "parent_title": "Health",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.html",
+  "topic_cluster": {
+    "clustering_title": "Logs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+        "clustering_title": "Logs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+        "clustering_title": "Logs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md b/corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
new file mode 100644
index 0000000..419633f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
@@ -0,0 +1,3 @@
+# Logs
+
+The VM Essentials logs tab aggregates appliance-specific logs into one list. If needed, users can export the logs by clicking EXPORT. This action triggers a download containing the last 10,000 log entries as a `.log` file.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json b/corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
new file mode 100644
index 0000000..7940183
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+  "title": "Maintaining GFS2 Consistency and High Availability",
+  "ordinal": 120,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B3241978-4E00-4630-A8AB-E597193E51E2.html",
+  "topic_cluster": {
+    "clustering_title": "Maintaining GFS2 Consistency and High Availability",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+        "clustering_title": "Maintaining GFS2 Consistency and High Availability"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+        "clustering_title": "Maintaining GFS2 Consistency and High Availability"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md b/corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
new file mode 100644
index 0000000..23faa0c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
@@ -0,0 +1,38 @@
+# Maintaining GFS2 Consistency and High Availability
+
+HVM Clusters utilize several open-source technologies to maintain consistency and high availability when GFS2 external storage is utilized. This section lists those technologies and a high level overview of how they work together to prevent data corruption and facilitate smooth failover when a cluster host is lost.
+
+Corosync
+
+- Open-source cluster engine providing a high-performance messaging layer
+- Ensures node communication and consistent cluster state in high availability systems
+- Tracks active nodes and prevents split-brain scenarios
+- Provides are reliable messaging backbone for syncronizing state and data
+- Handles node failures and reconfigures the cluster automatically
+- Works with Pacemaker as part of a full HA stack providing automatic failover
+- Distributes lock information, detects failures, and triggers fencing
+
+Pacemaker
+
+- Open-source HA resource manager
+- Ensures services and resources run on correct nodes, even during failures
+- Works with Corosync for messaging and membership
+- Handles resource management, such as IP addresses, filesystems, and services
+- Depects failures and facilitates automatic failover and restart
+- Manages GFS2 mounts, distributed lock management, and fencing agents (split-brain prevention)
+- Relocates VMs and services automatically on node failure
+
+Distributed Lock Manager (DLM)
+
+- Ensures data integrity in GFS2 clusters by managing file and metadata locks
+- Allows just one node to modify a resource at a time, preventing data corruption
+- Shares lock info across the cluster
+- Utilizes Corosync messaging to synchnonize lock states
+- On node failure, fencing releases locks safety before recovery
+
+Fencing
+
+- Ensures data integrity if a node fails
+- Isolates failed nodes from shared storage to prevent data corruption
+- Uses STONITH fencing method to completely disable nodes considered to be down to ensure they cannot access shared storage
+- Releases locks only when unresponsive nodes are safely fenced
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json b/corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
new file mode 100644
index 0000000..8c7d673
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+  "title": "Users",
+  "ordinal": 251,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html",
+  "topic_cluster": {
+    "clustering_title": "Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md b/corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
new file mode 100644
index 0000000..4d63f48
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
@@ -0,0 +1,5 @@
+# Users
+
+**Subtopics**  
+
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123_2.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json b/corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
new file mode 100644
index 0000000..f978e2d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+  "title": "User Photo",
+  "ordinal": 296,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html",
+  "topic_cluster": {
+    "clustering_title": "User Photo",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md b/corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
new file mode 100644
index 0000000..36ec146
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
@@ -0,0 +1,3 @@
+# User Photo
+
+Upload a custom image for your user avatar that is displayed in the top header and user administration sections. **Suggested Photo Dimensions: 128 x 128**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json b/corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
new file mode 100644
index 0000000..af518b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+  "title": "Network Interfaces",
+  "ordinal": 342,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.html",
+  "topic_cluster": {
+    "clustering_title": "Network Interfaces",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+        "clustering_title": "Network Interfaces"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+        "clustering_title": "Network Interfaces"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md b/corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
new file mode 100644
index 0000000..de88cb2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
@@ -0,0 +1,18 @@
+# Network Interfaces
+
+## About this task
+
+Run the following to rename the network NIC. Values inside angle brackets should be filled in with the appropriate value for your environment (ex. <varname>):
+
+## Procedure
+
+1. `sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub`
+2. `grub2-mkconfig -o /boot/grub2/grub.cfg` (location may be different, could be located at /boot/efi/EFI/centos/grub.cfg)
+3. `ifdown <orginal-nic>`
+4. `mv /etc/sysconfig/network-scripts/<orginal-nic> /etc/sysconfig/network-scripts/ifcfg-eth0` (this changes name/device to eth0)
+5. Edit `ifcfg-eth0` and change the NAME to `eth0`
+6. `bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'`
+7. `ip link set <orginal-nic> down`
+8. `ip link set <orginal-nic> name eth0`
+9. `ip link set eth0 up`
+10. `ifup eth0`
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json b/corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
new file mode 100644
index 0000000..a834f8e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+  "title": "Execute Options",
+  "ordinal": 60,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+        "clustering_title": "Execute Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+        "clustering_title": "Execute Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md b/corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
new file mode 100644
index 0000000..b176cdb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
@@ -0,0 +1,7 @@
+# Execute Options
+
+- **Continue on Error:** When marked, automation stacks including this Task can continue when this Task fails. Additionally, Instances provisioned with this Task as part of its automation stack can be considered provisioned successfully even if this Task has failed
+- **Retryable:** When marked, this Task can be configured to be retried in the event of failure
+- **Retry Count:** The maximum number of times the Task will be retried when there is a failure
+- **Retry Delay:** The length of time (in seconds) VM Essentials will wait to retry the Task
+- **Allow Custom Config:** When marked, a text area is provided at Task execution time to allow the user to pass extra variables or specify extra configuration. See the next section for an example.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json b/corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
new file mode 100644
index 0000000..dda8d5b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+  "title": "Getting Started",
+  "ordinal": 2,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md b/corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
new file mode 100644
index 0000000..558527f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
@@ -0,0 +1,14 @@
+# Getting Started
+
+HPE Morpheus VM Essentials Software is a unified solution allowing for easy deployment of KVM-based HVM workloads and intuitive integration of existing VMware vCenter Clouds, all with administration made easy through the HPE Morpheus VM Essentials Manager. Once deployed, take advantage of powerful features including live migration of VMs across HVM Cluster hosts with zero downtime, dynamically distribute workloads based on load, automatic failover of workloads following the loss of a host, and a lot more. Provisioning new workloads is also made easy with the VM Essentials image library, automation tools, and powerful provisioning wizard. In addition to HVM clusters, VM Essentials also includes a deep integration into VMware vCenter, which also takes advantage of the same powerful provisioning wizard, automation engine, and monitoring capabilities.
+
+This documentation covers the system requirements for HVM clusters and a setup guide for installing VM Essentials manager. It also includes example use cases for effective implementation of the feature set and in-depth sections for each area of the UI detailing the capabilities of each tool.
+
+Before getting started, it’s important to note that administrators have the responsibility to install and configure servers and network equipment in a way that will ensure successful operation of VM Essentials. This includes selecting host servers, storage hardware, and networking hardware that have been certified as compatible with the platform. The VM Essentials section of the [HPE Support Center](https://www.hpe.com/support/VME-Docs) contains a reference architecture document which includes a validated design with specific hardware SKUs. The same section of the HPE Support Center also includes a qualification matrix which lists hardware that has been certified compatible.
+
+Additionally, administrators will be required to perform some setup functions on their own, such as preinstalling Ubuntu 24.04 (or 22.04 though you won’t be able to utilize the latest cluster layouts) on host servers, configuring networking for each host, configuring access to external storage at the OS level, and establishing a network topology that ensures acceptable performance. Subsequent sections of this document will outline some effective network designs and some tips for selecting a network design based on available hardware. It will be the responsibility of the administrator to select a network design based on available hardware and to use the Linux command line to establish appropriate network bonds, storage configuration, and access across the cluster.
+
+**Subtopics**  
+
+- **[Deployment Guide](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.html)**
+- **[Elevating to HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json b/corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
new file mode 100644
index 0000000..a8f9d3c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+  "title": "Moving Workloads Between Hosts",
+  "ordinal": 122,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.html",
+  "topic_cluster": {
+    "clustering_title": "Moving Workloads Between Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md b/corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
new file mode 100644
index 0000000..13627fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
@@ -0,0 +1,9 @@
+# Moving Workloads Between Hosts
+
+To manually move workloads between hosts, drill into the detail page for the VM (from the VMs tab of the cluster detail page). Click ACTIONS and select “Manage Placement”. Choose a different host and select from the following placement strategies:
+
+- **Auto:** Manages VM placement based on load
+- **Failover:** Moves VMs only when failover is necessary
+- **Pinned:** Will not move this workload from the selected host
+
+Within a short time, the workload is moved to the new host.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json b/corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
new file mode 100644
index 0000000..d79d7db
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+  "title": "Managing Instances",
+  "ordinal": 47,
+  "parent_title": "Instances",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+        "clustering_title": "Managing Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+        "clustering_title": "Managing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md b/corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
new file mode 100644
index 0000000..a2cde71
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
@@ -0,0 +1,23 @@
+# Managing Instances
+
+Instance actions allow you to perform numerous management tasks on instances. The actions available depend on the instance type, hypervisor, roles permissions, and instance state. Actions can be accessed from the Instances list page or from an Instance detail page.
+
+Edit
+:   Edit the Name, Description, Environment, Group, Tags, and Owner for the Instance.
+
+Delete
+:   Deletes the Instance.
+
+IMPORTANT
+
+Deleting an Instance will delete the actual underlying VMs or Containers and cannot be undone.
+
+TIP
+
+You can change the owner of an instance easily by selecting the edit button and entering a new owner in the corresponding field.
+
+**Subtopics**  
+
+- **[Actions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.html)**
+- **[Performing Instance Actions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.html)**
+- **[Notes](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json b/corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
new file mode 100644
index 0000000..281c4ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+  "title": "Features",
+  "ordinal": 101,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md b/corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
new file mode 100644
index 0000000..3fefde1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
@@ -0,0 +1,6 @@
+# Features
+
+**Subtopics**  
+
+- **[Host Features](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html)**
+- **[VM Features](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json b/corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json
new file mode 100644
index 0000000..137f929
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json
@@ -0,0 +1,21 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701",
+  "title": "Manage Security Groups and Rules in Morpheus",
+  "ordinal": 361,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.html",
+  "topic_cluster": {
+    "clustering_title": "Manage Security Groups and Rules in Morpheus",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701",
+        "clustering_title": "Manage Security Groups and Rules in Morpheus"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md b/corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md
new file mode 100644
index 0000000..bdb1bb5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md
@@ -0,0 +1,17 @@
+# Manage Security Groups and Rules in Morpheus
+
+To manage security groups and rules in Morpheus, follow these steps:
+
+1. Navigate to Infrastructure > Network > Security Groups
+2. Select + ADD
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-7883AC52-480A-4E33-AB01-6703E3A41809-high.png)
+3. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-2145D633-F35B-41FC-950C-363353E38E8B-high.png)
+4. Within the new Security Group, select + Add Rule
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-2BA30350-BAC9-420C-90A3-381E66B9AF9D-high.png)
+5. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-CA593188-8380-492C-AAA7-08766D278427-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json b/corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
new file mode 100644
index 0000000..18b677b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+  "title": "Docker",
+  "ordinal": 325,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B82658C8-6002-424B-B257-D52A7D603BC3.html",
+  "topic_cluster": {
+    "clustering_title": "Docker",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+        "clustering_title": "Docker"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+        "clustering_title": "Docker"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md b/corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
new file mode 100644
index 0000000..b506211
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
@@ -0,0 +1,7 @@
+# Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by VM Essentials out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. VM Essentials views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the VM Essentials appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json b/corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
new file mode 100644
index 0000000..873ad3e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+  "title": "Role Creation",
+  "ordinal": 246,
+  "parent_title": "Overview",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.html",
+  "topic_cluster": {
+    "clustering_title": "Role Creation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+        "clustering_title": "Role Creation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+        "clustering_title": "Role Creation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md b/corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
new file mode 100644
index 0000000..16e3722
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
@@ -0,0 +1,9 @@
+# Role Creation
+
+Roles are created within Administration > Roles. Creating a Role requires minimal information, just a Name for the Role in VM Essentials. You can optionally add a Description and a Landing URL as well. The landing URL determines the starting page for the User on initial login (such as the Instances list page or perhaps the detail page for a primary HVM cluster). Following creation, click into the Role from the Roles list page and you will see the granular controls available to Roles. These controls include access permissions for UI feature sections, Groups, Cluster types, and configured Tasks. Changes are automatically saved for the Role, there is no need to click a button to save any updates. See the next section for a detailed breakdown of individual feature permissions.
+
+Master tenant users are able to create a special type of user role called a multi-tenant user role. A multi-tenant user role is copied / duplicated down to all subtenants within VM Essentials. These can be viewed as canned role templates available to new tenants when their account is first created. Any changes made to the main role are propagated down to the subtenants version of the shared role so long as the subtenant users have not previously adjusted/changed that role. The moment a subtenant makes adjustments to the shared role within their account, it is unlinked from the parent role and treated entirely independently. In order to relink the Role in the Subtenant, a Master Tenant user would have to edit the Role, uncheck MULTITENANT USER ROLE, save the Role, check MULTITENANT USER ROLE once again, then save the Role once again.
+
+Another note about user roles is that when a user role is copied down to a subtenant, the permission scopes cannot supersede the tenant’s assigned tenant role. If they do they are automatically downgraded when propagated to the specific tenant. Any changes made to the tenant role will automatically ensure roles within the tenant are downgraded appropriately.
+
+Master Tenant administrators may edit permissions for Roles in other Tenants by viewing the Tenant detail page (Administration > Tenants > Selected Tenant) and accessing the Roles tab. From there, select the Role to edit and make changes on the resulting Role detail page.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json b/corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
new file mode 100644
index 0000000..474f43d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+  "title": "Creating a CentOS/RHEL 8 Image",
+  "ordinal": 339,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a CentOS/RHEL 8 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+        "clustering_title": "Creating a CentOS/RHEL 8 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+        "clustering_title": "Creating a CentOS/RHEL 8 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md b/corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
new file mode 100644
index 0000000..d046025
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
@@ -0,0 +1,10 @@
+# Creating a CentOS/RHEL 8 Image
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux build. You must be running ESXi 6.7 Update 2 or later.
+
+**Subtopics**  
+
+- **[Prepare The New CentOS 8/RHEL8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.html)**
+- **[SELinux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A2A63203-21AB-4358-8706-62DF795EAE62.html)**
+- **[Network Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.html)**
+- **[Final VMWare Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json b/corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
new file mode 100644
index 0000000..bacf0c1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+  "title": "VMware tools (vmtools) RPC mode",
+  "ordinal": 38,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.html",
+  "topic_cluster": {
+    "clustering_title": "VMware tools (vmtools) RPC mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+        "clustering_title": "VMware tools (vmtools) RPC mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+        "clustering_title": "VMware tools (vmtools) RPC mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md b/corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
new file mode 100644
index 0000000..d5332c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
@@ -0,0 +1,4 @@
+# VMware tools (vmtools) RPC mode
+
+- VMware tools is installed on the template(s)
+- Credentials have been entered on the Image if using an uploaded or synced image when Cloud-init or Guest Customizations or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json b/corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
new file mode 100644
index 0000000..8b30937
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+  "title": "Task Management",
+  "ordinal": 65,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html",
+  "topic_cluster": {
+    "clustering_title": "Task Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md b/corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
new file mode 100644
index 0000000..ef0cd34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
@@ -0,0 +1 @@
+# Task Management
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json b/corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
new file mode 100644
index 0000000..829cdbf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+  "title": "PXE Boot Settings",
+  "ordinal": 281,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-B94BC2CB-8504-41C6-8848-512529EEE941.html",
+  "topic_cluster": {
+    "clustering_title": "PXE Boot Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+        "clustering_title": "PXE Boot Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+        "clustering_title": "PXE Boot Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md b/corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
new file mode 100644
index 0000000..c3e2cfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
@@ -0,0 +1,4 @@
+# PXE Boot Settings
+
+Default Root Password
+:   Enter the default password to be set for Root during PXE Boots.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json b/corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
new file mode 100644
index 0000000..dc5212f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+  "title": "Common Options",
+  "ordinal": 58,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html",
+  "topic_cluster": {
+    "clustering_title": "Common Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md b/corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
new file mode 100644
index 0000000..1918c85
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
@@ -0,0 +1,3 @@
+# Common Options
+
+When creating a Task, the required and optional inputs will vary significantly by the Task type. However, there are options which are common to Tasks of all types.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json b/corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
new file mode 100644
index 0000000..77328a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+  "title": "Feature Access Permissions",
+  "ordinal": 250,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.html",
+  "topic_cluster": {
+    "clustering_title": "Feature Access Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+        "clustering_title": "Feature Access Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+        "clustering_title": "Feature Access Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md b/corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
new file mode 100644
index 0000000..8151805
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
@@ -0,0 +1,256 @@
+# Feature Access Permissions
+
+Feature Access settings control permissions for sections and objects in VM Essentials. Permission options include:
+
+None
+:   Hidden or inaccessible for user
+
+Read
+:   User can view but cannot edit or create
+
+Full
+:   User has full access
+
+User
+:   User can access Objects they have created or own
+
+Group
+:   User can access Objects assigned to or shared with Groups the User has access to
+
+Remote Console: Provisioned
+:   Remote Console tab will only appear after instance is successfully provisioned.
+
+Remote Console: Auto Login
+:   RDP and SSH only, controls if user is auto-logged in to Remote Console or presented with login prompt.
+
+Role Mappings
+:   Gives User Access to Role Mappings config in `/admin/roles` for configuring Identity Source Role Mappings without providing Access to other Identity Source configuration settings.
+
+## Admin Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Admin: Ansible | None, Full | Allows or disallows the ability to edit existing Ansible integrations | Ansible integrations are shown on the Integrations list page (Administration > Integrations). Users with access may view and edit them here. | This permission is recommended for those responsible for administering VM Essentials, including creating integrations with third‐party technologies, specifically Ansible |  |
+| Admin: Appliance Settings | None, Full | Allows or disallows access to the Appliance and License tabs in Administration > Settings | The Appliance tab in Administration > Settings is where VM Essentials administrators would configure the appliance URL, Tenant and User management, email, proxy, and currency settings. Additionally, defining which Clouds are available for integration within VM Essentials is done on this page. On the License tab information about the current VM Essentials license may be viewed and a new license may be applied when needed. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant. Those responsible for configuring currency, email, and proxy settings for Cloud API access will need this permission. | This permission is recommended to be set to None on the Tenant Role to restrict this access for all Subtenant Users. |
+| Admin: Backup Settings | None, Full | Allows or disallows access to Administration > Settings > Backups. Master Tenant administrators have additional settings for appliance backups and defaults on this page. | The Backup Settings page is where users define the default VM Essentials backup bucket, backup schedule, and retention count. Additionally, if given to a Master Tenant user they will have the ability to enable scheduled backups, create backups, and backup appliance. | This permission is recommended for those responsible for enabling backups and setting default backup buckets within VM Essentials. |  |
+| Admin: Clients | None, Full | Allows or disallows access to the Clients tab in global settings (Administration > Settings) | The Clients settings section is where API clients are created and edited. Default clients may have their validity and refresh periods edited but cannot be deleted. User‐created API clients may be edited or deleted | This permission is recommended for those responsible for administering API access. |  |
+| Admin: Distributed Workers | None, Full | Allows or disallows access to Administration > Integrations > Distributed Workers Tab |  |  |  |
+| Admin: Environment Settings | None, Full | Allows or disallows access to the Environments tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define the visibility of the environment to either private or public. When given to a Subtenant user the environments are only visible to the subtenant (private). | The Environments tab is where named environments such as development or production are created and given a description as well as a code for use within the API. A display order and visibility is also set. | This permission is recommended for those responsible for defining environments that will be available to select at provision time whether they are the Master Tenant or Subtenant users. |  |
+| Admin: Export/Import | None, Full | Allows access to the Export/Import functionality which is part of the Code Repositories section of VM Essentials UI (Provisioning > Code) | Export/Import tools allow users to configure integrated Git repositories as either export or import targets (or both) and execute exports or imports | This permission is recommended for administrators as it allows wholesale export of VM Essentials constructs (Tasks, Library Items, and more) as code into Git repositories as well as import of new items from repositories into the appliance |  |
+| Admin: Guidance Settings | None, Full | Allows or disallows access to the Guidance tab in Administration > Settings | The Guidance tab controls global thresholds for VM Essentials guidance recommendations | This permission is recommended for those responsible for cost and resource management |  |
+| Admin: Health | None, Read | Determines access to the Administration > Health page, including the VM Essentials Health and VM Essentials Logs tabs. | The Health pages provide an overview of VM Essentials health, notifications from integrations, and the current VM Essentials‐ui log. | This permission is recommended for those responsible for administering and troubleshooting VM Essentials. | This permission is recommended to be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Identity Source | None, Role Mappings, Full | Allows or disallows access to create, edit, or delete integrated Identity Sources associated with subtenants. The “Role Mappings” option allows the user to edit role mappings without seeing higher level details about the integration itself (such as server IP addresses and admin usernames). | The Identity Sources page associated with the selected Tenant allows for creating, editing, and removing of identity sources in addition to configuring role mapping between VM Essentials and the identity provider. | Full permission is recommended for those responsible for integrating VM Essentials with Identity Providers. Role Mapping permission is recommended for those responsible for Role Based Access Control (RBAC). | This permission is recommended to be set to None for any subtenant user roles via use of a Tenant Role unless they manage their own RBAC. |
+| Admin: Integrations | None, Read, Full | This allows or disallows full or read access to Administration > Integrations. | The Administration Integrations tab is where many new or existing integration types can be configured. These include Chef, Puppet, Ansible, Ansible Tower, vRealize Orchestrator, Microsoft DNS, PowerDNS, Route 53, Git, GitHub, Docker, Jenkins, ServiceNow, Cherwell, Remedy, and ACI. | This permission is recommended for those responsible for the integration between VM Essentials and integrated technologies. |  |
+| Admin: License Settings | None, Full | Allows or disallows access to the Licenses tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define specific subtenants in which the licenses may be used. | The Licenses tab is where software licenses may be added for tracking in VM Essentials. VM Essentials may then be configured to apply these licenses on provision. Currently, only Windows license types are available. | This permission is recommended for those responsible for managing Windows licenses. |  |
+| Admin: Log Settings | None, Full | Allows or disallows access to the Administration > Settings > Logs. | The Logs page is where logs are enabled. Syslog forwarding rules are also configured here. | This permission is recommended for those responsible for configuring VM Essentials log settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access to Subtenant Users. |
+| Admin: Message of the day | None, Full | Allows or disallows access to create and edit Message of the Day policies in Administration > Policies | The Policies page is where policies are defined. When creating a policy, users can select “Message of the Day” from the TYPE dropdown with this permission set to Full. | This permission is recommended for those responsible for publishing the Message of the Day. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Monitoring Settings | None, Full | Allows or disallows access to Administration > Settings > Monitoring | The monitoring settings page is where VM Essentials monitoring and monitoring integrations are configured. Monitoring checks can be turned on or off, and availability time frame, check interval period, and reported availability precision are also configured on this page. | This permission is recommended for those responsible for configuring VM Essentials monitoring settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Packages | None, Full | Allows or disallows access to the Packages tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom library packages (mpg) are added. | This permission is recommended for those responsible for managing the Library. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Plugins | None, Full | Allows or disallows access to the Plugins tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom plugins are added to extend VM Essentials functionality. | This permission is recommended for those responsible for extending VM Essentials functionality through custom plugins. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Policies | None, Read, Full | This setting determines the level of access to Administration > Policies. When given to a Master Tenant user the ability to define Global policies and associate them with one or many Subtenants is granted. When given to a Subtenant user, a global policy applies only to their subtenant. | The Policies page is where policies are defined. On create, the type of policy is selected, a name, description, and scope are defined. | This permission is recommended for those responsible for configuring and managing policies either at the Master Tenant or Subtenant. |  |
+| Admin: Profiles | none,read,full | Allows or disallows access to Profiles (Clouds) | Profiles are where Terraform, Key/Value profiles are created and managed. | This permission is recommended for those responsible for managing secrets and other metadata that needs to be accessed by provisioning and automation processes. |  |
+| Admin: Provisioning Settings | None, Full | Allows or disallows access to the Settings tab of the Administration > Settings > Provisioning page. | The Settings tab is where global provisioning settings are configured. For Master Tenant users, these include allowing Cloud selection, allowing host selection, requiring environment selection, showing pricing, hiding datastore stats on selection, cross‐Tenant naming policies, and reusing naming sequence numbers. For both Master Tenant and Subtenant users, defining the deploy archive store, cloud‐init setting, the PXE boot root password, and default App Blueprint types are available. | This permission is recommended to only be assigned to roles utilized within the Master Tenant. |  |
+| Admin: Roles | None, Read, Full | This setting determines access to the Administration > Roles page. When given to a Subtenant user, the ability to create user roles is granted. When given to a Master Tenant user, the ability to create and manage Tenant and Multi‐Tenant Users roles is also granted. | The Roles page is where roles are defined. On create, a name and description are defined. Once created, the Role is accessed and feature access, Group access, Instance Type access and Blueprint access may be configured. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC) either globally or within their Subtenant. |  |
+| Admin: Service Plans | None, Read, Full | This setting determines access to Administration > Plans & Pricing. When given to a Subtenant user, access to the Plans tab is granted. When given to a user in the Master Tenant, the Price Sets and Prices tabs are also available. | The Plans tab is where service plans are defined. On create, a name and code (for API) are defined, display order, provisioning type, storage, memory, core count and the price may be configured. Additionally, the actions menu will allow group access to be scoped. | This permission is recommended for those responsible for defining and managing pricing and applying plans. |  |
+| Admin: Tenant | None, Read, Full | This setting determines access to the Administration > Tenants page. With this permission, local users may be created or deleted within each Tenant. Critical Note: Granting this permission to Subtenant users will expose all Tenants and Tenant users to the Subtenant. | The Tenant page is where all Tenants may be viewed, edited, created, or even deleted. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant who are responsible for the creation, configuration, and/or deletion of Subtenants. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Tenant ‐ Impersonate Users | None, Full | This setting allows or disallows access to impersonate users. This selection is located on the Administration > Users page in the Actions menu. When set to Full, Impersonate selection is available. | This permission allows for users in the Master Tenant to impersonate users of the Master Tenant and Subtenants. | This permission is recommended to be assigned only to Roles utilized within the Master Tenant who are responsible for configuring RBAC or for supporting users. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Users | None, Read, Full | This setting determines access to the Administration > Users page (both Users and User Groups tabs). User Roles can also be set or edited when creating or editing a User on this page. Note: A Master Tenant user with the Admin: Tenants (Full) permission may also access and perform user management from the associated Tenant page. | The User tab is where all users may be viewed, edited, created, or even deleted. The User Groups tab is where User Groups may be viewed, edited, created, or even deleted. Within VM Essentials, a User Group may be selected during provisioning in order to add each group member’s credentials to an Instance. When creating a User Group a name, description, server group (in Linux, name of the group to assign members), sudo access toggle, and a list of users are defined. | This permission is recommended for those responsible for managing users and RBAC. |  |
+| Admin: Whitelabel Settings | None, Full | Allows or disallows access to the Whitelabel tab in Administration > Settings. | The Whitelabel tab is where custom Tenant logos, colors, and security banners may be configured. | This permission is recommended for those responsible for branding tenants, whether they are Master Tenant users or individual Subtenant users. |  |
+
+## API Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| API: Billing | None, Read, Full | Allows or disallows access to invoices and projects via VM Essentials API/CLI. | The invoices API/CLI is used to generate bills and gather highly‐granular costing data for supported Clouds. Read access allows list and get functions and Full allows access to post (refresh). | This permission is recommended for those responsible for generating invoices or projects. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| API: Execution Request | None, Full | Allows or disallows access to an API endpoint. | This endpoint allows users to execute scripts on Instances, containers, or hosts and then polls for a response. | This permission is recommended for those responsible for arbitrary API script execution. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Backups Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Backups | None, View, Read, User, Full | Determines access to the Backups secton of VM Essentials UI, including the Summary, Jobs, Backups, and History subpages. The “User” permission allows access only to backup objects the user owns. | The Summary subpage allows the user to see the number of configured backups, the success rate, recent failures, and the size of the backups, as well as, the upcoming and in‐progress backups. The Jobs subpage is where backup jobs may be created, cloned, edited or deleted. On create, a name, code (for use within the API), retention count, and schedule are selected (Note: Selectable schedules are defined Execution Schedules which are created in the Library > Automation). On the backups subpage, a list of configured backups is provided and new backups may be created or on‐demand backups may be executed. On create, the place where the target exists is selected (Instance, Host, or Provider), the source is selected and a name is defined as well as the selected execution schedule. On the History subpage both the backups and restores tabs are available. Names, statuses, start times, durations and size may be viewed. | This permission is recommended for those responsible for performing the backup and restoration of workloads. |  |
+| Backups: Integrations | None, Read, Full | Determines access to the Backups > Integrations page. | From this page, backup integrations may be created, edited, or deleted. The page also provides the status of existing integrations. On create the integration product is selected and all associated connection and authentication information must be provided. Additionally, visibility is set to either public or private. Integrations available include Avamar, Commvault, Rubrik, Veeam, and Zerto. | This permission is recommended for those responsible for the integration between VM Essentials and backup technologies. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Catalog Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Catalog (Formerly Service Catalog: Catalog) | None, Full | Determines access to Provisioning > Catalog and Catalog in the Service Catalog Persona view | The Catalog page displays the complete list of Catalog Items that can be ordered from the Service Catalog | This permission is recommended for users who will order items from the Service Catalog |  |
+| Catalog: Dashboard (Formerly Service Catalog: Dashboard) | None, Read | Determines access to and Dashboard in Service Catalog Persona view | The Catalog Dashboard contains featured Catalog Items, recently‐ordered Catalog items and Inventory items. The Catalog Dashboard is the default landing page for the Service Catalog Persona view | This permission is recommended for users who will use the Service Catalog |  |
+| Catalog: Inventory (Formerly Service Catalog: Inventory) | None, Full | Determines access to and Dashboard in Service Catalog Persona view | The Inventory is the complete list of user‐owned items provisioned from the Service Catalog | This permission is recommended for users who will use the Service Catalog and need to be able to view details on the items they’ve provisioned from the Catalog |  |
+
+## Infrastructure Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Infrastructure: Boot | None, Read, Full | Determines access to the Integrations > Bootpage, including the Mapping, Boot Menus, Answer Files, Images, and Discovered MAC Addresses tabs. | VM Essentials includes a PXE Server to provide for rapid bare metal provisioning. The Boot page is where users may add, edit, or delete answer files, as well as, manage their own images or use existing ones. Boot menus and mappings are also managed here and discovered MAC addresses are displayed. | This permission is recommend for those responsible for bare metal provisioning. |  |
+| Infrastructure: Certificates | None, Read, Full | Determines access to the SSL Certificates tab on the Infrastructure > Keys& Certs page. | The SSL Certificates page is where certificates may be uploaded and managed. These certificates may then be used within VM Essentials when orchestrating load balancers. | This permission is recommended for personnel who will be orchestrating and provisioning load balancers. |  |
+| Infrastructure: Clouds | None, Read, Group, Full | Determines access to the Infrastructure > Clouds page. The “Group” permission limits the Cloud list page (Infrastructure > Clouds) to show only Clouds in their assigned Groups. | The Cloud page is where new Clouds are integrated with VM Essentials and existing Cloud integrations are managed. This includes creating a code for use within the API, the location, visibility, tenant, whether or not it should be enabled, and if VMs should be automatically powered on. Additionally, Clouds may be integrated from the Clouds tab of a Group detail page. | This permission is recommended for those responsible for configuring RBAC as well as those responsible for VM Essentials Cloud Integrations. |  |
+| Infrastructure: Clusters | None, Read, Group, Full | Determines access to the Infrastructure > Clusters page. | The Clusters page allows you to create and manage Kubernetes, Docker, and KVM Clusters, as well as Cloud‐specific Kubernetes services such as EKS. | This permission is recommend for those creating and managing containers or container services. |  |
+| Infrastructure: Compute | None, Read, Full | Determines access to the Infrastructure > Hostspage, including the Hosts, Virtual Machines, and Bare Metal tabs. | The Hosts page provides for viewing and managing hosts, virtual machines, and bare metal hosts. On the bare metal hosts page, hosts may come from PXE boot or may be manually added. On the Hosts page hypervisors and Docker hosts are displayed. The Virtual Machines page lists all VMs. On all three pages actions may be performed against machines. Additionally, views may be refined by altering the columns displayed and CSV/JSON exporting of lists is available. | This permission is recommend for those whom need to take action on machines and those responsible for bare metal provisioning. |  |
+| Infrastructure: Credentials | None, Read, Full | Determines access to the Credentials tab in Infrastructure > Trust | The credentials tab allows you to create and manage credential sets stored internally and in external Cypher server integrations | This permission is recommended for those responsible for maintaining credentials |  |
+| Infrastructure: Groups | None, Read, Full | Determines access to the Infrastructure > Groups page. | The Groups page is where VM Essentials Groups are created and given a code for use within the API. Additionally, the DNS service, CMDB, service registry, and config management may be selected. Existing Clouds/Hosts or new Clouds/Hosts are added to the Group and virtual or bare metal machines may be viewed. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC). |  |
+| Infrastructure: Keypairs | None, Read, Full | Determines access to the Key Pairs tab on the Infrastructure > Keys& Certs page. | The Keypairs page allows for ease in accessing instances via SSH. On create a name, public key, private key, and passphrase are entered. | This permission is recommended for those whom utilize VM Essentials deployment and management of Linux Instances. |  |
+| Infrastructure: Kubernetes Control | None, Full | Determines access to the Control tab on Kubernetes Cluster detail pages (Infrastructure > Clusters > Selected Kubernetes Cluster > ControlTab) | Run `kubectl` commands, apply templates, and run workloads on the Kubernetes Cluster | This permission is recommended for Kubernetes Cluster administrators |  |
+| Infrastructure: Load Balancers | None, Read, Full | Determines access to the Infrastructure > Load Balancers page, including both the Load Balancers and Virtual Servers tabs. | The Load Balancers page is where new load balancer integrations may be configured. Additionally, existing integrations may be managed. The Virtual Servers page is where virtual servers are managed to include policies, pools, profiles, monitors, nodes, and rule scripts may be managed. | This permission is recommended for those responsible for integrating VM Essentials with load balancers as well as those responsible for managing virtual servers. |  |
+| Infrastructure: Move Servers | None, Full | Determines access to the “Change Cloud” action on server detail pages (Infrastructure > Compute > Virtual Machines tab > SelectedVM > Actions > Change Cloud) | Change Cloud allows server records to be migrated from one Cloud to another. Note that this is not a migration tool but simply allows for upkeep of records in VM Essentials. | This permission is recommended for appliance administrators. See other sections of VM Essentials documentation for more information on the use of this feature. |  |
+| Infrastructure: Networks | None, Read, Group, Full | Determines access to the Infrastructure > Networks page, including the Networks, network groups, and integrations tabs. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Networks page is where networks are configured for DHCP or static IP assignment and existing networks are displayed. The Network Groups page is where networks are grouped to allow round robin provisioning among the group. The Integrations page is where IPAM, DNS, security, service registry, and virtual network tools are integrated. These include Cisco ACI, VMware NSX T and V, Infoblox, Bluecat, phpIPAM, SolarWinds, Stealth, Microsoft DNS, PowerDNS, and Route 53. | This permission is recommended for those responsible for integration with network technologies and the configuration and management of networks to be used during provisioning. |  |
+| Infrastructure: Policies | None, Read, Full | Determines access to the Policies tabs on the Group and Cloud detail pages (Infrastructure > Groups > selected Group OR Infrastructure > Cloud > selected Cloud). | Policies can be created from this tab which are scoped to the Cloud or Group being viewed. | This permission is recommended for users who will need to set quotas which pertain specifically to Groups or Clouds the user has access to. |  |
+| Infrastructure: Security Groups | None, Read, Full | Determines access to the Security Groups tab on the Infrastructure > Networks page. | The Security Groups page is where Security Groups (aka virtual firewalls) are defined. | This permission is recommended for those responsible for firewall configuration and management. |  |
+| Infrastructure: State | None, Read, Full | Determines access to the power state toggle on the Infrastructure > Hostspage. | This toggle moves Hosts between a started and stopped state. | This permission is recommended for those responsible for managing Hosts. |  |
+| Infrastructure: Storage | None, Read, Full | Determines access to the Infrastructure > Storage page, including the Buckets, File Shares, Volumes, Data Stores, and Servers tabs. | The Servers page is where storage integrations are configured. Integrations available include 3Par, AWS S3, Dell EMC ECS and Isilon, Huawei or Open Telekom OBS and Huawei, Open Telekom, OpenStack SFS. The Volumes page is where storage volumes may be created or viewed. The File Shares page is where File Shares of types CIFS, Dell EMC ECS or Isilon, local storage, and NFSv3 may be configured. The Buckets page is where storage buckets of type AWS S3, Alibaba, Azure, Open Telekom OBS, OpenStack Swift, Racspace CDN may be created. Storage buckets are used for Backup, Archives, and Virtual Images. The Data Store page is where permissions to data stores may be managed and new data stores are added. | This permission is recommended for those responsible for storage integrations and configurations. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+| Infrastructure: Storage Browser | None, Read, Full | Determines file browsing access to buckets and file shares on the Buckets and File Shares tabs of the Infrastructure > Storage page. | The Storage Browser permission allows users who also have appropriate Infrastructure: Storage permission to browse, add files and folders, download, and delete from the buckets and file shares. | This permission is recommended for those who need to browse storage. |  |
+| Infrastructure: Trust Integrations | None, Read, Full | Determines access to the Integrations tab of the Infrastructure > Keys& Certs page. | The Integrations tab is where new trust integrations can be configured. | This permission is recommended for those responsible for the integration between VM Essentials and trust providers. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+
+## Library Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Library: App Blueprints (Formerly Provisioning: Blueprints) | None, Read, Full | Determines access to the Library > Blueprints > App Blueprints page. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of VM Essentials is available. | This permission is recommended for those responsible for defining VM Essentials‐type Blueprints. |  |
+| Library: Blueprints ‐ ARM (Formerly Provisioning: Blueprints ‐ ARM) | None, Provision, Full | Determines access to ARM‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from ARM Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of ARM is available. | This permission is recommended for those responsible for defining ARM blueprints. |  |
+| Library: Blueprints ‐ CloudFormation (Formerly Provisioning: Blueprints ‐ CloudFormation) | None, Provision, Full | Determines access to CloudFormation‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from CloudFormation Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of CloudFormation is available. | This permission is recommended for those responsible for defining CloudFormation blueprints. |  |
+| Library: Blueprints ‐ Helm (Formerly Provisioning: Blueprints ‐ Helm) | None, Provision, Full | Determines access to Helm‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Helm Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Helm is available. | This permission is recommended for those responsible for defining Helm blueprints. |  |
+| Library: Blueprints ‐ Kubernetes (Formerly Provisioning: Blueprints ‐ Kubernetes) | None, Provision, Full | Determines access to Kubernetes‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Kubernetes Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Kubernetes is available. | This permission is recommended for those responsible for defining Kubernetes blueprints. |  |
+| Library: Blueprint ‐ Terraform (Formerly Provisioning: Blueprints ‐ Terraform) | None, Provision, Full | Determines access to Terraform‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Terraform Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Terraform is available. | This permission is recommended for those responsible for defining Terraform blueprints. |  |
+| Library: Catalog Items (Formerly Tools: Self Service) | None, Read, Full | Determines access to Library > Blueprints > Catalog Items | Library > Blueprints > Catalog Items allows administrators to configure Catalog Items for the Library Catalog and Self Service Persona users | This permission is recommended for those responsible for creating and managing Library Catalog Items. |  |
+| Library: Instance Types (Formerly Provisioning: Library) | None, Read, Full | Determines access to the Library > Blueprints > Instance Types | Library > Blueprints > Instance Types is where Instance Types are created and maintained. | This permission is recommended for those responsible for managing the Instance Types. |  |
+| Library: Integrations (Formerly Provisioning: Automation Integrations) | None, Read, Full | Determines access to Library > Integrations. | Library > Integrationsis where Library Automation created and maintained.. These include Chef, Puppet, Ansible, Ansible Tower and vRealize Orchestrator. | This permission is recommended for those responsible for the integration between VM Essentials and integrated automation technologies. |  |
+| Library: Packages | None, Read, Full | Determines access to Library > Templates > Cluster Packages. | Library > Templates > Cluster Packages is where Cluster Packages are created or edited. Cluster Packages are associated with Cluster Layouts | This permission is recommended for those responsible for Cluster Layout templating |  |
+| Library: Options | None, Read, Full | Determines access to Library > Options ‐ Inputs (Option Types) and Option Lists. |  | This permission is recommended for those responsible for creating and managing Library Inputs (Option Types) and Option Lists. |  |
+| Library: Scheduling ‐ Execute (Formerly Provisioning: Scheduling ‐ Execute) | None, Read, Full | Determines access to Library > Automation > Execute Scheduling. | The Execute Scheduling is where time schedules for Jobs, including Task, Workflow, and Backup Jobs are created and managed. | This permission is recommended for those responsible to create and manage schedules to be selected when scheduling jobs. |  |
+| Library: Scheduling ‐ Power (Formerly Provisioning: Scheduling ‐ Power) | None, Read, Full | Determines access to Library > Automation > Power Scheduling. | Power Scheduling is where startup and shutdown times are created, these schedules can be applied via policy or manaully. | This permission is recommended for those responsible to create and manage power schedules. |  |
+| Library: Tasks (Formerly Provisioning: Tasks) | None, Read, Full | Determines access to Library > Automation > Tasks and Library > Automation > Workflows. | Library > Automation > Tasks is where Tasks are created and managed. Library > Automation > Workflows is where Workflows are created and managed. Workflows are used to execute one or many tasks during specified phases. | This permission is recommended for those responsible for creating provisioning and operational scripts. |  |
+| Library: Tasks ‐ Script Engines (Formerly Provisioning: Tasks ‐ Script Engines) | None, Full | Determines access to **Execute Target** of **Local** for Tasks. | This permission limits Tasks from being able to run on the Morpheus appliance(s). Additionally, Task Types that only contain the **Execute Target** of **Local** will be removed, such as: Groovy, Javascript, and Python Task Types. | This permission is recommended for those responsible for Tasks that may need to execute on the appliance(s). |  |
+| Library: Templates | None, Read, Full | Determines access to Library > Templates | Library > Templates is where Spec Templates, File Templates, Script Templates and Security Packages are created and managed. | This permission is recommended for those responsible for creating and managing Spec Templates, File Templates, Script Templates and Security Packages. |  |
+| Library: Thresholds (Formerly Provisioning: Thresholds) | None, Read, Full | Determines access to Library > Automation > Scale Thresholds. | Scale Thresholds is where preconfigured settings for auto‐scaling Instances are configured. When adding auto‐scaling to an Instance, existing Scale Thresholds can be selected to define auto‐scaling rules. | This permission is recommended for those responsible for defining auto‐scaling for Instances. | This permission is recommended to be set to None or Read on the Tenant Role to restrict access for Subtenant users. |
+| Library: Virtual Images (Formerly Provisioning: Virtual Images) | None, Read, Full | Determines access to the Library > Virtual Images page. | Library > Virtual Images is where user and system Virtual Images are managed. | This permission is recommended for those who are responsible for image management. |  |
+
+## Lifecycle Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Environment Variables | None, User, Read, Full | Allows access to the Environments tab of the Instance detail page | Allows Instance environment variables to be edited. If set to “User” level only environment variables of Instances owned by the currently logged in user may be edited. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Extend Expirations | None, User, Full | Determines if the user can extend an expiration or shutdown Policy | Allows the user to extend automated shutdown or expiration policies set against any workload (“full” permission) or against the user’s own workloads (“user” permission) | This permission is recommended for administrators or those who need to be able to extend Policies set against their own workloads (“user” level permission) |  |
+| Power Control | None, User, Full | Allows access to power state controls for Instances and servers, including stopping, starting, restarting and suspending. | Allows the user to change the current power state of Instances and servers | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure | None, User, Full | Allows general access to Instance and server reconfigure (resize) feature. See additional reconfigure permissions below for more granular control over specific reconfigure functionality. | Allows general access to reconfigure features for Instances and servers. “User” level permission allows only Instances and servers owned by the currently logged in user to be reconfigured. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Change Plan | None, User, Full | Allows the user to change the Instance service plan | When reconfiguring, the user may change the service plan associated with the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their plans changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Add | None, User, Full | Allows the user to add disks to an Instance or server during reconfigure. | When reconfiguring, the user may add disks to the selected Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Change Type | None, User, Full | Allows the user to change the datastore or volume type during reconfigure. | When reconfiguring, the user may update datastore or volume types. “User” level permission allows only Instances owned by the currently logged in user to have their disk types changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Modify | None, User, Full | Allows the user to modify an attached disk during reconfigure. | When reconfiguring, the user may modify disks attached to the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Remove | None, User, Full | Allows the user to remove disks or volumes during reconfigure. | When reconfiguring, the user may remove disks attached to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks removed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Add | None, User, Full | Allows the user to add a network adapter during reconfigure. | When reconfiguring, the user may add a network interface to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces added. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Modify | None, User, Full | Allows the user to edit network adapters during reconfigure. | When reconfiguring, the user may edit network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces modified. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Remove | None, User, Full | Allows the user to remove network adapters during reconfigure. | When reconfiguring, the user may remove network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces removed. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Retry/Cancel | None, Full | Determines access to retry and cancel buttons for Tasks (for example, in the History tab of an Instance detail page) | Retry and cancel functionality allows failed automation Tasks to be retried or stuck Tasks to be stopped from various places within VM Essentials UI (such as in the History tab of an Instance detail page) |  |  |
+
+## Monitoring Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Monitoring | None, Read, User, Full | Determines level of access to the Monitoring section of VM Essentials UI, including the Status, Apps, Checks, Groups, Incidents, Contacts, and Alert Rules subpages. The “User” permission will allow access only to objects the user owns. | The Checks page is where automatically‐created checks are customized or new checks are created. The Groups and Apps pages are where checks may be grouped. The Incidents page is where incidents are created upon Check failure. The Contacts page is where contacts may be added for notifications. The Alert Rules page is where notification are configured. | This permission is recommended for those responsible for monitoring applications, incidents, or configuring notifications. |  |
+| Monitoring: Logs (Formerly Logs) | None, Read, User, Full | Determines level of access to the Logs section of VM Essentials UI. The “User” permission will allow access only to objects the user owns. | Monitoring > Logs is where Instance and Server logs may be viewed (also must be enabled in order to view Appliance logs from Administration > Health > Morpheus Logs Logs when health permission is also enabled). | This permission is recommended for those who should have access to Instance and Server logs. | Setting permission to Full on the Tenant Role will give Subtenant users full access to all logs appliance‐wide, including to workloads living in other Tenants, for any Subtenant users who also have Full permission on their User Role. It’s recommended that you set this permission to User on the Tenant Role so that Subtenant users are not able to see logs for workloads other than their own. |
+
+## Networks Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Networks: DHCP Relays | None, Read, Full | Determines access to the DHCP Relays in applicable network integrations | Allows DHCP Relays to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: DHCP Servers | None, Read, Full | Determines access to the DHCP Servers in applicable network integrations | Allows DHCP Servers to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: Domains | None, Read, Group, Full | Determines access to the Domains tab on the Infrastructure > Network page. Domains may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into Domains scoped to Groups they can access. | The Domains page is where network domains are managed. Domains are used for setting FQDNs, joining Windows Instances to domains, and creating A‐Records with DNS integrations. On create the domain controller and credentials for domain join must be provided. | This permission is recommended for those responsible for VM Essentials DNS and domain‐join integrations. |  |
+| Networks: Firewalls | None, Read, Manage Rules, Full | Determines access to the Firewall tab on applicable network integrations detail pages. When the “Manage Rules” permission is given, users have read‐only access to firewall groups and the ability to create and manage firewall rules on those groups | The Firewall tab is where network firewall groups and rules are viewed, created and managed | This permission is recommended for those tasked with network security management |  |
+| Networks: Floating IPs | None, Read, Full | Determines access to the Floating IPs tab on the Network list page (Infrastructure > Network) | The Floating IPs tab is where Floating IPs from supported Clouds are listed once synced into VM Essentials Users may also release unattached Floating IPs from this page and link through to any workloads which have Floating IPs attached | This permission is recommended for those tasked with network management |  |
+| Networks: IP Pools | None, Read, Group, Full | Determines access to the IP Pools tab on the Network list page (Infrastructure > Network). IP Pools may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into IP Pools scoped to Groups they can access. | The IP Pools tab is where IP pools from various networks are displayed. Detail pages for IP pools can also be accessed here | This permission is recommended for those tasked with IP address management |  |
+| Networks: Integration | None, Read, Full | Determines access to the Integrations tab on the Network list page (Infrastructure > Network) | The integrations tab is where network integrations can be viewed, added and managed. Additionally, the detail pages for network integrations are accessed here | This permission is recommended for those tasked with handling network integrations and their use within VM Essentials |  |
+| Networks: Proxies | None, Read, Full | Determines access to the Proxies tab on the Infrastructure > Networks page. | The Infrastructure Networks Proxies page is where Proxy configurations are stored, which are available for use by the provisioning engines. | This permission is recommended for those responsible for configuring proxies to be used when provisioning. |  |
+| Networks: Router Firewalls | None, Read, Full | Determines access to Firewall tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Firewall tab is where firewall rules are viewed, created, and managed | This permission is recommended for those responsible for managing firewall rules |  |
+| Networks: Router Interfaces | None, Read, Full | Determines access to Interfaces tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Interface tab is where router interfaces can be viewed, created and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router NAT | None, Read, Full | Determines access to the NAT tab on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The NAT tab is where NAT rules are viewed, created, and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router Redistribution | None, Read, Full | Determines access to Route Redistribution tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Route Redistribution tab is where redistribution rules are viewed, created, and managed | This permission is recommended for those responsible for redistribution rules |  |
+| Networks: Router Routes | None, Read, Full | Determines access to Routing tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Routing tab is where routes are viewed, created, and managed | This permission is recommended for those responsible for network route management |  |
+| Networks: Routers | None, Read, Group, Full | Determines access to the Routers tab on the Infrastructure > Networks page. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Routers page is where virtual routers are created and managed from Cloud and Network integrations. | This permission is recommended for those responsible for network management. |  |
+| Networks: Server Groups | None, Read, Full | Determines access to |  |  |  |
+| Networks: Static Routes | None, Read, Full | Determines access to the routing tab on a router detail page (/infrastructure/networks/routes) | The routers tab is where routes are created and managed | This permission is recommended for those responsible for network management |  |
+
+## Operations Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Operations: Activity | None, Read | Determines access to the Activity and History tabs on the Operations > Activity page. | The Activity page displays four types of recent activities: Provisioning, Alerts, Backups, and Permissions. | This permission is recommended for those responsible to monitor or view activities and their statuses within VM Essentials. |  |
+| Operations: Alarms | None, Read, Full | Determines access to the Alarms tab in the Activity section (Operations > Health) | The Alarms tab is where alarms are listed and acknowledgement actions can be taken against them | This permission is recommended for those responsible for monitoring |  |
+| Operations: Analytics | None, Read, Full | Determines access to the Operations > Analytics page. | The Analytics page gives administrators the ability to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. | This permission is recommended for those responsible for understanding utilization and costs. |  |
+| Operations: Approvals | None, Read, Full | Determines access to the Operations > Approvals page. | When a Provision Approval‐type Policy is enabled for a Group or Cloud, an approval request will be created on each relevant provision attempt. These approvals can be handled directly in VM Essentials or dealt with in ServiceNow with a properly‐configured integration. | This permission is recommended for those responsible for approving, denying, or canceling approval requests. |  |
+| Operations: Budgets | None, Read, Full | Determines access to the Operations > Budgetspage. | The Budgets page is where budgets are created and applied to clouds, tenants, users, or groups. | This permission is recommended for those responsible for managing budgets. |  |
+| Operations: Dashboard | None, Read | Determines access to the Operations > Dashboard page (default VM Essentials landing page). | The Dashboard page is a single pane of glass showing quick, easy‐to‐read performance and configuration information about the VM Essentials environment. | “Read” permission is recommended for all users. When set to None, Operations > Reports becomes the default landing page and attempts to go to the Dashboard will redirect users to their User Settings page. |  |
+| Operations: Guidance | None, Read, Full | Determines access to the Operations > Guidance page. | The Guidance page shows recommendations for resource and cost‐utilization optimization. | This permission is recommended for those responsible to optimize utilization and costs of Cloud‐based resources. |  |
+| Operations: Invoices | None, Read, Full | Determines access to the Invoices tab in Operations > Costing | The Invoices tab allows access to highly‐granular historical costing data | This permission is recommended for those responsible for generating invoices and analyzing spend |  |
+| Operations: Reports | None, Read, Full | Determines access to the Operations > Reports page. | The Reports page is where reports may be generated and exported into JSON or CSV format. | This permission is recommended for those responsible for account, infrastructure, provisioning, usage, and cost reports. |  |
+| Operations: Usage | None, Read, Full | Determines access to the Usage tab on the Operations > Activity page. | The Usage tab shows billing information for Instances and hosts that have pricing configured on their Service Plans. | This permissions is recommended for those responsible for cost accounting. |  |
+| Operations: Wiki | None, Read, Full | Determines access to the Operations > Wiki page. | The Wiki page allows easy UI, API and CLI access to information to be referenced or shared with others. Wiki pages encompass individual Clouds, Groups, Servers, Instances, Clusters, and other pages can be manually created. Wiki pages from resources are accessible from the Operations > Wiki page or within individual resource detail pages on their respective Wiki tabs. | This permission is recommend for those responsible for documentation and knowledge management. |  |
+
+## Projects Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Projects | None, Read, Full | Determines access to Projects through VM Essentials API | Projects are used to associate resources together and apply common tags to their invoices | This permission is recommended for those responsible for cost analysis and invoice reporting |  |
+
+## Provisioning Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Provisioning: Administrator | None, Full | When editing an Instance (Provisioning > Instances > selected Instance > EDITbutton), this permission determines access to changing the owner of an Instance. | Allows you to change the owning user of an Instance. | This permission is recommended for those responsible to ensure all instances are owned by appropriate personnel. |  |
+| Provisioning: Advanced Node Type Options | None, Full | This allows or disallows access to the “Extra Options” field of the Node Types tab on the Library page when the Node Type Technology value is set to “VMware”. | When VMware technology type is selected for a new or existing Node Type (Library > Blueprints > Node Types), the “Extra Options” field will be available in the VMware VM Options section. These allow defining advanced vmx‐file parameters during provisioning. | This permission is recommended for those responsible for managing VMware Node Types (images). |  |
+| Provisioning: Apps | None, Read, User, Full | Determines access to the Provisioning > Apps page. The “User” permission will allow access to only object the user owns. | The Apps page allows Instances to be grouped and tiered logically into Apps. From this page, Apps can be deployed from existing Blueprints and Instances can be added to existing Apps. Security groups and environmental variables (Linux Only) may be added and edited. The App log, history, and monitoring tabs may be viewed. | This permission is recommended for those responsible for provisioning. |  |
+| Provisioning: Code Deployments | None, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Deployments page provides the ability to use git, fetch from a url, or upload a file to be utilized during the provisioning of an Instance or pushed to an existing Instance. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Code Integrations | None, Read, Full | Determines access to the Integrations tab on the Provisioning > Code page. | From this page code integrations may be created, edited, or deleted. Integrations available include Git, Github, and Jenkins. | This permission is recommended for those responsible for the integration between VM Essentials and code repositories and services. |  |
+| Provisioning: Code Repositories | None, List Files, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Code Repositories contains the repositories integrated with VM Essentials allowing users to browse repositories folders and files and view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Execute Script | None, Full | Determines access to the Run Script and Apply Template selections from the Actions menu on an Instance detail page | These selections bring up a menu allowing the user to select a script and run it against the viewed Instance or select a template to write to the Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Task | None, Full | Determines access to the Run Task selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Task and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Workflow | None, Full | Determines access to the Run Workflow selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Workflow and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Executions | None, Read, User | Determines access Provisioning > Executions. When the permission level is set to “User” only the executions owned by the current user are shown | Provisioning > Executions is where Task, Workflow, and Security Scan execution output can be viewed | This permission is recommended for those who are responsible for managing or troubleshooting Task, Workflow, and Security Scan executions. |  |
+| Provisioning: Import Image | None, Full | Determines access to the Import as Image and Clone to Image selections from the Actions menu on an Instance detail page | These selections allow users to create an image from an existing Instance or import the Instance as an image to a selected bucket | This permission is recommended for those responsible for managing the library of provisionable items |  |
+| Provisioning: Instances: Add | None, Full | Gives access to create Instances. Without this permission the user cannot directly add Instances. | The “+ ADD” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance create API actions as well | This permission is recommended for any user who needs to be able to provision Instances |  |
+| Provisioning: Instances: Clone | None, User, Full | Determines the presence of the “Clone” selection under the Actions menu on the Instance detail page and Instance clone API functionality | The “Clone” selection will not be available under the “Actions” menu on the Instance detail page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be cloned. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Delete | None, User, Full | Determines the presence of the “Delete” button on the Instance detail page, delete bulk action on the Instances list page, and Instance delete API functionality | The “Delete” button will not be available on the Instance detail page and the delete action will not be available from the Instances list page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be deleted. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Edit | None, User, Full | Gives access to the Edit Instances modal for existing Instances (and corresponding API functionality). This allows the user to edit an Instance display name, tags, or Input (custom option) values | The “EDIT” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance edit API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be edited. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Force Delete | None, Full | Determines access to the force delete option when deleting Instances | The force delete option (checkbox) will not be available when deleting Instances if this permission is not given. Force deleting allows VM Essentials to delete an Instance object even when it is unable to confirm the delete happened in the target cloud. Occasionally, this may be necessary but improper use can cause orphaned objects. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: List | None, User, Full | Controls which Instances are listed on the Instances list page (Provisioning > Instances). When set to “User”, only Instances owned by the currently logged in user will be displayed. |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Lock/Unlock | None, User, Full | Gives access to the lock/unlock actions on Instance detail pages (and corresponding API functionality). This allows the user to lock or unlock Instances which reduces the chances of accidental removal of important workloads. | The Lock/Unlock selections will not be visible in the Actions menu on the Instances List Page if permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be locked or unlocked. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Remove From Control | None, User, Full | Gives access to deleting an Instance in VM Essentials only. The instance remains in the target cloud. This may only be done for brownfield workloads which were converted to managed VM Essentials Instances |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Scale | None, User, Full | Gives access to the scale tab on Instance detail pages which allow configuration of automated scaling thresholds (and corresponding API functionality). This allows the user to control scaling thresholds and add/remove nodes from an Instance. | The Scale tab on the Instance detail pages will not be visible and the user will not be able to add/remove nodes from Instances if the permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be scaled. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Settings | None, User, Read, Full | Gives access to configuration changes if the Instance supports dynamic settings templates |  |  |  |
+| Provisioning: Job Executions | None, Read | Determines access to the Job Executions tab on the Provisioning > Jobs page. | The Job Executions page contains execution history of completed jobs, including any process outputs and error messages. | This permission is recommended for those who are responsible for managing or troubleshooting jobs. |  |
+| Provisioning: Jobs | None, Read, Full | Determines access to the Jobs tab on the Provisioning > Jobs page. | The Jobs page is where jobs are scheduled for the execution of automation Tasks and Workflows against Instances or servers. | This permission is recommended for those responsible to schedule the exectution of Tasks or Workflows. |  |
+| Provisioning: Remote Console | None, User, Full | Determines access to the console on a Host detail page (Infrastructure > Hosts > selected Host, VM, or Bare Metal resource > Consoletab). The “User” permission gives access to the console only for resources the logged in user owns. | Remote console access for Instances, hosts, virtual machines, and bare metal. | This permission is recommended for those who need console access for provisioned Cloud resources. |  |
+| Provisioning: Remote Console Auto Login | No, Yes | This allows or disallows the ability to automatically log into the remote console. | VM Essentials will automatically log into the machine using the credentials defined on the VM or Host. The credentials are defined either from the virtual image used, added via cloud‐init or VMware Tools using the global cloud‐init settings (Administration > Settings > Provisioning), or the Linux or Windows settings defined in User Settings. | This permission is recommended when an organization utilizes VM Essentials to create user accounts on provisioned or managed machines, as well as, allow remote console access. |  |
+| Provisioning: Service Mesh | None, Read, User, Full | Determines access to the Provisioning > ServiceMesh page, including the Services and DNS tabs. The “User” permission will allow access only to objects the user owns. | The Service Mesh page displays container services and DNS information. A service mesh ensures fast and reliable communication between containerized application services. | This permission is recommended for those responsible for container management. |  |
+| Provisioning: State | None, Read, Full | Determines access to the State tab for a Terraform Instance or App | The State tab is where [Terraform state management](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-app-state-management) is handled for Terraform Instances or Apps | This permission is recommended for those responsible for any Terraform‐based workloads |  |
+
+## Security Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Security: Scanning | None, Read, Full | Determines access to the Security Packages tab on the Jobs list page (Provisioning > Jobs), Security Scanning type Jobs, and Security Subtab inside the Software tab on a server detail page where the results of security scans are viewed | Allows access to view, create, and run security scans on existing systems, as well as view the results of previously‐run scans | This permission is recommended for those responsible for security compliance of existing systems |  |
+
+## Snapshots Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Snapshots | None, Read, Full | Determines access to the “Create Snapshot” function in the Actions menu on an Instance detail page (Provisoning > Instances > selected Instance). | If utilizing a VMware Cloud, the ability to create snapshots is available on the Instance detail page (Provisoning > Instances > selected Instance). | This permission is recommended for Instance owners who should be allowed to take snapshots. |  |
+| Snapshots: Linked Clone | None, Full | For VMware Cloud Instances, this controls access to the ability to create linked clone snapshots on the Instance detail page |  |  |  |
+
+## Tools Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Tools: Archives | None, Read, Full | Determines access to the Tools > Archives page. | Archives provides a way to store files and make them available for download by scripts and users. Archives are organized by buckets. Each bucket has a unique name that is used to identify it in URLs and Scripts. | This permission is recommended for those responsible for storage or scripts which will use the Archive. |  |
+| Tools: Cypher | None, Read, User, Full, Full Decrypt | Determines access to the Tools > Cypher page. The “User” permission will allow access only to objects the user owns. The “Full Decrypt” permission will allow for decryption of secrets. | Secure key/value store. Cypher keys can be used in scripts. | Recommended for those who need to store or use security key value pairs. |  |
+| Tools: Image Builder | None, Read, Full | Determines access to the Tools > Image Builder page, Image Builds, Boot Scripts, and Preseed Scripts tabs. | The VM Essentials Image Builder tool creates vmdk, qcow2, vhd and raw images. The Image Builder creates a blank VM in VMware, attaches an OS ISO, executes a boot script on the VM at startup via VNC, which calls a preseed script that runs the unattended OS installation and configuration. VM Essentials then executes an OVA export of the completed vmdk to the target storage provider and converts the image to all other specified formats. | Recommended for those who are responsible for image creation. |  |
+| Tools: Kubernetes | None, Read, User, Full | Allows for the management of Kubernetes clusters via the API (may be deprecated in the near future). | Allows for the management of Kubernetes clusters via the API | This permission is recommended for those who need to manage Kubernetes clusters via the API. | It is recommended this permission is set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Virtual Desktop Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Virtual Desktop: Copy/Paste | None, Full | Allows copy and paste access from the virtual desktop terminal | Enables the user to copy and paste values from a virtual desktop session into the paste buffer of their local computer |  |  |
+| Virtual Desktop: Local Printer | None, Full | Enables printing from a virtual desktop session to a locally installed printer |  |  |  |
+| Tools: VDI Pools | None, Read, Full | Allows for the management of virtual desktop (VDI) pools. | Enables the user to access the VDI Pools section (Tools > VDI Pools) and view existing pools (with “read” permission) or create and edit pools (with “full” permission). Related API functions are also granted with this feature permission. | This permission is recommended for those needing to manage VDI pools |  |
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json b/corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
new file mode 100644
index 0000000..83b9546
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+  "title": "Networking Integrations",
+  "ordinal": 347,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html",
+  "topic_cluster": {
+    "clustering_title": "Networking Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md b/corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
new file mode 100644
index 0000000..e211684
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
@@ -0,0 +1,6 @@
+# Networking Integrations
+
+**Subtopics**  
+
+- **[ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html)**
+- **[HPE Aruba CX DSS](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json b/corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
new file mode 100644
index 0000000..f2b6ee3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+  "title": "Dashboard",
+  "ordinal": 6,
+  "parent_title": "Operations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.html",
+  "topic_cluster": {
+    "clustering_title": "Dashboard",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+        "clustering_title": "Dashboard"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+        "clustering_title": "Dashboard"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md b/corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
new file mode 100644
index 0000000..7e4bd14
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
@@ -0,0 +1,17 @@
+# Dashboard
+
+The Dashboard is a single, high-level view into your environment which includes easy-to-read performance and configuration information. In many cases other areas within VM Essentials UI will allow you to drill deeper into the information presented in the dashboard.
+
+![dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-EED20D75-2987-4570-A0F2-5AD920F49D1D-high.png)
+
+**Subtopics**  
+
+- **[Environment](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.html)**
+- **[System Status](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.html)**
+- **[Favorites](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.html)**
+- **[Alarms (dashboard)](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.html)**
+- **[Instance Status](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.html)**
+- **[Instances By Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-91D3F799-4C17-4008-B605-FEE370890091.html)**
+- **[Task Executions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json b/corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
new file mode 100644
index 0000000..b8d72f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+  "title": "Using Cypher Keys in Scripts",
+  "ordinal": 224,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.html",
+  "topic_cluster": {
+    "clustering_title": "Using Cypher Keys in Scripts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+        "clustering_title": "Using Cypher Keys in Scripts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+        "clustering_title": "Using Cypher Keys in Scripts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md b/corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
new file mode 100644
index 0000000..3cb9e8b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
@@ -0,0 +1,15 @@
+# Using Cypher Keys in Scripts
+
+To use a Cypher key in a script, use the following syntax:
+
+`<%=cypher.read('var_name')%>`
+
+Example: `PASSWORD=<%=cypher.read('secret/myuserpassword')%>`
+
+Cypher also includes an option to read a value from the `password/*` mountpoint or create one if it doesn’t already exist. Use the following syntax:
+
+`<%=cypher.readPassword('var_name')%>`
+
+Example: `` PASSWORD=<%=cypher.readPassword('myuserpassword')%>` ``
+
+It should be noted that when Cypher keys are created using the `readPassword` function, the subsequent reads can only come from the same user. If another VM Essentials user attempts to run the automation script containing the `readPassword` call, the secret value will not be read and it’s very likely the script will fail. For Tasks that need to be run by multiple users, use a pre-existing Cypher key and reference it back in the script using `read` rather than `readPassword`.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json b/corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
new file mode 100644
index 0000000..19efed5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+  "title": "Hypervisor Console Keyboards",
+  "ordinal": 136,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html",
+  "topic_cluster": {
+    "clustering_title": "Hypervisor Console Keyboards",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md b/corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
new file mode 100644
index 0000000..d1367ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
@@ -0,0 +1,52 @@
+# Hypervisor Console Keyboards
+
+HVM VMs support guest console access as well as hypervisor console access. For each HVM VM, users can set a keyboard layout configuration which will then be set for use on each session.
+
+IMPORTANT
+
+This feature requires HVM Host agent version 3.0.3 or greater. Upgrade the host agent from the host detail page for **each** host by expanding the ACTIONS menu and clicking "Upgrade Agent." Alternatively, select "Download Agent Script" to download a script to run against the host manually from a terminal session. These scripts are specific to each host so you must download a script for each host and run the correct script against the correct host.
+
+Currently, the following layouts are supported:
+
+- Dutch (Belgium)
+- French (Belgium)
+- German
+- Italian
+- English (United Kingdom)
+- English (United States)
+- French
+- Spanish
+- German (Switzerland)
+- Finnish
+- French (Switzerland)
+- Icelandic
+- Norwegian
+- Portuguese
+- Danish
+
+Setting the Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click EDIT
+6. Expand the Advanced Options section
+7. In the KEYBOARD LAYOUT field, select the desired keyboard localization
+8. Click SAVE CHANGES
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-6EC36C91-5E13-4B5B-AB20-10DE225F85B3-high.png)
+
+Using the Configured Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click on the Console tab
+6. Click on the dropdown labeled GUEST and change the selection to Hypervisor
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-B75612CA-1867-4066-937C-B66FA952D251-high.png)
+7. Click on the keyboard icon and see the keyboard layout has changed to the selected layout
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-EC09C556-7F46-4036-ABDF-7E36BE8BFD8D-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json b/corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
new file mode 100644
index 0000000..cf9598f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+  "title": "Affinity Groups",
+  "ordinal": 125,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md b/corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
new file mode 100644
index 0000000..19d236e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
@@ -0,0 +1,28 @@
+# Affinity Groups
+
+HVM Clusters offer affinity groups and anti-affinity groups. These work similarly to affinity groups on other platforms, such as the affinity rules concept in VMware vSphere. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Whenever possible, servers configured to "Keep Together" will run on the same HVM Host. Servers configured to "Keep Separate" will be balanced across HVM Hosts to the maximum extent possible.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-C5C8E073-11BC-4D5A-A900-14571F77280D-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next cluster sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+TIP
+
+Placement settings (ex. pinning a VM to a specific host) can override an affinity group. HVM Clusters will attempt to implement affinity groups intelligently to work around VM placement. For example, in a group of five VMs configured to "keep together" with one pinned to host 1, the Cluster would run all five VMs on host 1 (if possible) to simultaneously honor the placement and the affinity group. In some scenarios, it will not be possible to simultaneously honor all placements and affinities/anti-affinities.
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-9C039E15-FE97-4CFD-987E-07A16E644534-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-12E8B43B-9A47-46D9-8A99-3EBDF1FAD577-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json b/corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
new file mode 100644
index 0000000..56c181f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+  "title": "VMware vCenter",
+  "ordinal": 314,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html",
+  "topic_cluster": {
+    "clustering_title": "VMware vCenter",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md b/corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
new file mode 100644
index 0000000..384239b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
@@ -0,0 +1,25 @@
+# VMware vCenter
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.html)**
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.html)**
+- **[Windows Provisioning Tips](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.html)**
+- **[Existing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.html)**
+- **[Service Plans](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-30353E6D-5FA2-470C-BB80-238663945F6F.html)**
+- **[Virtual Images / Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.html)**
+- **[Snapshots](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.html)**
+- **[Tagging and Metadata](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.html)**
+- **[Docker](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B82658C8-6002-424B-B257-D52A7D603BC3.html)**
+- **[Multitenancy](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.html)**
+- **[Advanced](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1EB800EB-6832-487E-BB11-07D8520003CF.html)**
+- **[VMware Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.html)**
+- **[Creating a VM Essentials VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.html)**
+- **[Creating a Windows Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.html)**
+- **[Creating a CentOS/RHEL 7 Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.html)**
+- **[Creating a CentOS/RHEL 8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.html)**
+- **[Creating an Ubuntu 20.04 Image](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.html)**
+- **[Gotchas](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.html)**
+- **[A Note on Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json b/corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
new file mode 100644
index 0000000..b822442
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+  "title": "Delete Group",
+  "ordinal": 88,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Group",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+        "clustering_title": "Delete Group"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+        "clustering_title": "Delete Group"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md b/corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
new file mode 100644
index 0000000..39958a6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
@@ -0,0 +1,13 @@
+# Delete Group
+
+## About this task
+
+To delete a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to delete.
+4. Click the Delete button.
+5. Confirm
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json b/corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
new file mode 100644
index 0000000..5815cb0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+  "title": "Automation",
+  "ordinal": 55,
+  "parent_title": "Library",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.html",
+  "topic_cluster": {
+    "clustering_title": "Automation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+        "clustering_title": "Automation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+        "clustering_title": "Automation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md b/corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
new file mode 100644
index 0000000..c81ab40
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
@@ -0,0 +1,10 @@
+# Automation
+
+Library  >  Automation
+
+The automation section is where scripts, known as Tasks, can be created. Tasks are individual Bash or Powershell scripts which can be selected to run against Instances at the time they are provisioned from the Instance provisioning wizard. In this section, users can also create execution schedules which are configured time intervals on which automated jobs (such as backups) would be carried out.
+
+**Subtopics**  
+
+- **[Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html)**
+- **[Execute Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json b/corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
new file mode 100644
index 0000000..c125322
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+  "title": "Google Cloud Storage Buckets",
+  "ordinal": 182,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.html",
+  "topic_cluster": {
+    "clustering_title": "Google Cloud Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+        "clustering_title": "Google Cloud Storage Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+        "clustering_title": "Google Cloud Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md b/corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
new file mode 100644
index 0000000..c485aa7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
@@ -0,0 +1,53 @@
+# Google Cloud Storage Buckets
+
+## About this task
+
+NOTE
+
+Google Cloud Storage Buckets are associated with an existing GCP Cloud integration. Ensure the GCP Cloud integration is pre-existing before attempting to create a new Google Cloud Storage Bucket. On the initial integration and subsequent cloud syncs, Google Cloud Storage Buckets are automatically onboarded and updated.
+
+To add a Google Cloud Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Select the Storage link in the sub-navigation bar
+3. In the BUCKETS tab, Click the + ADD button
+4. Select Google Cloud Storage from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   A friendly name for the bucket in VM Essentials
+
+   STORAGE SERVICE
+   :   Select the GCP cloud integration this bucket should be created in
+
+   PROJECT ID
+   :   Select the Project to create the group under, Projects are a GCP-specific concept and are logical grouping for your resources. Select any existing project associated with your selected GCP cloud integration
+
+   BUCKET NAME
+   :   The name for the bucket resource on the GCP side
+
+   LOCATION TYPE
+   :   Select Region, Dual-Region, or Multi-Region. Buckets with a Region location type will be stored in one GCP region, such as “us-east1 (South Carolina)”. Dual-Region and Multi-Region data is stored in two (or more, in the case of multi-region) GCP regions separated by a significant physical distance. Dual-Region and Multi-Region data is geo-redundant across the multiple selected regions
+
+   LOCATION
+   :   A selected GCP region (or regions, in the case of dual and multi-location data) where the data will be stored
+
+   STORAGE CLASS
+   :   Select Standard, Nearline, Coldline, or Archive. The appropriate storage class will depend on how frequently the bucket data is accessed and how long the type of data in the bucket is expected to be stored. More information on storage classes can be found in [GCP Documentation](https://cloud.google.com/storage/docs/storage-classes#descriptions)
+
+   ACTIVE
+   :   When marked, the bucket is available for use in VM Essentials
+
+   DEFAULT BACKUP TARGET
+   :   Sets the bucket as the default storage option when creating backups at provision time or in the Backups section of VM Essentials
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this Bucket as the default storage target when uploading deployment files in the Deployments section
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this bucket as the default storage target when uploading virtual images from the Virtual Images section, importing images from Instance actions, creating images with the Image Builder, and when creating new images from Migrations
+
+   RETENTION POLICY
+   :   Select None and the files in this bucket will never be deleted or backed up by VM Essentials. When selecting ‘Backup Old Files’, VM Essentials will backup files into another selected bucket once they reach a certain number of days old. When selecting ‘Delete Old Files’, VM Essentials will delete any files that reach a certain number of days old
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json b/corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
new file mode 100644
index 0000000..4004026
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+  "title": "Creating a Windows Image",
+  "ordinal": 333,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Windows Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+        "clustering_title": "Creating a Windows Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+        "clustering_title": "Creating a Windows Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md b/corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
new file mode 100644
index 0000000..cd62b45
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
@@ -0,0 +1,6 @@
+# Creating a Windows Image
+
+**Subtopics**  
+
+- **[Supported Versions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.html)**
+- **[Image Preparation](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json b/corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
new file mode 100644
index 0000000..51cb23b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+  "title": "Activity",
+  "ordinal": 21,
+  "parent_title": "Activity",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md b/corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
new file mode 100644
index 0000000..12a6c25
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
@@ -0,0 +1,12 @@
+# Activity
+
+There are three types of activities that are displayed in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
+
+**Subtopics**  
+
+- **[To View a Recent Activity report:](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.html)**
+- **[Review](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json b/corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
new file mode 100644
index 0000000..6ab4862
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+  "title": "Creating Instances",
+  "ordinal": 45,
+  "parent_title": "Instances",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+        "clustering_title": "Creating Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+        "clustering_title": "Creating Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md b/corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
new file mode 100644
index 0000000..ee29be4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
@@ -0,0 +1,25 @@
+# Creating Instances
+
+The Instance catalog is where you will create new workloads targeting the HVM clusters and/or VMware vCenter Clouds available to the VM Essentials environment. The list contains only Instance Types relevant to the provisioning engines which enabled and integrated in the current appliance.
+
+To get started, simply click the + Add button in the upper right of the Provisioning > Instances page. A modal will display allowing the catalog to be searched. Once an item is selected, it is just a matter of following the steps through the wizard.
+
+TIP
+
+The Instance catalog can be customized via role-based access control (RBAC) to restrict provision types only to certain Roles. It is completely customizable.
+
+The next step will ask for a Group and Cloud to be selected. The Group is an abstract representation that can contain multiple HVM clusters or VMware vCenter integrations. Clouds can be in multiple Groups and Groups are also useful for using RBAC to restrict provisioning access and set retainment policies. The wizard continues by allowing us to choose a name for the Instance as well as an environment.
+
+NOTE
+
+Currently the Environment option is most useful for presenting the user with informative metadata around the Instance when coming back to it later.
+
+Moving on, it is now time to configure the Instance. Depending on the Instance Configuration that is chosen, fields will change. This can include cloud-specific fields (i.e. target hosts for HVM clusters or datastores for VMware Clouds). There will also be options like setting an initial user account. Some of these fields are optional and will be represented as such in the wizard.
+
+One last step before the Instance can be provisioned is the Automation step. It is here that you can select Tasks which will run during the provision process and these Tasks must complete successfully in order for the Instance status to be reported as successful. Tasks are either Bash or Powershell scripts which can be configured in the Library > Automationsection.
+
+Now that the steps are completed for provisioning the selected Instance type, simply review your selections and complete. The Instance will automatically show up in the Instances list and its provisioning state will be represented. Depending on what was provisioned this step can range from seconds to minutes.
+
+**Subtopics**  
+
+- **[Converting Discovered Resources to Managed Instances](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json b/corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
new file mode 100644
index 0000000..f104c17
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+  "title": "Adding ArubaCX Integration",
+  "ordinal": 354,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.html",
+  "topic_cluster": {
+    "clustering_title": "Adding ArubaCX Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+        "clustering_title": "Adding ArubaCX Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+        "clustering_title": "Adding ArubaCX Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md b/corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
new file mode 100644
index 0000000..fefa00e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
@@ -0,0 +1,73 @@
+# Adding ArubaCX Integration
+
+## About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.
+
+## Procedure
+
+1. Navigate to Administration > Integrations
+2. Select + New Integration > Other > ArubaCX 
+
+   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
+3. Enter the following: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   ENABLED
+   :   Deselect to disable the integration
+
+   USERNAME
+   :   User username for all switches
+
+   PASSWORD
+   :   User password for all switches
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 4
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 4
+
+   UPLINK LAG INTERFACE
+   :   Name of the uplink LAG interface (default is 'lag1')
+4. Select SAVE CHANGES
+
+## Results
+
+Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:
+
+![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)
+
+NOTE
+
+All fields can be edited after saving.
+
+Sample Reference Architecture for EVPN Configuration
+
+1. Minimum four leaf switches, two spine switches, and one core switch
+2. At least two servers in separate racks
+3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
+4. VMs on servers in different racks communicate through the EVPN switch configuration
+5. Route traffic between racks through spine switches
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json b/corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
new file mode 100644
index 0000000..49b7789
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+  "title": "Trust",
+  "ordinal": 196,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md b/corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
new file mode 100644
index 0000000..cf9ca3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
@@ -0,0 +1,9 @@
+# Trust
+
+The Trust section is where credentials and SSH keypairs are stored. Stored credentials are useful for easy integration with VMware Clouds or other third party technologies using stored credential sets. In the keypairs section, generate SSH keypairs which can be associated with your user account so that your public key is automatically added to the authorized keys file on provisioned workloads for easy access.
+
+**Subtopics**  
+
+- **[Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.html)**
+- **[OAuth 2.0 Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.html)**
+- **[Key Pairs](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json b/corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
new file mode 100644
index 0000000..1cd202d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+  "title": "Requirements",
+  "ordinal": 98,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md b/corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
new file mode 100644
index 0000000..c38ea78
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
@@ -0,0 +1,4 @@
+# Requirements
+
+- VM Essentials Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters
+- VM Essentials Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json b/corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
new file mode 100644
index 0000000..0b071ea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+  "title": "To View a Recent Activity report:",
+  "ordinal": 22,
+  "parent_title": "Activity",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.html",
+  "topic_cluster": {
+    "clustering_title": "To View a Recent Activity report:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+        "clustering_title": "To View a Recent Activity report:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+        "clustering_title": "To View a Recent Activity report:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md b/corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
new file mode 100644
index 0000000..31fea08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
@@ -0,0 +1,10 @@
+# To View a Recent Activity report:
+
+## Procedure
+
+1. Select the `Operations` link in the navigation bar.
+2. Select `Activity` in the sub navigation bar.
+
+## Results
+
+Recent activity is displayed in order from recent to oldest. This view can be searched and filtered by type, user, and date range.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json b/corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
new file mode 100644
index 0000000..8a3433a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+  "title": "Adding and Removing Labels",
+  "ordinal": 53,
+  "parent_title": "Labels",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.html",
+  "topic_cluster": {
+    "clustering_title": "Adding and Removing Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+        "clustering_title": "Adding and Removing Labels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+        "clustering_title": "Adding and Removing Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md b/corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
new file mode 100644
index 0000000..19d518c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
@@ -0,0 +1,5 @@
+# Adding and Removing Labels
+
+Labels can be created when adding or edited any of the supported constructs listed above. When adding or editing the object, enter or edit the comma-separated list of labels you wish to apply.
+
+![../_images/labeladd.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-B0C645F7-A738-4975-9AA9-9F5E0C581874-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json b/corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
new file mode 100644
index 0000000..cebf954
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+  "title": "Creating an Ubuntu 20.04 Image",
+  "ordinal": 344,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an Ubuntu 20.04 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+        "clustering_title": "Creating an Ubuntu 20.04 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+        "clustering_title": "Creating an Ubuntu 20.04 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md b/corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
new file mode 100644
index 0000000..c360e34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
@@ -0,0 +1,97 @@
+# Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Change the network interface to `eth0` by editing `/etc/default/grub`. The line `GRUB_CMDLINE_LINUX=""` should be edited to `GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"`.
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to VM Essentials to onboard the image and use it to begin building your provisioning library.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.json b/corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
new file mode 100644
index 0000000..16c6917
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+  "title": "HVM clusters",
+  "ordinal": 100,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CA806876-1093-4A39-BE62-439C4802A915.html",
+  "topic_cluster": {
+    "clustering_title": "HVM clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+        "clustering_title": "HVM clusters"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+        "clustering_title": "HVM clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.md b/corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
new file mode 100644
index 0000000..b9f0547
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
@@ -0,0 +1,17 @@
+# HVM clusters
+
+An HVM cluster is a hypervisor clustering technology utilizing KVM. Beginning with just a few basic Ubuntu boxes, VM Essentials can create a cluster of HVM hypervisor hosts complete with monitoring, failover, easy migration of workloads across the cluster, and zero-downtime maintenance access to hypervisor host nodes. All of this is backed by a highly-granular RBAC engine, and image library with automation stacks.
+
+**Subtopics**  
+
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html)**
+- **[Base Cluster Details](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.html)**
+- **[Provisioning the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9886AD4A-5C64-4E09-A106-B14419362757.html)**
+- **[Provisioning a Workload](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.html)**
+- **[HVM Cluster Networking](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html)**
+- **[HVM Cluster Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html)**
+- **[Utilizing Existing QCOW & ISO Images from an NFS File Share](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.html)**
+- **[Image Prep (Windows)](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html)**
+- **[Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html)**
+- **[Hypervisor Console Keyboards](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json b/corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
new file mode 100644
index 0000000..7b15f2b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+  "title": "Overview",
+  "ordinal": 172,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md b/corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
new file mode 100644
index 0000000..f012482
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
@@ -0,0 +1,3 @@
+# Overview
+
+The Network Integrations section allows you to add and manage IPAM, DNS, and Service Registry integrations.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json b/corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
new file mode 100644
index 0000000..3fe382a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+  "title": "Operations",
+  "ordinal": 5,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html",
+  "topic_cluster": {
+    "clustering_title": "Operations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md b/corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
new file mode 100644
index 0000000..68faf3f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
@@ -0,0 +1,7 @@
+# Operations
+
+**Subtopics**  
+
+- **[Dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.html)**
+- **[Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CD00669C-741C-480C-B444-67F079061438.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.json b/corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.json
new file mode 100644
index 0000000..182b7cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+  "title": "Wiki",
+  "ordinal": 16,
+  "parent_title": "Operations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CD00669C-741C-480C-B444-67F079061438.html",
+  "topic_cluster": {
+    "clustering_title": "Wiki",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+        "clustering_title": "Wiki"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+        "clustering_title": "Wiki"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.md b/corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.md
new file mode 100644
index 0000000..a4c27d1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD00669C-741C-480C-B444-67F079061438.md
@@ -0,0 +1,11 @@
+# Wiki
+
+The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, and Clusters. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations > Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
+
+![wiki](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-F0F0DA3A-4058-45D6-AECA-8A5BEF62FDBA-high.png)
+
+**Subtopics**  
+
+- **[Highlights](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.html)**
+- **[Creating Wikis](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.html)**
+- **[Hosting Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json b/corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
new file mode 100644
index 0000000..b2cea00
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+  "title": "Final VMWare Tasks",
+  "ordinal": 343,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.html",
+  "topic_cluster": {
+    "clustering_title": "Final VMWare Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+        "clustering_title": "Final VMWare Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+        "clustering_title": "Final VMWare Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md b/corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
new file mode 100644
index 0000000..e205cf3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
@@ -0,0 +1,8 @@
+# Final VMWare Tasks
+
+## Procedure
+
+1. Detach any install media
+2. Shutdown the VM
+3. Convert the VM to template on the VM Essentials side
+4. Refresh the VM Essentials Cloud to allow the new template to sync
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json b/corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
new file mode 100644
index 0000000..8f0ff9d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+  "title": "CIFS File Shares",
+  "ordinal": 188,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.html",
+  "topic_cluster": {
+    "clustering_title": "CIFS File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+        "clustering_title": "CIFS File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+        "clustering_title": "CIFS File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md b/corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
new file mode 100644
index 0000000..4860113
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
@@ -0,0 +1,76 @@
+# CIFS File Shares
+
+## About this task
+
+To Add a CIFS File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select CIFS (Samba Windows File Sharing) from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   HOST
+   :   Enter host IP or resolvable hostname
+       :   Example: `192.168.200.210`
+
+   USERNAME
+   :   CIFS Share Username
+
+   PASSWORD
+   :   CIFS Share User Password
+
+   SHARE PATH
+   :   Enter CIFS Share Path
+       :   Example: `cifs`
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json b/corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
new file mode 100644
index 0000000..6d65413
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+  "title": "Creating Environments",
+  "ordinal": 289,
+  "parent_title": "Overview",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+        "clustering_title": "Creating Environments"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+        "clustering_title": "Creating Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md b/corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
new file mode 100644
index 0000000..1df2e04
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
@@ -0,0 +1,24 @@
+# Creating Environments
+
+## Procedure
+
+1. Select + Create Environment
+2. Populate the following for the New Environment: 
+
+   Name
+   :   The friendly name for the environment in VM Essentials
+
+   Code
+   :   Shortcode used for API and CLI
+
+   Description
+   :   Environment description displayed on the Environments list page
+
+   Display Order
+   :   The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
+
+## Results
+
+NOTE
+
+User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. VM Essentials-default environments can only be hidden from users during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json b/corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
new file mode 100644
index 0000000..2113f28
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+  "title": "Example Cluster Deployment",
+  "ordinal": 106,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.html",
+  "topic_cluster": {
+    "clustering_title": "Example Cluster Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+        "clustering_title": "Example Cluster Deployment"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+        "clustering_title": "Example Cluster Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md b/corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
new file mode 100644
index 0000000..0d8747e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
@@ -0,0 +1,15 @@
+# Example Cluster Deployment
+
+In this example cluster, each host box consists of:
+
+- 4 vCPU
+- 16 GB memory
+- 20 GB OS boot disk
+- 250 GB data disk (deployed to `/dev/sdb`)
+- 3 network interfaces for management, storage, and compute traffic (set to `eth0`, `eth1`, and `eth2`, respectively, in this example. Your environment may differ.)
+
+NOTE
+
+250 GB data disks used in this example are simply for demonstration purposes. A typical test cluster should consist of at least 500 GB storage and more will be required for production. Do not raid disks on physical servers. Multiple disks may be specified per host by giving a comma-separated list (ex. /dev/sda,/dev/sdb,/dev/sdc,etc.) in the DATA DEVICE field during cluster setup. These along with disks from all other nodes will be added to the total storage, which is presented as one large volume.
+
+HVM clusters must also live in Private Cloud-type Clouds (See Infrastructure > Clouds). A pre-existing Cloud may be used or a new Cloud could be created to house HVM clusters.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json b/corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
new file mode 100644
index 0000000..69b7da2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+  "title": "Directory Pools Overview",
+  "ordinal": 113,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.html",
+  "topic_cluster": {
+    "clustering_title": "Directory Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+        "clustering_title": "Directory Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+        "clustering_title": "Directory Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md b/corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
new file mode 100644
index 0000000..58e01a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
@@ -0,0 +1,11 @@
+# Directory Pools Overview
+
+Directory Pools allow designation of a directory on the local host filesystem as a datastore. By default on creation of the HVM cluster, three Directory Pools are automatically created which helps ensure HVM can work straight out of the box even without other integrated storage. The default Directory Pools are:
+
+- `local` at `/var/morpheus/kvm/local` for storage of virtual disks for VMs
+- `morpheus-cloud-init` at `/var/morpheus/kvm/cloud-init` for storage of ephemeral clout-init ISOs
+- `morpheus-images` at `/var/morpheus/kvm/images` for storage of virtual images
+
+TIP
+
+Of these default Directory Pools, only the `local` pool is selectable as a provisioning target for storing virtual disks. Using this Directory Pool runs the risk of filling up the HVM Host filesystem and bringing down the host. For this reason, it may be advisable to edit this datastore and make it inactive. Use an alternative datastore, such as an NFS Pool or GFS Pool (discussed in the upcoming sections) to avoid filling up the local filesystem. The other two default Directory Pools can remain active as they are created for specific purposes and will not be selectable for users as a datastore at provision time.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json b/corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
new file mode 100644
index 0000000..5099af6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+  "title": "Tasks",
+  "ordinal": 56,
+  "parent_title": "Automation",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html",
+  "topic_cluster": {
+    "clustering_title": "Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md b/corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
new file mode 100644
index 0000000..70f3e8e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
@@ -0,0 +1,12 @@
+# Tasks
+
+**Subtopics**  
+
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.html)**
+- **[Target Options](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.html)**
+- **[Execute Options](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.html)**
+- **[Source Options](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.html)**
+- **[Allow Custom Config](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.html)**
+- **[Adding Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6B80D87B-8461-414D-9172-07E68896EB06.html)**
+- **[Editing Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.html)**
+- **[Deleting Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json b/corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
new file mode 100644
index 0000000..6d12725
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+  "title": "To add a VM Essentials Network Pool",
+  "ordinal": 156,
+  "parent_title": "IP Pools",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.html",
+  "topic_cluster": {
+    "clustering_title": "To add a VM Essentials Network Pool",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+        "clustering_title": "To add a VM Essentials Network Pool"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+        "clustering_title": "To add a VM Essentials Network Pool"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md b/corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
new file mode 100644
index 0000000..3e4e7b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
@@ -0,0 +1,26 @@
+# To add a VM Essentials Network Pool
+
+## Procedure
+
+1. Click + ADD in Infrastructure  >  Network  >  IP Pools
+2. Enter the following:
+   :   Name
+       :   A friendly name for the IP Pool in VM Essentials.
+
+       Pool Type
+       :   Currently, HVM-type IP Pools and NSX IP Pools (with a configured integration) can be created directly from VM Essentials
+
+       Starting Address
+       :   The starting IP address of the IP Pool address range. ex: 192.168.0.2
+
+       Ending Address:
+       :   The ending IP address of the IP Pool address range. ex: 192.168.0.255
+3. Save Changes
+
+## Results
+
+NOTE
+
+Multiple Address Ranges can be added to a pool by selecting the + icon next to the address range.
+
+After saving the IP pool will be available for assignment to networks in the NETWORK POOL dropdown when adding or editing a network.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json b/corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
new file mode 100644
index 0000000..08456ac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+  "title": "Adding NFS Pools",
+  "ordinal": 116,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.html",
+  "topic_cluster": {
+    "clustering_title": "Adding NFS Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+        "clustering_title": "Adding NFS Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+        "clustering_title": "Adding NFS Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md b/corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
new file mode 100644
index 0000000..ff3e407
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
@@ -0,0 +1,21 @@
+# Adding NFS Pools
+
+Before adding an NFS Pool, ensure your NFS target is configured as described in the previous section. With configuration complete, follow the steps below:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. Click into the Storage tab and then the Data Stores subtab
+4. Click ADD
+5. From the ADD DATA STORE modal, configure the following:
+
+   1. **NAME:** An identifiable name for the datastore in the UI
+   2. **TYPE:** NFS Pool
+   3. **SOURCE HOST:** The NFS server name or IP address
+   4. **SOURCE DIRECTORY:** The path of the exported NFS share
+   5. **VERSION:** Either 3 or 4 depending on the NFS version running on the source server
+   6. **IMAGE TARGET:** Marked if this datastore should be used as a storage location for virtual images
+6. Click Save
+
+![The add datastore modal for NFS-type datastores](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-D53B7324-222A-4953-9222-824F49846CB0-high.png)
+
+At this point the HVM manager will automatically mount the NFS share on all hosts within the cluster. It will also handle setting various other options such as autostart and management of mountpoint for the share within the host filesystem.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json b/corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
new file mode 100644
index 0000000..d13ca3f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+  "title": "Additional System Health Indices",
+  "ordinal": 262,
+  "parent_title": "VM Essentials Health",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.html",
+  "topic_cluster": {
+    "clustering_title": "Additional System Health Indices",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+        "clustering_title": "Additional System Health Indices"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+        "clustering_title": "Additional System Health Indices"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md b/corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
new file mode 100644
index 0000000..a10a94f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
@@ -0,0 +1,106 @@
+# Additional System Health Indices
+
+CPU
+:   - Processor Count
+    - Process Time
+    - Morpheus CPU
+    - System CPU
+    - System Load
+
+MEMORY
+:   - Morpheus Memory
+    - Morpheus Used Memory
+    - Morpheus Free Memory
+    - Morpheus Memory Usage
+    - System Memory
+    - System Used Memory
+    - System Free Memory
+    - System Memory Usage
+    - System Swap
+    - Free Swap
+
+DATABASE
+:   - Lifetime Connections
+    - Aborted Connections
+    - Max Used Connections
+    - Max Connections
+    - Threads Running
+    - Threads Connected
+    - Slow Queries
+    - Temp Tables
+    - Key Reads
+    - Handler Reads
+    - Buffer Pool Free
+    - Open Tables
+    - Table Scans
+    - Full Joins
+    - Key Read Requests
+    - Key Reads
+    - Engine Waits
+    - Lock Waits
+    - Handler Reads
+    - Engine IO Writes
+    - Engine IO Reads
+    - Engine IO Double Writes
+    - Engine Log Writes
+    - Engine Memory
+    - Dictionary Memory
+    - Buffer Pool Size
+    - Free Buffers
+    - Database Pages
+    - Old Pages
+    - Dirty Page Percent
+    - Max Dirty Pages
+    - Pending Reads
+    - Insert Rate
+    - Update Rate
+    - Delete Rate
+    - Read Rate
+    - Buffer Hit Rate
+    - Read Write Ratio
+    - Uptime
+
+ELASTIC
+:   - Status
+    - Cluster
+    - Node Count
+    - Data Nodes
+    - Shards
+    - Primary Shards
+    - Relocating Shards
+    - Initializing
+    - Unassigned
+    - Pending Tasks
+    - Active Shards
+
+NOTE
+
+status is typical for Opensearch
+
+Elastic Nodes
+:   - Node
+    - Master
+    - Location
+    - Heap Usage
+    - Memory Usage
+    - CPU Usage
+    - 1M Load
+    - 5M Load
+    - 15M Load
+
+Elastic Indices
+:   - Health
+    - Index
+    - Status
+    - Primary
+    - Replicas
+    - Doc
+    - Count
+    - Primary
+    - Size
+    - Total Size
+
+Queues
+:   - Queue Count
+    - Busy Queues
+    - Error Queues
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json b/corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
new file mode 100644
index 0000000..42adb2f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+  "title": "VM Essentials Health",
+  "ordinal": 260,
+  "parent_title": "Health",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html",
+  "topic_cluster": {
+    "clustering_title": "VM Essentials Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+        "clustering_title": "VM Essentials Health"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+        "clustering_title": "VM Essentials Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md b/corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
new file mode 100644
index 0000000..af787f4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
@@ -0,0 +1,15 @@
+# VM Essentials Health
+
+The VM Essentials Health section provides an overview of the health of your VM Essentials appliance. It includes an appliance health summary in the following areas:
+
+- **CPU:** Appliance CPU usage is checked. If usage is greater than 50%, this indicator will be in a yellow or warning state. If VM Essentials is unable to complete the check, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to upgrade to increase CPU. The **Overall** health indicator will mirror the CPU health indicator
+- **Memory:** If swap usage is above 60% or VM Essentials memory usage is above 95%, this indicator will be in a yellow or warning state. If VM Essentials is unable to complete the check for any reason, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to increase swap, upgrade the appliance to add memory, or consider a different appliance architecture for those using single-node appliances
+- **Storage:** If utilization of the filesystem mounted at “/” exceeds 80%, this indicator will be in a yellow warned status. Above 90% will put this indicator in red or error status
+- **Database:** The database is checked. If the number of database connections exceeds the configured maximum number of connections or if any test queries are reported as being slow, this indicator will be in a yellow or warning state. If VM Essentials is unable to communicate with the database, it will be in a red or error state. In the database section further down the page, you can check the number of maximum used connections against the number of max connections. In the case of database connections exceeding the maximum, consider increasing the maximum settings connection
+- **Elastic:** Elasticsearch is polled for the health status of each index. If any indices are not reporting a “green” health status, this indicator will be in a yellow or warning state.
+- **Queues:** RabbitMQ queues are checked. Any queues containing more than 1000 messages are considered to be in an error state. Appliance Queue health is given in a yellow or warning status when any queues are in such an error state. In the Queues section further down the page you can see the individual Queues listed and which have messages piling up. When the appliance is unable to complete the check for any reason, this indicator will be in a red or error state
+
+**Subtopics**  
+
+- **[Health Levels](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.html)**
+- **[Additional System Health Indices](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json b/corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
new file mode 100644
index 0000000..1238af5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+  "title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+  "ordinal": 235,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md b/corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
new file mode 100644
index 0000000..52d2865
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
@@ -0,0 +1,59 @@
+# Configuring Windows Workloads (Windows 2022 or later) for Migration
+
+Migrating Windows workloads from VMware vCenter Clouds to HVM Clusters using the bulk Migrations feature requires some initial configurations checks. This section goes through an example preparation process for a Windows VM running on vCenter.
+
+This guide makes the following assumptions about the workload to be migrated:
+
+- Configured to boot as EFI or BIOS
+- Virtualization Based Security (VBS) is enabled
+- Secure Boot is enabled
+- Trusted Platform Module (TPM) is disabled
+- The VM has access to the recovery partition (if not, a Windows Recovery Environment disc or installation media may be required to access some of the menus referenced in this section)
+
+Inject VirtIO Drivers
+
+To begin, restart the VMware Windows guest in the [Windows Recovery Environment (Windows RE)](https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b). In Windows RE, choose a keyboard layout if prompted. Then, select the **Troubleshoot** option. From the Troubleshoot menu, select **Command Prompt**.
+
+Within the Command Prompt session, enter **diskpart** using this command: `diskpart`. Check the disks that are available with `list disk`. At this point, you may receive the message that "There are no fixed disks to show." or the disk with Windows OS might not be listed. If that is the case, follow the steps in the next section to mount the drives. If that is not the case, skip to the following section to continue the process of injecting the VirtIO drivers.
+
+![Enter dispart command line tool and list disks](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-6D43B362-18E8-4E21-8CE1-733555398E59-high.png)
+
+Mounting the Drives
+
+From vCenter, mount the VMware Tools installer to the VM using the "Install VMware Tools..." option (**Actions > Guest OS > Install VMware Tools...**). Then, back in diskpart, use the following command to find the CD/DVD-ROM drive letter: `list volume`. Make note of the CD-ROM drive letter, which in the case of this example is drive "D." Exit diskpart with the `exit` command.
+
+![listing volumes in diskpart](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-E8FB0956-0BE4-4600-ACC9-DD48E590F2CE-high.png)
+
+Enter the following command to load the storage drivers which will enable you to see the hard disks: `drvload "D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64\pvscsi.inf"`. Note that the prior command references Windows 10 as the operating system but choose the most appropriate or the latest available. It also references drive "D" which may vary from case to case.
+
+With the driver loaded, once again confirm the disks are mounted with `diskpart` and `list disk`. They're now mounted but the partitions/volumes need drive letters so, while still in diskpart, list the volumes with: `list volume`. In this example case, "Volume 1" is the primary Windows volume. Select the volume and assign a drive letter, in the example case the assigned letter will be "C": `select volume 1` and `assign letter=c`. Check your work by listing the volumes again, the primary Windows volume should be assigned the correct drive letter: `list volume`.
+
+![Assigning a drive letter to a volume](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-8506AA86-13D4-4086-B361-5C5AB0CFC5E9-high.png)
+
+Exit diskpart once again (`exit`) and unmount the VMware Tools installer from the VM back in the vCenter console (**Actions > Guest OS > Unmount VMware Tools Installer**).
+
+Inject VirtIO drivers (cont.)
+
+Download the [latest](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) or [stable](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/) VirtIO drivers ISO to your local workstation. The latest is recommended but often they are the same. Add the ISO to vCenter either by uploading it to a datastore or to the Content Library. Still in vCenter, mount the ISO using a CD-ROM device on the VM and make sure it's connected. Enter the following commands to inject the VirtIO storage drivers into the Windows boot-start drivers from the mounted ISO: `dism /image:C:\ /add-driver:D:\viostor\2k22\amd64\viostor.inf` and `dism /image:C:\ /add-driver:D:\vioscsi\2k22\amd64\vioscsi.inf`. Note once again that the OS volume will not be assigned the "C" drive letter and the CD-ROM device will not be assigned the "D" drive letter in every case. Similarly, in this example "2k22" is used but that won't be appropriate in every case. If successful, a message will be received that the driver packages were successfully installed. Close the Command Prompt window and click **Continue** to boot Windows once again.
+
+![installing viostor.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-A481A334-59CE-42D9-857D-0B5FDEE31BAB-high.png)![installing vioscsi.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-10CEA2F9-9885-464E-A57B-303AC913FBBD-high.png)
+
+Prepare the OS
+
+Once logged back in, install the VirtIO drivers in the OS using the ISO, which is still mounted, by navigating to the CD-ROM/DVD-ROM drive. Install `virtio-win-gt-x64.msi` and `virtio-win-guest-tools.exe` from the root of the ISO. Maintain all default selections during the installation. Next, unmount any ISOs still attached to the VM, either by ejecting in Windows or by setting the CD-ROM drive to "Client Device" in vCenter.
+
+Now, shut down the VM. Keep in mind that the VMware Cloud integration may be configured to automatically maintain power state of associated VMs. Navigate to Infrastructure > Clouds and edit the Cloud. Make note of the "AUTOMATICALLY POWER ON VMS" configuration. If checked, you will need to shut down the VM via the product UI tools rather than from the vCenter console or from within the guest OS. Alternatively, you could uncheck "AUTOMATICALLY POWER ON VMS", save changes to the Cloud, and then power down the VM from vCenter or from the guest OS but bear in mind changing this configuration would affect all VMs associated with the Cloud in the product.
+
+Migrating
+
+This completes the preparation steps. From here, create a new Migration Plan that includes the prepared VM and run it. Take a look at the previous section for more information on creating and running Migration Plans.
+
+Post-Conversion
+
+As a final note, bear in mind that the migration tool does not uninstall VMware Tools following conversion, which can lead to start-up errors being surfaced in migrated VMs. In some cases, the VMware Tools installation may become corrupted which prevents simply uninstalling using the Control Panel.
+
+To prevent VMware Tools from executing at startup, within the Windows guest navigate to Settings > Apps > Startup and turn off VMware Tools Core Service. See the example screenshot below for a Windows 2022 Guest.
+
+![Turning off VMware Tools Core Service at Windows guest startup](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-EEC38EAD-A903-41BD-8C98-BACAC114BA0E-high.png)
+
+Additionally, you can attempt to uninstall VMware Tools completely using Microsoft recommended processes and tooling for uninstalling stuck programs. See [this article](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d) from the Microsoft Support for procedure and links to a helpful tool.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json b/corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
new file mode 100644
index 0000000..ac66bf2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+  "title": "Task Types",
+  "ordinal": 64,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.html",
+  "topic_cluster": {
+    "clustering_title": "Task Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+        "clustering_title": "Task Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+        "clustering_title": "Task Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md b/corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
new file mode 100644
index 0000000..7784855
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
@@ -0,0 +1,9 @@
+# Task Types
+
+Available Task Types
+
+         |  | Task Type | Task Description | Source Options | Execute Target Options | Configuration Requirements | Role Permissions Requirements |
+| --- | --- | --- | --- | --- | --- | --- |
+| powershell | PowerShell Script | Execute PowerShell Script on the Target Resource | Local, Repository, Url | Remote, Resource, Local | None | Library: Tasks |
+| restart | Restart | Restarts target VM/Host/Container and confirms startup status before executing next task in Workflow | System | Resource | None | Library: Tasks |
+| shellscript | Shell Script | Executes Bash script on the target resource | Local, Repository, Url | Local, Remote, Resource | None | Library: Tasks |
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json b/corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
new file mode 100644
index 0000000..d673843
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+  "title": "Existing Instances",
+  "ordinal": 319,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.html",
+  "topic_cluster": {
+    "clustering_title": "Existing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+        "clustering_title": "Existing Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+        "clustering_title": "Existing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md b/corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
new file mode 100644
index 0000000..b8a8b9a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
@@ -0,0 +1,11 @@
+# Existing Instances
+
+VM Essentials provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into VM Essentials. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, VM Essentials will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json b/corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
new file mode 100644
index 0000000..71d321c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+  "title": "Configuring HPE Morpheus Enterprise Appliance Backup",
+  "ordinal": 311,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D647F00D-6B45-4E18-B442-14835847EFA7.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+        "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+        "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md b/corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
new file mode 100644
index 0000000..9f20e4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
@@ -0,0 +1,23 @@
+# Configuring HPE Morpheus Enterprise Appliance Backup
+
+## About this task
+
+With the groundwork laid in the previous sections, we’re ready to enable and configure HPE Morpheus Enterprise appliance backup.
+
+## Procedure
+
+1. Navigate to Administration > Settings > Backups
+2. Slide the switch labeled “Backup Appliance”
+3. Click SAVE
+
+## Results
+
+On saving this change, a text link labeled “Backup” will be activated which will take you directly to the automatically-generated appliance backup job. Click this link to continue.
+
+1. Click the EDIT button
+2. Enter a name for the appliance backup job if you wish to change it from the default
+3. Select the appropriate storage bucket or file share
+4. Choose a pre-created backup job. If you do not have an existing backup job that fits, a retention count and schedule can be manually created in this modal. If you manually configure retention counts and schedules in addition to associating a Job, the Job values will override any manual settings.
+5. Click SAVE CHANGES
+
+At this point, your appliance will be automatically backed up on the schedule you chose and stored in the selected location. An appliance backup will store backup copies of the appliance MySQL database. Should you need to restore or migrate your database from backup, follow the steps in the next section of this guide.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json b/corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
new file mode 100644
index 0000000..16ce3d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+  "title": "Upgrade License Key",
+  "ordinal": 293,
+  "parent_title": "License",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrade License Key",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+        "clustering_title": "Upgrade License Key"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+        "clustering_title": "Upgrade License Key"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md b/corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
new file mode 100644
index 0000000..f5d10b4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
@@ -0,0 +1,14 @@
+# Upgrade License Key
+
+## About this task
+
+To add a new or update an existing License:
+
+## Procedure
+
+1. Copy the license key into the large text area at the bottom of the page
+2. Click UPDATE
+
+## Results
+
+If valid, the new License will be applied. Note that the new license may replace an existing license or may stack onto an existing license.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json b/corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
new file mode 100644
index 0000000..d4934af
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+  "title": "Overview",
+  "ordinal": 167,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md b/corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
new file mode 100644
index 0000000..61dbeb6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
@@ -0,0 +1,5 @@
+# Overview
+
+In many situations, organizations deploy virtual machines in proxy restricted environments for things such as PCI Compliance, or just general security. As a result of this VM Essentials provides out of the box support for proxy connectivity. Proxy authentication support is also provided with both Basic Authentication capabilities as well as NTLM for Windows Proxy environments. VM Essentials is even able to configure virtual machines it provisions to utilize these proxies by setting up the operating systems proxy settings directly (restricted to cloud-init based Linux platforms for now, but can also be done on windows based platforms in a different manner).
+
+To get started with Proxies, it may first be important to configure the VM Essentials appliance itself to have access to proxy communication for downloading service catalog images. To configure this, visit the Administration > Settings page where a section labeled “Proxy Settings” is located. Fill in the relevant connection info needed to utilize the proxy. It may also be advised to ensure that the Linux environment’s `http_proxy`, `https_proxy`, and no\_proxy are set appropriately.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json b/corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
new file mode 100644
index 0000000..3366e91
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+  "title": "Storage",
+  "ordinal": 365,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md b/corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
new file mode 100644
index 0000000..ba97b12
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
@@ -0,0 +1,5 @@
+# Storage
+
+**Subtopics**  
+
+- **[HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json b/corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
new file mode 100644
index 0000000..5e8d30d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+  "title": "Provisioning with Proxies",
+  "ordinal": 170,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning with Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+        "clustering_title": "Provisioning with Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+        "clustering_title": "Provisioning with Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md b/corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
new file mode 100644
index 0000000..ef3dff8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
@@ -0,0 +1,5 @@
+# Provisioning with Proxies
+
+Proxy configurations can vary from operating system to operating system and in some cases it is necessary for these to be configured in the blueprint as a prerequisite. In other cases it can also be configured automatically. Mostly with the use of cloud-init (which all of our out of the box service catalog utilizes on all clouds). When editing/creating a cloud there is a setting for “Provisioning Proxy” in “Provisioning Options”. If this proxy is set, VM Essentials will automatically apply these proxy settings to the guest operating system.
+
+Overriding proxy settings can also be done on the Network record. Networks (or subnets) can be configured in Infrastructure  >  Networks or on the Networks tab of the relevant Cloud detail page. Here, a proxy can also be assigned as well as additional options like the No Proxy rules for proxy exceptions.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json b/corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
new file mode 100644
index 0000000..fa7e92a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+  "title": "Initial Backups Setup",
+  "ordinal": 205,
+  "parent_title": "Backups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.html",
+  "topic_cluster": {
+    "clustering_title": "Initial Backups Setup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+        "clustering_title": "Initial Backups Setup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+        "clustering_title": "Initial Backups Setup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md b/corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
new file mode 100644
index 0000000..a923190
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
@@ -0,0 +1,8 @@
+# Initial Backups Setup
+
+Global Backup settings (Administration > Settings > Backups), Storage Providers (Infrastructure > Storage) and Execution Schedules (Library > Automation > Execute Scheduling) should be configured prior to creating backups. Global backup settings are where scheduled backups can be globally enabled or disabled and certain global backup default settings can be configured. Storage providers include local and remote configured storage locations that can be used as backup targets. Execution schedules are timed intervals at which individual automated backup jobs will run. See the next two sections for full details on global backup settings and configuring execution schedules. See VM Essentials UI [storage documentation](https://docs.morpheusdata.com/en/latest/infrastructure/storage/storage.html) for more information about configuring local and remote storage targets and/or integrating with third party storage providers.
+
+**Subtopics**  
+
+- **[Global Backups Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html)**
+- **[Execution Schedules](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json b/corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
new file mode 100644
index 0000000..f4fd980
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+  "title": "Configuring Virtual Images",
+  "ordinal": 72,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md b/corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
new file mode 100644
index 0000000..596f20f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
@@ -0,0 +1,6 @@
+# Configuring Virtual Images
+
+**Subtopics**  
+
+- **[System Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-6549D43B-D0BB-4416-9771-AF11F387B629.html)**
+- **[User Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json b/corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
new file mode 100644
index 0000000..0b01f57
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+  "title": "Alarms (dashboard)",
+  "ordinal": 10,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.html",
+  "topic_cluster": {
+    "clustering_title": "Alarms (dashboard)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+        "clustering_title": "Alarms (dashboard)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+        "clustering_title": "Alarms (dashboard)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md b/corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
new file mode 100644
index 0000000..47a8563
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
@@ -0,0 +1,3 @@
+# Alarms (dashboard)
+
+The most recent five Alarms are displayed here and the user may link through to the resource which triggered the Alarm. For the complete list of Alarms and more information on each Alarm navigate to Operations > Activity > Alarms
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json b/corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
new file mode 100644
index 0000000..0e1050f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+  "title": "Viewing and Assigning Hardware Devices",
+  "ordinal": 134,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing and Assigning Hardware Devices",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md b/corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
new file mode 100644
index 0000000..8fcd487
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
@@ -0,0 +1,23 @@
+# Viewing and Assigning Hardware Devices
+
+Hardware Devices are surfaced at the Host detail level and the VM (server) detail level through a Devices tab. The Host detail will show all attached hardware devices and their current status: Attached (to the host), detached (from the host), or assigned (to a VM). The VM detail will show only hardware devices currently attached to that VM. To begin consuming hardware devices with HVM Cluster VMs, look again at the list in the Devices tab on the Host detail page. Detach a piece of hardware from the host using the ACTIONS dropdown for that piece of hardware. As shown in the screenshot below, DETACH DEVICE is selected for a USB device.
+
+![../../_images/detachDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-A94BDC5A-C89C-426E-9EF6-2914BC84AC21-high.png)
+
+Once detached, the status of the device is changed to “Detached” (see screenshot below) and the device is available for consumption by VMs running on this host.
+
+![../../_images/deviceDetached.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-34E14A70-071B-4A63-BD76-5D0A1261BC20-high.png)
+
+To assign the hardware to a specific VM, click the ACTIONS dropdown once again for the now-detached hardware. Now, click ASSIGN DEVICE.
+
+![../../_images/assignDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-443A34ED-8373-4AB9-9F26-730FF70DDD3C-high.png)
+
+Within the ASSIGN DEVICE modal that will appear, select the server for device assignment and click EXECUTE.
+
+![../../_images/assignToServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-F76B03BD-5880-4AC2-8B3D-98537D873BDE-high.png)
+
+The icon and status for the device in the hardware list has now changed to “Assigned.” If we then open a console session with this VM, we can see the USB device is assigned successfully and is usable by the guest OS.
+
+![../../_images/vmConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-C1FCF142-72C3-4E92-9EBB-6277EC6DD1AA-high.png)
+
+The same process can be used to detach and assign GPU or NVME devices.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json b/corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
new file mode 100644
index 0000000..a1a5bee
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+  "title": "User Settings",
+  "ordinal": 255,
+  "parent_title": "Users",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md b/corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
new file mode 100644
index 0000000..e5ee51f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
@@ -0,0 +1,3 @@
+# User Settings
+
+Additional settings for a User can be found in the User Settings section, including a user photo, API access, two-factor authentication settings, default Groups and Clouds, and more. User Settings is accessed by clicking on the name of the User in the upper-right corner of the application window and selecting “User Settings.” See the dedicated section on User Settings elsewhere in this documentation for a more in-depth description of User Settings.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json b/corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
new file mode 100644
index 0000000..6a97faf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+  "title": "Monitoring the Cluster",
+  "ordinal": 121,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md b/corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
new file mode 100644
index 0000000..c267398
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
@@ -0,0 +1,14 @@
+# Monitoring the Cluster
+
+With the server provisioned and a workload running, take a look at the monitoring and actions capabilities on the cluster detail page (Infrastructure > Clusters, then click on the new HVM cluster). View cluster performance and resource usage (Summary and Monitoring tabs), drill into individual hosts (Hosts tab), see individual workloads (VMs tab), and more.
+
+**Subtopics**  
+
+- **[Moving Workloads Between Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.html)**
+- **[Adding hosts](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.html)**
+- **[Maintenance Mode](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html)**
+- **[vCPU Placement](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html)**
+- **[Host Hardware Sensor Data Collection](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html)**
+- **[Failover](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.html)**
+- **[Adding an NFS Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json b/corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
new file mode 100644
index 0000000..eb1c519
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+  "title": "Email Settings",
+  "ordinal": 269,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.html",
+  "topic_cluster": {
+    "clustering_title": "Email Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+        "clustering_title": "Email Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+        "clustering_title": "Email Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md b/corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
new file mode 100644
index 0000000..11fefe0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
@@ -0,0 +1,23 @@
+# Email Settings
+
+In this section, you can configure an SMTP server for email notification delivery. You will need to provide VM Essentials the following information, your mail server systems administrator can assist you in filling these fields and with the preferred encryption method.
+
+- From Address
+- SMTP Server
+- SMTP Port
+- SSL Enabled
+- TLS Encryption
+- SMTP User
+- SMTP Password
+
+We recommend that you add the VM Essentials server to your SMTP whitelist as well as using user authentication as an additional security measure.
+
+Once you have added your SMTP server information into VM Essentials, scroll down to the bottom of the page and press the blue SAVE button which can be found under the Enabled Clouds section.
+
+When you have saved your SMTP server settings in the VM Essentials appliance you will then need to restart the UI. To restart the morpheus-ui, connect to your VM Essentials server via SSH and run the below command:
+
+`sudo morpheus-ctl restart morpheus-ui`
+
+IMPORTANT
+
+If you do not restart morpheus-ui, the notifications will not be sent. Please note it can take up to three minutes for the UI to become reachable again.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json b/corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
new file mode 100644
index 0000000..3b49908
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+  "title": "Provisioning",
+  "ordinal": 276,
+  "parent_title": "Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md b/corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
new file mode 100644
index 0000000..a39da47
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
@@ -0,0 +1,11 @@
+# Provisioning
+
+**Subtopics**  
+
+- **[Provisioning Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.html)**
+- **[Cloud-Init Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3D27BE17-47C9-476C-AD13-DD516697F862.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.html)**
+- **[Library Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.html)**
+- **[PXE Boot Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B94BC2CB-8504-41C6-8848-512529EEE941.html)**
+- **[App Blueprint Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.html)**
+- **[Terraform Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json b/corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
new file mode 100644
index 0000000..021c743
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+  "title": "HPE Aruba CX DSS",
+  "ordinal": 356,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Aruba CX DSS",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md b/corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
new file mode 100644
index 0000000..a5bec7c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
@@ -0,0 +1,12 @@
+# HPE Aruba CX DSS
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.html)**
+- **[Adding HPE Aruba CX DSS Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.html)**
+- **[Manage Security Groups and Rules in Morpheus](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.html)**
+- **[Create HPE ANW DSS Port Group Network](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.html)**
+- **[Delete HPE ANW DSS Port Group Network](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.html)**
+- **[View HPE Aruba CX DSS Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json b/corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
new file mode 100644
index 0000000..ca7ee39
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+  "title": "vCPU Placement",
+  "ordinal": 126,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html",
+  "topic_cluster": {
+    "clustering_title": "vCPU Placement",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md b/corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
new file mode 100644
index 0000000..045999e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
@@ -0,0 +1,28 @@
+# vCPU Placement
+
+vCPU placement settings relate to vCPU placement within the physical topology of the CPU. Since a vCPU is just a schedulable thread the hypervisor maps onto physical cores, we can create performance increases through smart scheduling. A simplified CPU topology might look something like this:
+
+```
+```
+Socket  
+ └── NUMA node  
+     └── Core  
+         └── Threads (SMT / Hyper-Threading)
+```
+```
+
+As you can see from the diagram above, multiple physical cores can reside within the same NUMA node. Physical CPU cores within the same NUMA node share the same region of the L3 cache and local memory access. By scheduling vCPUs making up a single VM to cores within the same NUMA node, we can avoid the performance penalties associated with crossing NUMA boundaries and accessing remote memory locations.
+
+HVM Clusters offer three vCPU placement settings. The default setting is **Unmanaged**. Clusters with unmanaged vCPU placement will make no special effort to schedule vCPUs within the same NUMA region. Next is **Region**. Clusters with this vCPU placement will attempt to schedule vCPUs associated with the same VM within the same NUMA region. When flexibility is needed, vCPUs may hop to different physical cores but they will be kept within the same NUMA region. Third is **Pinned**. Clusters with this vCPU placement will also attempt to schedule vCPUS associated with the same VM within the same NUMA region but the vCPUs will remain pinned to same cores. In certain cases, pinning may improve performance and in other cases creating inflexibility may introduce inefficiency.
+
+TIP
+
+Setting **Region** placement is a sensible starting configuration if you don't have a specific reason to choose one of the other two. In internal testing, a 7-10% improvement in prime number generation time was observed with Region pinning versus Unmanaged pinning.
+
+How to Configure vCPU Placement Settings
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. From the Cluster detail page, click Edit
+4. Within the vCPU Placement field, select the desired value. See the paragraphs above for a description of each configuration
+5. Click Save changes
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json b/corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
new file mode 100644
index 0000000..6f22061
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+  "title": "Utilities",
+  "ordinal": 294,
+  "parent_title": "Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.html",
+  "topic_cluster": {
+    "clustering_title": "Utilities",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+        "clustering_title": "Utilities"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+        "clustering_title": "Utilities"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md b/corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
new file mode 100644
index 0000000..84b2aac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
@@ -0,0 +1,16 @@
+# Utilities
+
+System administrators have access to a utilities panel with the following options:
+
+- **Reindex all searchable data:** Execute
+- **Toggle Maintenance Mode:** Enable
+
+NOTE
+
+Maintenance mode cleanly places VM Essentials into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting VM Essentials UI disables maintenance mode.
+
+NOTE
+
+When using VM Essentials in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
+
+A VM Essentials node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json b/corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
new file mode 100644
index 0000000..02e131d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+  "title": "Generate Key Pair",
+  "ordinal": 200,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.html",
+  "topic_cluster": {
+    "clustering_title": "Generate Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+        "clustering_title": "Generate Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+        "clustering_title": "Generate Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md b/corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
new file mode 100644
index 0000000..5f86685
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
@@ -0,0 +1,17 @@
+# Generate Key Pair
+
+## About this task
+
+To generate a Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. After naming the new key pair, VM Essentials will reveal both the public and private key
+
+## Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json b/corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
new file mode 100644
index 0000000..5cba3fe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+  "title": "History",
+  "ordinal": 25,
+  "parent_title": "Activity",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html",
+  "topic_cluster": {
+    "clustering_title": "History",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+        "clustering_title": "History"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+        "clustering_title": "History"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md b/corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
new file mode 100644
index 0000000..c10f905
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
@@ -0,0 +1,15 @@
+# History
+
+The HISTORY section shows process history from Instance processes. This is an aggregate view of the `History` tab contained in each Instance detail page.
+
+![History](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-DE8D2A86-CAB3-4D94-9D4C-83C5FA49585A-high.png)
+
+Processes can be expanded to view all process steps and process history detail including output and errors.
+
+Access to HISTORY is given by the `Operations:Activity` Role permission.
+
+The Logs displayed in Administration > Health > Morpheus Logs are from `/var/log/morpheus/morpheus-ui/current`. These logs show all ui activity and are useful for troubleshooting and auditing.
+
+NOTE
+
+Stack traces in Administration > Health > Morpheus Logs are filtered for VM Essentials services. Complete stack traces can be found in `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json b/corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
new file mode 100644
index 0000000..ec72af5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+  "title": "Key Pairs",
+  "ordinal": 202,
+  "parent_title": "Trust",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html",
+  "topic_cluster": {
+    "clustering_title": "Key Pairs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md b/corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
new file mode 100644
index 0000000..d26ac42
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
@@ -0,0 +1,20 @@
+# Key Pairs
+
+The key pairs section enables the following actions: Add and Delete key pairs. Key pairs are commonly used by HPE Morpheus VM Essentials for accessing instances via SSH. HPE Morpheus VM Essentials stores key pairs to simplify administration and access across both private and public clouds.
+
+HPE Morpheus VM Essentials only accepts key pairs in PEM format (for example, a private key beginning with `-----BEGIN RSA PRIVATE KEY-----`) and accepts RSA (PKCS#1 or PKCS#8, default), DSA (PKCS#1 or PKCS#8), EC (PKCS#8), and ed25519 (PKCS#8) keys. If you have a key in another format, such as OpenSSH, convert the key:
+
+```
+```
+#No passphrase  
+ssh-keygen -m pem -f /path/to/key  
+#With passphrase  
+ssh-keygen -p -P "old passphrase" -N "new passphrase" -m pem -f path/to/key
+```
+```
+
+**Subtopics**  
+
+- **[Add Existing Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C_2.html)**
+- **[Generate Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.html)**
+- **[Delete Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1_2.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json b/corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
new file mode 100644
index 0000000..7dd1b25
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+  "title": "Create Instance",
+  "ordinal": 370,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html",
+  "topic_cluster": {
+    "clustering_title": "Create Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+        "clustering_title": "Create Instance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+        "clustering_title": "Create Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md b/corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
new file mode 100644
index 0000000..5106171
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
@@ -0,0 +1,97 @@
+# Create Instance
+
+## About this task
+
+Create an Instance with the Datastore.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. In the Instances tab, Click + ADD.
+3. In the ADD INSTANCE wizard, provide the following details: 
+
+   - In the Type section, select HPE HVM.
+   - Click Next.
+
+     ![Create Instance Type](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-55F890E0-47C6-4621-9A97-C399B1AD1BB0-high.png)
+   - In the Group tab, provide the following details:
+
+     GROUP:
+     :   Select the group for the instance.
+
+     CLOUD:
+     :   Select the cloud for the instance.
+
+     NAME:
+     :   Enter the name for the instance in VM Essentials.
+
+     ENVIRONMENT:
+     :   Select the environment for the instance.
+   - Click Next.
+
+     ![Create Instance Group](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4EEB766E-54E0-4C82-A60B-59AE6B75D705-high.png)
+   - In the Configure tab, provide the following details:
+
+     LAYOUT:
+     :   Select the Layout for the Instance.
+
+     PLAN:
+     :   Select the Plan for the Instance.
+
+     RESOURCE POOL:
+     :   Select the Resource Pool (Cluster) for the Instance.
+
+     VOLUMES:
+     :   Add one or more Volumes to the Instance. Select the datastore created in the previous section.
+
+     Storage Type
+     :   Select the replication type from the Storage Type drop-down list.
+
+         If you select the `Standard Volume - HPE Alletra LUN` option, the system provisions VMs on a standard Logical Unit Number (LUN).
+
+         If you select the `HPE Alletra LUN - Active Peer Persistence` option, remote copy groups are created, and VMs are replicated across both primary and secondary storage systems.
+
+         For VMs created with the `HPE Alletra LUN - Active Peer Persistence` storage type, Host Proximity is set to `All`, allowing access from both the primary and secondary sites. VMs created with this storage type are automatically added to an Active-Active Peer Persistence (AAPP) replication group.
+
+         NOTE
+
+         VMs and storage volumes are not created if you select a mix of replicated and non-replicated volumes.
+
+     NETWORK:
+     :   Add Networks to the Instance.
+
+     IMAGE:
+     :   Select the Image for the Instance.
+
+     HOST:
+     :   Select the cluster host for the Instance.
+
+     Other configurations may be added as needed.
+
+     ![Create Instance Configure](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-358491C6-43F7-4197-9F53-94D50A1E99F1-high.png)
+   - Click Next.
+   - Add Automation Tasks, if needed
+   - Click Next.
+   - Review the Instance configuration.
+   - Click Complete.![Create Instance - Review](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-22C7AB89-6966-4E4D-8514-6A2FAD489B61-high.png)
+
+## Results
+
+The Instance is now provisioned to the new datastore and is viewable within the Instances (Provisioning > Instances) section.
+
+CAUTION
+
+- Pre-existing host records may prevent successful host creation and provisioning.
+- VM Essentials does not automatically rename hosts created externally.
+- Host names must match on both primary and secondary systems for host proximity to work.
+
+To view the details of volumes or disks for an AAPP Instance provisioning:
+
+1. Navigate to Provisioning > Instances.
+2. In the Instances tab, click the replicated VM to see its details.
+3. Click the Storage > Volumes tab. ![Volume tab](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-0E66529D-3C71-48BF-B797-D866B4A703B4-high.png)
+4. Click Volume Name to see the details, such as Remote Copy Status, Volume Type, Remote Copy Group Status, and Host Sets. ![Volume details](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-331D2A26-6024-4810-9FD1-E0D4BD3253AA-high.png)
+
+   The following volume details screen is displayed for an Instance with non-AAPP storage type: ![Volume details - non-aapp](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4AF2DEA6-B2D8-46F8-B654-E1A46304439C-high.png)
+
+The volume details can also be accessed by navigating to Infrastructure > Storage > Volumes and clicking a volume name.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json b/corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
new file mode 100644
index 0000000..013afd5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+  "title": "Overview",
+  "ordinal": 139,
+  "parent_title": "Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md b/corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
new file mode 100644
index 0000000..034629a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
@@ -0,0 +1,5 @@
+# Overview
+
+The Networks section is for configuring networks across all Clouds in VM Essentials. Existing networks from Clouds added in VM Essentials will auto-populate in the Networks section.
+
+Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, VM Essentials allows administrators to restrict management of VM Essentials-created Networks through Role permissions.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json b/corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
new file mode 100644
index 0000000..039357c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+  "title": "User Management Settings",
+  "ordinal": 268,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.html",
+  "topic_cluster": {
+    "clustering_title": "User Management Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+        "clustering_title": "User Management Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+        "clustering_title": "User Management Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md b/corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
new file mode 100644
index 0000000..acf2b22
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
@@ -0,0 +1,31 @@
+# User Management Settings
+
+Min Password Length
+:   User passwords must at least be as many characters in length as the entered value
+
+Min Password Uppercase
+:   User passwords must include at least as many uppercase characters as the entered value
+
+Min Password Numbers
+:   User passwords must include at least as many numerals as the entered value
+
+Min Password Symbols
+:   User passwords must include at least as many special characters as the entered value
+
+Session Expires (Minutes)
+:   A user session is forcibly logged out after the entered number of minutes of inactivity
+
+Session Warning (Minutes)
+:   A pop-up warning is shown to the user when they have been inactive for the number of minutes entered. Example: If sessions are set to expire after 90 minutes, warn the user after 60 minutes if you intend to provide 30 minutes advance warning
+
+Expire Password After (Days)
+:   User account passwords will expire after the entered number of days. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User After Attempts (Number of Attempts)
+:   Disable a User account after a specified number of failed login attempts. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User If Inactive For (Days)
+:   Disable a User account if inactive for the entered number of days. The User will not be able to log into the appliance again until another User with sufficient rights enables the account. Enter 0 or leave the field empty to opt out of this feature.
+
+Send warning email before deactivating (Days)
+:   Enter the number of days prior to account deactivation that a warning email should be sent. For example, enter “5” to warn the User when they are five days short of the deactivation time entered in the prior field. Enter 0 or leave the field empty to opt out of this feature.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json b/corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
new file mode 100644
index 0000000..694375f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+  "title": "Amazon S3 Buckets",
+  "ordinal": 180,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.html",
+  "topic_cluster": {
+    "clustering_title": "Amazon S3 Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+        "clustering_title": "Amazon S3 Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+        "clustering_title": "Amazon S3 Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md b/corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
new file mode 100644
index 0000000..2308261
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
@@ -0,0 +1,77 @@
+# Amazon S3 Buckets
+
+## About this task
+
+To Add an Amazon S3 Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Amazon S3 from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   ACCESS KEY
+   :   AWS IAM Access Key
+
+   SECRET KEY
+   :   AWS IAM Secret Key
+
+   BUCKET NAME
+   :   Enter existing S3 Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   CREATE BUCKET
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created. If enabled, select an AWS Region to create the Bucket in.
+
+   ENDPOINT URL
+   :   Optional endpoint URL if pointing to an object store other than amazon that mimics the Amazon S3 APIs.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json b/corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
new file mode 100644
index 0000000..381acad
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+  "title": "Favorites",
+  "ordinal": 9,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.html",
+  "topic_cluster": {
+    "clustering_title": "Favorites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+        "clustering_title": "Favorites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+        "clustering_title": "Favorites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md b/corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
new file mode 100644
index 0000000..0baa217
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
@@ -0,0 +1,3 @@
+# Favorites
+
+Any Instances you’ve “favorited” will appear here along with the Instance name, type, and IP address
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json b/corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
new file mode 100644
index 0000000..0b8bae3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+  "title": "Integrate a Bucket or File Share",
+  "ordinal": 310,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.html",
+  "topic_cluster": {
+    "clustering_title": "Integrate a Bucket or File Share",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+        "clustering_title": "Integrate a Bucket or File Share"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+        "clustering_title": "Integrate a Bucket or File Share"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md b/corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
new file mode 100644
index 0000000..e848a75
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
@@ -0,0 +1,19 @@
+# Integrate a Bucket or File Share
+
+## About this task
+
+When configuring a HPE Morpheus Enterprise appliance backup, a storage location is selected. If you already have the destination bucket or file share integrated with HPE Morpheus Enterprise, skip to the next section. To integrate a new storage bucket, follow the steps below:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage
+2. Click on the Buckets or File Shares tab depending on your chosen storage type
+3. Click + ADD
+4. Select the appropriate bucket or file share type
+5. Complete the required fields and click SAVE CHANGES
+
+## Results
+
+NOTE
+
+Additional guidance on integrating each of the supported bucket and file share types can be found in [storage](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html) documentation.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json b/corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
new file mode 100644
index 0000000..20152f4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+  "title": "Integrations",
+  "ordinal": 256,
+  "parent_title": "Administration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md b/corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
new file mode 100644
index 0000000..fba41da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
@@ -0,0 +1,15 @@
+# Integrations
+
+The Integrations allows administrators to manage platform extensions and packages. Using Integrations, you can add, update, and remove plugins and packages to extend the functionality and standardize configurations.
+
+To access the Integrations, click Administration > Integrations.
+
+The Integrations page contains the following tabs:
+
+- Plugins
+- Packages
+
+**Subtopics**  
+
+- **[Plugins](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.html)**
+- **[Packages](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json b/corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
new file mode 100644
index 0000000..b95110e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+  "title": "Integrations",
+  "ordinal": 171,
+  "parent_title": "Network",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md b/corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
new file mode 100644
index 0000000..9bc5d1b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
@@ -0,0 +1,6 @@
+# Integrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.html)**
+- **[Scoping Services](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json b/corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
new file mode 100644
index 0000000..373e7c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+  "title": "Alarms",
+  "ordinal": 24,
+  "parent_title": "Activity",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html",
+  "topic_cluster": {
+    "clustering_title": "Alarms",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+        "clustering_title": "Alarms"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+        "clustering_title": "Alarms"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md b/corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
new file mode 100644
index 0000000..83bc7fa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
@@ -0,0 +1,7 @@
+# Alarms
+
+The Alarms section shows Operation notifications from Cloud and other Service Integrations. Cloud and other Service Integration Alarms are not generated by HPE Morpheus VM Essentials Software but synced and displayed for visibility in HPE Morpheus VM Essentials Software.
+
+For the complete list of Alarms and more information on each Alarm, navigate to Operations > Activity > Alarms.
+
+![Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-444E2530-12E2-439A-A1C7-EED4D7F91D38-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json b/corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
new file mode 100644
index 0000000..004e54b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+  "title": "Usage",
+  "ordinal": 331,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.html",
+  "topic_cluster": {
+    "clustering_title": "Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+        "clustering_title": "Usage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+        "clustering_title": "Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md b/corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
new file mode 100644
index 0000000..4de7e18
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
@@ -0,0 +1,18 @@
+# Usage
+
+vCenter
+:   - Non-Propagating
+
+Datacenter
+:   - Non-Propagating
+
+Cluster
+:   - Non-Propagating
+
+Host
+:   - Non-Propagating
+
+Datastore/Datastore Cluster
+:   - Propagating
+
+After completing the above steps, all VMware Cloud functionality should be available in VM Essentials without running into permissions errors.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json b/corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
new file mode 100644
index 0000000..bb3a1f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+  "title": "VM Provision Steps",
+  "ordinal": 28,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html",
+  "topic_cluster": {
+    "clustering_title": "VM Provision Steps",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+        "clustering_title": "VM Provision Steps"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+        "clustering_title": "VM Provision Steps"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md b/corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
new file mode 100644
index 0000000..9ac9fd5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
@@ -0,0 +1,48 @@
+# VM Provision Steps
+
+While many things can happen during an individual provisioning process, the basic order is:
+
+- Look for the Virtual Image
+
+  VM Essentials will check if the Virtual Image set on the Node Type or selected from a list of images during provisioning is already available to the HVM cluster or to a vCenter Cloud target. If not and it is an uploaded or local image, VM Essentials will attempt to upload the image to the HVM cluster or vCenter target.
+
+  **Upload Image**
+
+  For uploaded or local images that do not exist in the target, VM Essentials will need to upload the Image. Ensure the Virtual Image is valid for the target technology, the image meets the target upload requirements, and VM Essentials has network access and permissions to upload the image.
+
+  NOTE
+
+  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+  **Clone Image**
+
+  Once the Image is confirmed available in the target cloud, VM Essentials will clone the Image to the target Datastore.
+
+  NOTE
+
+  The target host must have access to the target Datastore of the Image
+- Reconfigure Image
+
+  Once cloned, VM Essentials will resize the Image based off provisioning parameters
+- Cloud-init (if enabled)
+  :   Attached cloud-init iso
+      :   When using cloud-init, VM Essentials will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.
+
+      VM Tools
+      :   VM Essentials will run guest customizations via VMware VM Tools, including network config when assigning static IP addresses.
+- Wait for Power On status and Network info
+
+  VM Essentials will wait to hear back from the target that the VM has successfully started and has an IP address.
+
+  NOTE
+
+  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, VM Essentials will skip waiting for network.
+- Finalize
+
+  By default, this step will include Agent installation.
+
+  IMPORTANT
+
+  If the VM is stuck in finalize for long periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.
+
+  If agent installation is not possible or is not desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json b/corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
new file mode 100644
index 0000000..7794b38
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+  "title": "Target Options",
+  "ordinal": 59,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.html",
+  "topic_cluster": {
+    "clustering_title": "Target Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+        "clustering_title": "Target Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+        "clustering_title": "Target Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md b/corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
new file mode 100644
index 0000000..e03bb7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
@@ -0,0 +1,7 @@
+# Target Options
+
+When creating a Task, users can select a target to perform the execution. Some Task types allow for any of the three execution targets listed below and some will limit the user to two or just one. The table in the next section lists the available execution targets for each Task type.
+
+- **Resource:** A VM Essentials-managed Instance or server is selected to execute the Task
+- **Local:** The Task is executed by the VM Essentials appliance node
+- **Remote:** The user specifies a remote box which will execute the Task
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json b/corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
new file mode 100644
index 0000000..c35e842
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+  "title": "Adding hosts",
+  "ordinal": 123,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.html",
+  "topic_cluster": {
+    "clustering_title": "Adding hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+        "clustering_title": "Adding hosts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+        "clustering_title": "Adding hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md b/corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
new file mode 100644
index 0000000..7044493
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
@@ -0,0 +1,11 @@
+# Adding hosts
+
+The process of adding hosts to a pre-existing cluster is very similar to the process of provisioning the cluster initially. The requirements for the new worker node will be identical to the nodes initially added when the cluster was first provisioned. See the earlier sections in this guide for additional details on configuring the worker nodes.
+
+To add the host, begin from the Cluster detail page (selected from the list at Infrastructure > Clusters). From the Cluster detail page, click ACTIONS and select “Add Worker”. Configurations required are the same as those given when the cluster was first created. Refer to the section above on “Provisioning the Cluster” for a detailed description of each configuration.
+
+Once VM Essentials has completed its configuration scripts and joined the new worker node to the cluster, it will appear in a ready state within the Hosts tab of the Cluster detail page. When provisioning workloads to this Cluster in the future, the new node will be selectable as a target host for new Instances. It will also be an available target for managing placement of existing VMs running on the cluster.
+
+NOTE
+
+It’s useful to confirm all scripts related to creating the new host and joining the new host to the cluster completed successfully. To confirm, navigate to the detail page for the new host (Infrastructure > Clusters > Selected Cluster > HostsTab > SelectedHost) and click on the History tab. Confirm all scripts, even those run on the pre-existing hosts, completed successfully as it’s possible the new host was added successfully (green status) but failed in joining the cluster. When such a situation occurs it may appear adding the new host was successful though it will not be possible to provision workloads onto it due to not joining the cluster successfully.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json b/corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
new file mode 100644
index 0000000..7f9c54d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+  "title": "Overview",
+  "ordinal": 214,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md b/corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
new file mode 100644
index 0000000..a591a1c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
@@ -0,0 +1,7 @@
+# Overview
+
+Cypher at its core is a secure Key/Value store. But what makes Cypher useful is the ability to securely store or generate credentials to connect to your Instances. Not only are these credentials encrypted but by using Cypher you don’t have to burn in connection credentials between Instances into your apps.
+
+Cypher keys can be revoked, either through lease timeouts or manually. So, even if somebody were to gain access to your keys you could revoke access to the keys and generate new ones for your applications.
+
+Keys can have different behaviors depending on the specified mountpoint.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json b/corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
new file mode 100644
index 0000000..b08fd0a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+  "title": "Instance Status",
+  "ordinal": 11,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Status",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+        "clustering_title": "Instance Status"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+        "clustering_title": "Instance Status"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md b/corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
new file mode 100644
index 0000000..a76f11f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
@@ -0,0 +1,3 @@
+# Instance Status
+
+The total number of Instances is listed along with a pie chart showing the statuses of each. Hover over each section of the pie chart to see the total number and percentage of Instances in that state. States may include running, stopped, provisioning, and more
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json b/corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
new file mode 100644
index 0000000..3043926
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+  "title": "OAuth 2.0 Credentials",
+  "ordinal": 198,
+  "parent_title": "Trust",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.html",
+  "topic_cluster": {
+    "clustering_title": "OAuth 2.0 Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+        "clustering_title": "OAuth 2.0 Credentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+        "clustering_title": "OAuth 2.0 Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md b/corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
new file mode 100644
index 0000000..f6ad8b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
@@ -0,0 +1,26 @@
+# OAuth 2.0 Credentials
+
+VM Essentials supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
+
+To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
+
+- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
+- **NAME:** A name for the credential set in VM Essentials
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **GRANT TYPE:** Client Credentials or Password Credentials
+- **ACCESS TOKEN URL:** The authorization server’s token endpoint
+- **CLIENT ID:** The client ID for an app registered with the target service
+- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
+- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
+- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
+- **SCOPE:** The scope of access requested to the target resource
+- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how VM Essentials should issue the token received in requests to the target resource
+
+Once done, click ADD CREDENTIALS.
+
+**Subtopics**  
+
+- **[Add Existing Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.html)**
+- **[Generate Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.html)**
+- **[Delete Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json b/corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
new file mode 100644
index 0000000..e08742e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+  "title": "Manage Permissions",
+  "ordinal": 193,
+  "parent_title": "Storage",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.html",
+  "topic_cluster": {
+    "clustering_title": "Manage Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+        "clustering_title": "Manage Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+        "clustering_title": "Manage Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md b/corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
new file mode 100644
index 0000000..1ae3770
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
@@ -0,0 +1,13 @@
+# Manage Permissions
+
+From this view, users can manage permissions for any data store synced from integrated Clouds. This includes setting which Groups have access to the data store. To edit data store permissions:
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click ACTIONS > Edit
+- **Groups:** Select “all” Groups or select specific Groups which should have access to the data store
+- **Active:** When marked, the data store is active and available for provisioning
+- Click SAVE CHANGES
+
+**Subtopics**  
+
+- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json b/corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
new file mode 100644
index 0000000..aecb390
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+  "title": "Clouds",
+  "ordinal": 90,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html",
+  "topic_cluster": {
+    "clustering_title": "Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md b/corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
new file mode 100644
index 0000000..f440fa3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
@@ -0,0 +1,8 @@
+# Clouds
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.html)**
+- **[Creating Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.html)**
+- **[Cloud Detail View](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html)**
+- **[Deleting Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json b/corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
new file mode 100644
index 0000000..464d71b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+  "title": "Elevating to HPE Morpheus Enterprise",
+  "ordinal": 4,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.html",
+  "topic_cluster": {
+    "clustering_title": "Elevating to HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+        "clustering_title": "Elevating to HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+        "clustering_title": "Elevating to HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md b/corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
new file mode 100644
index 0000000..b5514e8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
@@ -0,0 +1,109 @@
+# Elevating to HPE Morpheus Enterprise
+
+This section of the guide goes over the process for upgrading a HPE Morpheus VM Essentials Software appliance to a HPE Morpheus Enterprise Software appliance. HPE Morpheus VM Essentials and HPE Morpheus Enterprise are essentially the same product with HPE Morpheus VM Essentials focused specifically on management and consumption of HVM clusters and HPE Morpheus Enterprise adding on support for many other public and private Cloud types with a richer orchestration and automation experience (in addition to all features included with HPE Morpheus VM Essentials). HPE Morpheus Enterprise requires separate licensing, reach out to your account manager if you’re unsure which licensing entitlements you can access. This guide is intended for HPE Morpheus VM Essentials administrators to upgrade their existing appliances and assumes a level of comfort with the Linux command line and the version upgrade process for HPE Morpheus VM Essentials and/or HPE Morpheus Enterprise. After upgrading, refer to HPE Morpheus Enterprise [documentation](https://www.hpe.com/support/morpheus-enterprise-documentation-latest) for use guides to consuming the full HPE Morpheus Enterprise feature set.
+
+## Prerequisites
+
+- HPE Morpheus VM Essentials manager version 8.0.1+
+- A bucket integrated with HPE Morpheus VM Essentials manager which can house an appliance database backup
+- The HPE Morpheus Enterprise upgrade package (version 8.0.4+)
+- A HPE Morpheus Enterprise license to add following the upgrade to enable the full feature set
+
+## Back Up the Appliance
+
+Start by taking a fresh backup of the appliance database. View the appliance backup job by navigating to Backups > Jobs. As in the screenshot, there should be a backup job named “Morpheus Appliance.” If an appliance backup job is not shown, enable the “Backup Appliance” setting within global settings (Administration > Settings > Backups).
+
+![../_images/upgradeCheckBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-983B614F-468D-405F-8143-085388C6B629-high.png)
+
+Click Run Now and wait for a new green checkmark to appear indicating a new run of the backup job was successful.
+
+## Package Installation
+
+Upgrading the HPE Morpheus VM Essentials manager to a HPE Morpheus Enterprise appliance is as simple as installing the HPE Morpheus Enterprise package over the existing HPE Morpheus VM Essentials package in a process very similar to version upgrades you may have done in the past. First, download the HPE Morpheus Enterprise `.deb` package. The download URL shown below is a placeholder, reach out to your account manager if you’re unsure where to find the download URL for the latest package.
+
+```
+```
+wget https://url.to.morpheus-appliance_x.x.x-x.deb
+```
+```
+
+Next, stop the HPE Morpheus VM Essentials UI.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui
+```
+```
+
+Install the HPE Morpheus Enterprise package and force it to overwrite.
+
+```
+```
+dpkg -i --force-overwrite morpheus-appliance_x.x.x-x.deb
+```
+```
+
+Wait for the installation to complete. There will be warnings about conflicts which may be safely ignored. When installation is complete, you will see a message similar to the screenshot below:
+
+![../_images/upgradeFinishInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-967FDDAE-077D-492D-A9E6-27259A79FCCB-high.png)
+
+Now, remove the HPE Morpheus VM Essentials package.
+
+```
+```
+sudo apt-get remove -y hpe-vm-essentials
+```
+```
+
+Following removal, restart any recommended services if prompted.
+
+![../_images/upgradeRemoveVme.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-DCBE5796-22E4-4207-B179-DD8B37BA91EF-high.png)
+
+We must now clean up OpenSearch directories. Currently, HPE Morpheus Enterprise uses ElasticSearch while HPE Morpheus VM Essentials manager uses OpenSearch. Migration through snapshots is not supported due to this incompatibility. In general, OpenSearch and ElasticSearch contain VM performance metrics. This data can be considered ephemeral and safely deleted as the default retention is only 30 days. HPE Morpheus Enterprise is planned to migrate to OpenSearch in the future and at that point, this cleanup step will not be required and metrics will persist across an upgrade to HPE Morpheus Enterprise. Remove the following directories:
+
+```
+```
+rm -rf /var/run/morpheus/opensearch  
+rm -rf /opt/morpheus/service/opensearch
+```
+```
+
+Next, run the reconfigure command. This will configure ElasticSearch for use with the upgraded appliance.
+
+```
+```
+sudo morpheus-ctl reconfigure
+```
+```
+
+Once the reconfigure is complete, make sure all HPE Morpheus Enterprise services are started
+
+```
+```
+sudo morpheus-ctl status
+```
+```
+
+If any services need started, use the following command:
+
+```
+```
+sudo morpheus-ctl start {service name}
+```
+```
+
+You can watch the logs to see when the UI comes back up:
+
+```
+```
+sudo morpheus-ctl tail morpheus-ui
+```
+```
+
+When the Morpheus ASCII logo appears, you should be able to reach the UI from a web browser.
+
+## Upgrading the License
+
+Now that HPE Morpheus Enterprise UI is reachable, the license must be upgraded. Navigate to Administration > Settings > License where you’ll see a field to paste in your license key. Once again, contact your account manager if you have questions on accessing your license key. Finally, make sure you select the appropriate option of either stacking the license onto an existing license or replacing it. Then, click Update.
+
+At this point, the process is complete. Now that the full Morpheus feature set is unlocked, refer to Morpheus [documentation](https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=1014895562&tab=manuals&cep=on) going forward.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json b/corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
new file mode 100644
index 0000000..0e5ca76
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+  "title": "Local Virtual Images",
+  "ordinal": 31,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.html",
+  "topic_cluster": {
+    "clustering_title": "Local Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+        "clustering_title": "Local Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+        "clustering_title": "Local Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md b/corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
new file mode 100644
index 0000000..4188c74
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
@@ -0,0 +1,11 @@
+# Local Virtual Images
+
+A Local Virtual Image means it has been uploaded to VM Essentials. To provision, VM Essentials will need to upload the image to the provisioning target upon first provision.
+
+- Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and VM Essentials has network access and permissions to upload the image.
+
+NOTE
+
+When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+Once a local Virtual Image has been uploaded to a provisioning target, subsequent provisions will use the image local to the target instead of uploading again as long as the copied image is still available.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json b/corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
new file mode 100644
index 0000000..0782aa8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+  "title": "Preferences",
+  "ordinal": 302,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html",
+  "topic_cluster": {
+    "clustering_title": "Preferences",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md b/corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
new file mode 100644
index 0000000..af97647
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
@@ -0,0 +1,8 @@
+# Preferences
+
+- **Default Group:** Sets the default Group selection when provisioning
+- **Default Cloud:** Sets the default Cloud selection when provisioning
+- **Default Persona:** Sets the default Persona used when logging in
+- **Default Locale:** Sets the user’s preferred language and region, this setting will override the global locale for the individual user
+
+![../../_images/user_settings_preferences_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-1FDED76C-74B0-4FCA-A922-28AD152EC59A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json b/corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
new file mode 100644
index 0000000..7c87d66
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+  "title": "Prerequisites",
+  "ordinal": 359,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md b/corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
new file mode 100644
index 0000000..225d649
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
@@ -0,0 +1,24 @@
+# Prerequisites
+
+The following requirements must be met to deploy and configure the HPE Aruba CX DSS Network plugin in VM Essentials
+
+- Aruba CX 10000 series switches
+
+  - At least two Aruba CX 10000 switches are configured
+  - VSX and KeepAlive are configured
+  - Switches are connected to the upstream network
+- Pre-existing HVM cluster
+
+  - Ensure all hosts within the HVM cluster are physically connected to the CX 10000 switches for optimal network integration and redundancy
+- VM Essentials appliance version 8.0.6 or higher
+
+  - AFC and PSM are deployed and reachable from the VM Essentials manager
+- Aruba Fabric Composer (AFC) version 7.2 or higher, deployed as a VM
+- AMD Pensando PSM (Policy and Services Manager), deployed as a VM
+
+NOTE
+
+- Download AFC and PSM from the [HPE Networking Support portal](https://networkingsupport.hpe.com/downloads/software/RmlsZTo0YzQ2MzIyYS0xOTU2LTExZjAtYTMzNS0yZmRkN2QyMjdhOTY%253D)
+- For more information on deploying AFC and PSM, refer to the official documentation
+- The AFC and PSM must have network connectivity to the CX 10000 switches
+- Making full use of the VM Essentials Aruba CX 10000 integration requires credentials for AFC with API access granted and read/write access to AFC configuration
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json b/corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
new file mode 100644
index 0000000..3233a28
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+  "title": "Service Plan Configuration",
+  "ordinal": 243,
+  "parent_title": "Overview",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plan Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+        "clustering_title": "Service Plan Configuration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+        "clustering_title": "Service Plan Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md b/corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
new file mode 100644
index 0000000..03161e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
@@ -0,0 +1,31 @@
+# Service Plan Configuration
+
+NOTE
+
+Not all fields listed below are available for every provision type. After selecting the provision type, the correct fields for that type of Service Plan will be revealed. Not all fields are required to save a valid Service Plan
+
+- **NAME:** The name of the Service Plan in VM Essentials
+- **ACTIVE:** Inactive Service Plans are not available for selection during provisioning or reconfigure. New discovered records cannot be associated with deactivated Plans when converting to managed resources. Any resources attached to a Plan will continue to be associated if the Plan is later deactivated
+- **CODE:** A unique identifier for use in VM Essentials API and CLI
+- **DISPLAY ORDER:** Configures the order in which plans are displayed relative to other plans associated with the same provision type. Note that Plans will be displayed in low-to-high order based on the Display Order property. This is reversed from Layouts which are displayed in high-to-low order
+- **PROVISION TYPE:** Determines the resource Provision Type this Service Plan is available for when provisioning, reconfiguring and converting discovered resources to managed
+- **REGION CODE:** (Optional) Limits availability of the Service Plan to Clouds with the specified Region Code
+- **STORAGE:** The default storage size of the root volume (in MB or GB)
+- **CUSTOMIZE ROOT VOLUME:** Allows the root volume size to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CUSTOMIZE EXTRA VOLUMES:** Allows the extra volume sizes to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **ADD VOLUMES:** Allows additional volumes to be added during provisioning or reconfigure
+- **MEMORY:** The amount of memory included with the plan (in MB or GB)
+- **CUSTOM MEMORY:** Allows the amount of memory to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORE COUNT:** The number of virtual CPU cores included with the plan
+- **CUSTOM CORES:** Allows the number of virtual CPU cores to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORES PER SOCKET:** Determines core distribution across sockets. CORES PER SOCKET cannot be larger than CORE COUNT, and CORE COUNT must be divisible by CORES PER SOCKET. For example four CORES with two CORES PER SOCKET means two sockets would have two cores each assigned. Four CORES with one CORE PER SOCKET would have four sockets with one core each assigned, and four CORES with four CORES PER SOCKET would have one socket with four cores assigned
+- **TOTAL STORAGE:** When custom storage is enabled for the plan, this sets a minimum and maximum total storage allowed (all disks combined)
+- **PER DISK SIZE:** When custom storage is enabled for the plan, this sets the minimum and maximum storage for each disk
+- **CUSTOM MEMORY RANGE:** The minimum and maximum allowed amount of memory for the Plan when CUSTOM MEMORY is enabled for the Plan
+- **CUSTOM CORES RANGE:** The minimum and maximum allowed amount of virtual CPU cores for the Plan when CUSTOM CORES is enabled for the Plan
+- **SOCKETS:** The minimum and maximum allowed sockets range for the Plan when CUSTOM CORES is enabled for the Plan
+- **CORES PER SOCKET:** The minimum and maximum allowed cores per socket for the Plan when CUSTOM CORES is enabled for the Plan
+
+TIP
+
+Custom Range storage and memory values units (GB/MB) are inherited from the :STORAGE:: and :MEMORY:: GB/MB settings in the same Plan. For example, if :STORAGE: is configured for for 40 GB, a custom range for Storage would also be in GB.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json b/corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
new file mode 100644
index 0000000..d69b0e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+  "title": "Windows Settings",
+  "ordinal": 304,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md b/corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
new file mode 100644
index 0000000..9e1ea48
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
@@ -0,0 +1,13 @@
+# Windows Settings
+
+When provisioning a Windows-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Windows accounts
+- **Password:** The password that will be used with your Windows accounts
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+
+WARNING
+
+If your users Windows Settings password is not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_windows_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4558D828-A24E-42F3-8ACD-F5E4ACCD556C-high.png)
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json b/corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
new file mode 100644
index 0000000..7954497
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+  "title": "Features",
+  "ordinal": 350,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md b/corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
new file mode 100644
index 0000000..52c9abf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
@@ -0,0 +1,3 @@
+# Features
+
+- Network - Create or Delete OVS Port Group.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json b/corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
new file mode 100644
index 0000000..c5b3b82
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+  "title": "Prepare The New CentOS 8/RHEL8 Image",
+  "ordinal": 340,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.html",
+  "topic_cluster": {
+    "clustering_title": "Prepare The New CentOS 8/RHEL8 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+        "clustering_title": "Prepare The New CentOS 8/RHEL8 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+        "clustering_title": "Prepare The New CentOS 8/RHEL8 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md b/corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
new file mode 100644
index 0000000..9bfd361
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
@@ -0,0 +1,8 @@
+# Prepare The New CentOS 8/RHEL8 Image
+
+## Procedure
+
+1. Install epel-release: `yum -y install epel-release` (This step is not necessary for RHEL)
+2. Install git, wget, curl, cloud-init, cloud-utils-gropart, and open-vm-tools: `yum -y install git wget curl cloud-init cloud-utils-growpart open-vm-tools`
+3. Update: `yum -y update`
+4. Finally run: `rpm -qa kernel | sed 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}`
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json b/corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
new file mode 100644
index 0000000..390524c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+  "title": "Packages",
+  "ordinal": 258,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.html",
+  "topic_cluster": {
+    "clustering_title": "Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+        "clustering_title": "Packages"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+        "clustering_title": "Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md b/corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
new file mode 100644
index 0000000..94cc0ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
@@ -0,0 +1,29 @@
+# Packages
+
+## About this task
+
+Packages define reusable HPE Morpheus Essentials resources that you can upload and use across appliances. The platform supports package files in `.morpkg`, `.mpkg`, or `.mopkg` format.
+
+HPE Morpheus Essentials supports task object. Whereas Morpheus Enterprise supports automation objects, such as:
+
+- Instance Types
+- Layouts
+- Node Types
+- Tasks
+- Spec Templates
+- Cluster layouts
+
+Perform the following to upload a package:
+
+## Procedure
+
+1. Navigate to Administration > Integrations.
+2. Click Packages tab.
+3. Navigate to Package Upload section.
+4. Click Choose File.
+5. Select the required package.
+6. Click Upload.
+
+## Results
+
+The system extracts the package and populates the Library with the contained resources. The package appears in the list with its installation status.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json b/corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
new file mode 100644
index 0000000..00b7f55
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+  "title": "Twilio SMS Settings",
+  "ordinal": 270,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.html",
+  "topic_cluster": {
+    "clustering_title": "Twilio SMS Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+        "clustering_title": "Twilio SMS Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+        "clustering_title": "Twilio SMS Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md b/corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
new file mode 100644
index 0000000..a3d77d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
@@ -0,0 +1,7 @@
+# Twilio SMS Settings
+
+Configure SMS text message delivery for VM Essentials alerts. Previously, customers could use VM Essentials’ own account for delivery, but for security reasons clients must now supply their own. Complete the fields indicated below and then restart all VM Essentials nodes to apply the changes.
+
+- **Account SID:** Twilio Account SID
+- **SMS From #:** The “From” number to receive the text message from
+- **Auth Token:** The Twilio API authentication token for your account
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json b/corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
new file mode 100644
index 0000000..46fa00a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+  "title": "Edit Group",
+  "ordinal": 87,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.html",
+  "topic_cluster": {
+    "clustering_title": "Edit Group",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+        "clustering_title": "Edit Group"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+        "clustering_title": "Edit Group"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md b/corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
new file mode 100644
index 0000000..583d1cd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
@@ -0,0 +1,14 @@
+# Edit Group
+
+## About this task
+
+To edit a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to edit.
+4. Click the Edit button.
+5. From the Edit Group Wizard modify information as needed.
+6. Click the Save Changes button to save.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json b/corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
new file mode 100644
index 0000000..264e945
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+  "title": "Edit User",
+  "ordinal": 254,
+  "parent_title": "Users",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.html",
+  "topic_cluster": {
+    "clustering_title": "Edit User",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+        "clustering_title": "Edit User"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+        "clustering_title": "Edit User"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md b/corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
new file mode 100644
index 0000000..418e2a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
@@ -0,0 +1,18 @@
+# Edit User
+
+## About this task
+
+User settings can be edited from Administration > Users.
+
+NOTE
+
+Some User data from Users created via an Identity Source Integration such as Active Directory is not editable in VM Essentials, as it is synced with the Identity Source.
+
+To edit a User from the Administration > Users Section:
+
+## Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Click the edit (pencil) icon from within the row of the selected User
+4. Make changes and select SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json b/corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
new file mode 100644
index 0000000..8617a1c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+  "title": "Guest Console SSH Tunnel",
+  "ordinal": 145,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.html",
+  "topic_cluster": {
+    "clustering_title": "Guest Console SSH Tunnel",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+        "clustering_title": "Guest Console SSH Tunnel"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+        "clustering_title": "Guest Console SSH Tunnel"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md b/corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
new file mode 100644
index 0000000..e955611
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
@@ -0,0 +1,18 @@
+# Guest Console SSH Tunnel
+
+In some scenarios, Instances that are segregated from the VM Essentials appliance by port restrictions, or other mechanisms, can cause difficulties to access the guest console via the VM Essentials web UI. Guest Console SSH Tunnel settings allow the administrator to configure a jump host’s settings that is dual-homed, accessible by VM Essentials but also resides on the segregated network. When the guest console is configured with the SSH protocol, the traffic will be routed to the jump host, which will then relay to the target instance.
+
+GUEST CONSOLE JUMP HOST
+:   DNS hostname or IP of the jump host to relay the traffic
+
+GUEST CONSOLE JUMP PORT
+:   Port override, if different than 22 for SSH
+
+GUEST CONSOLE JUMP USERNAME
+:   Username used to authenticate to the jump host
+
+GUEST CONSOLE JUMP PASSWORD
+:   Password that is used with the username to autenticate to the jump host
+
+GUEST CONSOLE KEYPAIR
+:   Keypair saved in VM Essentials to be used in lieu of, or in addition to, the password to the jump host, which is associated with the configured username Keypairs can be imported at: Infrastructure > Trust > Key Pairs
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json b/corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
new file mode 100644
index 0000000..6ac1a50
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+  "title": "Cloud Detail Tabs",
+  "ordinal": 94,
+  "parent_title": "Cloud Detail View",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Detail Tabs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+        "clustering_title": "Cloud Detail Tabs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+        "clustering_title": "Cloud Detail Tabs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md b/corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
new file mode 100644
index 0000000..39c0ec9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
@@ -0,0 +1,29 @@
+# Cloud Detail Tabs
+
+NOTE
+
+Not all tabs are available for all Cloud Types.
+
+Clusters
+:   The Clusters tab displays clusters provisioned into the Cloud being viewed, including their status, type, name, layout, workers, and compute, memory, and storage stats. You can add a cluster by clicking ADD CLUSTER.
+
+Hosts
+:   The Hosts tab displays available hosts in the Cloud and displays power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status. You can add a resource by clicking ADD RESOURCE, add a hypervisor host by clicking ADD HYPERVISOR, or perform action an action by selecting one or more Hosts and clicking ACTIONS.
+
+    VMs
+    :   Displays an inventory of existing Instances in your Cloud configuration and provides details such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Bare Metal
+:   Setup PXE Boot in the Boot section to add bare metal servers. Once set up you can view information such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Security Groups
+:   The Security Groups tab displays a list of existing security groups in the cloud. You can add a security group to this cloud by clicking EDIT SECURITY GROUPS.
+
+Networks
+:   Displays Networks synced or added to the Cloud, including their name, type, CIDR, pool, DHCP status, visibility and targeted Tenant.
+
+Data Stores
+:   Displays Datastores synced or added to the Cloud, including their name, type, capacity, online status, visibility, and targeted Tenant.
+
+Resources
+:   Displays Resource Pools synced from the Cloud, including their name, description, and targeted Tenant.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json b/corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
new file mode 100644
index 0000000..f06785b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+  "title": "Creating Cypher Keys",
+  "ordinal": 216,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Cypher Keys",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+        "clustering_title": "Creating Cypher Keys"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+        "clustering_title": "Creating Cypher Keys"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md b/corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
new file mode 100644
index 0000000..60553b6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
@@ -0,0 +1,6 @@
+# Creating Cypher Keys
+
+## Procedure
+
+1. Navigate to Tools > Cypher and select + ADD
+2. Configure one of the following types of Keys:
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json b/corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
new file mode 100644
index 0000000..3860af1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+  "title": "Add Virtual Image",
+  "ordinal": 77,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.html",
+  "topic_cluster": {
+    "clustering_title": "Add Virtual Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+        "clustering_title": "Add Virtual Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+        "clustering_title": "Add Virtual Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md b/corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
new file mode 100644
index 0000000..516c0bc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
@@ -0,0 +1,108 @@
+# Add Virtual Image
+
+## About this task
+
+Virtual Images can be uploaded to VM Essentials from local files or URLs.
+
+WARNING
+
+Be conscious of your Storage Provider selection. The default Storage Provider is the VM Essentials Appliance at `/var/opt/morpheus/morpheus-ui/vms`. Uploading large images to the VM Essentials Appliance when there is inadequate space will cause upload failures and impact Appliance functionality. Ensure there is adequate space on your selected Storage Provider. Additional Storage Provider can be added at Infrastructure  >  Storage, which can be configured as the default Virtual Image Store or selected when uploading Images.
+
+NOTE
+
+VMware-type OVF Virtual Images do not support mounted ISO uploads
+
+To Add Virtual Image:
+
+## Procedure
+
+1. Select + Add in the Virtual Images page.
+2. Select Image format: 
+
+   - ISO
+   - QCOW2
+   - RAW
+   - VMware (vmdk/ovf/ova)
+3. Configure the following on the Virtual Image: 
+
+   Name
+   :   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant VM Essentials environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, VM Essentials will install the FIPS-compliant VM Essentials Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to VMware vCenter Clouds. Enable if the Windows Image has been sysprepped. If enabled, VM Essentials will inject `unattend.xml`
+
+   NOTE
+
+   Default Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage. Ensure local folders are owned by morpheus-app.morpheus-app if used.
+
+   WARNING
+
+   Provisioning will fail if Cloud init Enabled is checked and Cloud-Init is not installed on the Image.
+
+   NOTE
+
+   Existing Image credentials are required for Linux Images that are not Cloud-Init enabled and for Windows Images when Guest Customizations are not used. Cloud-Init and Windows user settings need to be configured in Administration > Settings > Provisioning when using Cloud-Init or Guest Customizations and new credentials are not set on the Virtual Image.
+4. Upload Image
+   :   Images can be uploaded by File or URL:
+       :   File
+           :   Drag and Drop the image file, or select Add File to select the image file.
+
+           Url
+           :   Select the URL radio button, and enter URL of the Image.
+
+       NOTE
+
+       The Virtual Image configuration can be saved when using a URL and the upload will finish in the background. When selecting/drag and dropping a file, the image files must upload completely before saving the Virtual Image record or the Image will not be valid.
+5. Save Changes.
+
+**Subtopics**  
+
+- **[VMware - VM Templates Copies](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json b/corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
new file mode 100644
index 0000000..179f2db
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+  "title": "Virtual Images",
+  "ordinal": 29,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md b/corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
new file mode 100644
index 0000000..b5dc14d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
@@ -0,0 +1,14 @@
+# Virtual Images
+
+The most common provisioning method within VM Essentials involves Virtual Machines, and the most important part of provisioning a VM is the Virtual Image. When provisioning a VM, VM Essentials will need to do a few things depending on the location of the Virtual Image and if agent install and console access are desired.
+
+Synced Images need to be properly configured
+:   VM Essentials gathers as much metadata for synced images as possible, but depending on the target (HVM cluster or VMware vCenter), OS, image configuration, or agent install settings, the synced Virtual Images may not be ready to provision without some configuration within VM Essentials. The Virtual Image is already at the target Cloud, but datastore selection, credentials, cloud-init settings, networks, and security settings on the Virtual Image can cause provisioning issues.
+
+Local/Uploaded Virtual Images
+:   Images uploaded to VM Essentials are configured during the Add Virtual Image process, however VM Essentials in most scenarios will still need to copy the Virtual Image to the target Hypervisor/Cloud upon the first provision to the target Cloud. In addition to the requirements for provisioning a synced Virtual Image, copying an uploaded Virtual Image to the target Cloud is required. Network and image configurations can cause upload failures, resulting in provisioning issues.
+
+**Subtopics**  
+
+- **[Synced Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.html)**
+- **[Local Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json b/corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
new file mode 100644
index 0000000..4f42c06
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+  "title": "Library Settings",
+  "ordinal": 280,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.html",
+  "topic_cluster": {
+    "clustering_title": "Library Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+        "clustering_title": "Library Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+        "clustering_title": "Library Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md b/corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
new file mode 100644
index 0000000..54e1ae9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
@@ -0,0 +1,8 @@
+# Library Settings
+
+In this section, enable or disable access globally to provisioning sections of Catalog (self-service shopping cart provisioning), Apps (apps deployed from configured App Blueprints), and Instances
+
+- Enable Catalog
+- Enable Apps
+- Enable Instances
+- Provisioning Order: Sets the order for Instances, Apps, and Catalog to appear in the Provisioning menu
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json b/corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
new file mode 100644
index 0000000..633d3b6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+  "title": "Create Service Plan",
+  "ordinal": 241,
+  "parent_title": "Overview",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.html",
+  "topic_cluster": {
+    "clustering_title": "Create Service Plan",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+        "clustering_title": "Create Service Plan"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+        "clustering_title": "Create Service Plan"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md b/corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
new file mode 100644
index 0000000..7c6ac10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
@@ -0,0 +1,12 @@
+# Create Service Plan
+
+## About this task
+
+Perform the following to create a service plan:
+
+## Procedure
+
+1. Navigate to Administration > Plans (`/admin/service-plans`)
+2. Click the + ADD dropdown and select the appropriate Plan type
+3. Configure details for the Plan on the General tab, the configuration options will depend on the Plan type. See the section above for a detailed description of each configuration option available for Service Plans
+4. Click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json b/corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
new file mode 100644
index 0000000..8a60256
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+  "title": "Secret",
+  "ordinal": 219,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.html",
+  "topic_cluster": {
+    "clustering_title": "Secret",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+        "clustering_title": "Secret"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+        "clustering_title": "Secret"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md b/corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
new file mode 100644
index 0000000..6a1e555
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
@@ -0,0 +1,20 @@
+# Secret
+
+A Cypher secret is the standard secret module that stores a key/value in encrypted form.
+
+Key
+:   Pattern “secret/key”
+
+    - EXAMPLE: secret/mysecret
+
+Value
+:   Add the secret value to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the secret will be encrypted and available for use.
+
+If your VM Essentials user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the secret.
+
+To delete the secret, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json b/corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
new file mode 100644
index 0000000..8585aa7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+  "title": "Hosting Images",
+  "ordinal": 19,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.html",
+  "topic_cluster": {
+    "clustering_title": "Hosting Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+        "clustering_title": "Hosting Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+        "clustering_title": "Hosting Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md b/corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
new file mode 100644
index 0000000..2cb96fa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
@@ -0,0 +1,11 @@
+# Hosting Images
+
+It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the VM Essentials appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
+
+```
+```
+![my alt text](https://myimage.com/image.jpg)
+```
+```
+
+The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The VM Essentials [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the VM Essentials appliance local storage. VM Essentials generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in VM Essentials Archives within your Wiki pages.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json b/corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
new file mode 100644
index 0000000..f428bb5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+  "title": "Creating a CentOS/RHEL 7 Image",
+  "ordinal": 336,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a CentOS/RHEL 7 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+        "clustering_title": "Creating a CentOS/RHEL 7 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+        "clustering_title": "Creating a CentOS/RHEL 7 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md b/corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
new file mode 100644
index 0000000..acb2520
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
@@ -0,0 +1,21 @@
+# Creating a CentOS/RHEL 7 Image
+
+## About this task
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+## Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install open-vm-tools using command `yum install open-vm-tools`
+6. Install git by running `yum install git`
+7. Install epel-release repo using command `yum install epel-release`
+8. selinux set to permissive (enforced can cause problems with cloud-init) `sudo vi /etc/selinux/config`
+
+**Subtopics**  
+
+- **[Cloud-Init](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.html)**
+- **[Network Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json b/corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
new file mode 100644
index 0000000..ecabfba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+  "title": "Appliance",
+  "ordinal": 265,
+  "parent_title": "Settings",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md b/corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
new file mode 100644
index 0000000..dd40ea2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
@@ -0,0 +1,14 @@
+# Appliance
+
+**Subtopics**  
+
+- **[Appliance Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html)**
+- **[Tenant Management Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.html)**
+- **[User Management Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.html)**
+- **[Email Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.html)**
+- **[Twilio SMS Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.html)**
+- **[Proxy Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.html)**
+- **[Currency Settings](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html)**
+- **[Integrating With a Currency Exchange Provider](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-AC461BBD-647D-447D-9307-218A41CE368B.html)**
+- **[Consuming Currency Exchange in VM Essentials](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.html)**
+- **[Enabled Clouds (Types)](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/render?page=GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.html)**
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json b/corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
new file mode 100644
index 0000000..e4d6dcc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+  "title": "Actions",
+  "ordinal": 48,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.html",
+  "topic_cluster": {
+    "clustering_title": "Actions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+        "clustering_title": "Actions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+        "clustering_title": "Actions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md b/corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
new file mode 100644
index 0000000..d3dc184
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
@@ -0,0 +1,43 @@
+# Actions
+
+Available options in the Actions dropdown can include:
+
+Suspend
+:   Puts the VM in a suspended state without shutting down the OS.
+
+Stop/Start/Restart Server
+:   Stops, Starts or Restarts the Virtual Machine.
+
+Import as Image
+:   Clones and exports VM in its current state to target Storage provider and adds a Virtual Image record with metadata matching the source Instance configuration.
+
+Clone to Image
+:   Clones and converts VM in its current state to image in the source Cloud and adds a Virtual Image record with metadata matching the source Instance configuration.
+
+Lock/Unlock Instance
+:   A locked Instance cannot be deleted until it is unlocked.
+
+Reconfigure
+:   The Reconfigure action allows service plan, disk, CPU, memory, networks and storage controller changes. Available options depend on the type and Plan configuration. Some resize actions require an Instance restart.
+
+Clone
+:   Creates a new Instance from the Instance at its current state.
+
+Backup
+:   Immediately executes a backup of the Instance. This is only available for Instances with backups enabled.
+
+Run Task
+:   Select a currently-configured Task to run against the Instance. Tasks can be created and edited in Library > Automation.
+
+Add Node
+:   Adds an additional node to the configuration. Additional options and configurations are required in the add node wizard depending on Instance configuration and type.
+
+Eject Disk
+:   Ejects attached disks (ISOs).
+
+Clone to Template (VMware)
+:   Creates a new VMware Template from the Instance with corresponding VM Essentials Virtual Image record.
+
+TIP
+
+Scrolling down in the Actions dropdown may be necessary to see all options.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json b/corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
new file mode 100644
index 0000000..35bbd54
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+  "title": "Image Prep (Windows)",
+  "ordinal": 131,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html",
+  "topic_cluster": {
+    "clustering_title": "Image Prep (Windows)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+        "clustering_title": "Image Prep (Windows)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+        "clustering_title": "Image Prep (Windows)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md b/corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
new file mode 100644
index 0000000..604f266
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
@@ -0,0 +1,94 @@
+# Image Prep (Windows)
+
+This section will go through the steps to prepare a Windows image which can be successfully provisioned to HVM clusters. Additionally, this image can serve as a template from which additional images and VM Essentials Library items can be built. In this example case, we’ll start from downloading a Windows Server 2019 ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
+
+With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+
+- **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2019 ISO”
+- **OPERATING SYSTEM:** “windows server 2019”
+- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+
+In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+
+With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large dropzone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled “Add File” and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES.
+
+![../../_images/progress.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-984BC461-04D2-4759-9E91-D9ACF2C6EB23-high.png)
+
+Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+
+On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+
+On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+
+As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+![../../_images/configTabBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+
+The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+
+Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+
+Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then “Open Console.” This will open a new window with a console session into the VM.
+
+![../../_images/initialConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+
+After selecting the language, click “Next.” On the following screen, click “Install Now.” This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click “Next.”
+
+![../../_images/chooseOs.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+
+Accept the licensing terms and click “Next.”
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+
+On the next screen, choose a custom install.
+
+![../../_images/clickInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+
+The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+![../../_images/selectVirtioPackage.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+
+After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+![../../_images/selectDisk.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+
+Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+![../../_images/windowsExp.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+
+Step through the installer. Simply click “Next” or “Install” through each step, there are no configuration changes needed. Once the installer has completed, click “Finish.” You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+![../../_images/showInterface.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+
+We can now eject the two virtual disks, drives D: and E: in my case. Then, launch Windows Security so we can disable firewalls. Turn off firewall for domain, private network, and public network.
+
+![../../_images/winDefender.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-DAA8652B-17E0-4AF2-9273-C548F0FA0614-high.png)
+
+Next, back in Command Prompt, run `winrm quickconfig` to configure `winrm`. Within `Services`, ensure that `winrm` (Windows Remote Management) is set to automatic on startup. Right-click on the Start button and select Run. Enter “sysprep” and click OK. In the Windows Explorer window that appears, right-click on `sysprep` and click “Run as Administrator”. Under “Shutdown Options”, choose Quit and click OK. If this is set to shutdown, VM Essentials will simply restart the VM. Once this is completed, a new file `Sysprep_succeeded.tag` appears in Windows Explorer.
+
+![../../_images/sysprepComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007620en_us/GUID-A11613FB-FC10-42BC-A6A3-3FB44D08260B-high.png)
+
+We’re now done configuring Windows and the console window can be closed. We’ll move on to creating a template from the VM we just configured. Begin by opening an SSH session into the VM Essentials appliance server. Confirm `jq` is up to date on the appliance box (`apt install jq`). Then, go ahead and stop the running Windows VM. We can do this from the Instance detail page in VM Essentials. Click ACTIONS and then “Stop Server.” Still on the Instance detail page, click ACTIONS and then “Import as Image.” This will perform a snapshot and create a new Virtual Image (Library > Virtual Images).
+
+The Virtual Image is not usable until it’s in an active status and the UI indication may display an active status even before it’s fully ready. If it’s “SAVING” or “QUEUED,” it is still being prepared and saved. To determine the current status of the Virtual Image, check with a call to VM Essentials API like the one below. When the return output lists a status of “Active,” the image is ready to be provisioned from.
+
+```
+```
+curl -k --request GET --url https://xx.xx.xx.xx/api/virtual-images/<id>  
+--header 'accept: application/json' --header 'authorization: Bearer xxx-xxx-xxx-xxx-xxx' |  
+jq '.virtualImage.status'
+```
+```
+
+Once saved, additional configurations are needed on the Virtual Image in VM Essentials. Edit the new Virtual Image and check the following configurations:
+
+- **MINIMUM MEMORY:** Set as appropriate
+- **SYSPREPPED/GENERALIZED IMAGE?:** Checked
+- **INSTALL AGENT?:** Checked
+- **USERNAME:** Remove if present
+- **PASSWORD:** Remove if present
+- **VIRTIO DRIVERS LOADED?:** Checked
+
+All other checkbox-type configurations not mentioned in the above list should be unchecked. Click SAVE CHANGES.
+
+At this point all image preparation steps are completed. Repeat the process of provisioning an HVM Instance Type selecting the new image in the future when needed.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json b/corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
new file mode 100644
index 0000000..e25493d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+  "title": "Execution Schedules",
+  "ordinal": 207,
+  "parent_title": "Initial Backups Setup",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.html",
+  "topic_cluster": {
+    "clustering_title": "Execution Schedules",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+        "clustering_title": "Execution Schedules"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+        "clustering_title": "Execution Schedules"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md b/corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
new file mode 100644
index 0000000..e923e44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
@@ -0,0 +1,3 @@
+# Execution Schedules
+
+Backup Execution Schedules can be configured and managed in Library > Automation > Execute Scheduling. An execution schedule stores only the interval at which some execution should be run and they can apply to both backups and automation scripts. To create a new backup job with this schedule, navigate to Backups  >  Backups and click “+ADD”. In the final step of creating the backup job we are able to select any of our created execution schedules. The Default Backup Schedule set in Administration > Settings > Backups will be selected when creating a backup job and not specifying an execution schedule.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json b/corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
new file mode 100644
index 0000000..31169b8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+  "title": "Environment",
+  "ordinal": 7,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.html",
+  "topic_cluster": {
+    "clustering_title": "Environment",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+        "clustering_title": "Environment"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+        "clustering_title": "Environment"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md b/corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
new file mode 100644
index 0000000..7ec85ea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
@@ -0,0 +1,8 @@
+# Environment
+
+- **Groups:** Total number of Groups currently created
+- **Clouds:** Total number of Clouds currently integrated
+- **Clusters:** Total number of clusters currently provisioned
+- **Apps:** Total number of Apps currently provisioned
+- **Instances:** Total number of Instances currently provisioned
+- **Users:** Total number of VM Essentials user accounts
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json b/corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
new file mode 100644
index 0000000..dca1d65
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+  "title": "Cloud Communication",
+  "ordinal": 169,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Communication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+        "clustering_title": "Cloud Communication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+        "clustering_title": "Cloud Communication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md b/corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
new file mode 100644
index 0000000..b70bd48
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
@@ -0,0 +1,3 @@
+# Cloud Communication
+
+When morpheus needs to connect to various cloud APIs to issue provisioning commands or to sync in existing environments, we need to ensure that those api endpoints are accessible by the appliance. In some cases the appliance may be behind a proxy when it comes to public cloud access like Azure and AWS. To configure the cloud integration to utilize a proxy, when adding or editing a cloud there is a setting called “API Proxy” under “Advanced Options”. This is where the proxy of choice can be selected to instruct the Provisioning engine how to communicate with the public cloud. Simply adjust this setting and the cloud should start being able to receive/issue instructions.
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json b/corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
new file mode 100644
index 0000000..2bc55ae
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+  "title": "Adding Groups",
+  "ordinal": 85,
+  "parent_title": "Groups",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+        "clustering_title": "Adding Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+        "clustering_title": "Adding Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md b/corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
new file mode 100644
index 0000000..7cb5270
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
@@ -0,0 +1,13 @@
+# Adding Groups
+
+## About this task
+
+To add a group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Create Group button
+4. Input out the Name and Location (optional) fields
+5. Click the Save Changes button to save
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json b/corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
new file mode 100644
index 0000000..c4c19d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_1",
+  "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+  "title": "Highlights",
+  "ordinal": 17,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007620en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007620en_us&page=GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.html",
+  "topic_cluster": {
+    "clustering_title": "Highlights",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+        "clustering_title": "Highlights"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_2",
+        "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+        "clustering_title": "Highlights"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md b/corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
new file mode 100644
index 0000000..89866df
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_1/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
@@ -0,0 +1,13 @@
+# Highlights
+
+- Main Wiki section is at Operations > Wiki
+- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, and Clusters detail pages
+- Additional Wiki Pages and Categories can be created from Operations > Wiki
+- When a Wiki tab is populated, a Page is automatically added and accessible at Operations > Wiki
+- The Wiki is accessible from the UI, CLI and API.
+- Wiki access is RBAC-controlled via the Operations: Wiki permission in Roles (None, Read and Full)
+- Page updates are stamped with the “Last Updated By” user and the time the edit was made
+- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
+- All wiki pages are encrypted using AES 256-bit encryption
+- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
+- Create a new page with title “Home” to replace the default Wiki landing page that ships with VM Essentials
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json b/corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
new file mode 100644
index 0000000..98b3b78
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+  "title": "Global Backups Settings",
+  "ordinal": 206,
+  "parent_title": "Initial Backups Setup",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html",
+  "topic_cluster": {
+    "clustering_title": "Global Backups Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+        "clustering_title": "Global Backups Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-008AF6CD-E219-4D76-B175-B763E5C397CE",
+        "clustering_title": "Global Backups Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md b/corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
new file mode 100644
index 0000000..d93a136
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.md
@@ -0,0 +1,27 @@
+# Global Backups Settings
+
+VM Essentials Backups can be enabled under Administration > Settings > Backups.
+
+Scheduled Backups
+:   When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
+
+Create Backups
+:   When enabled, VM Essentials will automatically configure backup jobs for Instances at provision time.
+
+Backup Appliance
+:   When enabled, a Backup will be created to backup the VM Essentials appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
+
+Default Backup Bucket
+:   From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
+
+Default Backup Schedule
+:   From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+Backup Retention Count
+:   The default maximum number of successful backups to retain.
+
+Default Synthetic Full Backup Enabled
+:   When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
+
+Default Synthetic Full Backups Schedule
+:   From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json b/corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
new file mode 100644
index 0000000..990efc4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+  "title": "Scoping Services",
+  "ordinal": 173,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html",
+  "topic_cluster": {
+    "clustering_title": "Scoping Services",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+        "clustering_title": "Scoping Services"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-02679208-A796-4A58-80AC-33DCF6A4899F",
+        "clustering_title": "Scoping Services"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md b/corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
new file mode 100644
index 0000000..8b76936
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-02679208-A796-4A58-80AC-33DCF6A4899F.md
@@ -0,0 +1,20 @@
+# Scoping Services
+
+NETWORKING
+:   Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
+
+IPAM
+:   IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
+
+SECURITY
+:   Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
+
+DNS
+:   DNS integrations will populate domains in the Infrastructure  >  Network  >  Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+Service Registry
+:   Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+NOTE
+
+Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json b/corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
new file mode 100644
index 0000000..00ab44a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+  "title": "Group and Tenant Access",
+  "ordinal": 144,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html",
+  "topic_cluster": {
+    "clustering_title": "Group and Tenant Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+        "clustering_title": "Group and Tenant Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C",
+        "clustering_title": "Group and Tenant Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md b/corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
new file mode 100644
index 0000000..37ab560
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.md
@@ -0,0 +1,3 @@
+# Group and Tenant Access
+
+Networks can be configured to provide specific Group access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json b/corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
new file mode 100644
index 0000000..635794f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+  "title": "Cloud-Init Agent install mode",
+  "ordinal": 39,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init Agent install mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+        "clustering_title": "Cloud-Init Agent install mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522",
+        "clustering_title": "Cloud-Init Agent install mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md b/corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
new file mode 100644
index 0000000..28af5bf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.md
@@ -0,0 +1,4 @@
+# Cloud-Init Agent install mode
+
+- Cloud-Init is configured in Administration > Settings > Provisioning section
+- Provisioned image has Cloud-Init (Linux) or Cloudbase-Init (Windows) installed
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json b/corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
new file mode 100644
index 0000000..c5b6f90
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+  "title": "Activity",
+  "ordinal": 20,
+  "parent_title": "Operations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0503F050-177F-4360-9B1A-49439AF366B8",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md b/corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
new file mode 100644
index 0000000..4aa8af0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0503F050-177F-4360-9B1A-49439AF366B8.md
@@ -0,0 +1,11 @@
+# Activity
+
+The Activity section displays a recent activity report for Auditing. VM Essentials defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, etc… This view can be searched and filtered by type, user, and date range.
+
+![Activity page](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-01147D13-F369-4441-B97D-9354DA79DF93-high.png)
+
+**Subtopics**  
+
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html)**
+- **[Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html)**
+- **[History](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.json b/corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
new file mode 100644
index 0000000..578fd4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+  "title": "Add ArubaCX Integration to a Cluster",
+  "ordinal": 355,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html",
+  "topic_cluster": {
+    "clustering_title": "Add ArubaCX Integration to a Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+        "clustering_title": "Add ArubaCX Integration to a Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-054A7DC4-C03C-4356-8486-19472075129E",
+        "clustering_title": "Add ArubaCX Integration to a Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.md b/corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
new file mode 100644
index 0000000..f6f20e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-054A7DC4-C03C-4356-8486-19472075129E.md
@@ -0,0 +1,10 @@
+# Add ArubaCX Integration to a Cluster
+
+## Procedure
+
+1. In Infrastructure > Clusters select the target Cluster
+2. Select the Edit icon for the Cluster
+3. In the “Integrations” dropdown, select an available ArubaCX Integration
+4. Save Changes 
+
+   ![../../_images/arubacx_edit_cluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-6978CDB6-74D2-492A-B461-2F0EC476F018-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.json b/corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.json
new file mode 100644
index 0000000..0878f65
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+  "title": "Group Access",
+  "ordinal": 161,
+  "parent_title": "Editing Domain Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-06426E05-BE70-4917-89E3-153236303513.html",
+  "topic_cluster": {
+    "clustering_title": "Group Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+        "clustering_title": "Group Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-06426E05-BE70-4917-89E3-153236303513",
+        "clustering_title": "Group Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.md b/corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.md
new file mode 100644
index 0000000..4659567
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-06426E05-BE70-4917-89E3-153236303513.md
@@ -0,0 +1,3 @@
+# Group Access
+
+The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json b/corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
new file mode 100644
index 0000000..25fb8ad
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+  "title": "Currency Settings",
+  "ordinal": 272,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html",
+  "topic_cluster": {
+    "clustering_title": "Currency Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+        "clustering_title": "Currency Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776",
+        "clustering_title": "Currency Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md b/corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
new file mode 100644
index 0000000..44fd21e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.md
@@ -0,0 +1,3 @@
+# Currency Settings
+
+In VM Essentials, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, VM Essentials allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json b/corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
new file mode 100644
index 0000000..fe59c96
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+  "title": "NFSv3 File Shares",
+  "ordinal": 190,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html",
+  "topic_cluster": {
+    "clustering_title": "NFSv3 File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+        "clustering_title": "NFSv3 File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-07778212-ECE2-41DC-A130-1A6271833CA4",
+        "clustering_title": "NFSv3 File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md b/corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
new file mode 100644
index 0000000..7a77b90
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-07778212-ECE2-41DC-A130-1A6271833CA4.md
@@ -0,0 +1,80 @@
+# NFSv3 File Shares
+
+## About this task
+
+NOTE
+
+Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
+
+NOTE
+
+Upon save VM Essentials will create a persistent mount owned by `morpheus-app.morpheus-app` on the VM Essentials Appliance for the NFSv3 File Share. The VM Essentials appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before VM Essentials is able to successfully mount the share.
+
+To Add a NFSv3 File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select NFSv3 from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   HOST
+   :   Enter the File Share path on the local VM Essentials Appliance.
+
+   EXPORT FOLDER
+   :   Enter the NFSv3 Folder
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+**Subtopics**  
+
+- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json b/corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
new file mode 100644
index 0000000..f0cc2b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+  "title": "Add HPE Alletra MP Storage",
+  "ordinal": 368,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html",
+  "topic_cluster": {
+    "clustering_title": "Add HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+        "clustering_title": "Add HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-098F382C-607E-4341-AAE1-7898A7E5D739",
+        "clustering_title": "Add HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md b/corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
new file mode 100644
index 0000000..ea06f9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-098F382C-607E-4341-AAE1-7898A7E5D739.md
@@ -0,0 +1,33 @@
+# Add HPE Alletra MP Storage
+
+## About this task
+
+The first step is to create a storage server in VM Essentials. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage
+2. In the “Servers” tab, Click the + ADD button
+3. From the ADD STORAGE SERVER wizard, input the following: 
+
+   NAME:
+   :   Name of the storage server in VM Essentials
+
+   TYPE:
+   :   Select “HPE Alletra MP”
+
+   URL:
+   :   URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
+
+   USERNAME:
+   :   Add your administrative user account
+
+   PASSWORD:
+   :   Add your administrative user account password
+4. Select SAVE CHANGES
+
+## Results
+
+![../../_images/add-storage-server.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-432FC4EC-3961-492E-9423-55CC7E6BCACA-high.png)
+
+The Storage Server will be added and displayed in the Datastore tab.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json b/corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
new file mode 100644
index 0000000..0f2c5f1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+  "title": "Plans",
+  "ordinal": 239,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md b/corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
new file mode 100644
index 0000000..d281c40
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
@@ -0,0 +1,5 @@
+# Plans
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json b/corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
new file mode 100644
index 0000000..e764803
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+  "title": "Cloud Detail View",
+  "ordinal": 93,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Detail View",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+        "clustering_title": "Cloud Detail View"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57",
+        "clustering_title": "Cloud Detail View"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md b/corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
new file mode 100644
index 0000000..2ef69fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.md
@@ -0,0 +1,22 @@
+# Cloud Detail View
+
+The Cloud Detail view shows metrics on health, sync status, resource utilization statistics, and resource counts for hosts, virtual machines, or any other constructs under the umbrella of the selected Cloud.
+
+From the Cloud list page, select the name of a Cloud to display that Cloud’s detail page. You’ll notice the following actions are available:
+
+EDIT
+:   Edit the setup configuration of the Cloud.
+
+REFRESH
+:   Force a sync with the Cloud.
+
+DELETE
+:   Delete the Cloud from VM Essentials.
+
+IMPORTANT
+
+All Instances, managed Hosts, and VMs associated with the Cloud must be removed prior to deleting a Cloud.
+
+**Subtopics**  
+
+- **[Cloud Detail Tabs](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json b/corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
new file mode 100644
index 0000000..e7efe27
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+  "title": "Environments",
+  "ordinal": 287,
+  "parent_title": "Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
+  "topic_cluster": {
+    "clustering_title": "Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md b/corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
new file mode 100644
index 0000000..515cae9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
@@ -0,0 +1,5 @@
+# Environments
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json b/corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
new file mode 100644
index 0000000..ebcbb7e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+  "title": "Overview",
+  "ordinal": 357,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md b/corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
new file mode 100644
index 0000000..8018b5a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.md
@@ -0,0 +1,11 @@
+# Overview
+
+The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus VM Essentials Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
+
+Implemented as a VM Essentials `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for VM Essentials environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM cluster.
+
+On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. VM Essentials integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM hosts in the HVM cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
+
+The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM cluster.
+
+Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json b/corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
new file mode 100644
index 0000000..c7bbf2d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+  "title": "Editing Domain Permissions",
+  "ordinal": 160,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Domain Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+        "clustering_title": "Editing Domain Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2",
+        "clustering_title": "Editing Domain Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md b/corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
new file mode 100644
index 0000000..25a72e2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.md
@@ -0,0 +1,7 @@
+# Editing Domain Permissions
+
+To edit visibility permissions for a domain, navigate to Infrastructure  >  Network  >  Domains. In the row for the selected domain, click MORE > Permissions. Within the Permissions modal, set Group access permissions.
+
+**Subtopics**  
+
+- **[Group Access](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-06426E05-BE70-4917-89E3-153236303513.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json b/corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
new file mode 100644
index 0000000..c1512c6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+  "title": "Disabling Two-Factor Authentication",
+  "ordinal": 300,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.html",
+  "topic_cluster": {
+    "clustering_title": "Disabling Two-Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+        "clustering_title": "Disabling Two-Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D",
+        "clustering_title": "Disabling Two-Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md b/corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
new file mode 100644
index 0000000..13d174a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.md
@@ -0,0 +1,5 @@
+# Disabling Two-Factor Authentication
+
+When two-factor authentication is set up, this section contains two buttons: DISABLE 2FA and GET 2FA CODE. To generate a new QR code and configure an authenticator app, click GET 2FA CODE. Once you generate a new QR code, the old one is no longer valid. At that point you must reconfigure your authenticator app or you will not be able to access your account on the next login attempt. Generating a new QR code requires your password.
+
+To disable 2FA, click DISABLE 2FA. This action does not require a password.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json b/corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
new file mode 100644
index 0000000..7538941
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+  "title": "Openstack Swift Buckets",
+  "ordinal": 184,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.html",
+  "topic_cluster": {
+    "clustering_title": "Openstack Swift Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+        "clustering_title": "Openstack Swift Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA",
+        "clustering_title": "Openstack Swift Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md b/corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
new file mode 100644
index 0000000..e09082b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.md
@@ -0,0 +1,77 @@
+# Openstack Swift Buckets
+
+## About this task
+
+To Add an OpenStack Swift Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Openstack Swift from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   USERNAME
+   :   Openstack Swift Username
+
+   API KEY
+   :   Openstack Swift API Key
+
+   BUCKET NAME
+   :   Enter existing Openstack Swift Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   IDENTITY URL
+   :   Openstack Swift Identity URL
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json b/corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
new file mode 100644
index 0000000..cce08a0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+  "title": "Health Levels",
+  "ordinal": 261,
+  "parent_title": "VM Essentials Health",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.html",
+  "topic_cluster": {
+    "clustering_title": "Health Levels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+        "clustering_title": "Health Levels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471",
+        "clustering_title": "Health Levels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md b/corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
new file mode 100644
index 0000000..31250f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.md
@@ -0,0 +1,10 @@
+# Health Levels
+
+Health levels provide a live representation of the current memory and CPU load on the appliance. Bear in mind that in an HA appliance, this data will be specific to the appliance node you happen to be using. By default, VM Essentials does not include any endpoint or UI tool which can show you the currently used app node. However, a plugin has been developed which can surface this information if needed. See [this thread](https://discuss.morpheusdata.com/t/custom-ping-endpoint-via-morpheus-plugin/389) in the VM Essentials official forums for additional details about accessing and using the plugin.
+
+- **Morpheus CPU:** Instantaneous amount of CPU capacity in use by VM Essentials processes
+- **System CPU:** Instantaneous amount of CPU capacity in use by all processes
+- **Morpheus Memory:** Instantaneous amount of system memory currently in use by VM Essentials processes (see the Knowledge Base article linked in the TIP box below for more information on how VM Essentials claims and manages available memory)
+- **System Memory:** Instantaneous amount of total system memory currently claimed (this is commonly a high percentage, see the TIP box below)
+- **Used Swap:** Instantaneous amount of total available system swap in use
+- **Storage:** The instantaneous percentage utilization of the filesystem mounted at “/”
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json b/corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
new file mode 100644
index 0000000..3913fc8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+  "title": "Data Stores",
+  "ordinal": 191,
+  "parent_title": "NFSv3 File Shares",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.html",
+  "topic_cluster": {
+    "clustering_title": "Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+        "clustering_title": "Data Stores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0",
+        "clustering_title": "Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md b/corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
new file mode 100644
index 0000000..31b9c81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0EE0DFC1-1364-410B-92FD-DD9F6EC320E0.md
@@ -0,0 +1,5 @@
+# Data Stores
+
+Data Stores are logical divisions of underlying storage disk. Organizations may use them to divide and track cloud resources by team or department. When integrating certain Cloud types, VM Essentials will onboard all existing data stores and administrators can then make them available to Groups as needed. At provision time, when applicable based on Cloud and Layout, users can select the datastore they wish to provision to.
+
+Here within the Data Store view in the storage section, users can see a list of data stores for each Cloud. In the row for each Cloud, the storage type, associated Cloud, and permissions information are shown.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json b/corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
new file mode 100644
index 0000000..bb392ca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+  "title": "Create HPE ANW DSS Port Group Network",
+  "ordinal": 362,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.html",
+  "topic_cluster": {
+    "clustering_title": "Create HPE ANW DSS Port Group Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+        "clustering_title": "Create HPE ANW DSS Port Group Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F",
+        "clustering_title": "Create HPE ANW DSS Port Group Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md b/corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
new file mode 100644
index 0000000..052b5a9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.md
@@ -0,0 +1,24 @@
+# Create HPE ANW DSS Port Group Network
+
+## About this task
+
+To create an HPE ANW DSS Port Group network, follow these steps:
+
+## Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select + Add Network > HPE ANW DSS Port Group 
+
+   ![../../_images/3.1_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-3CE7AFEC-D544-4E9A-9277-1343D8DCD7BE-high.png)
+3. Select the Network Service in the CREATE NETWORK form: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-3A253CC3-F827-4CA3-A2C5-58F8FEC8C30D-high.png)
+4. Enter the following details in the CREATE NETWORK form. Note that the values in the screenshot are reference examples. Input only the values intended for the actual network: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-34B08F15-1A6E-4E91-97C0-59D865049E4A-high.png)
+5. Save the network by clicking on Save changes. 
+
+   ![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-02143765-1935-4568-A755-9A6B134CA122-high.png)![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-BF4B2385-7813-4CB8-912B-DCF724834F47-high.png)
+6. The network will be created and displayed in the list of networks. 
+
+   ![../../_images/3.4_network_created.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-2ABDBDC9-8594-4248-B7F8-056488423C77-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json b/corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
new file mode 100644
index 0000000..1b76872
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+  "title": "Credentials",
+  "ordinal": 197,
+  "parent_title": "Trust",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.html",
+  "topic_cluster": {
+    "clustering_title": "Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+        "clustering_title": "Credentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-10A7B17C-6F0D-432A-85BD-3205728606A0",
+        "clustering_title": "Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md b/corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
new file mode 100644
index 0000000..d5f1e98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.md
@@ -0,0 +1,27 @@
+# Credentials
+
+The credentials section allows for various credential types to be securely stored and called back when necessary, such as when creating new integrations with Cloud accounts or other outside technologies. Credentials can also be used to populate REST-based Option Lists sourced from data behind an authentication wall, as well as to run automation Tasks on remote targets that require authentication. Credentials are stored internally and securely on the VM Essentials appliance. The following credential pair types are currently supported:
+
+- Access Key and Secret Key
+- Client ID and Secret
+- Email and Private Key
+- OAuth 2.0
+- Tenant, Username, and Keypair
+- Username and API Key
+- Username and Keypair
+- Username and Password
+- Username, Password, and Keypair
+
+To create a new credential set, click + ADD and then select the type of credential set you’d like to store. Complete the following:
+
+- **CREDENTIAL STORE:** Select “Internal”, an integrated external Cypher store (if any), or an integrated Hashicorp Vault server (if any). See the section below for instructions on integrating with Vault or standing up and integrating with an external Cypher store.
+- **NAME:** A name for the credential set in VM Essentials
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **CREDENTIAL VALUES:** Depending on the credential pair type selected (listed above), the remaining fields will be specific to the chosen type. See the next section for a more complete walkthrough on storing and using OAuth 2.0 credentials
+
+![../../_images/addCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-6107BD26-E1BA-4F6E-888A-10CEDF3C01D7-high.png)
+
+Finally, click ADD CREDENTIALS. Once saved, the credential set will be available for selection where appropriate in VM Essentials UI. In the screenshot below, I’m integrating a new VMware Cloud. In the credentials section, I have the following options: Creating (and using) a new Username and Password credential set (which includes the option to save internally or to an external Cypher store), choosing a previously-stored credential set, or simply entering my credentials locally and not saving them for reuse.
+
+![../../_images/useCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-714A8DE9-4992-4DB9-B9E2-5CAAD363B7A2-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json b/corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
new file mode 100644
index 0000000..1359352
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+  "title": "Creating Service Plans for GPU Hardware Passthrough",
+  "ordinal": 133,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md b/corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
new file mode 100644
index 0000000..5e8645f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
@@ -0,0 +1,7 @@
+# Creating Service Plans for GPU Hardware Passthrough
+
+When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
+
+To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
+
+![../../_images/gpuPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-FEF30612-0724-4835-9310-79D70E4641F1-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json b/corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
new file mode 100644
index 0000000..5e7f390
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+  "title": "Creating Wikis",
+  "ordinal": 18,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Wikis",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+        "clustering_title": "Creating Wikis"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E",
+        "clustering_title": "Creating Wikis"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md b/corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
new file mode 100644
index 0000000..59a5813
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.md
@@ -0,0 +1,13 @@
+# Creating Wikis
+
+The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
+
+Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
+
+![create wiki](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4029426C-1AA2-4873-AE1C-CB4677EFB0F7-high.png)
+
+Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many VM Essentials constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
+
+IMPORTANT
+
+All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json b/corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
new file mode 100644
index 0000000..344fd97
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+  "title": "Linux Settings",
+  "ordinal": 303,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md b/corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
new file mode 100644
index 0000000..43af544
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
@@ -0,0 +1,14 @@
+# Linux Settings
+
+When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Linux user
+- **Password:** The password that will be used with your Linux user (optional if specifying key)
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
+
+WARNING
+
+If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_linux_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-98554851-1F7D-4D05-A502-2FB93933551A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json b/corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
new file mode 100644
index 0000000..ca7ded4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+  "title": "Adding Network Groups",
+  "ordinal": 148,
+  "parent_title": "Network Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+        "clustering_title": "Adding Network Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2",
+        "clustering_title": "Adding Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md b/corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
new file mode 100644
index 0000000..052ae19
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.md
@@ -0,0 +1,19 @@
+# Adding Network Groups
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks Groups
+2. Select ADD
+3. Enter the following: 
+
+   Group info:
+   :   - Name: Name of the Network Group in VM Essentials
+       - Description: Details of the Network Group in VM Essentials
+
+   Networks
+   :   - Search for and select target Networks for the Network Group
+       - Search for and select target Subnets for the Network Group
+
+   Group Access
+   :   - Set Group Access for the Network Group. Group access controls which Groups at provision time will have access to this resource. Select “all” (default) to give workloads provisioned to any Group access to this resource. If this resource should be restricted only to workloads provisioned to specific Groups, select all that apply.
+4. Select SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json b/corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
new file mode 100644
index 0000000..68b7803
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+  "title": "System Status",
+  "ordinal": 8,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.html",
+  "topic_cluster": {
+    "clustering_title": "System Status",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+        "clustering_title": "System Status"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1457342F-8258-47AC-AEB3-54E5FE00E434",
+        "clustering_title": "System Status"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md b/corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
new file mode 100644
index 0000000..124125c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.md
@@ -0,0 +1,3 @@
+# System Status
+
+System status gives a high-level view of the health of the appliance. More detailed information can be viewed on the appliance health detail page (Administration > Health) and a more detailed breakdown of the meaning of each status indicator is in [VM Essentials Health](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json b/corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
new file mode 100644
index 0000000..66b0473
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+  "title": "Selecting a Domain while provisioning an Instance",
+  "ordinal": 165,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.html",
+  "topic_cluster": {
+    "clustering_title": "Selecting a Domain while provisioning an Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+        "clustering_title": "Selecting a Domain while provisioning an Instance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8",
+        "clustering_title": "Selecting a Domain while provisioning an Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md b/corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
new file mode 100644
index 0000000..fdcd970
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.md
@@ -0,0 +1,6 @@
+# Selecting a Domain while provisioning an Instance
+
+## Procedure
+
+1. While creating an instance, in the Configure section, expand the DNS Options.
+2. Select Domain from the Domain dropdown.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json b/corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
new file mode 100644
index 0000000..b0ce77b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+  "title": "Adding Directory Pools",
+  "ordinal": 114,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Directory Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+        "clustering_title": "Adding Directory Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487",
+        "clustering_title": "Adding Directory Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md b/corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
new file mode 100644
index 0000000..1ccf33b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.md
@@ -0,0 +1,25 @@
+# Adding Directory Pools
+
+Before adding a Directory Pool, identify the path to be used as the datastore location. You may use an existing directory, or you may specify a desired path that doesn't yet exist. HPE Morpheus VM Essentials will handle creation of the directory (if necessary), changing its ownership, and defining the storage pool (along with configuring auto-start) all in the background.
+
+To create a new Directory Pool-type datastore:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. Select the Storage tab and the Datastores subtab
+4. Click ADD
+5. Configure the following:
+
+   1. **NAME:** An identifiable name for the datastore used throughout HPE Morpheus VM Essentials UI
+   2. **DIRECTORY:** Directory Pool
+   3. **TARGET PATH:** Your desired path (does not have to currently exist)
+   4. **IMAGE TARGET:** If selected, this datastore will be made available for storage of virtual images
+6. Click SAVE
+
+![The add directory pool modal](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-F74F45D1-59C7-4B4B-BCA2-726D24B4B76A-high.png)
+
+WARNING
+
+When Directory Pools are removed, the target directory is deleted along with all files contained within. Users should take care not to manually store additional files in Directory Pool-targeted directories as the files could be deleted if a datastore were removed.
+
+![The datastores list showing the newly-added directory pool](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-CA6224CA-4FD9-4E70-8FED-81234ABACC40-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json b/corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
new file mode 100644
index 0000000..62e228c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+  "title": "NFS Pools Overview",
+  "ordinal": 115,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.html",
+  "topic_cluster": {
+    "clustering_title": "NFS Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+        "clustering_title": "NFS Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386",
+        "clustering_title": "NFS Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md b/corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
new file mode 100644
index 0000000..e42a1fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.md
@@ -0,0 +1,19 @@
+# NFS Pools Overview
+
+NFS Pools enable an HVM Cluster to use an NFS share as a datastore. The exact steps to configure the NFS share will depend on the storage system providing it, but this section will go over the requirements for creating a compatible share and for adding it to the HVM Cluster via the HPE Morpheus VM Essentials UI.
+
+Administrators only need to set up the NFS server, export the desired directories with the proper permissions and options, and ensure the hosts are able to reach it. HPE Morpheus VM Essentials handles everything else, including mounting directories to the filesystem and handling datastore creation.
+
+Compatible NFS shares must meet the following requirements:
+
+- NFS version 3 or 4
+- The share must allow read and write access
+- The share must be configured with the `no-root-squash` export option
+
+NOTE
+
+NFS version 4 is only supported on HPE Morpheus VM Essentials version 8.0.13 and higher. When using the Migrations feature to move VMware VMs to HVM Clusters targeting an NFS Pool datastore, NFS version 4 must be used.
+
+IMPORTANT
+
+The `no-root-squash` export option is required but typically not set by default. When `no-root-squash` is not set, requests from the NFS client are mapped to an anonymous user on the NFS server, which will result in permissions errors that do not allow the NFS Pool to function correctly. You must set this export option in the `/etc/exports` config file or in a management interface depending on the NFS storage system being utilized.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json b/corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
new file mode 100644
index 0000000..0e6795c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+  "title": "Creating a VM Essentials VMware Image",
+  "ordinal": 332,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a VM Essentials VMware Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+        "clustering_title": "Creating a VM Essentials VMware Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-17230E5D-DFC2-42A1-900E-1C01A1508954",
+        "clustering_title": "Creating a VM Essentials VMware Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md b/corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
new file mode 100644
index 0000000..9495c81
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.md
@@ -0,0 +1,7 @@
+# Creating a VM Essentials VMware Image
+
+VM Essentials comes out of the box with a default set of blueprints for use in many modern deployment scenarios. These consist mostly of base operating system images with a few additional adjustments. These adjustments typically include the addition of cloud-init (which is highly recommended to be used in most environments, but not mandatory). However, in many on-premise deployments there are custom image requirements as well as networking requirements. This guide will go over how to create a VMware Images for use within VM Essentials.
+
+NOTE
+
+A VM Essentials appliance may have many vCenter Clouds tied to any number of vCenter appliances. If the same images need to be available to multiple vCenter Clouds, you will need to download the OVF from one vCenter and upload it into the others. At that point you can make multiple VM Essentials Node Types from the images and it will be available to all needed vCenter Clouds. This is a vCenter limitation but one which may not be obvious when provisioning via VM Essentials.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json b/corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
new file mode 100644
index 0000000..fb36885
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+  "title": "Library",
+  "ordinal": 51,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
+  "topic_cluster": {
+    "clustering_title": "Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md b/corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
new file mode 100644
index 0000000..23c22b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
@@ -0,0 +1,7 @@
+# Library
+
+**Subtopics**  
+
+- **[Labels](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.html)**
+- **[Automation](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json b/corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
new file mode 100644
index 0000000..56cfeb5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+  "title": "Creating Clouds",
+  "ordinal": 92,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+        "clustering_title": "Creating Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE",
+        "clustering_title": "Creating Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md b/corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
new file mode 100644
index 0000000..7b2edac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.md
@@ -0,0 +1,3 @@
+# Creating Clouds
+
+Clouds can be added from Infrastructure > Clouds or in Infrastructure > Groups > (selected Group) > Clouds. A more detailed guide to adding a VMware vCenter Cloud can be found in the vCenter integration guide. The other available Cloud type, known as Private Cloud, is a generic Cloud type that doesn’t directly integrate with any other technology as the vCenter Cloud type does. Instead Private Cloud-type Clouds are used to house your HVM clusters. Make as many Private Cloud-type Clouds as needed to organize your HVM clusters properly.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json b/corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
new file mode 100644
index 0000000..d91e743
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+  "title": "Backups",
+  "ordinal": 210,
+  "parent_title": "Backups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-187699B7-66AC-465F-BDA4-37F51FB0267B",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md b/corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
new file mode 100644
index 0000000..1e04ddf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.md
@@ -0,0 +1,11 @@
+# Backups
+
+In the Backups > Backups section, currently-configured Backups can be viewed and managed, and new Instance, Host and Provider backups be configured. Backups must be tied to a Backup Job, which holds the retention count and the schedule on which the backup should automatically be run. You can create a new Job at the same time as the backup is created or you can create the job ahead of time and associate any new backups to the existing job.
+
+NOTE
+
+Role permissions for Backups determine which backups will be accessible to the individual user.
+
+**Subtopics**  
+
+- **[Create an Instance Backup](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9DA38943-BF95-446D-AB09-32323160D51B.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json b/corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
new file mode 100644
index 0000000..679053d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+  "title": "Deleting Existing Routers",
+  "ordinal": 153,
+  "parent_title": "Routers",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Existing Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+        "clustering_title": "Deleting Existing Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047",
+        "clustering_title": "Deleting Existing Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md b/corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
new file mode 100644
index 0000000..a3b5ee5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.md
@@ -0,0 +1,7 @@
+# Deleting Existing Routers
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the trash can icon for the appropriate router
+3. Acknowledge the pop-up banner ensuring you wish to delete the router
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json b/corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
new file mode 100644
index 0000000..72163a8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+  "title": "VM Essentials Backup Settings",
+  "ordinal": 286,
+  "parent_title": "Backup Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.html",
+  "topic_cluster": {
+    "clustering_title": "VM Essentials Backup Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+        "clustering_title": "VM Essentials Backup Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190",
+        "clustering_title": "VM Essentials Backup Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md b/corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
new file mode 100644
index 0000000..6ab313c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.md
@@ -0,0 +1,25 @@
+# VM Essentials Backup Settings
+
+Scheduled Backups
+:   Enable automatic scheduled backups for provisioned instances
+
+Create Backups
+:   When enabled, VM Essentials will automatically configure instances for manual or scheduled backups
+
+Backup Appliance
+:   When enabled, a backup will be created for the VM Essentials appliance database. Select the `Backup` text link to view or edit settings related to the appliance backup
+
+Default Backup Bucket
+:   Select an existing bucket as the default for future backup runs. Click the `Infrastructure Storage` text link to add a new storage bucket to VM Essentials if needed
+
+Default Backup Schedule
+:   Choose a default schedule interval for automated backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
+
+Default Backup Retention
+:   Choose the default number of backups to be retained for automated Instance and appliance backup jobs
+
+Default Synthetic Full Backup enabled
+:   When enabled, full synthetic backups will be on by default in addition to standard backups for supported workload types
+
+Default Synthetic Full Backup Schedule
+:   Choose a default schedule interval for full synthetic backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json b/corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
new file mode 100644
index 0000000..2c4d3fb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+  "title": "Roles and Identity Sources",
+  "ordinal": 247,
+  "parent_title": "Roles",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.html",
+  "topic_cluster": {
+    "clustering_title": "Roles and Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+        "clustering_title": "Roles and Identity Sources"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A",
+        "clustering_title": "Roles and Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md b/corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
new file mode 100644
index 0000000..d1711d8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.md
@@ -0,0 +1,3 @@
+# Roles and Identity Sources
+
+It is very common for large Enterprises to have an existing identity source that they would like to plug in to VM Essentials for authentication. This includes services like LDAP, Active Directory, OKTA, Jump Cloud, One Login, and SAML. When using these services it becomes important to configure a role mapping between the VM Essentials role assignments to the equivalent identity source groups/roles the user belongs to. This is configurable within the identity source management UI. Sections are provided allowing things like LDAP groups to be directly mapped to specific roles within VM Essentials. If a user matches more than one LDAP/role group then both sets of roles are applied to the user automatically. Configuring Identity Sources is done in Administration > Users. Additionally, administrators may opt to lock users to their mapped role in VM Essentials or keep the roles unlocked to manually administer roles in one-off scenarios. See the docs section dedicated to identity sources for more information on configuring the specific SSO technologies VM Essentials supports.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json b/corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
new file mode 100644
index 0000000..5b83ed2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+  "title": "Roles",
+  "ordinal": 244,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md b/corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
new file mode 100644
index 0000000..d79a599
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
@@ -0,0 +1,7 @@
+# Roles
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.html)**
+- **[Roles and Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1D1D4AAD-3C8A-485D-86CB-2D0FCE48DD4A.html)**
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json b/corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
new file mode 100644
index 0000000..53d468b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+  "title": "Tagging and Metadata",
+  "ordinal": 324,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.html",
+  "topic_cluster": {
+    "clustering_title": "Tagging and Metadata",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+        "clustering_title": "Tagging and Metadata"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2",
+        "clustering_title": "Tagging and Metadata"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md b/corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
new file mode 100644
index 0000000..d665e2e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.md
@@ -0,0 +1,13 @@
+# Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json b/corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
new file mode 100644
index 0000000..c19a3be
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+  "title": "User Process Guides",
+  "ordinal": 307,
+  "parent_title": "Guides",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.html",
+  "topic_cluster": {
+    "clustering_title": "User Process Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+        "clustering_title": "User Process Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1E5AE301-CE00-4509-9820-FB286DDA806A",
+        "clustering_title": "User Process Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md b/corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
new file mode 100644
index 0000000..c4c6f87
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.md
@@ -0,0 +1,5 @@
+# User Process Guides
+
+**Subtopics**  
+
+- **[Backing Up and Restoring the HPE Morpheus VM Essentials Manager](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json b/corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
new file mode 100644
index 0000000..81643e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+  "title": "Failover",
+  "ordinal": 128,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.html",
+  "topic_cluster": {
+    "clustering_title": "Failover",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+        "clustering_title": "Failover"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E",
+        "clustering_title": "Failover"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md b/corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
new file mode 100644
index 0000000..5b6ffce
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.md
@@ -0,0 +1,15 @@
+# Failover
+
+HVM clusters support automatic failover of running workloads in the event of the loss of a host. Administrators can control the failover behavior through the “Manage Placement” action on any running VM. From the VM detail page, click ACTIONS and select “Manage Placement”. Any VM with a placement strategy of “Auto” or “Failover” will be eligible for an automatic move in the event its host is lost. When the loss of a host does occur, the workload will be up and running from a different cluster host within just a short time if it’s configured to be moved during an automatic failover event. Any VMs pinned to a lost host will not be moved and will not be accessible if the host is lost. When the host is restored, those VMs will be in a stopped state and may be restarted if needed.
+
+![../../_images/threeRunningWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-D85300D8-59A9-406D-99F4-2A83E4812C52-high.png)
+
+Each of these VMs is configured for a different failover strategy. When the host is lost, we should expect to see the first two VMs moved to an available host (since they have the “Auto” and “Failover” placement strategies, respectively). We should not see the third VM moved.
+
+![../../_images/auto.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4AF17304-D863-46CD-B761-F76CA83B5DA1-high.png) ![../../_images/failover.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-450A2043-9995-4352-B52F-0D85D7A9500E-high.png) ![../../_images/pinned.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-3C5798EF-8010-4C2C-A9C1-B1A07D5BBCE3-high.png)
+
+After loss of the host these three VMs were running on, we can see the lost host still has one associated VM in a stopped state. The other two VMs are running on a second host which is still available.
+
+![../../_images/lostNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-69BB84AC-5461-4818-A90F-10BB7308E937-high.png) ![../../_images/liveNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-688399E1-CBDA-4B89-AC61-80CF6FCBEBCD-high.png)
+
+When the lost host returns, the moved VMs will come back to their original host. The third VM is associated with this host as well and is in a stopped state until it is manually restarted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json b/corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
new file mode 100644
index 0000000..73bad7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+  "title": "Advanced",
+  "ordinal": 327,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-1EB800EB-6832-487E-BB11-07D8520003CF.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+        "clustering_title": "Advanced"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-1EB800EB-6832-487E-BB11-07D8520003CF",
+        "clustering_title": "Advanced"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md b/corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
new file mode 100644
index 0000000..69d8995
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-1EB800EB-6832-487E-BB11-07D8520003CF.md
@@ -0,0 +1,11 @@
+# Advanced
+
+There are several advanced features provided within VM Essentials that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the VM Essentials appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires VM Essentials v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in VM Essentials via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via VM Essentials. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json b/corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
new file mode 100644
index 0000000..672fe31
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+  "title": "Overview",
+  "ordinal": 315,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-202C8048-0342-4653-97C6-7817B2A9EEB3",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md b/corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
new file mode 100644
index 0000000..956d25f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.md
@@ -0,0 +1,3 @@
+# Overview
+
+VMware is a very common cloud integration choice supported by VM Essentials . They have provided a top notch virtualization solution and one might argue pioneered the virtualization space altogether. As such, many companies utilize this technology and all the features that come with it, so VM Essentials covers a broad feature set in vCenter.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json b/corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
new file mode 100644
index 0000000..d1a6b7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+  "title": "Allow Custom Config",
+  "ordinal": 62,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.html",
+  "topic_cluster": {
+    "clustering_title": "Allow Custom Config",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+        "clustering_title": "Allow Custom Config"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-20656567-501C-4D21-9EDA-1C6898DF61F5",
+        "clustering_title": "Allow Custom Config"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md b/corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
new file mode 100644
index 0000000..fc4d17e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.md
@@ -0,0 +1,9 @@
+# Allow Custom Config
+
+When “Allow Custom Config” is marked on a Task, the user is shown a text area for custom configuration when the Task is executed manually from the Tasks List Page. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+**Subtopics**  
+
+- **[Example JSON Map:](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.html)**
+- **[Task Types](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.html)**
+- **[Task Management](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json b/corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
new file mode 100644
index 0000000..ae034da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+  "title": "Appliance Settings",
+  "ordinal": 266,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+        "clustering_title": "Appliance Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281",
+        "clustering_title": "Appliance Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md b/corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
new file mode 100644
index 0000000..6c34e94
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.md
@@ -0,0 +1,59 @@
+# Appliance Settings
+
+Appliance URL
+:   The default URL used for Agent install and Agent functionality. All Instances and Hosts must be able to resolve and reach this URL over 443 for successful agent install and communication.
+
+NOTE
+
+Alternate Appliance URLs can be configured per Cloud in the Edit Cloud  >  Advanced Options section.
+
+Internal Appliance URL (PXE)
+:   For PXE-Boot your appliance needs to be routable directly with minimal NAT masquerading. This allows one to override the default appliance url endpoint for use by the PXE Server. If this is unset, the default appliance url will be used instead.
+
+API Allowed Origins
+:   A CORS-related field which specifies the origins that are allowed to access the VM Essentials API. For example, if you were designing a web application which needed to make AJAX calls to VM Essentials API. The origins should be specified here. By default, all origins are allowed. When this field is filled, an exclusive whitelist of allowed origins is established.
+
+Cloud Sync Interval
+:   Data is refreshed through cloud integrations at the interval specified here in seconds, the default value is 300 seconds (five minutes). Appliances managing a very large number of clouds may be adversely affected by setting this value too low.
+
+Cluster Sync Interval
+:   Data is refreshed through provisioned Clusters at the interval specified here in seconds, the default value is 60 seconds. Appliances managing a very large number of Clusters may be adversely affected by setting this value too low.
+
+Usage Retainment
+:   Determines how many days to keep account usage (metered costing data) records. Retainment period is not set by default. Usage records will remain indefinitely if Usage Retainment is not set. Note this does not affect generated Invoice records.
+
+Invoice Retainment
+:   Enter the number of days VM Essentials should keep invoice records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large invoice database tables can affect the stability of the application.
+
+Incident Retainment
+:   Enter the number of days VM Essentials should keep incident records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large incident database tables can affect the stability of the application.
+
+Stats Retainment
+:   Select 30, 60 or 90 days period for stats retainment. Selecting a larger period gives the ability to analyze stats, such as Instance metrics, over a longer period of time. For example, in the Monitoring tab of an Instance detail page, users can select a 60 or 90-day analysis period if the stats have been retained that long
+
+Denied Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which should not be allowed sources for HTTP Tasks or REST-populated Option Lists.
+
+Approved Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which are the only approved sources for HTTP Tasks or REST-populated Option Lists. By entering any values here, all others are automatically denied.
+
+Exchange URL
+:   Enter the URL which should be checked for updates to any installed plugins. The default exchange is: `https://share.morpheusdata.com`
+
+Skip Agent Install
+:   For appliances in which skipping the Agent install is the default selection, enable this global flag to default to skipping the Agent install during provisioning
+
+Enable SSL Verification of Agent (Communications)
+:   Enabling SSL Verification of Agent Communications requires a valid Certificate be installed on the Appliance.
+
+Disable SSH Password Authentication
+:   Only allow ssh login using SSH keys. When true, SSH Password Authentication will not be enabled for VM’s and Hosts provisioned after the setting is enabled.
+
+Default Appliance Locale
+:   Sets the default language and region for all users on the VM Essentials appliance. Users with individual language preferences may also override this selection on their User Settings page
+
+Default Console Gateway
+:   Select a configured VM Essentials Worker as a console gateway or VDI gateway. For more on installation and configuration of a gateway, see the [VDI Gateways section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html#vdi-gateways) of VM Essentials documentation.
+
+Max Option List Size
+:   Sets a maximum size for Option Lists (such as those sourced from REST calls to a remote server) to preserve appliance performance in the event that a very large payload is inadvertently accessed. The entered number is multiplied by 1000 (for example, entering “1” results in a maximum list size of 1000).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json b/corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
new file mode 100644
index 0000000..9ee6ed8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+  "title": "Create User",
+  "ordinal": 253,
+  "parent_title": "Users",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-21972435-BFD0-481F-A3E6-A52B116989F3.html",
+  "topic_cluster": {
+    "clustering_title": "Create User",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+        "clustering_title": "Create User"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-21972435-BFD0-481F-A3E6-A52B116989F3",
+        "clustering_title": "Create User"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md b/corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
new file mode 100644
index 0000000..c498f3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-21972435-BFD0-481F-A3E6-A52B116989F3.md
@@ -0,0 +1,52 @@
+# Create User
+
+## About this task
+
+Users are created in Administration > Users.
+
+NOTE
+
+Authorized Identity Source Users will be automatically created upon first sign in.
+
+To create a User:
+
+## Procedure
+
+1. Navigate to Administration > Users
+2. Select + CREATE USER.
+3. From the New User Wizard input: 
+
+   Username & Email
+   :   - First Name
+       - Last Name
+       - Username
+       - Email address
+
+   Receive Notifications
+   :   Enable to receive provisioning email notifications.
+
+   Roles
+   :   Role(s) to be inherited by the user. If multiple roles are selected, the higher permission levels of one role will override the other role(s). See the Roles section of this documentation for more information on stacking Roles and specific Role permissions.
+
+   Password
+   :   Password must contain at least one uppercase letter, one lowercase letter, a number, and a symbol.
+
+   Enabled
+   :   If unchecked, the user will no longer be able to sign into VM Essentials, but their user data will remain.
+
+   Account Locked
+   :   This box is checked when a User has tried unsuccessfully to log in too many times. An administrator will need to uncheck this box in order for the User to be able to make another login attempt.
+
+   Password Expired
+   :   If enabled, the User will be forced to create a new password upon next login. The expired password cannot be used again.
+
+   Linux Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Linux Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this VM Essentials user is a member of.
+
+   Windows Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Windows Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this VM Essentials user is a member of.
+
+       IMPORTANT
+
+       Please ensure password entered is allowable by Windows.
+4. Select SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json b/corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
new file mode 100644
index 0000000..560f5f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+  "title": "Viewing Volumes",
+  "ordinal": 375,
+  "parent_title": "Volumes tab",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing Volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+        "clustering_title": "Viewing Volumes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84",
+        "clustering_title": "Viewing Volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md b/corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
new file mode 100644
index 0000000..24e3f50
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.md
@@ -0,0 +1,21 @@
+# Viewing Volumes
+
+The Volumes tab provides a list of all volumes, including their summary, capacity information, and ransomware monitoring status.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server name.
+3. Select the Volumes tab. You can view the following information:
+   - **Name**: Displays the volume name for the VM.
+   - **Details**: Displays the CD Drive volume or data disk associated with the VM name.
+   - **Usage**: Displays a progress bar. The progress bar displays:
+     - Used capacity in percentage.
+     - Used capacity in either GiB or TiB, based on its value, in comparison to the total capacity.
+   - **Ransomware Monitoring**: Indicates whether ransomware monitoring is enabled or disabled for the volume. Ransomware monitoring is enabled or disabled while creating the datastore.
+
+     NOTE
+
+     Once ransomware monitoring is enabled for a datastore, the ransomware monitoring status cannot be edited​.
+   - **IOPS**: Displays the number of read and write operations performed by the volume each second.
+   - **Throughput**: Displays the amount of data transferred to or from the volume each second.
+
+   ![Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-8E25EA50-EEC7-48EA-8FCF-973EB252A822-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json b/corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
new file mode 100644
index 0000000..f5aa183
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+  "title": "Base Cluster Details",
+  "ordinal": 104,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.html",
+  "topic_cluster": {
+    "clustering_title": "Base Cluster Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+        "clustering_title": "Base Cluster Details"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5",
+        "clustering_title": "Base Cluster Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md b/corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
new file mode 100644
index 0000000..a87472d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.md
@@ -0,0 +1,8 @@
+# Base Cluster Details
+
+An HVM cluster using the hyperconverged infrastructure (HCI) Layout consists of at least three hosts. Physical hosts are recommended to experience full performance of the solution. In smaller environments, it is possible to create an HVM cluster with three nested virtual machines, a single physical host (non-HCI only), or a single nested virtual machine (non-HCI only) though performance may be reduced. With just one host it won’t be possible to migrate workloads between hosts or take advantage of automatic failover. Currently, the default cluster layout requires hosts be a pre-existing Ubuntu 24.04 box with environment and host system requirements described in this section. An earlier cluster layout requiring Ubuntu 22.04 is also included. VM Essentials handles cluster configuration by providing the IP address(es) for your host(s) and a few other details. Details on adding the cluster to VM Essentials are contained in the next section.
+
+**Subtopics**  
+
+- **[Hardware Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-634760AA-7E46-42A7-AD08-85CCE4656873.html)**
+- **[Example Cluster Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json b/corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
new file mode 100644
index 0000000..a4d0097
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+  "title": "Overview",
+  "ordinal": 155,
+  "parent_title": "IP Pools",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-238F9226-4EB4-4E14-B533-584277951C4B.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-238F9226-4EB4-4E14-B533-584277951C4B",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md b/corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
new file mode 100644
index 0000000..1c16721
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-238F9226-4EB4-4E14-B533-584277951C4B.md
@@ -0,0 +1,3 @@
+# Overview
+
+The IP Pools tab in the Networks section allows you to create HVM-type IP Pools (which is an IP address range VM Essentials can use to assign available static IP addresses to Instances) and NSX IP Pools. The IP Pool section also displays pools synced from IPAM integrations like Infoblox, Bluecat and others.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json b/corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
new file mode 100644
index 0000000..de15aef
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+  "title": "Review",
+  "ordinal": 23,
+  "parent_title": "Activity",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.html",
+  "topic_cluster": {
+    "clustering_title": "Review",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+        "clustering_title": "Review"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441",
+        "clustering_title": "Review"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md b/corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
new file mode 100644
index 0000000..8fcfbfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.md
@@ -0,0 +1,7 @@
+# Review
+
+To review the item that generated the activity, click the name of the activity and it will go to a new page and display that item. The list of activity can be filtered by type, user or date range.
+
+NOTE
+
+Deleted activities are displayed as an alert and do not contain a link to the event item. If the activity is not a deletion event we provide a link on the activity name to go to the item the activity occurred on. Delete activity alerts are shown for Instances, servers, Clouds, and Groups.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json b/corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
new file mode 100644
index 0000000..1e637c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+  "title": "Cluster Permissions",
+  "ordinal": 99,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+        "clustering_title": "Cluster Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2581C2D1-AC07-4DE2-B794-20AC25652417",
+        "clustering_title": "Cluster Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md b/corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
new file mode 100644
index 0000000..f3086d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.md
@@ -0,0 +1,3 @@
+# Cluster Permissions
+
+Each Cluster has Group and Service Plan access permissions settings (Gear icon > Permissionsfrom the Clusters list page).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json b/corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
new file mode 100644
index 0000000..69eae42
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+  "title": "Cypher",
+  "ordinal": 213,
+  "parent_title": "Tools",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html",
+  "topic_cluster": {
+    "clustering_title": "Cypher",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md b/corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
new file mode 100644
index 0000000..8f1bb12
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
@@ -0,0 +1,15 @@
+# Cypher
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.html)**
+- **[Mountpoints](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.html)**
+- **[Creating Cypher Keys](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.html)**
+- **[Password](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.html)**
+- **[tfvars](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.html)**
+- **[Secret](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.html)**
+- **[UUID](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.html)**
+- **[Key](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.html)**
+- **[Vault](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.html)**
+- **[Editing Cypher Keys](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.html)**
+- **[Using Cypher Keys in Scripts](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json b/corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
new file mode 100644
index 0000000..bfcc5d7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+  "title": "Gotchas",
+  "ordinal": 345,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.html",
+  "topic_cluster": {
+    "clustering_title": "Gotchas",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+        "clustering_title": "Gotchas"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F",
+        "clustering_title": "Gotchas"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md b/corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
new file mode 100644
index 0000000..88824c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.md
@@ -0,0 +1,5 @@
+# Gotchas
+
+SELinux can cause issues with cloud-init when in enforced mode. It may be advisable to set this to permissive unless it is mandatory within your organization to use an enforced SELinux configuration. If that is the case please see the documentation for the cloud\_init\_t security policies.
+
+Network Manager will also prevent the required restart of the Network Service when assigning static IP’s. Disable Network Manager when possible or Static IP assignment may not work until the Network Service is restarted manually.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json b/corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
new file mode 100644
index 0000000..1fa966a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+  "title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "ordinal": 308,
+  "parent_title": "User Process Guides",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.html",
+  "topic_cluster": {
+    "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+        "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB",
+        "clustering_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md b/corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
new file mode 100644
index 0000000..c73c13a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2686BF33-E793-4BF9-98BE-82F800ED03EB.md
@@ -0,0 +1,17 @@
+# Backing Up and Restoring the HPE Morpheus VM Essentials Manager
+
+NOTE
+
+In the event of a total system failure (full crash), the recovery process requires the user to provision a new, freshly installed VME Manager. You cannot perform this recovery on a partially configured or corrupted appliance. The recovery process involves following:
+
+- Provision the replacement VME Manager
+- Transfer and restore security keys
+- Database injection and reconfiguration
+- Verifying the restored VME Manager
+
+**Subtopics**  
+
+- **[Create A Backup Job](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.html)**
+- **[Integrate a Bucket or File Share](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.html)**
+- **[Configuring HPE Morpheus Enterprise Appliance Backup](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D647F00D-6B45-4E18-B442-14835847EFA7.html)**
+- **[Restoring the HPE Morpheus Enterprise Manager from Backup](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json b/corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
new file mode 100644
index 0000000..8155573
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+  "title": "Overview",
+  "ordinal": 252,
+  "parent_title": "Users",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-26D622EF-A71E-44D7-A705-176ED6445B3D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md b/corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
new file mode 100644
index 0000000..03960d2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-26D622EF-A71E-44D7-A705-176ED6445B3D.md
@@ -0,0 +1,16 @@
+# Overview
+
+The Users page displays a list of all Users. The following fields are surfaced for each User:
+
+- Display Name
+- Username
+- Email
+- Role
+
+Users which are grayed out in the list are currently inactive and cannot log in. The pencil and trash icons at the end of each row allow for editing or deleting Users. Click MORE to see the “impersonate” button. This allows administrators to impersonate any User, which may help confirm their Role permissions meet and do not exceed the desired result.
+
+Click on the hyperlinked Display Name of the User to see a page detailing their effective Role permissions. This is especially useful for Users in multiple Roles where it might otherwise be difficult to determine their exact rights. This page looks identical to a User Role detail page except none of the fields are editable. Edit the User Role permissions for the User if changes need to be made.
+
+NOTE
+
+Some User data created through an Identity Source integration (such as Active Directory) is not editable in VM Essentials, as it is synced from the Identity Source.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json b/corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
new file mode 100644
index 0000000..6851ffc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+  "title": "Setting Up Two-Factor Authentication",
+  "ordinal": 299,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.html",
+  "topic_cluster": {
+    "clustering_title": "Setting Up Two-Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+        "clustering_title": "Setting Up Two-Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E",
+        "clustering_title": "Setting Up Two-Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md b/corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
new file mode 100644
index 0000000..3a70f44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.md
@@ -0,0 +1,7 @@
+# Setting Up Two-Factor Authentication
+
+When two-factor authentication isn’t yet set up, this section contains a single button: ENABLE 2FA. To get started, click this button and VM Essentials will prompt for your password. After entering the password, you’ll be shown a QR code which can be scanned into your authenticator application of choice. Once the QR code is shown, 2FA is active and the supplemental code will need to be entered each time the user logs in.
+
+![../../_images/2fa_qr.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-B46B6795-F044-4E76-BEB1-3A96F5575CE6-high.png)
+
+On subsequent login attempts, the user will be prompted to enter a 2FA code after successful entry of the username and password. Retrieve this code from the 2FA app you set up in the prior section and enter it to complete the login process.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json b/corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
new file mode 100644
index 0000000..6b1d5ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+  "title": "Performing Instance Actions",
+  "ordinal": 49,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.html",
+  "topic_cluster": {
+    "clustering_title": "Performing Instance Actions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+        "clustering_title": "Performing Instance Actions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8",
+        "clustering_title": "Performing Instance Actions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md b/corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
new file mode 100644
index 0000000..939fc3e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.md
@@ -0,0 +1,7 @@
+# Performing Instance Actions
+
+## Procedure
+
+1. Select the Provisioning link in the navigation bar.
+2. From the Instances list, select the desired Instance.
+3. Click the Actions dropdown button and select an Action.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json b/corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
new file mode 100644
index 0000000..70de1f3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+  "title": "Overview",
+  "ordinal": 81,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md b/corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
new file mode 100644
index 0000000..c0719a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.md
@@ -0,0 +1,14 @@
+# Overview
+
+## About this task
+
+Groups in VM Essentials define the available resources for each user. Group access is defined by Roles. Clouds are added to Groups, and a User can only access the Clouds associated with Groups in their Role. Resources such as networks, datastores, resource pools, and folders have additional Group access settings.
+
+The Groups list page displays all current groups, which can be filtered by applied Labels or by simple search. Existing Groups can be edited here and new Groups can be created.
+
+To View Groups:
+
+## Procedure
+
+1. Hover over the Infrastructure link in the menu bar
+2. Click the Groups link
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json b/corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
new file mode 100644
index 0000000..85466b6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+  "title": "Tools",
+  "ordinal": 212,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html",
+  "topic_cluster": {
+    "clustering_title": "Tools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md b/corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
new file mode 100644
index 0000000..0cea6ce
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
@@ -0,0 +1,7 @@
+# Tools
+
+**Subtopics**  
+
+- **[Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html)**
+- **[Archives](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html)**
+- **[Migrations](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json b/corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
new file mode 100644
index 0000000..21a887c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+  "title": "Task Executions",
+  "ordinal": 14,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.html",
+  "topic_cluster": {
+    "clustering_title": "Task Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+        "clustering_title": "Task Executions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615",
+        "clustering_title": "Task Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md b/corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
new file mode 100644
index 0000000..2c67d7c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.md
@@ -0,0 +1,3 @@
+# Task Executions
+
+Displays the number of successful and unsuccessful Task executions over the last day, week or month
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json b/corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
new file mode 100644
index 0000000..b03509d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+  "title": "Handling User Lock-Out",
+  "ordinal": 301,
+  "parent_title": "2 Factor Authentication",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.html",
+  "topic_cluster": {
+    "clustering_title": "Handling User Lock-Out",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+        "clustering_title": "Handling User Lock-Out"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D",
+        "clustering_title": "Handling User Lock-Out"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md b/corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
new file mode 100644
index 0000000..99c89c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.md
@@ -0,0 +1,3 @@
+# Handling User Lock-Out
+
+If a user loses the device they’ve configured for authentication or if they cannot proceed through 2FA login for any other reason, an administrator should impersonate the user’s account, reset their password, disable 2FA, then share the new temporary password with the user. At that point, the user can login, reset their password to something more secure, and re-enable 2FA (if desired).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json b/corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
new file mode 100644
index 0000000..ab1a781
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+  "title": "Prerequisites",
+  "ordinal": 351,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2D035C3B-0102-4FB3-BE34-74094659DC87",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md b/corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
new file mode 100644
index 0000000..aa8dafc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.md
@@ -0,0 +1,11 @@
+# Prerequisites
+
+- A pair of ArubaCX 8325 series switches
+- All the hosts in the Cluster are connected to these pair of switches
+- REST API access to the ArubaCX switches with administrative rights
+- User credentials for the ArubaCX switch pair with API access granted and read/write access to the switch configuration
+
+**Subtopics**  
+
+- **[Server Network Configuration (Netplan)](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-392743FA-D99D-4995-A8F6-3E5541271263.html)**
+- **[Switch Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json b/corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
new file mode 100644
index 0000000..2acbd6f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+  "title": "Backups",
+  "ordinal": 284,
+  "parent_title": "Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md b/corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
new file mode 100644
index 0000000..9b4ecaa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
@@ -0,0 +1,5 @@
+# Backups
+
+**Subtopics**  
+
+- **[Backup Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3A5066B9-898A-4673-A713-C3E41D502742.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json b/corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
new file mode 100644
index 0000000..509b3cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+  "title": "Adding Domains",
+  "ordinal": 159,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+        "clustering_title": "Adding Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD",
+        "clustering_title": "Adding Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md b/corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
new file mode 100644
index 0000000..0c6aa34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.md
@@ -0,0 +1,51 @@
+# Adding Domains
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Domains
+2. Select + ADD
+3. Enter the following: 
+
+   Domain Name
+   :   Ex. demo.example.com
+
+   Description
+   :   Descriptive metadata for use in VM Essentials
+
+   Display Name
+   :   Overrides the displayed name in domain selection components, which is useful when using many OU paths
+
+   Public Zone
+   :   Check for Public Zones, leave uncheck for Private Zones
+
+   Workflow
+   :   Select an existing Workflow which will be applied to Instances at provision time when they are associated with the domain. This is useful for any domain-related scripting you may currently use. For example, you may want to ensure a machine is removed from the domain when it’s torn down which could be accomplished by creating a Provisioning Workflow (with teardown phase Tasks) and associating the Workflow with the domain
+
+   Active
+   :   Active Domains are available for selection in Domain selection fields across VM Essentials. Inactive Domains are removed from Domain selection fields.
+
+   Join Domain Controller
+   :   Enable to have Windows instances join a Domain
+
+   Username
+   :   Admin user for Domain. `domain\username` format required when specifying OU Path
+
+   Password
+   :   Password for DC user account
+
+   DC Server
+   :   (optional) Specify the URL or Path of the DC Server
+
+   OU Path
+   :   (optional) Enter the OU Path for the connection string.
+
+   Guest Username
+   :   (optional) If set, this will change the provisioned hosts RPC Service User after domain join. Useful when a domain policy disables the Administrator account that typically would be set as the RPC user on a host record. VM Essentials will update the RPC username and password on the host(s) record after domain join with the specified Guest Username and Guest Password. The RPC username and password are used for auth during Remote Procedure Call (RPC) executions over winrm, ssh and guest tools.
+
+   Guest Password
+   :   (optional) The password for the Guest User account indicated in the prior field
+4. Click Save Changes
+
+## Results
+
+The Domain has been added and will be selectable in the Domain dropdown during provisioning, and in Cloud and Network settings.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json b/corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
new file mode 100644
index 0000000..99f647d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+  "title": "Role Requirements",
+  "ordinal": 175,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.html",
+  "topic_cluster": {
+    "clustering_title": "Role Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+        "clustering_title": "Role Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84",
+        "clustering_title": "Role Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md b/corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
new file mode 100644
index 0000000..0776daf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.md
@@ -0,0 +1,3 @@
+# Role Requirements
+
+There are two Role permissions for the Infrastructure > Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage gives Full, Read or No access to the Infrastructure > Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json b/corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
new file mode 100644
index 0000000..f060553
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+  "title": "SSH/Winrm",
+  "ordinal": 35,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.html",
+  "topic_cluster": {
+    "clustering_title": "SSH/Winrm",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+        "clustering_title": "SSH/Winrm"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2",
+        "clustering_title": "SSH/Winrm"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md b/corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
new file mode 100644
index 0000000..5b88f26
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.md
@@ -0,0 +1,6 @@
+# SSH/Winrm
+
+**Subtopics**  
+
+- **[Linux Agent](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.html)**
+- **[Windows Agent](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9969BD6B-639D-4633-B825-79578464E8E6.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json b/corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
new file mode 100644
index 0000000..2328e61
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+  "title": "Proxy Settings",
+  "ordinal": 271,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.html",
+  "topic_cluster": {
+    "clustering_title": "Proxy Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+        "clustering_title": "Proxy Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34",
+        "clustering_title": "Proxy Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md b/corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
new file mode 100644
index 0000000..34a07f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.md
@@ -0,0 +1,17 @@
+# Proxy Settings
+
+The VM Essentials Appliance can be configured to communicate through a Proxy server for Cloud API’s and Agent communication back to the Appliance.
+
+NOTE
+
+Additional Proxy configuration is available in the Infrastructure  >  Network  >  Proxies section. Added Proxies can be scoped to Clouds in the Edit Cloud  >  Advanced Options section of the Cloud.
+
+Add a Global Proxy server by entering the following:
+
+- Proxy Host
+- Proxy Port
+- Proxy User
+- Proxy Password
+- Proxy Domain
+- Proxy Workstation
+- No Proxy
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json b/corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
new file mode 100644
index 0000000..35f8224
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+  "title": "Overview",
+  "ordinal": 158,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md b/corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
new file mode 100644
index 0000000..04a66be
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.md
@@ -0,0 +1,12 @@
+# Overview
+
+The Domains section is for creating and managing domains for use in VM Essentials. Domains are used for setting FQDNs, joining Domains, and creating DNS records. The Domains section is also a multi-tenant endpoint for managing domain settings across multiple tenants.
+
+- Domains are synced in from Cloud, DNS and Network Integrations. Domains can also be user created.
+- Active Domains are available for selection in the Domain dropdown when provisioning an Instance
+- Default Domains can be set for Clouds and Networks in their Advanced Options sections.
+- Images can be flagged to Auto-Join Domains in the Infrastructure  >  Network  >  Domains section
+
+IMPORTANT
+
+For an Instance to auto-join a Domain, a Domain must set in the Advanced Options section of the Cloud or Network used when provisioning
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json b/corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
new file mode 100644
index 0000000..075338c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+  "title": "Service Plans",
+  "ordinal": 320,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-30353E6D-5FA2-470C-BB80-238663945F6F.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+        "clustering_title": "Service Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30353E6D-5FA2-470C-BB80-238663945F6F",
+        "clustering_title": "Service Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md b/corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
new file mode 100644
index 0000000..a88aee9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30353E6D-5FA2-470C-BB80-238663945F6F.md
@@ -0,0 +1,3 @@
+# Service Plans
+
+A default set of Service Plans are created in VM Essentials for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json b/corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
new file mode 100644
index 0000000..7acf6ab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+  "title": "File Detail Page",
+  "ordinal": 230,
+  "parent_title": "Archives",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.html",
+  "topic_cluster": {
+    "clustering_title": "File Detail Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+        "clustering_title": "File Detail Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8",
+        "clustering_title": "File Detail Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md b/corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
new file mode 100644
index 0000000..9c4efb3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.md
@@ -0,0 +1,3 @@
+# File Detail Page
+
+The File Detail Page contains details about the file itself as well as private and public (if available) URLs. In the lower section are three tabs. The Links tab contains any download links which have been generated (both active and expired). The History tab contains historical information about the file including creation and deletion of download links and download events. The scripts tab contains a guide for getting started using Archive-stored files in scripts.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json b/corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
new file mode 100644
index 0000000..e7342ae
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+  "title": "Features",
+  "ordinal": 316,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md b/corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
new file mode 100644
index 0000000..f36ee84
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.md
@@ -0,0 +1,25 @@
+# Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+- Metadata tag sync
+
+On top of all these features, VM Essentials also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json b/corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
new file mode 100644
index 0000000..aea2d6f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+  "title": "Features",
+  "ordinal": 358,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md b/corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
new file mode 100644
index 0000000..20767e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.md
@@ -0,0 +1,8 @@
+# Features
+
+- Create and delete networks of type `HPE ANW DSS Port Group` directly from the integration
+- Automatically create and delete networks in Aruba Fabric Composer (AFC) when HVM hosts are added or removed from the HVM cluster
+- Manage network configurations through seamless integration with AFC
+- Enable both micro-segmentation and macro-segmentation for flexible network isolation
+- View detailed summaries and status of Aruba CX 10000 switches
+- Ensure automatic, realtime synchronization of network configurations with Aruba CX 10000 switches
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json b/corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
new file mode 100644
index 0000000..aaa165f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+  "title": "Storage Buckets",
+  "ordinal": 177,
+  "parent_title": "Default Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md b/corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
new file mode 100644
index 0000000..47021a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
@@ -0,0 +1,3 @@
+# Storage Buckets
+
+Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json b/corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
new file mode 100644
index 0000000..d9f38c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+  "title": "Guides",
+  "ordinal": 306,
+  "parent_title": null,
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html",
+  "topic_cluster": {
+    "clustering_title": "Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md b/corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
new file mode 100644
index 0000000..2382ca3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
@@ -0,0 +1,6 @@
+# Guides
+
+**Subtopics**  
+
+- **[User Process Guides](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1E5AE301-CE00-4509-9820-FB286DDA806A.html)**
+- **[Integration Guides](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json b/corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
new file mode 100644
index 0000000..71ed8f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+  "title": "Add Storage Server",
+  "ordinal": 195,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.html",
+  "topic_cluster": {
+    "clustering_title": "Add Storage Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+        "clustering_title": "Add Storage Server"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-33F3509A-A175-4204-A1A8-F3699338CAC5",
+        "clustering_title": "Add Storage Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md b/corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
new file mode 100644
index 0000000..c48367d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.md
@@ -0,0 +1,96 @@
+# Add Storage Server
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+## Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following:
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server
+       :   Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following:
+
+   NAME
+   :   Name of the Storage Server in VM Essentials
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json b/corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
new file mode 100644
index 0000000..90c3716
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+  "title": "Editing Cypher Keys",
+  "ordinal": 223,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Cypher Keys",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+        "clustering_title": "Editing Cypher Keys"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-34291BF2-6D39-46FD-B18A-338089CAF11E",
+        "clustering_title": "Editing Cypher Keys"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md b/corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
new file mode 100644
index 0000000..c72e7ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-34291BF2-6D39-46FD-B18A-338089CAF11E.md
@@ -0,0 +1,3 @@
+# Editing Cypher Keys
+
+Cypher key types which accept user-entered values (not generated values) are editable. To edit, click the “ACTIONS” button at the end of the row for the appropriate Cypher key and then click “Edit.” Edit the values and click SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json b/corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
new file mode 100644
index 0000000..36ceeca
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+  "title": "Restoring the HPE Morpheus Enterprise Manager from Backup",
+  "ordinal": 312,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.html",
+  "topic_cluster": {
+    "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+        "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6",
+        "clustering_title": "Restoring the HPE Morpheus Enterprise Manager from Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md b/corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
new file mode 100644
index 0000000..df46efb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-34B1DB42-8ADD-45C4-B945-137EB77810B6.md
@@ -0,0 +1,38 @@
+# Restoring the HPE Morpheus Enterprise Manager from Backup
+
+Begin by ensuring the Morpheus UI service is stopped on the HPE Morpheus Enterprise Manager VM. Connect to the manager over SSH from your workstation **bearing in mind that most commands in this process will require sudo or root access.** Enter the following command:
+
+```
+```
+[root@app-server~] morpheus-ctl stop morpheus-ui
+```
+```
+
+To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file. View it like so:
+
+```
+```
+[root@app-server~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---- this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Make note of the first `morpheus_password` value as indicated above.
+
+Copy the SQL database backup from the backup bucket or file share to the destination Manager VM at path `/tmp/morpheus_backup.sql`. Then, you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The database backup is now replicated on the new Manager VM. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server~] morpheus-ctl start morpheus-ui
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json b/corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
new file mode 100644
index 0000000..c5a6169
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+  "title": "File Shares",
+  "ordinal": 186,
+  "parent_title": "Rackspace CDN Buckets",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-35419962-0058-4856-A6BD-F4923FD0F044.html",
+  "topic_cluster": {
+    "clustering_title": "File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+        "clustering_title": "File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-35419962-0058-4856-A6BD-F4923FD0F044",
+        "clustering_title": "File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md b/corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
new file mode 100644
index 0000000..1a96540
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-35419962-0058-4856-A6BD-F4923FD0F044.md
@@ -0,0 +1,3 @@
+# File Shares
+
+File Shares are for Backup, Archives, and Virtual Images storage targets. File Shares can be browsed and files and folders can be uploaded, downloaded or deleted from the File Shares section. Retention Policies can be set on Storage File Shares for files to be deleted or backed up to another File Share after a set amount of time.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json b/corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
new file mode 100644
index 0000000..8695c9b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+  "title": "Azure Buckets",
+  "ordinal": 181,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+        "clustering_title": "Azure Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3",
+        "clustering_title": "Azure Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md b/corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
new file mode 100644
index 0000000..1a99064
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.md
@@ -0,0 +1,74 @@
+# Azure Buckets
+
+## About this task
+
+To Add an Azure Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Azure from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   STORAGE ACCOUNT
+   :   Name of the Storage Account in Azure for the Bucket
+
+   STORAGE KEY
+   :   Storage Key provided from Azure
+
+   SHARE NAME
+   :   Enter existing Azure Storage Share name, or to add a new Share enter a new name and select Create Bucket below.
+
+   CREATE BUCKET
+   :   Enable if the Share entered in SHARE NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json b/corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
new file mode 100644
index 0000000..5bec0bc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+  "title": "Adding GFS2 Pools",
+  "ordinal": 118,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3702D75B-9505-40D0-B220-7739F5F72760.html",
+  "topic_cluster": {
+    "clustering_title": "Adding GFS2 Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+        "clustering_title": "Adding GFS2 Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3702D75B-9505-40D0-B220-7739F5F72760",
+        "clustering_title": "Adding GFS2 Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md b/corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
new file mode 100644
index 0000000..ad87dd1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3702D75B-9505-40D0-B220-7739F5F72760.md
@@ -0,0 +1,47 @@
+# Adding GFS2 Pools
+
+In order to utilize GFS2 Pools with HVM Clusters, users must first present the block storage devices to the HVM Hosts. These can be configured via iSCSI or Fibre Channel and all Hosts in the Cluster must be able to access the same block device. For now, this guide will focus more specifically on iSCSI configuration but additional guidance on Fibre Channel configuration may be added in the future.
+
+Once disks are presented to the HVM Hosts, iSCSI targets and GFS2 datastores can be added via the UI. The HPE Morpheus VM Essentials handles most of the configuration from there (including multipathing).
+
+To get started, ensure the following configuration has been made on the storage system. The exact process will depend on the storage system being used:
+
+- Create a LUN and map to an iSCSI target
+- Enable concurrent connections
+- Decide if you want to use CHAP authentication. GFS2 Pools with HVM Clusters support the use of CHAP authentication but there is currently no UI tool to enable it. If you wish to enable it, further instructions are available in [this knowledge article](https://support.hpe.com/hpesc/public/docDisplay?docId=sf000111606en_us&docLocale=en_US)
+
+With the above groundwork laid, create iSCSI target(s) in HPE Morpheus VM Essentials. If two paths to the iSCSI target have been created, two iSCSI objects can be created in the UI and HPE Morpheus VM Essentials will configure multipathing for you.
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the iSCSI subtab
+3. Click Add
+4. Enter the iSCSI target IP address and the port. A default port is already entered for you
+5. Click Save changes
+6. Within a short moment, the modal is dismissed and a new iSCSI target is added to the list
+7. If you intend to go on immediately to the next step of adding a GFS2 datastore, manually refresh the Cluster now (Open the ACTIONS menu on the Cluster detail page and click "Refresh Daily")
+
+IMPORTANT
+
+The above steps are repeated when a second path to the iSCSI target exists. With both paths configured, HPE Morpheus VM Essentials can automatically handle configuration of multipathing. Multipathing cannot be automatically established after the datastore is created in the next step. Both paths must be registered with HPE Morpheus VM Essentials using the process described above prior to creating the datastore in order for multipathing configuration to be handled automatically.
+
+![Adding an iSCSI target](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-ECF9319A-BDC9-48F6-AEB7-9A223C2BD71A-high.png)
+
+![List of added iSCSI targets is shown](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-B8532AB4-AA0A-470B-BEF3-2C0D5C680C3D-high.png)
+
+With the iSCSI targets created, all HVM Hosts should have the LUN mounted as a new block device. With that in place, we can create a new GFS2 datastore.
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the Data Stores subtab
+3. Click Add
+4. Configure the following:
+
+   1. **NAME:** An identifiable name for the datastore in HPE Morpheus VM Essentials
+   2. **TYPE:** GFS2 Pool (Global File System 2)
+   3. **BLOCK DEVICE:** The block device now seen by the host as a result of adding the new iSCSI target(s)
+   4. **ALLOW REFORMATTING:** When marked, HPE Morpheus VM Essentials will reformat the disk if a GFS2 filesystem doesn't currently exist. Marking this box will destroy all data on the disk, use this option with caution
+   5. **IMAGE TARGET:** When marked, this data store will be available to store virtual images. Keep in mind that the HVM Cluster should have just one image target
+5. Click Save
+
+WARNING
+
+Utilizing the "Allow Reformatting" configuration when creating the GFS2 Pool-type datastore will destroy any data currently residing on the disk. Use this option with caution.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json b/corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
new file mode 100644
index 0000000..9ddfb2f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+  "title": "Activity",
+  "ordinal": 15,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-371A58A1-F821-449C-8D2D-EC2657C13B56",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md b/corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
new file mode 100644
index 0000000..ff7809e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.md
@@ -0,0 +1,9 @@
+# Activity
+
+The activity list displays the last few events that have taken place in VM Essentials by any user. This could be new provisioned workloads, deleted workloads, backups, or a number of other things. A more complete list of recent activities can be viewed in Operations > Activity.
+
+There are three types of activities available in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json b/corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
new file mode 100644
index 0000000..02fcc9a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+  "title": "Servers",
+  "ordinal": 194,
+  "parent_title": "Manage Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html",
+  "topic_cluster": {
+    "clustering_title": "Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md b/corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
new file mode 100644
index 0000000..15eee7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
@@ -0,0 +1 @@
+# Servers
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json b/corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
new file mode 100644
index 0000000..e2e1803
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+  "title": "Server Network Configuration (Netplan)",
+  "ordinal": 352,
+  "parent_title": "Prerequisites",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-392743FA-D99D-4995-A8F6-3E5541271263.html",
+  "topic_cluster": {
+    "clustering_title": "Server Network Configuration (Netplan)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+        "clustering_title": "Server Network Configuration (Netplan)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-392743FA-D99D-4995-A8F6-3E5541271263",
+        "clustering_title": "Server Network Configuration (Netplan)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md b/corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
new file mode 100644
index 0000000..a43ae52
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-392743FA-D99D-4995-A8F6-3E5541271263.md
@@ -0,0 +1,21 @@
+# Server Network Configuration (Netplan)
+
+## Procedure
+
+1. On each host, configure a `bond0` interface on the management interfaces
+2. The management interfaces should be connected to the ArubaCX switch pair Sample configuration: 
+
+   ```
+   ```
+   {  
+       bonds:  
+         bond0:  
+           interfaces:  
+             - ens2f0np0  
+             - ens1f0np0  
+           parameters:  
+             mode: "active-backup"  
+       ...  
+   }
+   ```
+   ```
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json b/corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
new file mode 100644
index 0000000..9f03c8a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+  "title": "Role Permissions",
+  "ordinal": 248,
+  "parent_title": "Roles",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md b/corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
new file mode 100644
index 0000000..9137283
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
@@ -0,0 +1,10 @@
+# Role Permissions
+
+NOTE
+
+Permission options for sub-tenant user roles will only list options permitted by the Tenant role applied to the sub-tenant. Sub-Tenant user roles permissions cannot exceed permissions set by the overriding Tenant Role.
+
+**Subtopics**  
+
+- **[Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.html)**
+- **[Feature Access Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json b/corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
new file mode 100644
index 0000000..d42e1f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+  "title": "Add a storage server",
+  "ordinal": 371,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.html",
+  "topic_cluster": {
+    "clustering_title": "Add a storage server",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+        "clustering_title": "Add a storage server"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1",
+        "clustering_title": "Add a storage server"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md b/corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
new file mode 100644
index 0000000..f311837
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.md
@@ -0,0 +1,9 @@
+# Add a storage server
+
+The first step is to create a storage server in VM Essentials. After the storage server is added, you can view the storage summary and alerts, and view or edit volumes. For more information on adding a storage server, see Add HPE Alletra MP Storage.
+
+**Subtopics**  
+
+- **[Viewing the Summary page](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.html)**
+- **[Viewing Alerts](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.html)**
+- **[Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json b/corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
new file mode 100644
index 0000000..5bdc387
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+  "title": "Backup Settings",
+  "ordinal": 285,
+  "parent_title": "Backups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3A5066B9-898A-4673-A713-C3E41D502742.html",
+  "topic_cluster": {
+    "clustering_title": "Backup Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+        "clustering_title": "Backup Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3A5066B9-898A-4673-A713-C3E41D502742",
+        "clustering_title": "Backup Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md b/corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
new file mode 100644
index 0000000..df5c1de
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3A5066B9-898A-4673-A713-C3E41D502742.md
@@ -0,0 +1,11 @@
+# Backup Settings
+
+The Backup settings page allows you enable or disable scheduled backups, select a default backup bucket, and administer global settings related to backups. Changes to global settings only affect new backups going forward and do not affect existing backups.
+
+NOTE
+
+Appliance backups are subject to a two-hour time limit to complete the backup. Automated backup attempts will be abandoned and will fail once this time limit is exceeded.
+
+**Subtopics**  
+
+- **[VM Essentials Backup Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1C1ADB18-710D-40A4-ADCA-660DC7988190.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json b/corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
new file mode 100644
index 0000000..a7effe8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+  "title": "Provisioning",
+  "ordinal": 26,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md b/corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
new file mode 100644
index 0000000..18c9359
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.md
@@ -0,0 +1,9 @@
+# Provisioning
+
+There are many capabilities in the VM Essentials provisioning engine ranging from virtual machines bound for VMware vCenter and HVM cluster targets to containerized workloads targeting Docker. Deployment management and library template construction are also core aspects of the provisioning engine. This section of VM Essentials documentation covers the provisioning engine itself while the Library section covers template building, image management, and automation stacks.
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.html)**
+- **[Provisioning Concepts](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-44974486-3ED4-4C5C-849B-8746A4899889.html)**
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json b/corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
new file mode 100644
index 0000000..6eae7c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+  "title": "Migrations Plans",
+  "ordinal": 234,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md b/corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
new file mode 100644
index 0000000..8a51d16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
@@ -0,0 +1,25 @@
+# Migrations Plans
+
+Migration plans are created and run from the Migrations section of the Tools menu (Tools > Migrations). Migrations happen by creating and running Migration Plans. Plans are created in a pending state, meaning an additional action must be undertaken to set the plan in motion. Thus, Plans may be created which are intended to be run at a later time. Once finished, completed Plans remain on the Migrations list page for later review and, if desired, deletion.
+
+Creating Migration Plans
+
+Begin creating a Migration Plan from the Migrations list page (Tools > Migrations). This page contains a list of all Migrations already created, including those completed, currently running, and available to be run (pending). To start a new Migration, click + ADD.![A list of all currently-created Migrations.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-93D37CD4-FDF6-48AC-95C5-A5B7D7F30E35-high.png)
+
+From the SETUP tab of the CREATE MIGRATION PLAN modal, configure the following:
+
+- **NAME:** A name to identify the Migration
+- **SOURCE:** The source VMware vCenter Cloud
+- **TARGET:** The target Cloud containing the HVM Cluster
+- **RESOURCE POOL:** The selected destination HVM Cluster
+- **GROUP:** The Group which should own the migrated VMs
+
+When finished, click NEXT.![The SETUP tab of the CREATE MIGRATION PLAN modal.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-D9CD7CB0-1B54-42D7-A75C-010C489E9E09-high.png)
+
+The next step is to choose VMs from the selected VMware source Cloud to migrate. Select as many as desired given current recommendations regarding the maximum size due to storage space and available bandwidth (see the previous section). Selected VMs will form a list at the bottom of the modal. When finished, click NEXT.![Selecting source VMs to migration from the source VMware Cloud.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-EB548317-44C7-4C2C-B943-03241A92389D-high.png)
+
+The next tab establishes resource mapping. Listed, you will see the current networks and storage locations for the selected VMs. Choose destination networks and destination storage locations for each. Optionally, enter existing Linux or Windows user credentials and choose if prechecks or guest tools installation should be skipped. Click NEXT.![Mapping source networks and storage to destination networks and storage.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-7B17FB9E-19D1-42B2-9696-7856C59EC92F-high.png)
+
+The final tab is a review tab where all current selections can be checked. Return to any previous tabs, if necessary, to update selections.
+
+At this point, the Migration is created but will not run without additional input. The Migration is in a "Pending" state. All selections made when configuring the Migration are shown here. To execute the Migration, click RUN. The length of time it will take for the Migration to run depends on many factors. Once run, the Migration detail page will provide status updates on VMs currently being migrated, which have completed successfully, and if any have failed. The History tab provides greater detail on current and past migration actions taken. The Destination tab includes details on VMware VMs which have successfully been migrated to the HVM Cluster. Migrations are run just once and may be kept indefinitely after for review. When a Migration is no longer needed, click DELETE.![The migration detail page showing a migration in a pending state.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-7B7CB8A7-E91D-40E5-9B1B-E040BCFB2A0A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json b/corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
new file mode 100644
index 0000000..42c5776
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+  "title": "Overview",
+  "ordinal": 226,
+  "parent_title": "Archives",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md b/corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
new file mode 100644
index 0000000..7d60909
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.md
@@ -0,0 +1,3 @@
+# Overview
+
+Archives provides a way to store your files and make them available for download by your scripts and Users. Archives are organized by buckets and can be tied to any existing Bucket or File Share that may be currently integrated (for more on integrating new storage targets, see storage documentation). Thus, storage buckets in public clouds, on networked storage, or even on the appliance itself may be used to host files.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json b/corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
new file mode 100644
index 0000000..4d90604
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+  "title": "Configuring Backups during Provisioning",
+  "ordinal": 208,
+  "parent_title": "Backups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Backups during Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+        "clustering_title": "Configuring Backups during Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0",
+        "clustering_title": "Configuring Backups during Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md b/corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
new file mode 100644
index 0000000..6cb06a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.md
@@ -0,0 +1,36 @@
+# Configuring Backups during Provisioning
+
+When Backups are enabled, Backup options are presented in the AUTOMATION tab of the provisioning wizard. Note that your default backup bucket and default backup schedule will be set according to your global backup settings as mentioned in the previous sections.
+
+NOTE
+
+The Backup options presented in the Automation tab can be disabled using a “Create Backup” Policy. See ../administration/policies/policies
+
+BACKUP TYPE
+:   Select the type for the Backup. Backup Types displayed will be filtered by available options for the selected Instance Layout
+
+BACKUP NAME
+:   Defaults to the Instance name
+
+BACKUP TARGET
+:   Select the Storage Provider target for the Backup (when applicable)
+
+BACKUP JOB TYPE
+:   Create a new job, clone an existing job, or Add to existing job
+
+JOB NAME
+:   Defaults to the Instance name
+
+RETENTION COUNT
+:   Maximum number of successful backups to retain
+
+BACKUP SCHEDULE
+:   Select the schedule for the backup job from the list of existing execution schedules
+
+SYNTHETIC FULL (Currently only available for KVM VM Snapshot-type backups, such as those used with HVM Instances. More Layout types are expected to support synthetic full backups in the future)
+:   When checked, an additional schedule is configured for the backup job during which a synthetic full backup will be taken. In general, this should be on a longer time period than that at which standard backups (full backup followed by incremental backups) are configured
+
+SYNTHETIC FULL SCHEDULE
+:   Select the schedule for the backup job on which synthetic full backups should be taken
+
+Backup Types displayed will be filtered by available options per selected Instance Layout.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json b/corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
new file mode 100644
index 0000000..f595c8c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+  "title": "2 Factor Authentication",
+  "ordinal": 298,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3B34F036-4C25-4058-B5F4-5340545BE821.html",
+  "topic_cluster": {
+    "clustering_title": "2 Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+        "clustering_title": "2 Factor Authentication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3B34F036-4C25-4058-B5F4-5340545BE821",
+        "clustering_title": "2 Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md b/corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
new file mode 100644
index 0000000..ad2dfbc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3B34F036-4C25-4058-B5F4-5340545BE821.md
@@ -0,0 +1,9 @@
+# 2 Factor Authentication
+
+VM Essentials supports two-factor authentication (2FA) for local user accounts as well as those authenticating through Active Directory and LDAP identity sources. Authentication is handled through a 2FA app such as Authy or Google Authenticator. Other common methods for handling 2FA, such as through email or SMS text message are not currently supported. Two-factor authentication is handled on a per-user basis through the User Settings section. There is not currently a way for an administrator to enforce the use of two-factor authentication appliance-wide.
+
+**Subtopics**  
+
+- **[Setting Up Two-Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-27619E64-03DD-4F3B-B66A-9C2D5350466E.html)**
+- **[Disabling Two-Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0CBD386D-DED9-474D-A9F3-587F58B2D22D.html)**
+- **[Handling User Lock-Out](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-29CAF5CA-BE28-4EB4-BD65-AD667988C36D.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json b/corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
new file mode 100644
index 0000000..8256407
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+  "title": "Add Existing Key Pair",
+  "ordinal": 199,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.html",
+  "topic_cluster": {
+    "clustering_title": "Add Existing Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+        "clustering_title": "Add Existing Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C",
+        "clustering_title": "Add Existing Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md b/corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
new file mode 100644
index 0000000..eb72ead
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.md
@@ -0,0 +1,20 @@
+# Add Existing Key Pair
+
+## About this task
+
+To generate a existing Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. From the Add Key Pair modal input the following as needed: 
+
+   - Name
+   - Public Key
+   - Private Key
+   - Passphrase
+
+   NOTE
+
+   Certain features do not require storage of the private key.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json b/corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
new file mode 100644
index 0000000..4c78b27
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+  "title": "Cloud-Init Settings",
+  "ordinal": 278,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3D27BE17-47C9-476C-AD13-DD516697F862.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+        "clustering_title": "Cloud-Init Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3D27BE17-47C9-476C-AD13-DD516697F862",
+        "clustering_title": "Cloud-Init Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md b/corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
new file mode 100644
index 0000000..42b69e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3D27BE17-47C9-476C-AD13-DD516697F862.md
@@ -0,0 +1,12 @@
+# Cloud-Init Settings
+
+VM Essentials can add global users for Linux and Windows at provision time. Cloud-init/Cloudbase-Init or VMware Tools installed on the provisioned virtual images is required.
+
+Linux
+:   - **Username:** Enter User to be added to Linux Instances during provisioning.
+    - **Password:** Enter password to be set for the above Linux user.
+    - **KeyPair:** Select KeyPair to be added for the above Linux user.
+
+NOTE
+
+Either a password, keypair, or both can be populated for the Linux user. Keypairs can be added in the Infrastructure  >  Keys & Certs section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json b/corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
new file mode 100644
index 0000000..358c5f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+  "title": "Service Plan Permissions",
+  "ordinal": 242,
+  "parent_title": "Overview",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3E03B539-B71C-4D2E-A218-23713D723408.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plan Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+        "clustering_title": "Service Plan Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3E03B539-B71C-4D2E-A218-23713D723408",
+        "clustering_title": "Service Plan Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md b/corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
new file mode 100644
index 0000000..4f53c64
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3E03B539-B71C-4D2E-A218-23713D723408.md
@@ -0,0 +1,5 @@
+# Service Plan Permissions
+
+Group Access permissions determine availability of a Service Plan to Users based on their associated Roles.
+
+- Group Access determines which Groups the Service Plan will be available in for Provisioning and Reconfigure.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json b/corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
new file mode 100644
index 0000000..974388a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+  "title": "Managing Groups",
+  "ordinal": 86,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+        "clustering_title": "Managing Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704",
+        "clustering_title": "Managing Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md b/corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
new file mode 100644
index 0000000..1800608
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.md
@@ -0,0 +1,30 @@
+# Managing Groups
+
+## About this task
+
+To view a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Group name to view/modify
+
+## Results
+
+Available tabs in group view
+
+Hosts
+:   Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.
+
+Virtual Machines
+:   List all Virtual Machines in the Group.
+
+Bare Metal
+:   List all Bare Metal Hosts added to the Group
+
+Clouds
+:   Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.
+
+Wiki
+:   Provides a text area for entering wiki content related to the Group in Markdown format. Additional information on Wiki is available in the Operations > Wiki documentation section
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.json b/corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
new file mode 100644
index 0000000..7bb29ce
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+  "title": "User Settings",
+  "ordinal": 297,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-40300B80-D69C-450B-9848-7A21A3141005.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-40300B80-D69C-450B-9848-7A21A3141005",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.md b/corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
new file mode 100644
index 0000000..15db370
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-40300B80-D69C-450B-9848-7A21A3141005.md
@@ -0,0 +1,12 @@
+# User Settings
+
+The fields included in this section are described below. By entering any new values in these fields and clicking SAVE, the existing value will be overwritten.
+
+- **Theme:** Choose from a selection of themes including default and dark mode themes. The Theme setting is not available when Whitelabeling is enabled on the current Tenant
+- **Username:** Your VM Essentials username
+- **First Name:** Your first name (together with Last Name makes up your display name)
+- **Last Name:** Your last name (together with First Name makes up your display name)
+- **Email:** Your email address
+- **Password:** Enter a value and save changes to update your password. The value in the Confirm field below must match
+- **Confirm:** Confirm the new password you’ve entered
+- **RECEIEVE NOTIFICATIONS** Determines if provisioning notifications are emailed to this User
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json b/corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
new file mode 100644
index 0000000..b208fab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+  "title": "Synced Images",
+  "ordinal": 30,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.html",
+  "topic_cluster": {
+    "clustering_title": "Synced Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+        "clustering_title": "Synced Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6",
+        "clustering_title": "Synced Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md b/corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
new file mode 100644
index 0000000..62ddd9c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.md
@@ -0,0 +1,63 @@
+# Synced Images
+
+When a provisioning target (Cloud) is added, all available image and template records from that Cloud will be synced in regardless of Inventory settings on the Cloud. These image records will be available in the Virtual Images section and can be provisioned by using the target clouds generic Instance Type (ex. By selecting the HVM or VMware Instance Type from the provisioning wizard).
+
+NOTE
+
+Synced Virtual Images are just metadata records in VM Essentials pointing to the image in the target Cloud. The actual image files are not copied/imported to VM Essentials manager.
+
+Before provisioning a synced Virtual Image, ensure the image is configured properly:
+
+Name
+:   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image file.
+
+Operating System
+:   Specifies the platform and OS of the image. All Windows images will need to have Operating System specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified.
+
+Minimum Memory
+:   The Minimum Memory setting will filter available Plan options during provisioning. Plans that do not meet the minimum memory value set on the Virtual Image will not be provided as Plan choices by the provisioning wizard.
+
+Cloud Init Enabled?
+:   On by default, uncheck for any image that does not have Cloud-Init or Cloudbase-Init installed.
+
+    IMPORTANT
+
+    Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in VM Essentials but does not have cloud-init installed will result in immediate provisioning failure.
+
+Install Agent
+:   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, Task execution, and monitoring (Some utilization stats are still collected by Agent-less workloads).
+
+Username
+:   An existing Username on the Image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init Guest Customizations or Nutanix Sysprep are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the Image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist in the image (aka `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change.
+
+Password
+:   Password for the existing user on the image if the Username field is populated.
+
+Storage Provider
+:   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/VMs`. Additional storage providers can be configured in Infrastructure > Storage.
+
+Cloud-Init User Data
+:   Accepts what would go in `runcmd` and can assume bash syntax. Example use: Script to configure satellite registration at provision time.
+
+Auto Join Domain?
+:   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure > Network and the configured domain set on the provisioned to Cloud or Network).
+
+VirtIO Drivers Loaded?
+:   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors, such as HVM cluster
+
+VM Tools Installed?
+:   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected.
+
+Force Guest Customization?
+:   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This is required for host/computer name definitions. domain joining, licenses and user definitions when using DHCP.
+
+Trial Version
+:   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning.
+
+IMPORTANT
+
+Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in VM Essentials but does not have cloud-init installed will result in immediate provisioning failure.
+
+IMPORTANT
+
+For Linux images without cloud-init, an existing username and password must be defined on the Virtual Image record for Agent Install, Domain joining, licensing, script execution and other automation, and SSH or RDP Console access.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json b/corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
new file mode 100644
index 0000000..b660e0f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+  "title": "User Images",
+  "ordinal": 74,
+  "parent_title": "Configuring Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.html",
+  "topic_cluster": {
+    "clustering_title": "User Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+        "clustering_title": "User Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87",
+        "clustering_title": "User Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md b/corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
new file mode 100644
index 0000000..e030950
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.md
@@ -0,0 +1,7 @@
+# User Images
+
+Typically VM Essentials does not have sufficient metatdata to successfully provision synced User Images with no additional configuration. After integrating Clouds and User Images have synced, it is highly recommended to configure the images prior to provisioning.
+
+**Subtopics**  
+
+- **[To edit and configure an existing Virtual Image:](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json b/corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
new file mode 100644
index 0000000..b94eed8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+  "title": "Volumes tab",
+  "ordinal": 374,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.html",
+  "topic_cluster": {
+    "clustering_title": "Volumes tab",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+        "clustering_title": "Volumes tab"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB",
+        "clustering_title": "Volumes tab"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md b/corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
new file mode 100644
index 0000000..148f355
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-443DD312-C75F-4267-A17E-FEDCFD7335FB.md
@@ -0,0 +1,6 @@
+# Volumes tab
+
+**Subtopics**  
+
+- **[Viewing Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-21FEDDFF-A1CE-4628-80C8-1CD0FC683A84.html)**
+- **[Editing volumes](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json b/corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
new file mode 100644
index 0000000..94989a4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+  "title": "Create vCenter Users and Roles",
+  "ordinal": 329,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.html",
+  "topic_cluster": {
+    "clustering_title": "Create vCenter Users and Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+        "clustering_title": "Create vCenter Users and Roles"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B",
+        "clustering_title": "Create vCenter Users and Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md b/corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
new file mode 100644
index 0000000..423fc38
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.md
@@ -0,0 +1,9 @@
+# Create vCenter Users and Roles
+
+For this example, I’ve added a new local user to be my VM Essentials integration user (Menu > Administration > Users and Groups) but any existing user, whether locally-created or sourced from an identity integration (like Active Directory), works fine.
+
+![../../../_images/addUsers.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-2664505C-63D5-43FB-9E16-21AD005B561C-high.png)
+
+The next step is to create a Role (Menu > Administration > Roles). You can edit an existing Role to be sure it has the correct privileges, I’ve opted to create a new role and assign the correct privileges. Below the screenshot, take note of the complete set of required privileges. Once all privileges are set, name the Role (if it’s a new one) and click Finish.
+
+![../../../_images/addRoles.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-3152339A-7CAC-4795-8CBD-67503905D112-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json b/corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
new file mode 100644
index 0000000..cbdcd37
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+  "title": "Provisioning Concepts",
+  "ordinal": 40,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-44974486-3ED4-4C5C-849B-8746A4899889.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Concepts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+        "clustering_title": "Provisioning Concepts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-44974486-3ED4-4C5C-849B-8746A4899889",
+        "clustering_title": "Provisioning Concepts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md b/corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
new file mode 100644
index 0000000..42bb026
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-44974486-3ED4-4C5C-849B-8746A4899889.md
@@ -0,0 +1,9 @@
+# Provisioning Concepts
+
+VM Essentials is a powerful provisioning and management platform for HVM clusters and VMware vCenter private cloud. Compared to other CMP platforms in the space, some terminology and concepts may differ. These concepts are documented in this section along with places where terminology may be slightly different compared with other platforms or with common industry parlance.
+
+**Subtopics**  
+
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.html)**
+- **[Containers / Nodes / Virtual Machines](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.html)**
+- **[Hosts / Servers](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json b/corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
new file mode 100644
index 0000000..f4f264a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+  "title": "Configuring Networks",
+  "ordinal": 140,
+  "parent_title": "Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+        "clustering_title": "Configuring Networks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03",
+        "clustering_title": "Configuring Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md b/corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
new file mode 100644
index 0000000..abc3416
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.md
@@ -0,0 +1,10 @@
+# Configuring Networks
+
+**Subtopics**  
+
+- **[DHCP](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.html)**
+- **[Static and IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.html)**
+- **[Advanced Options (Search Domains)](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.html)**
+- **[Group and Tenant Access](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C.html)**
+- **[Guest Console SSH Tunnel](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.html)**
+- **[Subnets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9FC58214-95C7-4690-91DA-3185640E3712.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json b/corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
new file mode 100644
index 0000000..d729328
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+  "title": "HPE Alletra MP Storage",
+  "ordinal": 366,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md b/corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
new file mode 100644
index 0000000..60003dd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
@@ -0,0 +1,9 @@
+# HPE Alletra MP Storage
+
+**Subtopics**  
+
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.html)**
+- **[Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-098F382C-607E-4341-AAE1-7898A7E5D739.html)**
+- **[Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html)**
+- **[Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html)**
+- **[Add a storage server](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-39D5E3C6-08F3-457E-BE0D-BDCF083963E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json b/corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
new file mode 100644
index 0000000..8cea2ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+  "title": "Provisioning a Workload",
+  "ordinal": 108,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a Workload",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+        "clustering_title": "Provisioning a Workload"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45B4119E-416A-43FA-B2A0-C7D52D028326",
+        "clustering_title": "Provisioning a Workload"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md b/corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
new file mode 100644
index 0000000..595d446
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.md
@@ -0,0 +1,15 @@
+# Provisioning a Workload
+
+At this point, the cluster is ready for workloads to be provisioned to it. Within the Instance provisioning wizard (See Provisioning > Instances documentation for more details on provisioning), there is now the “HVM” Instance Type. This Instance will allow you to choose from any HVM cluster-compatible images within your environment. Out of the box, VM Essentials does not include any compatible images but there is a section later in this guide covering the process of onboarding existing QCOW images into the UI as Virtual Images and another section covering the process of prepping Windows images from the downloaded ISO.
+
+After arriving at the Configure tab of the provisioning wizard, select a Plan based on resource needs. From the **RESOURCE POOL** field, select the desired HVM cluster. When configuring **VOLUMES** for the new workload, note that space can be claimed from the configured volume. Within **NETWORKS**, we can add the new workload to one of the **VLANS** set up as part of cluster creation. Finally, note that we can choose the HOST the workload should run on in addition to selecting the compatible image.
+
+TIP
+
+The VOLUMES configuration within the provisioning wizard includes a flyout menu allowing storage type (standard, thin, thick (lazy zero), and thick (eager) and storage profile (cache: none or cache: directsync) configurations to be set on each individual volume.
+
+Review and complete the provisioning wizard. After a short time, the workload should be up and running. With a workload now running on the cluster, we can take a look at some of the monitoring, migration, failover, and other actions we can take for workloads running on HVM clusters.
+
+NOTE
+
+HVM clusters support CPU pinning (tying specific vCPUs associated with running workloads to specific physical CPU cores). Currently, this must be done manually by accessing the appropriate HVM host and issuing `virsh` commands or editing XML. Adding UI tools to view and control CPU pinning is on the product roadmap to be added in the near future. Despite the requirement to edit CPU pinning manually, this is a supported action for workloads running on HVM clusters.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json b/corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
new file mode 100644
index 0000000..8836603
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+  "title": "Plugins",
+  "ordinal": 257,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.html",
+  "topic_cluster": {
+    "clustering_title": "Plugins",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+        "clustering_title": "Plugins"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45D07344-870A-4CB7-84D9-4AF78C151B70",
+        "clustering_title": "Plugins"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md b/corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
new file mode 100644
index 0000000..366284f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.md
@@ -0,0 +1,21 @@
+# Plugins
+
+## About this task
+
+The Plugins allow you to extend the functionality of HPE Morpheus VM Essentials beyond its default capabilities.
+
+To add a plugin, perform the following:
+
+## Procedure
+
+1. Navigate to Administration > Integrations.
+2. Click Plugins tab.
+3. Click ADD.
+4. You can upload the `.jar` file using either of the following:
+
+   - Drag and drop the file into the upload window.
+   - Select the file manually and click UPLOAD.
+
+## Results
+
+The plugin activates automatically if the validation succeeds.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json b/corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
new file mode 100644
index 0000000..4f073b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+  "title": "User Access",
+  "ordinal": 89,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.html",
+  "topic_cluster": {
+    "clustering_title": "User Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+        "clustering_title": "User Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A",
+        "clustering_title": "User Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md b/corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
new file mode 100644
index 0000000..c9e71fe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.md
@@ -0,0 +1,5 @@
+# User Access
+
+IMPORTANT
+
+User access to Groups is determined by their Role(s). Group access for Roles can be configured in the Group Access section of a Role’s Settings.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json b/corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
new file mode 100644
index 0000000..64e605f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+  "title": "Execute Scheduling",
+  "ordinal": 69,
+  "parent_title": "Automation",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+        "clustering_title": "Execute Scheduling"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3",
+        "clustering_title": "Execute Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md b/corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
new file mode 100644
index 0000000..2ba40af
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.md
@@ -0,0 +1,31 @@
+# Execute Scheduling
+
+Execute Scheduling creates time schedules for automated jobs, such as backups. Backup Jobs are discussed in greater detail in the Backups section and are configured with an execution schedule to coordinate their run times. This section goes through the process of creating and configuring the scheduling object.
+
+Schedules use CRON expressions, such as `0 23 * * 2` equalling `Executes every week on Tuesday at 23:00`. CRON expressions can easily be created by clicking the corresponding translation in the create or edit Execution Schedule modal below the Schedule field and selecting a new value.
+
+NOTE
+
+Execute Schedules CRON expressions should not include seconds or years. The days of the week should be numbered 1-7, beginning with Monday and ending with Sunday. SUN-SAT notation may also be used. For more on writing CRON expressions, many guides are hosted on the Internet including [this one](https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm). VM Essentials execution schedules support most cron syntax but certain more complex expressions may fail to evaluate and the execute schedule will not save. Additionally, some complex expressions may save and work correctly while the friendly written evaluation below the SCHEDULE field is not interpreted correctly. This is due to an issue with the underlying library used to build this feature and cannot easily be resolved at this time.
+
+NAME
+:   Name of the Execution Schedule
+
+    NOTE
+
+    When assigning Execution Schedules, the name value will appear in the selection drop-down. Using a name that makes clear the time interval is often helpful.
+
+DESCRIPTION
+:   Description of the Execution Schedule for reference in the Execution Schedules list
+
+TIME ZONE
+:   The time zone for execution
+
+Enabled
+:   Check to enable the schedule. Uncheck to disable all associated executions and remove the schedule as an option for Jobs in the future
+
+SCHEDULE
+:   Enter CRON expression for the Execution Schedule, for example `0 0 * * *` equals `Every day at 00:00`
+
+SCHEDULE TRANSLATION
+:   The entered CRON schedule is translated below the SCHEDULE field. Highlighted values can be updated by selecting the value, and relevant options will be presented. The CRON expression will automatically be updated
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json b/corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
new file mode 100644
index 0000000..65b9f32
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+  "title": "Storage",
+  "ordinal": 174,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md b/corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
new file mode 100644
index 0000000..9e67e93
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.md
@@ -0,0 +1,23 @@
+# Storage
+
+Infrastructure  >  Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in VM Essentials.
+
+**Subtopics**  
+
+- **[Role Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2E69D206-F6D6-48BF-8F13-D85D7E201B84.html)**
+- **[Default Storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A745B955-2E59-4769-AB47-E32098A84653.html)**
+- **[Supported Bucket Types](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.html)**
+- **[Alibaba Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.html)**
+- **[Amazon S3 Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.html)**
+- **[Azure Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-35B83D2C-52C6-4240-94B3-ED44777AD4B3.html)**
+- **[Google Cloud Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.html)**
+- **[Dell EMC ECS Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.html)**
+- **[Openstack Swift Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0D60567D-2DD3-4D8B-92D6-6849C7D773EA.html)**
+- **[Rackspace CDN Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.html)**
+- **[Supported File Share Types](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.html)**
+- **[CIFS File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.html)**
+- **[Local Storage File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.html)**
+- **[NFSv3 File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-07778212-ECE2-41DC-A130-1A6271833CA4.html)**
+- **[Create Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.html)**
+- **[Manage Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.html)**
+- **[Add Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-33F3509A-A175-4204-A1A8-F3699338CAC5.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json b/corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
new file mode 100644
index 0000000..0c59130
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+  "title": "HPE Morpheus VM Essentials Software",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus VM Essentials Software",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+        "clustering_title": "HPE Morpheus VM Essentials Software"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93",
+        "clustering_title": "HPE Morpheus VM Essentials Software"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md b/corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
new file mode 100644
index 0000000..237d481
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-498C49E5-5D26-44E1-A2CC-9AAC0813BA93.md
@@ -0,0 +1,12 @@
+# HPE Morpheus VM Essentials Software
+
+**Subtopics**  
+
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.html)**
+- **[Operations](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3A5117DE-E11D-41D0-A016-A68154A90DCA.html)**
+- **[Library](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html)**
+- **[Infrastructure](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.html)**
+- **[Tools](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html)**
+- **[Administration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AAD13737-533B-491F-A155-DDB027057157.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json b/corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
new file mode 100644
index 0000000..5d324d5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+  "title": "Image Preparation",
+  "ordinal": 335,
+  "parent_title": "Creating a Windows Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.html",
+  "topic_cluster": {
+    "clustering_title": "Image Preparation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+        "clustering_title": "Image Preparation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223",
+        "clustering_title": "Image Preparation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md b/corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
new file mode 100644
index 0000000..f4c087f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.md
@@ -0,0 +1,34 @@
+# Image Preparation
+
+## About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing VM Essentials, provisioning and post deploy scripts can expand drives to desired sizing.
+
+## Procedure
+
+1. Ensure VMware Tools is installed on the operating system.
+2. Apply any service packs / updates to the operating system.
+3. Configure WinRM to allow remote management and open the firewall. This is optional if using VMware Tools RPC mode for agent install and VM Essentials Agent for guest exec. To enable this, under local computer Administrator, open a command prompt and run 
+
+   ```
+   ```
+   winrm quickconfig
+   ```
+   ```
+4. Install .Net at least 4.5.2
+5. Ensure Windows Firewall will allow WinRM connections.
+6. Shutdown the virtual machine and convert to a template.
+
+## Results
+
+NOTE
+
+WinRM is not required and is used as a fallback when using vmtools guest exec and customizations
+
+NOTE
+
+Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
+
+IMPORTANT
+
+VM Essentials supports the use of SR-IOV network adapters with VMware Clouds. Windows images must have SR-IOV network drivers installed to work with this adapter type. If they do not, provisioning will fail.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json b/corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
new file mode 100644
index 0000000..5927ed0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+  "title": "Instances",
+  "ordinal": 41,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md b/corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
new file mode 100644
index 0000000..23ab26a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4A3953E9-FB5E-4552-9DA3-EA1BBFAFC89D.md
@@ -0,0 +1,5 @@
+# Instances
+
+VM Essentials starts with provisioning Instances. In some platforms, an Instance is representative of a singular object like a virtual machine in VMware vCenter. In VM Essentials, this concept was rethought. An Instance is more of a representation of a resource or service. This service may involve several virtual machines, as in the case of a database cluster or horizontally-scaled web servers.
+
+When viewing an Instance detail page, one is able to look at details and statistics specific to a virtual machine or container. VM Essentials simply helps simplify the management model for tracking these services.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json b/corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
new file mode 100644
index 0000000..dfc6ea0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+  "title": "Overview",
+  "ordinal": 291,
+  "parent_title": "License",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md b/corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
new file mode 100644
index 0000000..fdad66a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.md
@@ -0,0 +1,3 @@
+# Overview
+
+VM Essentials requires a valid license for provisioning new Instances and Clusters, and converting existing Instances to managed. Licenses can be applied and updated in this section, and the current license status, as well as usage metrics, can be checked.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json b/corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
new file mode 100644
index 0000000..f0d582f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+  "title": "Backups",
+  "ordinal": 204,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md b/corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
new file mode 100644
index 0000000..a65307c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4BDACB16-C2FA-4B0C-A07F-DE5795C824DD.md
@@ -0,0 +1,12 @@
+# Backups
+
+The VM Essentials built-in Backup solution provides VM, Container, Host, Database, File, Directory, Volume and Storage Provider Backup, Snapshot and Replication capabilities. Backups can be automatically configured during provisioning or manually created at any time. Backup Jobs with custom Execution Schedules and retention counts can be created and used across all environments in conjunction with configured Storage Providers. Backups can be restored over current Instances or as new Instances, and downloaded or deleted from VM Essentials.
+
+VM Essentials also integrates with external services to automate availability with other providers.
+
+**Subtopics**  
+
+- **[Initial Backups Setup](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.html)**
+- **[Configuring Backups during Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3AEA3F6C-138B-4BEB-97DC-F0F857F165D0.html)**
+- **[Summary](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-187699B7-66AC-465F-BDA4-37F51FB0267B.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json b/corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
new file mode 100644
index 0000000..9508ec0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+  "title": "Overview",
+  "ordinal": 232,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md b/corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
new file mode 100644
index 0000000..387ec01
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
@@ -0,0 +1,3 @@
+# Overview
+
+The bulk migration tool is designed to migrate existing VMs running on integrated VMware vCenter Clouds to HVM Clusters. Thus, creating a migration requires existing vCenter Cloud integration(s) and at least one functional HVM Cluster. See the VMware vCenter integration guide and the HVM Clusters guide elsewhere in this documentation stack for more details on getting started with and using those integrations. Migrations may include multiple VMs and may include both Linux and Windows workloads.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json b/corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
new file mode 100644
index 0000000..b593891
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+  "title": "Windows Provisioning Tips",
+  "ordinal": 318,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Provisioning Tips",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+        "clustering_title": "Windows Provisioning Tips"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96",
+        "clustering_title": "Windows Provisioning Tips"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md b/corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
new file mode 100644
index 0000000..0578b70
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.md
@@ -0,0 +1,7 @@
+# Windows Provisioning Tips
+
+By default when provisioning windows templates, VM Essentials performs guest customizations which initiates a sysprep. This resets the Administrator user and password. VM Essentials will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json b/corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
new file mode 100644
index 0000000..59eddb5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+  "title": "Network",
+  "ordinal": 137,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html",
+  "topic_cluster": {
+    "clustering_title": "Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md b/corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
new file mode 100644
index 0000000..9eeb061
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
@@ -0,0 +1,11 @@
+# Network
+
+**Subtopics**  
+
+- **[Networks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html)**
+- **[Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html)**
+- **[Routers](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html)**
+- **[IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html)**
+- **[Domains](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json b/corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
new file mode 100644
index 0000000..492bde9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+  "title": "Multitenancy",
+  "ordinal": 326,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.html",
+  "topic_cluster": {
+    "clustering_title": "Multitenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+        "clustering_title": "Multitenancy"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D",
+        "clustering_title": "Multitenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md b/corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
new file mode 100644
index 0000000..869e9b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.md
@@ -0,0 +1,3 @@
+# Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json b/corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
new file mode 100644
index 0000000..98c821d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+  "title": "View HPE Aruba CX DSS Network Integration",
+  "ordinal": 364,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.html",
+  "topic_cluster": {
+    "clustering_title": "View HPE Aruba CX DSS Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+        "clustering_title": "View HPE Aruba CX DSS Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571",
+        "clustering_title": "View HPE Aruba CX DSS Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md b/corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
new file mode 100644
index 0000000..cba06aa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.md
@@ -0,0 +1,19 @@
+# View HPE Aruba CX DSS Network Integration
+
+To view the HPE Aruba CX DSS Network integration, follow these steps:
+:   1. Navigate to Infrastructure > Network > Integrations
+    2. Select the HPE Aruba CX DSS integration from the list.
+
+       ![../../_images/5.1_list_network_integrations.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5F56F425-47AA-4B32-9A7B-48C69C82CFAB-high.png)
+       - `Summary` - Click on the Summary tab to view the summary of the integration.
+
+         ![../../_images/5.2_view_integration_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-0B2B766C-E581-4C17-BE5D-C95F72BDCB20-high.png)
+       - `Switches` - Click the Switches tab to view detailed information about all Aruba CX 10000 switches managed by the integration.
+
+         ![../../_images/5.3_view_integration_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-A5481BCF-8C48-4106-B3C2-F0AD92CEFEE3-high.png)
+       - `Networks` - Click on the Networks tab to view the networks associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-C93D74CC-3795-4FA8-A12A-BADF901EB1AB-high.png)
+       - `Firewalls` - Click on the Firewall tab to view firewall policies associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-FC71FD7B-012A-4291-9519-0AFD8374D65C-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json b/corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
new file mode 100644
index 0000000..383ec8a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+  "title": "Adding an Archive",
+  "ordinal": 228,
+  "parent_title": "Archives",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an Archive",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+        "clustering_title": "Adding an Archive"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A",
+        "clustering_title": "Adding an Archive"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md b/corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
new file mode 100644
index 0000000..c502d9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.md
@@ -0,0 +1,16 @@
+# Adding an Archive
+
+To add a new Archive, click + ADD from the Archives list page. Configure the following:
+
+- **NAME:** A friendly name for the Archive in VM Essentials
+- **DESCRIPTION:** An optional description for the Archive
+- **BUCKET:** Select an existing bucket or file share to store files in for this Archive. To integrate a new bucket or file share to use for an Archive, navigate to Infrastructure > Storage
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants selected will have access to the Archive
+- **PUBLIC URL:** When marked, VM Essentials will create a public download URL for all files in the Archive
+
+WARNING
+
+Be sure that no sensitive data will be stored in the Archive if it will be configured to generate public URLs. Anyone with the public URL will be able to download the file without authentication.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json b/corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
new file mode 100644
index 0000000..ffc51c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+  "title": "Containers / Nodes / Virtual Machines",
+  "ordinal": 42,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.html",
+  "topic_cluster": {
+    "clustering_title": "Containers / Nodes / Virtual Machines",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+        "clustering_title": "Containers / Nodes / Virtual Machines"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147",
+        "clustering_title": "Containers / Nodes / Virtual Machines"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md b/corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
new file mode 100644
index 0000000..4103f77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4F822F1E-105F-48CD-83A7-3BB562A5B147.md
@@ -0,0 +1,3 @@
+# Containers / Nodes / Virtual Machines
+
+In relation to Instances, an Instance can have many nodes. A node is a generic representation of a container or a virtual machine. In most cases, VM Essentials will represent a node as a Container or Virtual Machine depending on the provisioning engine used for the Instance (workload provisioned to a HVM cluster as opposed to a Docker cluster, for example). Node is just a generic naming representation when referring to these types of items. The public VM Essentials developer API, however, often refers to both virtual machines and Docker containers as “containers”. The UI was updated to better delineate this concept for easier understanding but, in essence, the name is valid for both concepts of containerized environments as well as virtual machines.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json b/corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
new file mode 100644
index 0000000..21617d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+  "title": "UI",
+  "ordinal": 82,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.html",
+  "topic_cluster": {
+    "clustering_title": "UI",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+        "clustering_title": "UI"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE",
+        "clustering_title": "UI"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md b/corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
new file mode 100644
index 0000000..5256ee8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.md
@@ -0,0 +1,4 @@
+# UI
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json b/corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
new file mode 100644
index 0000000..d40cb5b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+  "title": "Instances",
+  "ordinal": 44,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md b/corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
new file mode 100644
index 0000000..a103a16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-50571A00-659C-4D50-8AD6-8C0EBC77FA13.md
@@ -0,0 +1,10 @@
+# Instances
+
+Instances are a great starting point for taking advantage of self-service features and spinning up both VMs and containers. The top of the main Instances page shows overall statistics for the listed Instances, including count, status, and resource utilization. You can search for Instances by name, or filter by group, type, or category.
+
+The Instance list contains important information about each Instance, including the Instance name, environment tag, type, IP address and port info, Instance version, the number of virtual machines or containers, the Group, and the associated Cloud.
+
+**Subtopics**  
+
+- **[Creating Instances](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.html)**
+- **[Managing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json b/corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
new file mode 100644
index 0000000..d696359
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+  "title": "Tenant Management Settings",
+  "ordinal": 267,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Management Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+        "clustering_title": "Tenant Management Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54",
+        "clustering_title": "Tenant Management Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md b/corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
new file mode 100644
index 0000000..1c6f78b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.md
@@ -0,0 +1,13 @@
+# Tenant Management Settings
+
+Registration Enabled
+:   If enabled, the appliance login screen will have a “NEED AN ACCOUNT? SIGN UP HERE” link added, enabling new Tenant registration.
+
+Default Tenant Role
+:   Sets the default Tenant Role applied to Tenants created from Tenant Registration.
+
+Default User Role
+:   Sets the default User Role applied to the User created from a Tenant Registration.
+
+Docker Privileged Mode
+:   Enable to allow Docker containers running on VM Essentials Docker hosts to run in privileged mode which adds additional access to the host hardware and resources but also comes with additional security risks
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json b/corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
new file mode 100644
index 0000000..7cbeb85
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+  "title": "Viewing the Summary page",
+  "ordinal": 372,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing the Summary page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+        "clustering_title": "Viewing the Summary page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400",
+        "clustering_title": "Viewing the Summary page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md b/corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
new file mode 100644
index 0000000..1aecdfc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5174B2CB-BBD2-40CD-A48F-7C044FC9B400.md
@@ -0,0 +1,65 @@
+# Viewing the Summary page
+
+The Summary tab displays system information, capacity utilization of the system, and the number of ransomware alerts detected
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server. The Summary tab displays the information for the selected server. ![Summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-CADEC596-4D47-4B87-85E1-DC2756B5DAD8-high.png)
+
+   The Summary tab contains:
+
+   - **System**
+
+     The following information is displayed in the System tile:
+     - **Name**: Displays the system name of the selected server.
+     - **Model**: Displays the model name of the system.
+     - **Serial Number**: Displays the serial number of the system.
+     - **Health status**: Displays the system health status of the array depending on the highest severity type of the alerts listed in the Alerts tab for the storage system. The health status values can be Critical, Normal, or Warning.
+
+       | Highest Severity Type of Alerts | Health status |
+       | --- | --- |
+       | Critical or Fatal | Critical (The system has some major issues that will affect performance) |
+       | Major | Warning (The system is operational but with some non-critical issues) |
+       | Other types | Normal (The system is functioning as expected) |
+     - **Firmware version**: Displays the firmware version of the storage system.
+     - **WWN**: Displays a unique identifier name of the system.
+     - **Uptime**: Displays the total time the system has been operational.
+     - **IP Address**: Displays the IP address of the system.
+   - **Capacity Utilization**
+
+     The Capacity Utilization tile displays the total and used capacity percentage of the selected storage system.
+
+     - For models HPE Alletra MP B10000 and later, the Capacity Utilization tile populates the usable capacity.
+     - For models prior to HPE Alletra MP B10000, the Capacity Utilization tile populates the raw capacity information.
+
+     NOTE
+
+     You can get the latest system information by clicking the Summary tab.
+   - **Ransomware Detection**
+
+     The Ransomware Detection tile displays the number of ransomware alerts detected. A hyperlink is displayed when more than one ransomware alert is detected; otherwise, it is displayed as a plain text.
+
+     On clicking the hyperlink, you can view the details of alert by selecting Ransomware monitoring as the Filter by Type.
+
+     ![Alerts - ransomware monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-0E521724-F9E5-4619-B9D9-BB943E488958-high.png)
+   - **Protection**
+
+     Using the Filter by drop-down list, you can view the protection status for a `VM` or an `Instance`.
+
+     This tile displays the snapshot protection and remote replication status of both virtual machines (VMs) and instances on the storage system. You can also view the total percentage of VMs or Instances that are protected. Protection is determined based on snapshot availability with or without remote replication. The protection data is auto-refreshed periodically.
+
+     NOTE
+
+     Hover over the information (i) icon beside each field to display the description.
+
+     For VMs, the following information is displayed:
+     - **Snapshot:** Count of VMs where each volume has a point-in-time snapshot.
+     - **Remote Replication:** Count of VMs that have replicated volumes.
+     - **Snapshot + Remote Replication:** Count of VMs that have replicated volumes, where each volume also has a point in time snapshot.
+     - **Unprotected:** Count of VMs that have neither replicated volumes nor point-in-time snapshot on any volume.
+
+     For Instances, the following information is displayed:
+     - **Snapshot:** Count of instances where every volume associated with each VM has a point-in-time snapshot.
+     - **Remote Replication:** Count of instances where every volume associated with each VM is replicated.
+     - **Snapshot + Remote Replication:** Count of instances where each associated VM has replicated volumes and every volume has a point-in-time snapshot.
+     - **Unprotected:** Count of instances where each associated VM neither has replicated volumes nor point-in-time snapshot on any volume.
+     - **Partially Protected:** Count of instances where some, but not all, of the instance's VMs have snapshots and can be in remote replication.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json b/corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
new file mode 100644
index 0000000..b5eff77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+  "title": "Hosts / Servers",
+  "ordinal": 43,
+  "parent_title": "Provisioning Concepts",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.html",
+  "topic_cluster": {
+    "clustering_title": "Hosts / Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+        "clustering_title": "Hosts / Servers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E",
+        "clustering_title": "Hosts / Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md b/corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
new file mode 100644
index 0000000..2966bb9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-51BE3C61-0382-41CB-9598-7E2F353C1A0E.md
@@ -0,0 +1,5 @@
+# Hosts / Servers
+
+This concept is mostly tailored to users of VM Essentials who are responsible for managing and maintaining the underlying infrastructure integrations. A Host typically refers to a Docker Host in which a container (within an Instance) is running, or a hypervisor that virtual machines can be provisioned onto. A server is the underlying general representation of a physical or virtual server. It could be a Host representation, a Virtual Machine, or even a Bare Metal delineation.
+
+When a user provisions a VM-based Instance, a corresponding server record is created to represent the link to the actual resource via the underlying provisioning engine. This may seem a bit odd but provides an aspect of VM Essentials that is quite powerful. This singular concept is what allows VM Essentials to ingest “brownfield” environments. We do not need to start clean. VM Essentials can be integrated into existing environments and manage existing virtual machines. The way VM Essentials does this is by periodically syncing existing VMs from the added cloud integrations. A server record will be created and periodically updated (every five minutes, by default) with realtime information and changes. This, in essence, provides CMDB-like capabilities as well. When a server is discovered, the user (given the appropriate access) can convert the virtual machine to a managed Instance. When this is done, a corresponding Instance is made in the provisioning section of VM Essentials and the VM Essentials Agent can optionally be installed to provide more refined guest operating system-level statistics and logging.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json b/corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
new file mode 100644
index 0000000..3516655
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+  "title": "Create Datastore",
+  "ordinal": 369,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html",
+  "topic_cluster": {
+    "clustering_title": "Create Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+        "clustering_title": "Create Datastore"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE",
+        "clustering_title": "Create Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md b/corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
new file mode 100644
index 0000000..7d2d85e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.md
@@ -0,0 +1,42 @@
+# Create Datastore
+
+## About this task
+
+Add a Datastore to the Storage Server.
+
+## Procedure
+
+1. Navigate to Infrastructure > Clusters.
+2. Click into the detail page for the cluster where the datastore is to be created.
+3. Select the Storage tab.
+4. Under the Data Stores sub tab, click + ADD.
+5. From the ADD DATASTORE wizard, input the following: 
+
+   NAME:
+   :   Name of the datastore in HPE Morpheus Enterprise.
+
+   TYPE:
+   :   Select the type of storage system.
+
+   STORAGE SERVER:
+   :   Select the storage server that is created using the ADD STORAGE SERVER wizard.
+
+   PROTOCOL TYPE:
+   :   Select the type of storage protocol.
+
+   RANSOMWARE DETECTION:
+   :   Select the check box to enable ransomware detection for all VMs created with this datastore.
+
+   NOTE
+
+   The datastore creation fails if storage servers other than HPE Alletra Storage MP B10000 are selected along with the Ransomware Detection option.
+
+   CPG
+   :   Use the drop-down list to select a Common Provisioning Group (CPG) for allocating storage to the new datastore.
+6. Click SAVE.
+
+## Results
+
+![Add data store](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-6894A520-8797-40DF-9252-2F696167BA9F-high.png)
+
+The datastore is added and displayed in the Datastore tab. Confirm that its status is healthy.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json b/corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
new file mode 100644
index 0000000..256f76f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+  "title": "Migrations",
+  "ordinal": 231,
+  "parent_title": "Tools",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md b/corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
new file mode 100644
index 0000000..1f75968
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
@@ -0,0 +1,8 @@
+# Migrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html)**
+- **[Migrations Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html)**
+- **[Migrations Plans](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html)**
+- **[Configuring Windows Workloads (Windows 2022 or later) for Migration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.json b/corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.json
new file mode 100644
index 0000000..5f4c4e0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+  "title": "Provisioning Images",
+  "ordinal": 76,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5504862E-8120-469D-8708-2290772E5585.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+        "clustering_title": "Provisioning Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5504862E-8120-469D-8708-2290772E5585",
+        "clustering_title": "Provisioning Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.md b/corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.md
new file mode 100644
index 0000000..6930027
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5504862E-8120-469D-8708-2290772E5585.md
@@ -0,0 +1,13 @@
+# Provisioning Images
+
+When provisioning a system image, VM Essentials will stream the image from Amazon S3 to the target Cloud if the image is not local to the Cloud.
+
+When using images that already exist in the destination Cloud, such as synced or previously copied images, no image stream from S3 through the VM Essentials Appliance to the destination cloud will take place.
+
+NOTE
+
+The VM Essentials Appliance must be able to download from Amazon S3 when provisioning system images.
+
+NOTE
+
+The VM Essentials Appliance must be able reach and resolve the destination Host when provisioning System Images or uploaded Images for the first time. This included being able to resolve ESXi host names in VMware vCenter clouds, and reach the destination ESXi host over port 443.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json b/corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
new file mode 100644
index 0000000..71ff4d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+  "title": "Privileges",
+  "ordinal": 330,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.html",
+  "topic_cluster": {
+    "clustering_title": "Privileges",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+        "clustering_title": "Privileges"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC",
+        "clustering_title": "Privileges"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md b/corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
new file mode 100644
index 0000000..70cdf65
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.md
@@ -0,0 +1,80 @@
+# Privileges
+
+Content Library
+:   - All Content Library privileges
+
+Datastore/Datastore Cluster
+:   - Allocate Space
+    - Browse Datastore
+    - Low Level file Operations
+    - Remove File
+    - Update virtual machine files
+    - Update virtual machine metadata
+
+Distributed Switch
+:   - Port configuration operation
+    - Port setting operation
+
+Global
+:   - Log Event
+    - Manage custom attributes
+    - Set custom attribute
+
+Network
+:   - Assign Network
+    - Configure
+    - Remove
+
+Resource
+:   - Apply recommendation
+    - Assign vApp to resource pool
+    - Assign virtual machine to resource pool
+    - Migrate powered off virtual machine
+    - Migrate powered on virtual machine
+
+Scheduled task
+:   - Create tasks
+    - Modify task
+    - Remove task
+    - Run task
+
+Tasks
+:   - Create task
+    - Update task
+
+Virtual Machine
+:   - Configuration (all)
+    - Guest Operations (all)
+    - Interaction (all)
+    - Inventory (all)
+    - Provisioning (all)
+    - Service configuration (all)
+    - Snapshot management (all)
+    - vSphere Replication (all)
+
+vApp
+:   - Clone
+    - Export
+    - Import
+
+vSphere Tagging
+:   - Assign or Unassign vSphere Tag
+    - Assign or Unassign vSphere Tag on Object
+    - Create vSphere Tag
+    - Create vSphere Tag Category
+    - Delete vSphere Tag
+    - Delete vSphere Tag Category
+    - Edit vSphere Tag
+    - Edit vSphere Tag Category
+    - Modify UsedBy Field For Category
+    - Modify UsedBy Field For Tag
+    - privilege.InventoryService.Tagging.CreateScope.label
+    - privilege.InventoryService.Tagging.DeleteScope.label
+
+With the User and Role created, add permissions to associate the User and Role to the appropriate usage constructs. Navigate to the usage construct you wish to work with, navigate to the permissions tab, click the plus (+) button. In the screenshot below, I’m adding the permission for the vCenter usage construct. The complete list of usages and whether or not to mark the propagation box is below the image.
+
+NOTE
+
+For organization and security purposes, permissions can also be added to folders. This allows VM Essentials to see the folders and onboard any resources within them (if desired). Once the vCenter Cloud integration has been created in VM Essentials, you can view folders from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > ResourcesTab). By editing the folder here (Actions > Edit), folders can be set as the “Default” and/or the “Image Target”. When a folder is set as Default, this folder is pre-selected when provisioning new Instances into the Cloud. When a folder is set as the Image Target, VM Essentials will look into this folder to onboard VMware images into VM Essentials.
+
+![../../../_images/addPerms.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-C8A5BC12-8BBF-47AF-A193-BD89D2392417-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json b/corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
new file mode 100644
index 0000000..a25809f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+  "title": "Instances By Cloud",
+  "ordinal": 12,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.html",
+  "topic_cluster": {
+    "clustering_title": "Instances By Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+        "clustering_title": "Instances By Cloud"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1",
+        "clustering_title": "Instances By Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md b/corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
new file mode 100644
index 0000000..c7551b0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.md
@@ -0,0 +1,5 @@
+# Instances By Cloud
+
+The total number of Clouds which currently have an Instance provisioned is shown. Hover over each section of the pie chart to see the total number and percentage of Instances provisioned to each Cloud
+
+The number of Instances that have existed at any point in the day with additional breakdown to show the number provisioned to each Cloud. This number will include any pre-existing Instances which have carried over from previous days along with any new Instances that were provisioned and existed on that day even for a short time
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json b/corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
new file mode 100644
index 0000000..c3575ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+  "title": "Supported Versions",
+  "ordinal": 334,
+  "parent_title": "Creating a Windows Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+        "clustering_title": "Supported Versions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5571B267-5385-4EEC-A400-FD23FD4B239C",
+        "clustering_title": "Supported Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md b/corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
new file mode 100644
index 0000000..32be7b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.md
@@ -0,0 +1,3 @@
+# Supported Versions
+
+2008R2, 2012, 2012R2, 2016, 2019, 2022
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json b/corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
new file mode 100644
index 0000000..baf0e99
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+  "title": "Linux Agent",
+  "ordinal": 36,
+  "parent_title": "SSH/Winrm",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+        "clustering_title": "Linux Agent"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-55BA17AE-7F27-4832-BADC-D76B073635C6",
+        "clustering_title": "Linux Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md b/corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
new file mode 100644
index 0000000..6e6cdec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-55BA17AE-7F27-4832-BADC-D76B073635C6.md
@@ -0,0 +1,4 @@
+# Linux Agent
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json b/corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
new file mode 100644
index 0000000..5ed5eee
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+  "title": "Virtual Images",
+  "ordinal": 70,
+  "parent_title": "Library",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md b/corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
new file mode 100644
index 0000000..e002e7d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
@@ -0,0 +1,8 @@
+# Virtual Images
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.html)**
+- **[Configuring Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html)**
+- **[Provisioning Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5504862E-8120-469D-8708-2290772E5585.html)**
+- **[Add Virtual Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json b/corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
new file mode 100644
index 0000000..3d8e781
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+  "title": "Role Permissions",
+  "ordinal": 57,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md b/corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
new file mode 100644
index 0000000..7d61926
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.md
@@ -0,0 +1,7 @@
+# Role Permissions
+
+The User Role Permission ‘Provisioning: Tasks FULL’ is required to create, edit and delete Tasks.
+
+**Subtopics**  
+
+- **[Common Options](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json b/corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
new file mode 100644
index 0000000..8c902d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+  "title": "Proxies",
+  "ordinal": 166,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html",
+  "topic_cluster": {
+    "clustering_title": "Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md b/corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
new file mode 100644
index 0000000..fdcd4a7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
@@ -0,0 +1,8 @@
+# Proxies
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.html)**
+- **[Defining Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.html)**
+- **[Cloud Communication](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.html)**
+- **[Provisioning with Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json b/corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
new file mode 100644
index 0000000..0e2965e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+  "title": "Requirements",
+  "ordinal": 27,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md b/corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
new file mode 100644
index 0000000..d025406
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-57765DB0-E6F1-4C31-AEA5-0E52AD61B460.md
@@ -0,0 +1,13 @@
+# Requirements
+
+Provisioning Instances typically involves many steps beyond starting a workload and VM Essentials is centered around automating everything for your application to be fully operational. There is a lot that goes on when spinning up an Instance, and to make the magic happen a few requirements need to be met.
+
+IMPORTANT
+
+By default, Agent Installation is enabled when provisioning unless deselected on the Virtual Image or SKIP AGENT INSTALL is selected from the provisioning wizard.
+
+**Subtopics**  
+
+- **[VM Provision Steps](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.html)**
+- **[Agent Install](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json b/corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
new file mode 100644
index 0000000..217bdab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+  "title": "IP Pools",
+  "ordinal": 154,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html",
+  "topic_cluster": {
+    "clustering_title": "IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md b/corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
new file mode 100644
index 0000000..6d1d323
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
@@ -0,0 +1,8 @@
+# IP Pools
+
+Infrastructure  >  Network  >  IP Pools
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-238F9226-4EB4-4E14-B533-584277951C4B.html)**
+- **[To add a VM Essentials Network Pool](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json b/corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
new file mode 100644
index 0000000..72044d3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+  "title": "GPU Passthrough Example",
+  "ordinal": 135,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html",
+  "topic_cluster": {
+    "clustering_title": "GPU Passthrough Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md b/corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
new file mode 100644
index 0000000..9bf11ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
@@ -0,0 +1,25 @@
+# GPU Passthrough Example
+
+In a previous section, a Service Plan was created which consumes a GPU when a VM is provisioned using that Plan. This section shows an example provisioning a workload using that Plan and a GPU-accelerated workload running on the VM. In this example, there is an Nvidia GeForce RTX 3050 connected to one of the HVM Hosts. By passing the GPU hardware through to a provisioned VM, hardware-accelerated AI workloads can be run on the VM.
+
+Begin by navigating to Provisioning > Instances. The list of all currently-managed Instances is here along with high level information (power state, etc). To begin a new Instance, click + ADD. Choose type HVM and click NEXT. On the next pane, choose the Group and Cloud in which your desired HVM Cluster resides, name the Instance, and click NEXT.
+
+On the CONFIGURE tab, the main thing to note for this example is the PLAN configuration. This dropdown contains some default Plans that are included with HPE Morpheus VM Essentials and compatible with the HVM provisioning technology (named “1 CPU, 1GB Memory”, etc). This dropdown also includes user-created Plans, such as those you’ve created to consume GPU hardware. In the screenshot below, you can see the “GPU Plan” was selected.
+
+![../../_images/showPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-1FD71B7E-138D-4F35-B57F-AA2C3AA2E357-high.png)
+
+From here, complete the Instance provisioning wizard selecting any automation or lifecycle configurations and wait for the Instance provisioning to complete.
+
+With provisioning complete, check the attached device(s) from the HPE Morpheus VM Essentials UI. This is done from the VM level rather than the Instance level. From the Instance detail page, click on the Resources tab. Click on the name of the desired VM to access the VM detail page. Click on the Devices tab. As in the screenshot below, the attached GPU should be shown.
+
+![../../_images/attachedGpu.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5AC07D64-3534-439B-925D-858854858310-high.png)
+
+To go further, open a console session to the new VM either through HPE Morpheus VM Essentials UI or by connecting to the VM over SSH from a local terminal session. Use the `lspci` command to view all devices connected to PCI buses. The attached GPU should be shown here as it is in the UI.
+
+At this point, the VM is ready to run GPU-accelerated workloads normally. To test this, I’ll run Ollama which is an open-source tool designed to make it easy to run large language models (LLMs) locally. In the screenshot below, see the AI chatbot response to an input. This result took only a few seconds thanks to GPU hardware acceleration.
+
+![../../_images/ollamaOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-FEED6AA7-831F-4630-93F2-BD77DAB2EF2C-high.png)
+
+With the request completed, we can run the `ollama ps` command which confirms the model was running under GPU acceleration.
+
+![../../_images/gpuUsed.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-15D2AC03-19A9-47B0-8D16-7EA83603BDF2-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json b/corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
new file mode 100644
index 0000000..b5a0f34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+  "title": "Labels",
+  "ordinal": 52,
+  "parent_title": "Library",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.html",
+  "topic_cluster": {
+    "clustering_title": "Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+        "clustering_title": "Labels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9",
+        "clustering_title": "Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md b/corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
new file mode 100644
index 0000000..b894766
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-58D35AD8-1AE8-4EBC-9DB1-AC6B9C48D4B9.md
@@ -0,0 +1,23 @@
+# Labels
+
+Labels are a categorization feature designed to allow easier filtering of list views in the VM Essentials Library. The following library constructs can be labeled:
+
+- Clouds
+- Groups
+- Tasks
+- Instances
+- Servers
+- Virtual Images
+
+Labels are visible from the list views of any constructs listed above. By default, labels are turned on in the list view but if they aren’t showing, click the gear icon (⚙) and then click Labels to enable them.
+
+The list view contains a row of filters above the list, one of which is Labels. Enter a search string to find an existing label or click the dropdown button within the field to select an existing label. This will filter the list to show only constructs which have the selected label.
+
+NOTE
+
+Any list may be filtered by any label which exists on any construct. When a label is removed from a construct and no other constructs also have that label, VM Essentials will remove the label from the list during its nightly sync. It is normal for a label to continue to exist in this list, even if it’s not currently applied to any constructs, until the next nightly sync has taken place.
+
+**Subtopics**  
+
+- **[Adding and Removing Labels](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.html)**
+- **[Running Automation Against Label Targets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json b/corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
new file mode 100644
index 0000000..16f3998
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+  "title": "Clusters",
+  "ordinal": 96,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html",
+  "topic_cluster": {
+    "clustering_title": "Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md b/corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
new file mode 100644
index 0000000..21b726d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
@@ -0,0 +1,8 @@
+# Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.html)**
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.html)**
+- **[Cluster Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2581C2D1-AC07-4DE2-B794-20AC25652417.html)**
+- **[HVM clusters](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CA806876-1093-4A39-BE62-439C4802A915.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json b/corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
new file mode 100644
index 0000000..5e87774
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+  "title": "Archive Detail Page",
+  "ordinal": 229,
+  "parent_title": "Archives",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.html",
+  "topic_cluster": {
+    "clustering_title": "Archive Detail Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+        "clustering_title": "Archive Detail Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50",
+        "clustering_title": "Archive Detail Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md b/corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
new file mode 100644
index 0000000..b7e89c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.md
@@ -0,0 +1,7 @@
+# Archive Detail Page
+
+The Archive detail contains information about the Archive configuration as well as a list of files currently stored in the Archive. The Archive detail is accessed by navigating to the Archives list page (Tools > Archives) and selecting an existing Archive. As on the Archives List Page, users can download a ZIP folder containing all files in the Archive and edit the Archive from the ACTIONS menu.
+
+To delete the Archive, click DELETE. New files are added by clicking + ADD. When adding a new file, users may browse the file system on the local computer to select a file.
+
+From the files list, download or delete individual files by clicking on the appropriate selection from the ACTIONS menu.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json b/corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
new file mode 100644
index 0000000..27ceb21
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+  "title": "Switch Configuration",
+  "ordinal": 353,
+  "parent_title": "Prerequisites",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.html",
+  "topic_cluster": {
+    "clustering_title": "Switch Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+        "clustering_title": "Switch Configuration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC",
+        "clustering_title": "Switch Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md b/corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
new file mode 100644
index 0000000..ea0514a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5A273A29-5686-4D44-A5BF-CE8B5A3C4ECC.md
@@ -0,0 +1,53 @@
+# Switch Configuration
+
+## Procedure
+
+1. Configure the management interface and IP address on both switches in the pair
+2. The switch pair must be configured with `vsx-sync` enabled for high availability and redundancy 
+
+   Sample configuration:
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role primary  
+       keepalive peer 192.168.0.1 source 192.168.0.0  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role secondary  
+       keepalive peer 192.168.0.0 source 192.168.0.1  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+3. Create a Multi-Chassis Link Aggregation Group (MC-LAG) between the ArubaCX switch and the upstream network, referred to as `lag1`
+4. Configure the `lag1` interface on both switches in the pair Sample configuration: 
+
+   ```
+   ```
+   interface lag 1 multi-chassis  
+       no shutdown  
+       no routing  
+       vlan trunk native 1  
+       vlan trunk allowed 1,175  
+       lacp mode active  
+       loop-protect
+   ```
+   ```
+5. The switch ports connected to the server’s management interfaces should be set to “Trunk mode” with a “Native VLAN” Sample configuration: 
+
+   ```
+   ```
+   interface 1/1/1  
+   no shutdown  
+   no routing  
+   vlan trunk native 175  
+   vlan trunk allowed 175
+   ```
+   ```
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json b/corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
new file mode 100644
index 0000000..dba0174
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+  "title": "Deployment Guide",
+  "ordinal": 3,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.html",
+  "topic_cluster": {
+    "clustering_title": "Deployment Guide",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+        "clustering_title": "Deployment Guide"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63",
+        "clustering_title": "Deployment Guide"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md b/corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
new file mode 100644
index 0000000..98a5dbc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.md
@@ -0,0 +1,3 @@
+# Deployment Guide
+
+Deployment, installation, and initialization information is not contained in this user manual. Please refer to our dedicated HPE Morpheus VM Essentials Software [Deployment Guide](https://www.hpe.com/support/morpheus-vm-essentials-deployment-guide) for information on setting up the product and getting started with the first HVM Cluster.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json b/corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
new file mode 100644
index 0000000..56aa460
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+  "title": "tfvars",
+  "ordinal": 218,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.html",
+  "topic_cluster": {
+    "clustering_title": "tfvars",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+        "clustering_title": "tfvars"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722",
+        "clustering_title": "tfvars"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md b/corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
new file mode 100644
index 0000000..c22b34a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5C4A25A0-2184-4B3D-B0EF-34E6950D9722.md
@@ -0,0 +1,20 @@
+# tfvars
+
+A mountpoint to store tfvars files for Terraform App Blueprints.
+
+Key
+:   Pattern “tfvars/key”
+
+    Example: tfvars/my-aws-account
+
+Value
+:   The values for your tfvars file to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES and the stored values will be available for use.
+
+NOTE
+
+You may also see Cloud profiles stored at the tfvars mountpoint. They will have a key pattern like: “tfvars/profile/cloud/$cloudCode/variables”. Terraform Cloud profiles are created on the Cloud detail page (Infrastructure > Clouds > selected Cloud) under the Profiles tab. They allow Terraform apps and specs to be provisioned across multiple Clouds that require differed tfvars. See the [Cloud profiles](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/profiles.html) page for more.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json b/corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
new file mode 100644
index 0000000..1fa1cce
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+  "title": "Groups",
+  "ordinal": 80,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html",
+  "topic_cluster": {
+    "clustering_title": "Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md b/corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
new file mode 100644
index 0000000..4071711
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
@@ -0,0 +1,13 @@
+# Groups
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2794BD60-D1CC-4B0B-80FA-1BA80DDEBB27.html)**
+- **[UI](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4FFAB8A2-FFE8-45B3-9160-DAD8C21D03AE.html)**
+- **[CLI](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.html)**
+- **[API](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.html)**
+- **[Adding Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.html)**
+- **[Managing Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3E3C6410-58E6-4DF1-BD62-FF676EF52704.html)**
+- **[Edit Group](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.html)**
+- **[Delete Group](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.html)**
+- **[User Access](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-45E27A14-72ED-4C94-8E75-F7D5CC8E7B5A.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json b/corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
new file mode 100644
index 0000000..4faf292
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+  "title": "Network Groups",
+  "ordinal": 147,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md b/corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
new file mode 100644
index 0000000..8d0095e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
@@ -0,0 +1,7 @@
+# Network Groups
+
+Network Groups are useful for grouping networks during provisioning and scaling or grouping availability subnets together such that during provisioning vm’s within an instance can be round robin provisioned across availability zones.
+
+**Subtopics**  
+
+- **[Adding Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1411B76F-83AF-45D2-B7AC-FD6D82F76DB2.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json b/corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
new file mode 100644
index 0000000..9416b7d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+  "title": "Delete Key Pair",
+  "ordinal": 201,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+        "clustering_title": "Delete Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1",
+        "clustering_title": "Delete Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md b/corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
new file mode 100644
index 0000000..a368fb7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.md
@@ -0,0 +1,11 @@
+# Delete Key Pair
+
+## About this task
+
+To Delete Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected key pair
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json b/corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
new file mode 100644
index 0000000..cd7e006
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+  "title": "Provisioning Settings",
+  "ordinal": 277,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+        "clustering_title": "Provisioning Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C",
+        "clustering_title": "Provisioning Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md b/corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
new file mode 100644
index 0000000..f0e3bd2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.md
@@ -0,0 +1,29 @@
+# Provisioning Settings
+
+Allow Cloud Selection
+:   Displays or hides Cloud Selection dropdown in Provisioning wizard.
+
+Allow Host Selection
+:   Displays or hides Host Selection dropdown in Provisioning wizard.
+
+Require Environment Selection
+:   Forces users to select and Environment during provisioning
+
+Hide Datastore Stats On Selection
+:   Hides Datastore utilization and size stats in provisioning and app wizards
+
+Cross-Tenant Naming Policies
+:   Enable for the `sequence` value in naming policies to apply across tenants
+
+Reuse Naming Sequence Numbers
+:   When selected, sequence numbers can be reused when Instances are removed. Deselect this option and VM Essentials will track issued sequence numbers and use the next available number each time.
+
+Show Console Keyboard Layout Settings
+:   When enabled Users will see keyboard layout settings in console sessions
+
+Deployment Archive Store
+:   Default Storage Provider for storing Deployment Archives.
+
+    NOTE
+
+    Storage Providers can be configured and managed in the Infrastructure  >  Storage section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json b/corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
new file mode 100644
index 0000000..25d097b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+  "title": "UUID",
+  "ordinal": 220,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.html",
+  "topic_cluster": {
+    "clustering_title": "UUID",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+        "clustering_title": "UUID"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5",
+        "clustering_title": "UUID"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md b/corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
new file mode 100644
index 0000000..9fefb19
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-5F75E5AF-90D3-4F85-B937-F98415300AC5.md
@@ -0,0 +1,20 @@
+# UUID
+
+A Cypher UUID Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+Key
+:   Pattern “uuid/key”
+
+    - Example: uuid/myuuid
+
+Value
+:   Leave the Value filed blank for UUID, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the UUID will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate UUID.
+
+To delete the UUID, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json b/corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
new file mode 100644
index 0000000..d2b5066
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+  "title": "Overview",
+  "ordinal": 91,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md b/corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
new file mode 100644
index 0000000..0e60a08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.md
@@ -0,0 +1,3 @@
+# Overview
+
+In VM Essentials, a Cloud represents a grouping of HVM clusters (referred to as a “Private Cloud”) or an integration with a VMware vCenter appliance. This section describes general information about the Clouds construct and UI pages for Clouds. See the VMware integration guide for more specific details on integrating with VMware and the features supported by VM Essentials.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json b/corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
new file mode 100644
index 0000000..56506c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+  "title": "Create New Router",
+  "ordinal": 151,
+  "parent_title": "Routers",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-61053EC5-4910-454F-8B71-6B06408A6451.html",
+  "topic_cluster": {
+    "clustering_title": "Create New Router",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+        "clustering_title": "Create New Router"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-61053EC5-4910-454F-8B71-6B06408A6451",
+        "clustering_title": "Create New Router"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md b/corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
new file mode 100644
index 0000000..fabff5e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-61053EC5-4910-454F-8B71-6B06408A6451.md
@@ -0,0 +1,8 @@
+# Create New Router
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click + ADD
+3. Select the router type and complete the fields on the resulting modal
+4. Once complete, click ADD NETWORK ROUTER
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json b/corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
new file mode 100644
index 0000000..cba37d4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+  "title": "HVM Cluster Networking",
+  "ordinal": 109,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Cluster Networking",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+        "clustering_title": "HVM Cluster Networking"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F",
+        "clustering_title": "HVM Cluster Networking"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md b/corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
new file mode 100644
index 0000000..220d65f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.md
@@ -0,0 +1,49 @@
+# HVM Cluster Networking
+
+On initial cluster provisioning, OVS bridges and Libvirt Networks are created and are immediately ready for VM provisioning. However, when adding new network interfaces, you need to create networking objects in the UI manually. Currently, the HPE Morpheus VM Essentials Software Manager does not discover new interfaces that are not in netplan. You will need to ensure they are available in the `01-base.yml` netplan file, apply it, create the bonds in the `hpe-vm` tool, and then refresh the HVM Cluster through the UI. For details, refer the installation section at the beginning of this documentation repository for more information on the `hpe-vm` tool and its use.
+
+HVM network objects are created from the Network tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the HVM Cluster). Two subtabs are shown here for Routers and Networks. From a KVM perspective, OVS Bridges and Libvirt Networks (without any port groups) are created on the Routers subtab. Port Group entries are added to existing Libvirt Networks on the Networks subtab. For this reason, it is often most logical to begin creating new HVM network objects on the Routers subtab before moving onto the Networks subtab. For a higher level discussion and diagram of recommended HVM Cluster network topology and to see where these objects fit in, refer to the example network configurations in the "Getting Started" section of this user manual.
+
+Adding Routers
+
+1. From the Routers subtab, click + ADD, then select OVS Bridge Domain
+
+   ![The list of router objects associated with an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-BBBDCD20-D1FA-4F83-99A8-84F136F334AF-high.png)
+2. On the ADD NETWORK ROUTER modal, configure the following:
+
+   1. **GROUP:** Select "Shared" to make the router object available to all Groups or select an individual Group
+   2. **NAME:** A name for the router object in HPE Morpheus VM Essentials Software
+   3. **HOST BRIDGE:** Select an existing OVS bridge or choose "Create New"
+   4. **BRIDGE NAME:** Shown only when opting to create a new Host Bridge. Provide a name for the new OVS bridge to be created. The bridge name value entered here will be used to identify the bridge throughout the UI while examining the created objects via a terminal session connected to the Host will show it identified by the interface name
+   5. **NETWORK INTERFACE:** Shown only when opting to create a new Host Bridge. Select a network interface for the new OVS bridge. Keep in mind that currently new interfaces are not discovered automatically. See the opening paragraph of this section for more information on surfacing the new interface to the HVM Cluster
+
+   NOTE
+
+   By adding a router here and selecting an existing OVS bridge, a new Libvirt Network is created without any port groups but no new OVS bridge is created. When selecting "Create New" in the Host Bridge configuration field, a new OVS bridge is created and a new Libvirt Network is also created without any port groups. A free physical interface or bond must be available to create a new OVS bridge and currently these are not automatically discovered by the HVM Cluster. See the opening paragraph of this section for more information on surfacing new interfaces to the HVM Cluster. Libvirt Port Groups are created in the next section on adding networks. For a higher level discussion and diagram of recommended HVM Cluster network topology and to see where these objects fit in, refer back to the example network configurations in the "Getting Started" section of this user manual.
+3. Click ADD NETWORK ROUTER
+
+   ![Adding new router with host bridge created](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-8F3EFC34-3BE1-4E35-B563-E7168F483CC1-high.png)
+
+Once saved, the router object is created and it appears in the list of current routers.
+
+Adding Networks
+
+As mentioned in the previous section, creating network objects on HVM clusters is akin to adding Libvirt Portgroups to an existing Libvirt Network. If continuing from the previous section on adding routers, the OVS bridges and Libvirt networks will be in place to add port groups (referred to as networks here in the UI).
+
+1. From the Networks subtab, click + ADD, then select OVS Port Group
+
+   ![The list of network objects associated with an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-8A44146F-1F64-441D-A007-F3BEC320E60C-high.png)
+2. On the CREATE NETWORK modal, configure the following:
+
+   1. **GROUP:** Select "Shared" to make the router object available to all Groups or select an individual Group
+   2. **NAME:** A name for the network object in HPE Morpheus VM Essentials Software
+   3. **CIDR:** The CIDR range for the new network
+   4. **GATEWAY:** The network gateway address
+   5. **DNS PRIMARY:** The address for the primary DNS server
+   6. **DNS SECONDARY:** The address for the secondary DNS server
+   7. **ROUTER:** Select an existing OVS bridge. If you need to create a new OVS bridge, add a new "OVS Bridge Domain" from the Routers subtab (described above) and select "Create New" for it's "Host Bridge" field configuration. Additional details on router objects are provided above.
+   8. **VLAN ID:** A VLAN ID for the Libvirt Port Group to be created
+   9. **NETWORK POOL:** A typeahead field for selecting a currently-configured IP Pool
+3. Click SAVE CHANGES
+
+   ![Creating a new network object](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-6359D4EE-C3F8-431F-850D-A21F7470714E-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json b/corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
new file mode 100644
index 0000000..4366d59
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+  "title": "Overview",
+  "ordinal": 238,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md b/corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
new file mode 100644
index 0000000..fe04374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.md
@@ -0,0 +1,3 @@
+# Overview
+
+VM Essentials can integrate with many of the most common identity source technologies, such as Active Directory, Okta, and many others. These can be configured via the Identity Sources button on the Users list page (Administration > Users). These integrations map roles within these sign-on tools to equivalent roles in VM Essentials so at first log in users are assigned the appropriate role.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json b/corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
new file mode 100644
index 0000000..b88e475
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+  "title": "A Note on Proxies",
+  "ordinal": 346,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.html",
+  "topic_cluster": {
+    "clustering_title": "A Note on Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+        "clustering_title": "A Note on Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8",
+        "clustering_title": "A Note on Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md b/corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
new file mode 100644
index 0000000..df2d60c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.md
@@ -0,0 +1,25 @@
+# A Note on Proxies
+
+Proxy configurations are known to vary in some organizations and makes building a base blueprint a little more difficult. In order to fully configure proxies a few environment variables must be set in the /etc/environment file (This can be done automatically in a default user-data script for cloud-init as well in edit cloud).
+
+```
+```
+http_proxy="http://myproxyaddress:8080"  
+https_proxy="http://myproxyaddress:8080"  
+ftp_proxy="http://myproxyaddress:8080"  
+no_proxy=127.0.0.1,localhost,applianceUrl  
+https_no_proxy=127.0.0.1,localhost,applianceUrl
+```
+```
+
+IMPORTANT
+
+It is very important to properly set the no\_proxy list (applianceUrl) should be replaced with the actual appliance url. In future releases, morpheus plans to automatically take care of this.
+
+NOTE
+
+If using cloud-init agent install mode these settings need to be set in the custom Cloud-Init User data section of “Edit Cloud” or “Edit Virtual Image”
+
+IMPORTANT
+
+If using this virtual machine as a docker host, proxy settings must also be configured in the docker config. See Docker guides for instructions on how to properly set this. If necessary this can be wrapped in a task automation workflow for your own use.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json b/corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
new file mode 100644
index 0000000..28e06e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+  "title": "Getting Started",
+  "ordinal": 317,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md b/corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
new file mode 100644
index 0000000..c05c099
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.md
@@ -0,0 +1,23 @@
+# Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow VM Essentials to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json b/corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
new file mode 100644
index 0000000..d75a804
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+  "title": "Supported Bucket Types",
+  "ordinal": 178,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Bucket Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+        "clustering_title": "Supported Bucket Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A",
+        "clustering_title": "Supported Bucket Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md b/corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
new file mode 100644
index 0000000..4f07b51
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6340CE53-91CA-4D7F-B8DB-E5B2BDEA701A.md
@@ -0,0 +1,9 @@
+# Supported Bucket Types
+
+- Alibaba
+- Amazon S3
+- Azure
+- Google Cloud Storage
+- Openstack Swift
+- Rackspace CDN
+- Generic S3
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json b/corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
new file mode 100644
index 0000000..63e18c1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+  "title": "Hardware Requirements",
+  "ordinal": 105,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-634760AA-7E46-42A7-AD08-85CCE4656873.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+        "clustering_title": "Hardware Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-634760AA-7E46-42A7-AD08-85CCE4656873",
+        "clustering_title": "Hardware Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md b/corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
new file mode 100644
index 0000000..4e65f2b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-634760AA-7E46-42A7-AD08-85CCE4656873.md
@@ -0,0 +1,36 @@
+# Hardware Requirements
+
+- **Operating System**: Ubuntu 24.04 or Ubuntu 22.04
+- **CPU**: One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory**: 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
+- **Disk Space**: For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while VM Essentials will configure Ceph for multi-node clusters
+- **Network Connectivity**: HVM hosts must be assigned static IP addresses. They also need DNS resolution of the VM Essentials appliance and Internet access in order to download and install system packages for dependencies, such as KVM, Open vSwitch (OVS), and more
+
+NOTE
+
+Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.
+
+NOTE
+
+Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus VM Essentials Agent communication with the HPE Morpheus VM Essentials manager | HVM Host | HPE Morpheus VM Essentials manager | 443 | TCP |
+| HPE Morpheus VM Essentials Agent communication with the HVM Host for hypervisor console | HPE Morpheus VM Essentials manager | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus VM Essentials manager | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus VM Essentials manager SSH access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTP) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus VM Essentials manager WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus VM Essentials manager | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json b/corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
new file mode 100644
index 0000000..1fff811
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+  "title": "Supported Datastore Types",
+  "ordinal": 111,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-63ADF495-37BF-424E-85F4-614EE91DA301.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Datastore Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+        "clustering_title": "Supported Datastore Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-63ADF495-37BF-424E-85F4-614EE91DA301",
+        "clustering_title": "Supported Datastore Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md b/corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
new file mode 100644
index 0000000..f2f12c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-63ADF495-37BF-424E-85F4-614EE91DA301.md
@@ -0,0 +1,12 @@
+# Supported Datastore Types
+
+In relation to HVM Clusters, discussion of storage primarily centers around datastores, which serve as targets for holding virtual machine disks and storing images. Currently, six datastore types are supported with HVM Clusters:
+
+- Directory Pools
+- NFS Pools
+- GFS2 Pools
+- 3Par
+- HPE Alletra Block Storage HVM
+- HPE Alletra Block Storage Bare Metal
+
+The next several sections will cover Directory Pools, NFS Pools, and GFS2 Pools in detail, including pros and cons of each type, how to configure storage servers, and how to add new datastores through the UI. For more on integrating 3Par servers and HPE Alletra Storage, see the integration guides for those technologies elsewhere in this user manual.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json b/corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
new file mode 100644
index 0000000..cedacef
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+  "title": "Advanced Options (Search Domains)",
+  "ordinal": 143,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced Options (Search Domains)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+        "clustering_title": "Advanced Options (Search Domains)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E",
+        "clustering_title": "Advanced Options (Search Domains)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md b/corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
new file mode 100644
index 0000000..bb521c8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-63B0F6F4-69CA-40C1-997E-949DD702C77E.md
@@ -0,0 +1,3 @@
+# Advanced Options (Search Domains)
+
+Search domains are appended to DNS searches when a **non** fully qualified domain name (short name) is queried. Search domains can be entered as comma separated values, which will be added to DNS configurations, such as /etc/resolv.conf. These domains are injected through cloud-init or other method chosen for the virtual image.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json b/corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
new file mode 100644
index 0000000..5fd54da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+  "title": "Setting Heartbeat Datastores",
+  "ordinal": 119,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-64001B38-0509-46D5-854E-3A8500798DEE.html",
+  "topic_cluster": {
+    "clustering_title": "Setting Heartbeat Datastores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+        "clustering_title": "Setting Heartbeat Datastores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-64001B38-0509-46D5-854E-3A8500798DEE",
+        "clustering_title": "Setting Heartbeat Datastores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md b/corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
new file mode 100644
index 0000000..079c15a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-64001B38-0509-46D5-854E-3A8500798DEE.md
@@ -0,0 +1,13 @@
+# Setting Heartbeat Datastores
+
+While not set by default, after creating a datastore, users may choose to set it as a heartbeat datastore. Heartbeat datastores are essential for high-availability failover of VMs in the HVM Cluster. When heartbeat targets are enabled, each HVM Host continuously updates a heartbeat file, which is monitored by the other Hosts. When a Host becomes unavailable, the remaining Hosts detect this by discovering that the heartbeat file is no longer being updated. At that point, the Cluster initiates a failover process to migrate affected VMs to a new host. For greater detail on high-availability and the failover process, see [this knowledge article](https://cdn.support.hpe.com/hpesc/public/docDisplay?docId=sf000111669en_us&docLocale=en_US).
+
+To set selected datastores as heartbeat targets, use the steps below. Multiple heartbeat datastores can be enabled for additional redundancy:
+
+1. Navigate to Infrastructure > Clusters
+2. Click on the Storage tab and then the Data Stores subtab
+3. Within the Data Stores subtab, edit the desired datastore (pencil icon)
+4. Mark the box labeled "HEARTBEAT TARGET
+5. Click Save changes
+
+![Editing a GFS2 datastore to make it a heartbeat datastore](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5ACF121C-3475-4BFB-8794-ED483A879314-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.json b/corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
new file mode 100644
index 0000000..f12133b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+  "title": "Setting the default domain on a Network",
+  "ordinal": 164,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-650706CA-915E-4239-9D69-35902E82B60E.html",
+  "topic_cluster": {
+    "clustering_title": "Setting the default domain on a Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+        "clustering_title": "Setting the default domain on a Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-650706CA-915E-4239-9D69-35902E82B60E",
+        "clustering_title": "Setting the default domain on a Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.md b/corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
new file mode 100644
index 0000000..cd46239
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-650706CA-915E-4239-9D69-35902E82B60E.md
@@ -0,0 +1,9 @@
+# Setting the default domain on a Network
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network.
+2. Edit the target Network.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json b/corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
new file mode 100644
index 0000000..4466e2f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+  "title": "System Images",
+  "ordinal": 73,
+  "parent_title": "Configuring Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6549D43B-D0BB-4416-9771-AF11F387B629.html",
+  "topic_cluster": {
+    "clustering_title": "System Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+        "clustering_title": "System Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6549D43B-D0BB-4416-9771-AF11F387B629",
+        "clustering_title": "System Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md b/corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
new file mode 100644
index 0000000..1b21425
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6549D43B-D0BB-4416-9771-AF11F387B629.md
@@ -0,0 +1,7 @@
+# System Images
+
+System Virtual Images are pre-configured with metadata and have Cloud-Init or Cloudbase-Init installed. These images are ready to be provisioned with no configuration necessary, however it is required to populate Administration > Settings > Provisioning, Cloud-Init section, with user data as well as User Profile(s) users data when creating additional users prior to provisioning, as the user data from these sections is required when provisioning System provided Virtual Images.
+
+NOTE
+
+System Images settings are not editable.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json b/corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
new file mode 100644
index 0000000..33b80d4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+  "title": "HVM Cluster Storage",
+  "ordinal": 110,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Cluster Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+        "clustering_title": "HVM Cluster Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F",
+        "clustering_title": "HVM Cluster Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md b/corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
new file mode 100644
index 0000000..7dd805a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.md
@@ -0,0 +1,14 @@
+# HVM Cluster Storage
+
+**Subtopics**  
+
+- **[Supported Datastore Types](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-63ADF495-37BF-424E-85F4-614EE91DA301.html)**
+- **[Datastore Types Pros and Cons](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A1E79BA5-CE31-4357-878E-11464E03158C.html)**
+- **[Directory Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.html)**
+- **[Adding Directory Pools](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-15A15A8F-1BCA-4B74-A3C1-08B3F6CCF487.html)**
+- **[NFS Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-15AD88B3-D66A-4CA8-87DB-5F7FDDB9B386.html)**
+- **[Adding NFS Pools](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.html)**
+- **[GFS2 Pools Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.html)**
+- **[Adding GFS2 Pools](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3702D75B-9505-40D0-B220-7739F5F72760.html)**
+- **[Setting Heartbeat Datastores](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-64001B38-0509-46D5-854E-3A8500798DEE.html)**
+- **[Maintaining GFS2 Consistency and High Availability](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B3241978-4E00-4630-A8AB-E597193E51E2.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json b/corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
new file mode 100644
index 0000000..4dc329c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+  "title": "For All Agent Install modes",
+  "ordinal": 34,
+  "parent_title": "Agent Install Modes",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-69626666-7280-4AF5-9871-FA2D82CED05E.html",
+  "topic_cluster": {
+    "clustering_title": "For All Agent Install modes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+        "clustering_title": "For All Agent Install modes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-69626666-7280-4AF5-9871-FA2D82CED05E",
+        "clustering_title": "For All Agent Install modes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md b/corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
new file mode 100644
index 0000000..d42267b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-69626666-7280-4AF5-9871-FA2D82CED05E.md
@@ -0,0 +1,20 @@
+# For All Agent Install modes
+
+When an Instance is provisioned and the Agent does not install, verify the following for any agent install mode:
+
+- The VM Essentials `appliance_url` (Administration > Settings) is both reachable and resolvable from the provisioned node.
+- The `appliance_url` begins with to `https://`, not `http://`.
+
+NOTE
+
+Be sure to use `https://` even when using an IP address for the appliance.
+
+- Inbound connectivity access to the VM Essentials Appliance from provisioned VMs and HVM cluster hosts on port 443 (needed for Agent communication)
+- Private images (those not provided with VM Essentials by default) must have their credentials entered. These can be entered or edited in the Library > Virtual Images section by clicking the edit button (pencil icon) next to the appropriate image.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced section during provisioning. IP Pools can also be created in the Infrastructure > Network > IP Pools section and added any Cloud’s network section for IPAM.
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the VM Essentials appliance can be used.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json b/corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
new file mode 100644
index 0000000..e151a44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+  "title": "Deleting Clouds",
+  "ordinal": 95,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+        "clustering_title": "Deleting Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-69CE737F-F442-4C04-8B1A-8881930B69AE",
+        "clustering_title": "Deleting Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md b/corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
new file mode 100644
index 0000000..1902510
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.md
@@ -0,0 +1,17 @@
+# Deleting Clouds
+
+## About this task
+
+To delete a Cloud:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Clouds link in the sub navigation bar.
+3. Click the Delete icon of the cloud to delete.
+
+## Results
+
+IMPORTANT
+
+All Instances, managed Hosts and VMs must be removed prior to deleting a Cloud.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json b/corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
new file mode 100644
index 0000000..ac477c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+  "title": "Dell EMC ECS Buckets",
+  "ordinal": 183,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.html",
+  "topic_cluster": {
+    "clustering_title": "Dell EMC ECS Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+        "clustering_title": "Dell EMC ECS Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67",
+        "clustering_title": "Dell EMC ECS Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md b/corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
new file mode 100644
index 0000000..050fa0d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6B35AE72-3D19-447A-A19D-D96DDD769B67.md
@@ -0,0 +1,84 @@
+# Dell EMC ECS Buckets
+
+## About this task
+
+NOTE
+
+A Dell EMC ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell EMC ECS Bucket.
+
+To Add a Dell EMC ECS Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell EMC ECS bucket.
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json b/corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
new file mode 100644
index 0000000..fa3b8e5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+  "title": "Adding Tasks",
+  "ordinal": 66,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6B80D87B-8461-414D-9172-07E68896EB06.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+        "clustering_title": "Adding Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6B80D87B-8461-414D-9172-07E68896EB06",
+        "clustering_title": "Adding Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md b/corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
new file mode 100644
index 0000000..589fa10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6B80D87B-8461-414D-9172-07E68896EB06.md
@@ -0,0 +1,20 @@
+# Adding Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. On the Tasks tab, click the Add button
+3. From the New Task Wizard input a name for the task
+4. Select the type of task from from the type dropdown
+5. Input the appropriate configuration details. These will vary based on the selected Task type.
+6. Once done, click SAVE CHANGES
+
+## Results
+
+TIP
+
+When writing a Task config, it’s often necessary to reference VM Essentials variables which pertain to the specific Instance the Task is being run against. VM Essentials includes a pop-out column along the right side of the Add/Edit Task modal which lists available variables. Click and drag the relevant variable into the config area and VM Essentials will automatically fill in the variable call formatted for the currently chosen Task type. See the screenshot below.
+
+TIP
+
+When writing a Task that calls back into the HPE Morpheus VM Essentials API, pass an `Authorization: Execution <%=executionLeaseToken%>` header. The system API will authenticate against that during the life of the Task execution only. This is preferred over other methods of authorizing Task calls as there was a risk of the token expiring in the middle of the Task run.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json b/corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
new file mode 100644
index 0000000..6446a75
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+  "title": "Editing volumes",
+  "ordinal": 376,
+  "parent_title": "Volumes tab",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.html",
+  "topic_cluster": {
+    "clustering_title": "Editing volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+        "clustering_title": "Editing volumes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048",
+        "clustering_title": "Editing volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md b/corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
new file mode 100644
index 0000000..47a1e2c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6B9A77F8-731B-43A1-92C8-0163E20D8048.md
@@ -0,0 +1,28 @@
+# Editing volumes
+
+## About this task
+
+You can edit the volumes individually for VMs created without selecting the Ransomware Detection check box in the ADD DATA STORE screen.
+
+## Procedure
+
+1. Create a datastore without selecting the Ransomware Detection check box. 
+
+   To create a datastore, go to Infrastructure > Clusters, click the cluster name, then click Storage > Add. For more information on creating a datastore, see [Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE.html).
+2. Create a VM with the Ransomware Detection disabled datastore.
+
+   To begin provisioning a VM instance with the Ransomware Detection disabled datastore, go to Provisioning > Instances. For more information on creating a VM instance, see .
+3. Navigate to Infrastructure > Storage > Servers > Volumes tab.
+
+   The Actions drop-down menu is available for each volume that has the Ransomware Detection disabled.
+
+   NOTE
+
+   For VMs created with Ransomware Detection enabled datastore, the Actions drop-down is not displayed for such volumes.
+4. Click Actions > Edit.
+
+   The EDIT VOLUME message is displayed.
+
+   ![Edit volume](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-79282845-7740-4731-9DAF-BDAA8AC698BB-high.png)
+5. To change the status, select the Ransomware Detection check box if it is disabled or clear the check box if it is enabled.
+6. Click Save. The changes to the ransomware monitoring are saved.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json b/corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
new file mode 100644
index 0000000..e15dbe6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+  "title": "CLI",
+  "ordinal": 83,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.html",
+  "topic_cluster": {
+    "clustering_title": "CLI",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+        "clustering_title": "CLI"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D",
+        "clustering_title": "CLI"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md b/corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
new file mode 100644
index 0000000..482c2c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6C50C87E-7063-4E69-96AF-7A7CC7E7CF8D.md
@@ -0,0 +1,3 @@
+# CLI
+
+To view all groups: `groups list`. To use the group: `groups use <id>` or `groups use "group name"` To get a JSON output of a specific group: `groups get <id> -j` or `groups get "group name" -j`
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json b/corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
new file mode 100644
index 0000000..0afeccf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+  "title": "Vault",
+  "ordinal": 222,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.html",
+  "topic_cluster": {
+    "clustering_title": "Vault",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+        "clustering_title": "Vault"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047",
+        "clustering_title": "Vault"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md b/corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
new file mode 100644
index 0000000..4b13859
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6CB8AD5D-CE8B-42B1-9D62-7371B2BC0047.md
@@ -0,0 +1,25 @@
+# Vault
+
+Use this mountpoint to store Cypher secrets in a Hashicorp Vault server backend rather than VM Essentials. Additionally, you can call secrets stored in Vault from this Cypher mountpoint even if they are only saved there and not listed in the VM Essentials Cypher UI. This requires installation and configuration of the Hashicorp Vault plugin. See the YouTube video embedded in this section for more information on adding the plugin, configuration, and a demonstration of its capabilities.
+
+NOTE
+
+It’s recommended that you use a long-lived token as attempts to call Vault-stored values into Tasks will stop working if the token is no longer good. In such a case you’d have to obtain a new token, delete the Cypher entry with the old token, and create a new one to restore functionality once again. Using a long-lived token will prevent the need to do this often.
+
+Key
+:   Pattern “vault/<engineMount>/<secretPath>/data/<key>” (ex. vault/KV2/secret/data/morpheus/lab)
+
+Value
+:   Enter your key/value pair here in valid JSON (ex. {“hello”: “world”} )
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES. The example BASH script below onboards the value stored in Vault from the secret/data/morpheus/lab mountpoint:
+
+```
+```
+from_vault="<%= cypher.read('vault/KV2/secret/data/morpheus/lab') %>"  
+echo $from_vault
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json b/corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
new file mode 100644
index 0000000..c7bc2ab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+  "title": "Agent Install",
+  "ordinal": 32,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+        "clustering_title": "Agent Install"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD",
+        "clustering_title": "Agent Install"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md b/corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
new file mode 100644
index 0000000..42699ec
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6DB649A1-ECB0-4341-A395-FBB24F386BFD.md
@@ -0,0 +1,18 @@
+# Agent Install
+
+When provisioning an Instance, there are some network and configuration requirements to successfully install the Agent. Typically when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach VM Essentials, or depending on Agent install mode, VM Essentials is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the VM Essentials Appliance via the `appliance_url` set in Administration > Settings over both 443 and 80. When an Instance is provisioned from VM Essentials, it must be able to reach the VM Essentials appliance via the `appliance_url` or the Agent will not be installed.
+
+In addition to the main `appliance_url` in Administration > Settings, additional `appliance_urls` can be set per Cloud in the Advanced options of the Cloud configuration pane when creating or editing a Cloud. When this field is populated, it will override the main appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The VM Essentials current log, located at `/var/log/morpheus/morpheus-ui/current`, is very helpful when troubleshooting Agent installations.
+
+**Subtopics**  
+
+- **[Agent Install Modes](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.html)**
+- **[SSH/Winrm](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2F46F59C-22A3-4416-AC2A-BE1522B152D2.html)**
+- **[VMware tools (vmtools) RPC mode](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.html)**
+- **[Cloud-Init Agent install mode](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json b/corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
new file mode 100644
index 0000000..732f5c4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+  "title": "Agent Install Modes",
+  "ordinal": 33,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install Modes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+        "clustering_title": "Agent Install Modes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076",
+        "clustering_title": "Agent Install Modes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md b/corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
new file mode 100644
index 0000000..4e32bf7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6DFEB5BD-002C-4C1A-B22B-2549A4416076.md
@@ -0,0 +1,11 @@
+# Agent Install Modes
+
+There are 3 Agent install modes:
+
+- SSH/WinRM
+- VMware Tools
+- Cloud-init
+
+**Subtopics**  
+
+- **[For All Agent Install modes](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-69626666-7280-4AF5-9871-FA2D82CED05E.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json b/corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
new file mode 100644
index 0000000..306834e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+  "title": "Summary",
+  "ordinal": 209,
+  "parent_title": "Backups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.html",
+  "topic_cluster": {
+    "clustering_title": "Summary",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+        "clustering_title": "Summary"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4",
+        "clustering_title": "Summary"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md b/corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
new file mode 100644
index 0000000..5d8454a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-6FA46501-9D20-4BC5-82E4-75CA97D073A4.md
@@ -0,0 +1,12 @@
+# Summary
+
+The Backups Summary section shows the following metrics:
+
+- Number of Configured Backups trend
+- Backup Success Rate
+- Number of Completed Backups
+- Number of Failed Backups
+- Total Size of Backups (MB) trend
+- Upcoming and In Progress Backups
+
+If a User’s Role permission for Backups is set to User, the user will only see metrics for backups they own.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json b/corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
new file mode 100644
index 0000000..a148043
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+  "title": "Overview",
+  "ordinal": 240,
+  "parent_title": "Plans",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-712F2BB4-F856-419F-BB88-2E137DD46F72",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md b/corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
new file mode 100644
index 0000000..0b37c22
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-712F2BB4-F856-419F-BB88-2E137DD46F72.md
@@ -0,0 +1,11 @@
+# Overview
+
+Service Plans determine the amount of compute resources available to each Instance. When provisioning new Instances from VM Essentials, a plan is selected which determines the number of CPU cores, amount of memory and the amount of storage available to the associated machines. Additionally, when converting discovered instances in integrated clouds to VM Essentials-managed Instances, the user selects a plan which best fits the instance as it is currently configured. When Instances are reconfigured, a new plan may be selected which redefines the compute resources which should be available to the Instance. Plans can be as specific or open-ended as the user would like, restricting the user to the resources defined in the plan or allowing the user to increase those amounts at provision time.
+
+The Plans section Administration > Plans is where Plans are managed. A set of Service Plans are seeded by VM Essentials for immediate use with supported Cloud type out of the box. Additional Plans may be synced in on integrating additional Clouds depending on the type. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types.
+
+**Subtopics**  
+
+- **[Create Service Plan](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.html)**
+- **[Service Plan Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3E03B539-B71C-4D2E-A218-23713D723408.html)**
+- **[Service Plan Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.json b/corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.json
new file mode 100644
index 0000000..45ef215
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+  "title": "Overview",
+  "ordinal": 150,
+  "parent_title": "Routers",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7138E486-AE62-4778-9358-F098126785A5.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7138E486-AE62-4778-9358-F098126785A5",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.md b/corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.md
new file mode 100644
index 0000000..719388f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7138E486-AE62-4778-9358-F098126785A5.md
@@ -0,0 +1,5 @@
+# Overview
+
+Routers can be viewed, created, and managed from the Routers tab of the Infrastructure > Networks page. VM Essentials supports the creation of the following router types depending on networks that are currently configured:
+
+- OVS Bridge Domain
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json b/corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
new file mode 100644
index 0000000..5a56f58
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+  "title": "Key",
+  "ordinal": 221,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.html",
+  "topic_cluster": {
+    "clustering_title": "Key",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+        "clustering_title": "Key"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD",
+        "clustering_title": "Key"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md b/corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
new file mode 100644
index 0000000..8475e6f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7322B3C3-E10F-4484-9465-5BCFA5257CCD.md
@@ -0,0 +1,20 @@
+# Key
+
+A Cypher Key generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key).
+
+Key
+:   Pattern “key/bit\_length/key”
+
+    - Example: key/256/mykey
+
+Value
+:   Leave the Value filed blank for key, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the AES Key will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate AES Key.
+
+To delete the UUID, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json b/corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
new file mode 100644
index 0000000..b8d0fde
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+  "title": "API Access",
+  "ordinal": 305,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-74590319-12A6-4101-9043-8DDB56BB0720.html",
+  "topic_cluster": {
+    "clustering_title": "API Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+        "clustering_title": "API Access"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-74590319-12A6-4101-9043-8DDB56BB0720",
+        "clustering_title": "API Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md b/corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
new file mode 100644
index 0000000..ff27de7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-74590319-12A6-4101-9043-8DDB56BB0720.md
@@ -0,0 +1,18 @@
+# API Access
+
+Click the API Access button to expand the “API ACCESS” modal. In this modal you can generate or refresh access tokens that can be used with Morpheus API and Morpheus CLI.
+
+If no token yet exists for a particular “CLIENT ID”, click ACTIONS and then Generate. If a token has expired, we can also regenerate that token by clicking ACTIONS and then Regenerate. After regenerating a particular token, you would need to ensure any scripts using those tokens are updated.
+
+- **morph-api:** Used for VM Essentials API access and should be the default token-type used
+- **morph-cli:** Used for VM Essentials CLI access
+- **morph-automation:** Used by the internal Task engine and by jRuby-type Tasks to make API calls. It shouldn’t be used externally for other types of access or in external automation. It is surfaced in the UI so users can see if a token exists and can clear it when necessary
+- **morph-customer:** This token is available for legacy implementations and was previously recommended for custom API access (similar to the morph-api token). It’s not recommended for use but is still available to maintain support for legacy custom automation which may still be in use on customer sites
+
+After navigating away from the User Settings page, the complete access and refresh tokens will be masked from view. If these are lost or compromised, you can eliminate a token completely by clicking ACTIONS and then Clear. If you need to generate a new token for the same Client ID, click ACTIONS and then Regenerate.
+
+![../../_images/user-tokens.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-274AD26D-C940-4740-BBC7-7970107CCB4B-high.png)
+
+NOTE
+
+Access Tokens are only displayed/available after generation. Copy new Tokens and store appropriately before navigating from `/user-settings`, they will not be displayed again.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json b/corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
new file mode 100644
index 0000000..e6f12b9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+  "title": "User Settings",
+  "ordinal": 295,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md b/corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
new file mode 100644
index 0000000..6d9329a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
@@ -0,0 +1,13 @@
+# User Settings
+
+User settings are accessed by clicking on your display name in the far upper-right corner of the application window. In this dropdown menu, click on the “USER SETTINGS” link.
+
+**Subtopics**  
+
+- **[User Photo](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-40300B80-D69C-450B-9848-7A21A3141005.html)**
+- **[2 Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3B34F036-4C25-4058-B5F4-5340545BE821.html)**
+- **[Preferences](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html)**
+- **[Linux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html)**
+- **[API Access](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-74590319-12A6-4101-9043-8DDB56BB0720.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json b/corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
new file mode 100644
index 0000000..002ae34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+  "title": "Deleting Tasks",
+  "ordinal": 68,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+        "clustering_title": "Deleting Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F",
+        "clustering_title": "Deleting Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md b/corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
new file mode 100644
index 0000000..7877e98
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.md
@@ -0,0 +1,6 @@
+# Deleting Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. Click the trash icon (🗑) on the row of the Task you wish to delete
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json b/corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
new file mode 100644
index 0000000..9bedaef
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+  "title": "Role Permission Sections",
+  "ordinal": 249,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+        "clustering_title": "Role Permission Sections"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289",
+        "clustering_title": "Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md b/corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
new file mode 100644
index 0000000..c605cf2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-76B17464-6C1D-468E-B6D2-93ECF87E2289.md
@@ -0,0 +1,18 @@
+# Role Permission Sections
+
+Features
+:   Controls User access level for UI sections and features in VM Essentials. The complete feature permissions grid is included below.
+
+Groups
+:   Controls User access level for Groups. Groups are not a Multi-Tenant construct, only Groups created in the current Tenant will be visible.
+
+Cluster Types
+:   Controls user access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters (assuming the Role also has feature access to applicable permissions related to adding Clusters) VDI Pools
+
+    Controls User access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+    Workflows
+    :   Controls User access to configured Workflows, including the ability to view, edit, execute, or apply to Library item configurations
+
+Tasks
+:   Controls User access to configured Tasks, including the ability to view, edit, execute, or apply to Workflows
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json b/corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
new file mode 100644
index 0000000..e76b076
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+  "title": "Editing Existing Routers",
+  "ordinal": 152,
+  "parent_title": "Routers",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Existing Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+        "clustering_title": "Editing Existing Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C",
+        "clustering_title": "Editing Existing Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md b/corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
new file mode 100644
index 0000000..3f7a726
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.md
@@ -0,0 +1,7 @@
+# Editing Existing Routers
+
+## Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the pencil icon for the appropriate router
+3. After editing router fields, click SAVE
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json b/corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
new file mode 100644
index 0000000..ea0b1e0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+  "title": "Editing Tasks",
+  "ordinal": 67,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.html",
+  "topic_cluster": {
+    "clustering_title": "Editing Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+        "clustering_title": "Editing Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80",
+        "clustering_title": "Editing Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md b/corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
new file mode 100644
index 0000000..8cc589a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.md
@@ -0,0 +1,8 @@
+# Editing Tasks
+
+## Procedure
+
+1. Select Automation from within the Library menu
+2. Click the pencil icon (✎) on the row of the task you wish to edit
+3. Modify Task as needed
+4. Once done, click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json b/corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
new file mode 100644
index 0000000..b4ba4da
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+  "title": "Converting Discovered Resources to Managed Instances",
+  "ordinal": 46,
+  "parent_title": "Creating Instances",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.html",
+  "topic_cluster": {
+    "clustering_title": "Converting Discovered Resources to Managed Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+        "clustering_title": "Converting Discovered Resources to Managed Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F",
+        "clustering_title": "Converting Discovered Resources to Managed Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md b/corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
new file mode 100644
index 0000000..8dea8c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.md
@@ -0,0 +1,14 @@
+# Converting Discovered Resources to Managed Instances
+
+When creating new cloud integrations (or updating existing ones), users may opt for VM Essentials to onboard any existing resources that currently reside in the Cloud. For example, these may be virtual machines that exist on vCenter hosts prior to integration with VM Essentials. With the Add/Edit Cloud modal open, mark INVENTORY EXISTING INSTANCES for VM Essentials to automatically onboard these resources. Not only will VM Essentials inventory these hosts at the time the cloud is integrated (or updated), it will also continue to poll the target cloud every five minutes (by default) for newly added or removed servers. Users can see these discovered servers by looking in Infrastructure > Compute. Depending on the type of resource, it may appear on the Virtual Machines tab, the Containers tab, or another tab. Additionally, we can see a list of discovered servers on Cloud detail pages (Infrastructure > Clouds > Selected Cloud). Just click on the tabs for VMs, Containers or Hosts tab. Discovered resources will be indicated as such whereas containers which are associated with a managed Instance will be marked as a “Managed”.
+
+Additionally, VM Essentials allows users to convert discovered resources into managed Instances. Begin from the server detail page (Infrastructure > Compute > Virtual Machines > selected machine) and from the ACTIONS menu select “Convert to Managed”. At this point, we must make a number of selections:
+
+- Select a Group (this dropdown contains a filtered list of Groups in which the associated Cloud resides)
+- Username and password for a seeded account
+- Opt to install VM Essentials Agent or not
+- Select the Instance Type which should be associated with the new Instance containing this VM
+- Identify the operating system
+- Select a Plan (this dropdown contains a filtered list of plans which correlate to the size of the VM)
+
+Finally, click EXECUTE. Once this process is completed, the server will be indicated as “Managed” in the servers list. Additionally, a new Instance will appear on the Instances List page (Provisioning > Instances). We can now work with it in the same way we can work with any other Instance, such as by expanding the Instance horizontally with added nodes.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json b/corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
new file mode 100644
index 0000000..399fc08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+  "title": "Create A Backup Job",
+  "ordinal": 309,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.html",
+  "topic_cluster": {
+    "clustering_title": "Create A Backup Job",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+        "clustering_title": "Create A Backup Job"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528",
+        "clustering_title": "Create A Backup Job"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md b/corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
new file mode 100644
index 0000000..016680f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7C2AAD70-1D65-4E00-9DC0-54EF61292528.md
@@ -0,0 +1,22 @@
+# Create A Backup Job
+
+## About this task
+
+A Backup Job in HPE Morpheus Enterprise holds the schedule timing and retention count for automated backups. If you already have a Job configured, you can move on to the next section. If currently-existing options do not make sense for your backup needs or if none currently exist, create a new execution schedule. See the [execute scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html) section of this documentation for additional information on creating these schedules. To begin a new schedule, use the following steps:
+
+## Procedure
+
+1. Navigate to Library > Automation
+2. Click on the “Execute Scheduling” tab
+3. Click + ADD
+4. Enter schedule timing using `cron` notation
+5. Click SAVE
+
+## Results
+
+With the execution schedule created, we can move on to creating the Backup Job itself. A Backup Job includes both the backup retention count and an execution schedule (which we just created).
+
+1. Navigate to Backups > Jobs
+2. Click + ADD
+3. Name the Job, then configure the retention count and select the correct execution schedule
+4. Click SAVE
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json b/corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
new file mode 100644
index 0000000..7f81e66
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+  "title": "Identity Sources",
+  "ordinal": 237,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md b/corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
new file mode 100644
index 0000000..280bf83
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
@@ -0,0 +1,7 @@
+# Identity Sources
+
+Administration > Tenants > (Selected Tenant) > Identity Sources Administration > Users > Identity Sources
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-61C7ED60-DBD4-4147-A6DE-D45FCDB8DCF0.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json b/corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
new file mode 100644
index 0000000..aa49874
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+  "title": "Static and IP Pools",
+  "ordinal": 142,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.html",
+  "topic_cluster": {
+    "clustering_title": "Static and IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+        "clustering_title": "Static and IP Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE",
+        "clustering_title": "Static and IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md b/corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
new file mode 100644
index 0000000..2290cd4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7D5BFD2D-FCFB-4B24-94EE-C738A10D02AE.md
@@ -0,0 +1,42 @@
+# Static and IP Pools
+
+## About this task
+
+To configure a network for Static IP Assignment:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, add the following: 
+
+   - Gateway
+   - DNS Primary
+   - DNS Secondary
+   - CIDR ex 10.10.10.0/22
+   - VLAN ID (if necessary)
+   - Network Pool \* Leave as “choose a pool” for entering a static IP while provisioning \* Select a Pool to use a pre-configured VM Essentials or IPAM Integration IP Pool
+   - The Permissions settings are used for Multi-Tenant resource configuration
+
+     - Leave settings as default if used in a single-tenant environment (only one Tenant in your VM Essentials appliance)
+     - To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public
+     - To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private
+   - Active
+
+     - Leave as enabled to use this network
+     - Disable the active flag to remove this network from available network options
+5. Save Changes
+
+## Results
+
+NOTE
+
+When selecting a network with DHCP disabled and no IP Pool assigned during provisioning, an IP entry field will populate to the right of the selected network(s):
+
+NOTE
+
+When selecting a network with an IP Pool assigned during provisioning, the name of the IP pool will populate to the right of the selected network(s). IP Pools override DHCP.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json b/corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
new file mode 100644
index 0000000..0f2e658
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+  "title": "Delete HPE ANW DSS Port Group Network",
+  "ordinal": 363,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.html",
+  "topic_cluster": {
+    "clustering_title": "Delete HPE ANW DSS Port Group Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+        "clustering_title": "Delete HPE ANW DSS Port Group Network"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53",
+        "clustering_title": "Delete HPE ANW DSS Port Group Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md b/corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
new file mode 100644
index 0000000..1690bfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.md
@@ -0,0 +1,13 @@
+# Delete HPE ANW DSS Port Group Network
+
+## About this task
+
+To delete a HPE ANW DSS Port Group network, follow these steps:
+
+## Procedure
+
+1. Navigate to
+2. Select the network you want to delete from the list.
+3. Click on the delete icon (🗑) next to the network name. 
+
+   ![../../_images/4_delete_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5DFCE9ED-5DDA-469D-B118-24F0B3AC0429-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json b/corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
new file mode 100644
index 0000000..00cadd2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+  "title": "ArubaCX Network Integration",
+  "ordinal": 348,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html",
+  "topic_cluster": {
+    "clustering_title": "ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md b/corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
new file mode 100644
index 0000000..a283f9f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
@@ -0,0 +1,9 @@
+# ArubaCX Network Integration
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2D035C3B-0102-4FB3-BE34-74094659DC87.html)**
+- **[Adding ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.html)**
+- **[Add ArubaCX Integration to a Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-054A7DC4-C03C-4356-8486-19472075129E.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json b/corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
new file mode 100644
index 0000000..80c0542
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+  "title": "Prerequisites",
+  "ordinal": 367,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md b/corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
new file mode 100644
index 0000000..0f6c283
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7ED985CC-0C31-4A22-A16F-A1FD1B40E42B.md
@@ -0,0 +1,35 @@
+# Prerequisites
+
+- All HPE Alletra MP Storage iSCSI ports are reachable from each of the cluster hosts
+- The `multipath.conf` settings on each node should be configured as follows:
+
+```
+```
+defaults {  
+    find_multipaths yes  
+    user_friendly_names no  
+}
+```
+```
+
+Before you set up Active-Active Peer Persistence (AAPP) replication, ensure that the following requirements are met:
+
+**Supported configurations**
+
+- Remote Copy is configured using either Fibre Channel (RCFC) or IP (RCIP).
+- Replication targets are synchronous only.
+- HPE Alletra MP B10000 arrays are running OS version 10.5.0 or later.
+- AAPP replication supports only a 1:1 target mapping.
+
+**Array configuration (outside VM Essentials)**
+
+- Complete the AAPP Remote Copy configuration on both primary and secondary arrays.
+- Configure replication ports and define targets on both arrays.
+- Configure a Quorum Witness for the arrays.
+
+For more information about array configuration, see HPE GreenLake for Block Storage UI 2.5 User Guide.
+
+**VM Essentials setup**
+
+- Add both primary and secondary arrays as Storage Servers in Infrastructure > Storage > Server.
+- Create a datastore on both the primary and secondary Storage Servers.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json b/corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
new file mode 100644
index 0000000..d2760c5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+  "title": "API",
+  "ordinal": 84,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.html",
+  "topic_cluster": {
+    "clustering_title": "API",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+        "clustering_title": "API"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7",
+        "clustering_title": "API"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md b/corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
new file mode 100644
index 0000000..8d4ace2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-7FC478D1-40B2-4B9F-8848-0FA8D20F1CD7.md
@@ -0,0 +1,3 @@
+# API
+
+To view all groups: `curl https://api.gomorpheus.com/api/groups -H "Authorization: BEARER access_token"` To view a specific group: `curl https://api.gomorpheus.com/api/groups/:id -H "Authorization: BEARER access_token"`
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json b/corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
new file mode 100644
index 0000000..37d4092
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+  "title": "Infrastructure",
+  "ordinal": 79,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.html",
+  "topic_cluster": {
+    "clustering_title": "Infrastructure",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+        "clustering_title": "Infrastructure"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5",
+        "clustering_title": "Infrastructure"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md b/corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
new file mode 100644
index 0000000..e7feb0f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-81D65476-F9C2-40FE-804F-4BF36D3AA9F5.md
@@ -0,0 +1,12 @@
+# Infrastructure
+
+The heart of VM Essentials is the ability to manage provisioning across any infrastructure, from bare metal to virtualized clouds and all the way to public infrastructure.
+
+**Subtopics**  
+
+- **[Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html)**
+- **[Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html)**
+- **[Network](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json b/corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
new file mode 100644
index 0000000..ebad494
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+  "title": "Example JSON Map:",
+  "ordinal": 63,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.html",
+  "topic_cluster": {
+    "clustering_title": "Example JSON Map:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+        "clustering_title": "Example JSON Map:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640",
+        "clustering_title": "Example JSON Map:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md b/corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
new file mode 100644
index 0000000..aad0959
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-82BCDDB1-D073-4061-91B1-7ECC4A2A3640.md
@@ -0,0 +1,28 @@
+# Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Task is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json b/corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
new file mode 100644
index 0000000..3c22c97
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+  "title": "VMware Permissions",
+  "ordinal": 328,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+        "clustering_title": "VMware Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E",
+        "clustering_title": "VMware Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md b/corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
new file mode 100644
index 0000000..b955f9d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.md
@@ -0,0 +1,9 @@
+# VMware Permissions
+
+When integrating VMware vCenter with VM Essentials, users must supply credentials for a vCenter account and VM Essentials will only have access privileges equal to the integrated account. Many users will choose to use a vCenter administrator account so that VM Essentials can freely do any function in vCenter without worrying about hitting access limits. Others, for security reasons, may want to restrict VM Essentials only to the minimum permissions it needs to perform its functions. Follow the guide in this section to configure a user with minimal permissions and associate it with the appropriate usage levels before using it to create a VM Essentials Cloud integration.
+
+**Subtopics**  
+
+- **[Create vCenter Users and Roles](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-443F9C0E-FFD9-48B9-85A8-596A36E7114B.html)**
+- **[Privileges](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5510EBF1-D36C-4FC5-8581-200044D6F7CC.html)**
+- **[Usage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json b/corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
new file mode 100644
index 0000000..fa2f7d5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+  "title": "VMware - VM Templates Copies",
+  "ordinal": 78,
+  "parent_title": "Add Virtual Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.html",
+  "topic_cluster": {
+    "clustering_title": "VMware - VM Templates Copies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+        "clustering_title": "VMware - VM Templates Copies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE",
+        "clustering_title": "VMware - VM Templates Copies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md b/corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
new file mode 100644
index 0000000..22dd4e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.md
@@ -0,0 +1,11 @@
+# VMware - VM Templates Copies
+
+In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to VM Essentials, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be synced into VM Essentials.
+
+If all the vCenters are added as Clouds into VM Essentials and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in VM Essentials. This means that as you deploy to the various vCenter Clouds in VM Essentials using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.
+
+VM Essentials supports VMware Content Libraries storing VM templates and syncing into VM Essentials, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.
+
+NOTE
+
+VM templates are a **Datacenter** level object. The same process above applies to a single VMware cloud with multiple logical datacenters. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json b/corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
new file mode 100644
index 0000000..fa39f3d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+  "title": "App Blueprint Settings",
+  "ordinal": 282,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.html",
+  "topic_cluster": {
+    "clustering_title": "App Blueprint Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+        "clustering_title": "App Blueprint Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238",
+        "clustering_title": "App Blueprint Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md b/corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
new file mode 100644
index 0000000..bbbcfb9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.md
@@ -0,0 +1,10 @@
+# App Blueprint Settings
+
+Determines the Default Blueprint Type selected in new App Wizard
+
+- Morpheus
+- ARM Template
+- CloudFormation
+- Terraform
+- Kubernetes Spec
+- Helm Chart
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json b/corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
new file mode 100644
index 0000000..8f0c246
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+  "title": "Overview",
+  "ordinal": 245,
+  "parent_title": "Roles",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md b/corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
new file mode 100644
index 0000000..4b42f78
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-878B0BCE-B5BC-48D5-8DEB-3FAD1A0EDD88.md
@@ -0,0 +1,15 @@
+# Overview
+
+Within VM Essentials is a wide array of role-based access control capabilities. These roles can be managed within the Administration > Roles section of the VM Essentials UI as well as through the API or CLI. Entire sections within the appliance UI can be hidden based on the specified access levels for features within VM Essentials. Features have different access scopes that can be selected from and can range depending on the specific feature. The most common scope set involves none, read, and full.
+
+There are several handy tricks for creating new roles within VM Essentials and users can be assigned more than one role. When a user is assigned more than one role, permissions are granted by the role with the highest level of scope access. This allows roles to be built with small subsets of features and combined to grant different individuals relevant permission control. With resource permissions (that is, all types of permissions other than Feature permissions), a default access can be given as opposed to a specific (Full or None) permission for any resource. A specific permission will always supersede a default permission regardless of whether it’s more permissive or more restrictive. In other cases (default vs default OR specific vs specific) the more permissive access will be given.
+
+It’s also important to note that built-in Roles, such as the System Admin “Superuser” Role carry no special prominence. For resource permissions, the System Admin user has defaults set to Full in each section. Thus, pairing the System Admin Role with another Role that may include specific line item permissions for various resource categories may cause your System Admin users to take on a reduced permission set.
+
+NOTE
+
+Feature access control not only applies to the VM Essentials UI but also applies to the public developer API. It is sometimes necessary to logout and back in for changes to a users feature access level to be respected.
+
+**Subtopics**  
+
+- **[Role Creation](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json b/corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
new file mode 100644
index 0000000..756826b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+  "title": "Mountpoints",
+  "ordinal": 215,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.html",
+  "topic_cluster": {
+    "clustering_title": "Mountpoints",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+        "clustering_title": "Mountpoints"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-87FC621D-8EDE-48DE-901B-00058C07E62D",
+        "clustering_title": "Mountpoints"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md b/corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
new file mode 100644
index 0000000..8ff9c93
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-87FC621D-8EDE-48DE-901B-00058C07E62D.md
@@ -0,0 +1,27 @@
+# Mountpoints
+
+password
+:   Generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+tfvars
+:   This is a module to store a tfvars file for terraform app blueprints.
+
+secret
+:   This is the standard secret module that stores a key/value in encrypted form.
+
+uuid
+:   Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+key
+:   Generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key)
+
+vault
+:   Configures an integration between VM Essentials and a Hashicorp Vault server. See below for additional configuration instructions.
+
+    - Key lease times are entered in seconds and default to 32 days (2764800 s).
+
+      - Quick Time Reference:
+      - Day: 86400
+      - Week: 604800
+      - Month (30 days): 2592000
+      - Year: 31536000
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json b/corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
new file mode 100644
index 0000000..91f42bb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+  "title": "GFS2 Pools Overview",
+  "ordinal": 117,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.html",
+  "topic_cluster": {
+    "clustering_title": "GFS2 Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+        "clustering_title": "GFS2 Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27",
+        "clustering_title": "GFS2 Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md b/corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
new file mode 100644
index 0000000..68c6d3f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-880FEFB6-37C2-4FEB-B1B7-A23FAC1B3E27.md
@@ -0,0 +1,5 @@
+# GFS2 Pools Overview
+
+GFS2 is a shared-disk cluster file system that allows multiple nodes in a cluster to access the same storage at the block level. Adding GFS2 datastores to an HVM Cluster enables live migration and live failover of running VMs.
+
+Administrators only need to present the disks to the HVM Hosts and make a few specific configurations. HPE Morpheus VM Essentials handles everything else, including mounting datastores and enabling multipathing.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json b/corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
new file mode 100644
index 0000000..f5f10f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+  "title": "Affinity Groups",
+  "ordinal": 323,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md b/corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
new file mode 100644
index 0000000..29b8ff3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.md
@@ -0,0 +1,29 @@
+# Affinity Groups
+
+HPE Morpheus VM Essentials Software offers two-way sync for affinity groups with integrated VMware vCenter Clouds. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Affinity groups created from HPE Morpheus VM Essentials create "Should" rules (soft rules) rather than "Must" rules (hard rules) in vCenter. Thus whenever possible, servers configured to "Keep Together" will run on the same cluster host while servers configured to "Keep Separate" will be balanced across cluster hosts to the maximum extent possible. These rules may be broken if necessary to balance resources or recover from failures.
+
+TIP
+
+It is possible to create an empty affinity group (that is, one with no servers selected) in HPE Morpheus VM Essentials even though this is not possible in vCenter. If such an affinity group is created, HPE Morpheus VM Essentials will hold it without syncing to vCenter until at least one server is added and the affinity group becomes compatible with the vCenter API.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-7AD47077-8387-4499-9BDE-BBACFDDA2989-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the VMware Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **CLUSTER:** Select the vCenter cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next Cloud sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-C4C3EDB1-CA6E-4DEA-890C-B5C5B0E3DE13-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-688F89C9-1444-4D3A-94B5-E8DFE9BDC066-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json b/corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
new file mode 100644
index 0000000..093322a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+  "title": "Rackspace CDN Buckets",
+  "ordinal": 185,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.html",
+  "topic_cluster": {
+    "clustering_title": "Rackspace CDN Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+        "clustering_title": "Rackspace CDN Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4",
+        "clustering_title": "Rackspace CDN Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md b/corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
new file mode 100644
index 0000000..2ac66d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8A98C9E6-A54F-40CA-A99C-7FF4F7AF6BC4.md
@@ -0,0 +1,81 @@
+# Rackspace CDN Buckets
+
+## About this task
+
+To Add a Rackspace CDN Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Rackspace CDN from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   USERNAME
+   :   Rackspace CDN Username
+
+   API KEY
+   :   Rackspace CDN API Key
+
+   REGION
+   :   Enter Rackspace CDN Region
+
+   BUCKET NAME
+   :   Enter existing Rackspace CDN Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+**Subtopics**  
+
+- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-35419962-0058-4856-A6BD-F4923FD0F044.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json b/corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
new file mode 100644
index 0000000..cb8259f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+  "title": "Overview",
+  "ordinal": 288,
+  "parent_title": "Environments",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8AFBB53F-6749-4E7E-AAF2-310849586320",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md b/corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
new file mode 100644
index 0000000..7ac26c1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8AFBB53F-6749-4E7E-AAF2-310849586320.md
@@ -0,0 +1,7 @@
+# Overview
+
+The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
+
+**Subtopics**  
+
+- **[Creating Environments](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json b/corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
new file mode 100644
index 0000000..c911156
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+  "title": "Overview",
+  "ordinal": 97,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md b/corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
new file mode 100644
index 0000000..92f8ac2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8BDE5489-A20A-4B1F-A05B-CA725C5609A0.md
@@ -0,0 +1,3 @@
+# Overview
+
+The Infrastructure > Clusters section is where the list of existing HVM clusters can be viewed. Here you can view high-level statistics about all clusters under management by VM Essentials manager, such as aggregate resource usage by all clusters and the number of workloads running across all of them. Click into an existing HVM cluster to view additional metrics such as hosts, VMs, resource utilization by the host, and a lot more.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json b/corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
new file mode 100644
index 0000000..8f57765
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+  "title": "Network Interfaces",
+  "ordinal": 338,
+  "parent_title": "Creating a CentOS/RHEL 7 Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Interfaces",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+        "clustering_title": "Network Interfaces"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E",
+        "clustering_title": "Network Interfaces"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md b/corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
new file mode 100644
index 0000000..a831b15
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.md
@@ -0,0 +1,44 @@
+# Network Interfaces
+
+A slightly annoying change with centOS 7 is that the network interfaces have changed naming convention. You may notice when running ifconfig that the primary network interface is set to something like ens2344 or some other random number. This naming is dynamic typically by hardware id and we don’t want this to fluctuate when provisioning the blueprint in various VMware environments. Fortunately, there is a way to turn this functionality off and restore the interface back to eth0.
+
+Firstly we need to adjust our bootloader to disable interface naming like this.
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The above command adds a few arguments to the kernel args list (namely `net.ifnames=0` and `biosdevname=0`. It may be useful to view the `/etc/default/grub` file and ensure these settings were indeed applied.
+
+The next step is to adjust the network-scripts in centOS. we need to ensure we have a file called `/etc/sysconfig/network-scripts/ifcfg-eth0`
+
+Below is a script that we run on our packer builds to prepare the machines network configuration files.
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to ensure there is a new ifcfg-eth0 config created to replace the old ens config file. Please do verify this config exists after running. If it does not you will have to be sure to build one on your own.
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json b/corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
new file mode 100644
index 0000000..ac107e5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+  "title": "Settings",
+  "ordinal": 264,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.html",
+  "topic_cluster": {
+    "clustering_title": "Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+        "clustering_title": "Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467",
+        "clustering_title": "Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md b/corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
new file mode 100644
index 0000000..e8fdcf7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.md
@@ -0,0 +1,12 @@
+# Settings
+
+The Administration > Settings section sets global configuration parameters for the VM Essentials appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for VM Essentials itself.
+
+**Subtopics**  
+
+- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
+- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
+- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
+- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json b/corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
new file mode 100644
index 0000000..4e33495
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+  "title": "Overview",
+  "ordinal": 349,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md b/corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
new file mode 100644
index 0000000..e3542c9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8E19FA4E-4408-4784-A629-DD936DEEBA26.md
@@ -0,0 +1,3 @@
+# Overview
+
+The ArubaCX network plugin is implemented as a VM Essentials `GenericIntegrationProvider` in Groovy. The plugin handles network and cluster events generated by VM Essentials and modifies the configuration of ArubaCX switches based on the cable connections between the affected servers and switches. VM Essentials integrates directly with ArubaCX to create or delete networks for OVS Port Groups that are added or deleted within a configured Cluster.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json b/corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
new file mode 100644
index 0000000..053e614
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+  "title": "Consuming Currency Exchange in VM Essentials",
+  "ordinal": 274,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.html",
+  "topic_cluster": {
+    "clustering_title": "Consuming Currency Exchange in VM Essentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+        "clustering_title": "Consuming Currency Exchange in VM Essentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-8EC2E33D-2086-4253-BF7D-D953052774A0",
+        "clustering_title": "Consuming Currency Exchange in VM Essentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md b/corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
new file mode 100644
index 0000000..3104ca0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.md
@@ -0,0 +1,7 @@
+# Consuming Currency Exchange in VM Essentials
+
+Currency exchange data is synced from the integrated provider once every 12 hours. When needed, Morpheus will use this cached data to present currency conversions rather than hitting the API directly each time. This limits the total number of API hits and reduces costs.
+
+Exchanged currency values will be shown under conditions similar to the following scenario:
+
+A user is working in a Subtenant configured for Currency B. The user is attempting to provision an instance with pricing sets that have only been defined in Currency A. Morpheus will convert the pricing data from currency A to Currency B for this user (and all users in this Subtenant) since price conversion has been enabled.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.json b/corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
new file mode 100644
index 0000000..3056ed6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+  "title": "Backups",
+  "ordinal": 13,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-91D3F799-4C17-4008-B605-FEE370890091.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-91D3F799-4C17-4008-B605-FEE370890091",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.md b/corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
new file mode 100644
index 0000000..0290649
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-91D3F799-4C17-4008-B605-FEE370890091.md
@@ -0,0 +1,3 @@
+# Backups
+
+Displays the number of successful and unsuccessful backups over the last day, week or month
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json b/corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
new file mode 100644
index 0000000..f23426e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+  "title": "Password",
+  "ordinal": 217,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.html",
+  "topic_cluster": {
+    "clustering_title": "Password",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+        "clustering_title": "Password"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E",
+        "clustering_title": "Password"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md b/corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
new file mode 100644
index 0000000..4cbc429
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-92B9E282-D11B-47B0-94D6-3E7B2B17B82E.md
@@ -0,0 +1,20 @@
+# Password
+
+A Cypher password generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+Key
+:   Pattern “password/character\_length/key”
+
+    Example: password/10/mypassword
+
+Value
+:   Leave the Value filed blank for a password, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the password will be generated and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generated password.
+
+To delete the password key, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json b/corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
new file mode 100644
index 0000000..f80cfb3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+  "title": "Domains",
+  "ordinal": 157,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html",
+  "topic_cluster": {
+    "clustering_title": "Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md b/corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
new file mode 100644
index 0000000..3662e80
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
@@ -0,0 +1,13 @@
+# Domains
+
+Infrastructure  >  Network  >  Domains
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3026A7D3-3BC3-4ABC-AD6A-B0EE5362562E.html)**
+- **[Adding Domains](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2E68673C-77D9-4E8E-B9B4-2D5C06AE30BD.html)**
+- **[Editing Domain Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0CB2D2E2-20E1-41AD-BB39-2D966B108FF2.html)**
+- **[Editing and Removing Domains](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.html)**
+- **[Setting the default domain on a Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-97951AE9-439B-4779-823D-E118E1CB08D3.html)**
+- **[Setting the default domain on a Network](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-650706CA-915E-4239-9D69-35902E82B60E.html)**
+- **[Selecting a Domain while provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1569A1AD-385D-4E16-9C85-A1915813FCC8.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json b/corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
new file mode 100644
index 0000000..e3a8163
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+  "title": "Hardware Passthrough",
+  "ordinal": 132,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md b/corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
new file mode 100644
index 0000000..5e5ac49
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
@@ -0,0 +1,13 @@
+# Hardware Passthrough
+
+HPE Morpheus VM Essentials includes hardware passthrough and pooling support for VMs provisioned to HVM Clusters. This support extends to GPU, USB, NVME, and any other PCIe device types. In order to be usable, such devices must be attached to a HVM Host or to multiple HVM Hosts. HPE Morpheus VM Essentials includes controls to detach hardware devices from the underlying OS on the hypervisor host and add them to a pool where they are available for consumption by VMs. GPU hardware can be attached to VMs at provision time through custom Service Plans or on an ad-hoc basis by manually attaching hardware to existing VMs. Other supported hardware types must be passed through to the VM after provisioning.
+
+NOTE
+
+HVM Clusters sync certain data every few minutes (short sync) and other data once nightly (daily sync). New hardware attached to hosts is synced into HPE Morpheus VM Essentials during the nightly sync. To consume newly attached hardware immediately, you can force an additional daily sync at any time from the cluster detail page. Just expand the ACTIONS menu and click "Refresh Daily." Within a short time the additional daily sync will complete and newly attached hardware should be consumable from the UI.
+
+**Subtopics**  
+
+- **[Creating Service Plans for GPU Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html)**
+- **[Viewing and Assigning Hardware Devices](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html)**
+- **[GPU Passthrough Example](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json b/corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
new file mode 100644
index 0000000..aa26e91
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+  "title": "Local Storage File Shares",
+  "ordinal": 189,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.html",
+  "topic_cluster": {
+    "clustering_title": "Local Storage File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+        "clustering_title": "Local Storage File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E",
+        "clustering_title": "Local Storage File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md b/corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
new file mode 100644
index 0000000..023f157
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-953F9E2E-D9DD-4469-96EE-A288371FE36E.md
@@ -0,0 +1,82 @@
+# Local Storage File Shares
+
+## About this task
+
+IMPORTANT
+
+Local Storage refers to local to the VM Essentials Appliance and the path must be owned by morpheus-app. Please be conscious of storage space. High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end VM Essentials Appliances.
+
+NOTE
+
+To change the owner of a file path to be used as a Local Storage File Share, run `chown morpheus-app:morpheus-app /path` on the VM Essentials Appliance.
+
+NOTE
+
+VM Essentials will validate path and ownership of the File Share Path.
+
+To Add a Local Storage File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Local Storage Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   STORAGE PATH
+   :   Enter the File Share path on the local VM Essentials Appliance.
+       :   Example: `/var/opt/morpheus/morpheus-ui/vms/virtual-images`
+
+           IMPORTANT
+
+           High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end VM Essentials Appliances.
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json b/corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
new file mode 100644
index 0000000..a24bf39
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+  "title": "Virtual Images / Blueprints",
+  "ordinal": 321,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images / Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+        "clustering_title": "Virtual Images / Blueprints"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D",
+        "clustering_title": "Virtual Images / Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md b/corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
new file mode 100644
index 0000000..42d1439
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.md
@@ -0,0 +1,7 @@
+# Virtual Images / Blueprints
+
+VM Essentials will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for VM Essentials to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to VM Essentials . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints VM Essentials requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json b/corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
new file mode 100644
index 0000000..d2e688e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+  "title": "Create Data Stores",
+  "ordinal": 192,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.html",
+  "topic_cluster": {
+    "clustering_title": "Create Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+        "clustering_title": "Create Data Stores"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD",
+        "clustering_title": "Create Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md b/corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
new file mode 100644
index 0000000..45a9712
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-960DA835-B984-49FB-80DE-EE6D38D42EDD.md
@@ -0,0 +1,13 @@
+# Create Data Stores
+
+To a limited extent, data stores can be created from this view. In order to create a data store, you would need to first have an integrated 3Par server. See the section on storage servers for more information on setting up this integration.
+
+NOTE
+
+For all other data store types, create the needed data store within the target Cloud and VM Essentials will automatically sync in the data store on the next Cloud sync. You can force a Cloud sync from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > RefreshMenu > Short).
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click +ADD
+- Enter a Name, select a VMware Cloud, select a 3Par Volume, and select a Host Group
+- Manage permissions in the Group Access and Tenant Permissions sections, if needed
+- Click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json b/corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
new file mode 100644
index 0000000..1b1f3b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+  "title": "Maintenance Mode",
+  "ordinal": 124,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.html",
+  "topic_cluster": {
+    "clustering_title": "Maintenance Mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+        "clustering_title": "Maintenance Mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725",
+        "clustering_title": "Maintenance Mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md b/corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
new file mode 100644
index 0000000..092405b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.md
@@ -0,0 +1,3 @@
+# Maintenance Mode
+
+HVM hosts can be easily taken out of service for maintenance when needed. From the host detail page, click ACTIONS and then click “Enter Maintenance.” When entering maintenance mode, the host will be removed from the pool. Live VMs that can be migrated will be moved to new hosts. VMs that are powered off will also be moved when possible. When a live VM cannot be moved (such as if it’s “pinned” to the host), the host will not go into maintenance mode until that situation is cleared. You could manually move a VM to a new host or you could power it down if it’s non-essential. After taking that action, attempt to put the host into maintenance mode once again. VM Essentials UI provides a helpful dialog which shows you which VMs live on the host are to be moved as the host goes into maintenance mode. When maintenance has finished, go back to the ACTIONS menu and select “Leave Maintenance.”
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json b/corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
new file mode 100644
index 0000000..edf66bb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+  "title": "Viewing Alerts ",
+  "ordinal": 373,
+  "parent_title": "Add a storage server",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing Alerts ",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+        "clustering_title": "Viewing Alerts "
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F",
+        "clustering_title": "Viewing Alerts "
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md b/corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
new file mode 100644
index 0000000..21c6599
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-968E8B3B-0DAE-466A-BA37-CEBC6F24046F.md
@@ -0,0 +1,13 @@
+# Viewing Alerts
+
+The Alerts tab displays system alerts with severity levels of Fatal, Critical, or Major.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server.
+3. Select the Alerts tab.
+4. Select the type of alert that you want to view from the Filter by Type drop-down list.
+5. The alerts displayed in the Alerts tab provide the following information:
+   - **Severity**: Displays the severity of the alert. The severity can be Fatal, Critical, or Major. The severity of the alert determines the health status of the system.
+   - **Type**: Displays the type of the alert message.
+   - **Message**: Displays the description of the alert message.
+   - **Time**: Displays the time when the alert was created. The UTC timezone is the standard timezone in HPE Morpheus Enterprise.![Alerts tab](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-46AEA56B-E951-48EC-8781-EEAF84D5ADB7-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json b/corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
new file mode 100644
index 0000000..cda3894
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+  "title": "Setting the default domain on a Cloud",
+  "ordinal": 163,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-97951AE9-439B-4779-823D-E118E1CB08D3.html",
+  "topic_cluster": {
+    "clustering_title": "Setting the default domain on a Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+        "clustering_title": "Setting the default domain on a Cloud"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-97951AE9-439B-4779-823D-E118E1CB08D3",
+        "clustering_title": "Setting the default domain on a Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md b/corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
new file mode 100644
index 0000000..8125d16
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-97951AE9-439B-4779-823D-E118E1CB08D3.md
@@ -0,0 +1,9 @@
+# Setting the default domain on a Cloud
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Clouds.
+2. Edit the target Cloud.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json b/corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
new file mode 100644
index 0000000..8c1e707
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+  "title": "Provisioning the Cluster",
+  "ordinal": 107,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9886AD4A-5C64-4E09-A106-B14419362757.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+        "clustering_title": "Provisioning the Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9886AD4A-5C64-4E09-A106-B14419362757",
+        "clustering_title": "Provisioning the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md b/corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
new file mode 100644
index 0000000..baf2444
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9886AD4A-5C64-4E09-A106-B14419362757.md
@@ -0,0 +1,21 @@
+# Provisioning the Cluster
+
+As mentioned in the previous section, HVM hosts should be running Ubuntu 24.04 to use the latest HVM cluster layout (version 1.2+). HVM hosts running Ubuntu 22.04 can also be used (select HVM cluster layout 1.1). I also have a Private Cloud-type Cloud to house the cluster. Begin the cluster creation process from the Clusters list page (Infrastructure > Clusters). Click + ADD CLUSTER and select “HVM”.
+
+VM Essentials gives the option to select a hyperconverged infrastructure (HCI) **LAYOUT** or non-HCI. In this example, the HCI Layout is used (requires a three-node minimum). Next, configure the names and IP addresses for the host boxes (**SSH HOST**). The SSH HOST name configuration is simply a display name in VM Essentials, it does not need to be a hostname. By default, configuration space is given for three hosts which is what this example cluster will have. You must at least configure one and it’s possible to add more by clicking the (+) button. The **SSH PORT** is pre-configured for port 22, change this value if applicable in your environment. Next, set a pre-existing user on the host boxes (**SSH USERNAME** and **SSH PASSWORD**) and **SSH KEY**. Use a regular user with sudo access.
+
+In the next part of the modal, you’ll configure the storage devices and network interfaces. Find your disk name, if needed, with the `lsblk` command. In my case, the target device is located at `/dev/sdb`.
+
+Though not strictly required, it’s recommended to have separate network interfaces to handle cluster management, storage traffic, and compute. In this example case, `eth0` is configured as the **MANAGEMENT NET INTERFACE** which handles communication between the cluster hosts. `eth1` is configured as the **STORAGE NET INTERFACE** and `eth2` is configured as the **COMPUTE NET INTERFACE**. The **COMPUTE VLANS** field can take a single value (ex. 1) or a range of values (ex. 22-25). This will create OVS port group(s) selectable as networks when provisioning workloads to the cluster. If needed, you can find your network interface names with the `ip a` command.
+
+Next, only one **CPU TYPE** is currently supported (`x86_64`) though this may change in the future. For **CPU MODEL** configuration, we surface the entire database of model configurations from `libvirt`. If unsure or if you don’t know of a specific reason to choose one or the other, select `host-passthrough` which is the default option.
+
+Finally, select a **DYNAMIC PLACEMENT** and **POWER POLICY** configuration. When enabled, Dynamic Placement will automatically balance VMs across cluster hosts based on resource utilization. When disabled, VMs will only migrate to a new host if they are pinned to a specific host or failed over and not running on the preferred host. With Power Policy, set Balanced (default) or Performance configuration. Balanced optimizes for a mix of performance and efficiency. Performance mode is optimized for scenarios requiring maximum performance. It reduces network latency by applying configurations similar to the `tuned` "network-latency" profile and switches CPUs into performance mode.
+
+NOTE
+
+Power Policy settings require Agent version 3.0.0+ running on the HVM Host and take effect following the next sync cycle. You can upgrade HVM Host Agents by navigating to the Host detail page, opening the ACTIONS menu, and selecting Upgrade Agent. Alternatively, you can select Download Agent Script to download a script which can be run on the HVM Host to upgrade its Agent version. Download scripts are specific to the HVM Host so you will need an individual script per HVM Host. Power Policy settings will persist following a HVM Host reboot.
+
+![image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-8FF3A6DF-6A14-4A7D-B4C1-7E6BDB83B44D-high.png)
+
+At this point we’ve kicked off the process for configuring the cluster nodes. Drill into the Cluster detail page and click on the History tab. Here we can monitor the progress of configuring the cluster. HPE Morpheus VM Essentials will run scripts to install KVM, install OVS, and to prepare the cluster. In just a short time, the cluster provisioning should complete and the cluster will be ready to deploy workloads.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json b/corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
new file mode 100644
index 0000000..f8672fd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+  "title": "Supported File Share Types",
+  "ordinal": 187,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.html",
+  "topic_cluster": {
+    "clustering_title": "Supported File Share Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+        "clustering_title": "Supported File Share Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391",
+        "clustering_title": "Supported File Share Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md b/corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
new file mode 100644
index 0000000..8d2ef9e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-98AF56C4-8C58-4C3A-9AAA-D13A3D3AD391.md
@@ -0,0 +1,5 @@
+# Supported File Share Types
+
+- CIFS (Samba Windows File Sharing)
+- Local Storage
+- NFSv3
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json b/corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
new file mode 100644
index 0000000..6f54bc2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+  "title": "Generate Key Pair",
+  "ordinal": 203,
+  "parent_title": "Key Pairs",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.html",
+  "topic_cluster": {
+    "clustering_title": "Generate Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+        "clustering_title": "Generate Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086",
+        "clustering_title": "Generate Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md b/corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
new file mode 100644
index 0000000..baa6aa0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.md
@@ -0,0 +1,17 @@
+# Generate Key Pair
+
+## About this task
+
+To generate a Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Generate Key Pair”
+3. After naming the new key pair, HPE Morpheus VM Essentials will reveal both the public and private key
+
+## Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in HPE Morpheus VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json b/corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
new file mode 100644
index 0000000..09cce8d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+  "title": "Windows Agent",
+  "ordinal": 37,
+  "parent_title": "SSH/Winrm",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9969BD6B-639D-4633-B825-79578464E8E6.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+        "clustering_title": "Windows Agent"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9969BD6B-639D-4633-B825-79578464E8E6",
+        "clustering_title": "Windows Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md b/corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
new file mode 100644
index 0000000..79e4ab2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9969BD6B-639D-4633-B825-79578464E8E6.md
@@ -0,0 +1,8 @@
+# Windows Agent
+
+- Port 5985 must be open and WinRM enabled for Windows images.
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+NOTE
+
+Administrator user is required for Windows agent install.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json b/corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
new file mode 100644
index 0000000..9b814e9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+  "title": "Snapshots",
+  "ordinal": 322,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.html",
+  "topic_cluster": {
+    "clustering_title": "Snapshots",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+        "clustering_title": "Snapshots"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF",
+        "clustering_title": "Snapshots"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md b/corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
new file mode 100644
index 0000000..dbafb29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.md
@@ -0,0 +1,11 @@
+# Snapshots
+
+VM Essentials allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into VM Essentials every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+VM Essentials supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in VM Essentials for VMs using SR-IOV network adapters.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json b/corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
new file mode 100644
index 0000000..5ea9a31
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+  "title": "Enabled Clouds (Types)",
+  "ordinal": 275,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.html",
+  "topic_cluster": {
+    "clustering_title": "Enabled Clouds (Types)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+        "clustering_title": "Enabled Clouds (Types)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B",
+        "clustering_title": "Enabled Clouds (Types)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md b/corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
new file mode 100644
index 0000000..3cc91e3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.md
@@ -0,0 +1,5 @@
+# Enabled Clouds (Types)
+
+Controls which types of Cloud can be created.
+
+- When a Cloud type is disabled, it will be removed from the available options when adding new Clouds in Infrastructure  >  Clouds. Existing Clouds are not affected by changes to this setting.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json b/corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
new file mode 100644
index 0000000..bcc0d79
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+  "title": "License",
+  "ordinal": 290,
+  "parent_title": "Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html",
+  "topic_cluster": {
+    "clustering_title": "License",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md b/corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
new file mode 100644
index 0000000..366e122
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
@@ -0,0 +1,7 @@
+# License
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4AE72311-7C7E-4384-A7E1-A23048B29C40.html)**
+- **[Current License](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.html)**
+- **[Upgrade License Key](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json b/corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
new file mode 100644
index 0000000..76a9f40
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+  "title": "Cloud-Init",
+  "ordinal": 337,
+  "parent_title": "Creating a CentOS/RHEL 7 Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud-Init",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+        "clustering_title": "Cloud-Init"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74",
+        "clustering_title": "Cloud-Init"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md b/corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
new file mode 100644
index 0000000..68d2374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.md
@@ -0,0 +1,15 @@
+# Cloud-Init
+
+To get started with a base CentOS image we first install cloud-init. This is a relatively simple process using yum:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+There are two parts to this yum installation. We are first ensuring some core dependencies are installed for automation as well as cloud-init. git for example is installed for use by ansible playbook automation down the line and is therefore optional if not using ansible. The dracut-modules-growroot is responsible for resizing the root partition upon first boot to match the virtual disk size that was potentially adjusted during provisioning.
+
+A great benefit to using cloud-init is credentials don’t have to be locked into the blueprint. It is advisable, within VM Essentials , to configure the default cloud-init user that gets created when the vm boots automatically by cloud-init. This is located in Administration > Settings > Provisioning, within the Cloud-Init Settings section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json b/corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
new file mode 100644
index 0000000..c931428
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+  "title": "Adding an NFS Datastore",
+  "ordinal": 129,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an NFS Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+        "clustering_title": "Adding an NFS Datastore"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC",
+        "clustering_title": "Adding an NFS Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md b/corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
new file mode 100644
index 0000000..351b8cf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.md
@@ -0,0 +1,11 @@
+# Adding an NFS Datastore
+
+Existing NFS shares can be used with HVM clusters for virtual machine storage. These are added and viewed from the Storage tab of the cluster detail page and, once added and active, become selectable as targets for virtual machine storage.
+
+NOTE
+
+Ensure NFS is properly configured to allow all of the HVM hosts to access the shared directory, including permissions to read and write. For backup purposes, it’s also helpful to give VM Essentials access to NFS.
+
+Start by navigating to the Storage tab of the cluster detail page. Make sure the Data Stores subtab is also selected. Here you will see a list of existing datastores with some additional information, such as type, capacity, and status. Click ADD. Enter the NAME for the datastore in VM Essentials and select the TYPE as NFS Pool. Note that the datastore name cannot be changed once it has been created. This will update the available fields to include the additional fields needed to integrate the NFS server. Enter the SOURCE HOST which is the hostname or the IP address of the NFS server. Finally, enter the SOURCE DIRECTORY which is the directory path of the NFS share. Click SAVE.
+
+Once the modal is saved, it will take a few minutes to initialize the new datastore and show a successful online status in VM Essentials. Once this initialization process is completed, the datastore can now be used as VM storage for cluster.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json b/corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
new file mode 100644
index 0000000..6d09231
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+  "title": "Health",
+  "ordinal": 259,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html",
+  "topic_cluster": {
+    "clustering_title": "Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md b/corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
new file mode 100644
index 0000000..52a55e6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
@@ -0,0 +1,6 @@
+# Health
+
+**Subtopics**  
+
+- **[VM Essentials Health](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html)**
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json b/corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
new file mode 100644
index 0000000..6fc96b5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+  "title": "Networks",
+  "ordinal": 138,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html",
+  "topic_cluster": {
+    "clustering_title": "Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md b/corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
new file mode 100644
index 0000000..3b4f3f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
@@ -0,0 +1,8 @@
+# Networks
+
+Infrastructure  >  Network  >  Networks
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.html)**
+- **[Configuring Networks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-451A0EAA-D2AF-4529-AEF0-9543A638CE03.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json b/corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
new file mode 100644
index 0000000..d2b79ea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+  "title": "Create an Instance Backup",
+  "ordinal": 211,
+  "parent_title": "Backups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9DA38943-BF95-446D-AB09-32323160D51B.html",
+  "topic_cluster": {
+    "clustering_title": "Create an Instance Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+        "clustering_title": "Create an Instance Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9DA38943-BF95-446D-AB09-32323160D51B",
+        "clustering_title": "Create an Instance Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md b/corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
new file mode 100644
index 0000000..9732aea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9DA38943-BF95-446D-AB09-32323160D51B.md
@@ -0,0 +1,53 @@
+# Create an Instance Backup
+
+## About this task
+
+To create Instance backup:
+
+## Procedure
+
+1. Navigate to Backups > Backups
+2. Click + ADD
+3. From the Create Backup Wizard select the radio button for Instance, then click NEXT
+4. Input the following: 
+
+   Instance
+   :   Select an Instance to backup from the typeahead menu
+
+   Name
+   :   Enter a name for the backup job being created
+5. Click NEXT
+6. Depending on the Instance Type selected in the previous step, enter additional details. These can include a specific container, backup type, database name, username and password, or a number of other things depending on the Instance Type
+7. Configure the storage bucket and retention details: 
+
+   Storage
+   :   Select a configured storage bucket as the backup target
+
+   Backup Job Type
+   :   Create a new backup job, add this backup to an existing job, or clone an existing job to handle this backup
+
+   Job Name
+   :   If creating a new job, enter a name for the job
+
+   Retention Count
+   :   If creating a new job, enter the number of backups which should be simultaneously retained
+
+   Schedule
+   :   If creating a new job, select an execution schedule of which to run the backup
+
+   Synthetic Full
+   :   When the backup is targeting an HVM Instance, check this box to schedule synthetic full backups in addition to the normal full and incremental backups
+
+   Synthetic Full Schedule
+   :   If synthetic full backups are enabled, select an execution schedule on which to run the synthetic full backups
+8. Click COMPLETE.
+
+## Results
+
+NOTE
+
+On VMware Cloud types, VM Essentials will merge and consolidate the snapshots held against a VM before exporting the OVF to the storage location or share. This is so VM Essentials has a full and consistent copy of the VM state.
+
+TIP
+
+To edit an existing backup, click on the hyperlinked name of the backup job from the list of backups at Backups > Backups.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json b/corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
new file mode 100644
index 0000000..369038c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+  "title": "Archives",
+  "ordinal": 225,
+  "parent_title": "Tools",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html",
+  "topic_cluster": {
+    "clustering_title": "Archives",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md b/corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
new file mode 100644
index 0000000..7de1b2e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
@@ -0,0 +1,9 @@
+# Archives
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3AC9CEB6-F60C-46FA-83E1-769F4A989C10.html)**
+- **[Archives List Page](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.html)**
+- **[Adding an Archive](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4F6BB31D-D728-4328-86B8-DBD27CB5589A.html)**
+- **[Archive Detail Page](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-59EDC263-1E22-415A-8F24-8E9A0E0D0C50.html)**
+- **[File Detail Page](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-303E5EE7-A8F0-4555-BC8C-8A0D78A9BAD8.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json b/corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
new file mode 100644
index 0000000..e42af6f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+  "title": "Editing and Removing Domains",
+  "ordinal": 162,
+  "parent_title": "Domains",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.html",
+  "topic_cluster": {
+    "clustering_title": "Editing and Removing Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+        "clustering_title": "Editing and Removing Domains"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC",
+        "clustering_title": "Editing and Removing Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md b/corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
new file mode 100644
index 0000000..9e62c59
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9DEE3719-A49C-45E9-91DE-E4C3BEF855FC.md
@@ -0,0 +1,4 @@
+# Editing and Removing Domains
+
+- Domains can be edited by selecting the Actions dropdown for the Domain and selecting Edit, or by selecting the ✎ icon in list views.
+- Added Domains can be removed from VM Essentials by selecting the Actions dropdown for the Domain and selecting Remove, or the 🗑 icon in list views.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json b/corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
new file mode 100644
index 0000000..a02fa39
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+  "title": "Migrations Requirements",
+  "ordinal": 233,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md b/corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
new file mode 100644
index 0000000..de3253d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
@@ -0,0 +1,24 @@
+# Migrations Requirements
+
+This section contains requirements and recommendations that will ensure migrations run successfully. Keep an eye on this section as some requirements will change as this feature is updated over time to become more flexible.
+
+General Requirements
+:   - HVM Hosts must be upgraded to Agent version 2.10.0 at minimum. To upgrade the HVM Host Agent, navigate to the host detail page, open the ACTIONS menu, and select "Upgrade Agent." If this is unsuccessful, you may instead select "Download Agent Script" to download a shell script which may be run manually on the HVM Host. These download scripts are specific to the HVM Host so an individual install script would need to be downloaded for each HVM Host and run on the correct HVM Host.
+    - HVM Hosts must be able to reach ESXi hosts and vCenter on the target VMware vCenter Cloud via the Management Network
+    - The source VMs must be running for the preparation phase of the migration to complete successfully. If VMs are not running, they will automatically be restarted
+
+First Release Requirements
+:   This section includes requirements for the current version of the migration feature which are subject to change and improvement as road-mapped enhancements are included with subsequent versions of the product.
+
+    - If the target datastore is GFS2 or NFS, migrations will be "thin" QCOW2 rather than "thick" to reduce overhead and on-disk footprint. Other target datastore types must have enough "thick" space for each VM
+    - VMs will power down prior to the transfer meaning service of the source workload will be disrupted during the transfer
+    - VirtIO / VirtIO-SCSI target storage must be supported by the source VM
+    - Currently supported operating systems: RedHat, CentOS, Rocky, Alma, SUSE, Ubuntu, Debian, Windows (currently requires manual preparation steps described below)
+    - Source VMs must be capable of getting the `qemu-guest-tools` or `qemu-guest-agent` package installed.
+    - RDM (Raw Device Mappings) are not yet supported
+    - Source VMs must not have any attached ISOs or cdroms. These are not supported and the migration will fail.
+
+Recommendations
+:   - Batch limits and bandwidth limitations testing is still in progress. It's currently recommended you migrate no more than 20 VMs at a time. Testing is still ongoing to determine the upper limits of migrations and this recommendation is likely to increase over time
+    - Begin using this feature with a smaller migration than the limit to make sure your workloads are moving correctly
+    - When migrating to NFS-backed datastores, setting `async` on the NFS server may improve performance
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json b/corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
new file mode 100644
index 0000000..a9751b2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+  "title": "Source Options",
+  "ordinal": 61,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.html",
+  "topic_cluster": {
+    "clustering_title": "Source Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+        "clustering_title": "Source Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08",
+        "clustering_title": "Source Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md b/corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
new file mode 100644
index 0000000..ff7c3c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.md
@@ -0,0 +1,6 @@
+# Source Options
+
+Task configuration code may be entered locally or sourced via URL. Changing the SOURCE type will often update the available fields in the Task modal to accommodate the selected sourcing.
+
+- **Local:** The Task configuration code is written directly in VM Essentials in a large text area. VM Essentials includes syntax highlighting for easier debugging and script writing
+- **URL:** For Task configuration that can be source via an outside URL, specify the address in the URL field
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json b/corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
new file mode 100644
index 0000000..3c8ba71
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+  "title": "Subnets",
+  "ordinal": 146,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9FC58214-95C7-4690-91DA-3185640E3712.html",
+  "topic_cluster": {
+    "clustering_title": "Subnets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+        "clustering_title": "Subnets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9FC58214-95C7-4690-91DA-3185640E3712",
+        "clustering_title": "Subnets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md b/corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
new file mode 100644
index 0000000..423408d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9FC58214-95C7-4690-91DA-3185640E3712.md
@@ -0,0 +1,7 @@
+# Subnets
+
+Subnet details can be viewed from the SUBNETS tab on the detail page of a specific network. From the SUBNETS tab, Morpheus allows the user to search and edit existing subnets.
+
+In an Azure VNet, you can also create new subnets with the +ADD button.
+
+![../../_images/create_subnet_421.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-DAD09131-AC63-418D-9EE5-811611F8FB08-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json b/corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
new file mode 100644
index 0000000..080ff3a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+  "title": "DHCP",
+  "ordinal": 141,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.html",
+  "topic_cluster": {
+    "clustering_title": "DHCP",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+        "clustering_title": "DHCP"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C",
+        "clustering_title": "DHCP"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md b/corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
new file mode 100644
index 0000000..30a45e6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9FD14AFA-3E78-46BA-90E0-7CA03A0B357C.md
@@ -0,0 +1,26 @@
+# DHCP
+
+## About this task
+
+To configure a network for DHCP:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, set the DHCP flag as Active (default)
+5. Save Changes
+
+## Results
+
+IMPORTANT
+
+The DHCP flag tells VM Essentials this network has a DHCP server assigning IP Addresses to hosts. VM Essentials does not act as the DHCP server, and provisioning to a network that has the DHCP server flag active in VM Essentials, but no DHCP server actually on the network will, in most cases, cause the instance to not receive an IP address.
+
+NOTE
+
+When selecting a network with DHCP enabled during provisioning, “DHCP” will populate to the right of the selected network:
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json b/corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
new file mode 100644
index 0000000..54fbf97
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+  "title": "Defining Proxies",
+  "ordinal": 168,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.html",
+  "topic_cluster": {
+    "clustering_title": "Defining Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+        "clustering_title": "Defining Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766",
+        "clustering_title": "Defining Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md b/corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
new file mode 100644
index 0000000..1d68520
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-9FF6393B-3B5D-4409-B0BC-461062C5F766.md
@@ -0,0 +1,3 @@
+# Defining Proxies
+
+Proxies can be used in a few different contexts and optionally scoped to specific networks with which one may be provisioning into or on a cloud integration as a whole. To configure a Proxy for use by the provisioning engines within VM Essentials we must go to Infrastructure  >  Networks  >  Proxies. Here we can create records representing connection information for various proxies. This includes the host ip address, proxy port, and any credentials (if necessary) needed to utilize the proxy. Now that these proxies are defined we can use them in various contexts.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json b/corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
new file mode 100644
index 0000000..34d009f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+  "title": "Adding HPE Aruba CX DSS Network Integration",
+  "ordinal": 360,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE Aruba CX DSS Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+        "clustering_title": "Adding HPE Aruba CX DSS Network Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D",
+        "clustering_title": "Adding HPE Aruba CX DSS Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md b/corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
new file mode 100644
index 0000000..3f1d00e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.md
@@ -0,0 +1,35 @@
+# Adding HPE Aruba CX DSS Network Integration
+
+## Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Select + Add > Networking > HPEAruba CX DSS 
+
+   ![../../_images/addIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-61F5952F-CDFE-43E1-8A2B-445824B876A5-high.png)
+3. Enter the following details in the ADD NETWORK INTEGRATION form: 
+
+   NAME
+   :   Name of the integration in VM Essentials
+
+   AFC ADDRESS
+   :   Enter the network address of the AFC
+
+   AFC USERNAME
+   :   Enter the username
+
+   AFC PASSWORD
+   :   Enter the password
+
+   FABRIC NAME
+   :   Enter the fabric name from the AFC
+
+       ![../../_images/2_create_network_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5A349FA9-6B14-494D-B218-9F082BE5E18A-high.png)
+4. Click Add Network Integration
+
+## Results
+
+Upon add, the HPE Aruba CX DSS Network integration will be created.
+
+NOTE
+
+All fields can be edited after saving.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json b/corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
new file mode 100644
index 0000000..aedf9b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+  "title": "Datastore Types Pros and Cons",
+  "ordinal": 112,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A1E79BA5-CE31-4357-878E-11464E03158C.html",
+  "topic_cluster": {
+    "clustering_title": "Datastore Types Pros and Cons",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+        "clustering_title": "Datastore Types Pros and Cons"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A1E79BA5-CE31-4357-878E-11464E03158C",
+        "clustering_title": "Datastore Types Pros and Cons"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md b/corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
new file mode 100644
index 0000000..dc0bbc6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A1E79BA5-CE31-4357-878E-11464E03158C.md
@@ -0,0 +1,6 @@
+# Datastore Types Pros and Cons
+
+| Datastore Type | Directory Pools | NFS Pools | GFS2 Pools |
+| --- | --- | --- | --- |
+| **Pros** | - Simple to set up and easy to configure - No external dependencies - Uses the existing host filesystem | - Simple to set up - Centralized storage enables easy VM migration across hosts | - True shared disk, clustered filesystem - Pacemaker and Corosync provide high availability and fencing (reducing the risk of split brain) - Good for live VM migration and for clustered workloads |
+| **Cons** | - No redundancy - No capability for migration - Creates the potential for filling up the host filesystem and bringing the host down | - NFS server can be a single point of failure unless configured for high availability - Requires additional configuration not needed for Directory Pools - Network latency can cause performance issues | - More complex to configure and maintain - Requires reliable shared storage (SAN, iSCSI, etc) - Troubleshooting can be more complex |
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json b/corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
new file mode 100644
index 0000000..e3baef5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+  "title": "SELinux Settings",
+  "ordinal": 341,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A2A63203-21AB-4358-8706-62DF795EAE62.html",
+  "topic_cluster": {
+    "clustering_title": "SELinux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+        "clustering_title": "SELinux Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A2A63203-21AB-4358-8706-62DF795EAE62",
+        "clustering_title": "SELinux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md b/corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
new file mode 100644
index 0000000..9e0748e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A2A63203-21AB-4358-8706-62DF795EAE62.md
@@ -0,0 +1,10 @@
+# SELinux Settings
+
+## About this task
+
+If allowed by your internal IT policies, set SELinux to permissive to avoid potential issues with cloud-init down the road.
+
+## Procedure
+
+1. Edit the following: `vi /etc/selinux/config`
+2. Make the following change: `setenforce 0`
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json b/corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
new file mode 100644
index 0000000..0ef00b1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+  "title": "Terraform Settings",
+  "ordinal": 283,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+        "clustering_title": "Terraform Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C",
+        "clustering_title": "Terraform Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md b/corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
new file mode 100644
index 0000000..b8083c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.md
@@ -0,0 +1,3 @@
+# Terraform Settings
+
+- **Terraform Runtime:** Select “auto” or “manual”. When selecting “auto”, VM Essentials will automatically download and use the Terraform version indicated in the VERSION field on the Spec Templates that make up a Terraform Instance type or Blueprint. When selecting “manual”, VM Essentials will use the version of Terraform [installed on your appliance](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html?#terraform-installation).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json b/corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
new file mode 100644
index 0000000..5a8c9ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+  "title": "Overview",
+  "ordinal": 71,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A391DC49-6523-4517-9AE1-F2E78CE91411",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md b/corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
new file mode 100644
index 0000000..50ef90f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A391DC49-6523-4517-9AE1-F2E78CE91411.md
@@ -0,0 +1,11 @@
+# Overview
+
+The Virtual Image section displays a list of all images, local and synced, that are available to deploy. VM Essentials includes a rich catalog of pre-configured default images for HVM clusters or for VMware vCenter Cloud targets as well. User Images are automatically synced from Cloud Integrations and added to the Virtual Images section. Images can also be uploaded directly into VM Essentials via local file or url. Understanding the process of prepping images for consumption in VM Essentials is a very important step toward building an effective VM Essentials environment.
+
+IMPORTANT
+
+Invalid Image Settings cause provisioning failures. VM Essentials syncs in as much metadata as possible for synced images, but additional configuration may be needed to ensure successful provisioning.
+
+WARNING
+
+Cloud-init is enabled by default for all Linux images. If your Linux image does not have Cloud-init installed, Cloud-init Enabled must be unchecked before provisioning the image or it will fail immediately.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json b/corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
new file mode 100644
index 0000000..1f3aded
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+  "title": "Current License",
+  "ordinal": 292,
+  "parent_title": "License",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.html",
+  "topic_cluster": {
+    "clustering_title": "Current License",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+        "clustering_title": "Current License"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B",
+        "clustering_title": "Current License"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md b/corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
new file mode 100644
index 0000000..bacba1d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A3EE4127-5F12-4F3A-89EA-138882DA237B.md
@@ -0,0 +1,9 @@
+# Current License
+
+If a License Key has already been applied, it will be shown in the list of Current Licenses. This page also contains useful information on license usage including start and end dates for the license, the total number of HVM sockets licensed, and how many of the licensed HVM sockets have been used.
+
+NOTE
+
+Once a current License expires or has reached its limits, users will no longer be able to provision new Instances or Clusters and will not be able to convert existing VMs to managed. HPE Morpheus VM Essentials will otherwise continue to function.
+
+![The license settings page](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-DEE9EE99-95C7-48D3-9CA5-26BD14693D4D-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json b/corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
new file mode 100644
index 0000000..5d9b4f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
@@ -0,0 +1,21 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+  "title": "Host Hardware Sensor Data Collection",
+  "ordinal": 127,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html",
+  "topic_cluster": {
+    "clustering_title": "Host Hardware Sensor Data Collection",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+        "clustering_title": "Host Hardware Sensor Data Collection"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md b/corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
new file mode 100644
index 0000000..e8560d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
@@ -0,0 +1,27 @@
+# Host Hardware Sensor Data Collection
+
+If properly configured, HVM Hosts can display detailed hardware information on the HVM Hosts detail pages. This information includes system health LED state, CPU temperature, ambient temperature, fan speeds, power supply state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-BC8DF5F3-1416-4BE4-B58F-CB1926EF7DD2-high.png)
+
+Configuration
+
+In order to surface hardware sensor data into the UI, IPMI tool and it's dependency packages must be installed on each host. Following installation, the host agent must be restarted.
+
+1. Install IPMI tool and its dependency packages (`freeipmi-common`, `ipmitool`, `libfreeipmi17`, `openipmi`)
+
+   NOTE
+
+   This tool can also be installed via apt package manager provided that the corresponding Ubuntu mirrors (main and universe module repos) are enabled. Run `sudo apt update` and then `sudo apt install ipmitool`.
+2. To confirm installation, run `sudo ipmitool -v` and the installed version should be displayed
+3. Restart the host agent with `sudo morpheus-node-ctl restart`
+4. Repeat this process on all cluster hosts
+
+Viewing Hardware Sensor Data
+
+When properly configured, hardware sensor data may be viewed from the host detail page:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM cluster
+3. Select the Health subtab
+4. The hardware sensor states and hardware events are shown in the Sensors and Events subtabs
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json b/corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
new file mode 100644
index 0000000..28f4239
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+  "title": "Archives List Page",
+  "ordinal": 227,
+  "parent_title": "Archives",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.html",
+  "topic_cluster": {
+    "clustering_title": "Archives List Page",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+        "clustering_title": "Archives List Page"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA",
+        "clustering_title": "Archives List Page"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md b/corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
new file mode 100644
index 0000000..84be63d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A48E64B3-16CC-4E47-BCAD-3B0ADBFC26FA.md
@@ -0,0 +1,12 @@
+# Archives List Page
+
+To view or create Archives, navigate to Tools > Archives. At the Archives list page is a list of all currently-configured Archives. From the list view, the following details about each Archive are shown:
+
+- **NAME:** The name for the Archive in VM Essentials
+- **BUCKET:** The integrated bucket or file share where files in this Archive are stored
+- **# Files:** The number of files in the Archive
+- **SIZE:** The total size of all files in the Archive
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants listed here have access to the Archive
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **PUBLIC URL:** Indicates whether VM Essentials is automatically generating a public download URL for files in this Archive
+- **ACTIONS:** Within the ACTIONS menu users may download a ZIP folder containing all files in the Archive, edit the Archive, or remove it
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json b/corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
new file mode 100644
index 0000000..3355bd9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+  "title": "Windows Settings",
+  "ordinal": 279,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A5F5433C-0F21-4877-BFC6-522D421A1842",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md b/corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
new file mode 100644
index 0000000..b496e32
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.md
@@ -0,0 +1,3 @@
+# Windows Settings
+
+- **Administrator Password:** Enter password to be set for the Windows Administrator User during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json b/corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
new file mode 100644
index 0000000..a346a61
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+  "title": "Running Automation Against Label Targets",
+  "ordinal": 54,
+  "parent_title": "Labels",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.html",
+  "topic_cluster": {
+    "clustering_title": "Running Automation Against Label Targets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+        "clustering_title": "Running Automation Against Label Targets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33",
+        "clustering_title": "Running Automation Against Label Targets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md b/corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
new file mode 100644
index 0000000..31e5119
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A742B359-6C9C-4BC0-AA52-30189D93AA33.md
@@ -0,0 +1,7 @@
+# Running Automation Against Label Targets
+
+Tasks can be run against Instance Labels or Server Labels. When executing the Task, select either Server Label or Instance Label. After specifying the Label, the automation will be run against all Instances or Servers which have the indicated Label. Currently, only one Label may be selected and users cannot enter multiple Labels in the field. If a non-existent Label is entered, the automation simply will not run against any Workloads since the Label does not match any.
+
+NOTE
+
+Instance and server Labels are separate. Even if some Instances or servers have the same Label, the automation is only run against the selected construct (Instance Labels or Server Labels).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.json b/corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
new file mode 100644
index 0000000..9127e71
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+  "title": "Default Storage",
+  "ordinal": 176,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A745B955-2E59-4769-AB47-E32098A84653.html",
+  "topic_cluster": {
+    "clustering_title": "Default Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+        "clustering_title": "Default Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A745B955-2E59-4769-AB47-E32098A84653",
+        "clustering_title": "Default Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.md b/corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
new file mode 100644
index 0000000..4e80b7f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A745B955-2E59-4769-AB47-E32098A84653.md
@@ -0,0 +1,7 @@
+# Default Storage
+
+The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is `var/opt/morpheus/morpheus-ui/`. It is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure > Storage section to avoid running out of disk space on the VM Essentials Appliance.
+
+**Subtopics**  
+
+- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json b/corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
new file mode 100644
index 0000000..337a283
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+  "title": "To edit and configure an existing Virtual Image:",
+  "ordinal": 75,
+  "parent_title": "User Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.html",
+  "topic_cluster": {
+    "clustering_title": "To edit and configure an existing Virtual Image:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+        "clustering_title": "To edit and configure an existing Virtual Image:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-A7CB5566-0283-4C67-BA27-02852732D7C3",
+        "clustering_title": "To edit and configure an existing Virtual Image:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md b/corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
new file mode 100644
index 0000000..dde7c74
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-A7CB5566-0283-4C67-BA27-02852732D7C3.md
@@ -0,0 +1,69 @@
+# To edit and configure an existing Virtual Image:
+
+## Procedure
+
+1. Select the pencil icon at the right of any row on the Virtual Images list page, or click EDIT on a Virtual Image detail page.
+2. Configure the following on the Image: 
+
+   Name
+   :   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant VM Essentials environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, VM Essentials will install the FIPS-compliant VM Essentials Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to VMware vCenter Clouds. Enable if the Windows Image has been sysprepped. If enabled, VM Essentials will inject `unattend.xml`
+3. Click Save Changes 
+
+   NOTE
+
+   Cloud-Init is enabled by default on all images. Images without Cloud-Init or Cloudbase-Init installed must have the `cloud-init` flag disabled on the Virtual Image setting or Provisioning may fail.
+
+   IMPORTANT
+
+   VM Essentials does not validate or restrict image uploads to certain file types and any type of file may be uploaded as a Virtual Image. For security purposes, these files are stored in a non-executable state so users need not worry about potentially dangerous file types being uploaded (ex. executables).
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.json b/corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.json
new file mode 100644
index 0000000..200541b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+  "title": "Administration",
+  "ordinal": 236,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AAD13737-533B-491F-A155-DDB027057157.html",
+  "topic_cluster": {
+    "clustering_title": "Administration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+        "clustering_title": "Administration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AAD13737-533B-491F-A155-DDB027057157",
+        "clustering_title": "Administration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.md b/corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.md
new file mode 100644
index 0000000..a2888ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AAD13737-533B-491F-A155-DDB027057157.md
@@ -0,0 +1,14 @@
+# Administration
+
+There are several administrative integrations built into VM Essentials that make it great to work with within any organization ranging from small to large. Especially, with its built in white label support and multitenancy capabilities, managed service providers have a wide range of capabilities when it comes to managing customer accounts and users.
+
+**Subtopics**  
+
+- **[Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html)**
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.html)**
+- **[Health](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html)**
+- **[Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8DFFB70B-3D9D-411E-A0E2-3AB2E303B467.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json b/corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
new file mode 100644
index 0000000..651c532
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+  "title": "Host Features",
+  "ordinal": 102,
+  "parent_title": "Features",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "hvm_deployment_guide",
+        "page_id": "GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md b/corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
new file mode 100644
index 0000000..e6d043d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.md
@@ -0,0 +1,19 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and datastores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Governance through VM Essentials RBAC
+- Pass host-attached NVME, USB, and GPU hardware through to VMs running on the host
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json b/corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
new file mode 100644
index 0000000..8f6b9e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+  "title": "Routers",
+  "ordinal": 149,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html",
+  "topic_cluster": {
+    "clustering_title": "Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md b/corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
new file mode 100644
index 0000000..843da87
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
@@ -0,0 +1,8 @@
+# Routers
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7138E486-AE62-4778-9358-F098126785A5.html)**
+- **[Create New Router](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-61053EC5-4910-454F-8B71-6B06408A6451.html)**
+- **[Editing Existing Routers](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-76B546AD-121A-4C3A-B42C-D642C8624A3C.html)**
+- **[Deleting Existing Routers](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1A0E37CA-DAC9-49DE-99D3-FC177AB78047.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json b/corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
new file mode 100644
index 0000000..ca96325
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.json
@@ -0,0 +1,31 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+  "title": "VM Features",
+  "ordinal": 103,
+  "parent_title": "Features",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "hvm_deployment_guide",
+        "page_id": "GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md b/corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
new file mode 100644
index 0000000..558534e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Console support for running workloads
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore VM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- VM Essentials library and automation support
+- Claim and consume host-attached NVME, USB, and GPU hardware to run hardware-accelerated workloads on VMs
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json b/corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
new file mode 100644
index 0000000..d6885e6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+  "title": "Integrating With a Currency Exchange Provider",
+  "ordinal": 273,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AC461BBD-647D-447D-9307-218A41CE368B.html",
+  "topic_cluster": {
+    "clustering_title": "Integrating With a Currency Exchange Provider",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+        "clustering_title": "Integrating With a Currency Exchange Provider"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AC461BBD-647D-447D-9307-218A41CE368B",
+        "clustering_title": "Integrating With a Currency Exchange Provider"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md b/corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
new file mode 100644
index 0000000..b1d8f00
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AC461BBD-647D-447D-9307-218A41CE368B.md
@@ -0,0 +1,11 @@
+# Integrating With a Currency Exchange Provider
+
+## Procedure
+
+1. Navigate to Administration > Settings > Appliance
+2. Under the Currency Settings heading, make a “Currency Provider” selection
+3. Enter your “Provider API Key”
+
+## Results
+
+The service is now integrated and can be used as described in the next section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json b/corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
new file mode 100644
index 0000000..671141b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+  "title": "Notes",
+  "ordinal": 50,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.html",
+  "topic_cluster": {
+    "clustering_title": "Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+        "clustering_title": "Notes"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302",
+        "clustering_title": "Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md b/corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
new file mode 100644
index 0000000..0a09a5a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.md
@@ -0,0 +1,7 @@
+# Notes
+
+Every Instance has a Wiki section for adding useful information about the Instance. Wiki can be added by selecting the Wiki tab on the bottom of the Instance Detail page. Instances with associated VMware VMs will bi-directionally sync VM Essentials Wiki content and VMware VM Notes. See the [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CD00669C-741C-480C-B444-67F079061438.html) Section for more details.
+
+TIP
+
+Markdown Syntax is supported in Wikis.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json b/corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
new file mode 100644
index 0000000..bb8442c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+  "title": "Alibaba Buckets",
+  "ordinal": 179,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.html",
+  "topic_cluster": {
+    "clustering_title": "Alibaba Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+        "clustering_title": "Alibaba Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778",
+        "clustering_title": "Alibaba Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md b/corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
new file mode 100644
index 0000000..3ee20c7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ADF74748-AB0E-42F4-BB23-79C5B079A778.md
@@ -0,0 +1,77 @@
+# Alibaba Buckets
+
+## About this task
+
+To Add an Alibaba Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Alibaba from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   ACCESS KEY
+   :   Alibaba Access Key
+
+   SECRET KEY
+   :   Alibaba Secret Key
+
+   REGION
+   :   Enter Alibaba Region for the Bucket
+
+   BUCKET NAME
+   :   Enter existing Alibaba Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   Create Bucket
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json b/corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
new file mode 100644
index 0000000..5bb525b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+  "title": "Integration Guides",
+  "ordinal": 313,
+  "parent_title": "Guides",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html",
+  "topic_cluster": {
+    "clustering_title": "Integration Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md b/corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
new file mode 100644
index 0000000..707b4f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
@@ -0,0 +1,7 @@
+# Integration Guides
+
+**Subtopics**  
+
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA_2.html)**
+- **[Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json b/corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
new file mode 100644
index 0000000..2e344c0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+  "title": "Utilizing Existing QCOW & ISO Images from an NFS File Share",
+  "ordinal": 130,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.html",
+  "topic_cluster": {
+    "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+        "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7",
+        "clustering_title": "Utilizing Existing QCOW & ISO Images from an NFS File Share"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md b/corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
new file mode 100644
index 0000000..b3644e4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.md
@@ -0,0 +1,38 @@
+# Utilizing Existing QCOW & ISO Images from an NFS File Share
+
+Integrated NFS shares can be used both as a repository for HVM cluster images and as a target for saving new images from existing VMs. This offers benefits of greatly expanding the available storage compared to what’s available on the VM Essentials manager VM, insulates you from issues that can arise from images completely filling the manager storage, and allows for the same images to be easily integrated with multiple VM Essentials appliances.
+
+To begin, we need the NFS file share integrated with VM Essentials. This is done in the Infrastructure > Storage section of the UI. This guide assumes the NFS file share is pre-existing and the VM Essentials manager can reach it. Actually setting up an NFS file share goes beyond the scope of this guide. From the File Shares tab, check to see the desired file share is already integrated. If needed, you can add one by clicking + ADD and then selecting “NFSv3”.
+
+When adding a new file share, configure the following:
+
+- **NAME:** A friendly name for the file share within VM Essentials
+- **HOST:** The IP address or hostname for the NFS file share server
+- **EXPORT FOLDER:** The path to the folder that should be mounted to the manager
+- **ACTIVE:** Must be checked to be able to consume this file share elsewhere in VM Essentials manager UI
+- **DEFAULT VIRTUAL IMAGE STORE:** (Optional) Select if you wish this file share to be the default store for newly uploaded or generated images
+
+When done, click Save changes.
+
+![../../_images/editFileshare.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-CD1D4AB9-1183-4739-8E61-1FB428D244B9-high.png)
+
+IMPORTANT
+
+You must configure the NFS share to give VM Essentials manager read and write access if you want to be able to read images from and write images to the file share. Configuring NFS file shares goes beyond the scope of this guide. Deleting files from an integrated file share deletes the actual file and not just the representation of the file in VM Essentials. This includes Virtual Images. Deleting a Virtual Image that is backed by a QCOW or an ISO image files stored in an integrated file share will also cause the file itself to be deleted in addition to the Virtual Image object within VM Essentials.
+
+With the file share integrated, we can now create Virtual Images which are backed by QCOW or ISO images that are pre-existing in the file share. Navigate to Library > Virtual Images and click + ADD. From the dropdown, select “QCOW2” or "ISO". Make the configurations specified below. Those not mentioned can often be left on the default value. For a deeper explanation of configurations not mentioned here, see the dedicated section of VM Essentials documentation on Virtual Images.
+
+- **NAME:** A friendly name for the image in VM Essentials
+- **OPERATING SYSTEM:** Specify the operating system of the image
+- **MINIMUM MEMORY:** Enter a minimum memory value and VM Essentials will not allow the image to be provisioned using a plan with lower memory
+- **BUCKET:** Select the NFS share integrated in the previous step
+- **CREATE IMAGE ID:** Set to “URL/PATH”
+- **URL:** Enter the path to a QCOW or an ISO image within the file share. See the next paragraph for a deeper explanation of how to enter the path properly
+
+The entered path to the QCOW or an ISO image should not include the name of the NFS share or the name of the file itself. See the portion highlighted in the screenshot:
+
+![../../_images/viewQcow.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5EB8987F-1490-43A7-84A4-875FBCE66FEB-high.png)
+
+It also should only be the path to the folder containing the QCOW or an ISO image. The file name itself should not be part of the path. For example, `templates/qcow/ubuntu/server/2204/011025`. Click Save changes.
+
+With the NFS file share integrated and the Virtual Image created, the image is now usable from the provisioning wizard. This guide won’t fully cover the use of the provisioning wizard but from the Configure tab of the wizard, the image is now selectable (assuming you’ve selected a compatible provisioning target). Additionally, we can now click into the detail page for running Instances and save them to images backed by the NFS file share. From the Instance detail page, click Actions, then “Import as Image.” You’ll be able to set a name for the new image and specify the NFS file share as the target bucket.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json b/corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
new file mode 100644
index 0000000..5b71e7f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+  "title": "Logs",
+  "ordinal": 263,
+  "parent_title": "Health",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.html",
+  "topic_cluster": {
+    "clustering_title": "Logs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+        "clustering_title": "Logs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297",
+        "clustering_title": "Logs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md b/corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
new file mode 100644
index 0000000..419633f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-AFF4C609-07DB-429C-B7A7-82F9568D6297.md
@@ -0,0 +1,3 @@
+# Logs
+
+The VM Essentials logs tab aggregates appliance-specific logs into one list. If needed, users can export the logs by clicking EXPORT. This action triggers a download containing the last 10,000 log entries as a `.log` file.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json b/corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
new file mode 100644
index 0000000..0d14d0b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+  "title": "Maintaining GFS2 Consistency and High Availability",
+  "ordinal": 120,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B3241978-4E00-4630-A8AB-E597193E51E2.html",
+  "topic_cluster": {
+    "clustering_title": "Maintaining GFS2 Consistency and High Availability",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+        "clustering_title": "Maintaining GFS2 Consistency and High Availability"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B3241978-4E00-4630-A8AB-E597193E51E2",
+        "clustering_title": "Maintaining GFS2 Consistency and High Availability"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md b/corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
new file mode 100644
index 0000000..23faa0c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B3241978-4E00-4630-A8AB-E597193E51E2.md
@@ -0,0 +1,38 @@
+# Maintaining GFS2 Consistency and High Availability
+
+HVM Clusters utilize several open-source technologies to maintain consistency and high availability when GFS2 external storage is utilized. This section lists those technologies and a high level overview of how they work together to prevent data corruption and facilitate smooth failover when a cluster host is lost.
+
+Corosync
+
+- Open-source cluster engine providing a high-performance messaging layer
+- Ensures node communication and consistent cluster state in high availability systems
+- Tracks active nodes and prevents split-brain scenarios
+- Provides are reliable messaging backbone for syncronizing state and data
+- Handles node failures and reconfigures the cluster automatically
+- Works with Pacemaker as part of a full HA stack providing automatic failover
+- Distributes lock information, detects failures, and triggers fencing
+
+Pacemaker
+
+- Open-source HA resource manager
+- Ensures services and resources run on correct nodes, even during failures
+- Works with Corosync for messaging and membership
+- Handles resource management, such as IP addresses, filesystems, and services
+- Depects failures and facilitates automatic failover and restart
+- Manages GFS2 mounts, distributed lock management, and fencing agents (split-brain prevention)
+- Relocates VMs and services automatically on node failure
+
+Distributed Lock Manager (DLM)
+
+- Ensures data integrity in GFS2 clusters by managing file and metadata locks
+- Allows just one node to modify a resource at a time, preventing data corruption
+- Shares lock info across the cluster
+- Utilizes Corosync messaging to synchnonize lock states
+- On node failure, fencing releases locks safety before recovery
+
+Fencing
+
+- Ensures data integrity if a node fails
+- Isolates failed nodes from shared storage to prevent data corruption
+- Uses STONITH fencing method to completely disable nodes considered to be down to ensure they cannot access shared storage
+- Releases locks only when unresponsive nodes are safely fenced
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json b/corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
new file mode 100644
index 0000000..aee1ece
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+  "title": "Users",
+  "ordinal": 251,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html",
+  "topic_cluster": {
+    "clustering_title": "Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md b/corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
new file mode 100644
index 0000000..83cd525
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
@@ -0,0 +1,5 @@
+# Users
+
+**Subtopics**  
+
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123_2.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json b/corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
new file mode 100644
index 0000000..5e2dcf4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+  "title": "User Photo",
+  "ordinal": 296,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html",
+  "topic_cluster": {
+    "clustering_title": "User Photo",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md b/corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
new file mode 100644
index 0000000..36ec146
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
@@ -0,0 +1,3 @@
+# User Photo
+
+Upload a custom image for your user avatar that is displayed in the top header and user administration sections. **Suggested Photo Dimensions: 128 x 128**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json b/corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
new file mode 100644
index 0000000..9bb4c4d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+  "title": "Network Interfaces",
+  "ordinal": 342,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.html",
+  "topic_cluster": {
+    "clustering_title": "Network Interfaces",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+        "clustering_title": "Network Interfaces"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3",
+        "clustering_title": "Network Interfaces"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md b/corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
new file mode 100644
index 0000000..de88cb2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.md
@@ -0,0 +1,18 @@
+# Network Interfaces
+
+## About this task
+
+Run the following to rename the network NIC. Values inside angle brackets should be filled in with the appropriate value for your environment (ex. <varname>):
+
+## Procedure
+
+1. `sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub`
+2. `grub2-mkconfig -o /boot/grub2/grub.cfg` (location may be different, could be located at /boot/efi/EFI/centos/grub.cfg)
+3. `ifdown <orginal-nic>`
+4. `mv /etc/sysconfig/network-scripts/<orginal-nic> /etc/sysconfig/network-scripts/ifcfg-eth0` (this changes name/device to eth0)
+5. Edit `ifcfg-eth0` and change the NAME to `eth0`
+6. `bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'`
+7. `ip link set <orginal-nic> down`
+8. `ip link set <orginal-nic> name eth0`
+9. `ip link set eth0 up`
+10. `ifup eth0`
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json b/corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
new file mode 100644
index 0000000..92b042c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+  "title": "Execute Options",
+  "ordinal": 60,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+        "clustering_title": "Execute Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8",
+        "clustering_title": "Execute Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md b/corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
new file mode 100644
index 0000000..b176cdb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.md
@@ -0,0 +1,7 @@
+# Execute Options
+
+- **Continue on Error:** When marked, automation stacks including this Task can continue when this Task fails. Additionally, Instances provisioned with this Task as part of its automation stack can be considered provisioned successfully even if this Task has failed
+- **Retryable:** When marked, this Task can be configured to be retried in the event of failure
+- **Retry Count:** The maximum number of times the Task will be retried when there is a failure
+- **Retry Delay:** The length of time (in seconds) VM Essentials will wait to retry the Task
+- **Allow Custom Config:** When marked, a text area is provided at Task execution time to allow the user to pass extra variables or specify extra configuration. See the next section for an example.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json b/corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
new file mode 100644
index 0000000..118c976
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+  "title": "Getting Started",
+  "ordinal": 2,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md b/corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
new file mode 100644
index 0000000..8630a95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B5E3A52C-D672-4AED-88FB-3A607EB3F33B.md
@@ -0,0 +1,14 @@
+# Getting Started
+
+HPE Morpheus VM Essentials Software is a unified solution allowing for easy deployment of KVM-based HVM workloads and intuitive integration of existing VMware vCenter Clouds, all with administration made easy through the HPE Morpheus VM Essentials Manager. Once deployed, take advantage of powerful features including live migration of VMs across HVM Cluster hosts with zero downtime, dynamically distribute workloads based on load, automatic failover of workloads following the loss of a host, and a lot more. Provisioning new workloads is also made easy with the VM Essentials image library, automation tools, and powerful provisioning wizard. In addition to HVM clusters, VM Essentials also includes a deep integration into VMware vCenter, which also takes advantage of the same powerful provisioning wizard, automation engine, and monitoring capabilities.
+
+This documentation covers the system requirements for HVM clusters and a setup guide for installing VM Essentials manager. It also includes example use cases for effective implementation of the feature set and in-depth sections for each area of the UI detailing the capabilities of each tool.
+
+Before getting started, it’s important to note that administrators have the responsibility to install and configure servers and network equipment in a way that will ensure successful operation of VM Essentials. This includes selecting host servers, storage hardware, and networking hardware that have been certified as compatible with the platform. The VM Essentials section of the [HPE Support Center](https://www.hpe.com/support/VME-Docs) contains a reference architecture document which includes a validated design with specific hardware SKUs. The same section of the HPE Support Center also includes a qualification matrix which lists hardware that has been certified compatible.
+
+Additionally, administrators will be required to perform some setup functions on their own, such as preinstalling Ubuntu 24.04 (or 22.04 though you won’t be able to utilize the latest cluster layouts) on host servers, configuring networking for each host, configuring access to external storage at the OS level, and establishing a network topology that ensures acceptable performance. Subsequent sections of this document will outline some effective network designs and some tips for selecting a network design based on available hardware. It will be the responsibility of the administrator to select a network design based on available hardware and to use the Linux command line to establish appropriate network bonds, storage configuration, and access across the cluster.
+
+**Subtopics**  
+
+- **[Deployment Guide](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5AEA3215-5E74-4F8D-9CE3-C4A827534A63.html)**
+- **[Elevating to HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json b/corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
new file mode 100644
index 0000000..782a275
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+  "title": "Moving Workloads Between Hosts",
+  "ordinal": 122,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.html",
+  "topic_cluster": {
+    "clustering_title": "Moving Workloads Between Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md b/corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
new file mode 100644
index 0000000..13627fc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.md
@@ -0,0 +1,9 @@
+# Moving Workloads Between Hosts
+
+To manually move workloads between hosts, drill into the detail page for the VM (from the VMs tab of the cluster detail page). Click ACTIONS and select “Manage Placement”. Choose a different host and select from the following placement strategies:
+
+- **Auto:** Manages VM placement based on load
+- **Failover:** Moves VMs only when failover is necessary
+- **Pinned:** Will not move this workload from the selected host
+
+Within a short time, the workload is moved to the new host.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json b/corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
new file mode 100644
index 0000000..36e7f1c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+  "title": "Managing Instances",
+  "ordinal": 47,
+  "parent_title": "Instances",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+        "clustering_title": "Managing Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C",
+        "clustering_title": "Managing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md b/corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
new file mode 100644
index 0000000..4fb7db9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B6D2D749-9BFC-4304-8B26-2C1DE7F9815C.md
@@ -0,0 +1,23 @@
+# Managing Instances
+
+Instance actions allow you to perform numerous management tasks on instances. The actions available depend on the instance type, hypervisor, roles permissions, and instance state. Actions can be accessed from the Instances list page or from an Instance detail page.
+
+Edit
+:   Edit the Name, Description, Environment, Group, Tags, and Owner for the Instance.
+
+Delete
+:   Deletes the Instance.
+
+IMPORTANT
+
+Deleting an Instance will delete the actual underlying VMs or Containers and cannot be undone.
+
+TIP
+
+You can change the owner of an instance easily by selecting the edit button and entering a new owner in the corresponding field.
+
+**Subtopics**  
+
+- **[Actions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.html)**
+- **[Performing Instance Actions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-278B93C4-6B70-476F-B530-A2DBA4269FD8.html)**
+- **[Notes](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AD8C9349-D94C-47E1-9E1B-EC24B9BD8302.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json b/corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
new file mode 100644
index 0000000..7b2119d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+  "title": "Features",
+  "ordinal": 101,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md b/corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
new file mode 100644
index 0000000..7f7208e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
@@ -0,0 +1,6 @@
+# Features
+
+**Subtopics**  
+
+- **[Host Features](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AAEE49BC-286E-4C04-9664-4A2FEBDFDCA0.html)**
+- **[VM Features](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AC33B458-3F39-4BA6-A242-E00B613C60DA.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json b/corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json
new file mode 100644
index 0000000..572405f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.json
@@ -0,0 +1,21 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701",
+  "title": "Manage Security Groups and Rules in Morpheus",
+  "ordinal": 361,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.html",
+  "topic_cluster": {
+    "clustering_title": "Manage Security Groups and Rules in Morpheus",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701",
+        "clustering_title": "Manage Security Groups and Rules in Morpheus"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md b/corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md
new file mode 100644
index 0000000..2a15b80
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.md
@@ -0,0 +1,17 @@
+# Manage Security Groups and Rules in Morpheus
+
+To manage security groups and rules in Morpheus, follow these steps:
+
+1. Navigate to Infrastructure > Network > Security Groups
+2. Select + ADD
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-7883AC52-480A-4E33-AB01-6703E3A41809-high.png)
+3. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-2145D633-F35B-41FC-950C-363353E38E8B-high.png)
+4. Within the new Security Group, select + Add Rule
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-2BA30350-BAC9-420C-90A3-381E66B9AF9D-high.png)
+5. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-CA593188-8380-492C-AAA7-08766D278427-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json b/corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
new file mode 100644
index 0000000..822319f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+  "title": "Docker",
+  "ordinal": 325,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B82658C8-6002-424B-B257-D52A7D603BC3.html",
+  "topic_cluster": {
+    "clustering_title": "Docker",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+        "clustering_title": "Docker"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B82658C8-6002-424B-B257-D52A7D603BC3",
+        "clustering_title": "Docker"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md b/corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
new file mode 100644
index 0000000..b506211
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B82658C8-6002-424B-B257-D52A7D603BC3.md
@@ -0,0 +1,7 @@
+# Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by VM Essentials out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. VM Essentials views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the VM Essentials appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json b/corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
new file mode 100644
index 0000000..3d997f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+  "title": "Role Creation",
+  "ordinal": 246,
+  "parent_title": "Overview",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.html",
+  "topic_cluster": {
+    "clustering_title": "Role Creation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+        "clustering_title": "Role Creation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF",
+        "clustering_title": "Role Creation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md b/corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
new file mode 100644
index 0000000..16e3722
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B8673710-26A0-45E1-AD2D-0937F4C81DDF.md
@@ -0,0 +1,9 @@
+# Role Creation
+
+Roles are created within Administration > Roles. Creating a Role requires minimal information, just a Name for the Role in VM Essentials. You can optionally add a Description and a Landing URL as well. The landing URL determines the starting page for the User on initial login (such as the Instances list page or perhaps the detail page for a primary HVM cluster). Following creation, click into the Role from the Roles list page and you will see the granular controls available to Roles. These controls include access permissions for UI feature sections, Groups, Cluster types, and configured Tasks. Changes are automatically saved for the Role, there is no need to click a button to save any updates. See the next section for a detailed breakdown of individual feature permissions.
+
+Master tenant users are able to create a special type of user role called a multi-tenant user role. A multi-tenant user role is copied / duplicated down to all subtenants within VM Essentials. These can be viewed as canned role templates available to new tenants when their account is first created. Any changes made to the main role are propagated down to the subtenants version of the shared role so long as the subtenant users have not previously adjusted/changed that role. The moment a subtenant makes adjustments to the shared role within their account, it is unlinked from the parent role and treated entirely independently. In order to relink the Role in the Subtenant, a Master Tenant user would have to edit the Role, uncheck MULTITENANT USER ROLE, save the Role, check MULTITENANT USER ROLE once again, then save the Role once again.
+
+Another note about user roles is that when a user role is copied down to a subtenant, the permission scopes cannot supersede the tenant’s assigned tenant role. If they do they are automatically downgraded when propagated to the specific tenant. Any changes made to the tenant role will automatically ensure roles within the tenant are downgraded appropriately.
+
+Master Tenant administrators may edit permissions for Roles in other Tenants by viewing the Tenant detail page (Administration > Tenants > Selected Tenant) and accessing the Roles tab. From there, select the Role to edit and make changes on the resulting Role detail page.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json b/corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
new file mode 100644
index 0000000..ae4e425
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+  "title": "Creating a CentOS/RHEL 8 Image",
+  "ordinal": 339,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a CentOS/RHEL 8 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+        "clustering_title": "Creating a CentOS/RHEL 8 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42",
+        "clustering_title": "Creating a CentOS/RHEL 8 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md b/corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
new file mode 100644
index 0000000..bb8affd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.md
@@ -0,0 +1,10 @@
+# Creating a CentOS/RHEL 8 Image
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux build. You must be running ESXi 6.7 Update 2 or later.
+
+**Subtopics**  
+
+- **[Prepare The New CentOS 8/RHEL8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.html)**
+- **[SELinux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A2A63203-21AB-4358-8706-62DF795EAE62.html)**
+- **[Network Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B54D93CF-2212-4A58-9171-AC6A40CC45C3.html)**
+- **[Final VMWare Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json b/corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
new file mode 100644
index 0000000..6040c13
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+  "title": "VMware tools (vmtools) RPC mode",
+  "ordinal": 38,
+  "parent_title": "Agent Install",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.html",
+  "topic_cluster": {
+    "clustering_title": "VMware tools (vmtools) RPC mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+        "clustering_title": "VMware tools (vmtools) RPC mode"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142",
+        "clustering_title": "VMware tools (vmtools) RPC mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md b/corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
new file mode 100644
index 0000000..d5332c3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B8FB507C-D7BB-462A-847F-E5A4B708E142.md
@@ -0,0 +1,4 @@
+# VMware tools (vmtools) RPC mode
+
+- VMware tools is installed on the template(s)
+- Credentials have been entered on the Image if using an uploaded or synced image when Cloud-init or Guest Customizations or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json b/corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
new file mode 100644
index 0000000..7aefdd4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+  "title": "Task Management",
+  "ordinal": 65,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html",
+  "topic_cluster": {
+    "clustering_title": "Task Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md b/corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
new file mode 100644
index 0000000..ef0cd34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
@@ -0,0 +1 @@
+# Task Management
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json b/corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
new file mode 100644
index 0000000..a585309
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+  "title": "PXE Boot Settings",
+  "ordinal": 281,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-B94BC2CB-8504-41C6-8848-512529EEE941.html",
+  "topic_cluster": {
+    "clustering_title": "PXE Boot Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+        "clustering_title": "PXE Boot Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-B94BC2CB-8504-41C6-8848-512529EEE941",
+        "clustering_title": "PXE Boot Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md b/corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
new file mode 100644
index 0000000..c3e2cfa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-B94BC2CB-8504-41C6-8848-512529EEE941.md
@@ -0,0 +1,4 @@
+# PXE Boot Settings
+
+Default Root Password
+:   Enter the default password to be set for Root during PXE Boots.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json b/corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
new file mode 100644
index 0000000..2a3d087
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+  "title": "Common Options",
+  "ordinal": 58,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html",
+  "topic_cluster": {
+    "clustering_title": "Common Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md b/corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
new file mode 100644
index 0000000..1918c85
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
@@ -0,0 +1,3 @@
+# Common Options
+
+When creating a Task, the required and optional inputs will vary significantly by the Task type. However, there are options which are common to Tasks of all types.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json b/corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
new file mode 100644
index 0000000..67f512f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+  "title": "Feature Access Permissions",
+  "ordinal": 250,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.html",
+  "topic_cluster": {
+    "clustering_title": "Feature Access Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+        "clustering_title": "Feature Access Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F",
+        "clustering_title": "Feature Access Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md b/corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
new file mode 100644
index 0000000..8151805
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BB3046E2-F2D4-4B45-8B85-E4982E255B2F.md
@@ -0,0 +1,256 @@
+# Feature Access Permissions
+
+Feature Access settings control permissions for sections and objects in VM Essentials. Permission options include:
+
+None
+:   Hidden or inaccessible for user
+
+Read
+:   User can view but cannot edit or create
+
+Full
+:   User has full access
+
+User
+:   User can access Objects they have created or own
+
+Group
+:   User can access Objects assigned to or shared with Groups the User has access to
+
+Remote Console: Provisioned
+:   Remote Console tab will only appear after instance is successfully provisioned.
+
+Remote Console: Auto Login
+:   RDP and SSH only, controls if user is auto-logged in to Remote Console or presented with login prompt.
+
+Role Mappings
+:   Gives User Access to Role Mappings config in `/admin/roles` for configuring Identity Source Role Mappings without providing Access to other Identity Source configuration settings.
+
+## Admin Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Admin: Ansible | None, Full | Allows or disallows the ability to edit existing Ansible integrations | Ansible integrations are shown on the Integrations list page (Administration > Integrations). Users with access may view and edit them here. | This permission is recommended for those responsible for administering VM Essentials, including creating integrations with third‐party technologies, specifically Ansible |  |
+| Admin: Appliance Settings | None, Full | Allows or disallows access to the Appliance and License tabs in Administration > Settings | The Appliance tab in Administration > Settings is where VM Essentials administrators would configure the appliance URL, Tenant and User management, email, proxy, and currency settings. Additionally, defining which Clouds are available for integration within VM Essentials is done on this page. On the License tab information about the current VM Essentials license may be viewed and a new license may be applied when needed. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant. Those responsible for configuring currency, email, and proxy settings for Cloud API access will need this permission. | This permission is recommended to be set to None on the Tenant Role to restrict this access for all Subtenant Users. |
+| Admin: Backup Settings | None, Full | Allows or disallows access to Administration > Settings > Backups. Master Tenant administrators have additional settings for appliance backups and defaults on this page. | The Backup Settings page is where users define the default VM Essentials backup bucket, backup schedule, and retention count. Additionally, if given to a Master Tenant user they will have the ability to enable scheduled backups, create backups, and backup appliance. | This permission is recommended for those responsible for enabling backups and setting default backup buckets within VM Essentials. |  |
+| Admin: Clients | None, Full | Allows or disallows access to the Clients tab in global settings (Administration > Settings) | The Clients settings section is where API clients are created and edited. Default clients may have their validity and refresh periods edited but cannot be deleted. User‐created API clients may be edited or deleted | This permission is recommended for those responsible for administering API access. |  |
+| Admin: Distributed Workers | None, Full | Allows or disallows access to Administration > Integrations > Distributed Workers Tab |  |  |  |
+| Admin: Environment Settings | None, Full | Allows or disallows access to the Environments tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define the visibility of the environment to either private or public. When given to a Subtenant user the environments are only visible to the subtenant (private). | The Environments tab is where named environments such as development or production are created and given a description as well as a code for use within the API. A display order and visibility is also set. | This permission is recommended for those responsible for defining environments that will be available to select at provision time whether they are the Master Tenant or Subtenant users. |  |
+| Admin: Export/Import | None, Full | Allows access to the Export/Import functionality which is part of the Code Repositories section of VM Essentials UI (Provisioning > Code) | Export/Import tools allow users to configure integrated Git repositories as either export or import targets (or both) and execute exports or imports | This permission is recommended for administrators as it allows wholesale export of VM Essentials constructs (Tasks, Library Items, and more) as code into Git repositories as well as import of new items from repositories into the appliance |  |
+| Admin: Guidance Settings | None, Full | Allows or disallows access to the Guidance tab in Administration > Settings | The Guidance tab controls global thresholds for VM Essentials guidance recommendations | This permission is recommended for those responsible for cost and resource management |  |
+| Admin: Health | None, Read | Determines access to the Administration > Health page, including the VM Essentials Health and VM Essentials Logs tabs. | The Health pages provide an overview of VM Essentials health, notifications from integrations, and the current VM Essentials‐ui log. | This permission is recommended for those responsible for administering and troubleshooting VM Essentials. | This permission is recommended to be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Identity Source | None, Role Mappings, Full | Allows or disallows access to create, edit, or delete integrated Identity Sources associated with subtenants. The “Role Mappings” option allows the user to edit role mappings without seeing higher level details about the integration itself (such as server IP addresses and admin usernames). | The Identity Sources page associated with the selected Tenant allows for creating, editing, and removing of identity sources in addition to configuring role mapping between VM Essentials and the identity provider. | Full permission is recommended for those responsible for integrating VM Essentials with Identity Providers. Role Mapping permission is recommended for those responsible for Role Based Access Control (RBAC). | This permission is recommended to be set to None for any subtenant user roles via use of a Tenant Role unless they manage their own RBAC. |
+| Admin: Integrations | None, Read, Full | This allows or disallows full or read access to Administration > Integrations. | The Administration Integrations tab is where many new or existing integration types can be configured. These include Chef, Puppet, Ansible, Ansible Tower, vRealize Orchestrator, Microsoft DNS, PowerDNS, Route 53, Git, GitHub, Docker, Jenkins, ServiceNow, Cherwell, Remedy, and ACI. | This permission is recommended for those responsible for the integration between VM Essentials and integrated technologies. |  |
+| Admin: License Settings | None, Full | Allows or disallows access to the Licenses tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define specific subtenants in which the licenses may be used. | The Licenses tab is where software licenses may be added for tracking in VM Essentials. VM Essentials may then be configured to apply these licenses on provision. Currently, only Windows license types are available. | This permission is recommended for those responsible for managing Windows licenses. |  |
+| Admin: Log Settings | None, Full | Allows or disallows access to the Administration > Settings > Logs. | The Logs page is where logs are enabled. Syslog forwarding rules are also configured here. | This permission is recommended for those responsible for configuring VM Essentials log settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access to Subtenant Users. |
+| Admin: Message of the day | None, Full | Allows or disallows access to create and edit Message of the Day policies in Administration > Policies | The Policies page is where policies are defined. When creating a policy, users can select “Message of the Day” from the TYPE dropdown with this permission set to Full. | This permission is recommended for those responsible for publishing the Message of the Day. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Monitoring Settings | None, Full | Allows or disallows access to Administration > Settings > Monitoring | The monitoring settings page is where VM Essentials monitoring and monitoring integrations are configured. Monitoring checks can be turned on or off, and availability time frame, check interval period, and reported availability precision are also configured on this page. | This permission is recommended for those responsible for configuring VM Essentials monitoring settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Packages | None, Full | Allows or disallows access to the Packages tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom library packages (mpg) are added. | This permission is recommended for those responsible for managing the Library. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Plugins | None, Full | Allows or disallows access to the Plugins tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom plugins are added to extend VM Essentials functionality. | This permission is recommended for those responsible for extending VM Essentials functionality through custom plugins. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Policies | None, Read, Full | This setting determines the level of access to Administration > Policies. When given to a Master Tenant user the ability to define Global policies and associate them with one or many Subtenants is granted. When given to a Subtenant user, a global policy applies only to their subtenant. | The Policies page is where policies are defined. On create, the type of policy is selected, a name, description, and scope are defined. | This permission is recommended for those responsible for configuring and managing policies either at the Master Tenant or Subtenant. |  |
+| Admin: Profiles | none,read,full | Allows or disallows access to Profiles (Clouds) | Profiles are where Terraform, Key/Value profiles are created and managed. | This permission is recommended for those responsible for managing secrets and other metadata that needs to be accessed by provisioning and automation processes. |  |
+| Admin: Provisioning Settings | None, Full | Allows or disallows access to the Settings tab of the Administration > Settings > Provisioning page. | The Settings tab is where global provisioning settings are configured. For Master Tenant users, these include allowing Cloud selection, allowing host selection, requiring environment selection, showing pricing, hiding datastore stats on selection, cross‐Tenant naming policies, and reusing naming sequence numbers. For both Master Tenant and Subtenant users, defining the deploy archive store, cloud‐init setting, the PXE boot root password, and default App Blueprint types are available. | This permission is recommended to only be assigned to roles utilized within the Master Tenant. |  |
+| Admin: Roles | None, Read, Full | This setting determines access to the Administration > Roles page. When given to a Subtenant user, the ability to create user roles is granted. When given to a Master Tenant user, the ability to create and manage Tenant and Multi‐Tenant Users roles is also granted. | The Roles page is where roles are defined. On create, a name and description are defined. Once created, the Role is accessed and feature access, Group access, Instance Type access and Blueprint access may be configured. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC) either globally or within their Subtenant. |  |
+| Admin: Service Plans | None, Read, Full | This setting determines access to Administration > Plans & Pricing. When given to a Subtenant user, access to the Plans tab is granted. When given to a user in the Master Tenant, the Price Sets and Prices tabs are also available. | The Plans tab is where service plans are defined. On create, a name and code (for API) are defined, display order, provisioning type, storage, memory, core count and the price may be configured. Additionally, the actions menu will allow group access to be scoped. | This permission is recommended for those responsible for defining and managing pricing and applying plans. |  |
+| Admin: Tenant | None, Read, Full | This setting determines access to the Administration > Tenants page. With this permission, local users may be created or deleted within each Tenant. Critical Note: Granting this permission to Subtenant users will expose all Tenants and Tenant users to the Subtenant. | The Tenant page is where all Tenants may be viewed, edited, created, or even deleted. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant who are responsible for the creation, configuration, and/or deletion of Subtenants. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Tenant ‐ Impersonate Users | None, Full | This setting allows or disallows access to impersonate users. This selection is located on the Administration > Users page in the Actions menu. When set to Full, Impersonate selection is available. | This permission allows for users in the Master Tenant to impersonate users of the Master Tenant and Subtenants. | This permission is recommended to be assigned only to Roles utilized within the Master Tenant who are responsible for configuring RBAC or for supporting users. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Users | None, Read, Full | This setting determines access to the Administration > Users page (both Users and User Groups tabs). User Roles can also be set or edited when creating or editing a User on this page. Note: A Master Tenant user with the Admin: Tenants (Full) permission may also access and perform user management from the associated Tenant page. | The User tab is where all users may be viewed, edited, created, or even deleted. The User Groups tab is where User Groups may be viewed, edited, created, or even deleted. Within VM Essentials, a User Group may be selected during provisioning in order to add each group member’s credentials to an Instance. When creating a User Group a name, description, server group (in Linux, name of the group to assign members), sudo access toggle, and a list of users are defined. | This permission is recommended for those responsible for managing users and RBAC. |  |
+| Admin: Whitelabel Settings | None, Full | Allows or disallows access to the Whitelabel tab in Administration > Settings. | The Whitelabel tab is where custom Tenant logos, colors, and security banners may be configured. | This permission is recommended for those responsible for branding tenants, whether they are Master Tenant users or individual Subtenant users. |  |
+
+## API Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| API: Billing | None, Read, Full | Allows or disallows access to invoices and projects via VM Essentials API/CLI. | The invoices API/CLI is used to generate bills and gather highly‐granular costing data for supported Clouds. Read access allows list and get functions and Full allows access to post (refresh). | This permission is recommended for those responsible for generating invoices or projects. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| API: Execution Request | None, Full | Allows or disallows access to an API endpoint. | This endpoint allows users to execute scripts on Instances, containers, or hosts and then polls for a response. | This permission is recommended for those responsible for arbitrary API script execution. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Backups Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Backups | None, View, Read, User, Full | Determines access to the Backups secton of VM Essentials UI, including the Summary, Jobs, Backups, and History subpages. The “User” permission allows access only to backup objects the user owns. | The Summary subpage allows the user to see the number of configured backups, the success rate, recent failures, and the size of the backups, as well as, the upcoming and in‐progress backups. The Jobs subpage is where backup jobs may be created, cloned, edited or deleted. On create, a name, code (for use within the API), retention count, and schedule are selected (Note: Selectable schedules are defined Execution Schedules which are created in the Library > Automation). On the backups subpage, a list of configured backups is provided and new backups may be created or on‐demand backups may be executed. On create, the place where the target exists is selected (Instance, Host, or Provider), the source is selected and a name is defined as well as the selected execution schedule. On the History subpage both the backups and restores tabs are available. Names, statuses, start times, durations and size may be viewed. | This permission is recommended for those responsible for performing the backup and restoration of workloads. |  |
+| Backups: Integrations | None, Read, Full | Determines access to the Backups > Integrations page. | From this page, backup integrations may be created, edited, or deleted. The page also provides the status of existing integrations. On create the integration product is selected and all associated connection and authentication information must be provided. Additionally, visibility is set to either public or private. Integrations available include Avamar, Commvault, Rubrik, Veeam, and Zerto. | This permission is recommended for those responsible for the integration between VM Essentials and backup technologies. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Catalog Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Catalog (Formerly Service Catalog: Catalog) | None, Full | Determines access to Provisioning > Catalog and Catalog in the Service Catalog Persona view | The Catalog page displays the complete list of Catalog Items that can be ordered from the Service Catalog | This permission is recommended for users who will order items from the Service Catalog |  |
+| Catalog: Dashboard (Formerly Service Catalog: Dashboard) | None, Read | Determines access to and Dashboard in Service Catalog Persona view | The Catalog Dashboard contains featured Catalog Items, recently‐ordered Catalog items and Inventory items. The Catalog Dashboard is the default landing page for the Service Catalog Persona view | This permission is recommended for users who will use the Service Catalog |  |
+| Catalog: Inventory (Formerly Service Catalog: Inventory) | None, Full | Determines access to and Dashboard in Service Catalog Persona view | The Inventory is the complete list of user‐owned items provisioned from the Service Catalog | This permission is recommended for users who will use the Service Catalog and need to be able to view details on the items they’ve provisioned from the Catalog |  |
+
+## Infrastructure Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Infrastructure: Boot | None, Read, Full | Determines access to the Integrations > Bootpage, including the Mapping, Boot Menus, Answer Files, Images, and Discovered MAC Addresses tabs. | VM Essentials includes a PXE Server to provide for rapid bare metal provisioning. The Boot page is where users may add, edit, or delete answer files, as well as, manage their own images or use existing ones. Boot menus and mappings are also managed here and discovered MAC addresses are displayed. | This permission is recommend for those responsible for bare metal provisioning. |  |
+| Infrastructure: Certificates | None, Read, Full | Determines access to the SSL Certificates tab on the Infrastructure > Keys& Certs page. | The SSL Certificates page is where certificates may be uploaded and managed. These certificates may then be used within VM Essentials when orchestrating load balancers. | This permission is recommended for personnel who will be orchestrating and provisioning load balancers. |  |
+| Infrastructure: Clouds | None, Read, Group, Full | Determines access to the Infrastructure > Clouds page. The “Group” permission limits the Cloud list page (Infrastructure > Clouds) to show only Clouds in their assigned Groups. | The Cloud page is where new Clouds are integrated with VM Essentials and existing Cloud integrations are managed. This includes creating a code for use within the API, the location, visibility, tenant, whether or not it should be enabled, and if VMs should be automatically powered on. Additionally, Clouds may be integrated from the Clouds tab of a Group detail page. | This permission is recommended for those responsible for configuring RBAC as well as those responsible for VM Essentials Cloud Integrations. |  |
+| Infrastructure: Clusters | None, Read, Group, Full | Determines access to the Infrastructure > Clusters page. | The Clusters page allows you to create and manage Kubernetes, Docker, and KVM Clusters, as well as Cloud‐specific Kubernetes services such as EKS. | This permission is recommend for those creating and managing containers or container services. |  |
+| Infrastructure: Compute | None, Read, Full | Determines access to the Infrastructure > Hostspage, including the Hosts, Virtual Machines, and Bare Metal tabs. | The Hosts page provides for viewing and managing hosts, virtual machines, and bare metal hosts. On the bare metal hosts page, hosts may come from PXE boot or may be manually added. On the Hosts page hypervisors and Docker hosts are displayed. The Virtual Machines page lists all VMs. On all three pages actions may be performed against machines. Additionally, views may be refined by altering the columns displayed and CSV/JSON exporting of lists is available. | This permission is recommend for those whom need to take action on machines and those responsible for bare metal provisioning. |  |
+| Infrastructure: Credentials | None, Read, Full | Determines access to the Credentials tab in Infrastructure > Trust | The credentials tab allows you to create and manage credential sets stored internally and in external Cypher server integrations | This permission is recommended for those responsible for maintaining credentials |  |
+| Infrastructure: Groups | None, Read, Full | Determines access to the Infrastructure > Groups page. | The Groups page is where VM Essentials Groups are created and given a code for use within the API. Additionally, the DNS service, CMDB, service registry, and config management may be selected. Existing Clouds/Hosts or new Clouds/Hosts are added to the Group and virtual or bare metal machines may be viewed. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC). |  |
+| Infrastructure: Keypairs | None, Read, Full | Determines access to the Key Pairs tab on the Infrastructure > Keys& Certs page. | The Keypairs page allows for ease in accessing instances via SSH. On create a name, public key, private key, and passphrase are entered. | This permission is recommended for those whom utilize VM Essentials deployment and management of Linux Instances. |  |
+| Infrastructure: Kubernetes Control | None, Full | Determines access to the Control tab on Kubernetes Cluster detail pages (Infrastructure > Clusters > Selected Kubernetes Cluster > ControlTab) | Run `kubectl` commands, apply templates, and run workloads on the Kubernetes Cluster | This permission is recommended for Kubernetes Cluster administrators |  |
+| Infrastructure: Load Balancers | None, Read, Full | Determines access to the Infrastructure > Load Balancers page, including both the Load Balancers and Virtual Servers tabs. | The Load Balancers page is where new load balancer integrations may be configured. Additionally, existing integrations may be managed. The Virtual Servers page is where virtual servers are managed to include policies, pools, profiles, monitors, nodes, and rule scripts may be managed. | This permission is recommended for those responsible for integrating VM Essentials with load balancers as well as those responsible for managing virtual servers. |  |
+| Infrastructure: Move Servers | None, Full | Determines access to the “Change Cloud” action on server detail pages (Infrastructure > Compute > Virtual Machines tab > SelectedVM > Actions > Change Cloud) | Change Cloud allows server records to be migrated from one Cloud to another. Note that this is not a migration tool but simply allows for upkeep of records in VM Essentials. | This permission is recommended for appliance administrators. See other sections of VM Essentials documentation for more information on the use of this feature. |  |
+| Infrastructure: Networks | None, Read, Group, Full | Determines access to the Infrastructure > Networks page, including the Networks, network groups, and integrations tabs. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Networks page is where networks are configured for DHCP or static IP assignment and existing networks are displayed. The Network Groups page is where networks are grouped to allow round robin provisioning among the group. The Integrations page is where IPAM, DNS, security, service registry, and virtual network tools are integrated. These include Cisco ACI, VMware NSX T and V, Infoblox, Bluecat, phpIPAM, SolarWinds, Stealth, Microsoft DNS, PowerDNS, and Route 53. | This permission is recommended for those responsible for integration with network technologies and the configuration and management of networks to be used during provisioning. |  |
+| Infrastructure: Policies | None, Read, Full | Determines access to the Policies tabs on the Group and Cloud detail pages (Infrastructure > Groups > selected Group OR Infrastructure > Cloud > selected Cloud). | Policies can be created from this tab which are scoped to the Cloud or Group being viewed. | This permission is recommended for users who will need to set quotas which pertain specifically to Groups or Clouds the user has access to. |  |
+| Infrastructure: Security Groups | None, Read, Full | Determines access to the Security Groups tab on the Infrastructure > Networks page. | The Security Groups page is where Security Groups (aka virtual firewalls) are defined. | This permission is recommended for those responsible for firewall configuration and management. |  |
+| Infrastructure: State | None, Read, Full | Determines access to the power state toggle on the Infrastructure > Hostspage. | This toggle moves Hosts between a started and stopped state. | This permission is recommended for those responsible for managing Hosts. |  |
+| Infrastructure: Storage | None, Read, Full | Determines access to the Infrastructure > Storage page, including the Buckets, File Shares, Volumes, Data Stores, and Servers tabs. | The Servers page is where storage integrations are configured. Integrations available include 3Par, AWS S3, Dell EMC ECS and Isilon, Huawei or Open Telekom OBS and Huawei, Open Telekom, OpenStack SFS. The Volumes page is where storage volumes may be created or viewed. The File Shares page is where File Shares of types CIFS, Dell EMC ECS or Isilon, local storage, and NFSv3 may be configured. The Buckets page is where storage buckets of type AWS S3, Alibaba, Azure, Open Telekom OBS, OpenStack Swift, Racspace CDN may be created. Storage buckets are used for Backup, Archives, and Virtual Images. The Data Store page is where permissions to data stores may be managed and new data stores are added. | This permission is recommended for those responsible for storage integrations and configurations. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+| Infrastructure: Storage Browser | None, Read, Full | Determines file browsing access to buckets and file shares on the Buckets and File Shares tabs of the Infrastructure > Storage page. | The Storage Browser permission allows users who also have appropriate Infrastructure: Storage permission to browse, add files and folders, download, and delete from the buckets and file shares. | This permission is recommended for those who need to browse storage. |  |
+| Infrastructure: Trust Integrations | None, Read, Full | Determines access to the Integrations tab of the Infrastructure > Keys& Certs page. | The Integrations tab is where new trust integrations can be configured. | This permission is recommended for those responsible for the integration between VM Essentials and trust providers. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+
+## Library Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Library: App Blueprints (Formerly Provisioning: Blueprints) | None, Read, Full | Determines access to the Library > Blueprints > App Blueprints page. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of VM Essentials is available. | This permission is recommended for those responsible for defining VM Essentials‐type Blueprints. |  |
+| Library: Blueprints ‐ ARM (Formerly Provisioning: Blueprints ‐ ARM) | None, Provision, Full | Determines access to ARM‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from ARM Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of ARM is available. | This permission is recommended for those responsible for defining ARM blueprints. |  |
+| Library: Blueprints ‐ CloudFormation (Formerly Provisioning: Blueprints ‐ CloudFormation) | None, Provision, Full | Determines access to CloudFormation‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from CloudFormation Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of CloudFormation is available. | This permission is recommended for those responsible for defining CloudFormation blueprints. |  |
+| Library: Blueprints ‐ Helm (Formerly Provisioning: Blueprints ‐ Helm) | None, Provision, Full | Determines access to Helm‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Helm Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Helm is available. | This permission is recommended for those responsible for defining Helm blueprints. |  |
+| Library: Blueprints ‐ Kubernetes (Formerly Provisioning: Blueprints ‐ Kubernetes) | None, Provision, Full | Determines access to Kubernetes‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Kubernetes Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Kubernetes is available. | This permission is recommended for those responsible for defining Kubernetes blueprints. |  |
+| Library: Blueprint ‐ Terraform (Formerly Provisioning: Blueprints ‐ Terraform) | None, Provision, Full | Determines access to Terraform‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Terraform Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Terraform is available. | This permission is recommended for those responsible for defining Terraform blueprints. |  |
+| Library: Catalog Items (Formerly Tools: Self Service) | None, Read, Full | Determines access to Library > Blueprints > Catalog Items | Library > Blueprints > Catalog Items allows administrators to configure Catalog Items for the Library Catalog and Self Service Persona users | This permission is recommended for those responsible for creating and managing Library Catalog Items. |  |
+| Library: Instance Types (Formerly Provisioning: Library) | None, Read, Full | Determines access to the Library > Blueprints > Instance Types | Library > Blueprints > Instance Types is where Instance Types are created and maintained. | This permission is recommended for those responsible for managing the Instance Types. |  |
+| Library: Integrations (Formerly Provisioning: Automation Integrations) | None, Read, Full | Determines access to Library > Integrations. | Library > Integrationsis where Library Automation created and maintained.. These include Chef, Puppet, Ansible, Ansible Tower and vRealize Orchestrator. | This permission is recommended for those responsible for the integration between VM Essentials and integrated automation technologies. |  |
+| Library: Packages | None, Read, Full | Determines access to Library > Templates > Cluster Packages. | Library > Templates > Cluster Packages is where Cluster Packages are created or edited. Cluster Packages are associated with Cluster Layouts | This permission is recommended for those responsible for Cluster Layout templating |  |
+| Library: Options | None, Read, Full | Determines access to Library > Options ‐ Inputs (Option Types) and Option Lists. |  | This permission is recommended for those responsible for creating and managing Library Inputs (Option Types) and Option Lists. |  |
+| Library: Scheduling ‐ Execute (Formerly Provisioning: Scheduling ‐ Execute) | None, Read, Full | Determines access to Library > Automation > Execute Scheduling. | The Execute Scheduling is where time schedules for Jobs, including Task, Workflow, and Backup Jobs are created and managed. | This permission is recommended for those responsible to create and manage schedules to be selected when scheduling jobs. |  |
+| Library: Scheduling ‐ Power (Formerly Provisioning: Scheduling ‐ Power) | None, Read, Full | Determines access to Library > Automation > Power Scheduling. | Power Scheduling is where startup and shutdown times are created, these schedules can be applied via policy or manaully. | This permission is recommended for those responsible to create and manage power schedules. |  |
+| Library: Tasks (Formerly Provisioning: Tasks) | None, Read, Full | Determines access to Library > Automation > Tasks and Library > Automation > Workflows. | Library > Automation > Tasks is where Tasks are created and managed. Library > Automation > Workflows is where Workflows are created and managed. Workflows are used to execute one or many tasks during specified phases. | This permission is recommended for those responsible for creating provisioning and operational scripts. |  |
+| Library: Tasks ‐ Script Engines (Formerly Provisioning: Tasks ‐ Script Engines) | None, Full | Determines access to **Execute Target** of **Local** for Tasks. | This permission limits Tasks from being able to run on the Morpheus appliance(s). Additionally, Task Types that only contain the **Execute Target** of **Local** will be removed, such as: Groovy, Javascript, and Python Task Types. | This permission is recommended for those responsible for Tasks that may need to execute on the appliance(s). |  |
+| Library: Templates | None, Read, Full | Determines access to Library > Templates | Library > Templates is where Spec Templates, File Templates, Script Templates and Security Packages are created and managed. | This permission is recommended for those responsible for creating and managing Spec Templates, File Templates, Script Templates and Security Packages. |  |
+| Library: Thresholds (Formerly Provisioning: Thresholds) | None, Read, Full | Determines access to Library > Automation > Scale Thresholds. | Scale Thresholds is where preconfigured settings for auto‐scaling Instances are configured. When adding auto‐scaling to an Instance, existing Scale Thresholds can be selected to define auto‐scaling rules. | This permission is recommended for those responsible for defining auto‐scaling for Instances. | This permission is recommended to be set to None or Read on the Tenant Role to restrict access for Subtenant users. |
+| Library: Virtual Images (Formerly Provisioning: Virtual Images) | None, Read, Full | Determines access to the Library > Virtual Images page. | Library > Virtual Images is where user and system Virtual Images are managed. | This permission is recommended for those who are responsible for image management. |  |
+
+## Lifecycle Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Environment Variables | None, User, Read, Full | Allows access to the Environments tab of the Instance detail page | Allows Instance environment variables to be edited. If set to “User” level only environment variables of Instances owned by the currently logged in user may be edited. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Extend Expirations | None, User, Full | Determines if the user can extend an expiration or shutdown Policy | Allows the user to extend automated shutdown or expiration policies set against any workload (“full” permission) or against the user’s own workloads (“user” permission) | This permission is recommended for administrators or those who need to be able to extend Policies set against their own workloads (“user” level permission) |  |
+| Power Control | None, User, Full | Allows access to power state controls for Instances and servers, including stopping, starting, restarting and suspending. | Allows the user to change the current power state of Instances and servers | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure | None, User, Full | Allows general access to Instance and server reconfigure (resize) feature. See additional reconfigure permissions below for more granular control over specific reconfigure functionality. | Allows general access to reconfigure features for Instances and servers. “User” level permission allows only Instances and servers owned by the currently logged in user to be reconfigured. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Change Plan | None, User, Full | Allows the user to change the Instance service plan | When reconfiguring, the user may change the service plan associated with the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their plans changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Add | None, User, Full | Allows the user to add disks to an Instance or server during reconfigure. | When reconfiguring, the user may add disks to the selected Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Change Type | None, User, Full | Allows the user to change the datastore or volume type during reconfigure. | When reconfiguring, the user may update datastore or volume types. “User” level permission allows only Instances owned by the currently logged in user to have their disk types changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Modify | None, User, Full | Allows the user to modify an attached disk during reconfigure. | When reconfiguring, the user may modify disks attached to the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Remove | None, User, Full | Allows the user to remove disks or volumes during reconfigure. | When reconfiguring, the user may remove disks attached to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks removed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Add | None, User, Full | Allows the user to add a network adapter during reconfigure. | When reconfiguring, the user may add a network interface to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces added. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Modify | None, User, Full | Allows the user to edit network adapters during reconfigure. | When reconfiguring, the user may edit network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces modified. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Remove | None, User, Full | Allows the user to remove network adapters during reconfigure. | When reconfiguring, the user may remove network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces removed. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Retry/Cancel | None, Full | Determines access to retry and cancel buttons for Tasks (for example, in the History tab of an Instance detail page) | Retry and cancel functionality allows failed automation Tasks to be retried or stuck Tasks to be stopped from various places within VM Essentials UI (such as in the History tab of an Instance detail page) |  |  |
+
+## Monitoring Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Monitoring | None, Read, User, Full | Determines level of access to the Monitoring section of VM Essentials UI, including the Status, Apps, Checks, Groups, Incidents, Contacts, and Alert Rules subpages. The “User” permission will allow access only to objects the user owns. | The Checks page is where automatically‐created checks are customized or new checks are created. The Groups and Apps pages are where checks may be grouped. The Incidents page is where incidents are created upon Check failure. The Contacts page is where contacts may be added for notifications. The Alert Rules page is where notification are configured. | This permission is recommended for those responsible for monitoring applications, incidents, or configuring notifications. |  |
+| Monitoring: Logs (Formerly Logs) | None, Read, User, Full | Determines level of access to the Logs section of VM Essentials UI. The “User” permission will allow access only to objects the user owns. | Monitoring > Logs is where Instance and Server logs may be viewed (also must be enabled in order to view Appliance logs from Administration > Health > Morpheus Logs Logs when health permission is also enabled). | This permission is recommended for those who should have access to Instance and Server logs. | Setting permission to Full on the Tenant Role will give Subtenant users full access to all logs appliance‐wide, including to workloads living in other Tenants, for any Subtenant users who also have Full permission on their User Role. It’s recommended that you set this permission to User on the Tenant Role so that Subtenant users are not able to see logs for workloads other than their own. |
+
+## Networks Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Networks: DHCP Relays | None, Read, Full | Determines access to the DHCP Relays in applicable network integrations | Allows DHCP Relays to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: DHCP Servers | None, Read, Full | Determines access to the DHCP Servers in applicable network integrations | Allows DHCP Servers to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: Domains | None, Read, Group, Full | Determines access to the Domains tab on the Infrastructure > Network page. Domains may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into Domains scoped to Groups they can access. | The Domains page is where network domains are managed. Domains are used for setting FQDNs, joining Windows Instances to domains, and creating A‐Records with DNS integrations. On create the domain controller and credentials for domain join must be provided. | This permission is recommended for those responsible for VM Essentials DNS and domain‐join integrations. |  |
+| Networks: Firewalls | None, Read, Manage Rules, Full | Determines access to the Firewall tab on applicable network integrations detail pages. When the “Manage Rules” permission is given, users have read‐only access to firewall groups and the ability to create and manage firewall rules on those groups | The Firewall tab is where network firewall groups and rules are viewed, created and managed | This permission is recommended for those tasked with network security management |  |
+| Networks: Floating IPs | None, Read, Full | Determines access to the Floating IPs tab on the Network list page (Infrastructure > Network) | The Floating IPs tab is where Floating IPs from supported Clouds are listed once synced into VM Essentials Users may also release unattached Floating IPs from this page and link through to any workloads which have Floating IPs attached | This permission is recommended for those tasked with network management |  |
+| Networks: IP Pools | None, Read, Group, Full | Determines access to the IP Pools tab on the Network list page (Infrastructure > Network). IP Pools may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into IP Pools scoped to Groups they can access. | The IP Pools tab is where IP pools from various networks are displayed. Detail pages for IP pools can also be accessed here | This permission is recommended for those tasked with IP address management |  |
+| Networks: Integration | None, Read, Full | Determines access to the Integrations tab on the Network list page (Infrastructure > Network) | The integrations tab is where network integrations can be viewed, added and managed. Additionally, the detail pages for network integrations are accessed here | This permission is recommended for those tasked with handling network integrations and their use within VM Essentials |  |
+| Networks: Proxies | None, Read, Full | Determines access to the Proxies tab on the Infrastructure > Networks page. | The Infrastructure Networks Proxies page is where Proxy configurations are stored, which are available for use by the provisioning engines. | This permission is recommended for those responsible for configuring proxies to be used when provisioning. |  |
+| Networks: Router Firewalls | None, Read, Full | Determines access to Firewall tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Firewall tab is where firewall rules are viewed, created, and managed | This permission is recommended for those responsible for managing firewall rules |  |
+| Networks: Router Interfaces | None, Read, Full | Determines access to Interfaces tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Interface tab is where router interfaces can be viewed, created and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router NAT | None, Read, Full | Determines access to the NAT tab on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The NAT tab is where NAT rules are viewed, created, and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router Redistribution | None, Read, Full | Determines access to Route Redistribution tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Route Redistribution tab is where redistribution rules are viewed, created, and managed | This permission is recommended for those responsible for redistribution rules |  |
+| Networks: Router Routes | None, Read, Full | Determines access to Routing tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Routing tab is where routes are viewed, created, and managed | This permission is recommended for those responsible for network route management |  |
+| Networks: Routers | None, Read, Group, Full | Determines access to the Routers tab on the Infrastructure > Networks page. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Routers page is where virtual routers are created and managed from Cloud and Network integrations. | This permission is recommended for those responsible for network management. |  |
+| Networks: Server Groups | None, Read, Full | Determines access to |  |  |  |
+| Networks: Static Routes | None, Read, Full | Determines access to the routing tab on a router detail page (/infrastructure/networks/routes) | The routers tab is where routes are created and managed | This permission is recommended for those responsible for network management |  |
+
+## Operations Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Operations: Activity | None, Read | Determines access to the Activity and History tabs on the Operations > Activity page. | The Activity page displays four types of recent activities: Provisioning, Alerts, Backups, and Permissions. | This permission is recommended for those responsible to monitor or view activities and their statuses within VM Essentials. |  |
+| Operations: Alarms | None, Read, Full | Determines access to the Alarms tab in the Activity section (Operations > Health) | The Alarms tab is where alarms are listed and acknowledgement actions can be taken against them | This permission is recommended for those responsible for monitoring |  |
+| Operations: Analytics | None, Read, Full | Determines access to the Operations > Analytics page. | The Analytics page gives administrators the ability to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. | This permission is recommended for those responsible for understanding utilization and costs. |  |
+| Operations: Approvals | None, Read, Full | Determines access to the Operations > Approvals page. | When a Provision Approval‐type Policy is enabled for a Group or Cloud, an approval request will be created on each relevant provision attempt. These approvals can be handled directly in VM Essentials or dealt with in ServiceNow with a properly‐configured integration. | This permission is recommended for those responsible for approving, denying, or canceling approval requests. |  |
+| Operations: Budgets | None, Read, Full | Determines access to the Operations > Budgetspage. | The Budgets page is where budgets are created and applied to clouds, tenants, users, or groups. | This permission is recommended for those responsible for managing budgets. |  |
+| Operations: Dashboard | None, Read | Determines access to the Operations > Dashboard page (default VM Essentials landing page). | The Dashboard page is a single pane of glass showing quick, easy‐to‐read performance and configuration information about the VM Essentials environment. | “Read” permission is recommended for all users. When set to None, Operations > Reports becomes the default landing page and attempts to go to the Dashboard will redirect users to their User Settings page. |  |
+| Operations: Guidance | None, Read, Full | Determines access to the Operations > Guidance page. | The Guidance page shows recommendations for resource and cost‐utilization optimization. | This permission is recommended for those responsible to optimize utilization and costs of Cloud‐based resources. |  |
+| Operations: Invoices | None, Read, Full | Determines access to the Invoices tab in Operations > Costing | The Invoices tab allows access to highly‐granular historical costing data | This permission is recommended for those responsible for generating invoices and analyzing spend |  |
+| Operations: Reports | None, Read, Full | Determines access to the Operations > Reports page. | The Reports page is where reports may be generated and exported into JSON or CSV format. | This permission is recommended for those responsible for account, infrastructure, provisioning, usage, and cost reports. |  |
+| Operations: Usage | None, Read, Full | Determines access to the Usage tab on the Operations > Activity page. | The Usage tab shows billing information for Instances and hosts that have pricing configured on their Service Plans. | This permissions is recommended for those responsible for cost accounting. |  |
+| Operations: Wiki | None, Read, Full | Determines access to the Operations > Wiki page. | The Wiki page allows easy UI, API and CLI access to information to be referenced or shared with others. Wiki pages encompass individual Clouds, Groups, Servers, Instances, Clusters, and other pages can be manually created. Wiki pages from resources are accessible from the Operations > Wiki page or within individual resource detail pages on their respective Wiki tabs. | This permission is recommend for those responsible for documentation and knowledge management. |  |
+
+## Projects Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Projects | None, Read, Full | Determines access to Projects through VM Essentials API | Projects are used to associate resources together and apply common tags to their invoices | This permission is recommended for those responsible for cost analysis and invoice reporting |  |
+
+## Provisioning Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Provisioning: Administrator | None, Full | When editing an Instance (Provisioning > Instances > selected Instance > EDITbutton), this permission determines access to changing the owner of an Instance. | Allows you to change the owning user of an Instance. | This permission is recommended for those responsible to ensure all instances are owned by appropriate personnel. |  |
+| Provisioning: Advanced Node Type Options | None, Full | This allows or disallows access to the “Extra Options” field of the Node Types tab on the Library page when the Node Type Technology value is set to “VMware”. | When VMware technology type is selected for a new or existing Node Type (Library > Blueprints > Node Types), the “Extra Options” field will be available in the VMware VM Options section. These allow defining advanced vmx‐file parameters during provisioning. | This permission is recommended for those responsible for managing VMware Node Types (images). |  |
+| Provisioning: Apps | None, Read, User, Full | Determines access to the Provisioning > Apps page. The “User” permission will allow access to only object the user owns. | The Apps page allows Instances to be grouped and tiered logically into Apps. From this page, Apps can be deployed from existing Blueprints and Instances can be added to existing Apps. Security groups and environmental variables (Linux Only) may be added and edited. The App log, history, and monitoring tabs may be viewed. | This permission is recommended for those responsible for provisioning. |  |
+| Provisioning: Code Deployments | None, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Deployments page provides the ability to use git, fetch from a url, or upload a file to be utilized during the provisioning of an Instance or pushed to an existing Instance. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Code Integrations | None, Read, Full | Determines access to the Integrations tab on the Provisioning > Code page. | From this page code integrations may be created, edited, or deleted. Integrations available include Git, Github, and Jenkins. | This permission is recommended for those responsible for the integration between VM Essentials and code repositories and services. |  |
+| Provisioning: Code Repositories | None, List Files, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Code Repositories contains the repositories integrated with VM Essentials allowing users to browse repositories folders and files and view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Execute Script | None, Full | Determines access to the Run Script and Apply Template selections from the Actions menu on an Instance detail page | These selections bring up a menu allowing the user to select a script and run it against the viewed Instance or select a template to write to the Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Task | None, Full | Determines access to the Run Task selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Task and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Workflow | None, Full | Determines access to the Run Workflow selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Workflow and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Executions | None, Read, User | Determines access Provisioning > Executions. When the permission level is set to “User” only the executions owned by the current user are shown | Provisioning > Executions is where Task, Workflow, and Security Scan execution output can be viewed | This permission is recommended for those who are responsible for managing or troubleshooting Task, Workflow, and Security Scan executions. |  |
+| Provisioning: Import Image | None, Full | Determines access to the Import as Image and Clone to Image selections from the Actions menu on an Instance detail page | These selections allow users to create an image from an existing Instance or import the Instance as an image to a selected bucket | This permission is recommended for those responsible for managing the library of provisionable items |  |
+| Provisioning: Instances: Add | None, Full | Gives access to create Instances. Without this permission the user cannot directly add Instances. | The “+ ADD” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance create API actions as well | This permission is recommended for any user who needs to be able to provision Instances |  |
+| Provisioning: Instances: Clone | None, User, Full | Determines the presence of the “Clone” selection under the Actions menu on the Instance detail page and Instance clone API functionality | The “Clone” selection will not be available under the “Actions” menu on the Instance detail page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be cloned. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Delete | None, User, Full | Determines the presence of the “Delete” button on the Instance detail page, delete bulk action on the Instances list page, and Instance delete API functionality | The “Delete” button will not be available on the Instance detail page and the delete action will not be available from the Instances list page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be deleted. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Edit | None, User, Full | Gives access to the Edit Instances modal for existing Instances (and corresponding API functionality). This allows the user to edit an Instance display name, tags, or Input (custom option) values | The “EDIT” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance edit API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be edited. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Force Delete | None, Full | Determines access to the force delete option when deleting Instances | The force delete option (checkbox) will not be available when deleting Instances if this permission is not given. Force deleting allows VM Essentials to delete an Instance object even when it is unable to confirm the delete happened in the target cloud. Occasionally, this may be necessary but improper use can cause orphaned objects. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: List | None, User, Full | Controls which Instances are listed on the Instances list page (Provisioning > Instances). When set to “User”, only Instances owned by the currently logged in user will be displayed. |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Lock/Unlock | None, User, Full | Gives access to the lock/unlock actions on Instance detail pages (and corresponding API functionality). This allows the user to lock or unlock Instances which reduces the chances of accidental removal of important workloads. | The Lock/Unlock selections will not be visible in the Actions menu on the Instances List Page if permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be locked or unlocked. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Remove From Control | None, User, Full | Gives access to deleting an Instance in VM Essentials only. The instance remains in the target cloud. This may only be done for brownfield workloads which were converted to managed VM Essentials Instances |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Scale | None, User, Full | Gives access to the scale tab on Instance detail pages which allow configuration of automated scaling thresholds (and corresponding API functionality). This allows the user to control scaling thresholds and add/remove nodes from an Instance. | The Scale tab on the Instance detail pages will not be visible and the user will not be able to add/remove nodes from Instances if the permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be scaled. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Settings | None, User, Read, Full | Gives access to configuration changes if the Instance supports dynamic settings templates |  |  |  |
+| Provisioning: Job Executions | None, Read | Determines access to the Job Executions tab on the Provisioning > Jobs page. | The Job Executions page contains execution history of completed jobs, including any process outputs and error messages. | This permission is recommended for those who are responsible for managing or troubleshooting jobs. |  |
+| Provisioning: Jobs | None, Read, Full | Determines access to the Jobs tab on the Provisioning > Jobs page. | The Jobs page is where jobs are scheduled for the execution of automation Tasks and Workflows against Instances or servers. | This permission is recommended for those responsible to schedule the exectution of Tasks or Workflows. |  |
+| Provisioning: Remote Console | None, User, Full | Determines access to the console on a Host detail page (Infrastructure > Hosts > selected Host, VM, or Bare Metal resource > Consoletab). The “User” permission gives access to the console only for resources the logged in user owns. | Remote console access for Instances, hosts, virtual machines, and bare metal. | This permission is recommended for those who need console access for provisioned Cloud resources. |  |
+| Provisioning: Remote Console Auto Login | No, Yes | This allows or disallows the ability to automatically log into the remote console. | VM Essentials will automatically log into the machine using the credentials defined on the VM or Host. The credentials are defined either from the virtual image used, added via cloud‐init or VMware Tools using the global cloud‐init settings (Administration > Settings > Provisioning), or the Linux or Windows settings defined in User Settings. | This permission is recommended when an organization utilizes VM Essentials to create user accounts on provisioned or managed machines, as well as, allow remote console access. |  |
+| Provisioning: Service Mesh | None, Read, User, Full | Determines access to the Provisioning > ServiceMesh page, including the Services and DNS tabs. The “User” permission will allow access only to objects the user owns. | The Service Mesh page displays container services and DNS information. A service mesh ensures fast and reliable communication between containerized application services. | This permission is recommended for those responsible for container management. |  |
+| Provisioning: State | None, Read, Full | Determines access to the State tab for a Terraform Instance or App | The State tab is where [Terraform state management](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-app-state-management) is handled for Terraform Instances or Apps | This permission is recommended for those responsible for any Terraform‐based workloads |  |
+
+## Security Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Security: Scanning | None, Read, Full | Determines access to the Security Packages tab on the Jobs list page (Provisioning > Jobs), Security Scanning type Jobs, and Security Subtab inside the Software tab on a server detail page where the results of security scans are viewed | Allows access to view, create, and run security scans on existing systems, as well as view the results of previously‐run scans | This permission is recommended for those responsible for security compliance of existing systems |  |
+
+## Snapshots Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Snapshots | None, Read, Full | Determines access to the “Create Snapshot” function in the Actions menu on an Instance detail page (Provisoning > Instances > selected Instance). | If utilizing a VMware Cloud, the ability to create snapshots is available on the Instance detail page (Provisoning > Instances > selected Instance). | This permission is recommended for Instance owners who should be allowed to take snapshots. |  |
+| Snapshots: Linked Clone | None, Full | For VMware Cloud Instances, this controls access to the ability to create linked clone snapshots on the Instance detail page |  |  |  |
+
+## Tools Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Tools: Archives | None, Read, Full | Determines access to the Tools > Archives page. | Archives provides a way to store files and make them available for download by scripts and users. Archives are organized by buckets. Each bucket has a unique name that is used to identify it in URLs and Scripts. | This permission is recommended for those responsible for storage or scripts which will use the Archive. |  |
+| Tools: Cypher | None, Read, User, Full, Full Decrypt | Determines access to the Tools > Cypher page. The “User” permission will allow access only to objects the user owns. The “Full Decrypt” permission will allow for decryption of secrets. | Secure key/value store. Cypher keys can be used in scripts. | Recommended for those who need to store or use security key value pairs. |  |
+| Tools: Image Builder | None, Read, Full | Determines access to the Tools > Image Builder page, Image Builds, Boot Scripts, and Preseed Scripts tabs. | The VM Essentials Image Builder tool creates vmdk, qcow2, vhd and raw images. The Image Builder creates a blank VM in VMware, attaches an OS ISO, executes a boot script on the VM at startup via VNC, which calls a preseed script that runs the unattended OS installation and configuration. VM Essentials then executes an OVA export of the completed vmdk to the target storage provider and converts the image to all other specified formats. | Recommended for those who are responsible for image creation. |  |
+| Tools: Kubernetes | None, Read, User, Full | Allows for the management of Kubernetes clusters via the API (may be deprecated in the near future). | Allows for the management of Kubernetes clusters via the API | This permission is recommended for those who need to manage Kubernetes clusters via the API. | It is recommended this permission is set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Virtual Desktop Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Virtual Desktop: Copy/Paste | None, Full | Allows copy and paste access from the virtual desktop terminal | Enables the user to copy and paste values from a virtual desktop session into the paste buffer of their local computer |  |  |
+| Virtual Desktop: Local Printer | None, Full | Enables printing from a virtual desktop session to a locally installed printer |  |  |  |
+| Tools: VDI Pools | None, Read, Full | Allows for the management of virtual desktop (VDI) pools. | Enables the user to access the VDI Pools section (Tools > VDI Pools) and view existing pools (with “read” permission) or create and edit pools (with “full” permission). Related API functions are also granted with this feature permission. | This permission is recommended for those needing to manage VDI pools |  |
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json b/corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
new file mode 100644
index 0000000..6649535
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+  "title": "Networking Integrations",
+  "ordinal": 347,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html",
+  "topic_cluster": {
+    "clustering_title": "Networking Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md b/corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
new file mode 100644
index 0000000..44ef233
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
@@ -0,0 +1,6 @@
+# Networking Integrations
+
+**Subtopics**  
+
+- **[ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html)**
+- **[HPE Aruba CX DSS](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json b/corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
new file mode 100644
index 0000000..b3a66f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+  "title": "Dashboard",
+  "ordinal": 6,
+  "parent_title": "Operations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.html",
+  "topic_cluster": {
+    "clustering_title": "Dashboard",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+        "clustering_title": "Dashboard"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430",
+        "clustering_title": "Dashboard"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md b/corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
new file mode 100644
index 0000000..490bb21
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.md
@@ -0,0 +1,17 @@
+# Dashboard
+
+The Dashboard is a single, high-level view into your environment which includes easy-to-read performance and configuration information. In many cases other areas within VM Essentials UI will allow you to drill deeper into the information presented in the dashboard.
+
+![dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-EED20D75-2987-4570-A0F2-5AD920F49D1D-high.png)
+
+**Subtopics**  
+
+- **[Environment](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.html)**
+- **[System Status](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1457342F-8258-47AC-AEB3-54E5FE00E434.html)**
+- **[Favorites](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.html)**
+- **[Alarms (dashboard)](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.html)**
+- **[Instance Status](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.html)**
+- **[Instances By Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5535CC34-A097-4374-B6A9-CF82FC9E25E1.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-91D3F799-4C17-4008-B605-FEE370890091.html)**
+- **[Task Executions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2982E9F4-FB10-4CB9-A863-3A1D0D91A615.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-371A58A1-F821-449C-8D2D-EC2657C13B56.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json b/corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
new file mode 100644
index 0000000..9fb5410
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+  "title": "Using Cypher Keys in Scripts",
+  "ordinal": 224,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.html",
+  "topic_cluster": {
+    "clustering_title": "Using Cypher Keys in Scripts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+        "clustering_title": "Using Cypher Keys in Scripts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA",
+        "clustering_title": "Using Cypher Keys in Scripts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md b/corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
new file mode 100644
index 0000000..3cb9e8b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BCA61E72-6A56-4EED-9873-52D67A3F8CFA.md
@@ -0,0 +1,15 @@
+# Using Cypher Keys in Scripts
+
+To use a Cypher key in a script, use the following syntax:
+
+`<%=cypher.read('var_name')%>`
+
+Example: `PASSWORD=<%=cypher.read('secret/myuserpassword')%>`
+
+Cypher also includes an option to read a value from the `password/*` mountpoint or create one if it doesn’t already exist. Use the following syntax:
+
+`<%=cypher.readPassword('var_name')%>`
+
+Example: `` PASSWORD=<%=cypher.readPassword('myuserpassword')%>` ``
+
+It should be noted that when Cypher keys are created using the `readPassword` function, the subsequent reads can only come from the same user. If another VM Essentials user attempts to run the automation script containing the `readPassword` call, the secret value will not be read and it’s very likely the script will fail. For Tasks that need to be run by multiple users, use a pre-existing Cypher key and reference it back in the script using `read` rather than `readPassword`.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json b/corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
new file mode 100644
index 0000000..93ed65b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+  "title": "Hypervisor Console Keyboards",
+  "ordinal": 136,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html",
+  "topic_cluster": {
+    "clustering_title": "Hypervisor Console Keyboards",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md b/corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
new file mode 100644
index 0000000..9954624
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
@@ -0,0 +1,52 @@
+# Hypervisor Console Keyboards
+
+HVM VMs support guest console access as well as hypervisor console access. For each HVM VM, users can set a keyboard layout configuration which will then be set for use on each session.
+
+IMPORTANT
+
+This feature requires HVM Host agent version 3.0.3 or greater. Upgrade the host agent from the host detail page for **each** host by expanding the ACTIONS menu and clicking "Upgrade Agent." Alternatively, select "Download Agent Script" to download a script to run against the host manually from a terminal session. These scripts are specific to each host so you must download a script for each host and run the correct script against the correct host.
+
+Currently, the following layouts are supported:
+
+- Dutch (Belgium)
+- French (Belgium)
+- German
+- Italian
+- English (United Kingdom)
+- English (United States)
+- French
+- Spanish
+- German (Switzerland)
+- Finnish
+- French (Switzerland)
+- Icelandic
+- Norwegian
+- Portuguese
+- Danish
+
+Setting the Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click EDIT
+6. Expand the Advanced Options section
+7. In the KEYBOARD LAYOUT field, select the desired keyboard localization
+8. Click SAVE CHANGES
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-6EC36C91-5E13-4B5B-AB20-10DE225F85B3-high.png)
+
+Using the Configured Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click on the Console tab
+6. Click on the dropdown labeled GUEST and change the selection to Hypervisor
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-B75612CA-1867-4066-937C-B66FA952D251-high.png)
+7. Click on the keyboard icon and see the keyboard layout has changed to the selected layout
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-EC09C556-7F46-4036-ABDF-7E36BE8BFD8D-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json b/corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
new file mode 100644
index 0000000..11e494c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+  "title": "Affinity Groups",
+  "ordinal": 125,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md b/corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
new file mode 100644
index 0000000..8bf051d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
@@ -0,0 +1,28 @@
+# Affinity Groups
+
+HVM Clusters offer affinity groups and anti-affinity groups. These work similarly to affinity groups on other platforms, such as the affinity rules concept in VMware vSphere. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Whenever possible, servers configured to "Keep Together" will run on the same HVM Host. Servers configured to "Keep Separate" will be balanced across HVM Hosts to the maximum extent possible.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-C5C8E073-11BC-4D5A-A900-14571F77280D-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next cluster sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+TIP
+
+Placement settings (ex. pinning a VM to a specific host) can override an affinity group. HVM Clusters will attempt to implement affinity groups intelligently to work around VM placement. For example, in a group of five VMs configured to "keep together" with one pinned to host 1, the Cluster would run all five VMs on host 1 (if possible) to simultaneously honor the placement and the affinity group. In some scenarios, it will not be possible to simultaneously honor all placements and affinities/anti-affinities.
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-9C039E15-FE97-4CFD-987E-07A16E644534-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-12E8B43B-9A47-46D9-8A99-3EBDF1FAD577-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json b/corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
new file mode 100644
index 0000000..40465bb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+  "title": "VMware vCenter",
+  "ordinal": 314,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html",
+  "topic_cluster": {
+    "clustering_title": "VMware vCenter",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md b/corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
new file mode 100644
index 0000000..b3b8671
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
@@ -0,0 +1,25 @@
+# VMware vCenter
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-202C8048-0342-4653-97C6-7817B2A9EEB3.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-30D62FE4-33A5-4AD6-8DE8-CBA6DE904A9B.html)**
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6330641A-2097-4246-BEC6-2AD14EF8BFC7.html)**
+- **[Windows Provisioning Tips](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4D79ACBA-9CC0-4F2D-AE39-5D8C7051BF96.html)**
+- **[Existing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.html)**
+- **[Service Plans](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-30353E6D-5FA2-470C-BB80-238663945F6F.html)**
+- **[Virtual Images / Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-95CE50B4-A83B-40BE-9B43-2FE640DAB59D.html)**
+- **[Snapshots](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9988A0D1-2595-457C-84AE-037FCBD6DCFF.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-893076B2-A491-41B5-AFEA-9D4E9AFF1D67.html)**
+- **[Tagging and Metadata](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1D9C9A40-8C8C-4C06-A0AA-4834FB6823E2.html)**
+- **[Docker](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B82658C8-6002-424B-B257-D52A7D603BC3.html)**
+- **[Multitenancy](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4D9D5F48-E8E9-4685-B520-19F1BF6D045D.html)**
+- **[Advanced](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1EB800EB-6832-487E-BB11-07D8520003CF.html)**
+- **[VMware Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-83AC77E8-48AE-420C-8D3D-D9CCFFA2426E.html)**
+- **[Creating a VM Essentials VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-17230E5D-DFC2-42A1-900E-1C01A1508954.html)**
+- **[Creating a Windows Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.html)**
+- **[Creating a CentOS/RHEL 7 Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.html)**
+- **[Creating a CentOS/RHEL 8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42.html)**
+- **[Creating an Ubuntu 20.04 Image](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.html)**
+- **[Gotchas](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F.html)**
+- **[A Note on Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json b/corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
new file mode 100644
index 0000000..2cdfc4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+  "title": "Delete Group",
+  "ordinal": 88,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Group",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+        "clustering_title": "Delete Group"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD",
+        "clustering_title": "Delete Group"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md b/corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
new file mode 100644
index 0000000..39958a6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BF589862-B2FB-4AC4-AE04-DFEF0D2405CD.md
@@ -0,0 +1,13 @@
+# Delete Group
+
+## About this task
+
+To delete a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to delete.
+4. Click the Delete button.
+5. Confirm
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json b/corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
new file mode 100644
index 0000000..c63c35e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+  "title": "Automation",
+  "ordinal": 55,
+  "parent_title": "Library",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.html",
+  "topic_cluster": {
+    "clustering_title": "Automation",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+        "clustering_title": "Automation"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7",
+        "clustering_title": "Automation"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md b/corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
new file mode 100644
index 0000000..c465494
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-BF62AC21-9C15-4C31-BBD0-F56567143BD7.md
@@ -0,0 +1,10 @@
+# Automation
+
+Library  >  Automation
+
+The automation section is where scripts, known as Tasks, can be created. Tasks are individual Bash or Powershell scripts which can be selected to run against Instances at the time they are provisioned from the Instance provisioning wizard. In this section, users can also create execution schedules which are configured time intervals on which automated jobs (such as backups) would be carried out.
+
+**Subtopics**  
+
+- **[Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html)**
+- **[Execute Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-46D03C40-2146-434A-B75A-12BBBDB56FF3.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json b/corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
new file mode 100644
index 0000000..ce56058
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+  "title": "Google Cloud Storage Buckets",
+  "ordinal": 182,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.html",
+  "topic_cluster": {
+    "clustering_title": "Google Cloud Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+        "clustering_title": "Google Cloud Storage Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191",
+        "clustering_title": "Google Cloud Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md b/corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
new file mode 100644
index 0000000..c485aa7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C33FB8E6-B92B-45E9-ACCC-99AF61095191.md
@@ -0,0 +1,53 @@
+# Google Cloud Storage Buckets
+
+## About this task
+
+NOTE
+
+Google Cloud Storage Buckets are associated with an existing GCP Cloud integration. Ensure the GCP Cloud integration is pre-existing before attempting to create a new Google Cloud Storage Bucket. On the initial integration and subsequent cloud syncs, Google Cloud Storage Buckets are automatically onboarded and updated.
+
+To add a Google Cloud Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Select the Storage link in the sub-navigation bar
+3. In the BUCKETS tab, Click the + ADD button
+4. Select Google Cloud Storage from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   A friendly name for the bucket in VM Essentials
+
+   STORAGE SERVICE
+   :   Select the GCP cloud integration this bucket should be created in
+
+   PROJECT ID
+   :   Select the Project to create the group under, Projects are a GCP-specific concept and are logical grouping for your resources. Select any existing project associated with your selected GCP cloud integration
+
+   BUCKET NAME
+   :   The name for the bucket resource on the GCP side
+
+   LOCATION TYPE
+   :   Select Region, Dual-Region, or Multi-Region. Buckets with a Region location type will be stored in one GCP region, such as “us-east1 (South Carolina)”. Dual-Region and Multi-Region data is stored in two (or more, in the case of multi-region) GCP regions separated by a significant physical distance. Dual-Region and Multi-Region data is geo-redundant across the multiple selected regions
+
+   LOCATION
+   :   A selected GCP region (or regions, in the case of dual and multi-location data) where the data will be stored
+
+   STORAGE CLASS
+   :   Select Standard, Nearline, Coldline, or Archive. The appropriate storage class will depend on how frequently the bucket data is accessed and how long the type of data in the bucket is expected to be stored. More information on storage classes can be found in [GCP Documentation](https://cloud.google.com/storage/docs/storage-classes#descriptions)
+
+   ACTIVE
+   :   When marked, the bucket is available for use in VM Essentials
+
+   DEFAULT BACKUP TARGET
+   :   Sets the bucket as the default storage option when creating backups at provision time or in the Backups section of VM Essentials
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this Bucket as the default storage target when uploading deployment files in the Deployments section
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this bucket as the default storage target when uploading virtual images from the Virtual Images section, importing images from Instance actions, creating images with the Image Builder, and when creating new images from Migrations
+
+   RETENTION POLICY
+   :   Select None and the files in this bucket will never be deleted or backed up by VM Essentials. When selecting ‘Backup Old Files’, VM Essentials will backup files into another selected bucket once they reach a certain number of days old. When selecting ‘Delete Old Files’, VM Essentials will delete any files that reach a certain number of days old
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json b/corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
new file mode 100644
index 0000000..5466673
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+  "title": "Creating a Windows Image",
+  "ordinal": 333,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Windows Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+        "clustering_title": "Creating a Windows Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA",
+        "clustering_title": "Creating a Windows Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md b/corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
new file mode 100644
index 0000000..20bad9b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA.md
@@ -0,0 +1,6 @@
+# Creating a Windows Image
+
+**Subtopics**  
+
+- **[Supported Versions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5571B267-5385-4EEC-A400-FD23FD4B239C.html)**
+- **[Image Preparation](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4A17DFCB-0162-4C08-ADC4-20E4BF0F5223.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json b/corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
new file mode 100644
index 0000000..afe168d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+  "title": "Activity",
+  "ordinal": 21,
+  "parent_title": "Activity",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md b/corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
new file mode 100644
index 0000000..3252f86
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C5D5C9F7-43DD-4E63-AB94-D7268CB223C8.md
@@ -0,0 +1,12 @@
+# Activity
+
+There are three types of activities that are displayed in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
+
+**Subtopics**  
+
+- **[To View a Recent Activity report:](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.html)**
+- **[Review](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-24C6189F-5FCF-4B47-BA4D-0E5ED660F441.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json b/corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
new file mode 100644
index 0000000..25d0ddb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+  "title": "Creating Instances",
+  "ordinal": 45,
+  "parent_title": "Instances",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+        "clustering_title": "Creating Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496",
+        "clustering_title": "Creating Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md b/corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
new file mode 100644
index 0000000..c8815e7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C7399A7B-40C6-4DCA-8A92-EAB777739496.md
@@ -0,0 +1,25 @@
+# Creating Instances
+
+The Instance catalog is where you will create new workloads targeting the HVM clusters and/or VMware vCenter Clouds available to the VM Essentials environment. The list contains only Instance Types relevant to the provisioning engines which enabled and integrated in the current appliance.
+
+To get started, simply click the + Add button in the upper right of the Provisioning > Instances page. A modal will display allowing the catalog to be searched. Once an item is selected, it is just a matter of following the steps through the wizard.
+
+TIP
+
+The Instance catalog can be customized via role-based access control (RBAC) to restrict provision types only to certain Roles. It is completely customizable.
+
+The next step will ask for a Group and Cloud to be selected. The Group is an abstract representation that can contain multiple HVM clusters or VMware vCenter integrations. Clouds can be in multiple Groups and Groups are also useful for using RBAC to restrict provisioning access and set retainment policies. The wizard continues by allowing us to choose a name for the Instance as well as an environment.
+
+NOTE
+
+Currently the Environment option is most useful for presenting the user with informative metadata around the Instance when coming back to it later.
+
+Moving on, it is now time to configure the Instance. Depending on the Instance Configuration that is chosen, fields will change. This can include cloud-specific fields (i.e. target hosts for HVM clusters or datastores for VMware Clouds). There will also be options like setting an initial user account. Some of these fields are optional and will be represented as such in the wizard.
+
+One last step before the Instance can be provisioned is the Automation step. It is here that you can select Tasks which will run during the provision process and these Tasks must complete successfully in order for the Instance status to be reported as successful. Tasks are either Bash or Powershell scripts which can be configured in the Library > Automationsection.
+
+Now that the steps are completed for provisioning the selected Instance type, simply review your selections and complete. The Instance will automatically show up in the Instances list and its provisioning state will be represented. Depending on what was provisioned this step can range from seconds to minutes.
+
+**Subtopics**  
+
+- **[Converting Discovered Resources to Managed Instances](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-799C061A-12BC-4FD9-AD8B-FF39F2AC9A9F.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json b/corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
new file mode 100644
index 0000000..d2b146c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+  "title": "Adding ArubaCX Integration",
+  "ordinal": 354,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.html",
+  "topic_cluster": {
+    "clustering_title": "Adding ArubaCX Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+        "clustering_title": "Adding ArubaCX Integration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C7747582-1A56-458D-B985-DDF459F1CE7C",
+        "clustering_title": "Adding ArubaCX Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md b/corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
new file mode 100644
index 0000000..aedb686
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C7747582-1A56-458D-B985-DDF459F1CE7C.md
@@ -0,0 +1,73 @@
+# Adding ArubaCX Integration
+
+## About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.
+
+## Procedure
+
+1. Navigate to Administration > Integrations
+2. Select + New Integration > Other > ArubaCX 
+
+   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
+3. Enter the following: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   ENABLED
+   :   Deselect to disable the integration
+
+   USERNAME
+   :   User username for all switches
+
+   PASSWORD
+   :   User password for all switches
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 4
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 4
+
+   UPLINK LAG INTERFACE
+   :   Name of the uplink LAG interface (default is 'lag1')
+4. Select SAVE CHANGES
+
+## Results
+
+Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:
+
+![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)
+
+NOTE
+
+All fields can be edited after saving.
+
+Sample Reference Architecture for EVPN Configuration
+
+1. Minimum four leaf switches, two spine switches, and one core switch
+2. At least two servers in separate racks
+3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
+4. VMs on servers in different racks communicate through the EVPN switch configuration
+5. Route traffic between racks through spine switches
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json b/corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
new file mode 100644
index 0000000..7843dac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+  "title": "Trust",
+  "ordinal": 196,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md b/corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
new file mode 100644
index 0000000..87b9c3a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C7C90D95-205A-4DAC-AC39-3434BE8AAE70.md
@@ -0,0 +1,9 @@
+# Trust
+
+The Trust section is where credentials and SSH keypairs are stored. Stored credentials are useful for easy integration with VMware Clouds or other third party technologies using stored credential sets. In the keypairs section, generate SSH keypairs which can be associated with your user account so that your public key is automatically added to the authorized keys file on provisioned workloads for easy access.
+
+**Subtopics**  
+
+- **[Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-10A7B17C-6F0D-432A-85BD-3205728606A0.html)**
+- **[OAuth 2.0 Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.html)**
+- **[Key Pairs](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json b/corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
new file mode 100644
index 0000000..16b9463
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+  "title": "Requirements",
+  "ordinal": 98,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md b/corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
new file mode 100644
index 0000000..c38ea78
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C92A5571-4EF3-4944-A4A0-007DF4853A9D.md
@@ -0,0 +1,4 @@
+# Requirements
+
+- VM Essentials Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters
+- VM Essentials Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json b/corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
new file mode 100644
index 0000000..275782e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+  "title": "To View a Recent Activity report:",
+  "ordinal": 22,
+  "parent_title": "Activity",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.html",
+  "topic_cluster": {
+    "clustering_title": "To View a Recent Activity report:",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+        "clustering_title": "To View a Recent Activity report:"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7",
+        "clustering_title": "To View a Recent Activity report:"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md b/corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
new file mode 100644
index 0000000..31fea08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C95534E0-39FA-4D43-B4FB-D536277BC0D7.md
@@ -0,0 +1,10 @@
+# To View a Recent Activity report:
+
+## Procedure
+
+1. Select the `Operations` link in the navigation bar.
+2. Select `Activity` in the sub navigation bar.
+
+## Results
+
+Recent activity is displayed in order from recent to oldest. This view can be searched and filtered by type, user, and date range.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json b/corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
new file mode 100644
index 0000000..3900424
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+  "title": "Adding and Removing Labels",
+  "ordinal": 53,
+  "parent_title": "Labels",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.html",
+  "topic_cluster": {
+    "clustering_title": "Adding and Removing Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+        "clustering_title": "Adding and Removing Labels"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7",
+        "clustering_title": "Adding and Removing Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md b/corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
new file mode 100644
index 0000000..3a22536
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-C9E9EC07-3726-47E3-84B6-D33D8FFB42E7.md
@@ -0,0 +1,5 @@
+# Adding and Removing Labels
+
+Labels can be created when adding or edited any of the supported constructs listed above. When adding or editing the object, enter or edit the comma-separated list of labels you wish to apply.
+
+![../_images/labeladd.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-B0C645F7-A738-4975-9AA9-9F5E0C581874-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json b/corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
new file mode 100644
index 0000000..865e2a9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+  "title": "Creating an Ubuntu 20.04 Image",
+  "ordinal": 344,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an Ubuntu 20.04 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+        "clustering_title": "Creating an Ubuntu 20.04 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CA181AC5-CA1D-47ED-9D44-008642C89290",
+        "clustering_title": "Creating an Ubuntu 20.04 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md b/corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
new file mode 100644
index 0000000..c360e34
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CA181AC5-CA1D-47ED-9D44-008642C89290.md
@@ -0,0 +1,97 @@
+# Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Change the network interface to `eth0` by editing `/etc/default/grub`. The line `GRUB_CMDLINE_LINUX=""` should be edited to `GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"`.
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to VM Essentials to onboard the image and use it to begin building your provisioning library.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.json b/corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
new file mode 100644
index 0000000..902c9f6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+  "title": "HVM clusters",
+  "ordinal": 100,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CA806876-1093-4A39-BE62-439C4802A915.html",
+  "topic_cluster": {
+    "clustering_title": "HVM clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+        "clustering_title": "HVM clusters"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CA806876-1093-4A39-BE62-439C4802A915",
+        "clustering_title": "HVM clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.md b/corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
new file mode 100644
index 0000000..c9a90eb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CA806876-1093-4A39-BE62-439C4802A915.md
@@ -0,0 +1,17 @@
+# HVM clusters
+
+An HVM cluster is a hypervisor clustering technology utilizing KVM. Beginning with just a few basic Ubuntu boxes, VM Essentials can create a cluster of HVM hypervisor hosts complete with monitoring, failover, easy migration of workloads across the cluster, and zero-downtime maintenance access to hypervisor host nodes. All of this is backed by a highly-granular RBAC engine, and image library with automation stacks.
+
+**Subtopics**  
+
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html)**
+- **[Base Cluster Details](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-226C1DD5-E007-4F44-A215-2FC03C269EA5.html)**
+- **[Provisioning the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9886AD4A-5C64-4E09-A106-B14419362757.html)**
+- **[Provisioning a Workload](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-45B4119E-416A-43FA-B2A0-C7D52D028326.html)**
+- **[HVM Cluster Networking](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-61426C77-F236-4AFF-A1E3-92893A1FAA9F.html)**
+- **[HVM Cluster Storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6676AECE-BA9F-442A-B834-D6C0E1E1F61F.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html)**
+- **[Utilizing Existing QCOW & ISO Images from an NFS File Share](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AE35F0B9-BDF0-4A25-9E84-763F156878B7.html)**
+- **[Image Prep (Windows)](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html)**
+- **[Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html)**
+- **[Hypervisor Console Keyboards](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json b/corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
new file mode 100644
index 0000000..ad66b96
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+  "title": "Overview",
+  "ordinal": 172,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md b/corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
new file mode 100644
index 0000000..f012482
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.md
@@ -0,0 +1,3 @@
+# Overview
+
+The Network Integrations section allows you to add and manage IPAM, DNS, and Service Registry integrations.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json b/corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
new file mode 100644
index 0000000..96159f8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+  "title": "Operations",
+  "ordinal": 5,
+  "parent_title": "HPE Morpheus VM Essentials Software",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html",
+  "topic_cluster": {
+    "clustering_title": "Operations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md b/corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
new file mode 100644
index 0000000..5970244
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
@@ -0,0 +1,7 @@
+# Operations
+
+**Subtopics**  
+
+- **[Dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BC64B06C-3DB3-4A2F-A520-ADE8FFAEA430.html)**
+- **[Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CD00669C-741C-480C-B444-67F079061438.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0503F050-177F-4360-9B1A-49439AF366B8.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.json b/corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.json
new file mode 100644
index 0000000..bf17160
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+  "title": "Wiki",
+  "ordinal": 16,
+  "parent_title": "Operations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CD00669C-741C-480C-B444-67F079061438.html",
+  "topic_cluster": {
+    "clustering_title": "Wiki",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+        "clustering_title": "Wiki"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD00669C-741C-480C-B444-67F079061438",
+        "clustering_title": "Wiki"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.md b/corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.md
new file mode 100644
index 0000000..7da711a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD00669C-741C-480C-B444-67F079061438.md
@@ -0,0 +1,11 @@
+# Wiki
+
+The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, and Clusters. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations > Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
+
+![wiki](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-F0F0DA3A-4058-45D6-AECA-8A5BEF62FDBA-high.png)
+
+**Subtopics**  
+
+- **[Highlights](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.html)**
+- **[Creating Wikis](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-117D7430-4CD6-4320-9CBE-DFD64A689C7E.html)**
+- **[Hosting Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json b/corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
new file mode 100644
index 0000000..1690333
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+  "title": "Final VMWare Tasks",
+  "ordinal": 343,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.html",
+  "topic_cluster": {
+    "clustering_title": "Final VMWare Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+        "clustering_title": "Final VMWare Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B",
+        "clustering_title": "Final VMWare Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md b/corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
new file mode 100644
index 0000000..e205cf3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD2BA5DA-4A1E-4DB5-9A3B-0C5662D1629B.md
@@ -0,0 +1,8 @@
+# Final VMWare Tasks
+
+## Procedure
+
+1. Detach any install media
+2. Shutdown the VM
+3. Convert the VM to template on the VM Essentials side
+4. Refresh the VM Essentials Cloud to allow the new template to sync
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json b/corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
new file mode 100644
index 0000000..2bd1c31
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+  "title": "CIFS File Shares",
+  "ordinal": 188,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.html",
+  "topic_cluster": {
+    "clustering_title": "CIFS File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+        "clustering_title": "CIFS File Shares"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A",
+        "clustering_title": "CIFS File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md b/corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
new file mode 100644
index 0000000..4860113
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD828DD3-EC29-4AB9-AC61-2C61A0FAE02A.md
@@ -0,0 +1,76 @@
+# CIFS File Shares
+
+## About this task
+
+To Add a CIFS File Share:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select CIFS (Samba Windows File Sharing) from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in VM Essentials.
+
+   HOST
+   :   Enter host IP or resolvable hostname
+       :   Example: `192.168.200.210`
+
+   USERNAME
+   :   CIFS Share Username
+
+   PASSWORD
+   :   CIFS Share User Password
+
+   SHARE PATH
+   :   Enter CIFS Share Path
+       :   Example: `cifs`
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+## Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json b/corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
new file mode 100644
index 0000000..d69abdf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+  "title": "Creating Environments",
+  "ordinal": 289,
+  "parent_title": "Overview",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+        "clustering_title": "Creating Environments"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235",
+        "clustering_title": "Creating Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md b/corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
new file mode 100644
index 0000000..1df2e04
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CD9B0A0E-BC0E-4B44-82FA-CAC59FB13235.md
@@ -0,0 +1,24 @@
+# Creating Environments
+
+## Procedure
+
+1. Select + Create Environment
+2. Populate the following for the New Environment: 
+
+   Name
+   :   The friendly name for the environment in VM Essentials
+
+   Code
+   :   Shortcode used for API and CLI
+
+   Description
+   :   Environment description displayed on the Environments list page
+
+   Display Order
+   :   The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
+
+## Results
+
+NOTE
+
+User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. VM Essentials-default environments can only be hidden from users during provisioning.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json b/corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
new file mode 100644
index 0000000..b27ba1e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+  "title": "Example Cluster Deployment",
+  "ordinal": 106,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.html",
+  "topic_cluster": {
+    "clustering_title": "Example Cluster Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+        "clustering_title": "Example Cluster Deployment"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D",
+        "clustering_title": "Example Cluster Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md b/corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
new file mode 100644
index 0000000..0d8747e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CDB73B95-18B8-4A10-A09C-4176EE11497D.md
@@ -0,0 +1,15 @@
+# Example Cluster Deployment
+
+In this example cluster, each host box consists of:
+
+- 4 vCPU
+- 16 GB memory
+- 20 GB OS boot disk
+- 250 GB data disk (deployed to `/dev/sdb`)
+- 3 network interfaces for management, storage, and compute traffic (set to `eth0`, `eth1`, and `eth2`, respectively, in this example. Your environment may differ.)
+
+NOTE
+
+250 GB data disks used in this example are simply for demonstration purposes. A typical test cluster should consist of at least 500 GB storage and more will be required for production. Do not raid disks on physical servers. Multiple disks may be specified per host by giving a comma-separated list (ex. /dev/sda,/dev/sdb,/dev/sdc,etc.) in the DATA DEVICE field during cluster setup. These along with disks from all other nodes will be added to the total storage, which is presented as one large volume.
+
+HVM clusters must also live in Private Cloud-type Clouds (See Infrastructure > Clouds). A pre-existing Cloud may be used or a new Cloud could be created to house HVM clusters.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json b/corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
new file mode 100644
index 0000000..996a0f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+  "title": "Directory Pools Overview",
+  "ordinal": 113,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.html",
+  "topic_cluster": {
+    "clustering_title": "Directory Pools Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+        "clustering_title": "Directory Pools Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1",
+        "clustering_title": "Directory Pools Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md b/corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
new file mode 100644
index 0000000..58e01a2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CE78CA16-8C46-4714-B1F4-38CFF81043D1.md
@@ -0,0 +1,11 @@
+# Directory Pools Overview
+
+Directory Pools allow designation of a directory on the local host filesystem as a datastore. By default on creation of the HVM cluster, three Directory Pools are automatically created which helps ensure HVM can work straight out of the box even without other integrated storage. The default Directory Pools are:
+
+- `local` at `/var/morpheus/kvm/local` for storage of virtual disks for VMs
+- `morpheus-cloud-init` at `/var/morpheus/kvm/cloud-init` for storage of ephemeral clout-init ISOs
+- `morpheus-images` at `/var/morpheus/kvm/images` for storage of virtual images
+
+TIP
+
+Of these default Directory Pools, only the `local` pool is selectable as a provisioning target for storing virtual disks. Using this Directory Pool runs the risk of filling up the HVM Host filesystem and bringing down the host. For this reason, it may be advisable to edit this datastore and make it inactive. Use an alternative datastore, such as an NFS Pool or GFS Pool (discussed in the upcoming sections) to avoid filling up the local filesystem. The other two default Directory Pools can remain active as they are created for specific purposes and will not be selectable for users as a datastore at provision time.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json b/corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
new file mode 100644
index 0000000..a756d60
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+  "title": "Tasks",
+  "ordinal": 56,
+  "parent_title": "Automation",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html",
+  "topic_cluster": {
+    "clustering_title": "Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md b/corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
new file mode 100644
index 0000000..96256f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
@@ -0,0 +1,12 @@
+# Tasks
+
+**Subtopics**  
+
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5663C34A-23E8-42CA-B7BF-5A79A0070456.html)**
+- **[Target Options](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.html)**
+- **[Execute Options](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B5706BDE-C333-4E3C-83CA-AFDAD973B3C8.html)**
+- **[Source Options](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9F7205DD-815F-4E4E-AFC2-CDE670961E08.html)**
+- **[Allow Custom Config](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-20656567-501C-4D21-9EDA-1C6898DF61F5.html)**
+- **[Adding Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6B80D87B-8461-414D-9172-07E68896EB06.html)**
+- **[Editing Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-78DE430D-BDC3-4E67-9886-95B73F6D9C80.html)**
+- **[Deleting Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-75E8BE89-7C3B-4C6A-B78C-581A0F21297F.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json b/corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
new file mode 100644
index 0000000..8a91e60
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+  "title": "To add a VM Essentials Network Pool",
+  "ordinal": 156,
+  "parent_title": "IP Pools",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.html",
+  "topic_cluster": {
+    "clustering_title": "To add a VM Essentials Network Pool",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+        "clustering_title": "To add a VM Essentials Network Pool"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338",
+        "clustering_title": "To add a VM Essentials Network Pool"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md b/corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
new file mode 100644
index 0000000..3e4e7b7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D06F5BCE-D2E0-40AC-9F9C-BE1CA9926338.md
@@ -0,0 +1,26 @@
+# To add a VM Essentials Network Pool
+
+## Procedure
+
+1. Click + ADD in Infrastructure  >  Network  >  IP Pools
+2. Enter the following:
+   :   Name
+       :   A friendly name for the IP Pool in VM Essentials.
+
+       Pool Type
+       :   Currently, HVM-type IP Pools and NSX IP Pools (with a configured integration) can be created directly from VM Essentials
+
+       Starting Address
+       :   The starting IP address of the IP Pool address range. ex: 192.168.0.2
+
+       Ending Address:
+       :   The ending IP address of the IP Pool address range. ex: 192.168.0.255
+3. Save Changes
+
+## Results
+
+NOTE
+
+Multiple Address Ranges can be added to a pool by selecting the + icon next to the address range.
+
+After saving the IP pool will be available for assignment to networks in the NETWORK POOL dropdown when adding or editing a network.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json b/corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
new file mode 100644
index 0000000..780aaab
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+  "title": "Adding NFS Pools",
+  "ordinal": 116,
+  "parent_title": "HVM Cluster Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.html",
+  "topic_cluster": {
+    "clustering_title": "Adding NFS Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+        "clustering_title": "Adding NFS Pools"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E",
+        "clustering_title": "Adding NFS Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md b/corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
new file mode 100644
index 0000000..370adaf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D280323C-DF16-4F69-86CA-111B7CFCA25E.md
@@ -0,0 +1,21 @@
+# Adding NFS Pools
+
+Before adding an NFS Pool, ensure your NFS target is configured as described in the previous section. With configuration complete, follow the steps below:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. Click into the Storage tab and then the Data Stores subtab
+4. Click ADD
+5. From the ADD DATA STORE modal, configure the following:
+
+   1. **NAME:** An identifiable name for the datastore in the UI
+   2. **TYPE:** NFS Pool
+   3. **SOURCE HOST:** The NFS server name or IP address
+   4. **SOURCE DIRECTORY:** The path of the exported NFS share
+   5. **VERSION:** Either 3 or 4 depending on the NFS version running on the source server
+   6. **IMAGE TARGET:** Marked if this datastore should be used as a storage location for virtual images
+6. Click Save
+
+![The add datastore modal for NFS-type datastores](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-D53B7324-222A-4953-9222-824F49846CB0-high.png)
+
+At this point the HVM manager will automatically mount the NFS share on all hosts within the cluster. It will also handle setting various other options such as autostart and management of mountpoint for the share within the host filesystem.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json b/corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
new file mode 100644
index 0000000..78034d7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+  "title": "Additional System Health Indices",
+  "ordinal": 262,
+  "parent_title": "VM Essentials Health",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.html",
+  "topic_cluster": {
+    "clustering_title": "Additional System Health Indices",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+        "clustering_title": "Additional System Health Indices"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA",
+        "clustering_title": "Additional System Health Indices"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md b/corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
new file mode 100644
index 0000000..a10a94f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.md
@@ -0,0 +1,106 @@
+# Additional System Health Indices
+
+CPU
+:   - Processor Count
+    - Process Time
+    - Morpheus CPU
+    - System CPU
+    - System Load
+
+MEMORY
+:   - Morpheus Memory
+    - Morpheus Used Memory
+    - Morpheus Free Memory
+    - Morpheus Memory Usage
+    - System Memory
+    - System Used Memory
+    - System Free Memory
+    - System Memory Usage
+    - System Swap
+    - Free Swap
+
+DATABASE
+:   - Lifetime Connections
+    - Aborted Connections
+    - Max Used Connections
+    - Max Connections
+    - Threads Running
+    - Threads Connected
+    - Slow Queries
+    - Temp Tables
+    - Key Reads
+    - Handler Reads
+    - Buffer Pool Free
+    - Open Tables
+    - Table Scans
+    - Full Joins
+    - Key Read Requests
+    - Key Reads
+    - Engine Waits
+    - Lock Waits
+    - Handler Reads
+    - Engine IO Writes
+    - Engine IO Reads
+    - Engine IO Double Writes
+    - Engine Log Writes
+    - Engine Memory
+    - Dictionary Memory
+    - Buffer Pool Size
+    - Free Buffers
+    - Database Pages
+    - Old Pages
+    - Dirty Page Percent
+    - Max Dirty Pages
+    - Pending Reads
+    - Insert Rate
+    - Update Rate
+    - Delete Rate
+    - Read Rate
+    - Buffer Hit Rate
+    - Read Write Ratio
+    - Uptime
+
+ELASTIC
+:   - Status
+    - Cluster
+    - Node Count
+    - Data Nodes
+    - Shards
+    - Primary Shards
+    - Relocating Shards
+    - Initializing
+    - Unassigned
+    - Pending Tasks
+    - Active Shards
+
+NOTE
+
+status is typical for Opensearch
+
+Elastic Nodes
+:   - Node
+    - Master
+    - Location
+    - Heap Usage
+    - Memory Usage
+    - CPU Usage
+    - 1M Load
+    - 5M Load
+    - 15M Load
+
+Elastic Indices
+:   - Health
+    - Index
+    - Status
+    - Primary
+    - Replicas
+    - Doc
+    - Count
+    - Primary
+    - Size
+    - Total Size
+
+Queues
+:   - Queue Count
+    - Busy Queues
+    - Error Queues
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json b/corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
new file mode 100644
index 0000000..7f6e3ac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+  "title": "VM Essentials Health",
+  "ordinal": 260,
+  "parent_title": "Health",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.html",
+  "topic_cluster": {
+    "clustering_title": "VM Essentials Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+        "clustering_title": "VM Essentials Health"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4",
+        "clustering_title": "VM Essentials Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md b/corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
new file mode 100644
index 0000000..cd2e6f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D3B7CC62-F772-4B71-ADB5-2ED9381B7FB4.md
@@ -0,0 +1,15 @@
+# VM Essentials Health
+
+The VM Essentials Health section provides an overview of the health of your VM Essentials appliance. It includes an appliance health summary in the following areas:
+
+- **CPU:** Appliance CPU usage is checked. If usage is greater than 50%, this indicator will be in a yellow or warning state. If VM Essentials is unable to complete the check, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to upgrade to increase CPU. The **Overall** health indicator will mirror the CPU health indicator
+- **Memory:** If swap usage is above 60% or VM Essentials memory usage is above 95%, this indicator will be in a yellow or warning state. If VM Essentials is unable to complete the check for any reason, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to increase swap, upgrade the appliance to add memory, or consider a different appliance architecture for those using single-node appliances
+- **Storage:** If utilization of the filesystem mounted at “/” exceeds 80%, this indicator will be in a yellow warned status. Above 90% will put this indicator in red or error status
+- **Database:** The database is checked. If the number of database connections exceeds the configured maximum number of connections or if any test queries are reported as being slow, this indicator will be in a yellow or warning state. If VM Essentials is unable to communicate with the database, it will be in a red or error state. In the database section further down the page, you can check the number of maximum used connections against the number of max connections. In the case of database connections exceeding the maximum, consider increasing the maximum settings connection
+- **Elastic:** Elasticsearch is polled for the health status of each index. If any indices are not reporting a “green” health status, this indicator will be in a yellow or warning state.
+- **Queues:** RabbitMQ queues are checked. Any queues containing more than 1000 messages are considered to be in an error state. Appliance Queue health is given in a yellow or warning status when any queues are in such an error state. In the Queues section further down the page you can see the individual Queues listed and which have messages piling up. When the appliance is unable to complete the check for any reason, this indicator will be in a red or error state
+
+**Subtopics**  
+
+- **[Health Levels](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0DC34FAA-C182-4FAA-BFE3-70147815F471.html)**
+- **[Additional System Health Indices](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-D38ACCEA-91A1-402D-AF9A-D1E5991A46BA.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json b/corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
new file mode 100644
index 0000000..d762bea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+  "title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+  "ordinal": 235,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md b/corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
new file mode 100644
index 0000000..b61b5d6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
@@ -0,0 +1,59 @@
+# Configuring Windows Workloads (Windows 2022 or later) for Migration
+
+Migrating Windows workloads from VMware vCenter Clouds to HVM Clusters using the bulk Migrations feature requires some initial configurations checks. This section goes through an example preparation process for a Windows VM running on vCenter.
+
+This guide makes the following assumptions about the workload to be migrated:
+
+- Configured to boot as EFI or BIOS
+- Virtualization Based Security (VBS) is enabled
+- Secure Boot is enabled
+- Trusted Platform Module (TPM) is disabled
+- The VM has access to the recovery partition (if not, a Windows Recovery Environment disc or installation media may be required to access some of the menus referenced in this section)
+
+Inject VirtIO Drivers
+
+To begin, restart the VMware Windows guest in the [Windows Recovery Environment (Windows RE)](https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b). In Windows RE, choose a keyboard layout if prompted. Then, select the **Troubleshoot** option. From the Troubleshoot menu, select **Command Prompt**.
+
+Within the Command Prompt session, enter **diskpart** using this command: `diskpart`. Check the disks that are available with `list disk`. At this point, you may receive the message that "There are no fixed disks to show." or the disk with Windows OS might not be listed. If that is the case, follow the steps in the next section to mount the drives. If that is not the case, skip to the following section to continue the process of injecting the VirtIO drivers.
+
+![Enter dispart command line tool and list disks](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-6D43B362-18E8-4E21-8CE1-733555398E59-high.png)
+
+Mounting the Drives
+
+From vCenter, mount the VMware Tools installer to the VM using the "Install VMware Tools..." option (**Actions > Guest OS > Install VMware Tools...**). Then, back in diskpart, use the following command to find the CD/DVD-ROM drive letter: `list volume`. Make note of the CD-ROM drive letter, which in the case of this example is drive "D." Exit diskpart with the `exit` command.
+
+![listing volumes in diskpart](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-E8FB0956-0BE4-4600-ACC9-DD48E590F2CE-high.png)
+
+Enter the following command to load the storage drivers which will enable you to see the hard disks: `drvload "D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64\pvscsi.inf"`. Note that the prior command references Windows 10 as the operating system but choose the most appropriate or the latest available. It also references drive "D" which may vary from case to case.
+
+With the driver loaded, once again confirm the disks are mounted with `diskpart` and `list disk`. They're now mounted but the partitions/volumes need drive letters so, while still in diskpart, list the volumes with: `list volume`. In this example case, "Volume 1" is the primary Windows volume. Select the volume and assign a drive letter, in the example case the assigned letter will be "C": `select volume 1` and `assign letter=c`. Check your work by listing the volumes again, the primary Windows volume should be assigned the correct drive letter: `list volume`.
+
+![Assigning a drive letter to a volume](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-8506AA86-13D4-4086-B361-5C5AB0CFC5E9-high.png)
+
+Exit diskpart once again (`exit`) and unmount the VMware Tools installer from the VM back in the vCenter console (**Actions > Guest OS > Unmount VMware Tools Installer**).
+
+Inject VirtIO drivers (cont.)
+
+Download the [latest](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) or [stable](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/) VirtIO drivers ISO to your local workstation. The latest is recommended but often they are the same. Add the ISO to vCenter either by uploading it to a datastore or to the Content Library. Still in vCenter, mount the ISO using a CD-ROM device on the VM and make sure it's connected. Enter the following commands to inject the VirtIO storage drivers into the Windows boot-start drivers from the mounted ISO: `dism /image:C:\ /add-driver:D:\viostor\2k22\amd64\viostor.inf` and `dism /image:C:\ /add-driver:D:\vioscsi\2k22\amd64\vioscsi.inf`. Note once again that the OS volume will not be assigned the "C" drive letter and the CD-ROM device will not be assigned the "D" drive letter in every case. Similarly, in this example "2k22" is used but that won't be appropriate in every case. If successful, a message will be received that the driver packages were successfully installed. Close the Command Prompt window and click **Continue** to boot Windows once again.
+
+![installing viostor.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-A481A334-59CE-42D9-857D-0B5FDEE31BAB-high.png)![installing vioscsi.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-10CEA2F9-9885-464E-A57B-303AC913FBBD-high.png)
+
+Prepare the OS
+
+Once logged back in, install the VirtIO drivers in the OS using the ISO, which is still mounted, by navigating to the CD-ROM/DVD-ROM drive. Install `virtio-win-gt-x64.msi` and `virtio-win-guest-tools.exe` from the root of the ISO. Maintain all default selections during the installation. Next, unmount any ISOs still attached to the VM, either by ejecting in Windows or by setting the CD-ROM drive to "Client Device" in vCenter.
+
+Now, shut down the VM. Keep in mind that the VMware Cloud integration may be configured to automatically maintain power state of associated VMs. Navigate to Infrastructure > Clouds and edit the Cloud. Make note of the "AUTOMATICALLY POWER ON VMS" configuration. If checked, you will need to shut down the VM via the product UI tools rather than from the vCenter console or from within the guest OS. Alternatively, you could uncheck "AUTOMATICALLY POWER ON VMS", save changes to the Cloud, and then power down the VM from vCenter or from the guest OS but bear in mind changing this configuration would affect all VMs associated with the Cloud in the product.
+
+Migrating
+
+This completes the preparation steps. From here, create a new Migration Plan that includes the prepared VM and run it. Take a look at the previous section for more information on creating and running Migration Plans.
+
+Post-Conversion
+
+As a final note, bear in mind that the migration tool does not uninstall VMware Tools following conversion, which can lead to start-up errors being surfaced in migrated VMs. In some cases, the VMware Tools installation may become corrupted which prevents simply uninstalling using the Control Panel.
+
+To prevent VMware Tools from executing at startup, within the Windows guest navigate to Settings > Apps > Startup and turn off VMware Tools Core Service. See the example screenshot below for a Windows 2022 Guest.
+
+![Turning off VMware Tools Core Service at Windows guest startup](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-EEC38EAD-A903-41BD-8C98-BACAC114BA0E-high.png)
+
+Additionally, you can attempt to uninstall VMware Tools completely using Microsoft recommended processes and tooling for uninstalling stuck programs. See [this article](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d) from the Microsoft Support for procedure and links to a helpful tool.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json b/corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
new file mode 100644
index 0000000..4145277
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+  "title": "Task Types",
+  "ordinal": 64,
+  "parent_title": "Allow Custom Config",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.html",
+  "topic_cluster": {
+    "clustering_title": "Task Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+        "clustering_title": "Task Types"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837",
+        "clustering_title": "Task Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md b/corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
new file mode 100644
index 0000000..7784855
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D51F6C09-DCBA-4954-B0E9-8FDDC91B3837.md
@@ -0,0 +1,9 @@
+# Task Types
+
+Available Task Types
+
+         |  | Task Type | Task Description | Source Options | Execute Target Options | Configuration Requirements | Role Permissions Requirements |
+| --- | --- | --- | --- | --- | --- | --- |
+| powershell | PowerShell Script | Execute PowerShell Script on the Target Resource | Local, Repository, Url | Remote, Resource, Local | None | Library: Tasks |
+| restart | Restart | Restarts target VM/Host/Container and confirms startup status before executing next task in Workflow | System | Resource | None | Library: Tasks |
+| shellscript | Shell Script | Executes Bash script on the target resource | Local, Repository, Url | Local, Remote, Resource | None | Library: Tasks |
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json b/corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
new file mode 100644
index 0000000..3a1fd92
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+  "title": "Existing Instances",
+  "ordinal": 319,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.html",
+  "topic_cluster": {
+    "clustering_title": "Existing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+        "clustering_title": "Existing Instances"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA",
+        "clustering_title": "Existing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md b/corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
new file mode 100644
index 0000000..b8a8b9a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D5586743-D9BC-470E-9F25-3B35A3CD9ABA.md
@@ -0,0 +1,11 @@
+# Existing Instances
+
+VM Essentials provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into VM Essentials. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, VM Essentials will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json b/corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
new file mode 100644
index 0000000..14e509c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+  "title": "Configuring HPE Morpheus Enterprise Appliance Backup",
+  "ordinal": 311,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D647F00D-6B45-4E18-B442-14835847EFA7.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+        "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D647F00D-6B45-4E18-B442-14835847EFA7",
+        "clustering_title": "Configuring HPE Morpheus Enterprise Appliance Backup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md b/corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
new file mode 100644
index 0000000..9f20e4f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D647F00D-6B45-4E18-B442-14835847EFA7.md
@@ -0,0 +1,23 @@
+# Configuring HPE Morpheus Enterprise Appliance Backup
+
+## About this task
+
+With the groundwork laid in the previous sections, we’re ready to enable and configure HPE Morpheus Enterprise appliance backup.
+
+## Procedure
+
+1. Navigate to Administration > Settings > Backups
+2. Slide the switch labeled “Backup Appliance”
+3. Click SAVE
+
+## Results
+
+On saving this change, a text link labeled “Backup” will be activated which will take you directly to the automatically-generated appliance backup job. Click this link to continue.
+
+1. Click the EDIT button
+2. Enter a name for the appliance backup job if you wish to change it from the default
+3. Select the appropriate storage bucket or file share
+4. Choose a pre-created backup job. If you do not have an existing backup job that fits, a retention count and schedule can be manually created in this modal. If you manually configure retention counts and schedules in addition to associating a Job, the Job values will override any manual settings.
+5. Click SAVE CHANGES
+
+At this point, your appliance will be automatically backed up on the schedule you chose and stored in the selected location. An appliance backup will store backup copies of the appliance MySQL database. Should you need to restore or migrate your database from backup, follow the steps in the next section of this guide.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json b/corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
new file mode 100644
index 0000000..0baac1d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+  "title": "Upgrade License Key",
+  "ordinal": 293,
+  "parent_title": "License",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrade License Key",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+        "clustering_title": "Upgrade License Key"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB",
+        "clustering_title": "Upgrade License Key"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md b/corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
new file mode 100644
index 0000000..f5d10b4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D6B5BF84-8D86-4215-94FF-119D52387FDB.md
@@ -0,0 +1,14 @@
+# Upgrade License Key
+
+## About this task
+
+To add a new or update an existing License:
+
+## Procedure
+
+1. Copy the license key into the large text area at the bottom of the page
+2. Click UPDATE
+
+## Results
+
+If valid, the new License will be applied. Note that the new license may replace an existing license or may stack onto an existing license.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json b/corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
new file mode 100644
index 0000000..51db31a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+  "title": "Overview",
+  "ordinal": 167,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md b/corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
new file mode 100644
index 0000000..61dbeb6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D6E46E33-8FF6-48CE-9052-EB7C56EFE245.md
@@ -0,0 +1,5 @@
+# Overview
+
+In many situations, organizations deploy virtual machines in proxy restricted environments for things such as PCI Compliance, or just general security. As a result of this VM Essentials provides out of the box support for proxy connectivity. Proxy authentication support is also provided with both Basic Authentication capabilities as well as NTLM for Windows Proxy environments. VM Essentials is even able to configure virtual machines it provisions to utilize these proxies by setting up the operating systems proxy settings directly (restricted to cloud-init based Linux platforms for now, but can also be done on windows based platforms in a different manner).
+
+To get started with Proxies, it may first be important to configure the VM Essentials appliance itself to have access to proxy communication for downloading service catalog images. To configure this, visit the Administration > Settings page where a section labeled “Proxy Settings” is located. Fill in the relevant connection info needed to utilize the proxy. It may also be advised to ensure that the Linux environment’s `http_proxy`, `https_proxy`, and no\_proxy are set appropriately.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json b/corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
new file mode 100644
index 0000000..cb010a8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+  "title": "Storage",
+  "ordinal": 365,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md b/corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
new file mode 100644
index 0000000..dcc1390
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
@@ -0,0 +1,5 @@
+# Storage
+
+**Subtopics**  
+
+- **[HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json b/corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
new file mode 100644
index 0000000..9df73a6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+  "title": "Provisioning with Proxies",
+  "ordinal": 170,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning with Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+        "clustering_title": "Provisioning with Proxies"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9",
+        "clustering_title": "Provisioning with Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md b/corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
new file mode 100644
index 0000000..ef3dff8
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D8093DE3-D1E8-4963-866A-8A9E7E02CFB9.md
@@ -0,0 +1,5 @@
+# Provisioning with Proxies
+
+Proxy configurations can vary from operating system to operating system and in some cases it is necessary for these to be configured in the blueprint as a prerequisite. In other cases it can also be configured automatically. Mostly with the use of cloud-init (which all of our out of the box service catalog utilizes on all clouds). When editing/creating a cloud there is a setting for “Provisioning Proxy” in “Provisioning Options”. If this proxy is set, VM Essentials will automatically apply these proxy settings to the guest operating system.
+
+Overriding proxy settings can also be done on the Network record. Networks (or subnets) can be configured in Infrastructure  >  Networks or on the Networks tab of the relevant Cloud detail page. Here, a proxy can also be assigned as well as additional options like the No Proxy rules for proxy exceptions.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json b/corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
new file mode 100644
index 0000000..6d75732
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+  "title": "Initial Backups Setup",
+  "ordinal": 205,
+  "parent_title": "Backups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.html",
+  "topic_cluster": {
+    "clustering_title": "Initial Backups Setup",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+        "clustering_title": "Initial Backups Setup"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D",
+        "clustering_title": "Initial Backups Setup"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md b/corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
new file mode 100644
index 0000000..cfffc6b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-D94ACFB5-D9ED-4AD0-A102-6B0164C88B6D.md
@@ -0,0 +1,8 @@
+# Initial Backups Setup
+
+Global Backup settings (Administration > Settings > Backups), Storage Providers (Infrastructure > Storage) and Execution Schedules (Library > Automation > Execute Scheduling) should be configured prior to creating backups. Global backup settings are where scheduled backups can be globally enabled or disabled and certain global backup default settings can be configured. Storage providers include local and remote configured storage locations that can be used as backup targets. Execution schedules are timed intervals at which individual automated backup jobs will run. See the next two sections for full details on global backup settings and configuring execution schedules. See VM Essentials UI [storage documentation](https://docs.morpheusdata.com/en/latest/infrastructure/storage/storage.html) for more information about configuring local and remote storage targets and/or integrating with third party storage providers.
+
+**Subtopics**  
+
+- **[Global Backups Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-008AF6CD-E219-4D76-B175-B763E5C397CE.html)**
+- **[Execution Schedules](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json b/corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
new file mode 100644
index 0000000..68877f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+  "title": "Configuring Virtual Images",
+  "ordinal": 72,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md b/corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
new file mode 100644
index 0000000..aa2b21c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
@@ -0,0 +1,6 @@
+# Configuring Virtual Images
+
+**Subtopics**  
+
+- **[System Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-6549D43B-D0BB-4416-9771-AF11F387B629.html)**
+- **[User Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-43371F39-2265-4EA1-BC6D-A4BF96C47D87.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json b/corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
new file mode 100644
index 0000000..97755ea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+  "title": "Alarms (dashboard)",
+  "ordinal": 10,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.html",
+  "topic_cluster": {
+    "clustering_title": "Alarms (dashboard)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+        "clustering_title": "Alarms (dashboard)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96",
+        "clustering_title": "Alarms (dashboard)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md b/corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
new file mode 100644
index 0000000..47a8563
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DA572F5F-F68F-4A2B-8E24-1596DED8CD96.md
@@ -0,0 +1,3 @@
+# Alarms (dashboard)
+
+The most recent five Alarms are displayed here and the user may link through to the resource which triggered the Alarm. For the complete list of Alarms and more information on each Alarm navigate to Operations > Activity > Alarms
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json b/corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
new file mode 100644
index 0000000..cca658d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+  "title": "Viewing and Assigning Hardware Devices",
+  "ordinal": 134,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing and Assigning Hardware Devices",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md b/corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
new file mode 100644
index 0000000..a3dba77
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
@@ -0,0 +1,23 @@
+# Viewing and Assigning Hardware Devices
+
+Hardware Devices are surfaced at the Host detail level and the VM (server) detail level through a Devices tab. The Host detail will show all attached hardware devices and their current status: Attached (to the host), detached (from the host), or assigned (to a VM). The VM detail will show only hardware devices currently attached to that VM. To begin consuming hardware devices with HVM Cluster VMs, look again at the list in the Devices tab on the Host detail page. Detach a piece of hardware from the host using the ACTIONS dropdown for that piece of hardware. As shown in the screenshot below, DETACH DEVICE is selected for a USB device.
+
+![../../_images/detachDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-A94BDC5A-C89C-426E-9EF6-2914BC84AC21-high.png)
+
+Once detached, the status of the device is changed to “Detached” (see screenshot below) and the device is available for consumption by VMs running on this host.
+
+![../../_images/deviceDetached.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-34E14A70-071B-4A63-BD76-5D0A1261BC20-high.png)
+
+To assign the hardware to a specific VM, click the ACTIONS dropdown once again for the now-detached hardware. Now, click ASSIGN DEVICE.
+
+![../../_images/assignDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-443A34ED-8373-4AB9-9F26-730FF70DDD3C-high.png)
+
+Within the ASSIGN DEVICE modal that will appear, select the server for device assignment and click EXECUTE.
+
+![../../_images/assignToServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-F76B03BD-5880-4AC2-8B3D-98537D873BDE-high.png)
+
+The icon and status for the device in the hardware list has now changed to “Assigned.” If we then open a console session with this VM, we can see the USB device is assigned successfully and is usable by the guest OS.
+
+![../../_images/vmConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-C1FCF142-72C3-4E92-9EBB-6277EC6DD1AA-high.png)
+
+The same process can be used to detach and assign GPU or NVME devices.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json b/corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
new file mode 100644
index 0000000..65fa969
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+  "title": "User Settings",
+  "ordinal": 255,
+  "parent_title": "Users",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md b/corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
new file mode 100644
index 0000000..e5ee51f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DB94D057-9C2E-4BD2-A770-1A1EE13094AE.md
@@ -0,0 +1,3 @@
+# User Settings
+
+Additional settings for a User can be found in the User Settings section, including a user photo, API access, two-factor authentication settings, default Groups and Clouds, and more. User Settings is accessed by clicking on the name of the User in the upper-right corner of the application window and selecting “User Settings.” See the dedicated section on User Settings elsewhere in this documentation for a more in-depth description of User Settings.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json b/corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
new file mode 100644
index 0000000..6534838
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+  "title": "Monitoring the Cluster",
+  "ordinal": 121,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md b/corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
new file mode 100644
index 0000000..78d4045
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
@@ -0,0 +1,14 @@
+# Monitoring the Cluster
+
+With the server provisioned and a workload running, take a look at the monitoring and actions capabilities on the cluster detail page (Infrastructure > Clusters, then click on the new HVM cluster). View cluster performance and resource usage (Summary and Monitoring tabs), drill into individual hosts (Hosts tab), see individual workloads (VMs tab), and more.
+
+**Subtopics**  
+
+- **[Moving Workloads Between Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B6CC596C-034A-461E-9136-BE7AC57B9FDF.html)**
+- **[Adding hosts](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.html)**
+- **[Maintenance Mode](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-967D7E5A-D701-4580-BFCB-0EB3588D2725.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html)**
+- **[vCPU Placement](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html)**
+- **[Host Hardware Sensor Data Collection](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html)**
+- **[Failover](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-1E9B2F0E-E670-4103-AA64-FEFDBDBD516E.html)**
+- **[Adding an NFS Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9CB7CEE4-C724-448E-822A-75F155B88EAC.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json b/corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
new file mode 100644
index 0000000..8d3d217
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+  "title": "Email Settings",
+  "ordinal": 269,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.html",
+  "topic_cluster": {
+    "clustering_title": "Email Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+        "clustering_title": "Email Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336",
+        "clustering_title": "Email Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md b/corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
new file mode 100644
index 0000000..11fefe0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.md
@@ -0,0 +1,23 @@
+# Email Settings
+
+In this section, you can configure an SMTP server for email notification delivery. You will need to provide VM Essentials the following information, your mail server systems administrator can assist you in filling these fields and with the preferred encryption method.
+
+- From Address
+- SMTP Server
+- SMTP Port
+- SSL Enabled
+- TLS Encryption
+- SMTP User
+- SMTP Password
+
+We recommend that you add the VM Essentials server to your SMTP whitelist as well as using user authentication as an additional security measure.
+
+Once you have added your SMTP server information into VM Essentials, scroll down to the bottom of the page and press the blue SAVE button which can be found under the Enabled Clouds section.
+
+When you have saved your SMTP server settings in the VM Essentials appliance you will then need to restart the UI. To restart the morpheus-ui, connect to your VM Essentials server via SSH and run the below command:
+
+`sudo morpheus-ctl restart morpheus-ui`
+
+IMPORTANT
+
+If you do not restart morpheus-ui, the notifications will not be sent. Please note it can take up to three minutes for the UI to become reachable again.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json b/corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
new file mode 100644
index 0000000..5f70a2f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+  "title": "Provisioning",
+  "ordinal": 276,
+  "parent_title": "Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md b/corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
new file mode 100644
index 0000000..12455af
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
@@ -0,0 +1,11 @@
+# Provisioning
+
+**Subtopics**  
+
+- **[Provisioning Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5E442E1F-D996-4863-BA47-1EE76E07A12C.html)**
+- **[Cloud-Init Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3D27BE17-47C9-476C-AD13-DD516697F862.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A5F5433C-0F21-4877-BFC6-522D421A1842.html)**
+- **[Library Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.html)**
+- **[PXE Boot Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B94BC2CB-8504-41C6-8848-512529EEE941.html)**
+- **[App Blueprint Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8585CD8C-F26B-4BDF-BAD2-40E8522C9238.html)**
+- **[Terraform Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A326D9A4-3697-4635-9EE9-6B3DE7B6D87C.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json b/corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
new file mode 100644
index 0000000..449d750
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+  "title": "HPE Aruba CX DSS",
+  "ordinal": 356,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Aruba CX DSS",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md b/corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
new file mode 100644
index 0000000..85e536b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
@@ -0,0 +1,12 @@
+# HPE Aruba CX DSS
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0CA68FCD-5F9B-47CE-954A-5A2176286C79.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-30D9F5F5-7572-4440-8B31-9372D7CE352D.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.html)**
+- **[Adding HPE Aruba CX DSS Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-A1173E96-4BDD-4978-86FE-E6AB5BACE94D.html)**
+- **[Manage Security Groups and Rules in Morpheus](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-B7C568F0-6A6B-4DD5-954F-A8A66D5FF701.html)**
+- **[Create HPE ANW DSS Port Group Network](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-0F4C809D-5F7A-4CA1-AA7E-3C6C7E68B81F.html)**
+- **[Delete HPE ANW DSS Port Group Network](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-7D80BD98-F855-4690-AC44-6BA192EC1E53.html)**
+- **[View HPE Aruba CX DSS Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4DBEF77C-6A67-4F5F-900D-2C5AE8A53571.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json b/corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
new file mode 100644
index 0000000..649f51a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+  "title": "vCPU Placement",
+  "ordinal": 126,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html",
+  "topic_cluster": {
+    "clustering_title": "vCPU Placement",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md b/corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
new file mode 100644
index 0000000..045999e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
@@ -0,0 +1,28 @@
+# vCPU Placement
+
+vCPU placement settings relate to vCPU placement within the physical topology of the CPU. Since a vCPU is just a schedulable thread the hypervisor maps onto physical cores, we can create performance increases through smart scheduling. A simplified CPU topology might look something like this:
+
+```
+```
+Socket  
+ └── NUMA node  
+     └── Core  
+         └── Threads (SMT / Hyper-Threading)
+```
+```
+
+As you can see from the diagram above, multiple physical cores can reside within the same NUMA node. Physical CPU cores within the same NUMA node share the same region of the L3 cache and local memory access. By scheduling vCPUs making up a single VM to cores within the same NUMA node, we can avoid the performance penalties associated with crossing NUMA boundaries and accessing remote memory locations.
+
+HVM Clusters offer three vCPU placement settings. The default setting is **Unmanaged**. Clusters with unmanaged vCPU placement will make no special effort to schedule vCPUs within the same NUMA region. Next is **Region**. Clusters with this vCPU placement will attempt to schedule vCPUs associated with the same VM within the same NUMA region. When flexibility is needed, vCPUs may hop to different physical cores but they will be kept within the same NUMA region. Third is **Pinned**. Clusters with this vCPU placement will also attempt to schedule vCPUS associated with the same VM within the same NUMA region but the vCPUs will remain pinned to same cores. In certain cases, pinning may improve performance and in other cases creating inflexibility may introduce inefficiency.
+
+TIP
+
+Setting **Region** placement is a sensible starting configuration if you don't have a specific reason to choose one of the other two. In internal testing, a 7-10% improvement in prime number generation time was observed with Region pinning versus Unmanaged pinning.
+
+How to Configure vCPU Placement Settings
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. From the Cluster detail page, click Edit
+4. Within the vCPU Placement field, select the desired value. See the paragraphs above for a description of each configuration
+5. Click Save changes
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json b/corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
new file mode 100644
index 0000000..8a58962
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+  "title": "Utilities",
+  "ordinal": 294,
+  "parent_title": "Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.html",
+  "topic_cluster": {
+    "clustering_title": "Utilities",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+        "clustering_title": "Utilities"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178",
+        "clustering_title": "Utilities"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md b/corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
new file mode 100644
index 0000000..84b2aac
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DFC2EF97-82BB-4B0E-B032-26CE5B163178.md
@@ -0,0 +1,16 @@
+# Utilities
+
+System administrators have access to a utilities panel with the following options:
+
+- **Reindex all searchable data:** Execute
+- **Toggle Maintenance Mode:** Enable
+
+NOTE
+
+Maintenance mode cleanly places VM Essentials into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting VM Essentials UI disables maintenance mode.
+
+NOTE
+
+When using VM Essentials in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
+
+A VM Essentials node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json b/corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
new file mode 100644
index 0000000..1dd8750
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+  "title": "Generate Key Pair",
+  "ordinal": 200,
+  "parent_title": "OAuth 2.0 Credentials",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.html",
+  "topic_cluster": {
+    "clustering_title": "Generate Key Pair",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+        "clustering_title": "Generate Key Pair"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D",
+        "clustering_title": "Generate Key Pair"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md b/corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
new file mode 100644
index 0000000..5f86685
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.md
@@ -0,0 +1,17 @@
+# Generate Key Pair
+
+## About this task
+
+To generate a Key Pair:
+
+## Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. After naming the new key pair, VM Essentials will reveal both the public and private key
+
+## Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json b/corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
new file mode 100644
index 0000000..89c84f9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+  "title": "History",
+  "ordinal": 25,
+  "parent_title": "Activity",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.html",
+  "topic_cluster": {
+    "clustering_title": "History",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+        "clustering_title": "History"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8",
+        "clustering_title": "History"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md b/corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
new file mode 100644
index 0000000..2971dae
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-DFFCFAA0-CFE0-433F-ABB4-D05BEFA6E1A8.md
@@ -0,0 +1,15 @@
+# History
+
+The HISTORY section shows process history from Instance processes. This is an aggregate view of the `History` tab contained in each Instance detail page.
+
+![History](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-DE8D2A86-CAB3-4D94-9D4C-83C5FA49585A-high.png)
+
+Processes can be expanded to view all process steps and process history detail including output and errors.
+
+Access to HISTORY is given by the `Operations:Activity` Role permission.
+
+The Logs displayed in Administration > Health > Morpheus Logs are from `/var/log/morpheus/morpheus-ui/current`. These logs show all ui activity and are useful for troubleshooting and auditing.
+
+NOTE
+
+Stack traces in Administration > Health > Morpheus Logs are filtered for VM Essentials services. Complete stack traces can be found in `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json b/corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
new file mode 100644
index 0000000..9569a1d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+  "title": "Key Pairs",
+  "ordinal": 202,
+  "parent_title": "Trust",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html",
+  "topic_cluster": {
+    "clustering_title": "Key Pairs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md b/corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
new file mode 100644
index 0000000..aeed0fe
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
@@ -0,0 +1,20 @@
+# Key Pairs
+
+The key pairs section enables the following actions: Add and Delete key pairs. Key pairs are commonly used by HPE Morpheus VM Essentials for accessing instances via SSH. HPE Morpheus VM Essentials stores key pairs to simplify administration and access across both private and public clouds.
+
+HPE Morpheus VM Essentials only accepts key pairs in PEM format (for example, a private key beginning with `-----BEGIN RSA PRIVATE KEY-----`) and accepts RSA (PKCS#1 or PKCS#8, default), DSA (PKCS#1 or PKCS#8), EC (PKCS#8), and ed25519 (PKCS#8) keys. If you have a key in another format, such as OpenSSH, convert the key:
+
+```
+```
+#No passphrase  
+ssh-keygen -m pem -f /path/to/key  
+#With passphrase  
+ssh-keygen -p -P "old passphrase" -N "new passphrase" -m pem -f path/to/key
+```
+```
+
+**Subtopics**  
+
+- **[Add Existing Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C_2.html)**
+- **[Generate Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9908E99D-69AC-4D1E-8A4D-A55FDAFE4086.html)**
+- **[Delete Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1_2.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json b/corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
new file mode 100644
index 0000000..8bbf43c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+  "title": "Create Instance",
+  "ordinal": 370,
+  "parent_title": "HPE Alletra MP Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.html",
+  "topic_cluster": {
+    "clustering_title": "Create Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+        "clustering_title": "Create Instance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D",
+        "clustering_title": "Create Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md b/corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
new file mode 100644
index 0000000..53ecf94
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E0B9310C-0B93-4BD0-AE57-9CA6432C2C7D.md
@@ -0,0 +1,97 @@
+# Create Instance
+
+## About this task
+
+Create an Instance with the Datastore.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. In the Instances tab, Click + ADD.
+3. In the ADD INSTANCE wizard, provide the following details: 
+
+   - In the Type section, select HPE HVM.
+   - Click Next.
+
+     ![Create Instance Type](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-55F890E0-47C6-4621-9A97-C399B1AD1BB0-high.png)
+   - In the Group tab, provide the following details:
+
+     GROUP:
+     :   Select the group for the instance.
+
+     CLOUD:
+     :   Select the cloud for the instance.
+
+     NAME:
+     :   Enter the name for the instance in VM Essentials.
+
+     ENVIRONMENT:
+     :   Select the environment for the instance.
+   - Click Next.
+
+     ![Create Instance Group](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4EEB766E-54E0-4C82-A60B-59AE6B75D705-high.png)
+   - In the Configure tab, provide the following details:
+
+     LAYOUT:
+     :   Select the Layout for the Instance.
+
+     PLAN:
+     :   Select the Plan for the Instance.
+
+     RESOURCE POOL:
+     :   Select the Resource Pool (Cluster) for the Instance.
+
+     VOLUMES:
+     :   Add one or more Volumes to the Instance. Select the datastore created in the previous section.
+
+     Storage Type
+     :   Select the replication type from the Storage Type drop-down list.
+
+         If you select the `Standard Volume - HPE Alletra LUN` option, the system provisions VMs on a standard Logical Unit Number (LUN).
+
+         If you select the `HPE Alletra LUN - Active Peer Persistence` option, remote copy groups are created, and VMs are replicated across both primary and secondary storage systems.
+
+         For VMs created with the `HPE Alletra LUN - Active Peer Persistence` storage type, Host Proximity is set to `All`, allowing access from both the primary and secondary sites. VMs created with this storage type are automatically added to an Active-Active Peer Persistence (AAPP) replication group.
+
+         NOTE
+
+         VMs and storage volumes are not created if you select a mix of replicated and non-replicated volumes.
+
+     NETWORK:
+     :   Add Networks to the Instance.
+
+     IMAGE:
+     :   Select the Image for the Instance.
+
+     HOST:
+     :   Select the cluster host for the Instance.
+
+     Other configurations may be added as needed.
+
+     ![Create Instance Configure](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-358491C6-43F7-4197-9F53-94D50A1E99F1-high.png)
+   - Click Next.
+   - Add Automation Tasks, if needed
+   - Click Next.
+   - Review the Instance configuration.
+   - Click Complete.![Create Instance - Review](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-22C7AB89-6966-4E4D-8514-6A2FAD489B61-high.png)
+
+## Results
+
+The Instance is now provisioned to the new datastore and is viewable within the Instances (Provisioning > Instances) section.
+
+CAUTION
+
+- Pre-existing host records may prevent successful host creation and provisioning.
+- VM Essentials does not automatically rename hosts created externally.
+- Host names must match on both primary and secondary systems for host proximity to work.
+
+To view the details of volumes or disks for an AAPP Instance provisioning:
+
+1. Navigate to Provisioning > Instances.
+2. In the Instances tab, click the replicated VM to see its details.
+3. Click the Storage > Volumes tab. ![Volume tab](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-0E66529D-3C71-48BF-B797-D866B4A703B4-high.png)
+4. Click Volume Name to see the details, such as Remote Copy Status, Volume Type, Remote Copy Group Status, and Host Sets. ![Volume details](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-331D2A26-6024-4810-9FD1-E0D4BD3253AA-high.png)
+
+   The following volume details screen is displayed for an Instance with non-AAPP storage type: ![Volume details - non-aapp](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4AF2DEA6-B2D8-46F8-B654-E1A46304439C-high.png)
+
+The volume details can also be accessed by navigating to Infrastructure > Storage > Volumes and clicking a volume name.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json b/corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
new file mode 100644
index 0000000..dc760e4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+  "title": "Overview",
+  "ordinal": 139,
+  "parent_title": "Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md b/corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
new file mode 100644
index 0000000..034629a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E1B51387-134E-45BA-A6EB-7D68C8F2C86F.md
@@ -0,0 +1,5 @@
+# Overview
+
+The Networks section is for configuring networks across all Clouds in VM Essentials. Existing networks from Clouds added in VM Essentials will auto-populate in the Networks section.
+
+Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, VM Essentials allows administrators to restrict management of VM Essentials-created Networks through Role permissions.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json b/corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
new file mode 100644
index 0000000..8095475
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+  "title": "User Management Settings",
+  "ordinal": 268,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.html",
+  "topic_cluster": {
+    "clustering_title": "User Management Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+        "clustering_title": "User Management Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7",
+        "clustering_title": "User Management Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md b/corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
new file mode 100644
index 0000000..acf2b22
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.md
@@ -0,0 +1,31 @@
+# User Management Settings
+
+Min Password Length
+:   User passwords must at least be as many characters in length as the entered value
+
+Min Password Uppercase
+:   User passwords must include at least as many uppercase characters as the entered value
+
+Min Password Numbers
+:   User passwords must include at least as many numerals as the entered value
+
+Min Password Symbols
+:   User passwords must include at least as many special characters as the entered value
+
+Session Expires (Minutes)
+:   A user session is forcibly logged out after the entered number of minutes of inactivity
+
+Session Warning (Minutes)
+:   A pop-up warning is shown to the user when they have been inactive for the number of minutes entered. Example: If sessions are set to expire after 90 minutes, warn the user after 60 minutes if you intend to provide 30 minutes advance warning
+
+Expire Password After (Days)
+:   User account passwords will expire after the entered number of days. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User After Attempts (Number of Attempts)
+:   Disable a User account after a specified number of failed login attempts. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User If Inactive For (Days)
+:   Disable a User account if inactive for the entered number of days. The User will not be able to log into the appliance again until another User with sufficient rights enables the account. Enter 0 or leave the field empty to opt out of this feature.
+
+Send warning email before deactivating (Days)
+:   Enter the number of days prior to account deactivation that a warning email should be sent. For example, enter “5” to warn the User when they are five days short of the deactivation time entered in the prior field. Enter 0 or leave the field empty to opt out of this feature.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json b/corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
new file mode 100644
index 0000000..bce3d2d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+  "title": "Amazon S3 Buckets",
+  "ordinal": 180,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.html",
+  "topic_cluster": {
+    "clustering_title": "Amazon S3 Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+        "clustering_title": "Amazon S3 Buckets"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3",
+        "clustering_title": "Amazon S3 Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md b/corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
new file mode 100644
index 0000000..2308261
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E29A25C3-FD64-4935-8BC8-7F1FE3245CC3.md
@@ -0,0 +1,77 @@
+# Amazon S3 Buckets
+
+## About this task
+
+To Add an Amazon S3 Storage Bucket:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Amazon S3 from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in VM Essentials.
+
+   ACCESS KEY
+   :   AWS IAM Access Key
+
+   SECRET KEY
+   :   AWS IAM Secret Key
+
+   BUCKET NAME
+   :   Enter existing S3 Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   CREATE BUCKET
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created. If enabled, select an AWS Region to create the Bucket in.
+
+   ENDPOINT URL
+   :   Optional endpoint URL if pointing to an object store other than amazon that mimics the Amazon S3 APIs.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+## Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json b/corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
new file mode 100644
index 0000000..9929473
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+  "title": "Favorites",
+  "ordinal": 9,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.html",
+  "topic_cluster": {
+    "clustering_title": "Favorites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+        "clustering_title": "Favorites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12",
+        "clustering_title": "Favorites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md b/corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
new file mode 100644
index 0000000..0baa217
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E2AA01BB-BACC-4C5B-8B8E-1C7BEEDF6F12.md
@@ -0,0 +1,3 @@
+# Favorites
+
+Any Instances you’ve “favorited” will appear here along with the Instance name, type, and IP address
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json b/corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
new file mode 100644
index 0000000..816a6b4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+  "title": "Integrate a Bucket or File Share",
+  "ordinal": 310,
+  "parent_title": "Backing Up and Restoring the HPE Morpheus VM Essentials Manager",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.html",
+  "topic_cluster": {
+    "clustering_title": "Integrate a Bucket or File Share",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+        "clustering_title": "Integrate a Bucket or File Share"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069",
+        "clustering_title": "Integrate a Bucket or File Share"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md b/corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
new file mode 100644
index 0000000..b10bce6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E32D92B2-8DB3-42C3-982C-7E9D88231069.md
@@ -0,0 +1,19 @@
+# Integrate a Bucket or File Share
+
+## About this task
+
+When configuring a HPE Morpheus Enterprise appliance backup, a storage location is selected. If you already have the destination bucket or file share integrated with HPE Morpheus Enterprise, skip to the next section. To integrate a new storage bucket, follow the steps below:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage
+2. Click on the Buckets or File Shares tab depending on your chosen storage type
+3. Click + ADD
+4. Select the appropriate bucket or file share type
+5. Complete the required fields and click SAVE CHANGES
+
+## Results
+
+NOTE
+
+Additional guidance on integrating each of the supported bucket and file share types can be found in [storage](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-4885ECA7-94F5-481E-A2FE-A433FAA899C8.html) documentation.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json b/corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
new file mode 100644
index 0000000..08670bf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+  "title": "Integrations",
+  "ordinal": 256,
+  "parent_title": "Administration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md b/corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
new file mode 100644
index 0000000..255eb06
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E3A970B8-01F6-4368-9D06-541B2BCE30D9.md
@@ -0,0 +1,15 @@
+# Integrations
+
+The Integrations allows administrators to manage platform extensions and packages. Using Integrations, you can add, update, and remove plugins and packages to extend the functionality and standardize configurations.
+
+To access the Integrations, click Administration > Integrations.
+
+The Integrations page contains the following tabs:
+
+- Plugins
+- Packages
+
+**Subtopics**  
+
+- **[Plugins](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-45D07344-870A-4CB7-84D9-4AF78C151B70.html)**
+- **[Packages](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json b/corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
new file mode 100644
index 0000000..e9e8802
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+  "title": "Integrations",
+  "ordinal": 171,
+  "parent_title": "Network",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md b/corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
new file mode 100644
index 0000000..23ae4ba
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
@@ -0,0 +1,6 @@
+# Integrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-CAD6A263-1895-4FEB-9B5E-73B02B1558EC.html)**
+- **[Scoping Services](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-02679208-A796-4A58-80AC-33DCF6A4899F.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json b/corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
new file mode 100644
index 0000000..24be561
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+  "title": "Alarms",
+  "ordinal": 24,
+  "parent_title": "Activity",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.html",
+  "topic_cluster": {
+    "clustering_title": "Alarms",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+        "clustering_title": "Alarms"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19",
+        "clustering_title": "Alarms"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md b/corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
new file mode 100644
index 0000000..b792d6e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E4F3DF9C-1873-4893-BE81-D85015D67F19.md
@@ -0,0 +1,7 @@
+# Alarms
+
+The Alarms section shows Operation notifications from Cloud and other Service Integrations. Cloud and other Service Integration Alarms are not generated by HPE Morpheus VM Essentials Software but synced and displayed for visibility in HPE Morpheus VM Essentials Software.
+
+For the complete list of Alarms and more information on each Alarm, navigate to Operations > Activity > Alarms.
+
+![Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-444E2530-12E2-439A-A1C7-EED4D7F91D38-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json b/corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
new file mode 100644
index 0000000..df20586
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+  "title": "Usage",
+  "ordinal": 331,
+  "parent_title": "VMware Permissions",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.html",
+  "topic_cluster": {
+    "clustering_title": "Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+        "clustering_title": "Usage"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8",
+        "clustering_title": "Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md b/corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
new file mode 100644
index 0000000..4de7e18
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E543FF33-06CE-4547-BC37-5B2AD091D8A8.md
@@ -0,0 +1,18 @@
+# Usage
+
+vCenter
+:   - Non-Propagating
+
+Datacenter
+:   - Non-Propagating
+
+Cluster
+:   - Non-Propagating
+
+Host
+:   - Non-Propagating
+
+Datastore/Datastore Cluster
+:   - Propagating
+
+After completing the above steps, all VMware Cloud functionality should be available in VM Essentials without running into permissions errors.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json b/corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
new file mode 100644
index 0000000..c6e6e3b
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+  "title": "VM Provision Steps",
+  "ordinal": 28,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.html",
+  "topic_cluster": {
+    "clustering_title": "VM Provision Steps",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+        "clustering_title": "VM Provision Steps"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526",
+        "clustering_title": "VM Provision Steps"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md b/corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
new file mode 100644
index 0000000..9ac9fd5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E5BD72D4-D17D-4B2D-AE72-CB13FF3B9526.md
@@ -0,0 +1,48 @@
+# VM Provision Steps
+
+While many things can happen during an individual provisioning process, the basic order is:
+
+- Look for the Virtual Image
+
+  VM Essentials will check if the Virtual Image set on the Node Type or selected from a list of images during provisioning is already available to the HVM cluster or to a vCenter Cloud target. If not and it is an uploaded or local image, VM Essentials will attempt to upload the image to the HVM cluster or vCenter target.
+
+  **Upload Image**
+
+  For uploaded or local images that do not exist in the target, VM Essentials will need to upload the Image. Ensure the Virtual Image is valid for the target technology, the image meets the target upload requirements, and VM Essentials has network access and permissions to upload the image.
+
+  NOTE
+
+  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+  **Clone Image**
+
+  Once the Image is confirmed available in the target cloud, VM Essentials will clone the Image to the target Datastore.
+
+  NOTE
+
+  The target host must have access to the target Datastore of the Image
+- Reconfigure Image
+
+  Once cloned, VM Essentials will resize the Image based off provisioning parameters
+- Cloud-init (if enabled)
+  :   Attached cloud-init iso
+      :   When using cloud-init, VM Essentials will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.
+
+      VM Tools
+      :   VM Essentials will run guest customizations via VMware VM Tools, including network config when assigning static IP addresses.
+- Wait for Power On status and Network info
+
+  VM Essentials will wait to hear back from the target that the VM has successfully started and has an IP address.
+
+  NOTE
+
+  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, VM Essentials will skip waiting for network.
+- Finalize
+
+  By default, this step will include Agent installation.
+
+  IMPORTANT
+
+  If the VM is stuck in finalize for long periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.
+
+  If agent installation is not possible or is not desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json b/corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
new file mode 100644
index 0000000..e403602
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+  "title": "Target Options",
+  "ordinal": 59,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.html",
+  "topic_cluster": {
+    "clustering_title": "Target Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+        "clustering_title": "Target Options"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5",
+        "clustering_title": "Target Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md b/corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
new file mode 100644
index 0000000..e03bb7a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E6B3CF7A-7C08-43CD-876D-551434CDC9B5.md
@@ -0,0 +1,7 @@
+# Target Options
+
+When creating a Task, users can select a target to perform the execution. Some Task types allow for any of the three execution targets listed below and some will limit the user to two or just one. The table in the next section lists the available execution targets for each Task type.
+
+- **Resource:** A VM Essentials-managed Instance or server is selected to execute the Task
+- **Local:** The Task is executed by the VM Essentials appliance node
+- **Remote:** The user specifies a remote box which will execute the Task
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json b/corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
new file mode 100644
index 0000000..188f0e0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+  "title": "Adding hosts",
+  "ordinal": 123,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.html",
+  "topic_cluster": {
+    "clustering_title": "Adding hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+        "clustering_title": "Adding hosts"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56",
+        "clustering_title": "Adding hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md b/corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
new file mode 100644
index 0000000..7044493
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E6E80A16-46F6-40B9-A99C-DBEDF044BD56.md
@@ -0,0 +1,11 @@
+# Adding hosts
+
+The process of adding hosts to a pre-existing cluster is very similar to the process of provisioning the cluster initially. The requirements for the new worker node will be identical to the nodes initially added when the cluster was first provisioned. See the earlier sections in this guide for additional details on configuring the worker nodes.
+
+To add the host, begin from the Cluster detail page (selected from the list at Infrastructure > Clusters). From the Cluster detail page, click ACTIONS and select “Add Worker”. Configurations required are the same as those given when the cluster was first created. Refer to the section above on “Provisioning the Cluster” for a detailed description of each configuration.
+
+Once VM Essentials has completed its configuration scripts and joined the new worker node to the cluster, it will appear in a ready state within the Hosts tab of the Cluster detail page. When provisioning workloads to this Cluster in the future, the new node will be selectable as a target host for new Instances. It will also be an available target for managing placement of existing VMs running on the cluster.
+
+NOTE
+
+It’s useful to confirm all scripts related to creating the new host and joining the new host to the cluster completed successfully. To confirm, navigate to the detail page for the new host (Infrastructure > Clusters > Selected Cluster > HostsTab > SelectedHost) and click on the History tab. Confirm all scripts, even those run on the pre-existing hosts, completed successfully as it’s possible the new host was added successfully (green status) but failed in joining the cluster. When such a situation occurs it may appear adding the new host was successful though it will not be possible to provision workloads onto it due to not joining the cluster successfully.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json b/corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
new file mode 100644
index 0000000..506a173
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+  "title": "Overview",
+  "ordinal": 214,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md b/corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
new file mode 100644
index 0000000..a591a1c
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E8CD3D0A-3BA1-4953-817D-C6C74B40B43C.md
@@ -0,0 +1,7 @@
+# Overview
+
+Cypher at its core is a secure Key/Value store. But what makes Cypher useful is the ability to securely store or generate credentials to connect to your Instances. Not only are these credentials encrypted but by using Cypher you don’t have to burn in connection credentials between Instances into your apps.
+
+Cypher keys can be revoked, either through lease timeouts or manually. So, even if somebody were to gain access to your keys you could revoke access to the keys and generate new ones for your applications.
+
+Keys can have different behaviors depending on the specified mountpoint.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json b/corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
new file mode 100644
index 0000000..6824dfb
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+  "title": "Instance Status",
+  "ordinal": 11,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Status",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+        "clustering_title": "Instance Status"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A",
+        "clustering_title": "Instance Status"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md b/corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
new file mode 100644
index 0000000..a76f11f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-E9CEABBF-F8C7-41E0-97A0-211B1967124A.md
@@ -0,0 +1,3 @@
+# Instance Status
+
+The total number of Instances is listed along with a pie chart showing the statuses of each. Hover over each section of the pie chart to see the total number and percentage of Instances in that state. States may include running, stopped, provisioning, and more
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json b/corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
new file mode 100644
index 0000000..ba3fd08
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+  "title": "OAuth 2.0 Credentials",
+  "ordinal": 198,
+  "parent_title": "Trust",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.html",
+  "topic_cluster": {
+    "clustering_title": "OAuth 2.0 Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+        "clustering_title": "OAuth 2.0 Credentials"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB",
+        "clustering_title": "OAuth 2.0 Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md b/corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
new file mode 100644
index 0000000..6b337d3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EB317455-AAFD-4465-8961-6E7C13B48CCB.md
@@ -0,0 +1,26 @@
+# OAuth 2.0 Credentials
+
+VM Essentials supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
+
+To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
+
+- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
+- **NAME:** A name for the credential set in VM Essentials
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **GRANT TYPE:** Client Credentials or Password Credentials
+- **ACCESS TOKEN URL:** The authorization server’s token endpoint
+- **CLIENT ID:** The client ID for an app registered with the target service
+- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
+- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
+- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
+- **SCOPE:** The scope of access requested to the target resource
+- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how VM Essentials should issue the token received in requests to the target resource
+
+Once done, click ADD CREDENTIALS.
+
+**Subtopics**  
+
+- **[Add Existing Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-3BCC85EA-1CBD-405F-AEFC-844BF2D9FE6C.html)**
+- **[Generate Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DFC73E7E-71E9-4FF1-A338-9944A8413A9D.html)**
+- **[Delete Key Pair](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-5D0F2D33-623B-4AA3-A767-48980AA8A4E1.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json b/corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
new file mode 100644
index 0000000..92760c2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+  "title": "Manage Permissions",
+  "ordinal": 193,
+  "parent_title": "Storage",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.html",
+  "topic_cluster": {
+    "clustering_title": "Manage Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+        "clustering_title": "Manage Permissions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3",
+        "clustering_title": "Manage Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md b/corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
new file mode 100644
index 0000000..35410f4
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EC246C7B-ADD1-4239-8439-5D0AFAE05CA3.md
@@ -0,0 +1,13 @@
+# Manage Permissions
+
+From this view, users can manage permissions for any data store synced from integrated Clouds. This includes setting which Groups have access to the data store. To edit data store permissions:
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click ACTIONS > Edit
+- **Groups:** Select “all” Groups or select specific Groups which should have access to the data store
+- **Active:** When marked, the data store is active and available for provisioning
+- Click SAVE CHANGES
+
+**Subtopics**  
+
+- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json b/corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
new file mode 100644
index 0000000..54f0631
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+  "title": "Clouds",
+  "ordinal": 90,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html",
+  "topic_cluster": {
+    "clustering_title": "Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md b/corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
new file mode 100644
index 0000000..3599bc2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
@@ -0,0 +1,8 @@
+# Clouds
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-60AD4FB6-CAF9-4D70-A299-D67E4967345A.html)**
+- **[Creating Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-17EE6294-53E4-41F2-B3DE-8509268CE8AE.html)**
+- **[Cloud Detail View](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-09DFA0EB-D5E4-48B8-A95D-F47F2F627B57.html)**
+- **[Deleting Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-69CE737F-F442-4C04-8B1A-8881930B69AE.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json b/corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
new file mode 100644
index 0000000..358d572
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+  "title": "Elevating to HPE Morpheus Enterprise",
+  "ordinal": 4,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.html",
+  "topic_cluster": {
+    "clustering_title": "Elevating to HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+        "clustering_title": "Elevating to HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713",
+        "clustering_title": "Elevating to HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md b/corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
new file mode 100644
index 0000000..a4fd12a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ECCA4FDD-37C8-45CE-A71F-C6E73B3BA713.md
@@ -0,0 +1,109 @@
+# Elevating to HPE Morpheus Enterprise
+
+This section of the guide goes over the process for upgrading a HPE Morpheus VM Essentials Software appliance to a HPE Morpheus Enterprise Software appliance. HPE Morpheus VM Essentials and HPE Morpheus Enterprise are essentially the same product with HPE Morpheus VM Essentials focused specifically on management and consumption of HVM clusters and HPE Morpheus Enterprise adding on support for many other public and private Cloud types with a richer orchestration and automation experience (in addition to all features included with HPE Morpheus VM Essentials). HPE Morpheus Enterprise requires separate licensing, reach out to your account manager if you’re unsure which licensing entitlements you can access. This guide is intended for HPE Morpheus VM Essentials administrators to upgrade their existing appliances and assumes a level of comfort with the Linux command line and the version upgrade process for HPE Morpheus VM Essentials and/or HPE Morpheus Enterprise. After upgrading, refer to HPE Morpheus Enterprise [documentation](https://www.hpe.com/support/morpheus-enterprise-documentation-latest) for use guides to consuming the full HPE Morpheus Enterprise feature set.
+
+## Prerequisites
+
+- HPE Morpheus VM Essentials manager version 8.0.1+
+- A bucket integrated with HPE Morpheus VM Essentials manager which can house an appliance database backup
+- The HPE Morpheus Enterprise upgrade package (version 8.0.4+)
+- A HPE Morpheus Enterprise license to add following the upgrade to enable the full feature set
+
+## Back Up the Appliance
+
+Start by taking a fresh backup of the appliance database. View the appliance backup job by navigating to Backups > Jobs. As in the screenshot, there should be a backup job named “Morpheus Appliance.” If an appliance backup job is not shown, enable the “Backup Appliance” setting within global settings (Administration > Settings > Backups).
+
+![../_images/upgradeCheckBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-983B614F-468D-405F-8143-085388C6B629-high.png)
+
+Click Run Now and wait for a new green checkmark to appear indicating a new run of the backup job was successful.
+
+## Package Installation
+
+Upgrading the HPE Morpheus VM Essentials manager to a HPE Morpheus Enterprise appliance is as simple as installing the HPE Morpheus Enterprise package over the existing HPE Morpheus VM Essentials package in a process very similar to version upgrades you may have done in the past. First, download the HPE Morpheus Enterprise `.deb` package. The download URL shown below is a placeholder, reach out to your account manager if you’re unsure where to find the download URL for the latest package.
+
+```
+```
+wget https://url.to.morpheus-appliance_x.x.x-x.deb
+```
+```
+
+Next, stop the HPE Morpheus VM Essentials UI.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui
+```
+```
+
+Install the HPE Morpheus Enterprise package and force it to overwrite.
+
+```
+```
+dpkg -i --force-overwrite morpheus-appliance_x.x.x-x.deb
+```
+```
+
+Wait for the installation to complete. There will be warnings about conflicts which may be safely ignored. When installation is complete, you will see a message similar to the screenshot below:
+
+![../_images/upgradeFinishInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-967FDDAE-077D-492D-A9E6-27259A79FCCB-high.png)
+
+Now, remove the HPE Morpheus VM Essentials package.
+
+```
+```
+sudo apt-get remove -y hpe-vm-essentials
+```
+```
+
+Following removal, restart any recommended services if prompted.
+
+![../_images/upgradeRemoveVme.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-DCBE5796-22E4-4207-B179-DD8B37BA91EF-high.png)
+
+We must now clean up OpenSearch directories. Currently, HPE Morpheus Enterprise uses ElasticSearch while HPE Morpheus VM Essentials manager uses OpenSearch. Migration through snapshots is not supported due to this incompatibility. In general, OpenSearch and ElasticSearch contain VM performance metrics. This data can be considered ephemeral and safely deleted as the default retention is only 30 days. HPE Morpheus Enterprise is planned to migrate to OpenSearch in the future and at that point, this cleanup step will not be required and metrics will persist across an upgrade to HPE Morpheus Enterprise. Remove the following directories:
+
+```
+```
+rm -rf /var/run/morpheus/opensearch  
+rm -rf /opt/morpheus/service/opensearch
+```
+```
+
+Next, run the reconfigure command. This will configure ElasticSearch for use with the upgraded appliance.
+
+```
+```
+sudo morpheus-ctl reconfigure
+```
+```
+
+Once the reconfigure is complete, make sure all HPE Morpheus Enterprise services are started
+
+```
+```
+sudo morpheus-ctl status
+```
+```
+
+If any services need started, use the following command:
+
+```
+```
+sudo morpheus-ctl start {service name}
+```
+```
+
+You can watch the logs to see when the UI comes back up:
+
+```
+```
+sudo morpheus-ctl tail morpheus-ui
+```
+```
+
+When the Morpheus ASCII logo appears, you should be able to reach the UI from a web browser.
+
+## Upgrading the License
+
+Now that HPE Morpheus Enterprise UI is reachable, the license must be upgraded. Navigate to Administration > Settings > License where you’ll see a field to paste in your license key. Once again, contact your account manager if you have questions on accessing your license key. Finally, make sure you select the appropriate option of either stacking the license onto an existing license or replacing it. Then, click Update.
+
+At this point, the process is complete. Now that the full Morpheus feature set is unlocked, refer to Morpheus [documentation](https://support.hpe.com/connect/s/product?language=en_US&kmpmoid=1014895562&tab=manuals&cep=on) going forward.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json b/corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
new file mode 100644
index 0000000..d20e2ff
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+  "title": "Local Virtual Images",
+  "ordinal": 31,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.html",
+  "topic_cluster": {
+    "clustering_title": "Local Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+        "clustering_title": "Local Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA",
+        "clustering_title": "Local Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md b/corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
new file mode 100644
index 0000000..4188c74
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.md
@@ -0,0 +1,11 @@
+# Local Virtual Images
+
+A Local Virtual Image means it has been uploaded to VM Essentials. To provision, VM Essentials will need to upload the image to the provisioning target upon first provision.
+
+- Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and VM Essentials has network access and permissions to upload the image.
+
+NOTE
+
+When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the VM Essentials Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+Once a local Virtual Image has been uploaded to a provisioning target, subsequent provisions will use the image local to the target instead of uploading again as long as the copied image is still available.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json b/corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
new file mode 100644
index 0000000..f67b8a0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+  "title": "Preferences",
+  "ordinal": 302,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html",
+  "topic_cluster": {
+    "clustering_title": "Preferences",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md b/corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
new file mode 100644
index 0000000..e7f248e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
@@ -0,0 +1,8 @@
+# Preferences
+
+- **Default Group:** Sets the default Group selection when provisioning
+- **Default Cloud:** Sets the default Cloud selection when provisioning
+- **Default Persona:** Sets the default Persona used when logging in
+- **Default Locale:** Sets the user’s preferred language and region, this setting will override the global locale for the individual user
+
+![../../_images/user_settings_preferences_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-1FDED76C-74B0-4FCA-A922-28AD152EC59A-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json b/corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
new file mode 100644
index 0000000..f6d99dc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+  "title": "Prerequisites",
+  "ordinal": 359,
+  "parent_title": "HPE Aruba CX DSS",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md b/corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
new file mode 100644
index 0000000..225d649
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-ED27B01F-2AC3-41B2-A7B8-45546B58C88D.md
@@ -0,0 +1,24 @@
+# Prerequisites
+
+The following requirements must be met to deploy and configure the HPE Aruba CX DSS Network plugin in VM Essentials
+
+- Aruba CX 10000 series switches
+
+  - At least two Aruba CX 10000 switches are configured
+  - VSX and KeepAlive are configured
+  - Switches are connected to the upstream network
+- Pre-existing HVM cluster
+
+  - Ensure all hosts within the HVM cluster are physically connected to the CX 10000 switches for optimal network integration and redundancy
+- VM Essentials appliance version 8.0.6 or higher
+
+  - AFC and PSM are deployed and reachable from the VM Essentials manager
+- Aruba Fabric Composer (AFC) version 7.2 or higher, deployed as a VM
+- AMD Pensando PSM (Policy and Services Manager), deployed as a VM
+
+NOTE
+
+- Download AFC and PSM from the [HPE Networking Support portal](https://networkingsupport.hpe.com/downloads/software/RmlsZTo0YzQ2MzIyYS0xOTU2LTExZjAtYTMzNS0yZmRkN2QyMjdhOTY%253D)
+- For more information on deploying AFC and PSM, refer to the official documentation
+- The AFC and PSM must have network connectivity to the CX 10000 switches
+- Making full use of the VM Essentials Aruba CX 10000 integration requires credentials for AFC with API access granted and read/write access to AFC configuration
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json b/corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
new file mode 100644
index 0000000..9047374
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+  "title": "Service Plan Configuration",
+  "ordinal": 243,
+  "parent_title": "Overview",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.html",
+  "topic_cluster": {
+    "clustering_title": "Service Plan Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+        "clustering_title": "Service Plan Configuration"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B",
+        "clustering_title": "Service Plan Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md b/corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
new file mode 100644
index 0000000..03161e1
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EDCE321C-91B2-4C2D-8773-9F9B6485CB1B.md
@@ -0,0 +1,31 @@
+# Service Plan Configuration
+
+NOTE
+
+Not all fields listed below are available for every provision type. After selecting the provision type, the correct fields for that type of Service Plan will be revealed. Not all fields are required to save a valid Service Plan
+
+- **NAME:** The name of the Service Plan in VM Essentials
+- **ACTIVE:** Inactive Service Plans are not available for selection during provisioning or reconfigure. New discovered records cannot be associated with deactivated Plans when converting to managed resources. Any resources attached to a Plan will continue to be associated if the Plan is later deactivated
+- **CODE:** A unique identifier for use in VM Essentials API and CLI
+- **DISPLAY ORDER:** Configures the order in which plans are displayed relative to other plans associated with the same provision type. Note that Plans will be displayed in low-to-high order based on the Display Order property. This is reversed from Layouts which are displayed in high-to-low order
+- **PROVISION TYPE:** Determines the resource Provision Type this Service Plan is available for when provisioning, reconfiguring and converting discovered resources to managed
+- **REGION CODE:** (Optional) Limits availability of the Service Plan to Clouds with the specified Region Code
+- **STORAGE:** The default storage size of the root volume (in MB or GB)
+- **CUSTOMIZE ROOT VOLUME:** Allows the root volume size to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CUSTOMIZE EXTRA VOLUMES:** Allows the extra volume sizes to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **ADD VOLUMES:** Allows additional volumes to be added during provisioning or reconfigure
+- **MEMORY:** The amount of memory included with the plan (in MB or GB)
+- **CUSTOM MEMORY:** Allows the amount of memory to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORE COUNT:** The number of virtual CPU cores included with the plan
+- **CUSTOM CORES:** Allows the number of virtual CPU cores to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORES PER SOCKET:** Determines core distribution across sockets. CORES PER SOCKET cannot be larger than CORE COUNT, and CORE COUNT must be divisible by CORES PER SOCKET. For example four CORES with two CORES PER SOCKET means two sockets would have two cores each assigned. Four CORES with one CORE PER SOCKET would have four sockets with one core each assigned, and four CORES with four CORES PER SOCKET would have one socket with four cores assigned
+- **TOTAL STORAGE:** When custom storage is enabled for the plan, this sets a minimum and maximum total storage allowed (all disks combined)
+- **PER DISK SIZE:** When custom storage is enabled for the plan, this sets the minimum and maximum storage for each disk
+- **CUSTOM MEMORY RANGE:** The minimum and maximum allowed amount of memory for the Plan when CUSTOM MEMORY is enabled for the Plan
+- **CUSTOM CORES RANGE:** The minimum and maximum allowed amount of virtual CPU cores for the Plan when CUSTOM CORES is enabled for the Plan
+- **SOCKETS:** The minimum and maximum allowed sockets range for the Plan when CUSTOM CORES is enabled for the Plan
+- **CORES PER SOCKET:** The minimum and maximum allowed cores per socket for the Plan when CUSTOM CORES is enabled for the Plan
+
+TIP
+
+Custom Range storage and memory values units (GB/MB) are inherited from the :STORAGE:: and :MEMORY:: GB/MB settings in the same Plan. For example, if :STORAGE: is configured for for 40 GB, a custom range for Storage would also be in GB.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json b/corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
new file mode 100644
index 0000000..6bbe063
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+  "title": "Windows Settings",
+  "ordinal": 304,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md b/corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
new file mode 100644
index 0000000..6cf0ead
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
@@ -0,0 +1,13 @@
+# Windows Settings
+
+When provisioning a Windows-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Windows accounts
+- **Password:** The password that will be used with your Windows accounts
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+
+WARNING
+
+If your users Windows Settings password is not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_windows_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4558D828-A24E-42F3-8ACD-F5E4ACCD556C-high.png)
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json b/corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
new file mode 100644
index 0000000..855d2b9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+  "title": "Features",
+  "ordinal": 350,
+  "parent_title": "ArubaCX Network Integration",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md b/corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
new file mode 100644
index 0000000..52c9abf
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F18BAB29-FA73-48AC-9B2A-B4853B12CA18.md
@@ -0,0 +1,3 @@
+# Features
+
+- Network - Create or Delete OVS Port Group.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json b/corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
new file mode 100644
index 0000000..5ce4442
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+  "title": "Prepare The New CentOS 8/RHEL8 Image",
+  "ordinal": 340,
+  "parent_title": "Creating a CentOS/RHEL 8 Image",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.html",
+  "topic_cluster": {
+    "clustering_title": "Prepare The New CentOS 8/RHEL8 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+        "clustering_title": "Prepare The New CentOS 8/RHEL8 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F25A1489-CFA2-4B4A-9340-1C278198A951",
+        "clustering_title": "Prepare The New CentOS 8/RHEL8 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md b/corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
new file mode 100644
index 0000000..9bfd361
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F25A1489-CFA2-4B4A-9340-1C278198A951.md
@@ -0,0 +1,8 @@
+# Prepare The New CentOS 8/RHEL8 Image
+
+## Procedure
+
+1. Install epel-release: `yum -y install epel-release` (This step is not necessary for RHEL)
+2. Install git, wget, curl, cloud-init, cloud-utils-gropart, and open-vm-tools: `yum -y install git wget curl cloud-init cloud-utils-growpart open-vm-tools`
+3. Update: `yum -y update`
+4. Finally run: `rpm -qa kernel | sed 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}`
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json b/corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
new file mode 100644
index 0000000..3b56ec2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+  "title": "Packages",
+  "ordinal": 258,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.html",
+  "topic_cluster": {
+    "clustering_title": "Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+        "clustering_title": "Packages"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618",
+        "clustering_title": "Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md b/corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
new file mode 100644
index 0000000..94cc0ed
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F2B392B4-ECB0-4759-AB3A-BDFDBFA0E618.md
@@ -0,0 +1,29 @@
+# Packages
+
+## About this task
+
+Packages define reusable HPE Morpheus Essentials resources that you can upload and use across appliances. The platform supports package files in `.morpkg`, `.mpkg`, or `.mopkg` format.
+
+HPE Morpheus Essentials supports task object. Whereas Morpheus Enterprise supports automation objects, such as:
+
+- Instance Types
+- Layouts
+- Node Types
+- Tasks
+- Spec Templates
+- Cluster layouts
+
+Perform the following to upload a package:
+
+## Procedure
+
+1. Navigate to Administration > Integrations.
+2. Click Packages tab.
+3. Navigate to Package Upload section.
+4. Click Choose File.
+5. Select the required package.
+6. Click Upload.
+
+## Results
+
+The system extracts the package and populates the Library with the contained resources. The package appears in the list with its installation status.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json b/corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
new file mode 100644
index 0000000..0b34008
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+  "title": "Twilio SMS Settings",
+  "ordinal": 270,
+  "parent_title": "Appliance",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.html",
+  "topic_cluster": {
+    "clustering_title": "Twilio SMS Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+        "clustering_title": "Twilio SMS Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565",
+        "clustering_title": "Twilio SMS Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md b/corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
new file mode 100644
index 0000000..a3d77d0
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.md
@@ -0,0 +1,7 @@
+# Twilio SMS Settings
+
+Configure SMS text message delivery for VM Essentials alerts. Previously, customers could use VM Essentials’ own account for delivery, but for security reasons clients must now supply their own. Complete the fields indicated below and then restart all VM Essentials nodes to apply the changes.
+
+- **Account SID:** Twilio Account SID
+- **SMS From #:** The “From” number to receive the text message from
+- **Auth Token:** The Twilio API authentication token for your account
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json b/corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
new file mode 100644
index 0000000..f4fd4bc
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+  "title": "Edit Group",
+  "ordinal": 87,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.html",
+  "topic_cluster": {
+    "clustering_title": "Edit Group",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+        "clustering_title": "Edit Group"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13",
+        "clustering_title": "Edit Group"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md b/corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
new file mode 100644
index 0000000..583d1cd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F506C181-F8D0-41F9-B0FC-A5F9B4A72E13.md
@@ -0,0 +1,14 @@
+# Edit Group
+
+## About this task
+
+To edit a Group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to edit.
+4. Click the Edit button.
+5. From the Edit Group Wizard modify information as needed.
+6. Click the Save Changes button to save.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json b/corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
new file mode 100644
index 0000000..ee7fe6d
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+  "title": "Edit User",
+  "ordinal": 254,
+  "parent_title": "Users",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.html",
+  "topic_cluster": {
+    "clustering_title": "Edit User",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+        "clustering_title": "Edit User"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E",
+        "clustering_title": "Edit User"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md b/corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
new file mode 100644
index 0000000..418e2a3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F59F3ACB-1C1F-4DCA-89F6-50D3EAC5CE6E.md
@@ -0,0 +1,18 @@
+# Edit User
+
+## About this task
+
+User settings can be edited from Administration > Users.
+
+NOTE
+
+Some User data from Users created via an Identity Source Integration such as Active Directory is not editable in VM Essentials, as it is synced with the Identity Source.
+
+To edit a User from the Administration > Users Section:
+
+## Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Click the edit (pencil) icon from within the row of the selected User
+4. Make changes and select SAVE CHANGES.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json b/corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
new file mode 100644
index 0000000..ca22f10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+  "title": "Guest Console SSH Tunnel",
+  "ordinal": 145,
+  "parent_title": "Configuring Networks",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.html",
+  "topic_cluster": {
+    "clustering_title": "Guest Console SSH Tunnel",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+        "clustering_title": "Guest Console SSH Tunnel"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D",
+        "clustering_title": "Guest Console SSH Tunnel"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md b/corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
new file mode 100644
index 0000000..e955611
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F5A3797F-275A-40ED-A338-CEBFC8C2EC8D.md
@@ -0,0 +1,18 @@
+# Guest Console SSH Tunnel
+
+In some scenarios, Instances that are segregated from the VM Essentials appliance by port restrictions, or other mechanisms, can cause difficulties to access the guest console via the VM Essentials web UI. Guest Console SSH Tunnel settings allow the administrator to configure a jump host’s settings that is dual-homed, accessible by VM Essentials but also resides on the segregated network. When the guest console is configured with the SSH protocol, the traffic will be routed to the jump host, which will then relay to the target instance.
+
+GUEST CONSOLE JUMP HOST
+:   DNS hostname or IP of the jump host to relay the traffic
+
+GUEST CONSOLE JUMP PORT
+:   Port override, if different than 22 for SSH
+
+GUEST CONSOLE JUMP USERNAME
+:   Username used to authenticate to the jump host
+
+GUEST CONSOLE JUMP PASSWORD
+:   Password that is used with the username to autenticate to the jump host
+
+GUEST CONSOLE KEYPAIR
+:   Keypair saved in VM Essentials to be used in lieu of, or in addition to, the password to the jump host, which is associated with the configured username Keypairs can be imported at: Infrastructure > Trust > Key Pairs
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json b/corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
new file mode 100644
index 0000000..ef77736
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+  "title": "Cloud Detail Tabs",
+  "ordinal": 94,
+  "parent_title": "Cloud Detail View",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Detail Tabs",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+        "clustering_title": "Cloud Detail Tabs"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158",
+        "clustering_title": "Cloud Detail Tabs"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md b/corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
new file mode 100644
index 0000000..39c0ec9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F5A818DC-E3A9-4020-84FC-B087B2C14158.md
@@ -0,0 +1,29 @@
+# Cloud Detail Tabs
+
+NOTE
+
+Not all tabs are available for all Cloud Types.
+
+Clusters
+:   The Clusters tab displays clusters provisioned into the Cloud being viewed, including their status, type, name, layout, workers, and compute, memory, and storage stats. You can add a cluster by clicking ADD CLUSTER.
+
+Hosts
+:   The Hosts tab displays available hosts in the Cloud and displays power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status. You can add a resource by clicking ADD RESOURCE, add a hypervisor host by clicking ADD HYPERVISOR, or perform action an action by selecting one or more Hosts and clicking ACTIONS.
+
+    VMs
+    :   Displays an inventory of existing Instances in your Cloud configuration and provides details such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Bare Metal
+:   Setup PXE Boot in the Boot section to add bare metal servers. Once set up you can view information such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Security Groups
+:   The Security Groups tab displays a list of existing security groups in the cloud. You can add a security group to this cloud by clicking EDIT SECURITY GROUPS.
+
+Networks
+:   Displays Networks synced or added to the Cloud, including their name, type, CIDR, pool, DHCP status, visibility and targeted Tenant.
+
+Data Stores
+:   Displays Datastores synced or added to the Cloud, including their name, type, capacity, online status, visibility, and targeted Tenant.
+
+Resources
+:   Displays Resource Pools synced from the Cloud, including their name, description, and targeted Tenant.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json b/corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
new file mode 100644
index 0000000..e3b31f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+  "title": "Creating Cypher Keys",
+  "ordinal": 216,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Cypher Keys",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+        "clustering_title": "Creating Cypher Keys"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF",
+        "clustering_title": "Creating Cypher Keys"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md b/corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
new file mode 100644
index 0000000..60553b6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F5D7A6A5-94B0-4243-8C31-824DB19771CF.md
@@ -0,0 +1,6 @@
+# Creating Cypher Keys
+
+## Procedure
+
+1. Navigate to Tools > Cypher and select + ADD
+2. Configure one of the following types of Keys:
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json b/corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
new file mode 100644
index 0000000..e9c9681
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+  "title": "Add Virtual Image",
+  "ordinal": 77,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.html",
+  "topic_cluster": {
+    "clustering_title": "Add Virtual Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+        "clustering_title": "Add Virtual Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749",
+        "clustering_title": "Add Virtual Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md b/corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
new file mode 100644
index 0000000..430d47f
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F6D9BD42-0D7F-4263-9D7C-83656DC3E749.md
@@ -0,0 +1,108 @@
+# Add Virtual Image
+
+## About this task
+
+Virtual Images can be uploaded to VM Essentials from local files or URLs.
+
+WARNING
+
+Be conscious of your Storage Provider selection. The default Storage Provider is the VM Essentials Appliance at `/var/opt/morpheus/morpheus-ui/vms`. Uploading large images to the VM Essentials Appliance when there is inadequate space will cause upload failures and impact Appliance functionality. Ensure there is adequate space on your selected Storage Provider. Additional Storage Provider can be added at Infrastructure  >  Storage, which can be configured as the default Virtual Image Store or selected when uploading Images.
+
+NOTE
+
+VMware-type OVF Virtual Images do not support mounted ISO uploads
+
+To Add Virtual Image:
+
+## Procedure
+
+1. Select + Add in the Virtual Images page.
+2. Select Image format: 
+
+   - ISO
+   - QCOW2
+   - RAW
+   - VMware (vmdk/ovf/ova)
+3. Configure the following on the Virtual Image: 
+
+   Name
+   :   Name of the Virtual Image in VM Essentials. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as VM Essentials will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless VM Essentials is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, VM Essentials will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, VM Essentials will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. VM Essentials recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant VM Essentials environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, VM Essentials will install the FIPS-compliant VM Essentials Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. VM Essentials will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to VMware vCenter Clouds. Enable if the Windows Image has been sysprepped. If enabled, VM Essentials will inject `unattend.xml`
+
+   NOTE
+
+   Default Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage. Ensure local folders are owned by morpheus-app.morpheus-app if used.
+
+   WARNING
+
+   Provisioning will fail if Cloud init Enabled is checked and Cloud-Init is not installed on the Image.
+
+   NOTE
+
+   Existing Image credentials are required for Linux Images that are not Cloud-Init enabled and for Windows Images when Guest Customizations are not used. Cloud-Init and Windows user settings need to be configured in Administration > Settings > Provisioning when using Cloud-Init or Guest Customizations and new credentials are not set on the Virtual Image.
+4. Upload Image
+   :   Images can be uploaded by File or URL:
+       :   File
+           :   Drag and Drop the image file, or select Add File to select the image file.
+
+           Url
+           :   Select the URL radio button, and enter URL of the Image.
+
+       NOTE
+
+       The Virtual Image configuration can be saved when using a URL and the upload will finish in the background. When selecting/drag and dropping a file, the image files must upload completely before saving the Virtual Image record or the Image will not be valid.
+5. Save Changes.
+
+**Subtopics**  
+
+- **[VMware - VM Templates Copies](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-83AF39C3-5542-4739-B9ED-C867C472CDCE.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json b/corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
new file mode 100644
index 0000000..0ad27b3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+  "title": "Virtual Images",
+  "ordinal": 29,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md b/corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
new file mode 100644
index 0000000..cbdcdf5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F7007D76-D8A4-4FE3-B139-A626C340FDA0.md
@@ -0,0 +1,14 @@
+# Virtual Images
+
+The most common provisioning method within VM Essentials involves Virtual Machines, and the most important part of provisioning a VM is the Virtual Image. When provisioning a VM, VM Essentials will need to do a few things depending on the location of the Virtual Image and if agent install and console access are desired.
+
+Synced Images need to be properly configured
+:   VM Essentials gathers as much metadata for synced images as possible, but depending on the target (HVM cluster or VMware vCenter), OS, image configuration, or agent install settings, the synced Virtual Images may not be ready to provision without some configuration within VM Essentials. The Virtual Image is already at the target Cloud, but datastore selection, credentials, cloud-init settings, networks, and security settings on the Virtual Image can cause provisioning issues.
+
+Local/Uploaded Virtual Images
+:   Images uploaded to VM Essentials are configured during the Add Virtual Image process, however VM Essentials in most scenarios will still need to copy the Virtual Image to the target Hypervisor/Cloud upon the first provision to the target Cloud. In addition to the requirements for provisioning a synced Virtual Image, copying an uploaded Virtual Image to the target Cloud is required. Network and image configurations can cause upload failures, resulting in provisioning issues.
+
+**Subtopics**  
+
+- **[Synced Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-429877DA-255E-41FC-86B6-E7069B0EE7A6.html)**
+- **[Local Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-ECD5EC3F-BA9F-4E74-908E-A6C85C1C94AA.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json b/corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
new file mode 100644
index 0000000..52cf1bd
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+  "title": "Library Settings",
+  "ordinal": 280,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.html",
+  "topic_cluster": {
+    "clustering_title": "Library Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+        "clustering_title": "Library Settings"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7",
+        "clustering_title": "Library Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md b/corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
new file mode 100644
index 0000000..54e1ae9
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-F975055E-C129-4D47-9C7B-3DA11F59CCD7.md
@@ -0,0 +1,8 @@
+# Library Settings
+
+In this section, enable or disable access globally to provisioning sections of Catalog (self-service shopping cart provisioning), Apps (apps deployed from configured App Blueprints), and Instances
+
+- Enable Catalog
+- Enable Apps
+- Enable Instances
+- Provisioning Order: Sets the order for Instances, Apps, and Catalog to appear in the Provisioning menu
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json b/corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
new file mode 100644
index 0000000..3d9ee29
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+  "title": "Create Service Plan",
+  "ordinal": 241,
+  "parent_title": "Overview",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.html",
+  "topic_cluster": {
+    "clustering_title": "Create Service Plan",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+        "clustering_title": "Create Service Plan"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96",
+        "clustering_title": "Create Service Plan"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md b/corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
new file mode 100644
index 0000000..7c6ac10
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FA5B37E8-E994-44C0-9C4C-1F9DF1A83C96.md
@@ -0,0 +1,12 @@
+# Create Service Plan
+
+## About this task
+
+Perform the following to create a service plan:
+
+## Procedure
+
+1. Navigate to Administration > Plans (`/admin/service-plans`)
+2. Click the + ADD dropdown and select the appropriate Plan type
+3. Configure details for the Plan on the General tab, the configuration options will depend on the Plan type. See the section above for a detailed description of each configuration option available for Service Plans
+4. Click SAVE CHANGES
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json b/corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
new file mode 100644
index 0000000..f12ae95
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+  "title": "Secret",
+  "ordinal": 219,
+  "parent_title": "Cypher",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.html",
+  "topic_cluster": {
+    "clustering_title": "Secret",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+        "clustering_title": "Secret"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FA7264AB-8547-45E3-8752-8D47B6708F86",
+        "clustering_title": "Secret"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md b/corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
new file mode 100644
index 0000000..6a1e555
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FA7264AB-8547-45E3-8752-8D47B6708F86.md
@@ -0,0 +1,20 @@
+# Secret
+
+A Cypher secret is the standard secret module that stores a key/value in encrypted form.
+
+Key
+:   Pattern “secret/key”
+
+    - EXAMPLE: secret/mysecret
+
+Value
+:   Add the secret value to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the secret will be encrypted and available for use.
+
+If your VM Essentials user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the secret.
+
+To delete the secret, select Actions  >  Remove and confirm.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json b/corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
new file mode 100644
index 0000000..cfd04f2
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+  "title": "Hosting Images",
+  "ordinal": 19,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.html",
+  "topic_cluster": {
+    "clustering_title": "Hosting Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+        "clustering_title": "Hosting Images"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1",
+        "clustering_title": "Hosting Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md b/corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
new file mode 100644
index 0000000..2cb96fa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FA903FF7-0D74-4CDC-A25A-E19FF95F55E1.md
@@ -0,0 +1,11 @@
+# Hosting Images
+
+It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the VM Essentials appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
+
+```
+```
+![my alt text](https://myimage.com/image.jpg)
+```
+```
+
+The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The VM Essentials [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the VM Essentials appliance local storage. VM Essentials generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in VM Essentials Archives within your Wiki pages.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json b/corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
new file mode 100644
index 0000000..e09f2f5
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+  "title": "Creating a CentOS/RHEL 7 Image",
+  "ordinal": 336,
+  "parent_title": "VMware vCenter",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a CentOS/RHEL 7 Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+        "clustering_title": "Creating a CentOS/RHEL 7 Image"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2",
+        "clustering_title": "Creating a CentOS/RHEL 7 Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md b/corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
new file mode 100644
index 0000000..c146e92
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2.md
@@ -0,0 +1,21 @@
+# Creating a CentOS/RHEL 7 Image
+
+## About this task
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+## Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install open-vm-tools using command `yum install open-vm-tools`
+6. Install git by running `yum install git`
+7. Install epel-release repo using command `yum install epel-release`
+8. selinux set to permissive (enforced can cause problems with cloud-init) `sudo vi /etc/selinux/config`
+
+**Subtopics**  
+
+- **[Cloud-Init](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9C1E97D3-4285-4F70-ACAF-A56767901C74.html)**
+- **[Network Interfaces](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8DA22ED1-6EFE-40DD-B09D-DA883C50017E.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json b/corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
new file mode 100644
index 0000000..5bd8da3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+  "title": "Appliance",
+  "ordinal": 265,
+  "parent_title": "Settings",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md b/corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
new file mode 100644
index 0000000..37b72fa
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
@@ -0,0 +1,14 @@
+# Appliance
+
+**Subtopics**  
+
+- **[Appliance Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-206AB627-EE3C-4F56-AA25-0DFDECB86281.html)**
+- **[Tenant Management Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-51618D67-169D-4CCC-AC65-B3BE7DB45C54.html)**
+- **[User Management Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-E28627C8-0B64-44F6-BB1F-2E64951C2FE7.html)**
+- **[Email Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-DEC040BA-50C0-4DB1-B7DF-8A264FDA8336.html)**
+- **[Twilio SMS Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-F3650ED7-96D8-4542-8D04-ED3527A9C565.html)**
+- **[Proxy Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-2F84EEC0-C7BE-43B0-B17E-E35376B54F34.html)**
+- **[Currency Settings](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-06E4D650-D16A-4E96-98FE-B634E5DEA776.html)**
+- **[Integrating With a Currency Exchange Provider](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-AC461BBD-647D-447D-9307-218A41CE368B.html)**
+- **[Consuming Currency Exchange in VM Essentials](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-8EC2E33D-2086-4253-BF7D-D953052774A0.html)**
+- **[Enabled Clouds (Types)](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/render?page=GUID-9AA16B50-F8A4-443B-AD6C-6E018596459B.html)**
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json b/corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
new file mode 100644
index 0000000..68b501a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+  "title": "Actions",
+  "ordinal": 48,
+  "parent_title": "Managing Instances",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.html",
+  "topic_cluster": {
+    "clustering_title": "Actions",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+        "clustering_title": "Actions"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D",
+        "clustering_title": "Actions"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md b/corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
new file mode 100644
index 0000000..d3dc184
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FB7D15CC-A606-42DC-9DBF-27778D20282D.md
@@ -0,0 +1,43 @@
+# Actions
+
+Available options in the Actions dropdown can include:
+
+Suspend
+:   Puts the VM in a suspended state without shutting down the OS.
+
+Stop/Start/Restart Server
+:   Stops, Starts or Restarts the Virtual Machine.
+
+Import as Image
+:   Clones and exports VM in its current state to target Storage provider and adds a Virtual Image record with metadata matching the source Instance configuration.
+
+Clone to Image
+:   Clones and converts VM in its current state to image in the source Cloud and adds a Virtual Image record with metadata matching the source Instance configuration.
+
+Lock/Unlock Instance
+:   A locked Instance cannot be deleted until it is unlocked.
+
+Reconfigure
+:   The Reconfigure action allows service plan, disk, CPU, memory, networks and storage controller changes. Available options depend on the type and Plan configuration. Some resize actions require an Instance restart.
+
+Clone
+:   Creates a new Instance from the Instance at its current state.
+
+Backup
+:   Immediately executes a backup of the Instance. This is only available for Instances with backups enabled.
+
+Run Task
+:   Select a currently-configured Task to run against the Instance. Tasks can be created and edited in Library > Automation.
+
+Add Node
+:   Adds an additional node to the configuration. Additional options and configurations are required in the add node wizard depending on Instance configuration and type.
+
+Eject Disk
+:   Ejects attached disks (ISOs).
+
+Clone to Template (VMware)
+:   Creates a new VMware Template from the Instance with corresponding VM Essentials Virtual Image record.
+
+TIP
+
+Scrolling down in the Actions dropdown may be necessary to see all options.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json b/corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
new file mode 100644
index 0000000..cd336d3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+  "title": "Image Prep (Windows)",
+  "ordinal": 131,
+  "parent_title": "HVM clusters",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html",
+  "topic_cluster": {
+    "clustering_title": "Image Prep (Windows)",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+        "clustering_title": "Image Prep (Windows)"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7",
+        "clustering_title": "Image Prep (Windows)"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md b/corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
new file mode 100644
index 0000000..3a1f1b6
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.md
@@ -0,0 +1,94 @@
+# Image Prep (Windows)
+
+This section will go through the steps to prepare a Windows image which can be successfully provisioned to HVM clusters. Additionally, this image can serve as a template from which additional images and VM Essentials Library items can be built. In this example case, we’ll start from downloading a Windows Server 2019 ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
+
+With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+
+- **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2019 ISO”
+- **OPERATING SYSTEM:** “windows server 2019”
+- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+
+In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+
+With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large dropzone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled “Add File” and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES.
+
+![../../_images/progress.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-984BC461-04D2-4759-9E91-D9ACF2C6EB23-high.png)
+
+Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+
+On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+
+On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+
+As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+![../../_images/configTabBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+
+The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+
+Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+
+Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then “Open Console.” This will open a new window with a console session into the VM.
+
+![../../_images/initialConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+
+After selecting the language, click “Next.” On the following screen, click “Install Now.” This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click “Next.”
+
+![../../_images/chooseOs.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+
+Accept the licensing terms and click “Next.”
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+
+On the next screen, choose a custom install.
+
+![../../_images/clickInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+
+The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+![../../_images/selectVirtioPackage.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+
+After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+![../../_images/selectDisk.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+
+Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+![../../_images/windowsExp.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+
+Step through the installer. Simply click “Next” or “Install” through each step, there are no configuration changes needed. Once the installer has completed, click “Finish.” You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+![../../_images/showInterface.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+
+We can now eject the two virtual disks, drives D: and E: in my case. Then, launch Windows Security so we can disable firewalls. Turn off firewall for domain, private network, and public network.
+
+![../../_images/winDefender.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-DAA8652B-17E0-4AF2-9273-C548F0FA0614-high.png)
+
+Next, back in Command Prompt, run `winrm quickconfig` to configure `winrm`. Within `Services`, ensure that `winrm` (Windows Remote Management) is set to automatic on startup. Right-click on the Start button and select Run. Enter “sysprep” and click OK. In the Windows Explorer window that appears, right-click on `sysprep` and click “Run as Administrator”. Under “Shutdown Options”, choose Quit and click OK. If this is set to shutdown, VM Essentials will simply restart the VM. Once this is completed, a new file `Sysprep_succeeded.tag` appears in Windows Explorer.
+
+![../../_images/sysprepComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007735en_us/GUID-A11613FB-FC10-42BC-A6A3-3FB44D08260B-high.png)
+
+We’re now done configuring Windows and the console window can be closed. We’ll move on to creating a template from the VM we just configured. Begin by opening an SSH session into the VM Essentials appliance server. Confirm `jq` is up to date on the appliance box (`apt install jq`). Then, go ahead and stop the running Windows VM. We can do this from the Instance detail page in VM Essentials. Click ACTIONS and then “Stop Server.” Still on the Instance detail page, click ACTIONS and then “Import as Image.” This will perform a snapshot and create a new Virtual Image (Library > Virtual Images).
+
+The Virtual Image is not usable until it’s in an active status and the UI indication may display an active status even before it’s fully ready. If it’s “SAVING” or “QUEUED,” it is still being prepared and saved. To determine the current status of the Virtual Image, check with a call to VM Essentials API like the one below. When the return output lists a status of “Active,” the image is ready to be provisioned from.
+
+```
+```
+curl -k --request GET --url https://xx.xx.xx.xx/api/virtual-images/<id>  
+--header 'accept: application/json' --header 'authorization: Bearer xxx-xxx-xxx-xxx-xxx' |  
+jq '.virtualImage.status'
+```
+```
+
+Once saved, additional configurations are needed on the Virtual Image in VM Essentials. Edit the new Virtual Image and check the following configurations:
+
+- **MINIMUM MEMORY:** Set as appropriate
+- **SYSPREPPED/GENERALIZED IMAGE?:** Checked
+- **INSTALL AGENT?:** Checked
+- **USERNAME:** Remove if present
+- **PASSWORD:** Remove if present
+- **VIRTIO DRIVERS LOADED?:** Checked
+
+All other checkbox-type configurations not mentioned in the above list should be unchecked. Click SAVE CHANGES.
+
+At this point all image preparation steps are completed. Repeat the process of provisioning an HVM Instance Type selecting the new image in the future when needed.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json b/corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
new file mode 100644
index 0000000..16914d3
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+  "title": "Execution Schedules",
+  "ordinal": 207,
+  "parent_title": "Initial Backups Setup",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.html",
+  "topic_cluster": {
+    "clustering_title": "Execution Schedules",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+        "clustering_title": "Execution Schedules"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099",
+        "clustering_title": "Execution Schedules"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md b/corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
new file mode 100644
index 0000000..e923e44
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FCC43C3E-1AB9-4911-BA1B-3F30913DA099.md
@@ -0,0 +1,3 @@
+# Execution Schedules
+
+Backup Execution Schedules can be configured and managed in Library > Automation > Execute Scheduling. An execution schedule stores only the interval at which some execution should be run and they can apply to both backups and automation scripts. To create a new backup job with this schedule, navigate to Backups  >  Backups and click “+ADD”. In the final step of creating the backup job we are able to select any of our created execution schedules. The Default Backup Schedule set in Administration > Settings > Backups will be selected when creating a backup job and not specifying an execution schedule.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json b/corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
new file mode 100644
index 0000000..21ac30a
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+  "title": "Environment",
+  "ordinal": 7,
+  "parent_title": "Dashboard",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.html",
+  "topic_cluster": {
+    "clustering_title": "Environment",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+        "clustering_title": "Environment"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE",
+        "clustering_title": "Environment"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md b/corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
new file mode 100644
index 0000000..7ec85ea
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FCD97C29-07B4-4029-BDAC-8B60EB0FCAAE.md
@@ -0,0 +1,8 @@
+# Environment
+
+- **Groups:** Total number of Groups currently created
+- **Clouds:** Total number of Clouds currently integrated
+- **Clusters:** Total number of clusters currently provisioned
+- **Apps:** Total number of Apps currently provisioned
+- **Instances:** Total number of Instances currently provisioned
+- **Users:** Total number of VM Essentials user accounts
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json b/corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
new file mode 100644
index 0000000..5c7c74e
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+  "title": "Cloud Communication",
+  "ordinal": 169,
+  "parent_title": "Proxies",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Communication",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+        "clustering_title": "Cloud Communication"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D",
+        "clustering_title": "Cloud Communication"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md b/corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
new file mode 100644
index 0000000..b70bd48
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FD01C2EA-47A9-4F9F-A7B9-5588B8F9F52D.md
@@ -0,0 +1,3 @@
+# Cloud Communication
+
+When morpheus needs to connect to various cloud APIs to issue provisioning commands or to sync in existing environments, we need to ensure that those api endpoints are accessible by the appliance. In some cases the appliance may be behind a proxy when it comes to public cloud access like Azure and AWS. To configure the cloud integration to utilize a proxy, when adding or editing a cloud there is a setting called “API Proxy” under “Advanced Options”. This is where the proxy of choice can be selected to instruct the Provisioning engine how to communicate with the public cloud. Simply adjust this setting and the cloud should start being able to receive/issue instructions.
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json b/corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
new file mode 100644
index 0000000..bf77a97
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+  "title": "Adding Groups",
+  "ordinal": 85,
+  "parent_title": "Groups",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+        "clustering_title": "Adding Groups"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FDC357F5-AFCA-4175-ADF4-43928922C384",
+        "clustering_title": "Adding Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md b/corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
new file mode 100644
index 0000000..7cb5270
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FDC357F5-AFCA-4175-ADF4-43928922C384.md
@@ -0,0 +1,13 @@
+# Adding Groups
+
+## About this task
+
+To add a group:
+
+## Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Create Group button
+4. Input out the Name and Location (optional) fields
+5. Click the Save Changes button to save
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json b/corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
new file mode 100644
index 0000000..95c61f7
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "hvm_user_manual_8_1_2",
+  "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+  "title": "Highlights",
+  "ordinal": 17,
+  "parent_title": "Wiki",
+  "doc_id": "sd00007735en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007735en_us&page=GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.html",
+  "topic_cluster": {
+    "clustering_title": "Highlights",
+    "clustered_topics": [
+      {
+        "bundle_id": "hvm_user_manual_8_1_0",
+        "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+        "clustering_title": "Highlights"
+      },
+      {
+        "bundle_id": "hvm_user_manual_8_1_1",
+        "page_id": "GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B",
+        "clustering_title": "Highlights"
+      }
+    ]
+  }
+}
diff --git a/corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md b/corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
new file mode 100644
index 0000000..89866df
--- /dev/null
+++ b/corpus/hvm_user_manual_8_1_2/GUID-FF6CE93F-99CA-44FE-9DD6-D0591AC0221B.md
@@ -0,0 +1,13 @@
+# Highlights
+
+- Main Wiki section is at Operations > Wiki
+- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, and Clusters detail pages
+- Additional Wiki Pages and Categories can be created from Operations > Wiki
+- When a Wiki tab is populated, a Page is automatically added and accessible at Operations > Wiki
+- The Wiki is accessible from the UI, CLI and API.
+- Wiki access is RBAC-controlled via the Operations: Wiki permission in Roles (None, Read and Full)
+- Page updates are stamped with the “Last Updated By” user and the time the edit was made
+- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
+- All wiki pages are encrypted using AES 256-bit encryption
+- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
+- Create a new page with title “Home” to replace the default Wiki landing page that ships with VM Essentials