Web/API以下の文書内のリンクURLを正規化 (#2360)

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

2 files changed, 5 insertions, 5 deletions

diff --git a/files/ja/web/api/frame_timing_api/index.html b/files/ja/web/api/frame_timing_api/index.html
index 7f2a31ec71..abf14b743d 100644
--- a/files/ja/web/api/frame_timing_api/index.html
+++ b/files/ja/web/api/frame_timing_api/index.html
@@ -51,6 +51,6 @@ translation_of: Web/API/Frame_Timing_API
 <h2 id="See_also">See also</h2>
 
 <ul>
- <li><a href="/docs/Tools/Performance/Frame_rate">Frame Rate (Firefox Performance Tool)</a></li>
+ <li><a href="/ja/docs/Tools/Performance/Frame_rate">Frame Rate (Firefox Performance Tool)</a></li>
  <li><a href="/Web/API/Frame_Timing_API/Using_the_Frame_Timing_API">Using the Frame Timing API</a></li>
 </ul>
diff --git a/files/ja/web/api/frame_timing_api/using_the_frame_timing_api/index.html b/files/ja/web/api/frame_timing_api/using_the_frame_timing_api/index.html
index fa1be473f4..ae5be9ee24 100644
--- a/files/ja/web/api/frame_timing_api/using_the_frame_timing_api/index.html
+++ b/files/ja/web/api/frame_timing_api/using_the_frame_timing_api/index.html
@@ -119,11 +119,11 @@ observe_frame.observe({entryTypes: ['frame']});
 
 <h3 id="Firefox_performance_tool">Firefox performance tool</h3>
 
-<p>Firefox's performance tool allows the developer to <em>record</em> a piece of the user's interaction and the data obtained during the recording is used to create a <em>profile</em> of the browser's activity. The profile includes a <em><a href="https://developer.mozilla.org/en-US/docs/Tools/Performance/Waterfall">waterfall</a></em> of the activity such as event handling, layout, painting, scripting, etc.</p>
+<p>Firefox's performance tool allows the developer to <em>record</em> a piece of the user's interaction and the data obtained during the recording is used to create a <em>profile</em> of the browser's activity. The profile includes a <em><a href="/ja/docs/Tools/Performance/Waterfall">waterfall</a></em> of the activity such as event handling, layout, painting, scripting, etc.</p>
 
-<p>Firefox's performance tool also includes a <em><a href="https://developer.mozilla.org/en-US/docs/Tools/Performance/Frame_rate">frame rate graph</a></em> which provides timestamps for each frame including the average frame rate and the minimum and maximum rates (for a specific recording session). This data, along with the waterfall data, gives an indication of where a site might be having frame related performance problems (for example, by correlating the recording's minimum rates with their respective waterfall events).</p>
+<p>Firefox's performance tool also includes a <em><a href="/ja/docs/Tools/Performance/Frame_rate">frame rate graph</a></em> which provides timestamps for each frame including the average frame rate and the minimum and maximum rates (for a specific recording session). This data, along with the waterfall data, gives an indication of where a site might be having frame related performance problems (for example, by correlating the recording's minimum rates with their respective waterfall events).</p>
 
-<p>The performance tool's <em><a href="https://developer.mozilla.org/en-US/docs/Tools/Performance/Flame_Chart">flame chart</a></em> and <em><a href="https://developer.mozilla.org/en-US/docs/Tools/Performance/Call_Tree">call tree</a></em> tabs provide data to help analyze the site's JavaScript usage. The call tree shows where the application is spending most of its time, whereas the flame chart shows the state of the JavaScript stack for the code at every millisecond during the performance profile. This provides a way to know exactly which function was executing at any point during the recording, how long it ran, and where it was called from.</p>
+<p>The performance tool's <em><a href="/ja/docs/Tools/Performance/Flame_Chart">flame chart</a></em> and <em><a href="/ja/docs/Tools/Performance/Call_Tree">call tree</a></em> tabs provide data to help analyze the site's JavaScript usage. The call tree shows where the application is spending most of its time, whereas the flame chart shows the state of the JavaScript stack for the code at every millisecond during the performance profile. This provides a way to know exactly which function was executing at any point during the recording, how long it ran, and where it was called from.</p>
 
 <h3 id="Chrome_performance_tool">Chrome performance tool</h3>
 
@@ -132,6 +132,6 @@ observe_frame.observe({entryTypes: ['frame']});
 <h2 id="あわせて参照">あわせて参照</h2>
 
 <ul>
- <li><a href="/docs/Tools/Performance/Frame_rate">Frame Rate (Firefox Performance Tool)</a></li>
+ <li><a href="/ja/docs/Tools/Performance/Frame_rate">Frame Rate (Firefox Performance Tool)</a></li>
  <li><a href="https://w3c.github.io/frame-timing/">Frame Timing</a>; W3C Editor's Draft</li>
 </ul>