would this be a many to many relationship or one to many?
It's regarded as many-to-many, because many projects can refer to many sections.
You'll need to implement a table that sits between projects
and sections
, using foreign keys from both to be the primary key. Example:
PROJECTS_SECTIONS_XREF
table
PROJECT_ID
, pk, fk
SECTION_ID
, pk, fk
The naming convention is up to you, but I recommend something informational by using the names of both tables involved. Corrollary, cross references (xref), lookup, etc. There's been two questions regarding the naming convention in the past week or so - all the names are synonyms, choose whatever you like.