Skip to content

Commit a256055

Browse files
committed
the renderer doesn't like C<I<foo>>, trying I<C<foo>> what is righter
anyways
1 parent 57f7325 commit a256055

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

doc/Language/functions.pod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -644,7 +644,7 @@ a 1; # Int 1\n Any 1
644644
=end code
645645
646646
As mentioned earlier, multi subs are not the only situation in which
647-
C<I<callwith>>, C<I<callsame>>, C<I<nextwith>> and C<I<nextsame>> can be helpful.
647+
I<C<callwith>>, I<C<callsame>>, I<C<nextwith>> and I<C<nextsame>> can be helpful.
648648
One is is for dispatching to wrapped routines:
649649
650650
=begin code

doc/Language/typesystem.pod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ TODO
3838
3939
=head2 C<subset>
4040
41-
A C<I<subset>> declares a new type that will re-dispatch to its base type. If a
41+
A I<C<subset>> declares a new type that will re-dispatch to its base type. If a
4242
C<where> clause is supplied any assignment will be checked against the given
4343
code object.
4444

0 commit comments

Comments
 (0)