Skip to content

Commit 42b2e20

Browse files
committed
fix docs typos
1 parent 4226c12 commit 42b2e20

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/source/roadmap.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ Roadmap
44
2021-Q2
55
-------
66

7-
Element and Component Identity:
7+
**Element and Component Identity**:
88
At the moment, whenever a particular branch of a layout is updated, all the state
99
(i.e. hooks and event handlers) that live within that branch are thrown away and
1010
reconstructed. Given IDOM's current implementation for
1111
:class:`~idom.core.layout.Layout` this is unavoidable. To resolve this issue, we
12-
need to add a concept of `"keys" <https://reactjs.org/docs/lists-and-keys.html>`
12+
need to add a concept of `"keys" <https://reactjs.org/docs/lists-and-keys.html>`__
1313
which can be used to indicate the identity of an element within the layout
1414
structure. For example, if you have a list of elements that get re-ordered when a
1515
button is pressed, their state should be preserved, and reassigned to their new
@@ -29,7 +29,7 @@ Element and Component Identity:
2929
- https://github.com/idom-team/idom/issues/330
3030
- https://github.com/idom-team/idom/issues/19
3131

32-
Reconsider Custom Component Interface:
32+
**Reconsider Custom Component Interface**:
3333
One problem that's come up several times while implementing alternate client
3434
solutions with React is that custom components must use the same React instances
3535
as the client. This is problematic for developers of these custom components because

0 commit comments

Comments
 (0)