summaryrefslogtreecommitdiff
path: root/pod/perllocale.pod
diff options
context:
space:
mode:
authorKarl Williamson <khw@cpan.org>2018-01-14 20:14:50 -0700
committerKarl Williamson <khw@cpan.org>2018-01-14 20:18:17 -0700
commit26a9b33ac8fca65ec470c3cf33d46b0f5d0ad42a (patch)
treecad24f095dfe04af99d111dbd078f2f79a11da2d /pod/perllocale.pod
parent22803c6a19ff20ad1dd5d566e2e46cc7bb44ca42 (diff)
downloadperl-26a9b33ac8fca65ec470c3cf33d46b0f5d0ad42a.tar.gz
perllocale: Wording/formatting nits
Diffstat (limited to 'pod/perllocale.pod')
-rw-r--r--pod/perllocale.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perllocale.pod b/pod/perllocale.pod
index bb39c3840d..233aaeba1a 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -177,8 +177,8 @@ Another thread may change the locale at any time, which could cause at a
minimum that a given thread is operating in a locale it isn't expecting
to be in. On some platforms, segfaults can also occur. The locale
change need not be explicit; some operations cause perl to change the
-locale itself. You are vulnerable simply by having done a C<"use
-locale">.
+locale itself. You are vulnerable simply by having done a S<C<"use
+locale">>.
By default, Perl itself (outside the L<POSIX> module)
ignores the current locale. The S<C<use locale>>
@@ -907,7 +907,7 @@ characters between lower and uppercase. This affects the case-mapping
functions--C<fc()>, C<lc()>, C<lcfirst()>, C<uc()>, and C<ucfirst()>;
case-mapping
interpolation with C<\F>, C<\l>, C<\L>, C<\u>, or C<\U> in double-quoted
-strings and C<s///> substitutions; and case-independent regular expression
+strings and C<s///> substitutions; and case-insensitive regular expression
pattern matching using the C<i> modifier.
Starting in v5.20, Perl supports UTF-8 locales for C<LC_CTYPE>, but