fix(iam): review ro

Co-authored-by: Rowena Jones <[email protected]>

Author: ldecarvalho-doc

pages/iam/reference-content/guests-to-members-migration.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
   title: IAM Guests to Members migration
-  description: Learn how to migrate IAM guests to members, including roles and API keys, with Scaleway's IAM introduction
+  description: Learn how to migrate IAM Guests to Members, including roles and API keys, with Scaleway's IAM introduction
 content:
   h1: IAM Guests to Members Migration
-  paragraph: This page guides you through the process of migrating IAM guests to members, covering key aspects such as roles and API keys, following the introduction of IAM on Scaleway
+  paragraph: This page guides you through the process of migrating IAM Guests to Members, covering key aspects such as roles and API keys, following the introduction of IAM on Scaleway
 tags: iam migration
 categories:
   - iam
@@ -28,11 +28,12 @@ Whereas Owners have full rights and access to all resources and features in thei
 From June 2025, IAM Guests will become IAM Members. The migration process will be carried out in two phases:
 
     - **Phase 1** - Starting on the *18th of July 2025*, the [manual migration of Guests](#how-to-manually-migrate-a-user-from-guest-to-member) will be available in the Console to all Owners and users with [IAMManager permissions](/iam/reference-content/permission-sets).
-    - **Phase 2** - Starting in *July 2025*, Guests that have not yet become members will be automatically migrated.
+    - **Phase 2** - Starting in *July 2025*, Guests that have not yet become Members will be automatically migrated.
 
 Keep in mind that:
 
 - Members exist only within the Organizations in which they were created, and have a [dedicated login process](/iam/how-to/log-in-as-a-member).
+- Migrating a Guest to a Member does not mean that the Guest loses the Organization of which they are Owner. However, when creating Members in the future who do not already have Scaleway accounts, they will not be obliged to create their own Organization.
 - Organization admins manage Member accounts, including enforcing security requirements (MFA, password renewal).
 - Single Sign-On (SSO) remains available.
 - The management of API keys, IAM policies, and groups remains the same.
@@ -52,7 +53,7 @@ The table below summarizes the key account and access management features that S
 
 | Feature | Guests | Members |
 |:--------:|:---------:|:---------:|
-| Login | Guests logged into their own accounts and could access all Organizations they were a part of via the console. | Currently, Members must log into their Organizations to access it. If they are logged into a different Organization with the same email, they must log out before logging into the other. |
+| Login | Guests logged into their own accounts and could access all Organizations they were a part of via the console. | Currently, Members must log into each of their Organizations separately to access them. If they log into an Organization, then want to access a different one using the same email, they must log out of the former first. |
 | Enforcement of MFA | It was not possible to enforce MFA if a Guest in your Organization had not enabled MFA in their account. Organization admins could send reminder emails, but had to wait for the Guest to enable MFA, or remove them from the Organization to complete the enforce process. | When MFA is enforced in the Organization, Members have a [grace period](iam/concepts/#grace-period) to enable MFA in their accounts. This period is set by the Organization admins and starts as soon as a new Member is added. If they fail to enable MFA within this period, their accounts are locked. |
 | Password renewal | Guests were not required to renew their passwords to stay in an Organization. | As a security measure, Organization admins can require Members to renew their passwords within a grace period. If a password was attributed to Members upon their creation, they must renew this password after their first login. |
 | User management | Guest accounts and personal Organizations could not be managed by anyone other than them. Their permissions on Organizations they were invited to are the prerogative of Organization admins. | Member accounts are an 100% manageable resource - they can be created, updated, locked and deleted by Organization admins. |
@@ -61,7 +62,7 @@ The table below summarizes the key account and access management features that S
 ## How to manually migrate a user from Guest to Member
 
 <Message type="important">
-  The migration does not effect any impacts to your production.
+  The migration does not have any impact on your production.
 </Message>
 
 <Macro id="requirements" />