`submodule.foo.path = path/to/bar`.
The `gitlink` entry contains the object name of the commit that the
- superproject expects the submodule’s working directory to be at.
+ superproject expects the submodule's working directory to be at.
The section `submodule.foo.*` in the `.gitmodules` file gives additional
-hints to Gits porcelain layer such as where to obtain the submodule via
-the `submodule.foo.url` setting.
+hints to Git's porcelain layer. For example, the `submodule.foo.url`
+setting specifies where to obtain the submodule.
Submodules can be used for at least two different use cases:
of the superproject.
* Deinitialized submodule: A `gitlink`, and a `.gitmodules` entry,
- but no submodule working directory. The submodule’s Git directory
-but no submodule working directory. The submodule's git directory
-may be there as after deinitializing the git directory is kept around.
++but no submodule working directory. The submodule's Git directory
+may be there as after deinitializing the Git directory is kept around.
The directory which is supposed to be the working directory is empty instead.
+
A submodule can be deinitialized by running `git submodule deinit`.