Updated readme

README.md

@@ -47,6 +47,8 @@ The deployment features supported currently by Clace are:
 
 - Backend app code run in a [security sandbox](https://clace.io/docs/applications/appsecurity/#security-model), with allowlist based permissions.
 - [No build step](https://clace.io/docs/app/overview/#app-lifecycle), the development artifacts are ready for production use.
+- Support for github integration, apps being directly deployed from github code.
+- Database backed application file system, for atomic version updates and rollbacks.
 - Zero downtime application updates.
 - Scalable backend, all performance critical code is in Go, only application handler code is in Starlark.
 - Support for domain based and path based [routing](https://clace.io/docs/applications/routing/#request-routing) at the app level.
@@ -60,9 +62,8 @@ Clace is early in its development. The feature roadmap for Clace is:
 - Support for OAuth2 based login.
 - Support for SSO with SAML.
 - All plugins are internal (built into Clace binary) currently. The plan is to move to an external plugin model, plugins being loaded dynamically using [go-plugin](/~https://github.com/hashicorp/go-plugin).
-- Support for github integration, apps being deployed from artifacts directly loaded from github.
-- SQLite is used as the metadata storage currently. Support for postgres and other systems is planned.
-- Preview mode for app updates, to check whether changes work before making them live.
+- SQLite is used for metadata storage currently. Support for postgres and other systems is planned.
+- Staging mode for app updates, to verify whether changes work before making them live.
 - Support for workflow jobs, which would have a form based interface with limited customizability, but with support for triggered and scheduled execution.
 - Support for application data persistance.
 - UI interface for Clace admin operations.