Fix missing image in RH-SSO docs

authorization_services/topics/policy-client-scope-policy-required-client-scope.adoc

@@ -4,7 +4,7 @@
 When creating a client scope-based policy, you can specify a specific client scope as `Required`. When you do that, the policy will grant access only if the client requesting access has been granted *all* the *required* client scopes.
 
 .Example of Required Client Scope
-image:{project_images}/policy/create-client-scope.png[alt="Example of Required Client Scope"]
+image:images/policy/create-client-scope.png[alt="Example of Required Client Scope"]
 
 To specify a client scope as required, select the `Required` checkbox for the client scope you want to configure as required.
 

authorization_services/topics/policy-client-scope-policy.adoc

@@ -8,7 +8,7 @@ By default, client scopes added to this policy are not specified as required and
 To create a new client scope-based policy, select *Client Scope* in the dropdown list in the upper right corner of the policy listing.
 
 .Add Client Scope-Based Policy
-image:{project_images}/policy/create-client-scope.png[alt="Add Client Scope-Based Policy"]
+image:images/policy/create-client-scope.png[alt="Add Client Scope-Based Policy"]
 
 == Configuration
 

server_admin/topics/clients/oidc/confidential.adoc

@@ -24,7 +24,7 @@ When choosing this credential type you will have to also generate a private key
 The private key will be used to sign the JWT, while the certificate is used by the server to verify the signature.
 
 .Keys Tab
-image:{project_images}/client-oidc-keys.png[]
+image:images/client-oidc-keys.png[]
 
 Click on the `Generate new keys and certificate` button to start this process.