Fix docs inconsistencies (#214)
Summary: When referring to the project, we usually capitalize Flipper, but don't do this super consistently. This fixes a few cases and some other grammar issues. Pull Request resolved: https://github.com/facebook/flipper/pull/214 Reviewed By: jknoxville Differential Revision: D9219587 Pulled By: passy fbshipit-source-id: 4c2a30730b8719ea4c058ad3c6cc262cbbdf6266
This commit is contained in:
committed by
Facebook Github Bot
parent
047b6ed7b7
commit
b22f02510c
@@ -3,7 +3,7 @@ id: layout-plugin
|
||||
title: Layout Inspector
|
||||
---
|
||||
|
||||
The Layout Inspector in Flipper is useful for a ton of different debugging scenarios. First of all you can inspect what views the hierarchy is made up of as well as what properties each view has. This is incredibly useful when debugging issues with your product.
|
||||
The Layout Inspector in Flipper is useful for a ton of different debugging scenarios. First of all, you can inspect what views the hierarchy is made up of as well as what properties each view has. This is incredibly useful when debugging issues with your product.
|
||||
|
||||
The Layout tab supports [Litho](https://fblitho.com) and [ComponentKit](https://componentkit.org) components as well! We integrate with these frameworks to present components in the hierarchy just as if they were native views. We show you all the layout properties, props, and state of the components. The layout inspector is further extensible to support other UI frameworks.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user