Update fix-the-problem.md

Author: sdgilley

fix-the-problem.md

@@ -1,6 +1,13 @@
 # Fix the problem 
 
-When the pr-report shows a problem in a PR, you need to fix the problem before you can approve the PR.
+We currently have two code repos:
+
+| Docs reference | Code repo |
+| ---------------|-----------|
+| ~/azureml-examples-main | https://github.com/Azure-Samples/azureai-samples |
+| ~/foundry-samples-main | https://github.com/azure-ai-foundry/foundry-samples |
+
+When the pr-report shows a problem in a PR in either of these repos, you need to fix the problem before you can approve the PR.
 
 The problems that will break our build are:
 
@@ -11,7 +18,7 @@ Before the PR can be approved, we need to make sure that the docs that reference
 
 There are various ways to fix the problem, depending on the situation.  These are outlined in the sections below.
 
-> During a docs freeze (before Build or Ignite), don't approve any azureml-examples PRs that have problems - we can't fix them on our end during this time.  If they deleted a file, have them put it back.  If they deleted an ID or cell name, have them put it back, even if there are no contents in the section or cell.
+> During a docs freeze (before Build or Ignite), don't approve any PRs that have problems - we can't fix them on our end during this time.  If they deleted a file, have them put it back.  If they deleted an ID or cell name, have them put it back, even if there are no contents in the section or cell.
 > 
 ## Push back - why is the change needed?
 
@@ -56,18 +63,18 @@ If you can quickly fix the reference in azure-ai-docs-pr, do so.  For example, i
 * Create a PR in azure-ai-docs-pr to apply this fix.  
 * After your azure-ai-docs-pr PR with the fix is merged, you can approve the azureml-examples PR.
 
-> NOTE FOR RELEASE BRANCHES: During Build or Ignite, when there are release branches, this process is more complex. All those release branches also need your update.  Coordinate with the Build/Ignite roadshow owner before you approve the azureml-examples PR.  They'll need to sync main into the release branches before you can approve the original azureml-examples PR.
+> NOTE FOR RELEASE BRANCHES: During Build or Ignite, when there are release branches, this process is more complex. All those release branches also need your update.  Coordinate with the Build/Ignite roadshow owner before you approve the code repo's PR.  They'll need to sync main into all release branches before you can approve the original code repo PR.
 
 ## Move to a temporary branch
 
 If you can't do a quick fix, follow this process:
 
 1. If temp-fix has the same version of the file, skip 2 and proceed to #3.
-1. If temp-fix does not have the same version of the file, use the steps below to first [update the temp-fix branch](#temp-fix) in azureml-examples.
+1. If temp-fix does not have the same version of the file, use the steps below to first [update the temp-fix branch](#temp-fix) in the code repo.
 1. <a name="three"></a> Create a PR in azure-ai-docs-pr to use **~/azureml-examples-temp-fix** instead of **~/azureml-examples-main** for the reference(s) to the problem file/id(s).
-1. Once your PR in azure-ai-docs-pr is merged to main, you can approve the azureml-examples PR.
-   > NOTE FOR RELEASE BRANCHES: During Build or Ignite, when there are release branches, this process is more complex. All those release branches also need your update.  Coordinate with the Build/Ignite roadshow owner before you approve the azureml-examples PR.  They'll need to sync main into the release branches before you can approve the original azureml-examples PR.
-1. Create a work item to update these articles to again use ~/azureml-examples-main after the azureml-examples PR has merged.  We want to minimize the time that an article references a file on the temp-fix branch.
+1. Once your PR in azure-ai-docs-pr is merged to main, you can approve the code repo PR.
+   > NOTE FOR RELEASE BRANCHES: During Build or Ignite, when there are release branches, this process is more complex. All those release branches also need your update.  Coordinate with the Build/Ignite roadshow owner before you approve the azureml-examples PR.  They'll need to sync main into the release branches before you can approve the original code repo PR.
+1. Create a work item to update these articles to again use ~/azureml-examples-main or ~/foundry-samples-main after the azureml-examples PR has merged.  We want to minimize the time that an article references a file on the temp-fix branch.
 ### Example
 
 You'll see the following output from `python GitHub/pr-report.py 2888`: