scaleway
diff --git a/‎pages/object-storage/faq.mdx‎
Lines changed: 0 additions & 2 deletions b/‎pages/object-storage/faq.mdx‎
Lines changed: 0 additions & 2 deletions
diff --git a/‎pages/billing/assets/scaleway-Billing-FaaS-1-DEF.webp‎ renamed to ‎pages/serverless-functions/assets/scaleway-Billing-FaaS-1-DEF.webp‎ b/‎pages/billing/assets/scaleway-Billing-FaaS-1-DEF.webp‎ renamed to ‎pages/serverless-functions/assets/scaleway-Billing-FaaS-1-DEF.webp‎
diff --git a/‎pages/billing/assets/scaleway-Billing-FaaS-2-DEF.webp‎ renamed to ‎pages/serverless-functions/assets/scaleway-Billing-FaaS-2-DEF.webp‎ b/‎pages/billing/assets/scaleway-Billing-FaaS-2-DEF.webp‎ renamed to ‎pages/serverless-functions/assets/scaleway-Billing-FaaS-2-DEF.webp‎
@@ -177,8 +177,6 @@ No, because restoring an object can only be done from Glacier to Standard class.
 
 This means that you can transfer objects from Standard class to One Zone - IA and Glacier, but not from the last two to Standard. You can transfer objects from One Zone - IA to Glacier, but not restore objects from Glacier to One Zone - IA. The same applies when you make server-side copies.
 
-<Lightbox src="scaleway-schema-life-cycle-object-storage.webp" alt="" />
-
 ## Do the new storage classes impact Scaleway Glacier?
 
 No, the rules for using Glacier class remain the same and your data is still hosted in DC4. Refer to the [Cold storage section](#cold-storage) for more information on Scaleway Glacier.