Skip to content

Commit

Permalink
docs: tidy markup, fix encoding errors
Browse files Browse the repository at this point in the history
  • Loading branch information
dboddie committed Aug 2, 2023
1 parent ffbe66f commit ee87426
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions docs/base-snaps.rst
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ In most Ubuntu bases (except ``core``), *snapd* and its associated tools are pro
Defining a base
---------------

Bases are defined by adding the ``base:`` keyword to a snaps :ref:`snapcraft.yaml <the-snapcraft-yaml-schema>` followed by the base name.
Bases are defined by adding the ``base`` keyword to a snap's :ref:`snapcraft.yaml <the-snapcraft-yaml-schema>` followed by the base name.

For example, to specify ``core18``, use the following:

Expand All @@ -45,7 +45,7 @@ To specify ``core22``, use the following
base: core22
Snapcraft no longer supports building snaps with the older *core* base. Snapcraft 4 needs to be used instead. Snapcraft 4 is still being supported and can be installed from Snapcraft’s *4.x* :term:`track`:
Snapcraft no longer supports building snaps with the older ``core`` base. Snapcraft 4 needs to be used instead. Snapcraft 4 is still being supported and can be installed from Snapcraft’s *4.x* :term:`track`:

.. code:: bash
Expand Down
4 changes: 2 additions & 2 deletions docs/node-apps.rst
Original file line number Diff line number Diff line change
Expand Up @@ -171,7 +171,7 @@ After you have created the :file:`snapcraft.yaml` file, or used the one provided
++ npm pack .
++ tail -1
npm notice
npm notice wethr@1.5.2
npm notice 📦 wethr@1.5.2
npm notice === Tarball Contents ===
npm notice 1.1kB LICENSE
npm notice 29.1kB demo.gif
Expand Down Expand Up @@ -217,7 +217,7 @@ You can then try it out:
.. code:: bash
$ wethr
London, GB: 17.04C
London, GB: 17.04C 🌧
Removing the snap is simple too:

Expand Down

0 comments on commit ee87426

Please sign in to comment.