diff --git a/docs/design/tuple.md b/docs/design/tuple.md
index 57e984d..ffc74c7 100644
--- a/docs/design/tuple.md
+++ b/docs/design/tuple.md
@@ -25,7 +25,7 @@ For example, it can't use formatted `static_assert`s (because they make use of
`tuplelike` is modelled by `stdx::tuple` and `stdx::indexed_tuple` only.
`has_tuple_protocol` means that a type models the `get` protocol. This applies
-to much more: `stdx::tuple` but also `std::tuple`, `std::pair`, std::array`,
+to much more: `stdx::tuple` but also `std::tuple`, `std::pair`, `std::array`,
etc.
## `one_of`
diff --git a/docs/header_graph.mmd b/docs/header_graph.mmd
index 157b031..7867ed4 100644
--- a/docs/header_graph.mmd
+++ b/docs/header_graph.mmd
@@ -61,8 +61,8 @@ flowchart BT
bitset --> ct_string
panic(panic.hpp)
panic --> ct_string
- A(env.hpp
static_assert.hpp)
- A --> ct_string
+ env(env.hpp)
+ env --> ct_string
tuple_algorithms(tuple_algorithms.hpp)
tuple_algorithms --> tuple
functional(functional.hpp)
@@ -83,15 +83,15 @@ flowchart BT
atomic_bitset ---> bitset
B(intrusive_forward_list.hpp
intrusive_list.hpp)
B --> panic
- ct_format(ct_format.hpp)
pp_map(pp_map.hpp)
ranges(ranges.hpp)
- ct_format ----> ct_string
- ct_format ---> tuple_algorithms
- ct_format --> pp_map
- ct_format --> ranges
call_by_need(call_by_need.hpp)
call_by_need --> tuple_algorithms
+ ct_format(ct_format.hpp)
+ ct_format ---> ct_string
+ ct_format --> tuple_algorithms
+ ct_format --> pp_map
+ ct_format --> ranges
latched(latched.hpp)
latched --> functional
optional(optional.hpp)
@@ -100,3 +100,5 @@ flowchart BT
%% level 8
cached(cached.hpp)
cached --> latched
+ static_assert(static_assert.hpp)
+ static_assert --> ct_format