Confusing use of the term "subdirectory" in the file seed-paths

[davidculley]

I find the use of the word "subdirectory" (in line 22) confusing. I would say "directory" instead.

docs.getdbt.com/website/docs/reference/project-configs/seed-paths.md

Line 22 in 711fc27

### Use a subdirectory named `custom_seeds` instead of `seeds`

Everywhere else, you actually refer to the seeds/ directory as "directory" rather than "subdirectory", just not on line 22.

Evidence A:

docs.getdbt.com/website/docs/reference/project-configs/seed-paths.md

Line 15 in 711fc27

Optionally specify a custom list of directories where [seed](/docs/build/seeds) files are located.

Evidence B:

docs.getdbt.com/website/docs/reference/project-configs/seed-paths.md

Line 19 in 711fc27

By default, dbt expects seeds to be located in the `seeds` directory, i.e. `seed-paths: ["seeds"]`

The use of the term "subdirectory" in line 22 gets even more confusing when you introduce actual subdirectories (for example, seeds/one and seeds/two) to avoid having to make changes to seed-paths and then refer to the directory seeds/ on the root level of the project also as subdirectory (is it really a subdirectory when it's a directory at the root level?):

docs.getdbt.com/website/docs/reference/project-configs/seed-paths.md

Line 45 in 711fc27

Note: We recommend that you instead use two subdirectories within the `seeds/` directory to achieve a similar effect.

[matthewshaver]

Good call out! Thanks @davidculley