ianhitchman/tiptap
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: fix typos

Browse Source
This commit is contained in:
Hans Pagel
2021-10-14 10:46:09 +02:00
parent e37639ac6d
commit 4183499ff9
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api/marks/subscript.md
View File

@@ -1,5 +1,5 @@
--- ---
description: Write slightly below the the normal line, to show you’re unique. description: Write slightly below the normal line, to show you’re unique.
--- ---
# Subscript # Subscript

2
docs/api/marks/superscript.md
View File

@@ -1,5 +1,5 @@
--- ---
description: Write slightly above the the normal line, to show you’re just next level. description: Write slightly above the normal line, to show you’re just next level.
--- ---
# Superscript # Superscript

2
docs/guide/node-views/js.md
View File

@@ -45,7 +45,7 @@ Got it? Let’s see it in action. Feel free to copy the below example to get sta
That node view even interacts with the editor. Time to see how that is wired up. That node view even interacts with the editor. Time to see how that is wired up.
## Access node attributes ## Access node attributes
The editor passes a few helpful things to your render function. One of them is the the `node` prop. This one enables you to access node attributes in your node view. Let’s say you have [added an attribute](/guide/custom-extensions#attributes) named `count` to your node extension. You could access the attribute like this: The editor passes a few helpful things to your render function. One of them is the `node` prop. This one enables you to access node attributes in your node view. Let’s say you have [added an attribute](/guide/custom-extensions#attributes) named `count` to your node extension. You could access the attribute like this:
```js ```js
addNodeView() { addNodeView() {