look in the Roles tables and the Permissions table too - that will tell you what the tab_permission column RoleId and PermissionId are representing.  In my case I would find the page's tabId, look in Tab_permissions and then look at the role id that represents the one you want to close down...also, in my case a permissionid of 3 is View and a permission ID of 4 means edit.  I might also suggest creating a role that has no users so you can switch the roleid of the page you do not want all users to be able to edit and swap to that one, instead of deleting the row, which is harder to recover from if that does not work as expected.  Also, there is an "allow access" column in tab_permissions, but I am not 100% sure what it does.  I hope this is enough to get you going.  The reality is that this is just a hack and you will need to experiment a little to see what happens to your page as you change those permissions/roles on the page.  Hence, my strong encouragement that you do a back up before mucking about in the tables.  Nonetheless, being able to fat-finger values on the backend has saved my @$$ a few times.

Thanks, Everyone.

Here's what I ended up doing to resolve the issue.

I exported each page within with the dev site, modified the permissionkey
by setting it to "EDIT" and then imported each page to the production site.

It's not the most glamorous solution but it worked and we're able to move on.