Repository: go
Issue: x/pkgsite: inconsistent terminology when referring to packages makes module landing page confusing
Labels: NeedsInvestigation,pkgsite,UX

### What is the URL of the page with the issue?
 
https://pkg.go.dev/github.com/mattn/go-sqlite3


### What is your user agent?
 
```
Mozilla/5.0 (X11; CrOS x86_64 13505.73.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.109 Safari/537.36
```

 
### Screenshot

![image](https://user-images.githubusercontent.com/5200974/102915417-ca2d3e80-444f-11eb-977a-1cc1eaeff9f9.png)
![image](https://user-images.githubusercontent.com/5200974/102916082-f7c6b780-4450-11eb-9884-cdcf9fc70029.png)

 
### What did you do?
 
1. From https://pkg.go.dev, search for `go-sqlite3`.
2. Click the first search result.

 
### What did you expect to see?

I wanted to see documentation for the package at the root of the module, and specifically to find out the name that that package declares in its `package` directive.
 
The path indicated by the URL has the following properties:
* The _module path_ is `github.com/mattn/go-sqlite3`, and is correctly indicated by the breadcrumb nav at the top of the page.
* The _package path_ is `github.com/mattn/go-sqlite3`.
* The _package name_ is `sqlite3`.
* The heading at the top of the module's `README.md` is `go-sqlite3`.

Given those properties, I expected to see all of the following on the page, somewhere above the fold:
* Because `sqlite3` is the _package name_ but not the _module path_, I expected to see the string `sqlite3` next to the word “package” but **not** next to the word “module”.
* Because both the `README` and the package docs are forms of documentation, I expected to see the word “package” in the left-nav link for the package documentation.
* Because the [definition of a “module”](https://golang.org/ref/mod#modules-overview) is “a collection of packages …”, I expected to see the word “packages” in the left-nav link to the table listing the packages within the module.
 
### What did you see instead?

* The `module` badge is displayed next to the _package name_ instead of the _module path_. Since in this case the module path is _not_ the package name, this associates the concept “module” with the wrong identifier, especially since the `README` itself begins with (a fragment of) the actual module name.
* Because of the large number of README sub-headings, the “Documentation” link is pushed almost below the fold.
* The nav link for the package documentation does not mention the word “package” at all, and does not distinguish between _package_ documentation and other kinds of documentation (such as documentation for the module overall).
* The nav link for the list of packages within the module uses the word “directories” instead of “packages”.
   *  This is especially confusing for modules like `golang.org/x/tools`, where the `gopls` subdirectory is a separate module. In that case, the subdirectory is pulled to the bottom of the list, instead of appearing inline with the other subdirectories. If the terminology used were “packages” and “modules” instead of simply “directories”, then that separation would make intuitive sense — however, the use of the term “directories” instead sets the expectation that the table should contain an entry for each relevant directory regardless of what kind of entity it corresponds to.
      ![image](https://user-images.githubusercontent.com/5200974/102916448-9521eb80-4451-11eb-895a-049fdf56bb1a.png)
      ![image](https://user-images.githubusercontent.com/5200974/102916483-a23eda80-4451-11eb-8c09-12e3544e047f.png)