(AzureCXP) fixes MicrosoftDocs/azure-docs#107783

YashikaTyagii · web-flow · commit d2317ca8725c · 2023-04-10T14:09:18.000+05:30
performed changes in line no. 145, 146, 147
changed to
&lt;UserJourney Id="HelloWorldJourney"&gt;
  &lt;OrchestrationSteps&gt;
    &lt;OrchestrationStep Order="1" Type="SendClaims" CpimIssuerTechnicalProfileReferenceId="JwtIssuer" /&gt;
  &lt;/OrchestrationSteps&gt;
&lt;/UserJourney&gt;
diff --git a/articles/active-directory-b2c/custom-policies-series-hello-world.md b/articles/active-directory-b2c/custom-policies-series-hello-world.md
@@ -143,8 +143,10 @@ If you haven't already done so, create the following encryption keys. To automat
 
     ```xml
       <UserJourney Id="HelloWorldJourney">
-        <OrchestrationStep Order="1" Type="SendClaims" CpimIssuerTechnicalProfileReferenceId="JwtIssuer" />
-      </UserJourney>
+  <OrchestrationSteps>
+    <OrchestrationStep Order="1" Type="SendClaims" CpimIssuerTechnicalProfileReferenceId="JwtIssuer" />
+  </OrchestrationSteps>
+</UserJourney>
     ```
     
     We've added a [UserJourney](userjourneys.md). The user journey specifies the business logic the end user goes through as Azure AD B2C processes a request. This user journey has only one step that issues a JTW token with the claims that you'll define in the next step.
