@shapesim, which engine are you using and how are you implementing DLC? This path will vary by engine and implementation strategy hence why the instructions only guide you to list the respective DLC assets path in a generic fashion.
If your engine is configured to expect the assets to be in \GameDLC1 & \GameDLC2 then they should be there respectively to test the implementation. As you can see in the examples, the Viveport "title" on the documentation example is "DLC_Test" but the assets are housed in "DLC_Folder". I will have someone from this team pop into this thread and verify that my answer is correct.
To reach Viveport's customer service team, email email@example.com
To connect with a live support agent for hardware support, go to www.vive.com/support, click on "contact us" in the top righthand corner, and then opt to speak with a Live Chat agent David R
Technical Specialist - San Francisco, CA; Monday-Friday