[JENKINS-31153] More renames.

Originally-Committed-As: 199d8c9dc7ec8d02d6429dd652f666f14cbfc660

scm-step/README.md

@@ -50,7 +50,7 @@ This means that you can run multiple SCMs, even from a dynamic list, and get a r
 ## Polling
 
 If you configure the _Poll SCM_ trigger in the Pipeline’s UI configuration screen, then by default Jenkins will also poll for changes according to the selected _Schedule_, and schedule new builds automatically if changes are detected.
-(Note that this configuration is not part of the flow script, because it affects activities that Jenkins runs outside of the flow.)
+(Note that this configuration is not part of the Pipeline script, because it affects activities that Jenkins runs outside of the Pipeline.)
 Some SCMs allow polling with no workspace, which is ideal; others will try to lock the same slave and workspace previously used, to run polling on the slave.
 
 To avoid polling the server repeatedly, most SCM plugins allow remote commit triggers, such as the `/git/notifyCommit?url=…` HTTP endpoint in the case of the Git plugin.

scm-step/src/main/resources/org/jenkinsci/plugins/workflow/steps/scm/GenericSCMStep/help.html

@@ -1,7 +1,7 @@
 <div>
     <p>
     This is a special step that allows to run checkouts using any configuration
-    options offered by any Workflow-compatible SCM plugin.
+    options offered by any Pipeline-compatible SCM plugin.
     To use a concrete SCM implementations, just install the corresponding plugin 
     and check if it is shown in the list below.
     Then select the SCM to use from the dropdown list and configure it as needed.
@@ -10,4 +10,4 @@
     Any other specific step to run checkouts (like <code>svn</code> or <code>git</code>)
     are simplistic options of this step.
     </p>
-</div>
+</div>