Skip to content

Commit 94e0f66

Browse files
chalinfekete-robert
authored andcommitted
Prose tweaks
1 parent a512852 commit 94e0f66

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,7 @@
11
---
2-
title: "Update the Docsy Hugo Module"
3-
linkTitle: "Update the Docsy Hugo Module"
2+
title: Update your Docsy Hugo Module
43
weight: 1
5-
description: >
6-
Update the Docsy theme to the latest version using Hugo Modules.
4+
description: Update your Docsy theme to the latest version using Hugo Modules.
75
---
86

97
When using the Docsy theme as a Hugo Module, updating your theme is really easy.
@@ -20,20 +18,23 @@ Then invoke hugo's module `get` subcommand with the update flag:
2018
hugo mod get -u github.com/google/docsy
2119
```
2220

23-
Hugo automatically pulls in the latest theme version. That's it, your update is done!
24-
21+
Hugo automatically pulls in the latest theme version. That's it, your update is
22+
done!
2523

2624
{{% alert title="Tip" %}}
27-
If you want to set your module to a certain version inside the docsy theme repo, simply specific the name of the tag representing this version (here: _v{{% param "version" %}}_) when updating your theme:
25+
26+
If you want to set your module to a certain version inside the Docsy theme repo,
27+
simply specify the name of the tag representing this version when updating your
28+
theme, for example:
2829

2930
```bash
3031
hugo mod get -u github.com/google/docsy@v{{% param "version" %}}
3132
```
3233

33-
Instead of a version tag, you can also specify a commit hash inside the repo (here: _6c8a3afe_) when updating your theme:
34-
34+
Instead of a version tag, you can also specify a commit hash, for example:
3535

3636
```bash
3737
hugo mod get -u github.com/google/docsy@6c8a3afe
3838
```
39+
3940
{{% /alert %}}

0 commit comments

Comments
 (0)