the renderer doesn't like C<I<foo>>, trying I<C<foo>> what is righter

anyways
Raku · Mar 30, 2016 · a256055 · a256055
1 parent 57f7325
commit a256055
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/doc/Language/functions.pod b/doc/Language/functions.pod
@@ -644,7 +644,7 @@ a 1;        # Int 1\n Any 1
 =end code
 
 As mentioned earlier, multi subs are not the only situation in which
-C<I<callwith>>, C<I<callsame>>, C<I<nextwith>> and C<I<nextsame>> can be helpful.
+I<C<callwith>>, I<C<callsame>>, I<C<nextwith>> and I<C<nextsame>> can be helpful.
 One is is for dispatching to wrapped routines:
 
 =begin code

diff --git a/doc/Language/typesystem.pod b/doc/Language/typesystem.pod
@@ -38,7 +38,7 @@ TODO
 
 =head2 C<subset>
 
-A C<I<subset>> declares a new type that will re-dispatch to its base type. If a
+A I<C<subset>> declares a new type that will re-dispatch to its base type. If a
 C<where> clause is supplied any assignment will be checked against the given
 code object.