message: Adding to docs on accessing app info
diff: @@ -56,28 +56,37 @@ Error: Do not directly set the environment for a stack
  This is by design. The stacks in SST are meant to be re-deployed for multiple stages (like Serverless Framework). And so they depend on the region and AWS profile that's passed in through the CLI. If a stack is hardcoded to be deployed to a specific account or region, it can break your deployment pipeline.
  -### Prefixing resource names
  -You can optionally prefix resource names to make sure they don't thrash when deployed to different stages in the same AWS account.
  +### Accessing app info
  -You can do so in your stacks.
  +The stage, region, and app name can be accessed through the app object.
  -```jsx
  -this.node.root.logicalPrefixedName("MyResource");
  -```
  +So in the `lib/index.js` you can access it using.
  -This invokes the `logicalPrefixedName` method in `sst.App` that your stack is added to.
  +``` js
  +app.stage
  +app.region
  +app.name
  +```
  -You can also get the stage name using.
  +And in your stack classes (for example, `lib/MyStack.js`) you can use.
  -```jsx
  -this.node.root.stage;
  +``` js
  +this.node.root.stage
  +this.node.root.region
  +this.node.root.name
  ```
  -And the app name using.
  +You can use this to conditionally add stacks or resources to your app.
  +
  +### Prefixing resource names
  +
  +You can optionally prefix resource names to make sure they don't thrash when deployed to different stages in the same AWS account.
  +
  +You can do so in your stacks.
  ```jsx
  -this.node.root.name;
  +this.node.root.logicalPrefixedName("MyResource") // Returns "dev-my-sst-app-MyResource"
  ```
  -Again these access the `sst.App` that your stacks are added to.
  +This invokes the `logicalPrefixedName` method in `sst.App` that your stack is added to. This'll return `dev-my-sst-app-MyResource`, where `dev` is the current stage and `my-sst-app` is the name of the app.
  