Bug 1416023: Fix typo in `jar-manifests.rst`. r=gps
authorTom Prince <mozilla@hocat.ca>
Thu, 09 Nov 2017 15:35:28 -0700
changeset 391943 65c49a6c83f3152d1dc021056b2795e17de6bf11
parent 391942 62b191e02145b1220a39dd2034a3f4d7057e133f
child 391944 40eff3779e4126e766e0efba18d8029f0a498f9e
push id32908
push usercbrindusan@mozilla.com
push dateWed, 15 Nov 2017 22:22:51 +0000
treeherdermozilla-central@60b9fa15e427 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersgps
bugs1416023
milestone59.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1416023: Fix typo in `jar-manifests.rst`. r=gps MozReview-Commit-ID: HC4J9Bwx3DJ
build/docs/jar-manifests.rst
--- a/build/docs/jar-manifests.rst
+++ b/build/docs/jar-manifests.rst
@@ -30,17 +30,17 @@ To ship chrome files in a JAR, an indent
 
    <jarfile>.jar:
      path/in/jar/file_name.xul     (source/tree/location/file_name.xul)
 
 The JAR location may be preceded with a base path between square brackets::
    [base/path] <jarfile>.jar:
      path/in/jar/file_name.xul     (source/tree/location/file_name.xul)
 
-In this case, the jar will be directly located under the given ``base/bath``,
+In this case, the jar will be directly located under the given ``base/path``,
 while without a base path, it will be under a ``chrome`` directory.
 
 If the JAR manifest and packaged file live in the same directory, the path and
 parenthesis can be omitted. In other words, the following two lines are
 equivalent::
 
    path/in/jar/same_place.xhtml     (same_place.xhtml)
    path/in/jar/same_place.xhtml