Browse A-Z

機械支援の翻訳下書き (Japanese) for "Spaced Repetition Practice: Focus more time on difficult material": A practice rule for Spaced Repetition: Focus more time on difficult material with shorter intervals.

“例文の下書き: The learner applied this spaced repetition practice during a cross-domain study session.”

機械支援の翻訳下書き (Japanese) for "Spaced Repetition Practice: Increase intervals between reviews as retention": A practice rule for Spaced Repetition: Increase intervals between reviews as retention improves.

“例文の下書き: The learner applied this spaced repetition practice during a cross-domain study session.”

機械支援の翻訳下書き (Japanese) for "Spaced Repetition Practice: Review new material within 24 hours": A practice rule for Spaced Repetition: Review new material within 24 hours of initial learning.

“例文の下書き: The learner applied this spaced repetition practice during a cross-domain study session.”

機械支援の翻訳下書き (Japanese) for "Spaced Repetition Practice: Use active recall (testing yourself) rather": A practice rule for Spaced Repetition: Use active recall (testing yourself) rather than passive review.

“例文の下書き: The learner applied this spaced repetition practice during a cross-domain study session.”

機械支援の翻訳下書き (Japanese) for "Spaced Repetition Practice: Use software tools to automate optimal": A practice rule for Spaced Repetition: Use software tools to automate optimal scheduling.

“例文の下書き: The learner applied this spaced repetition practice during a cross-domain study session.”

機械支援の翻訳下書き (Japanese) for "Spam Risk Badge": The Spam Risk Badge is a visible trust marker that supports trust decisions around spam risk in PlatPhorm News. It helps reviewers and agents evaluate whether article listings, sources, domains, and links should be trusted, warned, or escalated.

“例文の下書き: The Spam Risk Badge was attached to the listing so reviewers could judge the source before promoting the story.”

機械支援の翻訳下書き (Japanese) for "Spam Risk Evidence": The Spam Risk Evidence is a supporting record that supports trust decisions around spam risk in PlatPhorm News. It helps reviewers and agents evaluate whether article listings, sources, domains, and links should be trusted, warned, or escalated.

“例文の下書き: The Spam Risk Evidence was attached to the listing so reviewers could judge the source before promoting the story.”

機械支援の翻訳下書き (Japanese) for "Spam Risk Flag": The Spam Risk Flag is a review marker that supports trust decisions around spam risk in PlatPhorm News. It helps reviewers and agents evaluate whether article listings, sources, domains, and links should be trusted, warned, or escalated.

“例文の下書き: The Spam Risk Flag was attached to the listing so reviewers could judge the source before promoting the story.”

機械支援の翻訳下書き (Japanese) for "Spam Risk Policy": The Spam Risk Policy is a rule set that supports trust decisions around spam risk in PlatPhorm News. It helps reviewers and agents evaluate whether article listings, sources, domains, and links should be trusted, warned, or escalated.

“例文の下書き: The Spam Risk Policy was attached to the listing so reviewers could judge the source before promoting the story.”

機械支援の翻訳下書き (Japanese) for "Spam Risk Score": The Spam Risk Score is a numeric or qualitative rating that supports trust decisions around spam risk in PlatPhorm News. It helps reviewers and agents evaluate whether article listings, sources, domains, and links should be trusted, warned, or escalated.

“例文の下書き: The Spam Risk Score was attached to the listing so reviewers could judge the source before promoting the story.”

機械支援の翻訳下書き (Japanese) for "Sports Context": The Sports Context is a topic framing that organizes sports coverage within PlatPhorm News. It connects domain nodes, article listings, topic feeds, and service routes so readers and agents can navigate by subject area.

“例文の下書き: The Sports Context helped group related PlatPhorm articles, sites, and services under the same subject area.”

機械支援の翻訳下書き (Japanese) for "Sports Feed": The Sports Feed is a stream of related entries that organizes sports coverage within PlatPhorm News. It connects domain nodes, article listings, topic feeds, and service routes so readers and agents can navigate by subject area.

“例文の下書き: The Sports Feed helped group related PlatPhorm articles, sites, and services under the same subject area.”

機械支援の翻訳下書き (Japanese) for "Sports Listing": The Sports Listing is a feed entry type that organizes sports coverage within PlatPhorm News. It connects domain nodes, article listings, topic feeds, and service routes so readers and agents can navigate by subject area.

“例文の下書き: The Sports Listing helped group related PlatPhorm articles, sites, and services under the same subject area.”

機械支援の翻訳下書き (Japanese) for "Sports Route": The Sports Route is a navigable path that organizes sports coverage within PlatPhorm News. It connects domain nodes, article listings, topic feeds, and service routes so readers and agents can navigate by subject area.

“例文の下書き: The Sports Route helped group related PlatPhorm articles, sites, and services under the same subject area.”

機械支援の翻訳下書き (Japanese) for "Sports Vertical": The Sports Vertical is a subject-area grouping that organizes sports coverage within PlatPhorm News. It connects domain nodes, article listings, topic feeds, and service routes so readers and agents can navigate by subject area.

“例文の下書き: The Sports Vertical helped group related PlatPhorm articles, sites, and services under the same subject area.”

機械支援の翻訳下書き (Japanese) for "Storage Autoscaling Policy": Storage Autoscaling Policy is a compute control loop that changes capacity based on demand signals for persistent data and object access. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.

“例文の下書き: The platform engineering team used Storage Autoscaling Policy when the workload read a large dataset, so the team could match resources to load before the workload scaled up.”

機械支援の翻訳下書き (Japanese) for "Storage Backpressure Control": Storage Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for persistent data and object access. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.

“例文の下書き: The platform engineering team used Storage Backpressure Control when the workload read a large dataset, so the team could avoid overload cascades before the workload scaled up.”

機械支援の翻訳下書き (Japanese) for "Storage Cache Invalidation": Storage Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for persistent data and object access. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.

“例文の下書き: The platform engineering team used Storage Cache Invalidation when the workload read a large dataset, so the team could serve current results before the workload scaled up.”

機械支援の翻訳下書き (Japanese) for "Storage Capacity Forecast": Storage Capacity Forecast is a compute planning model that estimates future resource needs for persistent data and object access. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.

“例文の下書き: The platform engineering team used Storage Capacity Forecast when the workload read a large dataset, so the team could avoid surprise shortages before the workload scaled up.”

機械支援の翻訳下書き (Japanese) for "Storage Checkpoint Restore": Storage Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for persistent data and object access. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.

“例文の下書き: The platform engineering team used Storage Checkpoint Restore when the workload read a large dataset, so the team could recover long-running work before the workload scaled up.”