That's what I ended up using. The readme.txt did an awful job at explaining how to use the damn thing, but I eventually found out how it worked. It works great and I can pass it off to my clients when my project is over.

The node/# solution didn't work. I'm still seeing the block displayed on the page it shouldn't be on. Also there is no WYSWYG editor on that field. Just plain text.

Indeed I did. I still see the block on pages it should not appear on.

Although I can do that, for some reason Drupal still displays the content on other pages. For example, I only want this block to show on the about page ([domain]/about) so I put "about" on the Show Block on Specific Pages with the Only the listed pages button selected. Lo and behold, the block is still displayed on all pages of the content type.

I got that done, but the block still shows on all pages of the content type I'm using.

So I've seen that "solution" too, but I wanted to know what I do to embed the view in a specific node. For example, if a user views my Resources page, I want them to be able to see the view that I created for that page plus the content that's already on it.