Skip to content

Commit 24042ba

Browse files
authored
Merge pull request #1136 from Madmaxs2/main
Fix typos and remove duplicate entries Changes Made
2 parents 89962d0 + c639e67 commit 24042ba

File tree

2 files changed

+2
-3
lines changed

2 files changed

+2
-3
lines changed

.github/ISSUE_TEMPLATE/docs_audit_results.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ op-conductor
104104
fp-contracts
105105
cannon
106106
op-program
107-
asterisc
107+
asterisk
108108
kona
109109
superchain-registry
110110
supersim
@@ -125,7 +125,6 @@ devops-tooling
125125
artifacts-packaging
126126
sequencer-in-a-box
127127
devnets
128-
op-supervisor
129128
performance-tooling
130129
peer-management-service
131130
proxyd

notes/resources.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Public Resources Folder
22

3-
Non-text resources like JSON files that are designed to be made available publicly should sit within the [public/resourcs](/public/resources/) folder at the root of this repository.
3+
Non-text resources like JSON files that are designed to be made available publicly should sit within the [public/resources](/public/resources/) folder at the root of this repository.
44
Files within this folder can be referenced by linking to `/resources/path/to/file` as if the `resources` folder existed at the root level of the project, similar to the way that images are referenced by linking to `/img/path/to/image`.
55
Nextra will automatically handle the translation of these links to the `/resources` folder to point to the actual `/public/resources` folder.
66
The [Lychee](./lychee.md) configuration file found at [lychee.toml](/lychee.toml) includes a remapping that will allow Lychee to correctly check for these resources during the link checking CI step.

0 commit comments

Comments
 (0)