Learn 以下の文書内のリンクURLを正規化 (#2356)

- /en-US へのリンクを /ja へのリンクに修正
- /ja が付いていないものに /ja を付加
- MDN内のリンクが完全URLの場合、 /ja/docs からのURLに修正

5 files changed, 28 insertions, 28 deletions

diff --git a/files/ja/learn/performance/business_case_for_performance/index.html b/files/ja/learn/performance/business_case_for_performance/index.html
index 106a517a8f..6b4fef087c 100644
--- a/files/ja/learn/performance/business_case_for_performance/index.html
+++ b/files/ja/learn/performance/business_case_for_performance/index.html
@@ -72,12 +72,12 @@ translation_of: Learn/Performance/business_case_for_performance
  <li><a href="/ja/docs/Learn/Performance/What_is_web_performance">ウェブパフォーマンスとは何ですか？</a></li>
  <li><a href="/ja/docs/Learn/Performance/Perceived_performance">ユーザーはパフォーマンスをどのように知覚しますか？</a></li>
  <li><a href="/ja/docs/Learn/Performance/Measuring_performance">パフォーマンスの測定</a></li>
- <li><a href="/en-US/docs/Learn/Performance/Multimedia">Multimedia: images</a></li>
- <li><a href="/en-US/docs/Learn/Performance/video">Multimedia: video</a></li>
- <li><a href="/en-US/docs/Learn/Performance/JavaScript">JavaScript performance best practices</a>.</li>
- <li><a href="/en-US/docs/Learn/Performance/HTML">HTML performance features</a></li>
- <li><a href="/en-US/docs/Learn/Performance/CSS">CSS performance features</a></li>
- <li><a href="/en-US/docs/Learn/Performance/Fonts">Fonts and performance</a></li>
- <li><a href="/en-US/docs/Learn/Performance/Mobile">Mobile performance</a></li>
+ <li><a href="/ja/docs/Learn/Performance/Multimedia">Multimedia: images</a></li>
+ <li><a href="/ja/docs/Learn/Performance/video">Multimedia: video</a></li>
+ <li><a href="/ja/docs/Learn/Performance/JavaScript">JavaScript performance best practices</a>.</li>
+ <li><a href="/ja/docs/Learn/Performance/HTML">HTML performance features</a></li>
+ <li><a href="/ja/docs/Learn/Performance/CSS">CSS performance features</a></li>
+ <li><a href="/ja/docs/Learn/Performance/Fonts">Fonts and performance</a></li>
+ <li><a href="/ja/docs/Learn/Performance/Mobile">Mobile performance</a></li>
  <li><a href="/ja/docs/Learn/Performance/business_case_for_performance">パフォーマンスに光をあてる</a></li>
 </ul>
diff --git a/files/ja/learn/performance/measuring_performance/index.html b/files/ja/learn/performance/measuring_performance/index.html
index f70a9cfa20..3f4985423c 100644
--- a/files/ja/learn/performance/measuring_performance/index.html
+++ b/files/ja/learn/performance/measuring_performance/index.html
@@ -21,7 +21,7 @@ translation_of: Learn/Performance/Measuring_performance
  <tbody>
   <tr>
    <th scope="row">前提:</th>
-   <td>基本的なコンピューターリテラシー、<a href="https://developer.mozilla.org/ja/Learn/Getting_started_with_the_web/Installing_basic_software">基本的なソフトウェアのインストール</a>、<a href="/en-US/docs/Learn/Getting_started_with_the_web">クライアントサイドのウェブ技術</a>の基本的な知識</td>
+   <td>基本的なコンピューターリテラシー、<a href="/ja/Learn/Getting_started_with_the_web/Installing_basic_software">基本的なソフトウェアのインストール</a>、<a href="/ja/docs/Learn/Getting_started_with_the_web">クライアントサイドのウェブ技術</a>の基本的な知識</td>
   </tr>
   <tr>
    <th scope="row">目的:</th>
@@ -94,12 +94,12 @@ translation_of: Learn/Performance/Measuring_performance
  <li><a href="/ja/docs/Learn/Performance/What_is_web_performance">ウェブパフォーマンスとは何か</a></li>
  <li><a href="/ja/docs/Learn/Performance/Perceived_performance">ユーザーはパフォーマンスをどのように知覚するか</a></li>
  <li><a href="/ja/docs/Learn/Performance/Measuring_performance">パフォーマンスの測定</a></li>
- <li><a href="/en-US/docs/Learn/Performance/Multimedia">Multimedia: images</a></li>
- <li><a href="/en-US/docs/Learn/Performance/video">Multimedia: video</a></li>
- <li><a href="/en-US/docs/Learn/Performance/JavaScript">JavaScript performance best practices</a>.</li>
- <li><a href="/en-US/docs/Learn/Performance/HTML">HTML performance features</a></li>
- <li><a href="/en-US/docs/Learn/Performance/CSS">CSS performance features</a></li>
- <li><a href="/en-US/docs/Learn/Performance/Fonts">Fonts and performance</a></li>
- <li><a href="/en-US/docs/Learn/Performance/Mobile">Mobile performance</a></li>
+ <li><a href="/ja/docs/Learn/Performance/Multimedia">Multimedia: images</a></li>
+ <li><a href="/ja/docs/Learn/Performance/video">Multimedia: video</a></li>
+ <li><a href="/ja/docs/Learn/Performance/JavaScript">JavaScript performance best practices</a>.</li>
+ <li><a href="/ja/docs/Learn/Performance/HTML">HTML performance features</a></li>
+ <li><a href="/ja/docs/Learn/Performance/CSS">CSS performance features</a></li>
+ <li><a href="/ja/docs/Learn/Performance/Fonts">Fonts and performance</a></li>
+ <li><a href="/ja/docs/Learn/Performance/Mobile">Mobile performance</a></li>
  <li><a href="/ja/docs/Learn/Performance/business_case_for_performance">パフォーマスに光をあてる</a></li>
 </ul>
diff --git a/files/ja/learn/performance/perceived_performance/index.html b/files/ja/learn/performance/perceived_performance/index.html
index 8af223ce2e..fceb427902 100644
--- a/files/ja/learn/performance/perceived_performance/index.html
+++ b/files/ja/learn/performance/perceived_performance/index.html
@@ -18,7 +18,7 @@ translation_of: Learn/Performance/perceived_performance
  <tbody>
   <tr>
    <th scope="row">前提条件:</th>
-   <td>基本的なコンピューターリテラシー、<a href="https://developer.mozilla.org/ja/Learn/Getting_started_with_the_web/Installing_basic_software">基本的なソフトウェアのインストール</a>、<a href="/ja/docs/Learn/Getting_started_with_the_web">クライアントサイドのウェブ技術</a>の基本的な知識</td>
+   <td>基本的なコンピューターリテラシー、<a href="/ja/Learn/Getting_started_with_the_web/Installing_basic_software">基本的なソフトウェアのインストール</a>、<a href="/ja/docs/Learn/Getting_started_with_the_web">クライアントサイドのウェブ技術</a>の基本的な知識</td>
   </tr>
   <tr>
    <th scope="row">目的:</th>
diff --git a/files/ja/learn/performance/web_performance_basics/index.html b/files/ja/learn/performance/web_performance_basics/index.html
index 276e2f2e04..02ea575063 100644
--- a/files/ja/learn/performance/web_performance_basics/index.html
+++ b/files/ja/learn/performance/web_performance_basics/index.html
@@ -12,23 +12,23 @@ translation_of: Learn/Performance/Web_Performance_Basics
 <h2 id="Best_practices">Best practices</h2>
 
 <ul>
- <li>Start with learning the <a href="https://developer.mozilla.org/en-US/docs/Web/Performance/Critical_rendering_path">critical rendering path</a> of the browser. Knowing this will help you understand how to improve the performance of the site.</li>
- <li>Using <a href="https://developer.mozilla.org/en-US/docs/Web/Performance/Controlling_resource_delivery_with_resource_hints">resource hints</a> such as <code>rel=preconnect, rel=dns-prefetch, rel=prefetch, and rel=preload</code></li>
+ <li>Start with learning the <a href="/ja/docs/Web/Performance/Critical_rendering_path">critical rendering path</a> of the browser. Knowing this will help you understand how to improve the performance of the site.</li>
+ <li>Using <a href="/ja/docs/Web/Performance/Controlling_resource_delivery_with_resource_hints">resource hints</a> such as <code>rel=preconnect, rel=dns-prefetch, rel=prefetch, and rel=preload</code></li>
  <li>Keep the size of Javascript to a <a href="https://medium.com/@addyosmani/the-cost-of-javascript-in-2018-7d8950fbb5d4">minimum</a>. Only use as much Javascript as needed for the current page.</li>
- <li><a href="https://developer.mozilla.org/en-US/docs/Learn/Performance/CSS_performance">CSS</a> performance factors</li>
- <li>Use <a href="https://developer.mozilla.org/en-US/docs/Learn/Performance/HTTP2">HTTP/2</a> on your server (or CDN).</li>
+ <li><a href="/ja/docs/Learn/Performance/CSS_performance">CSS</a> performance factors</li>
+ <li>Use <a href="/ja/docs/Learn/Performance/HTTP2">HTTP/2</a> on your server (or CDN).</li>
  <li>Use a CDN for resources which can reduce load times significantly.</li>
  <li>Compress your resources using <a href="https://www.gnu.org/software/gzip/" rel="nofollow noopener">gzip</a>, <a href="https://github.com/google/brotli" rel="nofollow noopener">Brotli</a>, and <a href="https://github.com/google/zopfli" rel="nofollow noopener">Zopfli</a>.</li>
  <li>Image optimization (use CSS animation, or SVG if possible).</li>
  <li>Lazy loading parts of your application outside the viewport. If you do, have a backup plan for SEO (e.g render full page for bot traffic); for example, by using the {{htmlattrxref("loading", "img")}} attribute on the {{HTMLElement("img")}} element</li>
- <li>It is also crucial to realize what is really important to your users. It might not be absolute timing, but <a href="https://developer.mozilla.org/en-US/docs/Learn/Performance/perceived_performance">user perception</a>.</li>
+ <li>It is also crucial to realize what is really important to your users. It might not be absolute timing, but <a href="/ja/docs/Learn/Performance/perceived_performance">user perception</a>.</li>
 </ul>
 
 <h2 id="Quick_Wins">Quick Wins</h2>
 
 <h3 id="CSS">CSS</h3>
 
-<p>Web performance is all about user experience and perceived performance. As we learned in the <a href="https://developer.mozilla.org/en-US/docs/Web/Performance/Critical_rendering_path">critical rendering path</a> document, linking CSS with a tradional link tag with rel="stylesheet" is synchronous and blocks rendering. Optimize the rendering of your page by removing blocking CSS.</p>
+<p>Web performance is all about user experience and perceived performance. As we learned in the <a href="/ja/docs/Web/Performance/Critical_rendering_path">critical rendering path</a> document, linking CSS with a tradional link tag with rel="stylesheet" is synchronous and blocks rendering. Optimize the rendering of your page by removing blocking CSS.</p>
 
 <p>To load CSS asynchronously one can simpy set the media type to print and then change to all once loaded. The following snippet includes an onload attribute, requiring Javascript, so it is important to include a noscript tag with a traditional fallback.</p>
 
@@ -45,13 +45,13 @@ translation_of: Learn/Performance/Web_Performance_Basics
 
 <h3 id="Javascript">Javascript</h3>
 
-<p>Avoid Javascript blocking by using the <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script">async</a> or <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script">defer</a> attributes, or link javascript assets after the page's DOM elements. Javascript only block rendering for elements that appear after the script tag in the DOM tree.</p>
+<p>Avoid Javascript blocking by using the <a href="/ja/docs/Web/HTML/Element/script">async</a> or <a href="/ja/docs/Web/HTML/Element/script">defer</a> attributes, or link javascript assets after the page's DOM elements. Javascript only block rendering for elements that appear after the script tag in the DOM tree.</p>
 
 <h3 id="Web_Fonts">Web Fonts</h3>
 
 <p>EOT and TTF formats are not compressed by default. Apply compression such as GZIP or Brotli for these file types. Use WOFF and WOFF2. These formats have compression built in.</p>
 
-<p>Within @font-face use font-display: swap. By using font display swap the browser will not block rendering and will use the backup system fonts that are defined. Optimiize <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/font-weight">font weight</a> to match the web font as closely as possible.</p>
+<p>Within @font-face use font-display: swap. By using font display swap the browser will not block rendering and will use the backup system fonts that are defined. Optimiize <a href="/ja/docs/Web/CSS/font-weight">font weight</a> to match the web font as closely as possible.</p>
 
 <h4 id="Icon_web_fonts">Icon web fonts</h4>
 
@@ -60,19 +60,19 @@ translation_of: Learn/Performance/Web_Performance_Basics
 <h2 id="Tools">Tools</h2>
 
 <ul>
- <li>Learn to use the <a href="https://developer.mozilla.org/en-US/docs/Tools/Performance">Firefox Dev Tools</a> to profile your site.</li>
+ <li>Learn to use the <a href="/ja/docs/Tools/Performance">Firefox Dev Tools</a> to profile your site.</li>
  <li><a href="https://developers.google.com/speed/docs/insights/v5/about">Pagespeed Insights</a> can analyze your page and give some general hints to improve performance.</li>
  <li><a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a> can give you a detailed breakdown of many aspects of your site including performance, SEO and accessibility.</li>
  <li>Test your page's speed using <a href="http://webpagetest.org/">Webpagetest.org</a>, where you can use different real device types and locations.</li>
  <li>Try the <a href="https://developers.google.com/web/tools/chrome-user-experience-report">Chrome User Experience Report</a> which quantifies real user metrics.</li>
- <li>Define a<a href="https://developer.mozilla.org/en-US/docs/Web/Performance/Performance_budget"> performance budget.</a></li>
+ <li>Define a<a href="/ja/docs/Web/Performance/Performance_budget"> performance budget.</a></li>
 </ul>
 
 <h3 id="APIs">APIs</h3>
 
 <ul>
  <li>Gather user metrics using <a href="https://github.com/akamai/boomerang">https://github.com/akamai/boomerang</a></li>
- <li>Or directly gather with <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/performance">window.performance.timing</a></li>
+ <li>Or directly gather with <a href="/ja/docs/Web/API/Window/performance">window.performance.timing</a></li>
 </ul>
 
 <h3 id="Things_not_to_do_bad_practices">Things not to do (bad practices)</h3>
diff --git a/files/ja/learn/performance/what_is_web_performance/index.html b/files/ja/learn/performance/what_is_web_performance/index.html
index 27dc13b688..a130006b2a 100644
--- a/files/ja/learn/performance/what_is_web_performance/index.html
+++ b/files/ja/learn/performance/what_is_web_performance/index.html
@@ -31,7 +31,7 @@ translation_of: Learn/Performance/What_is_web_performance
 	</tbody>
 </table>
 
-<p><em>* 次の記事で扱う主観的な<a href="/en-US/docs/Learn/Performance/Perceived_performance">知覚パフォーマンス</a>の対義語</em></p>
+<p><em>* 次の記事で扱う主観的な<a href="/ja/docs/Learn/Performance/Perceived_performance">知覚パフォーマンス</a>の対義語</em></p>
 
 <h2 id="What_is_web_performance">ウェブパフォーマンスとは何か</h2>