Clarify Dependency Scope table

[brkeh]

As mentioned in issue #1357, can we please clarify the dependency scope table on Introduction to the Dependency Mechanism ?

Can we label the column and row headers? It took me a while to understand the table from the sentences above the table and I think header labels would it make clearer and easier to understand. My understanding is each row header in left column is a Main project dependency and each column header in first row is a Dependency project dependency. I wasn't able to get two header rows in Mark Down so I used HTML.

Following this checklist to help us incorporate your contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Run mvn site and examine output in target/site directory.
  Site will also be built on your pull request automatically and attached to GitHub Action result.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[elharo]

Is this just changing to HTML?

[brkeh]

No, click on the button to display the rich diff to see the change. My idea was to add header labels to the table. I wasn't able to get two header rows in Mark Down so I used HTML. My understanding is each row header in left column is a Main project dependency and each column header in first row is a Dependency project dependency.